Hi everyone,

I just did an install of slackware 9.1 on my laptop. The system boots fine, but during boot up insmod is trying to load modules for devices I don't have on my computer. My question is this, What file do I need to edit in slackware to remove these invalid entries?

Thanks,
James

You have a number of options to do this. I think that specifying all modules you want to load manually is the fastest and easiest. You can do that by listing the modules you use at that moment (lsmod) and specify them in /etc/rc.d/rc.modules by adding lines like
/sbin/modprobe name-of-the-module
After you did that, remove the execute rights of /etc/rc.d/rc.hotplug . That should do it I think.

hotplug is probably trying to do this and there is no file that tells it "what" to load, but u can tell hotplug what NoT tO lOaD

edit /etc/hotplug/blacklist with your favorite editor (u will need to be root) and place the name of the module (without the .o or .c or whatever) on some new line anywhere in the file

make sure the line does NOT have a # before it (i did that and took me two days to figure out why the module i810_rng was still loading)


*edit: if u find that hotplug is a pain, then the above poster's way would work (just make sure u find out what modules hotplug is loading by doing lsmod and then put modprobe module module module in /etc/rc.d/rc.local; u can list the modules on one line)
also, to remove execution rights, i believe the command is chmod -x /etc/rc.d/rc.hotplug

i usually just edit rc.M and comment out the section for hotplug by placing # in front of all the commands

The right place for loading modules is not rc.local but rc.modules. You can do that in rc.local but there is a special script for it. Adding all the modules you don't want to be tested in the blacklist of hotplug could be a lot of work, I think adding the modules you do want is a much better way of doing that. And there's no need to edit rc.M because it starts scripts after testing if they are executable. If not, they will not be started. That's why I prefer to remove the execute rights of a startup script.

When using /sbin/modprobe <modulename> dependencies of that specific module will be resolved automaticly.

But there are many ways to solve certain problems. That's one of the things I like about Linux.

I think I am haveing a similar problem. Whenever I boot I get some errors about a module not being able to load or something... "dmesg" gives me this, "i810_rng: RNG not detected".

Do I just add "i810_rng" to the blacklist file?

yes Posty, this is exactly the thing hotplug was trying to load for my system

just add i810_rng to the blacklist file

I have looked in the files suggested, but I'm not able to find any reference to IRDA which is what I'm attempting to disable.