On Thu, 2002-05-30 at 15:58, Ricardo J. Méndez Castro wrote: > > > Also look in your boot logs to see what the SCSI driver is doing. > > [...] > > Looking at dmesg, the only SCSI device I found mentioned was the integrated > Promise FastTrack lite controller. Here's the sub-section: > > Journalled Block Device driver loaded > SCSI subsystem driver Revision: 1.00 > Promise FastTrak Series Linux Driver Version 1.2.0.14 > scsi0 : FASTTRAK > Vendor: Promise Model: 2+0 Stripe/RAID0 Rev: 1.10 > Type: Direct-Access ANSI SCSI revision: 02 > Attached scsi disk sda at scsi0, channel 0, id 0, lun 0 > SCSI device sda: 160836354 512-byte hdwr sectors (82348 MB) > sda: sda1 sda2 < sda5 sda6 sda7 sda8 sda9 sda10 sda11 sda12 sda13 sda14 > > kjournald starting. Commit interval 5 seconds > > > I decided to check again for the modules, just in case, and they seem to be > loaded. From lsmod: > > scsi_mod 95760 2 [ft sd_mod] > > > And from modinfo sg: > > filename: /lib/modules/2.4.7-10/kernel/drivers/scsi/sg.o > description: "SCSI generic (sg) driver" > author: "Douglas Gilbert" > license: <none> > parm: def_reserved_size int, description "size of buffer reserved for > each fd"
The above information suggests that (a) your Adaptec SCSI adapter is not being detected, and (b) the sg module is not loaded. Your system should look like it has two SCSI adapters, one for the Promise controller and the other for the Adaptec. Depending on what order they are detected, one should show up as scsi0, which is currently the case for your Promise controller, and the other should be scsi1. I suppose it's possible that nothing has referenced anything that would cause the Adaptec SCSI driver to be loaded, assuming it is compiled as a module. Have you tried doing a modprobe on the Adaptec SCSI driver (I don't remember its name right now)? Try doing that and watch the end of your /var/log/messages file. Linus _______________________________________________ Redhat-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-list