Building a PC Isn't Hard
David A. Bandel
david.bandel at gmail.com
Mon Feb 4 05:46:42 PST 2008
On Feb 4, 2008 7:38 AM, vu pham <vu at sivell.com> wrote:
> kwall at kurtwerks.com wrote:
> [...]
> > I've got a similar GigE NIC:
> >
> > Driver: r8169 Gigabit Ethernet driver 2.2LK loaded
> > NIC: RTL8168b/8111b
> >
> > Perversely, it loads at eth0, but gets configured at eth2. No, there
> > are no other NICs in the machine. Not sure if it's a driver problem
> > or a configuration problem in the OS.
>
> Here is what I have in my notebook's dmesg:
>
> eth0: Tigon3 [partno(BCM95755m) rev a002 PHY(5755)] (PCI Express)
> 10/100/1000Base-T Ethernet 00:1c:23:95:99:6c
> eth0: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[0] WireSpeed[1] TSOcap[1]
> eth0: dma_rwctrl[76180000] dma_mask[64-bit]
> net eth2: device_rename: sysfs_create_symlink failed (-17)
> udev: renamed network interface eth0 to eth2
>
>
> and it ends up using eth2 after boot. Don't know why the kernel changed
> it from eth0 to eth2. The system does have a Dell 1505 Draft 802.11n but
> it is never detected.
>
This is a function of udev. Look in /etc/udev/rules.d/ and you'll
find a file that redefines your ethernet device based on its mac
address/bios address. You can change it so that it is eth0 again (if
you want).
Ciao,
David A. Bandel
--
Focus on the dream, not the competition.
- Nemesis Air Racing Team motto
More information about the Linux-users
mailing list