10ec:8168 r8169 fails to autonegotiate speed/duplex

AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: ingo 1644 F.... pulseaudio
 /dev/snd/pcmC0D0p: ingo 1644 F...m pulseaudio
 /dev/snd/timer: ingo 1644 f.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'Audigy'/'SB Audigy 1 [SB0090] (rev.3, serial:0x511102) at 0xec00, irq 22'
   Mixer name : 'TriTech TR28602'
   Components : 'AC97a:54524123'
   Controls : 194
   Simple ctrls : 30
DistroRelease: Ubuntu 10.04
HibernationDevice: RESUME=UUID=8a62c5be-3701-4b55-b393-6f90bf413b29
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha amd64 (20100312)
IwConfig:
 lo no wireless extensions.

 eth0 no wireless extensions.
MachineType: System manufacturer System Product Name
NonfreeKernelModules: nvidia
Package: linux (not installed)
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-21-generic root=UUID=660123b5-42b4-48d7-9bac-10b31ddc10eb ro quiet splash
ProcEnviron:
 LANG=de_DE.utf8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-21.32-generic 2.6.32.11+drm33.2
Regression: Yes
RelatedPackageVersions: linux-firmware 1.34
Reproducible: Yes
RfKill:

Tags: lucid networking regression-potential needs-upstream-testing
Uname: Linux 2.6.32-21-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
dmi.bios.date: 03/18/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2002
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: M4A785TD-V EVO
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2002:bd03/18/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A785TD-VEVO:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

This problem affects me too.
It was introduced around the time when kernel version 2.6.31.20 was relesased. Before that update the network connection worked flawlessly. Therefore I am marking it as a regression.

I can reproduce this bug with the same steps Mathieu pointed out:
ethtool -s eth0 autoneg off

The suggested workaround (ethtool -s eth0 autoneg off) works for me too, but means the network is running at 10Mbps half duplex. (Forcing it to 10baseT-HD with mii-tool also works with the same effect).

03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 03)
Connected to a 100Mbps switch.

Network worked perfectly in Ubuntu 9.04 and 9.10. I know Realtek NICs generally suck, but since it worked before, I have high hopes that it can work again :)

It actually did work in Lucid too, but was broken by some upgraded packages.
Not being able to tell you more - because of lack of knowledge - makes me sad. :(

Please fix this...

This bug also affects me. My hardware is:

02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 03)
 Subsystem: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller
 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
 Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
 Latency: 0, Cache Line Size: 32 bytes
 Interrupt: pin A routed to IRQ 27
 Region 0: I/O ports at d800 [size=256]
 Region 2: Memory at fdfff000 (64-bit, prefetchable) [size=4K]
 Region 4: Memory at fdff8000 (64-bit, prefetchable) [size=16K]
 Expansion ROM at feae0000 [disabled] [size=128K]
 Capabilities: <access denied>
 Kernel driver in use: r8168
 Kernel modules: r8168

