New motherboard Intel I225-V 2.5Gb/s port is always down

English Network/Internet
#1

Hello, I switched from an Intel Skylake platform to the new Ryzen 7000; as usual just replaced stuff, normal boot followed. Had to configure the silly WiFi I laughed about as the new 2,5Gb/s from Intel doesn’t work. My extra Mellanox SFP+ card is also fine, but in a different VLAN, for NAS/SAN and some administrative stuff, so no internet on that one, as intended.

I am on Leap 15.4 fully updated kernel 5.14.21-150400.24.21-default

The cable is still fine, tested it, though the interface is down:

2: eth7: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000
    link/ether d8:5e:d3:e5:85:36 brd ff:ff:ff:ff:ff:ff
    altname enp14s0

The card is:


0e:00.0 Ethernet controller: Intel Corporation Ethernet Controller I225-V (rev 01)

Ethtool info:


driver: igc
version: 5.14.21-150400.24.21-default
firmware-version: 1045:740
expansion-rom-version: 
bus-info: 0000:0e:00.0
supports-statistics: yes
supports-test: yes
supports-eeprom-access: yes
supports-register-dump: yes
supports-priv-flags: yes

Lshw:


*-network
     description: Ethernet interface
     product: Ethernet Controller I225-V
     vendor: Intel Corporation
     physical id: 0
     bus info: pci@0000:0e:00.0
     logical name: eth7
     version: 01
     serial: d8:5e:d3:e5:85:36
     capacity: 2500Mbit/s
     width: 32 bits
     clock: 33MHz
     capabilities: pm msi msix pciexpress bus_master cap_list ethernet physical 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd 2500bt-fd autonegotiation
     configuration: autonegotiation=on broadcast=yes driver=igc driverversion=5.14.21-150400.24.21-default firmware=1045:740 latency=0 link=no multicast=yes port=twisted pair
     resources: irq:38 memory:80200000-802fffff memory:80300000-80303fff

Modinfo igc:


filename:       /lib/modules/5.14.21-150400.24.21-default/kernel/drivers/net/ethernet/intel/igc/igc.ko.zst
license:        GPL v2
description:    Intel(R) 2.5G Ethernet Linux Driver
author:         Intel Corporation, <linux.nics@intel.com>
suserelease:    SLE15-SP4
srcversion:     EB9DB39B6EBDC2A2E136416
alias:          pci:v00008086d000015FDsv*sd*bc*sc*i*
alias:          pci:v00008086d0000125Fsv*sd*bc*sc*i*
alias:          pci:v00008086d0000125Esv*sd*bc*sc*i*
alias:          pci:v00008086d0000125Dsv*sd*bc*sc*i*
alias:          pci:v00008086d0000125Csv*sd*bc*sc*i*
alias:          pci:v00008086d0000125Bsv*sd*bc*sc*i*
alias:          pci:v00008086d00000D9Fsv*sd*bc*sc*i*
alias:          pci:v00008086d00005503sv*sd*bc*sc*i*
alias:          pci:v00008086d00005502sv*sd*bc*sc*i*
alias:          pci:v00008086d00003102sv*sd*bc*sc*i*
alias:          pci:v00008086d00003101sv*sd*bc*sc*i*
alias:          pci:v00008086d00003100sv*sd*bc*sc*i*
alias:          pci:v00008086d000015F7sv*sd*bc*sc*i*
alias:          pci:v00008086d000015F8sv*sd*bc*sc*i*
alias:          pci:v00008086d000015F3sv*sd*bc*sc*i*
alias:          pci:v00008086d000015F2sv*sd*bc*sc*i*
depends:        
supported:      yes
retpoline:      Y
intree:         Y
name:           igc
vermagic:       5.14.21-150400.24.21-default SMP preempt mod_unload modversions 
sig_id:         PKCS#7
signer:         SUSE Linux Enterprise Secure Boot CA
sig_key:        ED:87:85:B7:8F:FC:12:7F
sig_hashalgo:   sha256
signature:      09:7C:FC:2E:E9:89:94:2F:9F:DA:56:DB:EF:57:3F:C9:B4:DF:FD:11:
                60:E4:90:22:03:48:A8:18:B4:91:3C:E7:32:81:BE:4F:A9:0A:98:EF:
                41:1F:3B:45:91:DA:10:10:E2:E3:6E:0F:6D:5B:68:FA:20:04:7B:14:
                39:A5:92:5B:8F:66:BA:8B:DC:A3:0D:DC:90:01:46:92:30:9E:5C:22:
                E2:A0:18:9D:F7:96:D4:1B:4E:A5:A2:A3:D9:86:52:40:F5:9B:E4:E8:
                B0:3F:66:68:B1:A2:C9:E2:0B:55:12:25:FB:CF:A5:26:35:26:8F:3C:
                3F:7C:AE:F9:3D:90:7A:7E:B6:B0:10:AA:90:25:29:EF:D9:01:99:51:
                21:EC:0C:3D:02:49:97:BC:3E:0C:3C:2B:F8:12:EC:D1:41:55:63:CB:
                B0:BF:7A:7D:D9:97:7D:D8:E7:DE:C5:AE:30:9F:1E:0E:18:36:33:8D:
                0A:CF:15:89:0A:42:15:A9:8B:F5:DC:0E:39:B6:33:02:9A:3C:5E:56:
                1A:1D:A5:C8:84:F7:AF:99:FA:12:03:7D:63:AC:66:C3:B3:08:C3:DF:
                CD:86:C9:05:4D:03:E6:D4:88:7C:D0:8A:F9:90:3C:78:CC:FA:8F:2E:
                83:9D:BD:7B:53:6C:71:C9:DD:81:90:AB:06:D5:24:37
