On Thu, 7 Feb 2002, Praedor Tempus wrote: > On Thursday 07 February 2002 06:06 pm, mike wrote: > > Praedor Tempus wrote: > > > Go ahead and put it in your /etc/rc.local file (if it wont "take)...why > > > NOT add it to rc.local? It will remain with every reboot. I used to > > > have to do that several linux iterations ago for alsa, as I recall. > > > > Ok Praedor, add this : alias scsi_hostadapter1 aic7xxx ? > > I wasn't refering to the alias bit. I thought the problem was that INSPIT of > this being in modules.conf he couldn't get the module to load with each > bootup. That being the case, screw modules.conf and aliases and simply to do > the automatic insmod bit from rc.local. > > It has been done by me and many many others in the past. > The main reasons not to put an 'insmod module_name' into rc.local are:
1) modules can be unloaded by the kernel. If they are in rc.local they will not get reloaded. 2) insmod doesn't satisfy module dependencies. modprobe should be used instead, and then only to manually load/unload modules. 3) kernel changes can cause problems with finding the module. The only thing that should be in the rc scripts is depmod, which figures out the module dependencies. If the module is not loaded on boot, it should load when the requests it. This may be the problem -- the module itself may not be showing up in an lsmod.
Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
