[SOLVED] ADDRCONF(NETDEV_UP): eth0: link is not ready

sjampoo · 06-19-2010, 10:49 AM

Done a fresh installation on a brand new Acer Veriton M265

It came with Linpus installed ( Gnome ) and I want to turn it into a virtualbox host with slackware13.1 64

Problem: The realtek card (eth0) doesn't work like I would like it to work. I briefly tested the factory Linpus installation, and everything worked. Installed Slackware, and no network.

Looks like its a Realtek 8169(?) ( Gigabit lan ) onboard card, that needs a special treatment? I did find some Ubuntu users fixing Realtek cards not giving a link after a dualboot with Windows, (Wake-On-Lan driver/function in windows sets eth-card into some kind of state that Linux can't get it out of. BUT: I haven't had a dualboot (or Windows) on the machine (ever). The postings I did find where all 'old': 2008-ish..
I would think the bleeding edge 13.1 ( :P ) slackware would run like a charm on this fairly new, but not bleeding edge hardware. (Pentium E5400, 2Gb ram, 160Gb hdd.

PS:
Will either run VirtualBox to host a W2K environment, or VMware player with XP Pro. W2K is good enough, but for remote desktopwork I will need VirualBox PUEL version, where VMware player doesn't support this (does it?) so for remote desktop I'll need XP Pro, I guess.

fskmh · 06-19-2010, 12:56 PM

Code:

su -c "lspci | grep -i ether"

So, for example, on my PC I get:

Code:

06:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 02)

AFAIK this uses the r8169 driver:

Code:

fskmh@fskmh:~> /sbin/lsmod | grep r8169
r8169                  36193  0 
mii                     3914  2 usbnet,r8169

To check that this device is in fact eth0:

Code:

fskmh@fskmh:~> /usr/sbin/ethtool -i eth0
driver: r8169
version: 2.3LK-NAPI
firmware-version: 
bus-info: 0000:06:00.0

sjampoo · 06-23-2010, 03:19 AM

lspci | grep -i ether:

Code:

02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 03)

Looks like the same, but newer revision as yours ( @fskmh )

/sbin/lsmod | grep r8169

Code:

r8169     36193  0
mii    3914 1 r8169

then, as root:

Code:

/usr/sbin/ethtool -i eth0

driver: r8169
version: 2.3LK-NAPI
firmware-version:
bus-info:0000:02:00.0

sjampoo · 06-23-2010, 03:31 AM

Further investigation:

dmesg | grep eth0

Code:

eth0: TRL8168d/8111d at ( adress etc etc IRQ 26 )
r8169: eth0: link down
r8169: eth0: link down
ADDRCONF(NETDEV_UP): eth0: link is not ready

still puzzled.

sjampoo · 06-23-2010, 04:24 AM

*ARGH*

SOLVED!

Murphy's law.

Still can't figure out why it did work out of the box with Linpus, but it was the freak'n CABLE! Got 4 wall plugs, 4 pc's, switched cables over and voila: works! The pc that got the cable from the slackbox went off-line instantly, so must be either the cable or the wall plug.

Everybody thank you for lurking and please whipe off that grin: hardware failure where you least expect it