parm:           debug:Debug level (0=none,...,16=all) (int)

Any idea how to get this card working, as I don’t have a clue of what should I do next? And please please :shame: constructive messages only, let’s skip the “go ancient”, “new bad”, “it is known” first hitters, because I have been there 3000 years ago rotfl!

#2

Post:

/sbin/lspci -nnk | grep -iA3 net
#3

Here it is:


0d:00.0 Ethernet controller [0200]: Mellanox Technologies MT27500 Family [ConnectX-3] [15b3:1003]
        Subsystem: Mellanox Technologies Device [15b3:0055]
        Kernel driver in use: mlx4_core
        Kernel modules: mlx4_core
0e:00.0 Ethernet controller [0200]: Intel Corporation Ethernet Controller I225-V [8086:15f3] (rev 01)
        Subsystem: Gigabyte Technology Co., Ltd Device [1458:e000]
        Kernel driver in use: igc
        Kernel modules: igc
0f:00.0 Network controller [0280]: Intel Corporation Wi-Fi 6 AX210/AX211/AX411 160MHz [8086:2725] (rev 1a)
        Subsystem: Intel Corporation Wi-Fi 6 AX210 160MHz [8086:0024]
        Kernel driver in use: iwlwifi
        Kernel modules: iwlwifi
#4

Hi
Anything in the journal about igc, ethtool give any hints?


journalctl -b | grep igc
dmesg | grep igc

ethtool eth7
#5

Please, take a look at ‘/etc/udev/rules.d/70-persistent-net.rules’ –

  • You seem to have changed the Mainboard and CPU and while retaining the previous hardware’s system disk.

Please, also take a look at ‘/sys/class/net/eth**?**’ with “udevadm info” –

  • Please check the PCI device path.

Once you’ve sorted out the udev device name and rebooted, please check the YaST Network configuration and, if need be, enable the device – and then reboot.

Please, check that, you have the “ucode-amd” Package installed.

#6

There doesn’t seem to be any firmware being loaded for this device.

  • Does this device need Firmware installed in ‘/lib/firmware/’ ?
#7

Hi
No, if it did would be in the module output.

#8 
# journalctl -b | grep igc
oct 18 11:47:11 FakeMoth-PC kernel: igc 0000:0e:00.0: PCIe PTM not supported by PCIe bus/controller
oct 18 11:47:11 FakeMoth-PC kernel: igc 0000:0e:00.0 (unnamed net_device) (uninitialized): PHC added
oct 18 11:47:11 FakeMoth-PC kernel: igc 0000:0e:00.0: 4.000 Gb/s available PCIe bandwidth (5.0 GT/s PCIe x1 link)
oct 18 11:47:11 FakeMoth-PC kernel: igc 0000:0e:00.0 eth0: MAC: d8:5e:d3:e5:85:36
oct 18 11:47:12 FakeMoth-PC kernel: igc 0000:0e:00.0 eth7: renamed from eth0

And pretty much the same


   42.861856] igc 0000:0e:00.0: PCIe PTM not supported by PCIe bus/controller
   42.913448] igc 0000:0e:00.0 (unnamed net_device) (uninitialized): PHC added
   42.936382] igc 0000:0e:00.0: 4.000 Gb/s available PCIe bandwidth (5.0 GT/s PCIe x1 link)
   42.936385] igc 0000:0e:00.0 eth0: MAC: d8:5e:d3:e5:85:36
   43.468912] igc 0000:0e:00.0 eth7: renamed from eth0
