Opened 2 years ago

Last modified 16 months ago

#14576 new bug

Realtek 8168 Ethernet not working

Reported by: mrentropy Owned by: nobody
Priority: normal Milestone: Unscheduled
Component: Drivers/Network/rtl81xx Version: R1/beta1
Keywords: Cc:
Blocked By: Blocking:
Platform: x86-64


RealTek 8168 isn't working booting via EUFI on a Kodlix N42-D system (Apollo Lake chipset).

device Network controller (Ethernet controller) [2|0|0]
  vendor 10ec: Realtek Semiconductor Co., Ltd.
  device 8168: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller

As far as I can tell, the device should be supported (past bug reports for Haiku, and listed under the 're' driver for FreeBSD).

Nothing is listed under /dev/net, nothing appears in the Network prefs panel, and ifconfig only shows the loop device.

Attachments (3)

listdev_ethernet.txt (129 bytes ) - added by mrentropy 2 years ago.
listdev for Ethernet
listdev.txt (4.4 KB ) - added by mrentropy 2 years ago.
The entire listdev
syslog (127.6 KB ) - added by mrentropy 2 years ago.
The Syslog

Download all attachments as: .zip

Change History (9)

by mrentropy, 2 years ago

Attachment: listdev_ethernet.txt added

listdev for Ethernet

by mrentropy, 2 years ago

Attachment: listdev.txt added

The entire listdev

by mrentropy, 2 years ago

Attachment: syslog added

The Syslog

comment:1 by diver, 2 years ago

Component: Network & InternetDrivers/Network/rtl81xx
[rtl81xx] (re) reset never completed!

comment:2 by michaelvoliveira, 2 years ago

Wlan RTL8192EE is not supported by the FreeBSD driver too.
Realtek PCIe Wlan
vendor 0x10ec
id 818b

comment:3 by mrentropy, 21 months ago

Using Haiku hrev52675, the device is now showing up in the Network preferences and /dev/net. However, Network preferences says that there is no link (there is). Disabling and re-enabling doesn't recognize the link.

The KERN: [rtl81xx] (re) reset never completed! line is still in Syslog.

comment:4 by waddlesplash, 21 months ago

KERN: [rtl81xx] (re) PHY read failed
KERN: [rtl81xx] (re) attaching PHYs failed

This is the actual problem.

comment:5 by waddlesplash, 20 months ago

Looks like there is a FreeBSD ticket about this: ​

It's mentioned there that taking the interface down and then bringing it back up again works around the problem. So, please try that (though interface down/up on Haiku behaves slightly differently than on FreeBSD, so you many not get the side effect.)

comment:6 by waddlesplash, 16 months ago

Please retest after hrev53174.

Note: See TracTickets for help on using tickets.