https://bugzilla.novell.com/show_bug.cgi?id=733506 https://bugzilla.novell.com/show_bug.cgi?id=733506#c1 --- Comment #1 from Craig Arno 2011-12-01 04:27:59 UTC --- Thought it might be helpful to provide network device chip numbers: Sabertooth 990FX: RTL8111E (the last digit could be a C) TEG-PCITXR: RTL8169SC The Sabretooth chip is tiny. I had trouble reading it with a bright light, magnifying glass, and trying to look at it from different directions. That said, I'm pretty sure the last digit is an E. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=733506 https://bugzilla.novell.com/show_bug.cgi?id=733506#c3 --- Comment #3 from Craig Arno 2011-12-01 18:49:06 UTC --- Created an attachment (id=465357) --> (http://bugzilla.novell.com/attachment.cgi?id=465357) dmesg - full output from boot for r8169 driver issue I figure this may provide more clues about the Realtek r8169 driver issue to someone with the background to understand. This is from a "stock" ASUS Sabretooth 990FX Motherboard right after a fresh install of OpenSUSE 12.1. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=733506 https://bugzilla.novell.com/show_bug.cgi?id=733506#c5 --- Comment #5 from Craig Arno 2011-12-01 19:40:24 UTC --- Apparently this problem has been around for years and affects many, which makes it surprising that it hasn't been fixed in the kernel distributions (used by SUSE, Ubuntu, Slackware, etc) yet. I don't know who to contact, so I won't be able to report this to the right people. It appears the solution that works for many is to go to http://www.realtek.com.tw/downloads/downloadsView.aspx?Langid=1&PNid=13&PFid=5&Level=5&Conn=4&DownTypeID=3&GetDown=false Download, compile into the Kernel, figure out how to disable the existing r8169 driver so it won't respond to PCI-ID[10EC:8168], install the latest driver, then reboot with a working driver. This PCI-ID matches what my system is reporting. I also see the same driver covers 8111C and 8111E chips (good for me since I can't figure out which I have on the motherboard. Most of what I'm reading, the successes read like this fellows message: Shane Guillory (shane-rppl) wrote on 2008-03-21: #14 We are using ... with the RealTek 8111/8168 PCI-E adapter and had similar issues to other bugs reported here. The manufacturer's r8168 driver (now at 8.005.00 as of 2008-01-29) for the 8111/8168 family(PCI id 10EC:8168) is generally much more robust than the r8169 driver in the kernel. With the mfg's r8168 (8168, that is, not 8169), I don't need to periodically restart the network any more, and it also fixed a major issue for us - the network adapter only worked if the adapter was physically connected at startup, the network would come up but not quite work right if connected after startup. I don't know the process for this, but based on our experience, we would recommend that the Mfg's 8168 driver be incorporated into the kernel, and the [10EC:8168] pci id to be unassociated with the r8169 driver. Shane's description of the problem; comes up but doesn't quite work, matches my experience. I'll try to make time this weekend to see if I can duplicate the successes I'm reading, then order my next system. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=733506 https://bugzilla.novell.com/show_bug.cgi?id=733506#c7 --- Comment #7 from Craig Arno 2011-12-02 06:34:20 UTC --- The new r8168 driver does not recognize the separate TRENDnet TEG-PCITXR PCI card with a RTL8169SC chip. I submitted a ticket to TRENDnet since their downloaded Linux driver software won't build. https://www.trendnet.com//asp/helpdesk/verifyhd.asp?id=99552 I'm now back to where this issue started after ruling out one more possible solution. Suggestions? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=733506 https://bugzilla.novell.com/show_bug.cgi?id=733506#c Craig Arno changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|eth0:r8169 driver: No |eth0:r8169 driver, Realtek |DHCP/Static IP only works |RTL8111E chip: IPv4 No |after fiddling; ASUS |DHCP/Static IP only; ASUS |Sabertooth 990FX |Sabertooth 990FX |motherboard |motherboard -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=733506 https://bugzilla.novell.com/show_bug.cgi?id=733506#c10 Craig Arno changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P0 - Crit Sit |P5 - None Severity|Critical |Major --- Comment #10 from Craig Arno 2011-12-09 04:46:37 UTC --- I don't like having to admit a mistake... there is a bug, just not the one I thought and identified previously. Summary: - Install OpenSUSE 12.1 x64 - Upgrade the r8169 driver module to r8168 from Realtek's site. - Setup for DHCP4 - /etc/init.d/network restart - Wait about 30 seconds - Run ifconfig to see the new DHCP4 provided IP (mine is 192.168.90.224/24) with correct gateway (192.168.90.2) and DNS settings. My new server; ASUS Sabertooth 990FX/Phenom T1100 8GB-DDR3 SSD connected to my 5-year old functioning Server; Athlon 6000+ 8GB-DDR2 running OpenSUSE 10.3 x64 through a D-Link DGS-1024D Gigabit Switch through 100ft CAT6 to a D-Link DIR-655 on another floor from this I ran another 100ft CAT6 to a D-Link DGS-1008G H/W Ver A1 Gigabit Switch sitting on a desk (this is my home, not office, and yes, 100ft/30meters is needed) This configuration didn't work. When I removed the D-Link DGS-1008G H/W Ver A1 Gigabit Switch, then DHCP4 started working. Static IP worked in all cases. I installed Windows 7 during debug because ASUS wouldn't talk to me while I had Linux installed, and noted Windows 7 had identical problems with zombie ethernet. When I removed the third switch, Windows 7 DHCP started working. This is when I reformatted the drive with OpenSUSE 12.1 to resume debug. DHCP didn't work with the delivered r8169 driver as installed for the RTL-8111E chip. I configured the port to a static IP and it worked well enough to download the new 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. After installing this new driver from Realtek and configuring back to DHCP4only, then "/etc/init.d/network restart", DHCP4 worked as I expected! For anyone trying to repeat this success--- During install I included all 12.1 C/C++ development tools and kernel source. Installing the new driver was as easy as executing (as root): tar xjf r8168-8.027.00.tar.bz2 cd r8168-8.027.00/ ./autorun.sh Which produced: linux-ijz2:~/r8168-8.027.00 # ./autorun.sh Check old driver and unload it. rmmod r8169 Build the module and install Backup r8169.ko rename r8169.ko to r8169.bak DEPMOD 3.1.0-1.2-desktop load module r8168 Completed. What I don't know is if the problem was a result of having 3 switches between servers, or if the brand new "green" D-Link DGS-1008G H/W Ver A1 Gigabit Switch caused the problem. Removing this last switch cleared the problem. Fighting two problems; bad driver, and a network configuration that wasn't working right made this issue very difficult to track down. I'll perform more testing, but I expect to say my system is now working. I'm leaving this bug open as "Major" because it does stop a new installation on an ASUS Sabertooth 990FX from working. It takes a moderately sophisticated understanding of network and Linux issues to figure out and resolve. I've been using Linux since 1994. I will attempt to report this bug to www.kernel.org. I'd appreciate it if someone from the OpenSUSE Kernel team would follow up to make sure I was successful with my kernel.org bug reporting for the r8169 module before closing this report. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=733506 https://bugzilla.novell.com/show_bug.cgi?id=733506#c12 Vadim Krevs changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |vkrevs@yahoo.com --- Comment #12 from Vadim Krevs 2012-08-31 10:26:47 UTC --- Similar issue on my new Sony VAIO SVE1711X1EB laptop on openSUSE 12.1. This laptop comes with a Realtek Gigabit Ethernet adapter (from lspci -v): 0e:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 07) Subsystem: Sony Corporation Device 90ac Flags: bus master, fast devsel, latency 0, IRQ 43 I/O ports at 2000 [size=256] Memory at c5004000 (64-bit, prefetchable) [size=4K] Memory at c5000000 (64-bit, prefetchable) [size=16K] Capabilities: [40] Power Management version 3 Capabilities: [50] MSI: Enable+ Count=1/1 Maskable- 64bit+ Capabilities: [70] Express Endpoint, MSI 01 Capabilities: [b0] MSI-X: Enable- Count=4 Masked- Capabilities: [d0] Vital Product Data Capabilities: [100] Advanced Error Reporting Capabilities: [140] Virtual Channel Capabilities: [160] Device Serial Number 07-00-00-00-68-4c-e0-00 Kernel driver in use: r8169 After hibernate, the r8169 driver loads, but Network Manager fails to get an IP address and /var/log/messages contains Aug 31 08:29:43 starfire rcnetwork[13640]: Starting the NetworkManager Aug 31 08:29:43 starfire kernel: [ 1233.787223] r8169 0000:0e:00.0: eth0: link down Aug 31 08:29:43 starfire kernel: [ 1233.788409] ADDRCONF(NETDEV_UP): eth0: link is not ready I've used "solution" (1) from http://en.opensuse.org/SDB:Realtek_8169_driver_problem to deal with it, but would very much prefer the native kernel driver to work properly. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.