Bug#726142: Info received (Bug#726142: Realtek NIC (r8169 driver) won't work at gigabit speed, must be forced to 100MB)

2013-10-13 Thread Shawn Heisey
On 10/13/2013 11:42 AM, Ben Hutchings wrote: > - There is no firmware patch for your LAN-on-motherboard chip > (RTL8168B). > > - There is a firmware patch for the chip on the PCIe card (RTL8168D), > but this was never included in the driver in Debian kernels (except in > some experimental versions

Bug#726142: Info received (Bug#726142: Realtek NIC (r8169 driver) won't work at gigabit speed, must be forced to 100MB)

2013-10-12 Thread Shawn Heisey
I left out the answer to one of your questions. Yes, the firmware-realtek package is installed. It is version 0.28+squeeze1. During my temporary 3.2 backports kernel experiment, I also upgraded all the firmware packages to the matching version from backports. This may be indirectly significant -

Bug#726142: Realtek NIC (r8169 driver) won't work at gigabit speed, must be forced to 100MB

2013-10-12 Thread Shawn Heisey
On 10/12/2013 8:52 PM, Ben Hutchings wrote: > In this original broken configuration, were there any ethtool settings > in /etc/network/interfaces ? > > Is the firmware-realtek package installed? > > Can you provide the boot log messages from r8169 > (grep r8169/var/log/dmesg) ? When I first set

Bug#726142: Realtek NIC (r8169 driver) won't work at gigabit speed, must be forced to 100MB

2013-10-12 Thread Shawn Heisey
Package: linux-2.6 Version: 2.6.32-48squeeze4 Severity: important This is a continuation of archived bug number 596390. The problem has never been solved. I have a workaround that I consider unsatisfactory. With everything set to auto-negotiate, and starting from a powered off system, the NIC h

Bug#596390: Log messages from 2.6.30 and 2.6.32

2010-12-01 Thread Shawn Heisey
On 11/20/2010 11:55 AM, Ben Hutchings wrote: Try 'mii-tool -vv eth0'? New output. Just in case, I tried it with a third and fourth v, no difference. This is with it hard-set to 100 full, I can do it with it set to auto when I get home. frodo:~# mii-tool -vv eth0 Using SIOCGMIIPHY=0x8947 e

Bug#596390: Log messages from 2.6.30 and 2.6.32

2010-11-20 Thread Shawn Heisey
On 11/20/2010 10:20 AM, Shawn Heisey wrote: Unknown RealTek chip (mask: 0x2800) I found what looks like a bug report and resolution for this same chip and problem in FreeBSD. http://www.pubbs.net/200904/netbsd/15177-50rc3-messed-up-rtl8111dl-onboard-nic.html I know there are licensing

Bug#596390: Log messages from 2.6.30 and 2.6.32

2010-11-20 Thread Shawn Heisey
On 9/11/2010 8:15 PM, Ben Hutchings wrote: Please try this while running kernel version 2.6.32: 1. Enable additional error logging by running: ethtool -s eth0 msglvl 0x3f 2. Enable autoneg again 3. Disconnect and reconnect the cable 4. Check for any new error messages in the kernel log Also send

Bug#596390: Log messages from 2.6.30 and 2.6.32

2010-09-11 Thread Shawn Heisey
On 9/10/2010 4:57 PM, Ben Hutchings wrote: Please test a newer version. There was a bug fix to r8169 in version 2.6.32-16 which might address this. I was already on the -20 version. Then I tried the -21 recently added to the backports archive, with no change. After a little experimentati

Bug#596390: linux-image-2.6.32-bpo.5-amd64: r8169 Link not ready

2010-09-10 Thread Shawn Heisey
Package: linux-2.6 Version: 2.6.32-20~bpo50+1 Severity: important WHen I boot this kernel, my ethernet port stops working. The light on the switch goes out. It is a Cisco 3550 switch with 10 10/100/1000 ports and two GBIC ports. This server is plugged into a 10/100/1000 port. In order to get