by I recently downloaded and compiled 1.3.84, and I can't seem to get
my SCSI ZIP drive to work. Basically, I config'd the low level driver,
g_NCR5380, to include the ncr53c400 extensions, and built all scsi support
as modules (scsi_mod, sd_mod, g_NCR5380). Everything compiled ok in a.out
format (except I had to install gawk3.0 for 'make dep', and my sources
seem to get munged after a build?!?) with 'make zImage', 'make modules',
and 'make modules_install'. After rebooting, I performed the following
steps: 'insmod scsi_mod' 'insmod g_NCR5380'
scsi0 : at port 0x358 irq 5 options CAN_QUEUE=16 CMD_PER_LUN=2
release=1 generic options AUTOPROBE_IRQ AUTOSENSE PSEUDO DMA generic
release=6 ncr53c400 release=2
scsi0 : Generic NCR5380/53C400 Driver
scsi : 1 host.
Vendor: IOMEGA Model: ZIP 100 Rev: C.22
Type: Direct-Access ANSI SCSI revision: 02
'insmod sd_mod'
--> KABOOM!
here's the syslog result:
Apr 9 22:16:18 red_dog kernel: scsi0 : aborting command
Apr 9 22:16:18 red_dog kernel: scsi0 : destination target 5, lun 0
Apr 9 22:16:18 red_dog kernel: command = Read (6) 00 00 00 02 00
Apr 9 22:16:18 red_dog kernel: NCR5380 : coroutine isn't running.
Apr 9 22:16:18 red_dog kernel: STATUS_REG: 07 ,PARITY,IO,SEL
Apr 9 22:16:18 red_dog kernel: BASR: 10
Apr 9 22:16:18 red_dog kernel: ICR: 00
Apr 9 22:16:18 red_dog kernel: MODE: 00
Apr 9 22:16:18 red_dog kernel: scsi0 : REQ not asserted, phase unknown.
Apr 9 22:16:18 red_dog kernel: scsi0: no currently connected command
Apr 9 22:16:18 red_dog kernel: scsi0: issue_queue
Apr 9 22:16:18 red_dog kernel: scsi0: disconnected_queue
Apr 9 22:16:18 red_dog kernel: scsi0 : destination target 5, lun 0
Apr 9 22:16:18 red_dog kernel: command = Read (6) 00 00 00 02 00
Apr 9 22:16:18 red_dog kernel: scsi0 : aborting command
Apr 9 22:16:18 red_dog kernel: scsi0 : destination target 5, lun 0
Apr 9 22:16:18 red_dog kernel: command = Read (6) 00 00 00 02 00
Apr 9 22:16:18 red_dog kernel: NCR5380 : coroutine isn't running.
Apr 9 22:16:18 red_dog kernel: STATUS_REG: 07 ,PARITY,IO,SEL
Apr 9 22:16:18 red_dog kernel: BASR: 10
Apr 9 22:16:18 red_dog kernel: ICR: 00
Apr 9 22:16:18 red_dog kernel: MODE: 00
Apr 9 22:16:18 red_dog kernel: scsi0 : REQ not asserted, phase unknown.
Apr 9 22:16:18 red_dog kernel: scsi0: no currently connected command
Apr 9 22:16:18 red_dog kernel: scsi0: issue_queue
Apr 9 22:16:18 red_dog kernel: scsi0: disconnected_queue
Apr 9 22:16:18 red_dog kernel: scsi0 : destination target 5, lun 0
Apr 9 22:16:18 red_dog kernel: command = Read (6) 00 00 00 02 00
Apr 9 22:16:18 red_dog kernel: SCSI disk error : host 0 channel 0 id 5 lun 0 return code = 50000
Apr 9 22:16:18 red_dog kernel: scsidisk I/O error: dev 08:00, sector 0
Apr 9 22:16:18 red_dog kernel: unable to read partition table
After 'insmod sd_mod', the drive is initially recognized, and
then it pauses for a few seconds, then the above error messages are
printed. Sometimes the driver will recover, and I can rmmod sd_mod, and
stability returns. Otherwise, the system locks completely. Once, I
rmmod'd sd_mod, and checked /proc/scsi(/g_NCR5380?), and it said that a
command had been sent, and it was waiting for the reply. The drive works
fine under DOS. I don't have any other scsi devices to test with, so I
don't know if the problem is the ZIP drive or the scsi drivers.
Other system info:
gcc-2.6.3
AMDX4/100, 20 megs ram
Slackware 2.2(mostly)
Thanks,
--
Andy Steinbach