Click to See Complete Forum and Search --> : peculiar problem with modules.conf


Qed
01-08-2001, 02:44 AM
I'm trying to set up a second NIC on my slackware 7.1 system and I have the following lines in my modules.conf:

alias eth0 ne
alias eth1 ne
options ne io=0x340,0x380

I boot my system and lsmod and find that ne is not loaded.

Then as root I type at the prompt:

# modprobe alias eth0 ne
# modprobe alias eth1 ne
# modprobe options ne io=0x340,0x380

After this I lsmod and ne is loaded just fine, and ifconfig shows both eth0 and eth0 set with the correct io, irq, and ethernet addresses.

Of course I'd prefer if these loaded on boot with modules.conf, does anyone know why it is not working (at least the way I'm expecting it to work)? Or am I completely off base on how modules.conf works?

Strike
01-08-2001, 03:19 AM
I believe /etc/modules.conf just specifies rules for loading modules, and which devices require what modules. It isn't a script that loads modules on startup.

The last command actually loaded the module. To automatically load those (although they should load when you try and access the device), just put it (modprobe options ne io=0x340,0x380) in one of your startup scripts like rc.local.

Qed
01-08-2001, 03:35 AM
Thanks for the advice. It works just fine now. =)