Bug 31947 - intel 1217-lm NIC - no connection with mageia 8, works with windows 10
Summary: intel 1217-lm NIC - no connection with mageia 8, works with windows 10
Status: NEW
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 8
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Kernel and Drivers maintainers
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-05-21 20:15 CEST by jeff deifik
Modified: 2023-06-01 21:12 CEST (History)
0 users

See Also:
Source RPM:
CVE:
Status comment:


Attachments
journalctl output (18.95 KB, application/octet-stream)
2023-05-31 21:34 CEST, jeff deifik
Details

Description jeff deifik 2023-05-21 20:15:03 CEST
Description of problem:

I am running mageia-8 x64 (non-uefi). It is fully patched as of may-21-2023.

I have a supermicro X10SLM-F motherboard with an intel e3-1270v3 processor and 16gb or ram. The mb has 2 intel nics built into it. I have added a realtek 2.5g nit card. All the nics are wired to a switch and work fine with windows 10.

The intel nics are the intel 1217-LM and the intel 1210.
The realtek nic is the rTL8125 2.5gbit.

The 1220 nic works great under windows and linux.
The 1217-lm is detected with mageia, but does not get a DHCP config. It works fine on windows 10.
I have network cables plugged into all the nics.

Here is what ifconfig reports:

eno1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 9014
       inet 192.168.47.151  netmask 255.255.255.0  broadcast 192.168.47.255
       inet6 fe80::225:90ff:fed8:df0a  prefixlen 64  scopeid 0x20<link>
       ether 00:25:90:d8:df:0a  txqueuelen 1000  (Ethernet)
       RX packets 23869651  bytes 36074885733 (33.5 GiB)
       RX errors 0  dropped 2  overruns 2  frame 0
       TX packets 2320297  bytes 130977943 (124.9 MiB)
       TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
       device memory 0xf7200000-f727ffff

eno2: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
       inet6 fe80::225:90ff:fed8:df0b  prefixlen 64  scopeid 0x20<link>
       ether 00:25:90:d8:df:0b  txqueuelen 1000  (Ethernet)
       RX packets 5846  bytes 436996 (426.7 KiB)
       RX errors 5  dropped 3  overruns 0  frame 5
       TX packets 55  bytes 4914 (4.7 KiB)
       TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
       device interrupt 20  memory 0xf7300000-f7320000

enp4s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 9014
       inet 10.10.10.150  netmask 255.0.0.0  broadcast 10.255.255.255
       inet6 fe80::28e:25ff:fe71:2f5  prefixlen 64  scopeid 0x20<link>
       ether 00:8e:25:71:02:f5  txqueuelen 1000  (Ethernet)
       RX packets 142971250  bytes 1247766730893 (1.1 TiB)
       RX errors 0  dropped 58292  overruns 0  frame 0
       TX packets 57769241  bytes 4164307235 (3.8 GiB)
       TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

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 424  bytes 47978 (46.8 KiB)
       RX errors 0  dropped 0  overruns 0  frame 0
       TX packets 424  bytes 47978 (46.8 KiB)
       TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0


Version-Release number of selected component (if applicable):


How reproducible: 100%


Steps to Reproduce:
1. boot mageia
2. no connectivity on the 1217-lm nic
3.
jeff deifik 2023-05-21 20:15:21 CEST

Summary: intel 1210 - no connection with mageia 8, works with windows 10 => intel 1210 NIC - no connection with mageia 8, works with windows 10

Comment 1 Lewis Smith 2023-05-21 21:10:56 CEST
Thank you for the report.
There is some confusion between the title and comment 0 about exactly which Intel device is not working. The title says "Intel 1210", the comment "Intel 1217-LM".

Can you say when this problem arose?
Has it always been the case, or has it shown since you added the realtek nic rTL8125?
Have the two onboard Intel controllers ever both worked?
Does the realtec device work OK?

To supplement the ifconfig output, please post that from:
 $ inxi -ni       [You may have to install inxi]
