Hi all,
I've recently upgraded a system from CentOS 4.4 to CentOS5, and now when the system boots, the r8169 ethernet card doesn't come up.
After the boot sequence, if I type "ifup eth1 | ifup eth1.10 | ifup eth1.203" then the adapter starts up ok. It seems to be something with the boot sequence it loads the ethernet adapters a different way around (ie 4.4 eth0 is now eth1 and eth1 is now eth0).
Is there a way to revert this? Module loading priority or similar?
-- Steven Haigh
Email: netwiz@crc.id.au Web: http://www.crc.id.au Phone: (03) 9017 0597 - 0404 087 474
On 29/04/2007, at 11:23 PM, Steven Haigh wrote:
I've recently upgraded a system from CentOS 4.4 to CentOS5, and now when the system boots, the r8169 ethernet card doesn't come up.
After the boot sequence, if I type "ifup eth1 | ifup eth1.10 | ifup eth1.203" then the adapter starts up ok. It seems to be something with the boot sequence it loads the ethernet adapters a different way around (ie 4.4 eth0 is now eth1 and eth1 is now eth0).
Is there a way to revert this? Module loading priority or similar?
Sorry, replying with a bit more info....
in /etc/modprobe.conf I have: # cat /etc/modprobe.conf alias eth0 via-rhine alias eth1 r8169
also, in /etc/sysconfig/hwconf I have: class: NETWORK bus: PCI detached: 0 device: eth1 driver: r8169 desc: "Realtek Semiconductor Co., Ltd. RTL-8169 Gigabit Ethernet" network.hwaddr: 00:18:4d:79:65:47 vendorId: 10ec deviceId: 8169 subVendorId: 1385 subDeviceId: 311a pciType: 1 pcidom: 0 pcibus: 0 pcidev: 14 pcifn: 0 - class: NETWORK bus: PCI detached: 0 device: eth0 driver: via-rhine desc: "VIA Technologies, Inc. VT6102 [Rhine-II]" network.hwaddr: 00:40:63:ea:b7:21 vendorId: 1106 deviceId: 3065 subVendorId: 1106 subDeviceId: 0102 pciType: 1 pcidom: 0 pcibus: 0 pcidev: 12 pcifn: 0
This would seem to indicate that the r8169 is certainly set as eth1, however in the dmesg output, I see:
eth0: Identified chip type is 'RTL8169s/8110s'. eth0: RTL8169 at 0xdf81c000, 00:18:4d:79:65:47, IRQ 11 eth1: VIA Rhine II at 0xfdffe000, 00:40:63:ea:b7:21, IRQ 10. eth1: MII PHY found at address 1, status 0x786d advertising 05e1 Link 0021. eth0: link up, 10Mbps, half-duplex, lpa 0x0021 eth0: no IPv6 routers present eth1: Identified chip type is 'RTL8169s/8110s'. eth1: RTL8169 at 0xdf81c000, 00:18:4d:79:65:47, IRQ 11
This looks to indicate that the kernel is first loading the r8169 driver, then the via-rhine, then somehow the 8169 goes over to eth1 - however this is after the system has booted and the network scripts have run.
Anyone have a clue what's going on here? :P
-- Steven Haigh
Email: netwiz@crc.id.au Web: http://www.crc.id.au Phone: (03) 9017 0597 - 0404 087 474
-
Steven Haigh