On Mon, 16 Mar 1998, John N. Derr wrote:
> I recently installed a Zip Zoom adapter for my SCSI external Zip drive
> I have rebuilt the kernel making sure SCSI support is installed.
> I am runing RH5.0 kernel 2.0.32. Currently I'm using a monolithic
> kernel.
> The problem is I can't get my SCSI Zip drive to be reognized. Enclosed
> is
> a portion of my dmesg output. Also the zip drive works fine under
> Windoze
>
>
> linear personality registered
> aha152x: processing commandline: ok
> aha152x: BIOS test: passed, detected 1 controller(s)
> aha152x0: vital data: PORTBASE=0x140, IRQ=9, SCSI ID=7,
> reconnect=enabled, parity=enabled, synchronous=disabled, delay=100,
> extended translation=disabled
> aha152x: trying software interrupt, lost.
> aha152x: IRQ 9 possibly wrong. Please verify.
> scsi0 : Adaptec 152x SCSI driver; $Revision: 1.18 $
> scsi : 1 host.
> scsi : aborting command due to timeout : pid 0, scsi0, channel 0, id 0,
> lun 0 Test Unit Ready 00 00 00 00 00
> scsi : aborting command due to timeout : pid 0, scsi0, channel 0, id 0,
> lun 0 Test Unit Ready 00 00 00 00 00
> scsi : aborting command due to timeout : pid 1, scsi0, channel 0, id 1,
> lun 0 Test Unit Ready 00 00 00 00 00
> scsi : aborting command due to timeout : pid 1, scsi0, channel 0, id 1,
> lun 0 Test Unit Ready 00 00 00 00 00
> scsi : aborting command due to timeout : pid 2, scsi0, channel 0, id 2,
> lun 0 Test Unit Ready 00 00 00 00 00
> scsi : aborting command due to timeout : pid 2, scsi0, channel 0, id 2,
> lun 0 Test Unit Ready 00 00 00 00 00
> scsi : aborting command due to timeout : pid 3, scsi0, channel 0, id 3,
> lun 0 Test Unit Ready 00 00 00 00 00
> scsi : aborting command due to timeout : pid 3, scsi0, channel 0, id 3,
> lun 0 Test Unit Ready 00 00 00 00 00
> scsi : aborting command due to timeout : pid 4, scsi0, channel 0, id 4,
> lun 0 Test Unit Ready 00 00 00 00 00
> scsi : aborting command due to timeout : pid 4, scsi0, channel 0, id 4,
> lun 0 Test Unit Ready 00 00 00 00 00
> scsi : aborting command due to timeout : pid 5, scsi0, channel 0, id 5,
> lun 0 Test Unit Ready 00 00 00 00 00
> scsi : aborting command due to timeout : pid 5, scsi0, channel 0, id 5,
> lun 0 Test Unit Ready 00 00 00 00 00
> scsi : aborting command due to timeout : pid 6, scsi0, channel 0, id 6,
> lun 0 Test Unit Ready 00 00 00 00 00
> scsi : aborting command due to timeout : pid 6, scsi0, channel 0, id 6,
> lun 0 Test Unit Ready 00 00 00 00 00
> scsi : detected total.
> tunnel: version v0.2b2
> Equalizer1996: $Revision: 1.9 $ $Date: 1996/10/12 11:14:37 $ Simon Janes
> ([EMAIL PROTECTED])
>
> I appreciate any help on figuring this out, as I am almost ready to give
> up hope.
> Thanks in advance,
John:
Recently while evaluating the AHA1502 which came with my ZIP Insider
(AHA152x "class" Card without a BIOS), I was getting the above messages
when I had accidently choosen a conflicting IRQ (happened to choose IRQ
10, which was already in use by my STB 4Com Serial Card). Curiously it
had worked under WIN95 where the STB 4Com is NOT supported (or Windoze
could work around the "conflict"), but for Linux (which is more rigorous
about requiring separate IRQs) this was a "problem". Any chance you have
a conflict on IRQ 9 (or IRQ 2)? There may also other issues using the
Cascading IRQ, so you may want to try another IRQ jumper setting!
Lawrence Houston - ([EMAIL PROTECTED])
--
PLEASE read the Red Hat FAQ, Tips, Errata and the MAILING LIST ARCHIVES!
http://www.redhat.com/RedHat-FAQ /RedHat-Errata /RedHat-Tips /mailing-lists
To unsubscribe: mail [EMAIL PROTECTED] with
"unsubscribe" as the Subject.
