Bug#992886: r8169: no dedicated PHY driver found for PHY ID 0xc1071002
On Tue, 24 Aug 2021 17:02:06 +0100 Roger Lynn <roger@rilynn.me.uk> wrote:
> Package: src:linux
> Version: 5.10.46-4
> Severity: normal
> File: /lib/modules/5.10.0-8-amd64/kernel/drivers/net/ethernet/realtek/r8169.ko
>
> I've just upgraded this machine to Bullseye and it seems unable to load the
> ethernet driver:
>
> [ 6.548031] r8169 0000:02:00.0: can't disable ASPM; OS doesn't have ASPM control
> [ 6.566607] libphy: r8169: probed
> [ 6.566613] r8169 0000:02:00.0: no dedicated PHY driver found for PHY ID 0xc1071002, maybe realtek.ko needs to be added to initramfs?
> [ 6.590372] r8169: probe of 0000:02:00.0 failed with error -49
> [ 6.590412] r8169 0000:03:00.0: can't disable ASPM; OS doesn't have ASPM control
> [ 6.592984] libphy: r8169: probed
> [ 6.592987] r8169 0000:03:00.0: no dedicated PHY driver found for PHY ID 0xc1071002, maybe realtek.ko needs to be added to initramfs?
> [ 6.626342] r8169: probe of 0000:03:00.0 failed with error -49
>
> This is long after the filesystem has been mounted, so the initramfs should be
> irrelevant, but I tried adding the realtek and r8169 modules to the initramfs
> and the only difference was that the error was earlier in the boot sequence.
>
> The machine is 12 years old and has worked with every stable Debian release in
> that time. The old Buster kernel, 4.19.0-17-amd64, running with Bullseye
> reports:
>
> [ 10.604259] r8169 0000:02:00.0: can't disable ASPM; OS doesn't have ASPM control
> [ 10.616071] libphy: r8169: probed
> [ 10.616222] r8169 0000:02:00.0 eth0: RTL8168d/8111d, 00:24:1d:1e:99:33, XID 281000c0, IRQ 25
> [ 10.616223] r8169 0000:02:00.0 eth0: jumbo features [frames: 9200 bytes, tx checksumming: ko]
> [ 10.616921] r8169 0000:03:00.0: can't disable ASPM; OS doesn't have ASPM control
> [ 10.619251] libphy: r8169: probed
> [ 10.619384] r8169 0000:03:00.0 eth1: RTL8168d/8111d, 00:24:1d:1e:99:31, XID 281000c0, IRQ 26
> [ 10.619385] r8169 0000:03:00.0 eth1: jumbo features [frames: 9200 bytes, tx checksumming: ko]
> ...
> [ 17.134036] r8169 0000:02:00.0: firmware: direct-loading firmware rtl_nic/rtl8168d-1.fw
> [ 17.134559] Generic PHY r8169-200:00: attached PHY driver [Generic PHY] (mii_bus:phy_addr=r8169-200:00, irq=IGNORE)
> [ 17.285430] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
> [ 17.286173] Generic PHY r8169-300:00: attached PHY driver [Generic PHY] (mii_bus:phy_addr=r8169-300:00, irq=IGNORE)
> [ 17.437417] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
> [ 20.009162] r8169 0000:02:00.0 eth0: Link is Up - 100Mbps/Full - flow control rx/tx
> [ 20.009180] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
>
> Thanks,
>
> Roger
>
A number of Gigabyte boards from ~2009 have broken BIOS support, resulting in the PHY
reporting an invalid PHY ID. Realtek / Gigabyte don't release errata information,
therefore there's not much that can be done. In bugzilla.kernel.org you can find
workarounds that helped for some users, else use the r8168 driver.
Reply to: