Hi,
First of all, thanks @Sauerland for providing easy to use Packages for the R8125 network interface.
I recently bought a ASUS Prime X870-P with the R8125 and I came across this thread while trying to get it work with Leap 15.6: The LAN connection is lost. Realtek RTL8125 2.5GbE driver is not loaded - #4 by raijar which help me get it working, to note one needs to disable secure boot, both in the BIOS/UEFI and in the Yast otherwise it does not work, I have no Idea why, but I also do not want to try to find out, most likely something with key signing.
My Question is, is there the possibility that these drivers will be included in Leap 16.0 or later?
Since there are Settings for Secure Boot in the BIOS and YAST I broke it down in to 4 Cases, thought 1, 2 and 3, 4 are the same and in all cases mokutil --list-new did not return something.
Case 1 & 2: BIOS: Secure Boot/OS Type: other OS Yast: Bootloader Secure boot checked or unchecked (did not change something) Network is working
>zypper se -si r8168 r8125 && mokutil --sb-state
Repository-Daten werden geladen...
Installierte Pakete werden gelesen...
S | Name | Type | Version | Arch | Repository
---+-----------------------+-------+-------------------------------------+--------+--------------------------------
i+ | r8125-blacklist-r8169 | Paket | 9.015.00-lp156.1.1 | x86_64 | Sauerland's Home Project (15.6)
i+ | r8125-kmp-default | Paket | 9.015.00_k6.4.0_150600.21-lp156.1.1 | x86_64 | Sauerland's Home Project (15.6)
i+ | r8125-ueficert | Paket | 9.015.00-lp156.1.1 | x86_64 | Sauerland's Home Project (15.6)
SecureBoot disabled
>mokutil --list-new
Case 3 & 4: BIOS: Secure Boot/OS Type: other OS Yast: Bootloader Secure boot checked or unchecked (did not change something) Network is NOT working
>zypper se -si r8168 r8125 && mokutil --sb-state
Repository-Daten werden geladen...
Installierte Pakete werden gelesen...
S | Name | Type | Version | Arch | Repository
---+-----------------------+-------+-------------------------------------+--------+--------------------------------
i+ | r8125-blacklist-r8169 | Paket | 9.015.00-lp156.1.1 | x86_64 | Sauerland's Home Project (15.6)
i+ | r8125-kmp-default | Paket | 9.015.00_k6.4.0_150600.21-lp156.1.1 | x86_64 | Sauerland's Home Project (15.6)
i+ | r8125-ueficert | Paket | 9.015.00-lp156.1.1 | x86_64 | Sauerland's Home Project (15.6)
SecureBoot enabled
>mokutil --list-new
@Sauerland, you mentioned that the Leap 16.0 r8169 driver would support the RTL8125 chip, just as Tumbleweed’s r8169 driver does. (And thank you very much for maintaining the r8125 driver for 15.6 – this post got my network working under 15.6.) I have created a 16.0 Network installation USB key, but the driver on it does not support the chip. When I rmmod r8169 and them modprobe r8169, I receive an error that contains r8169 0000:84:00.0: error -ENODEV: unknown chip XID 688, contact r8169 maintainers (see MAINTAINERS file). I also see in what I think is your personal repository for 16.0 that there are no r8125 packages. Before I start trying different things to get networking going for installation of 16.0, do you have any advice on how to proceed? And, should I post a bug report? Thanks in advance for your advice.
Try my Repo, it is easy to install and also deinstall the driver.
But you should know:
r8169 is a mutlti driver for rtl8168, rtl8125, rtl 8126, rtl 8136 and Chips more.
If you want to use r8125 you must blyklist the r8169 driver by mit blacklist file.
So the above Chips are not working anymore, you hav to install the appropriate package from my Repo.
Thank you once again, @Sauerland! You pointed me to your correct repository. I downloaded the r8125 packages (driver, blacklist, and certificate) while my PC was running Tumbleweed and was able to get networking working under the Leap 16 installation thumb drive. I may write up the steps I took to achive that.
In response to your statement about the r8169 driver, I do understand that it supports several chips. I am still not sure why the driver works perfectly when my PC is running Tumbleweed, but not when it runs Leap 15.6 or the 16.0 installation media (my PC multi-boots). There is obviously some difference between these distributions. I only mentioned your r8125 driver because I know it works for me. My preference is to use the most recent, up-to-date driver that works for my motherboard’s network chip (and RTL8125), whatever version that is.
And, at your suggestion in your subsequent post, I’ll take a look at the Fedora discussion and probably file a bug report with openSUSE’s bugzilla.
Again, much thanks for all you do and for helping me to proceed with my installation.
Thank you, @Sauerland. I have reported this on openSUSE’s bugzilla (https://bugzilla.opensuse.org/show_bug.cgi?id=1251973) and have informed the r8169 maintainers.
@Sauerland, I have a question about your repositories. On 15.6, I’ve been using the URL https://download.opensuse.org/repositories/home:/Sauerland/15.6/, gotten from software.opensuse.org. But I see another repository at https://download.opensuse.org/repositories/home:/Sauerland:/hardware/openSUSE_Leap_15.6/. Both have r8125 drivers, but they have (minor?) differences in the package versions. For just your r8125 drivers, is one repository better than the other, or does it not really matter? Thanks in advance for your reply.
Please do not use https://download.opensuse.org/repositories/home:/Sauerland
This can break your system.
Therefor I added the hardware Repo only with drivers, which will be branched automatically if I upload a newer Version to my /home Repo: https://download.opensuse.org/repositories/home:/Sauerland:/hardware/
Also my graphics repo and so on.
They are build from my /home Repo, have the same Version but different Release Versions.
Thank you, @Sauerland, for clarifying the difference between the repositories. I don’t like broken systems – I have changed to your preferred repository. Thanks for maintaining it.
This thread isn’t too old to ask why these newer drivers aren’t in the Tumbleweed kernel, seeing as rtl8126 is detected for the most part but is seriously buggy, and only your driver repo seems to fix it. And I don’t think rtl8127 is in the kernel at all.