I tried a sudo modprobe ice but it didn’t seem to do anything (no errors either).
So what do I need to do to get the nic enabled in the kernel via the ice driver? FWIW, the nic also did not work in the EndeavourOS live CD environment.
I have used Debian-based and RHEL-based distros in the past, and those had the nic working out of the box. But they used kernel 5.x, and this is my first time using Arch and kernel 6.x.
-f, --force
Try to strip any versioning information from the module which might otherwise stop it from loading: this is the same as using both --force-vermagic and --force-modversion. Naturally, these checks are there for your
protection, so using this option is dangerous unless you know what you are doing.
This comment was the key. The author was talking about IOMMU groups and how PCI device drivers should not modify the PCI BARs. That’s when I remembered I had turned on SR-IOV in my UEFI. In my particular motherboard, it’s a beta feature at this time.
Disabling SR-IOV and rebooting the system enabled the ice driver:
IF: enp14s0 state: down mac: <filter>
Device-3: Intel Ethernet E810-XXV for SFP driver: ice v: kernel port: N/A
bus-ID: 11:00.0
IF: enp17s0f0np0 state: up speed: 10000 Mbps duplex: full mac: <filter>
Device-4: Intel Ethernet E810-XXV for SFP driver: ice v: kernel port: N/A
bus-ID: 11:00.1
$ sudo ethtool enp17s0f0np0
Settings for enp17s0f0np0:
Supported ports: [ FIBRE ]
Supported link modes: 1000baseT/Full
10000baseT/Full
25000baseCR/Full
25000baseSR/Full
1000baseX/Full
10000baseSR/Full
10000baseLR/Full
Supported pause frame use: Symmetric
Supports auto-negotiation: No
Supported FEC modes: None
Advertised link modes: 25000baseSR/Full
10000baseSR/Full
Advertised pause frame use: No
Advertised auto-negotiation: No
Advertised FEC modes: None
Speed: 10000Mb/s
Duplex: Full
Auto-negotiation: off
Port: FIBRE
PHYAD: 0
Transceiver: internal
Supports Wake-on: d
Wake-on: d
Current message level: 0x00000007 (7)
drv probe link
Link detected: yes
I guess something about the newer Linux kernels 6.x might not like SR-IOV being enabled in my particular motherboard. Both older 5.x kernels in the other distros and Windows 11 did not have an issue with it.