Kernel r8169 driver is broken.

I do have a fix for it, BUT it needs kernel module to be compiled by someone.

Then a reload cycle for the module is needed.

See https://lja.fi/lja/wordpress/index.php/linux-kernel-r8169-network-driver-fixup/ for patch.

Comments

  • malcolmlewismalcolmlewis Knowledge Partner

    @Lauri Hi and welcome to the Forum :)
    Sometimes it can be a conflict between 8168 and 8169 driver can you provide info in the card;

    /sbin/lspci -nnk | egrep -A3 "Net|Eth"
    
  • edited March 30
    00:1f.6 Ethernet controller [0200]: Intel Corporation Ethernet Connection (10) I219-V [8086:0d4f]
            DeviceName:  LAN
            Subsystem: Intel Corporation Ethernet Connection (10) I219-V [8086:2081]
            Kernel driver in use: e1000e
            Kernel modules: e1000e
    01:00.0 Non-Volatile memory controller [0108]: Intel Corporation Device [8086:faf0] (rev 03)
    

    The patch I provided makes the driver work, when reloaded.

  • Wrong NIC info

  • edited March 30

    lspci -nnk | egrep -A3 "Net|Eth":
    02:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 03)
    Subsystem: Gigabyte Technology Co., Ltd Onboard Ethernet [1458:e000]
    Kernel driver in use: r8169
    Kernel modules: r8169
    03:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 03)
    Subsystem: Gigabyte Technology Co., Ltd Onboard Ethernet [1458:e000]
    Kernel driver in use: r8169
    Kernel modules: r8169
    04:00.0 SATA controller [0106]: JMicron Technology Corp. JMB363 SATA/IDE Controller [197b:2363] (rev 02)

    When reloading:
    [ 191.108877] libphy: r8169: probed
    [ 191.108882] r8169 0000:02:00.0: HW found: 0x001cc912
    [ 191.109309] r8169 0000:02:00.0 eth0: RTL8168d/8111d, 00:24:1d:12:e6:4a, XID 281, IRQ 28
    [ 191.109313] r8169 0000:02:00.0 eth0: jumbo features [frames: 9194 bytes, tx checksumming: ko]
    [ 191.110824] r8169 0000:03:00.0: can't disable ASPM; OS doesn't have ASPM control
    [ 191.111164] r8169 0000:02:00.0 enp2s0: renamed from eth0
    [ 191.116365] libphy: r8169: probed
    [ 191.116370] r8169 0000:03:00.0: HW found: 0x001cc912
    [ 191.125381] r8169 0000:03:00.0 eth0: RTL8168d/8111d, 00:24:1d:12:e6:1a, XID 281, IRQ 29
    [ 191.125389] r8169 0000:03:00.0 eth0: jumbo features [frames: 9194 bytes, tx checksumming: ko]
    [ 191.129915] r8169 0000:03:00.0 enp3s0: renamed from eth0
    [ 191.163114] RTL8211B Gigabit Ethernet r8169-200:00: attached PHY driver (mii_bus:phy_addr=r8169-200:00, irq=IGNORE)
    [ 191.329540] RTL8211B Gigabit Ethernet r8169-300:00: attached PHY driver (mii_bus:phy_addr=r8169-300:00, irq=IGNORE)
    [ 191.329633] r8169 0000:02:00.0 enp2s0: Link is Down
    [ 191.497110] r8169 0000:03:00.0 enp3s0: Link is Down
    [ 194.319837] r8169 0000:03:00.0 enp3s0: Link is Up - 1Gbps/Full - flow control rx/tx
    [ 194.319855] IPv6: ADDRCONF(NETDEV_CHANGE): enp3s0: link becomes ready

  • malcolmlewismalcolmlewis Knowledge Partner

    @Lauri Hi and what release of SLED and kernel is in use?

    cat /etc/os-release
    uname -a
    
  • Latest desktop release, the bug is not linux-installation specific.

  • malcolmlewismalcolmlewis Knowledge Partner

    @Lauri Hi, then will be very hard to fix AND ensure the system is supported, performing your patch will void any support, it would be better to raise a support request to get a supported fix.

Sign In or Register to comment.