#9

And thank you all for your interest in this!

I am not sure what I should do here, using NetworkManager BTW:


# cat /etc/udev/rules.d/70-persistent-net.rules
# This file was automatically generated by the /usr/lib/udev/write_net_rules
# program,run by the persistent-net-generator.rules rules file.
#
# You can modify it,as long as you keep each rule on a single
# line,and change only the value of the NAME= key.
# PCI device 0x8086:0x15b8 (e1000e)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="30:5a:3a:47:d6:ed", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"

# PCI device 0x14e4:0x164a (bnx2)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:23:7d:28:90:10", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth1"

# PCI device 0x14e4:0x164a (bnx2)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:23:7d:28:90:12", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth2"

# USB device 0x05ac:0x12a8 (usb)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="xhci_hcd", ATTR{dev_id}=="0x0", KERNELS=="0000:00:14.0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth3"

# mlx4_core (0000:07:00.0)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:02:c9:57:0d:32", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth4"

# mlx4_core (0000:04:00.0)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="e4:1d:2d:dc:c8:70", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth5"

# mlx4_core (0000:07:00.0)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:02:c9:57:0d:33", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth6"

# PCI device 0x8086:0x15f3 (igc)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="d8:5e:d3:e5:85:36", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth7"

# PCI device 0x8086:0x2725 (iwlwifi)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="ac:82:47:4c:c2:d7", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="wlan*", NAME="wlan0"



# udevadm info /sys/class/net/eth7
P: /devices/pci0000:00/0000:00:02.1/0000:04:00.0/0000:05:08.0/0000:0a:00.0/0000:0b:06.0/0000:0e:00.0/net/eth7
L: 0
E: DEVPATH=/devices/pci0000:00/0000:00:02.1/0000:04:00.0/0000:05:08.0/0000:0a:00.0/0000:0b:06.0/0000:0e:00.0/net/eth7
E: INTERFACE=eth7
E: IFINDEX=2
E: SUBSYSTEM=net
E: USEC_INITIALIZED=43505613
E: ID_NET_NAMING_SCHEME=sle15-sp4
E: ID_NET_NAME_MAC=enxd85ed3e58536
E: ID_OUI_FROM_DATABASE=GIGA-BYTE TECHNOLOGY CO.,LTD.
E: ID_NET_NAME_PATH=enp14s0
E: ID_BUS=pci
E: ID_VENDOR_ID=0x8086
E: ID_MODEL_ID=0x15f3
E: ID_PCI_CLASS_FROM_DATABASE=Network controller
E: ID_PCI_SUBCLASS_FROM_DATABASE=Ethernet controller
E: ID_VENDOR_FROM_DATABASE=Intel Corporation
E: ID_MODEL_FROM_DATABASE=Ethernet Controller I225-V
E: ID_MM_CANDIDATE=1
E: ID_PATH=pci-0000:0e:00.0
E: ID_PATH_TAG=pci-0000_0e_00_0
E: ID_NET_DRIVER=igc
E: ID_NET_LINK_FILE=/usr/lib/systemd/network/99-default.link
E: ID_NET_NAME=eth7
E: SYSTEMD_ALIAS=/sys/subsystem/net/devices/eth7
E: TAGS=:systemd:
E: CURRENT_TAGS=:systemd:
#10

Hi
In the system BIOS is there anything about PTM support?

What about;


ethtool eth0

dmesg | grep Intel
#11

Post output of

LC_ALL=C nmcli device | cat
#12 

# ethtool eth0
netlink error: no device matches name (offset 24)
netlink error: No such device
netlink error: no device matches name (offset 24)
netlink error: No such device
netlink error: no device matches name (offset 24)
netlink error: No such device
netlink error: no device matches name (offset 24)
netlink error: No such device
netlink error: no device matches name (offset 24)
netlink error: No such device
No data available



# dmesg | grep Intel
   15.859371] Intel(R) 2.5G Ethernet Linux Driver
   15.859373] Copyright(c) 2018 Intel Corporation.
   16.068275] Intel(R) Wireless WiFi driver for Linux
   16.242165] iwlwifi 0000:0f:00.0: Detected Intel(R) Wi-Fi 6 AX210 160MHz, REV=0x420
#13

Sure, here:

