Turns out there is a file in /etc/udev/rules.d called
70-persistent-net.rules. In it there was a line for the old ethernet
card to be assigned to eth0 and also one for the new ethernet card to be
assigned to eth2. The comments said it was OK to edit, So, I just
switched the eth0 and eth2. Now the new motherboard controller shows up
as eth0. Probably could have removed the old one altogether, but didn't
want to do anything that drastic.
All is now well.
Thanks
Chris Kottaridis (chriskot@xxxxxxxxxxxxx)
=====================================================
On Wed, 2008-03-26 at 11:55 -0600, Chris Kottaridis wrote:
> I had a Dell machine and the motherboard went belly up. So, I took my
> machine to a local Computer shop and the basically gave me a new chassis
> and motherboard, but kept my disk drives. Things are mostly working, but
> it, or rather me, seem to be a little bit confused about the on board
> ethernet.
>
> I have the on-board ethernet and an add-on card. During boot I see this
> message:
>
> tg3 device eth0 does not seem to be present, delaying initialization.
>
> Looking at dmesg I get the following:
>
> 8139too Fast Ethernet driver 0.9.28
> ACPI: PCI Interrupt 0000:00:1f.3[C] -> GSI 18 (level, low) -> IRQ 18
> ACPI: PCI Interrupt 0000:05:00.0[A] -> GSI 20 (level, low) -> IRQ 21
> eth0: RealTek RTL8139 at 0xf8834000, 00:1d:0f:c0:01:bc, IRQ 21
> eth0: Identified 8139 chip type 'RTL-8100B/8139D'
> r8169 Gigabit Ethernet driver 2.2LK-NAPI loaded
> ACPI: PCI Interrupt 0000:04:00.0[A] -> GSI 16 (level, low) -> IRQ 16
> PCI: Setting latency timer of device 0000:04:00.0 to 64
> eth1: RTL8168b/8111b at 0xf8966000, 00:1a:4d:5e:f2:75, XID 38000000 IRQ
> 219
> 8139cp: 10/100 PCI Ethernet driver v1.3 (Mar 22, 2004)
> udev: renamed network interface eth1 to eth2
> udev: renamed network interface eth0 to eth1
> ACPI: PCI Interrupt 0000:00:1b.0[A] -> GSI 22 (level, low) -> IRQ 22
>
> The RealTek RTL8139 is my add-on card and the r8168b/8222b id the new
> on-board ethernet.
>
> Doing an ifconfig -a shows:
>
> # ifconfig -a
> eth1 Link encap:Ethernet HWaddr 00:1D:0F:C0:01:BC
> inet addr:192.65.171.33 Bcast:192.65.171.63
> Mask:255.255.255.224
> inet6 addr: fe80::21d:fff:fec0:1bc/64 Scope:Link
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:22146 errors:0 dropped:0 overruns:0 frame:0
> TX packets:22187 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:1000
> RX bytes:20938687 (19.9 MiB) TX bytes:3083685 (2.9 MiB)
> Interrupt:21 Base address:0x4000
>
> eth2 Link encap:Ethernet HWaddr 00:1A:4D:5E:F2:75
> BROADCAST MULTICAST MTU:1500 Metric:1
> RX packets:0 errors:0 dropped:0 overruns:0 frame:0
> TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:1000
> RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
> Interrupt:219 Base address:0x6000
>
> lo Link encap:Local Loopback
> inet addr:127.0.0.1 Mask:255.0.0.0
> inet6 addr: ::1/128 Scope:Host
> UP LOOPBACK RUNNING MTU:16436 Metric:1
> RX packets:8096 errors:0 dropped:0 overruns:0 frame:0
> TX packets:8096 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:4239466 (4.0 MiB) TX bytes:4239466 (4.0 MiB)
>
>
> I am a little confused about udev remapping eth0 to eth1 and eth1 to
> eth2. Why isn't there an eth0 ?
>
> On my old motherboard I had the on-board ethernet come up as eth0 and
> the add-on board come up as eth1.
>
> I can actually bring up the eth2 interface which seems to be the
> on-board ethernet, at least I can ping addresses on that network:
> ========================================
> [root@worker log]# ifconfig eth2 172.25.33.35
> [root@worker log]# ifconfig -a
> eth1 Link encap:Ethernet HWaddr 00:1D:0F:C0:01:BC
> inet addr:192.65.171.33 Bcast:192.65.171.63
> Mask:255.255.255.224
> inet6 addr: fe80::21d:fff:fec0:1bc/64 Scope:Link
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:22189 errors:0 dropped:0 overruns:0 frame:0
> TX packets:22226 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:1000
> RX bytes:20955519 (19.9 MiB) TX bytes:3086385 (2.9 MiB)
> Interrupt:21 Base address:0x4000
>
> eth2 Link encap:Ethernet HWaddr 00:1A:4D:5E:F2:75
> inet addr:172.25.33.35 Bcast:172.25.255.255 Mask:255.255.0.0
> inet6 addr: fe80::21a:4dff:fe5e:f275/64 Scope:Link
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:3 errors:0 dropped:0 overruns:0 frame:0
> TX packets:19 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:1000
> RX bytes:200 (200.0 b) TX bytes:3687 (3.6 KiB)
> Interrupt:219 Base address:0x6000
>
> lo Link encap:Local Loopback
> inet addr:127.0.0.1 Mask:255.0.0.0
> inet6 addr: ::1/128 Scope:Host
> UP LOOPBACK RUNNING MTU:16436 Metric:1
> RX packets:8104 errors:0 dropped:0 overruns:0 frame:0
> TX packets:8104 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:4240288 (4.0 MiB) TX bytes:4240288 (4.0 MiB)
>
> [root@worker log]# ping 172.25.33.33
> PING 172.25.33.33 (172.25.33.33) 56(84) bytes of data.
> 64 bytes from 172.25.33.33: icmp_seq=1 ttl=255 time=3.29 ms
> 64 bytes from 172.25.33.33: icmp_seq=2 ttl=255 time=1.12 ms
>
> --- 172.25.33.33 ping statistics ---
> 2 packets transmitted, 2 received, 0% packet loss, time 999ms
> rtt min/avg/max/mdev = 1.125/2.211/3.298/1.087 ms
> =============================================
>
>
> So, how do I get Linux to recognize the new motherboard's ethernet card
> as eth0 instead of eth2 ?
>
>
> Thanks
> Chris Kottaridis (chriskot@xxxxxxxxxxxxx)
>
