Attached devices:
Host: scsi0 Channel: 00 Id: 00 Lun: 00
Vendor: WDIGTL Model: WDE4360-1807A3 Rev: 1.80
Type: Direct-Access ANSI SCSI revision: 02
Host: scsi0 Channel: 00 Id: 01 Lun: 00
Vendor: CONNER Model: CFP1080S Rev: 4040
Type: Direct-Access ANSI SCSI revision: 02
Host: scsi0 Channel: 00 Id: 05 Lun: 00
Vendor: NEC Model: CD-ROM DRIVE:464 Rev: 1.05
Type: CD-ROM ANSI SCSI revision: 02
Now, all this was working fine with the 2.0.33 kernel. However, when I
install my new 2.0.34 kernel, bad things happen.... Everything runs fine
until I hit the NEC CD-ROM. Basically, it initiates wide negotiation,
fails, and then gets really upset. I can't tell what the error message
is exactly because it's scrolling by at a mighty fine pace, but
basically, it says something to the effect of it using an illegal SCB
255.... If this is not a known problem I'll try to get a more detailed
error message.
After this happens, even a hard reset will not resusitate my CD-ROM
drive (my guess is that it decided to shut down). I can't access it in
Linux, Win95, or NT (multiboot, it's a wonderful thing for testing). It
doesn't even show up during SCSI Bios initialization. The only way to
get my CD-ROM drive back is to power off the system and then reboot.
I'm not sure if this problem is related to updates to the AIC7XXX SCSI
driver or updates the kernel's SCSI code. Any assistence would be
appreciated. If this turns out not to be a known problem, I'll also try
patching a 2.0.33 kernel with the latest AIC7XXX driver and see if that
works.
--Chris
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu