Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.kernel > #72738 > unrolled thread

Bug#992886: r8169: no dedicated PHY driver found for PHY ID 0xc1071002

Back to article view | Back to linux.debian.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Bug#992886: r8169: no dedicated PHY driver found for PHY ID 0xc1071002 Heiner Kallweit <heiner.kallweit@web.de> - 2021-08-25 08:10 +0200
    Bug#992886: r8169: no dedicated PHY driver found for PHY ID 0xc1071002 Roger Lynn <Roger@rilynn.me.uk> - 2021-09-02 00:40 +0200
      Bug#992886: r8169: no dedicated PHY driver found for PHY ID 0xc1071002 Roger Lynn <Roger@rilynn.me.uk> - 2021-09-08 13:00 +0200

#72738 — 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.

[toc] | [next] | [standalone]

#72783

On Wed, 25 Aug 2021 08:07:48 +0200 Heiner Kallweit <heiner.kallweit@web.de> 
wrote:
> 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.

In https://bugzilla.kernel.org/show_bug.cgi?id=207203 it was suggested to 
enable the boot ROM in the BIOS and/or reinsert the r8169 kernel module. 
Neither of these worked for me. Fortunately the r8168-dkms package does 
work. Thank you for the suggestion, as I was not aware of this driver.

Roger

[toc] | [prev] | [next] | [standalone]

#72847

On 05/09/2021 09:07, Salvatore Bonaccorso wrote:
> On Wed, Sep 01, 2021 at 10:59:19PM +0100, Roger Lynn wrote:
>> On Wed, 25 Aug 2021 08:07:48 +0200 Heiner Kallweit <heiner.kallweit@web.de>
>> wrote:
>> > 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.
>> 
>> In https://bugzilla.kernel.org/show_bug.cgi?id=207203 it was suggested to
>> enable the boot ROM in the BIOS and/or reinsert the r8169 kernel module.
>> Neither of these worked for me. Fortunately the r8168-dkms package does
>> work. Thank you for the suggestion, as I was not aware of this driver.
> 
> According to the discussion, there is not something to patch on the
> kernel side and rather likely a BIOS bug. So closing the bug.

The r8168-dkms package asks for bugs to be filed when it works but the 
in-kernel driver doesn't. I guess this bug already counts for that.

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.kernel

csiph-web