Yes, I have tried the r8168 driver from Realtek (http://www.realtek.com.tw/downloads/downloadsView.aspx?Langid=1&PNid=13&PFid=5&Level=5&Conn=4&DownTypeID=3&GetDown=false), the version is 8.018.00, but it doesn't work.

My workaround:
  sudo mii-tool -R ethX

Then ethX can work at 10 Mbps, link ok.
  ethX: 10 Mbit, half duplex, link ok

Although miitool reports the link is OK. But the ethX cannot send and receive any packets:

ping 192.168.1.1
 PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data.
 From 192.168.1.3 icmp_seq=1 Destination Host Unreachable
 From 192.168.1.3 icmp_seq=2 Destination Host Unreachable

mii-tool eth1
 th1: 10 Mbit, half duplex, link ok

So it's failed. //sigh

I have tried 3 versions:

 1. r8168 driver 8.018.00 (Realtek)
 2. r8169 from kernel 2.6.31 (ubuntu 9.10)
 3. r8169 from kernel 2.6.34 rc6 (kernel.org)

But all failed.

Can anybody save me?

I know it worked until Lucid Beta-2.
In Ubuntu 9.10 it's working fine too.

And it works when I use another end point. I have two routers, both Linksys models. One is capable of 1 Gb/s (WRT610N), the other 100 Mb/s (WRT160NL). Just the one with the 100 Mb/s link fails, on the other autonegotiation is working flawlessly.

Don't know if this info helps in any way, just wanted to point it out.

Thank Laryllan.

Yes, I have only one router which is TP-Link WL-541G+ with 100 Mb/s Ethernet ports.
In Ubuntu 9.10 it's working fine, but after upgrade to 10.04, it fails ...

Same here, issue is worked around with "ethtool -s eth2 autoneg off"

ethtool -s eth2 autoneg off
lspci -v -s 02:00.0
02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 03)
 Subsystem: ASUSTeK Computer Inc. Device 83a3
 Flags: bus master, fast devsel, latency 0, IRQ 27
 I/O ports at d800 [size=256]
 Memory at f8fff000 (64-bit, prefetchable) [size=4K]
 Memory at f8ff8000 (64-bit, prefetchable) [size=16K]
 Expansion ROM at feaf0000 [disabled] [size=64K]
 Capabilities: [40] Power Management version 3
 Capabilities: [50] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable+
 Capabilities: [70] Express Endpoint, MSI 01
 Capabilities: [ac] MSI-X: Enable- Mask- TabSize=4
 Capabilities: [cc] Vital Product Data <?>
 Capabilities: [100] Advanced Error Reporting <?>
 Capabilities: [140] Virtual Channel <?>
 Capabilities: [160] Device Serial Number 00-00-00-00-00-00-00-00
 Kernel driver in use: r8169
 Kernel modules: r8169

In my case a BIOS update for m4a785td-v evo solved the issue.

I own the same mother board and updated to BIOS version 2005 - issue not resolved here... :(

Assigning this to myself for the time being

Robin, François, Laryllan,

The way I see things, the issues you are reporting are unrelated. This is an issue specific to running Lucid, so Ubuntu 10.04, with Dell laptop hardware. Any different "environments" unfortunately change a lot of variables. Best bet is to open a new bug so that developers can look at it.

Øystein, as above, please open a new bug regarding the issues you're experiencing, there is not enough information in your comment to say if this is really a related issue.

In Windows, the NIC does not work either, and testing with another Dell Vostro 3400 yields no such issues, so I'm putting this on the case of broken hardware and marking this bug as Invalid.

To Mathieu Trudel :
  No, I don't think so.
  Now I have used the specified version of r8169.c from git.kernel.org, it's taken from:

http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=blob;f=drivers/net/r8169.c;hb=2d6a5e9500103680464a723a4564961675652680

  and the network card works perfectly.
So I think you should test this version,

eth1: negotiated 100baseTx-FD flow-control, link ok

02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 03)
 Subsystem: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller
 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
 Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
 Latency: 0, Cache Line Size: 32 bytes
 Interrupt: pin A routed to IRQ 27
 Region 0: I/O ports at d800 [size=256]
 Region 2: Memory at fdfff000 (64-bit, prefetchable) [size=4K]
 Region 4: Memory at fdff8000 (64-bit, prefetchable) [size=16K]
 Expansion ROM at feae0000 [disabled] [size=128K]
 Capabilities: [40] Power Management version 3
  Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=375mA PME(D0+,D1+,D2+,D3hot+,D3cold+)
  Status: D0 PME-Enable- DSel=0 DScale=0 PME-
 Capabilities: [50] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable+
  Address: 00000000fee0100c Data: 4189
 Capabilities: [70] Express (v2) Endpoint, MSI 01
  DevCap: MaxPayload 256 bytes, PhantFunc 0, Latency L0s <512ns, L1 <64us
   ExtTag- AttnBtn- AttnInd- PwrInd- RBE+ FLReset-
  DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported-
   RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop-
   MaxPayload 128 bytes, MaxReadReq 4096 bytes
  DevSta: CorrErr+ UncorrErr- FatalErr- UnsuppReq+ AuxPwr+ TransPend-
  LnkCap: Port #0, Speed 2.5GT/s, Width x1, ASPM L0s L1, Latency L0 <512ns, L1 <64us
   ClockPM+ Suprise- LLActRep- BwNot-
  LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- Retrain- CommClk+
   ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
  LnkSta: Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt-
 Capabilities: [ac] MSI-X: Enable- Mask- TabSize=4
  Vector table: BAR=4 offset=00000000
  PBA: BAR=4 offset=00000800
 Capabilities: [cc] Vital Product Data <?>
 Capabilities: [100] Advanced Error Reporting <?>
 Capabilities: [140] Virtual Channel <?>
 Capabilities: [160] Device Serial Number 00-e0-4c-68-00-00-00-03
 Kernel driver in use: r8169
 Kernel modules: r8169

