[SLE] SCSI module not loading on boot after applying update
This have been happening to me for a long time... First after updating SuSE 6.0, now after installing a few updates to (freshly installed) 6.3. I have built-in AIC-7895 SCSI adapter on the mobo (Gigabyte GA-6BXDS). The only device currently connected is Yamaha CRW-4416S CD-RW drive. After installing SuSE Linux for the first time from scratch everything is recognized and aic7xxx module loads automatically on each boot. After installing system updates via YaST everything works fine, but... SCSI module no longer loads on boot. SCSI adapter is still correctly recognized (according to KernelLog), and I can successfully load it manually with modprobe. No errors and everything works. Just that it does not load on boot time. I searched through modules.conf and other config files I can think of, but no go. How to force SCSI module loading back on boot time? Ivan Adzhubei -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
* Ivan Adzhubei (ivan@protein.bio.msu.su) [20000205 19:32]:
How to force SCSI module loading back on boot time?
There are several ways to achieve that goal. If you boot Linux from an IDE
disk, just add
alias scsi_hostadapter aic7xxx
to your /etc/modules.conf. If you boot off a SCSI disk (which doesn't seem
to be the case), you would have to take this route:
- boot SuSE Linux from CD or floppy
- open /etc/rc.config in the editor of your choice, search for the line
'INITRD_MODULES =', add "aic7xxx" after the equal sign and save the
file
- add 'initrd = /boot/initrd' to the global section of /etc/lilo.conf
- call mkinitrd
- call lilo
Either way should get the driver loaded the next time you boot Linux.
Philipp
--
Philipp Thomas
On Sat, 5 Feb 2000 22:59:55 +0100, Philipp Thomas wrote:
How to force SCSI module loading back on boot time?
There are several ways to achieve that goal. If you boot Linux from an IDE disk, just add
alias scsi_hostadapter aic7xxx
This does not work (btw, why?). Actually, it worked *before* the update even though the alias to scsi adapter was set to "off" and I never changed it.
to your /etc/modules.conf. If you boot off a SCSI disk (which doesn't seem to be the case), you would have to take this route:
- boot SuSE Linux from CD or floppy - open /etc/rc.config in the editor of your choice, search for the line 'INITRD_MODULES =', add "aic7xxx" after the equal sign and save the file - add 'initrd = /boot/initrd' to the global section of /etc/lilo.conf - call mkinitrd - call lilo
Aha, that looks more promising. I'll try it tomorrow. The reason I want scsi module to load on boot without having a SCSI HDD is minor but annoying bug (feature :) in Gigabyte BIOS: it switches HDD LED on on boot via built-in SCSI BIOS on boot and keeps it ON forever if SCSI adapter is not initialized by a driver. So I can't monitor ANY disk access because HDD LED is always on. Of course the most simple solution would be to buy a SCSI disk :-). Thanks, Ivan -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
* Ivan Adzhubei (ivan@protein.bio.msu.su) [20000206 00:42]:
- call mkinitrd
Aha, that looks more promising. I'll try it tomorrow.
A correction: that's mk_initrd, not mkinitrd.
--
Philipp Thomas
Add the following lines to your /etc/rc.d/boot.local: # SCSI driver echo -n "Starting aic7xxx SCSI driver..." modprobe aic7xxx This is how I did it... Nadeem Philipp Thomas wrote:
* Ivan Adzhubei (ivan@protein.bio.msu.su) [20000205 19:32]:
How to force SCSI module loading back on boot time?
There are several ways to achieve that goal. If you boot Linux from an IDE disk, just add
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
Philipp Thomas wrote:
How to force SCSI module loading back on boot time?
There are several ways to achieve that goal. If you boot Linux from an IDE disk, just add
alias scsi_hostadapter aic7xxx
to your /etc/modules.conf.
Tried once more and it definitely does not work with my configuration. BUT IT WORKED before I have applied the updates!
If you boot off a SCSI disk (which doesn't seem to be the case), you would have to take this route:
No, I am booting off the IDE disk. Does it mean I can do what listed below while booted from regular boot partition or I still have to boot from floppy?
- boot SuSE Linux from CD or floppy - open /etc/rc.config in the editor of your choice, search for the line 'INITRD_MODULES =', add "aic7xxx" after the equal sign and save the file
What the format of this line? I already have a module for my NIC listed there ('tulip' DEC chipset), should I add aic7xxx to the line? Separate both modules with spaces?
- add 'initrd = /boot/initrd' to the global section of /etc/lilo.conf - call mkinitrd - call lilo
Either way should get the driver loaded the next time you boot Linux.
Hmm, then tell me why tulip module loads on each boot without all the above? What's the major difference between tulip and aic7xxx? Can I expect YaST to take care of everything if I just add aic7xxx to INITRD_MODULES after tulip? BTW, INITRD_MODULES is not mentioned nowhere in documentation: it is missing from the rc.config section of SuSE printed manual, and there is no manpage on rc.config either. This is a shame since rc.config is a crusial file for SuSE system configuration and I beleive it should be fully documented in the first place. Ivan Adzhubei -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
* Ivan Adzhubei (ivan@protein.bio.msu.su) [20000206 16:36]:
What the format of this line? I already have a module for my NIC listed there ('tulip' DEC chipset), should I add aic7xxx to the line? Separate both modules with spaces?
Do it like this: INITRD_MODULES="aic7xxx tulip"
Hmm, then tell me why tulip module loads on each boot without all the above? What's the major difference between tulip and aic7xxx? Can I expect YaST to take care of everything if I just add aic7xxx to INITRD_MODULES after tulip?
No, it won't. You fist have to call mk_initrd after changing rc.config.
mk_initrd will rebuild the initial ramdisk to include the SCSI driver. After
that, call lilo, as lilo has to record the position of the initrd file on
the disk in order to access it when booting.
Philipp
--
Philipp Thomas
participants (3)
-
ivan＠protein.bio.msu.su -
nhasan＠usa.net -
pthomas＠suse.de