 |
> 00:04.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 20) > Kernel driver in use: 8139cp > Kernel modules: 8139too, 8139cp Both modules are in the 6.2 kernel (2.6.32-220.el6). Can you check to see if the driver is loaded? lsmod | grep 8139 If not, try loading it by a 'modprobe 8139cp'. |
 |
Nothing shows up in lsmod for 8139 modprobe returns 8139cp: 10/100 PCI Ethernet driver 1.3 (Mar 22, 2004) following modprobe, lsmod |grep 8139 shows 8139cp 18786 0 mii 4315 1 8139cp But restarting the network does not start eth0 "Device eth0 does not seem to be present" and lspci does not show the network card. My VPS vendor reports "We noticed this issue already on other customers VPS as Centos 6.1 and 6.2 doesn't get the ethernet card properly. Means the ethernet card doesn't initialized properly on boot up due to this issue the file eth0 under /sys/class/ doesn't exists." |
|
|
Also seeing this issue. Appears to have been introduced in 2.6.32-131.17.1. |
|
|
Not fixed in 2.6.32-220.2.1. (Yes, I know it wasn't in the release notes, but one can be hopeful.) |
|
|
And also not fixed in kernel-2.6.32-220.4.1 |
|
|
I am experiencing the same issue. Network device is present when I boot with kernel-2.6.32-71.29.1 or below but it disappears if I boot with kernel-2.6.32-131.21.1 and above. Also, I found this thread - http://www.webhostingtalk.com/showthread.php?t=1116047 . Sounds like the same issue. If it is, it's happening on other distributions also. Debian 6 is mentioned in that thread and I have seen someone mention Ubuntu 10.10 elsewhere. There is a possible workaround mentioned in the last post of that thread. |
|
|
Also applies to 2.6.32-220.4.2 |
|
|
I use 2.6.32-220 on x68_64 fujitsu mx130s1 Network card's module in the list of module after boot ( tg3 ) -> No eth0 Quick FIX rmmod tg3 modprobe tg3 -> eth0 up |
|
|
dmesg | grep tg3 [ 1.659028] tg3.c:v3.119 (May 18, 2011) [ 1.659064] tg3 0000:02:00.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18 [ 1.659292] tg3 0000:02:00.0: setting latency timer to 64 [ 1.667557] tg3 mdio bus: probed [ 1.667561] tg3 0000:02:00.0: No PHY devices [ 1.667591] tg3 0000:02:00.0: Problem fetching invariants of chip, aborting [ 1.667847] tg3 0000:02:00.0: PCI INT A disabled [ 112.138551] tg3.c:v3.119 (May 18, 2011) [ 112.138626] tg3 0000:02:00.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18 [ 112.138637] tg3 0000:02:00.0: setting latency timer to 64 [ 112.145752] tg3 mdio bus: probed [ 112.149902] tg3 0000:02:00.0: eth0: Tigon3 [partno(BCM57780) rev 57780001] (PCI Express) MAC address 00:19:99:a3:28:8f [ 112.149907] tg3 0000:02:00.0: eth0: attached PHY driver [Broadcom BCM57780] (mii_bus:phy_addr=200:01) [ 112.149912] tg3 0000:02:00.0: eth0: RXcsums[0] LinkChgREG[0] MIirq[0] ASF[0] TSOcap[1] [ 112.149916] tg3 0000:02:00.0: eth0: dma_rwctrl[76180000] dma_mask[64-bit] [ 112.212039] tg3 0000:02:00.0: irq 26 for MSI/MSI-X [ 113.150205] tg3 0000:02:00.0: eth0: Link is down [ 116.153015] tg3 0000:02:00.0: eth0: Link is up at 1000 Mbps, full duplex [ 116.153020] tg3 0000:02:00.0: eth0: Flow control is on for TX and on for RX |
- Anonymous
