LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (https://www.linuxquestions.org/questions/slackware-14/)
-   -   Loading modules (https://www.linuxquestions.org/questions/slackware-14/loading-modules-128593/)

trouby 12-24-2003 03:59 AM

Loading modules
 
Hey,

I never knew... where is the right place to load kernel modules?
Of course there are modules like ethernet cards that should be loaded before ifconfig configures the interfaces,


For some reason I have compiled as modules the ethernet cards and they go up automatically, I guess it loads automatically by the kernel itsself when something (like ifconfig) tries to access the ethernets.

Anyway, where do I put modules in Slackware? :)

Thanks.

delta9 12-24-2003 04:04 AM

I think the logical place would be /etc/rc.d/rc.modules

trouby 12-24-2003 04:06 AM

so /etc/modules.conf is only for aliasing or what?

kc00l 12-24-2003 04:54 AM

Re: Loading modules
 
Quote:

Originally posted by trouby
Hey,

I never knew... where is the right place to load kernel modules?
Of course there are modules like ethernet cards that should be loaded before ifconfig configures the interfaces,


For some reason I have compiled as modules the ethernet cards and they go up automatically, I guess it loads automatically by the kernel itsself when something (like ifconfig) tries to access the ethernets.

Anyway, where do I put modules in Slackware? :)

Thanks.

AFAIK if you're using kmod (automatic kernel modules loading) you don't need to worry about loading modules, since the kernel does that automatically when it needs modules loaded. For example, you need USB mass storage? It gets loaded the first time the kernel is instructed to have access to it, I repeat, as far as I know.

Anyway, usually you don't need to edit /etc/rc.d/rc.modules if you need modules you have built when compiling your kernel. If you compile external modules, which aren't normally in the kernel source, for example omnibook kernel module, you need to add the corresponding modprobe line to your rc.modules.

/etc/modules.conf is for aliasing, as you said, and I'll add another useful file, i.e. /etc/hotplug/blacklist to which you can add modules you don't want to be automatically loaded at startup. Have a look at blacklist, since it's clearly commented, and you'll understand what a newbie (even if my infos say I'm a member now) as myself is trying to say.

Merry Xmas.


All times are GMT -5. The time now is 08:24 PM.