Bug#1143994: general: Ethernet driver r8169 is used for RTL8125 chipset by default and disconnects intermittently

Nathan H <[email protected]>
Newsgroups gmane.linux.debian.devel.general
Message-ID <178628564903.5985.14849506142240328082.reportbug__2188.43589989177$1786285772$gmane$org@DGdesk500.home>
Package: general
Severity: important
X-Debbugs-Cc: [email protected]

Dear Maintainer,

I am using Debian Testing on my desktop PC, which uses a Realtek ethernet chipset. 
My internet connection would regularly disconnect (usually for a minute or less, sometimes it stayed disconnected until I restarted my computer). 

I ran the following command and found the output said I was using a mis-matched kernel driver for my ethernet chip:

lspci -k | grep -A3 Ethernet
06:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8125 2.5GbE Controller (rev 05)
        Subsystem: Micro-Star International Co., Ltd. [MSI] Device 7d45
        Kernel driver in use: r8169
        Kernel modules: r8169

r8169 I assume is used to cover a number of chipsets. But mine was 8125, and it did not like it. 

I switched ethernet drivers using this package:
r8125-dkms/testing,testing,now 9.016.01-1 all [installed]

After installing that package I no longer had issues with my ethernet. I believe this chipset should be set to use the 8125 driver by default, to prevent this.

An additional note about my troubleshooting that may not be relevant: I did some wrong troubleshooting steps before installing that package (thanks AI) so I ended up blacklisting my previous driver r8169, to prevent it from loading in first. That was before I discovered that debian had a package with the driver conveniently available. I may still have that blacklist enabled, preventing 8169 from loading.


Thank you for your attention.
I'm sorry if I sent this to the wrong place, I wasn't sure what "package" my default kernel ethernet driuver would be.
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.