# LC_ALL=C nmcli device | cat
DEVICE           TYPE      STATE                   CONNECTION              
wlan0            wifi      connected               WiFiVLAN11 - 10.0.1.20
br-3eb4a241bc11  bridge    connected (externally)  br-3eb4a241bc11         
docker0          bridge    connected (externally)  docker0                 
virbr0           bridge    connected (externally)  virbr0                  
eth5             ethernet  connected               VLAN30 - 192.168.1.2   
p2p-dev-wlan0    wifi-p2p  disconnected            --                      
eth7             ethernet  unavailable             --                      
vetha3819c5      ethernet  unmanaged               --                      
vethac78dc3      ethernet  unmanaged               --                      
lo               loopback  unmanaged               --
#14

Assuming you verified that cable and switch port are OK, you may try the latest kernel from https://download.opensuse.org/repositories/Kernel:/stable:/Backport/standard/.

#15

Thanks for all the great help guys, but it seems like a BIOS issue! Even if nothing is listed on their website as being fixed in regards to the network, after an upgrade to the latest version it just started to work; as I really had no idea what else I could do, said to myself that updating the BIOS and jumping in the 6 kernel bandwagon were the only options left. The motherboard is Gigabyte Aorus Master X670E, and the upgrade was from vs 6 to 8a.

Beautiful system, stuff working, still having network issues like the speed just dropping on the interface (the NIC stays at 1Gb/s, so not some connection issue, downgrading to 100megs), again not the Mellanox one but this Intel thingy. But these I had with the previous system too so I suspect something else, like the bridges, power management… and stuff… Whatever, I would mark this as closed/solved (mmmm, how do I do that?).

On more thing: very few sensors are detected, what can I do about that, any hints?

#16

Hi
Did you run sensors-detect --auto I suspect you may have a IT86xx sensor?

#17

Hello again. I did, and also right now, and I only get:

# sensors
amdgpu-pci-0300
Adapter: PCI adapter
vddgfx:       +0.78 V  
fan1:        1375 RPM  (min =  400 RPM, max = 4900 RPM)
edge:         +36.0°C  (crit = +85.0°C, hyst = -273.1°C)
                       (emerg = +90.0°C)
junction:     +36.0°C  (crit = +105.0°C, hyst = -273.1°C)
                       (emerg = +110.0°C)
mem:          +36.0°C  (crit = +95.0°C, hyst = -273.1°C)
                       (emerg = +100.0°C)
slowPPT:       8.00 W  (cap = 220.00 W)

iwlwifi_1-virtual-0
Adapter: Virtual device
temp1:            N/A

Don’t know what chip is responsible for this. The motherboard itself is stacked with features, even have 2 separate temp probes and a mic for noise, I suppose for the new CPUs I should still jump to kernel 6? Very annoying as for example in the Phoronix Suite those infos lack.

#18

Hi
In the output, browse the list, does it show a sensor detected?

#19

Here is the complete output:

# sensors-detect --auto
# sensors-detect revision $Revision$
# System: Gigabyte Technology Co., Ltd. X670E AORUS MASTER -CF]
# Kernel: 5.14.21-150400.24.21-default x86_64
# Processor: AMD Ryzen 7 7700X 8-Core Processor (25/97/2)

Running in automatic mode, default answers to all questions
are assumed.

Some south bridges, CPUs or memory controllers contain embedded sensors.
Do you want to scan for them? This is totally safe. (YES/no): 
Module cpuid loaded successfully.
Silicon Integrated Systems SIS5595...                       No
VIA VT82C686 Integrated Sensors...                          No
VIA VT8231 Integrated Sensors...                            No
AMD K8 thermal sensors...                                   No
AMD Family 10h thermal sensors...                           No
AMD Family 11h thermal sensors...                           No
AMD Family 12h and 14h thermal sensors...                   No
AMD Family 15h thermal sensors...                           No
AMD Family 16h thermal sensors...                           No
AMD Family 17h thermal sensors...                           No
AMD Family 15h power sensors...                             No
AMD Family 16h power sensors...                             No
Intel digital thermal sensor...                             No
Intel AMB FB-DIMM thermal sensor...                         No
Intel 5500/5520/X58 thermal sensor...                       No
VIA C7 thermal sensor...                                    No
VIA Nano thermal sensor...                                  No

