RTL8117 Network Interface not working

E

EricD

Member
Proxmox Subscriber
Sep 28, 2019
24
4
23
43
I have a proxmox 6 install on an ASUS Pro-WS-X570-ACE, the onboard Intel NIC is working but the RealTek is causing trouble (not that surprised here). My current guess is the r8169 firmware in the pve-firmware package doesn't understand this newish RealTek NIC?

Here is the device as listed by lspci:
Code: 
06:00.1 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 1a)
    Subsystem: ASUSTeK Computer Inc. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
    Flags: fast devsel, IRQ 24
    I/O ports at c800 [size=256]
    Memory at fc514000 (64-bit, non-prefetchable) [size=4K]
    Memory at fc508000 (64-bit, non-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: [100] Advanced Error Reporting
    Capabilities: [168] Device Serial Number 01-00-00-00-68-4c-e0-00
    Capabilities: [178] Transaction Processing Hints
    Kernel modules: r8169

There is one entry in dmesg about the module:
Code: 
[    1.813008] r8169 0000:06:00.1: unknown chip XID 54a


Here is my install info:
Code: 
$ pveversion -v
proxmox-ve: 6.0-2 (running kernel: 5.0.21-2-pve)
pve-manager: 6.0-7 (running version: 6.0-7/28984024)
pve-kernel-5.0: 6.0-8
pve-kernel-helper: 6.0-8
pve-kernel-5.0.21-2-pve: 5.0.21-3
pve-kernel-5.0.21-1-pve: 5.0.21-2
pve-kernel-5.0.15-1-pve: 5.0.15-1
ceph-fuse: 12.2.11+dfsg1-2.1+b1
corosync: 3.0.2-pve2
criu: 3.11-3
glusterfs-client: 5.5-3
ksm-control-daemon: 1.3-1
libjs-extjs: 6.0.1-10
libknet1: 1.12-pve1
libpve-access-control: 6.0-2
libpve-apiclient-perl: 3.0-2
libpve-common-perl: 6.0-4
libpve-guest-common-perl: 3.0-1
libpve-http-server-perl: 3.0-2
libpve-storage-perl: 6.0-8
libqb0: 1.0.5-1
lvm2: 2.03.02-pve3
lxc-pve: 3.1.0-65
lxcfs: 3.0.3-pve60
novnc-pve: 1.0.0-60
proxmox-mini-journalreader: 1.1-1
proxmox-widget-toolkit: 2.0-7
pve-cluster: 6.0-7
pve-container: 3.0-7
pve-docs: 6.0-4
pve-edk2-firmware: 2.20190614-1
pve-firewall: 4.0-7
pve-firmware: 3.0-2
pve-ha-manager: 3.0-2
pve-i18n: 2.0-3
pve-qemu-kvm: 4.0.0-5
pve-xtermjs: 3.13.2-1
qemu-server: 6.0-7
smartmontools: 7.0-pve2
spiceterm: 3.1-1
vncterm: 1.6-1
zfsutils-linux: 0.8.1-pve2
 
So far this Asus board seems to be the only one using this Realtek network chip version. It's not supported by the mainline r8169 driver yet. I added experimental support for it, based on the Realtek vendor driver. However I have no HW to test, therefore I'd appreciate if you could test it. Patch can be found here: https://patchwork.ozlabs.org/patch/1173105/
It applies on top of linux-next.
 
I've had success with enabling bluetooth on my Asus VM62 VivoPC by adding the keyword 'non-free' to the debian repositories in /etc/apt/sources.list and then copying a specific driver from firmware-realtek. I did not install firmware-realtek because there are conflicts with the pve-firmware package.
You can do this by adding non-free, then as root,:
apt update
apt download firmware-realtek
mkdir firmware-realtek
dpkg -x firmware-realtek_* firmware-realtek

Now you need to 'cp' stuff to
/lib/firmware/rtl_bt
and
/lib/firmware/rtlwifi

Stuff that has you rtlxxxx code in it, from the more or less corresponding firmware-realtek/rtl_bt and rtlwifi directories.
 
  • Like
Reactions: SamirD
You must log in or register to reply here.
Top Bottom