[Bug 1217417] New: Realtek RTL-8126 Network Driver
https://bugzilla.suse.com/show_bug.cgi?id=1217417 Bug ID: 1217417 Summary: Realtek RTL-8126 Network Driver Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Kernel:Drivers Assignee: kernel-bugs@suse.de Reporter: jmscdba@gmail.com QA Contact: qa-bugs@suse.de Target Milestone: --- Found By: --- Blocker: --- Yesterday I built a new PC using the Asus z790 Maximus Formula motherboard. The z790 Formula uses the Realtek 8126 PCIe 5 G/bps WIRED ethernet adapter. I installed TW 20231120 on it. Overall seems to be working, however, there does not seem to be a driver for the Realtek 8126. lspci | grep net 05:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. Device 8126 (rev 01) So it is detects the 8126 just fine it just doesn't have a driver for it. I checked realtek.com and found https://www.realtek.com/en/component/zoo/category/network-interface-controll... It looks like the download still says 8125, but I compiled the source and then since I have Secure boot enabled, I signed the resulting module file. After that the driver loaded and I now have wired networking and have not noticed any issues so far. Can we please get this driver added to TW ? Thank you very much ! -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1217417 https://bugzilla.suse.com/show_bug.cgi?id=1217417#c4 --- Comment #4 from Joe S <jmscdba@gmail.com> --- (In reply to Stephan Hemeier from comment #2)
Post: /sbin/lspci -nnk | grep -i net
So the ID and maybe driver is shown.
Hi Stephan, TW does not have a driver for the Realtek 8126 network adapter. The link I mentioned above is what I found on their website which looks like it was originally for the 8125. Here is the information you requested, however, keep in mind that it is after I downloaded and compiled the driver from that link and then signed it since I use secure boot. Here's he lspci --nk | grep -i net results 04:00.0 Network controller [0280]: Intel Corporation Device [8086:272b] (rev 1a) 05:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. Device [10ec:8126] (rev 01) Holler if you need anything else, THANK YOU! -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1217417 https://bugzilla.suse.com/show_bug.cgi?id=1217417#c3 --- Comment #3 from Joe S <jmscdba@gmail.com> --- (In reply to Takashi Iwai from comment #1)
You can check OBS hardware repo and look for already existing packages. If there is not there, try to create your own one (at first in your home project, and later submit to OBS hardware project). It shouldn't be too difficult.
Thanks for the pointer Takashi. I just checked that repo and I do not see any realtek drivers for the 8125 ( prior version ) or the 8126 ( version I have ). Compiling the module and then signing it works ( which is what I have done ), but I have not idea how to use OBS or to create a project there as you mentioned. It is probably above my pay grade :-) at least right now which is why I provided the link to the driver and have confirmed that it does in fact work so hoping that someone can get it included into TW for me. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1217417 https://bugzilla.suse.com/show_bug.cgi?id=1217417#c6 --- Comment #6 from Joe S <jmscdba@gmail.com> --- (In reply to Stephan Hemeier from comment #5)
My /sbin/lspci -nnk | grep -i net is not the same as your lspci --nk | grep -i net
So next time a little more carefully.
My apologies, I am sorry for the mistake and for the delay in responding, I had a friend pass away a few days ago and then last night my aunt passed away :-( so my mind is not focusing very well at the moment. Here is the output you request BUT, keep in mind that it is AFTER I compiled the driver from the realtek.com link I provided and AFTER, I signed the module so that the kernel would load it ( and imported the key with mokutil ) /sbin/lspci -nnk | grep -i net 04:00.0 Network controller [0280]: Intel Corporation Device [8086:272b] (rev 1a) 05:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. Device [10ec:8126] (rev 01)
I have installed r8125 from my hardware Repo and get: modprobeid 10ec:8126 Kernelmodulname r8125 filename: /lib/modules/5.14.21-150500.55.36-default/weak-updates/updates/r8125.ko.xz version: 9.012.03-NAPI license: GPL description: Realtek r8125 Ethernet controller driver author: Realtek and the Linux r8125 crew <netdev@vger.kernel.org> suserelease: SLE15-SP5 srcversion: 353F27D464BEFD974319666 alias: pci:v000010ECd00005000sv*sd*bc*sc*i* alias: pci:v000010ECd00008126sv*sd*bc*sc*i* alias: pci:v000010ECd00003000sv*sd*bc*sc*i* alias: pci:v000010ECd00008162sv*sd*bc*sc*i* alias: pci:v000010ECd00008125sv*sd*bc*sc*i* So the driver is r8125, you can get it:
https://download.opensuse.org/repositories/home:/Sauerland:/hardware/ openSUSE_Tumbleweed/
You have to install the kmp, ueficert and blacklist rpm.
I may be misunderstanding but it seems that you compiled the driver and made it available, but I already did that and have it working. My request was for the driver to make it to the TW repos so that it is automatically updated when I do zypper dup and so that I don't have to worry about compiling and signing when new kernel versions come out. Does that make sense ? Am I missing something from your reply ? Thanks for your patience during these challenging family times. Joe -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1217417 https://bugzilla.suse.com/show_bug.cgi?id=1217417#c8 --- Comment #8 from Joe S <jmscdba@gmail.com> --- (In reply to Stephan Hemeier from comment #7)
My request was for the driver to make it to the TW repos so that it is >automatically updated when I do zypper dup and so that I don't have to worry >about compiling and signing when new kernel versions come out.
Does that make sense ?
Maybe into the hardware Repo, but not directly to Tumbleweed........
Sorry I don't understand. Are you saying it will be in the HW repo but it will NEVER appear in TW during a new install ? When I installed I had to do an offline install since I didn't have a network connection because there was no 8125/8126 driver. After the install was done I had to setup wifi so that I could install gcc and kernel-devel so that I could compile the drivers. I must be misunderstanding you because I would be shocked if the latest driver for the new 5G wired network card would not eventually be included. Please help me understand better. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1217417 https://bugzilla.suse.com/show_bug.cgi?id=1217417#c10 --- Comment #10 from Joe S <jmscdba@gmail.com> --- (In reply to Stephan Hemeier from comment #9)
But not with your ID 8126......
So I do not know, if your ID will be backported to r8169 module , but I do not think, that any r8125.rpm will be shipped with original Tumbleweed or Leap.
That can only be done by serving an r8125 in the hardware Repo. Also I don't know if we have to blacklist the r8169 from kernel, because that supports more hardware.
But Takashi Iwai can say more to these problems.
This is REALLY new HW and it is the first motherboard I found that had the 8126. I purposely avoid the 2.5G wired networking because I found so many issues googling around with motherboards from all different vendors. Most motherboards seem to still have the 8125 even realtek.com just points you to the 8125 driver. So if I understand you correctly, the 8169 module would probably work since it supports the 8125 ( which is the driver I'm using ) it is just not currently recognizing that ID and someone would need to backport that id to the r8169 module. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1217417 https://bugzilla.suse.com/show_bug.cgi?id=1217417#c12 --- Comment #12 from Joe S <jmscdba@gmail.com> --- (In reply to Takashi Iwai from comment #11)
You can try to add the new entry for 8126 via sysfs and let r8169 driver binding with it without compilation. https://docs.kernel.org/PCI/pci.html?highlight=new_id
e.g. try to write like echo -n "10ec 8126 ffff ffff 0 0 0" > /sys/bus/pci/drivers/r8169/new_id echo -n "0000:05:00.0" > /sys/bus/pci/drivers/r8169/bind
Ok, I tried what you suggested above. First I load the module and verified it loaded: lsmod | grep r8169 modprobe r8169 lsmod | grep r8169 r8169 114688 0 mdio_devres 12288 1 r8169 libphy 245760 3 r8169,mdio_devres,realtek Your 1st echo does not report any issues echo -n "10ec 8126 ffff ffff 0 0 0" > /sys/bus/pci/drivers/r8169/new_id Your 2nd echo fails echo -n "0000:05:00.0" > /sys/bus/pci/drivers/r8169/bind -bash: echo: write error: No such device What am I doing wrong ? -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠suse.com