SlackwareThis Forum is for the discussion of Slackware Linux.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I have a system running slack 9-current.. it is a dell optiplex with an onboard intel pro/1000 MT nic. I just recently installed a dual port pro/1000 MT nic as well. Currently eth0 comes up as the first port of the dual nic, and eth1 is the 2nd port, and eth2 is the onboard nic. They all use the e1000 module and are all functioning correctly.
question: how can i make the onboard nic to be eth0?
I've tried adding the following to /etc/modules.conf :
alias eth0 e1000
alias eth1 e1000
alias eth2 e1000
options e1000 io=0xecc0,0xec80,0xec40
and also :
options e1000 irq=10,9,11
but on bootup i get an err saying e1000 does not support those parameters... not sure what else to try..
I got also that problem with my 2 nics (dlink 538-TX). And I come to the conclusion that the device (ethx) assignment is not related to IRQ,MAC nor to pci slot order, but maybe to the I/O address used by the NICs (I can be wrong).
The older ISA card need to be configured with irq,i/o but pci is plugNplay, that mean those irq,i/o will be assigned by the OS. I heard there are tool for that mii somethang (nope sure, maybe only for 538-tx card).
I quest on lilo there is a possibility to specify the irq,i/o for ethx, am nope sure whether this work, also don't have the time to probe n learnt to accept my eth1 to be the gateway to internet ..
We have 2 onboard tx, 1 Dual port fiber, 1 quad port Copper TX.
They all GB cards using the Innel e1000 driver.
Whats odd is...
Onboard is Eth0,1
Dual Fiber is Eth 2,4
Quad port is Eth 5,3,7,6. (top to bottom on card)
On the QUAD port it isn't even contiguous or in order. ARG.
I read an arcticle about using udev scripting to rename, based on MAc, which sounded liek a good idea. But I'd like to know what enables the wierd assignments. On teh exampe above, why in the world is ETH3 in the middle of a card?
If you swap the eth0 and eth1 in that file (which will be re-generated on boot if you delete it by the way), then your devices will be (re-)named exactly as defined there.
For non-UDEV systems you will have to pass the interface name on the kernel command line (e.g. in lilo.conf's "append" line) together with IO and IRQ addresses if possible, or else using modprobe options in /etc/modules.conf (2.4 kernels) or /etc/modprobe.conf (older Slackwares that do not have a /etc/modprobe.d/ directory).