From: "Daniel da Veiga" <danieldaveiga@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] modules.conf - alias for eth devices - can't set the correct interface number
Date: Thu, 26 Oct 2006 13:31:07 -0300 [thread overview]
Message-ID: <342e1090610260931g4ef48044kc04136ba7e4b1e34@mail.gmail.com> (raw)
In-Reply-To: <fd8aab850610260801p9ee7f62gf6ddea5edebbac8b@mail.gmail.com>
On 10/26/06, Claudinei Matos <claudineimatos@gmail.com> wrote:
> Hi guys,
>
> I'm changing my third network card (a 3c905cx) with a 3c905B one. Well, the
> drivers are the same and the slot used is also the same.
> My machine has other two NICs, one onboard (via-rhine) and a old realtek
> 8029 10/10 (ne2k-pci).
> On my /etc/modules.d/aliases I have the 3 lines below:
>
> alias eth0 via-rhine
> alias eth1 ne2k-pci
> alias eth2 3c59x
>
> and it works very well setting each device to the right eth interface until
> I'd start to change the NICs, sometimes it does not work but shuting down
> and powering up the machine again used to solve.
> now, since I'd changed the NICs, every time I boot up my machine the third
> device (3com) is associated with eth3 and eth2 does not have any device
> associated.
> my dmesg says that the interface eth2 was associated with the ne2k-pci but
> ifconfig tells that eth1 is ne2k-pci and eth3 (which doesn't appear at dmesg
> log) is the 3com one.
>
> ti01 myers # ifconfig eth3 up
> ti01 myers # ifconfig|grep eth
> eth0 Link encap:Ethernet HWaddr 00:50:8D:84:A8:4F
> eth1 Link encap:Ethernet HWaddr 00:C0:DF:EA:D6:49
> eth3 Link encap:Ethernet HWaddr 00:50:04:6E:9C:AB
>
> ti01 myers # dmesg|grep eth
> eth0: VIA Rhine II at 0xec061000, 00:50:8d:84:a8:4f, IRQ 193.
> eth0: MII PHY found at address 1, status 0x786d advertising 05e1 Link 45e1.
> eth2: RealTek RTL-8029 found at 0xa400, IRQ 209, 00:C0:DF:EA:D6:49.
> eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
>
> ti01 myers # dmesg|grep 3Com
> 0000:00:0a.0: 3Com PCI 3c905B Cyclone 100baseTx at ffffc20000228000.
>
> Well, I do not have any idea about how to fix it or what may be wrong since
> it is supposed to just setup /etc/modules.d/aliases and run modules-update
> to generate /etc/modules.conf.
> One extra information is that booting in single mode (init=/bin/bash) the
> interface order is ok. Could it be a udev problem?
>
> Thanks for the help,
>
I'm pretty sure you can use UDEV rules to set it, something like this:
# cat /etc/udev/rules.d/10-local.rules
BUS=="pci", KERNEL=="eth[0-9]", SYSFS{address}=="00:2a:9a:d4:65:32", \
NAME="lan0"
BUS=="pci", KERNEL=="eth[0-9]", SYSFS{address}=="00:a0:5d:3e:ae:54", \
NAME="lan1"
Where SYSFS{address} is the MAC address of the card.
--
Daniel da Veiga
Computer Operator - RS - Brazil
-----BEGIN GEEK CODE BLOCK-----
Version: 3.1
GCM/IT/P/O d-? s:- a? C++$ UBLA++ P+ L++ E--- W+++$ N o+ K- w O M- V-
PS PE Y PGP- t+ 5 X+++ R+* tv b+ DI+++ D+ G+ e h+ r+ y++
------END GEEK CODE BLOCK------
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2006-10-26 16:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-26 15:01 [gentoo-user] modules.conf - alias for eth devices - can't set the correct interface number Claudinei Matos
2006-10-26 16:31 ` Daniel da Veiga [this message]
2006-10-26 19:58 ` Claudinei Matos
2006-10-26 20:18 ` Daniel da Veiga
2006-10-26 20:49 ` Richard Fish
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=342e1090610260931g4ef48044kc04136ba7e4b1e34@mail.gmail.com \
--to=danieldaveiga@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox