Ok, here is my situation as best I can describe it.
Prior to the installation of RH6.0, our scsi tape device worked and
functioned normally with our backup software and RH5.2.
When I installed RH6.0, it was unable to locate the scsi device during
installation. So I set about the task of recompiling the kernel with the
correct driver (in this case, adaptech 7xxx family). To my untrained eye,
this appeared to go very well (I followed the step by step instructions
provided in the RH6.0 installation manual). After some frustration, all the
makes performed well, with no errors reported. I proceeded to reboot the
system with our newly compiled kernel. However, the system cannot see
device /dev/st0. An "mt -f /dev/st0 status" returns the message "no such
device".
Using a dmesg | less to look at the boot up output, I came across this
error msg in regards to the scsi device in question. I'll list it here:
(scsi0) <Adaptec AHA-294x SCSI host adapter> found at PCI 9/0
(scsi0) Narrow Channel, SCSI ID=7, 16/255 SCBs
(scsi0) Warning - detected auto-termination
(scsi0) Please verify driver detected settings are correct.
(scsi0) If not, then please properly set the device termination
(scsi0) in the Adaptec SCSI BIOS by hitting CTRL-A when prompted
(scsi0) during the machine bootup.
(scsi0) Cables present (Int-50 YES, Ext-50 NO)
(scsi0) Downloading sequencer code... 406 instructions downloaded
(scsi0) Couldn't register IRQ 9, ignoring controller
scsi : 0 hosts.
scsi : detected total
I'm guessing I did something incorrect during the recompilation process,
since this device worked well before RH6.0. I send this out in the hope
that some guru out there can spot something else that perhaps is non-kernel
related that I'm just missing. I don't know how one would verify that the
driver detected settings are correct, and if it is something that can be
fixed in the adaptec scsi bios, life would be grand!
The only other information I can provide is the fact that I installed
the correct adaptec driver during a "make menuconfig" not as a module, but
as an item to be included with the recompiled kernel. The only other thing
I added to recompile was a cyclades driver for a board we have on this
system. The dmesg | less info on that cyclades driver did NOT produce an
error message.
Anyhow, this is a pretty specific problem, most likely due to something
I did during the recompiling of the kernel. If anyone out there has ideas
other than this, I'd love to hear them :)
Thanks very very much in advance ,
April Escamilla
---------------------------------------------------------------------------
Send administrative requests to [EMAIL PROTECTED]