Some Super I/O chips contain embedded sensors. We have to write to
standard I/O ports to probe them. This is usually safe.
Do you want to scan for Super I/O sensors? (YES/no): 
Probing for Super-I/O at 0x2e/0x2f
Trying family `National Semiconductor/ITE'...               No
Trying family `SMSC'...                                     No
Trying family `VIA/Winbond/Nuvoton/Fintek'...               No
Trying family `ITE'...                                      Yes
Found unknown chip with ID 0x8689
Probing for Super-I/O at 0x4e/0x4f
Trying family `National Semiconductor/ITE'...               No
Trying family `SMSC'...                                     No
Trying family `VIA/Winbond/Nuvoton/Fintek'...               No
Trying family `ITE'...                                      Yes
Found unknown chip with ID 0x8883
    (logical device 4 has address 0x290, could be sensors)

Some systems (mainly servers) implement IPMI, a set of common interfaces
through which system health data may be retrieved, amongst other things.
We first try to get the information from SMBIOS. If we don't find it
there, we have to read from arbitrary I/O ports to probe for such
interfaces. This is normally safe. Do you want to scan for IPMI
interfaces? (YES/no): 
Probing for `IPMI BMC KCS' at 0xca0...                      No
Probing for `IPMI BMC SMIC' at 0xca8...                     No

Some hardware monitoring chips are accessible through the ISA I/O ports.
We have to write to arbitrary I/O ports to probe them. This is usually
safe though. Yes, you do have ISA I/O ports even if you do not have any
ISA slots! Do you want to scan the ISA I/O ports? (YES/no): 
Probing for `National Semiconductor LM78' at 0x290...       No
Probing for `National Semiconductor LM79' at 0x290...       No
Probing for `Winbond W83781D' at 0x290...                   No
Probing for `Winbond W83782D' at 0x290...                   No

Lastly, we can probe the I2C/SMBus adapters for connected hardware
monitoring devices. This is the most risky part, and while it works
reasonably well on most systems, it has been reported to cause trouble
on some systems.
Do you want to probe the I2C/SMBus adapters now? (YES/no): 
Using driver `i2c-piix4' for device 0000:00:14.0: AMD KERNCZ SMBus
Module i2c-dev loaded successfully.

Next adapter: AMDGPU DM i2c hw bus 0 (i2c-0)
Do you want to scan it? (yes/NO/selectively): 

Next adapter: AMDGPU DM i2c hw bus 1 (i2c-1)
Do you want to scan it? (yes/NO/selectively): 

Next adapter: AMDGPU DM i2c hw bus 2 (i2c-2)
Do you want to scan it? (yes/NO/selectively): 

Next adapter: AMDGPU DM i2c hw bus 3 (i2c-3)
Do you want to scan it? (yes/NO/selectively): 

Next adapter: AMDGPU DM aux hw bus 0 (i2c-4)
Do you want to scan it? (yes/NO/selectively): 

Next adapter: AMDGPU DM aux hw bus 1 (i2c-5)
Do you want to scan it? (yes/NO/selectively): 

Next adapter: AMDGPU DM aux hw bus 2 (i2c-6)
Do you want to scan it? (yes/NO/selectively): 

Next adapter: Synopsys DesignWare I2C adapter (i2c-7)
Do you want to scan it? (YES/no/selectively): 
Adapter doesn't support all probing functions.
Some addresses won't be probed.

Next adapter: Synopsys DesignWare I2C adapter (i2c-8)
Do you want to scan it? (YES/no/selectively): 
Adapter doesn't support all probing functions.
Some addresses won't be probed.
Client found at address 0x50
Probing for `Analog Devices ADM1033'...                     No
Probing for `Analog Devices ADM1034'...                     No
Probing for `SPD EEPROM'...                                 No
Probing for `EDID EEPROM'...                                No
Client found at address 0x51
Probing for `Analog Devices ADM1033'...                     No
Probing for `Analog Devices ADM1034'...                     No
Probing for `SPD EEPROM'...                                 No
Client found at address 0x52
Probing for `Analog Devices ADM1033'...                     No
Probing for `Analog Devices ADM1034'...                     No
Probing for `SPD EEPROM'...                                 No

Sorry, no sensors were detected.
Either your system has no sensors, or they are not supported, or
they are connected to an I2C or SMBus adapter that is not
supported. If you find out what chips are on your board, check
https://hwmon.wiki.kernel.org/device_support_status for driver status.
#20

Hi
So here it is;


 Trying family `ITE'...                                      Yes
Found unknown chip with ID 0x8689

See https://github.com/lm-sensors/lm-sensors/issues/154

Now I do have the it87 chip built for Tumbleweed as I need it it my test MiniPC, let me enable Leap.