I have just bought a Zotac ZBOX ID41 Plus, which uses a Realtek 8110SC/8169SC network chip.

The correct driver should be r8169 and it always reports: eth0: link down.

Autonegiation does not work.

Setting the autoneg off enable 10mbit half duplex. However, I have a Gbit capable network and 10mbit is not acceptable.

This bug seems to have existed for several years, please solve.

By the way I use Ubuntu 11.10

I just wanted to post some troubleshooting advice for others who think they may be affected by this bug. I was experiencing the "link down" and autonegotiation issues, which were resolvable with 'sudo ethtool -s eth0 autoneg off' but that gave me a virtually useless 10BaseT/half connection! I now have a Gigabit connection and the coveted green light on my router. I thought it was a software problem, but it was in fact a **temporary hardware bug**.

I spent about 10 hours troubleshooting with different drivers, kernels, and ethtool settings before discovering the problem was really due to a corrupted residual memory on the network card. So, before doing wasting your time troubleshooting, try this:

1) power down the computer safely
2) unplugging the network cable and power cable from the computer
3) wait 15 minutes
4) plug the cables back in
5) power on the computer
6) wait 2 minutes for the link to autonegotiate
7) check link status based on the lights on the router/card (preferred) or ethtool (can be incorrect if the wrong kernel module is installed)

Many thanks to 'tgalati4' at this post for the advice:
http://ubuntuforums.org/archive/index.php/t-1480328.html

I'm now using Maverick 10.10 with the Realtek driver, compiled as shown here:
http://djlab.com/2010/10/fixing-rtl8111-8168b-driver-debian-ubuntu/

However, I suspect the r8169 driver supplied with the kernel would work, now that I've resolved the hardware issue.

This solution may not fix all problems with r8168 cards, but it's **so easy** that you should really try it before troubleshooting the software.

- Fisslefink

Additional details of my **working** configuration:

Hardware: Zotac Zbox HD-ID11

mythtv@beagle:~$ cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=10.10
DISTRIB_CODENAME=maverick
DISTRIB_DESCRIPTION="Ubuntu 10.10"

mythtv@beagle:~$ lspci|grep Real
01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 03)

mythtv@beagle:~$ uname -a
Linux beagle 2.6.37-020637rc2-generic #201011160905 SMP Tue Nov 16 10:15:47 UTC 2010 i686 GNU/Linux

mythtv@beagle:~$ sudo ethtool eth0
Settings for eth0:
        Supported ports: [ TP ]
        Supported link modes: 10baseT/Half 10baseT/Full
                                100baseT/Half 100baseT/Full
                                1000baseT/Full
        Supports auto-negotiation: Yes
        Advertised link modes: 10baseT/Half 10baseT/Full
                                100baseT/Half 100baseT/Full
                                1000baseT/Full
        Advertised pause frame use: Symmetric Receive-only
        Advertised auto-negotiation: Yes
        Speed: 1000Mb/s
        Duplex: Full
        Port: Twisted Pair
        PHYAD: 0
        Transceiver: internal
        Auto-negotiation: on
        MDI-X: Unknown
        Supports Wake-on: pumbg
        Wake-on: g
        Current message level: 0x00000033 (51)
        Link detected: yes

mythtv@beagle:~$ sudo ethtool -i eth0
driver: r8168
version: 8.019.00-NAPI
firmware-version:
bus-info: 0000:01:00.0

mythtv@beagle:~$ sudo modinfo r8168 #do modinfo r8169 if you're not using the Realtek d...

Mathieu Trudel-Lapierre, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? Can you try with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/ .

If it remains an issue, could you run the following command in the development release from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux <replace-with-bug-number>

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please do not test the kernel in the daily folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. As well, please comment on which kernel version specifically you tested.

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream', and comment as to why specifically you were unable to test it.

Please let us know your results. Thanks in advance.

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]