Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.bugs.dist > #1069370
| From | Roger Lynn <Roger@rilynn.me.uk> |
|---|---|
| Newsgroups | linux.debian.bugs.dist, linux.debian.kernel |
| Subject | Bug#992886: r8169: no dedicated PHY driver found for PHY ID 0xc1071002 |
| Date | 2021-09-02 00:40 +0200 |
| Message-ID | <CSH3H-71N-1@gated-at.bofh.it> (permalink) |
| References | (1 earlier) <CPH9U-6J1-21@gated-at.bofh.it> <CPUgN-6xM-1@gated-at.bofh.it> <CPUgN-6xM-1@gated-at.bofh.it> <CPH9U-6J1-21@gated-at.bofh.it> <CPUgN-6xM-1@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
Cross-posted to 2 groups.
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
Back to linux.debian.bugs.dist | Previous | Next — Previous in thread | Find similar | Unroll thread
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
csiph-web