For those of us who have had to be using the AUR r8169 package to make our LAN chip work (better), it is time to go back to using the r8168, as r8169 is now incompatible with the current (& beyond I expect) kernel.
[edit:] (Though it is working for a least one person that I'm aware of? Perhaps this is due to a chip firmware/revision? I don't know.) /edit
The r8168 driver now seems to be working (it works after boot-up for me). The word is that r8168 should work after the update to 8.028.00-5.
I'm looking forward to being able to put a [SOLVED] on this problem on a thread I started on the ARCH forum on the 1st day of 2012, as both drivers have been giving me trouble with this NIC chip since then.
I even bought a NIC to replace (turn off in the BIOS) the onboard chip, & guess what, when I unpackaged the card it had the same chip but at least was a later revision. The new NIC has worked well enough on the AUR r8169 package, sometimes taking more than one boot before it would connect. Though it would at least stay connected as opposed to the on-board chip using either driver. That is until today's kernel upgrade put a stop to that.
The next week should tell the story as to whether the new kernel/driver combo has put this problem to bed...?
Last edited by handy (2012-05-04 21:47:44)
I am running latest kernel
[mrgreen@macmillan ~]$ uname -r 3.3.4-2-ARCH
and have 8168
[mrgreen@macmillan ~]$ lspci | grep Ethernet 03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 06)
Not had any problems with stock modules....
Can you post your lspci [version of r816x] ?
handy ~ $ 03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 06)
The onboard chip (which is more troublesome & not in use) is rev 01.
Last edited by handy (2012-05-04 23:58:12)