| Summary: | realtek RTL8125 2.5gigabit ethernet card - fresh install | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | jeff deifik <jeff> |
| Component: | Installer | Assignee: | Mageia Bug Squad <bugsquad> |
| Status: | RESOLVED WORKSFORME | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | CC: | anaselli, mageia, ouaurelien |
| Version: | 7 | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | unknown | CVE: | |
| Status comment: | |||
| Attachments: |
lspci -v output
log of journalctl log of update |
||
Created attachment 11976 [details]
lspci -v output
jeff deifik
2020-11-04 19:14:16 CET
Attachment 11976 description:
lsmod output =>
lspci -v output Hi, thanks for reporting this. (In reply to jeff deifik from comment #0) > Description of problem: > I installed a realtek 2.5gig ethernet card in an existing mageia 7 computer. > It worked fine. > I did a fresh install of mageia 7, and the 2.5 gig ethernet card doesn't work As far as I understand, your 2.5G Ethernet runs well on an already installed M7 system. But, if you reinstall M7, this card is no longer see as a Realtek RTL8125 2.5G. When I see "ifconfig" output above: - enp6s0 is 1G intel one. - enp7s0 is also a 1G intel... But lspci -v correctly see RTL8125 2.5G: 01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8125 2.5GbE Controller Subsystem: Realtek Semiconductor Co., Ltd. Device 0123 Flags: bus master, fast devsel, latency 0, IRQ 11, NUMA node 0 I/O ports at c800 [size=256] Memory at fbbf0000 (64-bit, non-prefetchable) [size=64K] Memory at fbbdc000 (64-bit, non-prefetchable) [size=16K] Expansion ROM at fbbe0000 [disabled] [size=64K] Capabilities: [40] Power Management version 3 Capabilities: [50] MSI: Enable- Count=1/1 Maskable+ 64bit+ Capabilities: [70] Express Endpoint, MSI 01 Capabilities: [b0] MSI-X: Enable- Count=4 Masked- Capabilities: [d0] Vital Product Data Capabilities: [100] Advanced Error Reporting Capabilities: [148] Virtual Channel Capabilities: [168] Device Serial Number 01-00-00-00-68-4c-e0-00 Capabilities: [178] Alternative Routing-ID Interpretation (ARI) Capabilities: [188] Single Root I/O Virtualization (SR-IOV) Capabilities: [1c8] Transaction Processing Hints Capabilities: [254] Latency Tolerance Reporting Capabilities: [25c] L1 PM Substates Capabilities: [26c] Vendor Specific Information: ID=0002 Rev=4 Len=100 Can you correct me if I'm wrong? Suggestion: - Update all packages (urpmi --auto-update) - Reboot - Under Mageia Control Center, run Network Configuration to verify if their are connections available. Please report here. CC:
(none) =>
ouaurelien
Aurelien Oudelet
2020-11-05 09:18:32 CET
Keywords:
(none) =>
NEEDINFO The same computer had the 2.5gig networking card working previously. I added a graphics card, and reinstalled mageia 7 from scratch, and the 2.5 gig card stopped working. I had already updated all packages, but I did it again with no change. I rebooted. Network Configuration sees the card, but has the same error message of "Unable to find network interface for detected device running r8169 driver)." Looking at the lspci -v on the internet usually shows a kernel driver loaded for the network card, but the mageia 7 output doesn't show a kernel driver loaded. I don't know if this is significant. ifconfig still does not show the 2.5 gig network card. Dual booting the machine to windows 10, the 2.5 gig network card is detected and works. the latest version of knoppix doesn't detect the 2.5 gig network card based on ifconfig output. the kernel of mageia 7 that I am using is 5.1.14-desktop-1.mga7 (In reply to jeff deifik from comment #4) > the kernel of mageia 7 that I am using is 5.1.14-desktop-1.mga7 That is the kernel version on the installer ISOs. If you have successfully updated your system, you should be using 5.7.19-desktop-3.mga7. CC:
(none) =>
mageia I tried running uprmi again: [root@localhost ~]# uname -a Linux localhost 5.1.14-desktop-1.mga7 #1 SMP Sat Jun 22 10:35:14 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux [root@localhost ~]# [root@localhost ~]# urpmi --auto-update medium "Core Release (distrib1)" is up-to-date medium "Core Updates (distrib3)" is up-to-date medium "Nonfree Release (distrib11)" is up-to-date medium "Nonfree Updates (distrib13)" is up-to-date medium "Core Release (distrib46)" is up-to-date medium "Core Updates (distrib48)" is up-to-date medium "Nonfree Release (distrib56)" is up-to-date medium "Nonfree Updates (distrib58)" is up-to-date Packages are up to date What does ls -l /boot show? s -l /boot total 46156 -rw-r--r-- 1 root root 218186 Jun 22 2019 config-5.1.14-desktop-1.mga7 -rw-r--r-- 1 root root 236770 Aug 27 15:28 config-5.7.19-desktop-1.mga7 -rw-r--r-- 1 root root 236770 Oct 18 09:20 config-5.7.19-desktop-3.mga7 drwxr-xr-x 2 root root 4096 Mar 26 2019 dracut/ drwxr-xr-x 6 root root 4096 Nov 3 21:58 grub2/ -rw------- 1 root root 13247978 Nov 4 06:15 initrd-5.1.14-desktop-1.mga7.img lrwxrwxrwx 1 root root 32 Nov 3 21:49 initrd.img -> initrd-5.1.14-desktop-1.mga7.img -rw-r--r-- 1 root root 186052 Jun 22 2019 symvers-5.1.14-desktop-1.mga7.xz -rw-r--r-- 1 root root 195324 Aug 27 15:28 symvers-5.7.19-desktop-1.mga7.xz -rw-r--r-- 1 root root 195324 Oct 18 09:20 symvers-5.7.19-desktop-3.mga7.xz -rw-r--r-- 1 root root 3978900 Jun 22 2019 System.map-5.1.14-desktop-1.mga7 -rw-r--r-- 1 root root 4755771 Aug 27 15:28 System.map-5.7.19-desktop-1.mga7 -rw-r--r-- 1 root root 4755463 Oct 18 09:20 System.map-5.7.19-desktop-3.mga7 lrwxrwxrwx 1 root root 29 Nov 3 21:49 vmlinuz -> vmlinuz-5.1.14-desktop-1.mga7 -rw-r--r-- 1 root root 6252928 Jun 22 2019 vmlinuz-5.1.14-desktop-1.mga7 -rw-r--r-- 1 root root 6486112 Aug 27 15:28 vmlinuz-5.7.19-desktop-1.mga7 -rw-r--r-- 1 root root 6483264 Oct 18 09:20 vmlinuz-5.7.19-desktop-3.mga7 [root@localhost ~]# That is odd. When I boot using grub, I just select 'mageia' There are the usual options, mageia, mageia recovery (paraphrasing), and windows. (In reply to jeff deifik from comment #8) > That is odd. When I boot using grub, I just select 'mageia' There are the > usual options, mageia, mageia recovery (paraphrasing), and windows. That sounds like you are using legacy grub, not grub2, but you don't have a legacy grub configuration in /boot. It doesn't look like your kernel updates completed successfully, as the vmlinuz and initrd.img symlinks still point to 5.1.14, and there are no initrd images for the newer kernels. Try reinstalling the latest kernel and look for error messages, both in the terminal window and in the system log. I did a completely fresh install, starting with an unpartitioned hard drive. The system is a non UEFI BIOS system. The motherboard is a supermicro x8dtl. I will try reinstalling the latest kernel. I would appreciate advice on the commands to do that, as I usually use the mageia control center and 'update your system'. [root@localhost ~]# urpme kernel-desktop-latest-5.7.19-3.mga7
removing kernel-desktop-latest-5.7.19-3.mga7.x86_64
removing package kernel-desktop-latest-5.7.19-3.mga7.x86_64
1/1: removing kernel-desktop-latest-5.7.19-3.mga7.x86_64
#######################################################
[root@localhost ~]# urpmi kernel-desktop-latest-5.7.19-3.mga7
$MIRRORLIST: media/core/updates/kernel-desktop-latest-5.7.19-3.mga7.x86_64.rpm
installing kernel-desktop-latest-5.7.19-3.mga7.x86_64.rpm from /var/cache/urpmi/rpms
Preparing... #######################################################
1/1: kernel-desktop-latest #######################################################
[root@localhost ~]# ls -l /boot
total 46156
-rw-r--r-- 1 root root 218186 Jun 22 2019 config-5.1.14-desktop-1.mga7
-rw-r--r-- 1 root root 236770 Aug 27 15:28 config-5.7.19-desktop-1.mga7
-rw-r--r-- 1 root root 236770 Oct 18 09:20 config-5.7.19-desktop-3.mga7
drwxr-xr-x 2 root root 4096 Mar 26 2019 dracut/
drwxr-xr-x 6 root root 4096 Nov 3 21:58 grub2/
-rw------- 1 root root 13247978 Nov 4 06:15 initrd-5.1.14-desktop-1.mga7.img
lrwxrwxrwx 1 root root 32 Nov 3 21:49 initrd.img -> initrd-5.1.14-desktop-1.mga7.img
-rw-r--r-- 1 root root 186052 Jun 22 2019 symvers-5.1.14-desktop-1.mga7.xz
-rw-r--r-- 1 root root 195324 Aug 27 15:28 symvers-5.7.19-desktop-1.mga7.xz
-rw-r--r-- 1 root root 195324 Oct 18 09:20 symvers-5.7.19-desktop-3.mga7.xz
-rw-r--r-- 1 root root 3978900 Jun 22 2019 System.map-5.1.14-desktop-1.mga7
-rw-r--r-- 1 root root 4755771 Aug 27 15:28 System.map-5.7.19-desktop-1.mga7
-rw-r--r-- 1 root root 4755463 Oct 18 09:20 System.map-5.7.19-desktop-3.mga7
lrwxrwxrwx 1 root root 29 Nov 3 21:49 vmlinuz -> vmlinuz-5.1.14-desktop-1.mga7
-rw-r--r-- 1 root root 6252928 Jun 22 2019 vmlinuz-5.1.14-desktop-1.mga7
-rw-r--r-- 1 root root 6486112 Aug 27 15:28 vmlinuz-5.7.19-desktop-1.mga7
-rw-r--r-- 1 root root 6483264 Oct 18 09:20 vmlinuz-5.7.19-desktop-3.mga7
Looks like boot is still pointing to 5.1.
Please advise.
That only removed the kernel-desktop-latest meta-package, not the actual kernel package. In one terminal window, as root run journalctl -f In a second terminal window, as root run urpme kernel-desktop-5.7.19-3.mga7-1-1.mga7 which should also remove kernel-desktop-latest. Then run urpmi kernel-desktop-latest Save the output from both terminal windows. Created attachment 11977 [details]
log of journalctl
Created attachment 11978 [details]
log of update
I added files which are from 'script' from journalctl and doing the update. ls -l /boot still shows the current kernel as 5.1 the message about /dev/sdb is because I have a 4 disk mdadm raid array. I reported a bug about some tools getting confused by a mdadm raid array. I can pull the drives if needed, because they are in hot swap trays. I pulled the raid array drives and did it again:
urpme kernel-desktop-5.7.19-3.mga7-1-1.mga7
To satisfy dependencies, the following 2 packages will be removed (70MB):
kernel-desktop-5.7.19-3.mga7-1-1.mga7.x86_64
kernel-desktop-latest-5.7.19-3.mga7.x86_64
(due to missing kernel-desktop-5.7.19-3.mga7)
Remove 2 packages? (y/N) y
removing kernel-desktop-5.7.19-3.mga7-1-1.mga7.x86_64 kernel-desktop-latest-5.7.19-3.mga7.x86_64
removing package kernel-desktop-5.7.19-3.mga7-1-1.mga7.x86_64
1/2: removing kernel-desktop-5.7.19-3.mga7-1-1.mga7.x86_64
##########################################
removing package kernel-desktop-latest-5.7.19-3.mga7.x86_64
2/2: removing kernel-desktop-latest-5.7.19-3.mga7.x86_64
##########################################
[root@localhost text]# urpmi kernel-desktop-latest
To satisfy dependencies, the following packages are going to be installed:
Package Version Release Arch
(medium "Core Updates (distrib3)")
kernel-desktop-5.7.19-3.mga7 1 1.mga7 x86_64
kernel-desktop-latest 5.7.19 3.mga7 x86_64
70MB of additional disk space will be used.
62MB of packages will be retrieved.
Proceed with the installation of the 2 packages? (Y/n) y
$MIRRORLIST: media/core/updates/kernel-desktop-latest-5.7.19-3.mga7.x86_64.rpm
$MIRRORLIST: media/core/updates/kernel-desktop-5.7.19-3.mga7-1-1.mga7.x86_64.rpm
installing kernel-desktop-5.7.19-3.mga7-1-1.mga7.x86_64.rpm kernel-desktop-latest-5.7.19-3.mga7.x86_64.rpm from /var/cache/urpmi/rpms
Preparing... ##########################################
1/2: kernel-desktop-latest ##########################################
2/2: kernel-desktop-5.7.19-3.mga7
##########################################
Creating: target|kernel|dracut args|basicmodules
remove-boot-splash: Format of /boot/initrd-5.7.19-desktop-3.mga7.img not recognized
You should restart your computer for kernel-desktop-5.7.19-3.mga7
/boot looks ok now:
ls -l /boot
total 60212
-rw-r--r-- 1 root root 218186 Jun 22 2019 config-5.1.14-desktop-1.mga7
-rw-r--r-- 1 root root 236770 Aug 27 15:28 config-5.7.19-desktop-1.mga7
-rw-r--r-- 1 root root 236770 Oct 18 09:20 config-5.7.19-desktop-3.mga7
drwxr-xr-x 2 root root 4096 Mar 26 2019 dracut/
drwxr-xr-x 6 root root 4096 Nov 5 08:06 grub2/
-rw------- 1 root root 13247978 Nov 4 06:15 initrd-5.1.14-desktop-1.mga7.img
-rw------- 1 root root 14390205 Nov 5 08:06 initrd-5.7.19-desktop-3.mga7.img
lrwxrwxrwx 1 root root 32 Nov 5 08:06 initrd-desktop.img -> initrd-5.7.19-desktop-3.mga7.img
lrwxrwxrwx 1 root root 32 Nov 5 08:06 initrd.img -> initrd-5.7.19-desktop-3.mga7.img
-rw-r--r-- 1 root root 186052 Jun 22 2019 symvers-5.1.14-desktop-1.mga7.xz
-rw-r--r-- 1 root root 195324 Aug 27 15:28 symvers-5.7.19-desktop-1.mga7.xz
-rw-r--r-- 1 root root 195324 Oct 18 09:20 symvers-5.7.19-desktop-3.mga7.xz
-rw-r--r-- 1 root root 3978900 Jun 22 2019 System.map-5.1.14-desktop-1.mga7
-rw-r--r-- 1 root root 4755771 Aug 27 15:28 System.map-5.7.19-desktop-1.mga7
-rw-r--r-- 1 root root 4755463 Oct 18 09:20 System.map-5.7.19-desktop-3.mga7
lrwxrwxrwx 1 root root 29 Nov 5 08:06 vmlinuz -> vmlinuz-5.7.19-desktop-3.mga7
-rw-r--r-- 1 root root 6252928 Jun 22 2019 vmlinuz-5.1.14-desktop-1.mga7
-rw-r--r-- 1 root root 6486112 Aug 27 15:28 vmlinuz-5.7.19-desktop-1.mga7
-rw-r--r-- 1 root root 6483264 Oct 18 09:20 vmlinuz-5.7.19-desktop-3.mga7
lrwxrwxrwx 1 root root 29 Nov 5 08:06 vmlinuz-desktop -> vmlinuz-5.7.19-desktop-3.mga7
Looks like I ran into another issue related to mdadm arrays.
The realtek 2.5gig ethernet card is now configurable via the network devices applet and it shows up with /sbin/ifconfig :-) So: (In reply to jeff deifik from comment #17) > The realtek 2.5gig ethernet card is now configurable via the network devices > applet and it shows up with /sbin/ifconfig :-) This works with updated 5.7.19-3.mga7 Kernel. Closing this. (In reply to jeff deifik from comment #16) > I pulled the raid array drives and did it again: > Looks like I ran into another issue related to mdadm arrays. Please report with an other bug report this. Resolution:
(none) =>
FIXED No update done on our side. Resolution:
FIXED =>
WORKSFORME There is still the issue of the kernel update not fixing the links on /boot when there is a raid array. That seems like a significant bug. Resolution:
WORKSFORME =>
FIXED
jeff deifik
2020-11-07 17:05:39 CET
Resolution:
FIXED =>
(none) No, you can't reopen this bug report as it is WORKSFORME for this installation and the issue is solved by "urpmi --auto-update" and booting to latest Kernel on M7. BUT: as I previously mentioned, I invited you to open a new bug about your RAID array that seems to conflicts with the Kernel update procedure. So, I open it for you at https://bugs.mageia.org/show_bug.cgi?id=27582 Resolution:
(none) =>
WORKSFORME I think i've already opened one https://bugs.mageia.org/show_bug.cgi?id=27395 CC:
(none) =>
anaselli @Angelo, that's a different issue again. The RTL8125 card Jeff is using here works with the latest Mageia 7 kernel. I guess there are different variants of that device, and only some are supported. true, mine is the B one, though they should be supported by installed both :p (since it seems B should be supported by upstream kernel too looking through commits) by mga8/cauldron installer i meant |
Description of problem: I installed a realtek 2.5gig ethernet card in an existing mageia 7 computer. It worked fine. I did a fresh install of mageia 7, and the 2.5 gig ethernet card doesn't work Version-Release number of selected component (if applicable): How reproducible: 100% Steps to Reproduce: 1. do a fresh install 2. try to configure realtek network 3. error message When I go to the network center, I can see the 2 intel gigabit controllers. I also see the realtek 2.5 gigabit controller. when I click configure I get the error unable to find network interface for selected device (using r8169 driver) It does not show up on ifconfig. Here is ifconfig output enp6s0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500 ether 00:25:90:0d:aa:7c txqueuelen 1000 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 device interrupt 16 memory 0xfbde0000-fbe00000 enp7s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 192.168.xx.xx netmask 255.255.255.0 broadcast 192.168.xx.255 inet6 2605:e000:1527:e3:225:90ff:fe0d:aa7d prefixlen 64 scopeid 0x0<global> inet6 fe80::225:90ff:fe0d:aa7d prefixlen 64 scopeid 0x20<link> ether 00:25:90:0d:aa:7d txqueuelen 1000 (Ethernet) RX packets 342977757 bytes 518881576558 (483.2 GiB) RX errors 0 dropped 38 overruns 0 frame 0 TX packets 18799717 bytes 1398812682 (1.3 GiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 device interrupt 17 memory 0xfbee0000-fbf00000 lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536 inet 127.0.0.1 netmask 255.0.0.0 inet6 ::1 prefixlen 128 scopeid 0x10<host> loop txqueuelen 1000 (Local Loopback) RX packets 54 bytes 3316 (3.2 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 54 bytes 3316 (3.2 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 Networking is working with the intel gigabit, but I really want the 2.5 gigabit network to work. It does work under windows 10 (dual boot machine).