[636] in linux-scsi channel archive
Conner CP30170E freezes during bus scan
daemon@ATHENA.MIT.EDU (Paul C. Dulany)
Mon Sep 25 17:54:45 1995
Date: Mon, 25 Sep 1995 12:36:22 -0400 (EDT)
From: "Paul C. Dulany" <dulany@quark.umd.edu>
To: linux-scsi@vger.rutgers.edu
Hello all,
Summary:
I have been having trouble with my Conner CP30170E and Linux. When
the kernel scans the SCSI bus at boot-up, the Conner freezes up the
computer, and will not respond until I cycle power (a reset does not
work). Everything works fine with DOS.
Details:
Kernels: 1.0.9, 1.2.13, 1.3.29
SCSI card: Future Domain 1680
SCSI Devices: id 1 -- DEC TK50 tape drive
id 3 -- Conner CP30170E hard drive
(IDE Drives: WD2540 and WD280 on hda and hdb respectively.)
Everything works great using DOS (if one can call DOS great). I have
also gotten the SCSI card to work great with borrowed hard drives and
my tape drive.
With just the Conner drive (no otjer SCSI devices), I get the
following when the BIOS scans the bus:
Future Domain 1800/18C50 SCSI ROM BIOS v3.00
(C) 1992 FUTURE DOMAIN CORP
ID 3 LUN 0 CONNER CP30170E - 170Mb Firmware Rev. 5.13
512 bytes per sector. (S)
When the kernel (1.3.29) boots, I get:
scsi0 <fdomain>: BIOS version 3.0 at 0xca000 using scsi id 6
scsi0 <fdomain>: TMC-1800 chip at 0x140 irq 5
scsi0 : Future Domain TMC-16x0 SCSI driver, version 5.36
scsi : 1 host.
fdomain: Selection failed
scsi: aborting command due to timeout: pid 4, scsi0, channel 0, id 3, lun 0, Inquiry 00 00 00 ff 00
fdomain: abort
Future Domain TMC-16x0 SCSI driver, version 5.36
scsi0 <fdomain>: BIOS version 3.0 at 0xca000 using scsi id 6
scsi0 <fdomain>: TMC-1800 chip at 0x140 irq 5
other (8), target = 3 cmd = 0x12 pieces = 0 size = 256
sent_command = 6, have_data_in = 1, timeout = 50
in_interrupt_flag = 0
FRM = 0xdfd8, IRR = 0x0009, ISR = 0x0000
SCSI Statue = 0x05
TMC Status = 0xe0
Interrupt Status = 0x99 (enabled)
Configuration 1 = 0x42
Interrupt after abort, ignoring
Then the computer freezes. If I reset the computer, the _BIOS_ no longer
recognizes the Conner drive, although I can boot up. I need to cycle
power before the drive answers again.
I have also compiled kernel 1.2.13 to display every SCSI command, and it
appears that the last command sent to the drive is 12 00 00 00 ff 00. (I
can e-mail the full output to anyone interested.) I have sent this command
to the drive using the Future Domain diagnostics in DOS and had no
problems. Once again, the card and driver work fine with my tape deck and
a borrowed drive under Linux.
I am stumped. Please help me to figure this out. I would really like
to get this drive up and working with Linux, or at least know _why_ it
is impossible to do that.
Thanks!
Paul
________________________________________________________________________
Paul C. Dulany dulany@quark.umd.edu
"I hold that a little rebellion now and then is a good thing, & as
necessary in the political world as storms in the physical."
Thomas Jefferson
Letter to James Madison
Jan. 30, 1787
