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.
Is there any way to load the same module for two network cards in the same PC running Slackware 64 14.1? Or load it twice, so that I can actually use both network cards?
I have two Intel gigabit network cards - one onboard for Intel motherboard DG33BU, and another Intel Gigabit CT Desktop Adapter, PCIe x1. They both need the same module: e1000e
I'm using the stock kernel vmlinux-huge-3.10.17.
For whatever reason the onboard nic can be loaded and assigned an IP, but the second nic cannot.
I can see this in the /etc/udev/rules.d/70-persisten-net.rules. (I've even deleted this file, for a fresh file to be written on reboot)
Dmesg reflects the same information, both nics are present.
Finally, "ifconfig" output only shows eth0, but "ifconfig -a" shows eth0 and eth1.
If I enter the command "ifconfig eth1 up", ifconfig then shows both eth0 and eth1, but it disappears after I restart the network interface(s) "/etc/rc.d/rc.inet1 restart" I have both interfaces set to DHCP, and there is a DHCP server running on both networks.
There must be a simple fix for this that I cannot figure out.
I google searched many times as well as searched the forums, but was unable to find an answer.
modules will only be loaded once, it will works as many same nic cards allowed at same time in your hardware setup.
in your 70-persistent-net.rules file, modify mac address:
ATT{adress}=="xx:xx:xx:xx:xx", NAME="eth0"
ATT{adress}=="xx:xx:xx:xx:xx", NAME="eth1"
then modify /etc/rc.d/rc.inet1.conf file according to your network setup. I don't understand your DHCP setup, but custom routing setup can be add in your rc.local file.
modules will only be loaded once,
in your 70-persistent-net.rules file, modify mac address:
ATT{adress}=="xx:xx:xx:xx:xx", NAME="eth0"
ATT{adress}=="xx:xx:xx:xx:xx", NAME="eth1"
then modify /etc/rc.d/rc.inet1.conf file according to your network setup.
The Mac addresses are already unique (and reflect each network cards MAC address). Below is my 70-persistent-net.rules file, but I replaced some of the address with xx:xx.... Can I somehow force the module to be loaded according to pci address?
No, you don't need to reload modules.
make sure your rc.inet1.conf file is properly edited.
using 2 dhcp improperly will mess up your default gateway.
One interface isn't quite true dchp - my employer uses dhcp to bind each MAC, a static address. (for security reasons - so you can't as easily plug in non-registered network interface into the network.) Yes, you can spoof MAC's etc - but that's not the point.
thanks again! Much appreciated. I'm glad I figured it out - rookie mistake though.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.