Its man page says "You should not paste your local WAN/IP".
Comment 2 jeff deifik 2023-05-21 21:55:41 CEST
I fixed the title.
I installed mageia-8 on the system yesterday.
I seem to recall that the 1217-lm worked before I ran all the updates, but I am not sure. I have had all the nics installed at all times.
The realtek device works great.

Here is the inxi -ni output:

inxi -ni
Network:
 Message: No Device data found.
 IF-ID-1: eno1 state: up speed: 1000 Mbps duplex: full
 mac: 00:25:90:d8:df:0a
 IP v4: 192.168.47.151/24 scope: global
 IP v6: fe80::225:90ff:fed8:df0a/64 scope: link
 IF-ID-2: eno2 state: up speed: 1000 Mbps duplex: full
 mac: 00:25:90:d8:df:0b
 IP v6: fe80::225:90ff:fed8:df0b/64 scope: link
 IF-ID-3: enp4s0 state: up speed: 2500 Mbps duplex: full
 mac: 00:8e:25:71:02:f5
 IP v4: 10.10.10.150/8 scope: global
 IP v6: fe80::28e:25ff:fe71:2f5/64 scope: link
 WAN IP: 75.85.182.170

Summary: intel 1210 NIC - no connection with mageia 8, works with windows 10 => intel 1217-lm NIC - no connection with mageia 8, works with windows 10

Comment 3 Lewis Smith 2023-05-30 21:47:11 CEST
Sorry to have left you.
"No Device data found" is not helpful. I was hoping to see the actual devices & associated drivers; e.g.
 $ inxi -N
Network:
  Device-1: Intel Gemini Lake PCH CNVi WiFi driver: iwlwifi
  Device-2: ASIX AX88179 Gigabit Ethernet type: USB driver: cdc_ncm
How is the intel 1217-lm connected?

"the 1217-lm worked before I ran all the updates, but I am not sure"
Surely you know whether it worked after installing Mageia 8. If you suspect a driver change, we need to know what that was originally, and is now.

CC: (none) => lewyssmith

Comment 4 jeff deifik 2023-05-30 22:11:37 CEST
When I spoke of updated, I meant updates after installing mageia-8.
This is new hardware for me. The network does work sometimes, but it isn't working right now. Fortunately, The motherboard has 2 intel NICs built into it.
I also have a realtek 2.5g nic pci-e card.

Right now, the intel networks are down.
# inxi -N
Network:   Message: No Device data found.

inxi -n
Network:   Message: No Device data found.
           IF-ID-1: eno1 state: down mac: 00:25:90:d8:df:0a
           IF-ID-2: eno2 state: up speed: 1000 Mbps duplex: full mac: 00:25:90:d8:df:0b
           IF-ID-3: enp4s0 state: up speed: 2500 Mbps duplex: full mac: 00:8e:25:71:02:f5

Sorry it doesn't say more.
Comment 5 Lewis Smith 2023-05-31 21:23:40 CEST
Thanks for the clarification about updates, comment 2.
I suppose we must see the system journal from a boot when at least one of the networks is down (better, like comment 2, both Intel ones).

Please do the following ASAP once you know the network situation:
 $ journalctl -b --no-hostname > journal.txt
 $ xz journal.txt
and attach to this bug the resulting compressed file 'journal.txt.xz'.
Comment 6 jeff deifik 2023-05-31 21:34:07 CEST
Created attachment 13860 [details]
journalctl output
Comment 7 Lewis Smith 2023-06-01 21:12:10 CEST
Thanks for that.

To summarise what I deduce: interface
'enp4s0' is the realtek rTL8125 device with driver <r8169> (version: 5.15.110-desktop-2.mga8) which always works;

'eno1': onboard intel 1217-LM with driver <igb> (version: 5.15.110-desktop-2.mga8), which seems to be the troublesome one [title, comment 0, comment 4].

'en02': onboard intel 1210 with driver <e1000e> (version: 5.15.110-desktop-2.mga8), which normally works [comment 4]

Assigning this to kernel/drivers.

Assignee: bugsquad => kernel
CC: lewyssmith => (none)


Note You need to log in before you can comment on or make changes to this bug.