Mailinglist Archive: opensuse-bugs (4254 mails)
|< Previous||Next >|
[Bug 733506] eth0:r8169 driver: No DHCP/Static IP only works after fiddling; ASUS Sabertooth 990FX motherboard
- From: bugzilla_noreply@xxxxxxxxxx
- Date: Thu, 1 Dec 2011 19:40:25 +0000
- Message-id: <20111201194025.7D08324551D@molor.provo.novell.com>
--- Comment #5 from Craig Arno <craig@xxxxxxxx> 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
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
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.
|< Previous||Next >|