SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I am using the 2.6.18 kernel with Slackware 11. On boot, some modules load for hardware that I have but don't currently use (for example, a printer port or an extra network card). Is there a way to disable loading of certain modules or probing of hardware? I tried adding "nohotplug" at boot but that didn't work.
You may also want to check in /etc/rc.d/rc.modules to make sure they aren't being loaded from there. There are some modules that are enabled by default that you may not use. Just comment out any modules that you don't want loaded. A quick way to see what is already enabled is the following command:
You may also want to check in /etc/rc.d/rc.modules to make sure they aren't being loaded from there. There are some modules that are enabled by default that you may not use. Just comment out any modules that you don't want loaded. A quick way to see what is already enabled is the following command:
Code:
grep -v ^# /etc/rc.d/rc.modules |uniq
Hope this helps.
That worked with kernel 2.4, but not 2.6. I can add modules to this file if I want them to be loaded when they aren't automatically detected, but I can't comment them out to stop them from being loaded automatically.
Can anyone tell me how modules are loaded anyway? I realize you can do it with modprobe, but how are they loaded automatically and how are they chosen? If I don't blacklist them, I get a bunch of modules for acpi for chipsets I don't have. Like four of them will load when I only need one. Is this because the automatic loader isn't that smart and just loads all the acpi it can when it detects acpi?
It's more likely that the extra acpi modules were made when the kernel was compiled. If you really want to get rid of extra bits and pieces for chipsets that you don't have, or generic code, the best way is to compile your own kernel.
It's more likely that the extra acpi modules were made when the kernel was compiled. If you really want to get rid of extra bits and pieces for chipsets that you don't have, or generic code, the best way is to compile your own kernel.
Have a look in /lib/modules/<kernel version>/
Well, I don't want to take that step because even though I am not using the hardware now, I might use it in the future and I'd rather just delete a blacklist line in a file than recompile a kernel just to get a printer working or something.
It's more likely that the extra acpi modules were made when the kernel was compiled. If you really want to get rid of extra bits and pieces for chipsets that you don't have, or generic code, the best way is to compile your own kernel.
Have a look in /lib/modules/<kernel version>/
Thanks for the reply. sony_acpi gets loaded automatically unless I blacklist it, but there's plenty of other modules that don't get loaded that I still have on under /lib/modules. I'm using ubuntu with a stock kernel so I don't think it's compiled in. I'm probably going to compile my own kernel eventually, but I want to know how this works, why some modules are automatically loaded and some are not.
Ok, noticed something odd. There's a toshiba acpi driver in the /lib/modules directory just like the sony and asus and others, but that doesn't get loaded for my computer even though it's a toshiba! So why's sony and asus load, but not toshiba?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.