More Trouble with Realtek Ethernet RTL8111/8168/8411 (rev 12)

brrbrrbruno · 2014-08-30 03:18:32

Hello everybody!

I got the same problem as others with the ethernet controller model mentioned in the title, but i have (rev 12) not 6 or 10 like others ...

I followed this thread:
https://bbs.archlinux.org/viewtopic.php?id=176413&p=2
... but none of the solutions worked.

i plugin the ethernet cable but network manager still shows "no cable attached" and no ip adress information ...

here are my details:
i have the same problem in kernel 3.16 and 3.14

$ ifconfig
-------------------------------------------------------------------------------------
enp3s0f1: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        ether 00:90:f5:f9:fd:d9  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 0  (Local Loopback)
        RX packets 656  bytes 51072 (49.8 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 656  bytes 51072 (49.8 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

wlp2s0: wlan chip by intel works fine

$ lspci -v
----------------------------------------------------------------------------------------------
[...]

03:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. Device 5287 (rev 01)
	Subsystem: CLEVO/KAPOK Computer Device 5494
	Flags: bus master, fast devsel, latency 0, IRQ 56
	Memory at f7c15000 (32-bit, non-prefetchable) [size=4K]
	Expansion ROM at f7c00000 [disabled] [size=64K]
	Capabilities: <access denied>
	Kernel driver in use: rtsx_pci
	Kernel modules: rtsx_pci

03:00.1 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 12)
	Subsystem: CLEVO/KAPOK Computer Device 5494
	Flags: bus master, fast devsel, latency 0, IRQ 61
	I/O ports at e000 [size=256]
	Memory at f7c14000 (64-bit, non-prefetchable) [size=4K]
	Memory at f7c10000 (64-bit, non-prefetchable) [size=16K]
	Capabilities: <access denied>
	Kernel driver in use: r8169
	Kernel modules: r8169

the computer that has the problem is a laptop and i dunno why there are 2 Realtek Entries ... it definitly has only ONE ethernet port!

((installing aur r8168 and loading the module ofc did not fix the problem as suggested by others ...))

$ dmesg | grep 8169
------------------------------------------------------------
[    2.304595] r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded
[    2.304609] r8169 0000:03:00.1: can't disable ASPM; OS doesn't have ASPM control
[    2.310138] r8169 0000:03:00.1: irq 61 for MSI/MSI-X
[    2.310452] r8169 0000:03:00.1 eth0: RTL8411 at 0xffffc900018c6000, 00:90:f5:f9:fd:d9, XID 1c800880 IRQ 61
[    2.310457] r8169 0000:03:00.1 eth0: jumbo features [frames: 9200 bytes, tx checksumming: ko]
[    5.594516] r8169 0000:03:00.1 enp3s0f1: rtl_phy_reset_cond == 1 (loop: 100, delay: 1).
[    5.596608] r8169 0000:03:00.1 enp3s0f1: link down

thanks for reading!

Last edited by brrbrrbruno (2014-08-30 03:28:21)

pigiron · 2014-08-30 08:24:03

Perhaps someone will come along and find that eating a moonpie will fix the problem. All I can go by is my novice interpretation of the code; and it's actually not much fun to follow (dem devlopers so uber clever with da macros).

On the technical side, I think the key line you supplied is "[ 5.596608] r8169 0000:03:00.1 enp3s0f1: link down".

Speaking in geek, that line appears to be saying that during bringup, the code interrogates the "TBILinkOk" bit in the "TBICSR: Ten Bit Interface Control and Status" register and finds it's not set. The spec says that if it were set it "...indicates that the channel connecting to the link partner is established." In unhuman terms I think means that the PHY of the ethernet adapter is reporting that the link is down.

So outside of eating a moonpie what should you do (actually not a bad idea)? Try swapping a "known" good cable with the one you're now using; try swapping ports (on your router???) with a "known" good port; substitute Network Manager with something better (I'm kidding... no I'm not). Besides that we can only hope the code is "doing the right thing(tm)" when it loads the firmware.

After you go through all that and it still fails, then fire off an email to the netdev@vger.kernel.org mailing list while supplying all the info you can possibly think of (especially the specific kernel... and be prepared to install a "vanilla" kernel). They own that code and can probably point you in a better direction than any of us mortals can.

But as the old/original Dennis Miller used to say "That's just my opinion. I could be wrong".

brrbrrbruno · 2014-09-01 06:06:56

thanks for your reply ...
tried different cables ...
tried different ports ...

will write the mail after i tried configuring with dhcpd ...

ps: what is moonpie?

ratcheer · 2014-09-01 14:25:19

brrbrrbruno wrote:

ps: what is moonpie?

LOL. It is a southern US pre-packaged cookie treat.

http://en.wikipedia.org/wiki/Moon_pie

Tim

ewaller · 2014-09-01 15:50:21

Moonpie. There is some good eating...

That Realtek chipset has caused a lot of issues. When you connect the cables, do the link lights on the ports (both the computer and the router) light?

Last edited by ewaller (2014-09-01 15:50:38)

brrbrrbruno · 2014-09-10 11:30:39

no they both don't light up ... but the cable definitly works ...
and using something other than network manager does not help either ... tried dhclient and dhcpd!
please excuse my delayed answer.

@moonpie:
wow looks to sweet to swallow ... but is moonpie something you give children so that they forget that they have hurt their finger or something ... i'm still totally confused about this colloquial expression "eating a moonpie will fix the problem" (not a native myself) ...

Last edited by brrbrrbruno (2014-09-10 11:32:08)

brrbrrbruno · 2014-09-10 12:09:00

UPDATE:
sent a mail to netdev@vger.kernel.org

UPDATE2:

just booted into ubuntu ... out of the box same problem ...
i guess that means that kernel 3.13.x has the same problem with this chipset ...

Additional information:
i bought the laptop this year from a vendor that only sells "linux computers" and linux compatible hardware, so i guess a broken ethernet port is unlikely ... i will contact the vendor though!

Last edited by brrbrrbruno (2014-09-10 12:11:24)

whoop · 2014-09-25 14:57:03

Any updates? I have RTL8111/8168/8411 version 01 and it's not working at al for me (currently on 3.16.3-1-ARCH)

[root@pc whoop]# netctl start static
Job for netctl@static.service failed. See 'systemctl status netctl@static.service' and 'journalctl -xn' for details.
[root@pc whoop]# systemctl status netctl@static.service
● netctl@static.service - A basic static ethernet connection
   Loaded: loaded (/etc/systemd/system/netctl@static.service; enabled)
   Active: failed (Result: exit-code) since Thu 2014-09-25 17:31:45 CEST; 8s ago
     Docs: man:netctl.profile(5)
  Process: 1021 ExecStart=/usr/lib/network/network start %I (code=exited, status=1/FAILURE)
 Main PID: 1021 (code=exited, status=1/FAILURE)

Sep 25 17:31:40 pc systemd[1]: Starting A basic static ethernet connection...
Sep 25 17:31:40 pc network[1021]: Starting network profile 'static'...
Sep 25 17:31:45 pc network[1021]: No connection found on interface 'eth0' (timeout)
Sep 25 17:31:45 pc network[1021]: Failed to bring the network up for profile 'static'
Sep 25 17:31:45 pc systemd[1]: netctl@static.service: main process exited, code=exited, status=1/FAILURE
Sep 25 17:31:45 pc systemd[1]: Failed to start A basic static ethernet connection.
Sep 25 17:31:45 pc systemd[1]: Unit netctl@static.service entered failed state.
[root@pc whoop]# journalctl -xn
-- Logs begin at Tue 2014-02-04 00:43:12 CET, end at Thu 2014-09-25 17:31:45 CEST. --
Sep 25 17:31:40 pc systemd[1]: Starting A basic static ethernet connection...
-- Subject: Unit netctl@static.service has begun with start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit netctl@static.service has begun starting up.
Sep 25 17:31:40 pc network[1021]: Starting network profile 'static'...
Sep 25 17:31:40 pc kernel: r8169 0000:03:00.0 eth0: link down
Sep 25 17:31:40 pc kernel: r8169 0000:03:00.0 eth0: link down
Sep 25 17:31:40 pc kernel: IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
Sep 25 17:31:45 pc network[1021]: No connection found on interface 'eth0' (timeout)
Sep 25 17:31:45 pc network[1021]: Failed to bring the network up for profile 'static'
Sep 25 17:31:45 pc systemd[1]: netctl@static.service: main process exited, code=exited, status=1/FAILURE
Sep 25 17:31:45 pc systemd[1]: Failed to start A basic static ethernet connection.
-- Subject: Unit netctl@static.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit netctl@static.service has failed.
-- 
-- The result is failed.
Sep 25 17:31:45 pc systemd[1]: Unit netctl@static.service entered failed state.

Last edited by whoop (2014-09-25 15:37:59)

Arch Linux

#1 2014-08-30 03:18:32

More Trouble with Realtek Ethernet RTL8111/8168/8411 (rev 12)

#2 2014-08-30 08:24:03

Re: More Trouble with Realtek Ethernet RTL8111/8168/8411 (rev 12)

#3 2014-09-01 06:06:56

Re: More Trouble with Realtek Ethernet RTL8111/8168/8411 (rev 12)

#4 2014-09-01 14:25:19

Re: More Trouble with Realtek Ethernet RTL8111/8168/8411 (rev 12)

#5 2014-09-01 15:50:21

Re: More Trouble with Realtek Ethernet RTL8111/8168/8411 (rev 12)

#6 2014-09-10 11:30:39

Re: More Trouble with Realtek Ethernet RTL8111/8168/8411 (rev 12)

#7 2014-09-10 12:09:00

Re: More Trouble with Realtek Ethernet RTL8111/8168/8411 (rev 12)

#8 2014-09-25 14:57:03

Re: More Trouble with Realtek Ethernet RTL8111/8168/8411 (rev 12)

Board footer