Upgraded to 26.7 today and lost links on E810-XXV-2 , failed to establish any carrier.
I had this in loader.conf.local on 26.1
# cat /boot/loader.conf.local
if_ice_load="YES"
ice_ddp_load="YES"
Here what I see in dmesg :
[1] ice0: <Intel(R) Ethernet Network Adapter E810-XXV-2 - 1.43.3-k> mem 0x380000000000-0x380001ffffff,0x380002000000-0x38000200ffff irq 16 at device 0.0 on pci1
[1] ice0: Loading the iflib ice driver
[1] ice0: DDP package already present on device: ICE OS Default Package version 1.3.41.0, track id 0xc0000001.
[1] ice0: fw 7.5.4 api 1.7 nvm 4.50 etid 8001d8ba netlist 4.3.5000-1.14.0.99840ef4 oem 1.3597.0
[1] ice0: Using 8 Tx and Rx queues
[1] ice0: Reserving 8 MSI-X interrupts for iRDMA
[1] ice0: Using MSI-X interrupts with 17 vectors
[1] ice0: Using 1024 TX descriptors and 1024 RX descriptors
[1] ice0: Ethernet address: 50:7c:6f:79:ca:e8
[1] ice0: ice_add_rss_cfg on VSI 0 could not configure every requested hash type
[1] ice0: PCI Express Bus: Speed 16.0GT/s Width x8
[1] ice0: pci_iov_attach failed (error=ENOENT)
[1] ice0: Firmware LLDP agent disabled
[1] ice0: netmap queues/slots: TX 8/1024, RX 8/1024
[1] ice0: link state changed to DOWN
[1] ice0: All configured link modes were attempted but failed to establish link.
[1] ice0: The device will restart the process to establish link.
[1] ice0: Possible Solution: Check link partner connection and configuration.
I don't have 15.1 on a machine with an e810 yet, so I can't compare directly (version, at least). I'd update the NVM and see if that helps. Do you have SR-IOV enabled in BIOS?
Just booting the 15.1 installer, my e810 links fine... but doesn't load the DDP. I can mess with the installer, but it'll take some time.
Hi, I upgraded my big firewall test machine today to 26.7 with DDP enabled on the E810 and it seems fine.
Module is loaded:
root@Firewall-1:~ # dmesg | grep -i ddp
[1] ice0: The DDP package was successfully loaded: ICE OS Default Package version 1.3.41.0, track id 0xc0000001.
[1] ice1: DDP package already present on device: ICE OS Default Package version 1.3.41.0, track id 0xc0000001.
root@Firewall-1:~ # kldstat | grep -i ddp
2 1 0xffffffff8277f000 14ce38 ice_ddp.ko
root@Firewall-1:~ # dmesg | grep -i ice0
[1] ice0: <Intel(R) Ethernet Network Adapter E810-C-Q2 - 1.43.3-k> mem 0x380ae000000-0x380afffffff,0x380b0010000-0x380b001ffff irq 120 at device 0.0 on pci10
[1] ice0: Loading the iflib ice driver
[1] ice0: The DDP package was successfully loaded: ICE OS Default Package version 1.3.41.0, track id 0xc0000001.
[1] ice0: fw 7.8.2 api 1.7 nvm 4.80 etid 80020543 netlist 4.4.2000-3.27.0.597b7167 oem 1.3805.0
[1] ice0: Using 8 Tx and Rx queues
[1] ice0: Reserving 8 MSI-X interrupts for iRDMA
[1] ice0: Using MSI-X interrupts with 17 vectors
[1] ice0: Using 1024 TX descriptors and 1024 RX descriptors
[1] ice0: Ethernet address: 6c:fe:54:c3:3a:80
[1] ice0: ice_add_rss_cfg on VSI 0 could not configure every requested hash type
[1] ice0: PCI Express Bus: Speed 16.0GT/s Width x16
[1] ice0: Firmware LLDP agent disabled
[1] ice0: link state changed to DOWN
[1] ice0: netmap queues/slots: TX 8/1024, RX 8/1024
[8] ice0: All configured link modes were attempted but failed to establish link.
[8] ice0: The device will restart the process to establish link.
[8] ice0: Possible Solution: Check link partner connection and configuration.
[20] ice0: All configured link modes were attempted but failed to establish link.
[20] ice0: The device will restart the process to establish link.
[20] ice0: Possible Solution: Check link partner connection and configuration.
[5789] ice0: Link is up, 100 Gbps Full Duplex, Requested FEC: None, Negotiated FEC: RS-FEC, Autoneg: True, Flow Control: None
[5789] ice0: link state changed to UP
I booted a machine connected to this firewall just recently and it connected, at least a ping to this machine succeeded.
Best regards,
Thomas
Quote from: Thomas Niedermeier on July 16, 2026, 05:10:57 PMHi, I upgraded my big firewall test machine today to 26.7 with DDP enabled on the E810 and it seems fine.
Module is loaded:
root@Firewall-1:~ # dmesg | grep -i ddp
[1] ice0: The DDP package was successfully loaded: ICE OS Default Package version 1.3.41.0, track id 0xc0000001.
[1] ice1: DDP package already present on device: ICE OS Default Package version 1.3.41.0, track id 0xc0000001.
root@Firewall-1:~ # kldstat | grep -i ddp
2 1 0xffffffff8277f000 14ce38 ice_ddp.ko
root@Firewall-1:~ # dmesg | grep -i ice0
[1] ice0: <Intel(R) Ethernet Network Adapter E810-C-Q2 - 1.43.3-k> mem 0x380ae000000-0x380afffffff,0x380b0010000-0x380b001ffff irq 120 at device 0.0 on pci10
[1] ice0: Loading the iflib ice driver
[1] ice0: The DDP package was successfully loaded: ICE OS Default Package version 1.3.41.0, track id 0xc0000001.
[1] ice0: fw 7.8.2 api 1.7 nvm 4.80 etid 80020543 netlist 4.4.2000-3.27.0.597b7167 oem 1.3805.0
[1] ice0: Using 8 Tx and Rx queues
[1] ice0: Reserving 8 MSI-X interrupts for iRDMA
[1] ice0: Using MSI-X interrupts with 17 vectors
[1] ice0: Using 1024 TX descriptors and 1024 RX descriptors
[1] ice0: Ethernet address: 6c:fe:54:c3:3a:80
[1] ice0: ice_add_rss_cfg on VSI 0 could not configure every requested hash type
[1] ice0: PCI Express Bus: Speed 16.0GT/s Width x16
[1] ice0: Firmware LLDP agent disabled
[1] ice0: link state changed to DOWN
[1] ice0: netmap queues/slots: TX 8/1024, RX 8/1024
[8] ice0: All configured link modes were attempted but failed to establish link.
[8] ice0: The device will restart the process to establish link.
[8] ice0: Possible Solution: Check link partner connection and configuration.
[20] ice0: All configured link modes were attempted but failed to establish link.
[20] ice0: The device will restart the process to establish link.
[20] ice0: Possible Solution: Check link partner connection and configuration.
[5789] ice0: Link is up, 100 Gbps Full Duplex, Requested FEC: None, Negotiated FEC: RS-FEC, Autoneg: True, Flow Control: None
[5789] ice0: link state changed to UP
I booted a machine connected to this firewall just recently and it connected, at least a ping to this machine succeeded.
Best regards,
Thomas
you're on nvm 4.80 I'm on 4.50
let me try to flash it
thanks!
I also have a 4-port e810.
Mine works fine, although I just checked and there's an update. Is it a good idea to update it?
grep -i ddp
[1] ice0: The driver could not load the DDP package file because a compatible DDP package is already present on the device. The device has package ICE OS Default Package version 1.3.43.0, track id 0xc0000001. The ice_ddp module has package: ICE OS Default Package version 1.3.41.0.
[1] ice1: The driver could not load the DDP package file because a compatible DDP package is already present on the device. The device has package ICE OS Default Package version 1.3.43.0, track id 0xc0000001. The ice_ddp module has package: ICE OS Default Package version 1.3.41.0.
[1] ice2: The driver could not load the DDP package file because a compatible DDP package is already present on the device. The device has package ICE OS Default Package version 1.3.43.0, track id 0xc0000001. The ice_ddp module has package: ICE OS Default Package version 1.3.41.0.
root@opn:~ # kldstat | grep -i ddp
12 1 0xffffffff82f71000 14ce38 ice_ddp.ko
root@opn:~ # dmesg | grep -i ice0
[1] ice0: <Intel(R) Ethernet Network Adapter E810-XXV-4 - 1.43.3-k> mem 0x382000000000-0x382001ffffff,0x382002000000-0x38200200ffff irq 21 at device 0.0 on pci5
[1] ice0: Loading the iflib ice driver
[1] ice0: The driver could not load the DDP package file because a compatible DDP package is already present on the device. The device has package ICE OS Default Package version 1.3.43.0, track id 0xc0000001. The ice_ddp module has package: ICE OS Default Package version 1.3.41.0.
[1] ice0: fw 7.6.2 api 1.7 nvm 4.60 etid 8001e8b2 netlist 4.3.2000-1.17.0.2c46f598 oem 1.3682.0
[1] ice0: Using 4 Tx and Rx queues
[1] ice0: Reserving 2 MSI-X interrupts for iRDMA
[1] ice0: Using MSI-X interrupts with 7 vectors
[1] ice0: Using 4096 TX descriptors and 4096 RX descriptors
[1] ice0: Ethernet address: 9c:69:b4:68:65:99
[1] ice0: ice_add_rss_cfg on VSI 0 could not configure every requested hash type
[1] ice0: PCI Express Bus: Speed 8.0GT/s Width x16
[1] ice0: pci_iov_attach failed (error=ENOENT)
[1] ice0: Firmware LLDP agent disabled
[1] ice0: link state changed to UP
[1] ice0: Link is up, 25 Gbps Full Duplex, Requested FEC: None, Negotiated FEC: RS-FEC, Autoneg: True, Flow Control: None
[1] ice0: netmap queues/slots: TX 4/4096, RX 4/4096
[1] ice0: link state changed to DOWN
[1] ice0: Link is up, 25 Gbps Full Duplex, Requested FEC: None, Negotiated FEC: None, Autoneg: True, Flow Control: None
[1] ice0: link state changed to UP
[11768] ice0: link state changed to DOWN
[11787] ice0: All configured link modes were attempted but failed to establish link.
[11787] ice0: The device will restart the process to establish link.
[11787] ice0: Possible Solution: Check link partner connection and configuration.
[60739] ice0: Link is up, 25 Gbps Full Duplex, Requested FEC: None, Negotiated FEC: None, Autoneg: False, Flow Control: None
[60739] ice0: link state changed to UP
Intel(R) Ethernet NVM Update Tool
NVMUpdate version 1.43.37.1a
Copyright(C) 2013 - 2026 Intel Corporation.
WARNING: To avoid damage to your device, do not stop the update or reboot or power off the system during this update.
Inventory in progress. Please wait [***-......]
Num Description Ver.(hex) DevId S:B Status
=== ================================== ============ ===== ====== ==============
01) Intel(R) Ethernet Converged N/A(N/A) 1563 00:037 Update not
Network Adapter X550-T2 available
02) Intel(R) Ethernet Network Adapter 4.96(4.60) 1593 00:042 Update
E810-XXV-4 available
Options: Adapter Index List (comma-separated), [A]ll, e[X]it
Enter selection:
Nothing works
Tried NVM 4.80 and 4.60 both result in this :
link goes up briefly :
# egrep -i ice0 4_60.log
[1] ice0: <Intel(R) Ethernet Network Adapter E810-XXV-2 - 1.43.3-k> mem 0x380000000000-0x380001ffffff,0x380002000000-0x38000200ffff irq 16 at device 0.0 on pci1
[1] ice0: Loading the iflib ice driver
[1] ice0: Error configuring transmit balancing: ICE_ERR_AQ_ERROR
[1] ice0: An unknown error occurred when loading the DDP package. Entering Safe Mode.
[1] ice0: fw 7.6.2 api 1.7 nvm 4.60 etid 8001e8b3 netlist 4.3.5000-1.14.0.99840ef4 oem 1.3682.0
[1] ice0: Using 1 Tx and Rx queues
[1] ice0: Using MSI-X interrupts with 2 vectors
[1] ice0: Using 1024 TX descriptors and 1024 RX descriptors
[1] ice0: Ethernet address: 50:7c:6f:79:ca:e8
[1] ice0: PCI Express Bus: Speed 16.0GT/s Width x8
[1] ice0: ice_init_dcb_setup: No DCB support
[1] ice0: Link is up, 25 Gbps Full Duplex, Requested FEC: RS-FEC, Negotiated FEC: RS-FEC, Autoneg: False, Flow Control: None
[1] ice0: link state changed to UP
[1] ice0: netmap queues/slots: TX 1/1024, RX 1/1024
But later something happens , I guess driver trying to read something from FW that not supporting it and it goes into Safe mode
[1] ice0: link state changed to DOWN
[9] ice0: ice_read_sff_eeprom: Error reading I2C data: err ICE_ERR_AQ_TIMEOUT aq_err OK
[12] ice0: ice_read_sff_eeprom: Error reading I2C data: err ICE_ERR_AQ_TIMEOUT aq_err OK
[14] ice0: ice_read_sff_eeprom: Error reading I2C data: err ICE_ERR_AQ_TIMEOUT aq_err OK
[16] ice0: ice_read_sff_eeprom: Error reading I2C data: err ICE_ERR_AQ_TIMEOUT aq_err OK
[29] ice0: Could not acquire current LLDP persistence status, err ICE_ERR_AQ_TIMEOUT aq_err OK
[30] ice0: Could not acquire current LLDP persistence status, err ICE_ERR_AQ_TIMEOUT aq_err OK
[31] ice0: ice_intersect_phy_types_and_speeds: ice_aq_get_phy_caps (ACTIVE) failed; status ICE_ERR_AQ_TIMEOUT, aq_err OK
[32] ice0: ice_intersect_phy_types_and_speeds: ice_aq_get_phy_caps (ACTIVE) failed; status ICE_ERR_AQ_TIMEOUT, aq_err OK
[33] ice0: ice_sysctl_fc_config: ice_aq_get_phy_caps failed; status ICE_ERR_AQ_TIMEOUT, aq_err OK
[34] ice0: ice_sysctl_fc_config: ice_aq_get_phy_caps failed; status ICE_ERR_AQ_TIMEOUT, aq_err OK
[38] ice0: ice_read_sff_eeprom: Error reading I2C data: err ICE_ERR_AQ_TIMEOUT aq_err OK
[46] ice0: ice_read_sff_eeprom: Error reading I2C data: err ICE_ERR_AQ_TIMEOUT aq_err OK
[48] ice0: ice_read_sff_eeprom: Error reading I2C data: err ICE_ERR_AQ_TIMEOUT aq_err OK
[51] ice0: ice_read_sff_eeprom: Error reading I2C data: err ICE_ERR_AQ_TIMEOUT aq_err OK
[53] ice0: ice_read_sff_eeprom: Error reading I2C data: err ICE_ERR_AQ_TIMEOUT aq_err OK
[65] ice0: ice_read_sff_eeprom: Error reading I2C data: err ICE_ERR_AQ_TIMEOUT aq_err OK
[76] ice0: ice_read_sff_eeprom: Error reading I2C data: err ICE_ERR_AQ_TIMEOUT aq_err OK
[78] ice0: ice_read_sff_eeprom: Error reading I2C data: err ICE_ERR_AQ_TIMEOUT aq_err OK
[80] ice0: ice_read_sff_eeprom: Error reading I2C data: err ICE_ERR_AQ_TIMEOUT aq_err OK
[82] ice0: ice_read_sff_eeprom: Error reading I2C data: err ICE_ERR_AQ_TIMEOUT aq_err OK
[85] ice0: ice_read_sff_eeprom: Error reading I2C data: err ICE_ERR_AQ_TIMEOUT aq_err OK
[87] ice0: Failed to set LAN Tx queue 0 (TC 0, handle 0) context, err ICE_ERR_AQ_TIMEOUT aq_err OK
[87] ice0: Unable to configure the main VSI for Tx: ENODEV
[88] ice0: Could not add new MAC filters, err ICE_ERR_AQ_TIMEOUT aq_err OK
[88] ice0: Failed to synchronize multicast filter list: EIO
[89] ice0: Could not add new MAC filters, err ICE_ERR_AQ_TIMEOUT aq_err OK
[89] ice0: Failed to synchronize multicast filter list: EIO
[90] ice0: Could not add new MAC filters, err ICE_ERR_AQ_TIMEOUT aq_err OK
[90] ice0: Failed to synchronize multicast filter list: EIO
[91] ice0: Could not add new MAC filters, err ICE_ERR_AQ_TIMEOUT aq_err OK
[91] ice0: Failed to synchronize multicast filter list: EIO
[92] ice0: Could not add new MAC filters, err ICE_ERR_AQ_TIMEOUT aq_err OK
[92] ice0: Failed to synchronize multicast filter list: EIO
[96] ice0: ice_read_sff_eeprom: Error reading I2C data: err ICE_ERR_AQ_TIMEOUT aq_err OK
[98] ice0: ice_read_sff_eeprom: Error reading I2C data: err ICE_ERR_AQ_TIMEOUT aq_err OK
[100] ice0: ice_read_sff_eeprom: Error reading I2C data: err ICE_ERR_AQ_TIMEOUT aq_err OK
[102] ice0: ice_read_sff_eeprom: Error reading I2C data: err ICE_ERR_AQ_TIMEOUT aq_err OK
ok after playing with FEC settings via sysctl I managed to get it working
had to use requested_fec=rs on WAN and requested_fec=auto on LAN
Well, I've updated mine to the latest version. I've been testing it and it's still working fine, both at 10Gbps and 25Gbps.
dmesg | grep -i ice0
[1] ice0: <Intel(R) Ethernet Network Adapter E810-XXV-4 - 1.43.3-k> mem 0x382000000000-0x382001ffffff,0x382002000000-0x38200200ffff irq 21 at device 0.0 on pci5
[1] ice0: Loading the iflib ice driver
[1] ice0: The driver could not load the DDP package file because a compatible DDP package is already present on the device. The device has package ICE OS Default Package version 1.3.43.0, track id 0xc0000001. The ice_ddp module has package: ICE OS Default Package version 1.3.41.0.
[1] ice0: fw 8.0.2 api 1.7 nvm 5.01 etid 80021faa netlist 4.4.2000-1.18.0.bc358136 oem 1.4031.0
[1] ice0: Using 4 Tx and Rx queues
[1] ice0: Reserving 2 MSI-X interrupts for iRDMA
[1] ice0: Using MSI-X interrupts with 7 vectors
[1] ice0: Using 4096 TX descriptors and 4096 RX descriptors
[1] ice0: Ethernet address: 9c:69:b4:68:65:99
[1] ice0: ice_add_rss_cfg on VSI 0 could not configure every requested hash type
[1] ice0: PCI Express Bus: Speed 8.0GT/s Width x16
[1] ice0: pci_iov_attach failed (error=ENOENT)
[1] ice0: Firmware LLDP agent disabled
[1] ice0: link state changed to DOWN
[1] ice0: netmap queues/slots: TX 4/4096, RX 4/4096
[11] ice0: Link is up, 10 Gbps Full Duplex, Requested FEC: None, Negotiated FEC: None, Autoneg: False, Flow Control: None
[11] ice0: link state changed to UP
[1423] ice0: link state changed to DOWN
[1434] ice0: Link is up, 25 Gbps Full Duplex, Requested FEC: None, Negotiated FEC: None, Autoneg: True, Flow Control: None
[1434] ice0: link state changed to UP
[1434] ice0: Link is up, 25 Gbps Full Duplex, Requested FEC: None, Negotiated FEC: None, Autoneg: True, Flow Control: None
Hm. I updated my main machine (on a physically isolated subnet, so no captures) to NVM 5.01 and booted FreeBSD 14.2 (driver 1.43.2-k) and it seems to work fine. No odd messages. Loads DDP 1.3.41.0. Trying to parse Intel's Feature Support Matrix (https://cdrdv2.intel.com/v1/dl/getContent/630155) when using the OS driver is... well, guesswork. I've never had a problem with an up-version NVM, and Intel's FreeBSD driver (in the 31.2.1 package) is apparently version 2.1.8. I need to reinstall 15.1 on the thing, but it'll take some time.
PoMpls: What does "sysctl dev.ice.0.ddp_version" say?
@pfry
Here you go:
sysctl dev.ice.0.ddp_version
dev.ice.0.ddp_version: ICE OS Default Package version 1.3.43.0, track id 0xc0000001
This is my card; I saw it a while ago for 157€ and bought it without thinking twice: 😀
https://es.aliexpress.com/item/1005006344562349.html?spm=a2g0o.order_list.order_list_main.15.bb2a194dELSfTX&gatewayAdapt=glo2esp
Long story short :
my card E810-XXV-2 - only works on 4.50 NVM in FreeBSD 14 (opnsense 26.1) and 15 (opnsense 26.7)
Any higher NVM fails in initializing TX queues balancing.
But
Higher NVMs work fine in Linux. Driver initializes DDP / TX balancing fine, no issues at all.
I am experiencing a similar issue after updating to opnsense 26.7 using DDP on a 25G link on an Intel E810-XXVDA4. Card negotiates to 1G with no issues with DDP enabled. I have yet to test 10G. Disabling DDP resolves the issue for 25G but that's a workaround for the time being.
sysctl dev.ice.1.fw_version shows: fw 8.0.1 api 1.7 nvm 5.00 etid 80021bd5 netlist 4.4.2000-1.18.0.bc358136 oem 1.4002.0
I'm seeing the same negotiation errors, with the only difference being that my 25G link is on ice1:
Quote from: bugacha on July 16, 2026, 09:17:20 AM[1] ice0: All configured link modes were attempted but failed to establish link.
[1] ice0: The device will restart the process to establish link.
[1] ice0: Possible Solution: Check link partner connection and configuration.
I will try to re-enable DDP tonight to get logs to post here.
Same problem for us.
We are on DEC4280.
We tried updating to latest NVM 5.01 without success
(it was working with nvm 5 on FreeBSD 14.3).
Currently the only way to get link is to not load the ddp package.
I filed bug with FreeBSD 15.3
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=296989
It will take a while until this is fixed tho
Same problem here.
With disabled ddp only about 1G is possible over 2x25G. We switched to an 10G card until this is fixed.
I'm not quiet sure if I have the same issue or something related...
I updated to 26.7 and I stopped getting a link on the E823-L. In addition the System behaved very unstable/slow on 26.7 when trying to login directly on the console. It took several seconds just to show the login prompt.
I'm on NVM 3.26 since my NIC is embedded SOC and Supermicro is not providing a newer OEM FW...
Same problem with no link on 25GbE, running both E810 and E823 and DDP after upgrading to 26.7
Without loading DDP we get link and about 1Gbps throughput on each NIC :/
E810-XXV fw 7.6.2 api 1.7 nvm 4.60
E823-C fw 7.1.6 api 1.7 nvm 3.26
ICE OS Default Package version 1.3.41.0
Upgraded to 26.7.4 as I saw the release notes pointed out that if_ice was updated, no changes, still no link after DDP has loaded.
However I am not sure that the DDP package is?
Has anyone tried to install the newest driver and DDP from Intel 2.1.8?
I have tested to build it on 26.7.4 with the current kernel sources from github, but have not yet tried to install it as I am not quite sure how to perform a roll back and keep future upgrade path clean?
Hello,
thanks to everyone who shared their experience in this thread.
We are currently running OPNsense 26.4.1 which is based on FreeBSD 14 and will stay on that version until the issue described in this thread got fixed.
We are using Intel E810-CQDA2 NIC, NVM version 4.80 which seems to work fine under FreeBSD 14. No issues whatsoever.
The issue described in this thread sounds like a regression in FreeBSD 15.
I think it would be great if we had the option to use the official driver from Intel instead of the one integrated in FreeBSD kernel tree.
Maybe that would solve the issue described here.
If OPNSense Team would decide to build and package the driver from intel and offer it as an optional package, it would be greatly appreciated.
Best regards
https://forum.opnsense.org/index.php?topic=52881.msg274557#msg274557
Quote from: bugacha on July 25, 2026, 10:06:38 AMI filed bug with FreeBSD 15.3
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=296989
It will take a while until this is fixed tho
Looks like there is some movement on this bug and this can be mainlined into 15 version
Added https://github.com/opnsense/src/commit/a5f857190 to stable/26.7 and built a test kernel:
# opnsense-update -zkr 26.7.4-next2
A confirmation would be good because then we can ship it in 26.7.6 next week.
Cheers,
Franco
Quote from: franco on October 05, 2026, 02:57:58 PMAdded https://github.com/opnsense/src/commit/a5f857190 to stable/26.7 and built a test kernel:
# opnsense-update -zkr 26.7.4-next2
A confirmation would be good because then we can ship it in 26.7.6 next week.
Cheers,
Franco
Hi Franco
Can I upgrade from 26.1.11_10 directly to 26.7.4-next2 using this command? Rollback with Snapshot should be fine right?
If not, I cannot test it because with 26.7 I dont get a link even with DDP Package disabled.
cheers
Patrick
Hi Patrick,
Unfortunately the upgrade will want to get the 26.7 kernel. You could try manually booting the 26.7.6 kernel from 26.1.11 which should be fine:
# opnsense-update -fkr 26.7.6 -a FreeBSD:15:amd64/26.7
(reboot)
If it works we can consider bumping the upgrade path from 26.1.11 to 26.7.6. Usually this takes some more time to verify things are still working as expected with the major upgrade also because we have a package manager update in between now.
Cheers,
Franco
26.7.6 also seems to have fixed it for me.
I also had to specify dev.ice.x.requested_fec explicit as RS-FEC, as it did not auto-negotiate successfull after DDP load without it set.
[1] ice0: <Intel(R) Ethernet Controller E810-XXV for SFP - 1.43.3-k> mem 0xc2000000-0xc3ffffff,0xc4010000-0xc401ffff at device 0.0 numa-domain 0 on pci6
[1] ice0: Loading the iflib ice driver
[1] ice0: The DDP package was successfully loaded: ICE OS Default Package version 1.3.41.0, track id 0xc0000001.
[1] ice0: fw 7.6.2 api 1.7 nvm 4.60 etid 8001e8d4 netlist 4.3.4000-4.f.0.493a8aab oem 1.3682.0
[1] ice0: Using 4 Tx and Rx queues
[1] ice0: Reserving 4 MSI-X interrupts for iRDMA
[1] ice0: Using MSI-X interrupts with 9 vectors
[1] ice0: Using 1024 TX descriptors and 1024 RX descriptors
[1] ice0: ice_add_rss_cfg on VSI 0 could not configure every requested hash type
[1] ice0: PCI Express Bus: Speed 16.0GT/s Width x8
[1] ice0: pci_iov_attach failed (error=ENOENT)
[1] ice0: link state changed to UP
[1] ice0: Link is up, 25 Gbps Full Duplex, Requested FEC: None, Negotiated FEC: RS-FEC, Autoneg: False, Flow Control: None
[1] ice0: netmap queues/slots: TX 4/1024, RX 4/1024
[1] ice0: link state changed to DOWN
[4] ice0: All configured link modes were attempted but failed to establish link.
[4] ice0: The device will restart the process to establish link.
[4] ice0: Possible Solution: Check link partner connection and configuration.
[25] ice0: Link is up, 25 Gbps Full Duplex, Requested FEC: RS-FEC, Negotiated FEC: RS-FEC, Autoneg: False, Flow Control: None
[25] ice0: link state changed to UP
[1] ice2: <Intel(R) Ethernet Connection E823-C for SFP - 1.43.3-k> mem 0xd0000000-0xd7ffffff,0xda010000-0xda01ffff at device 0.0 numa-domain 0 on pci8
[1] ice2: Loading the iflib ice driver
[1] ice2: The DDP package was successfully loaded: ICE OS Default Package version 1.3.41.0, track id 0xc0000001.
[1] ice2: fw 7.1.6 api 1.7 nvm 3.26 etid 8001bc8c netlist 0.0.2768-1.14.1.59461500 oem 1.3429.0
[1] ice2: Using 4 Tx and Rx queues
[1] ice2: Reserving 4 MSI-X interrupts for iRDMA
[1] ice2: Using MSI-X interrupts with 9 vectors
[1] ice2: Using 1024 TX descriptors and 1024 RX descriptors
[1] ice2: ice_add_rss_cfg on VSI 0 could not configure every requested hash type
[1] ice2: link state changed to UP
[1] ice2: Link is up, 25 Gbps Full Duplex, Requested FEC: None, Negotiated FEC: RS-FEC, Autoneg: False, Flow Control: None
[1] ice2: netmap queues/slots: TX 4/1024, RX 4/1024
[5] ice2: All configured link modes were attempted but failed to establish link.
[5] ice2: The device will restart the process to establish link.
[5] ice2: Possible Solution: Check link partner connection and configuration.
[5] ice2: link state changed to DOWN
[25] ice2: Link is up, 25 Gbps Full Duplex, Requested FEC: RS-FEC, Negotiated FEC: RS-FEC, Autoneg: False, Flow Control: None
[25] ice2: link state changed to UP
Quote from: franco on October 05, 2026, 02:57:58 PMAdded https://github.com/opnsense/src/commit/a5f857190 to stable/26.7 and built a test kernel:
# opnsense-update -zkr 26.7.4-next2
A confirmation would be good because then we can ship it in 26.7.6 next week.
Cheers,
Franco
Thanks a lot Franco, just upgraded to 26.7.6 and everything works fine now out of Opnsense without the need for SRV-IO stuff in Proxmox.
neat :D
Quote from: franco on October 08, 2026, 02:48:18 PMHi Patrick,
Unfortunately the upgrade will want to get the 26.7 kernel. You could try manually booting the 26.7.6 kernel from 26.1.11 which should be fine:
# opnsense-update -fkr 26.7.6 -a FreeBSD:15:amd64/26.7
(reboot)
If it works we can consider bumping the upgrade path from 26.1.11 to 26.7.6. Usually this takes some more time to verify things are still working as expected with the major upgrade also because we have a package manager update in between now.
Cheers,
Franco
Hey Franco
sorry I couldn't find time earlier for testing...
I just tried the update command and still have no link with the new kernel after reboot.
BUT! I was able to udpate anyway by disabling the DDP Package before the update...
I'm really sorry for the confusion and the false statement from my side! I guess I shouldn't do updates too late in the night...
Bad news... After I was on 26.7.7 I enabled the DDP Package again and had no link after the reboot.
Here are some logs. let me know if you need anything else.
On Version 26.1.11_10 with DDP enabled:
[1] ice0: <Intel(R) Ethernet Connection E823-L for SFP - 1.43.3-k> mem 0xf0000000-0xf7ffffff,0xfa010000-0xfa01ffff at device 0.0 numa-domain 0 on pci10
[1] ice0: Loading the iflib ice driver
[1] ice0: The DDP package was successfully loaded: ICE OS Default Package version 1.3.41.0, track id 0xc0000001.
[1] ice0: fw 7.2.14 api 1.7 nvm 3.42 etid 8001ff0f netlist 0.1.7000-1.25.0.f083a9d5 oem 1.3755.0
[1] ice0: Using 10 Tx and Rx queues
[1] ice0: Reserving 10 MSI-X interrupts for iRDMA
[1] ice0: Using MSI-X interrupts with 21 vectors
[1] ice0: Using 1024 TX descriptors and 1024 RX descriptors
[1] ice0: Ethernet address: ██:██:██:██:██:██
[1] ice0: ice_add_rss_cfg on VSI 0 could not configure every requested hash type
[1] ice0: Firmware LLDP agent disabled
[1] ice0: link state changed to DOWN
[1] ice0: netmap queues/slots: TX 10/1024, RX 10/1024
[2] ice0: All configured link modes were attempted but failed to establish link.
[2] ice0: The device will restart the process to establish link.
[2] ice0: Possible Solution: Check link partner connection and configuration.
[2] ice0: link state changed to UP
[2] ice0: Link is up, 25 Gbps Full Duplex, Requested FEC: RS-FEC, Negotiated FEC: RS-FEC, Autoneg: False, Flow Control: None
[43] ice0: Failed to add VLAN filters:
[43] ice0: - vlan 100, status -14
[43] ice0: Failure adding VLAN 100 to main VSI, err ICE_ERR_ALREADY_EXISTS aq_err OK
On Version 26.7.7 with DDP enabled:
[1] ice0: <Intel(R) Ethernet Connection E823-L for SFP - 1.43.3-k> mem 0xf0000000-0xf7ffffff,0xfa010000-0xfa01ffff at device 0.0 numa-domain 0 on pci10
[1] ice0: Loading the iflib ice driver
[1] ice0: The DDP package was successfully loaded: ICE OS Default Package version 1.3.41.0, track id 0xc0000001.
[1] ice0: fw 7.2.14 api 1.7 nvm 3.42 etid 8001ff0f netlist 0.1.7000-1.25.0.f083a9d5 oem 1.3755.0
[1] ice0: Using 10 Tx and Rx queues
[1] ice0: Reserving 10 MSI-X interrupts for iRDMA
[1] ice0: Using MSI-X interrupts with 21 vectors
[1] ice0: Using 1024 TX descriptors and 1024 RX descriptors
[1] ice0: Ethernet address: ██:██:██:██:██:██
[1] ice0: ice_add_rss_cfg on VSI 0 could not configure every requested hash type
[1] ice0: Firmware LLDP agent disabled
[1] ice0: link state changed to DOWN
[1] ice0: netmap queues/slots: TX 10/1024, RX 10/1024
[9] ice0: All configured link modes were attempted but failed to establish link.
[9] ice0: The device will restart the process to establish link.
[9] ice0: Possible Solution: Check link partner connection and configuration.
[9] ice0: All configured link modes were attempted but failed to establish link.
[9] ice0: The device will restart the process to establish link.
[9] ice0: Possible Solution: Check link partner connection and configuration.
[47] ice0: Failed to add VLAN filters:
[47] ice0: - vlan 100, status -14
[47] ice0: Failure adding VLAN 100 to main VSI, err ICE_ERR_ALREADY_EXISTS aq_err OK
[56] ice0: All configured link modes were attempted but failed to establish link.
[56] ice0: The device will restart the process to establish link.
[56] ice0: Possible Solution: Check link partner connection and configuration.
Quote from: paoba on October 13, 2026, 08:12:10 PMHey Franco
sorry I couldn't find time earlier for testing...
I just tried the update command and still have no link with the new kernel after reboot.
BUT! I was able to udpate anyway by disabling the DDP Package before the update...
I'm really sorry for the confusion and the false statement from my side! I guess I shouldn't do updates too late in the night...
Bad news... After I was on 26.7.7 I enabled the DDP Package again and had no link after the reboot.
Here are some logs. let me know if you need anything else.
On Version 26.7.7 with DDP enabled:
[1] ice0: <Intel(R) Ethernet Connection E823-L for SFP - 1.43.3-k> mem 0xf0000000-0xf7ffffff,0xfa010000-0xfa01ffff at device 0.0 numa-domain 0 on pci10
[1] ice0: Loading the iflib ice driver
[1] ice0: The DDP package was successfully loaded: ICE OS Default Package version 1.3.41.0, track id 0xc0000001.
[1] ice0: fw 7.2.14 api 1.7 nvm 3.42 etid 8001ff0f netlist 0.1.7000-1.25.0.f083a9d5 oem 1.3755.0
[1] ice0: Using 10 Tx and Rx queues
[1] ice0: Reserving 10 MSI-X interrupts for iRDMA
[1] ice0: Using MSI-X interrupts with 21 vectors
[1] ice0: Using 1024 TX descriptors and 1024 RX descriptors
[1] ice0: Ethernet address: ██:██:██:██:██:██
[1] ice0: ice_add_rss_cfg on VSI 0 could not configure every requested hash type
[1] ice0: Firmware LLDP agent disabled
[1] ice0: link state changed to DOWN
[1] ice0: netmap queues/slots: TX 10/1024, RX 10/1024
[9] ice0: All configured link modes were attempted but failed to establish link.
[9] ice0: The device will restart the process to establish link.
[9] ice0: Possible Solution: Check link partner connection and configuration.
[9] ice0: All configured link modes were attempted but failed to establish link.
[9] ice0: The device will restart the process to establish link.
[9] ice0: Possible Solution: Check link partner connection and configuration.
[47] ice0: Failed to add VLAN filters:
[47] ice0: - vlan 100, status -14
[47] ice0: Failure adding VLAN 100 to main VSI, err ICE_ERR_ALREADY_EXISTS aq_err OK
[56] ice0: All configured link modes were attempted but failed to establish link.
[56] ice0: The device will restart the process to establish link.
[56] ice0: Possible Solution: Check link partner connection and configuration.
What FEC settings do you have on the switch for this port ?
Try to play with RS or FC modes to see if link comes up.
From your log, driver and DDP are loaded fine, the issue is physical link which on this card is usually FEC related.
You can also try explicit tunable in Opnsense
dev.ice.0.requested_fec="RS-FEC"
@paoba yeah this seems like a slightly different issue from the pressing DDP load failed and driver doesn't work at all.
Cheers,
Franco
thanks for the heads up! here some more details about my interfaces and my switch. I was supprised my switch thinks the opnsense LAN is connected by Medium-type "Fiber", which is incorrect.
I don't know what FEC settings my internet provider has on their switch, but if required I can open up a ticket to find out.
I will try the tunable for both ports and see what happens after a reboot and also try to upgrade again.
testing tunables:
dev.ice.0.requested_fec="RS-FEC"
dev.ice.1.requested_fec="RS-FEC"
Switch opnsense LAN Port details:
Medium-type is Fiber
Admin duplex mode is AUTO, oper duplex is Full
Admin speed is 25G, oper speed is 25G
Flow control admin status is OFF, flow control oper status is OFF
Admin negotiation mode is OFF, oper negotiation state is OFF
Admin FEC mode is auto, oper FEC mode is rs
LAN Interface (ice0):
dev.ice.0.requested_fec: RS-FEC
dev.ice.0.negotiated_fec: RS-FEC
dev.ice.0.current_speed: 25 Gbps
media: Ethernet autoselect (25G-AUI <full-duplex>)
plugged: SFP/SFP+/SFP28 25GBASE-CR CA-25G-S (Copper pigtail)
WAN Interface (ice1):
dev.ice.1.requested_fec: RS-FEC
dev.ice.1.negotiated_fec: RS-FEC
dev.ice.1.current_speed: 25 Gbps
media: Ethernet autoselect (25GBase-LR <full-duplex>)
plugged: SFP/SFP+/SFP28 100GBASE-LR4 or 25GBASE-LR (LC)
well that worked better than expected... after I set both tunables, I could upgrade without issues!
thanks alot for the help! love this community!
So I guess it's better to keep the tunables in the future? is there anything you need from my side?
here is the dmesg log from 27.7.7:
[1] ice0: <Intel(R) Ethernet Connection E823-L for SFP - 1.43.3-k> mem 0xf0000000-0xf7ffffff,0xfa010000-0xfa01ffff at device 0.0 numa-domain 0 on pci10
[1] ice0: Loading the iflib ice driver
[1] ice0: The DDP package was successfully loaded: ICE OS Default Package version 1.3.41.0, track id 0xc0000001.
[1] ice0: fw 7.2.14 api 1.7 nvm 3.42 etid 8001ff0f netlist 0.1.7000-1.25.0.f083a9d5 oem 1.3755.0
[1] ice0: Using 10 Tx and Rx queues
[1] ice0: Reserving 10 MSI-X interrupts for iRDMA
[1] ice0: Using MSI-X interrupts with 21 vectors
[1] ice0: Using 1024 TX descriptors and 1024 RX descriptors
[1] ice0: Ethernet address: ██:██:██:██:██:██
[1] ice0: ice_add_rss_cfg on VSI 0 could not configure every requested hash type
[1] ice0: Firmware LLDP agent disabled
[1] ice0: link state changed to UP
[1] ice0: Link is up, 25 Gbps Full Duplex, Requested FEC: None, Negotiated FEC: RS-FEC, Autoneg: False, Flow Control: None
[1] ice0: netmap queues/slots: TX 10/1024, RX 10/1024
[1] ice0: link state changed to DOWN
[9] ice0: All configured link modes were attempted but failed to establish link.
[9] ice0: The device will restart the process to establish link.
[9] ice0: Possible Solution: Check link partner connection and configuration.
[47] ice0: Link is up, 25 Gbps Full Duplex, Requested FEC: RS-FEC, Negotiated FEC: RS-FEC, Autoneg: False, Flow Control: None
[47] ice0: link state changed to UP
[48] ice0: Failed to add VLAN filters:
[48] ice0: - vlan 100, status -14
[48] ice0: Failure adding VLAN 100 to main VSI, err ICE_ERR_ALREADY_EXISTS aq_err OK
[1] ice1: <Intel(R) Ethernet Connection E823-L for SFP - 1.43.3-k> mem 0xe8000000-0xefffffff,0xfa000000-0xfa00ffff at device 0.2 numa-domain 0 on pci10
[1] ice1: Loading the iflib ice driver
[1] ice1: DDP package already present on device: ICE OS Default Package version 1.3.41.0, track id 0xc0000001.
[1] ice1: fw 7.2.14 api 1.7 nvm 3.42 etid 8001ff0f netlist 0.1.7000-1.25.0.f083a9d5 oem 1.3755.0
[1] ice1: Using 10 Tx and Rx queues
[1] ice1: Reserving 10 MSI-X interrupts for iRDMA
[1] ice1: Using MSI-X interrupts with 21 vectors
[1] ice1: Using 1024 TX descriptors and 1024 RX descriptors
[1] ice1: Ethernet address: ██:██:██:██:██:██
[1] ice1: ice_add_rss_cfg on VSI 0 could not configure every requested hash type
[1] ice1: Firmware LLDP agent disabled
[1] ice1: link state changed to UP
[1] ice1: Link is up, 25 Gbps Full Duplex, Requested FEC: None, Negotiated FEC: RS-FEC, Autoneg: False, Flow Control: None
[1] ice1: netmap queues/slots: TX 10/1024, RX 10/1024
[6] ice1: All configured link modes were attempted but failed to establish link.
[6] ice1: The device will restart the process to establish link.
[6] ice1: Possible Solution: Check link partner connection and configuration.
[6] ice1: link state changed to DOWN
[46] ice1: Link is up, 25 Gbps Full Duplex, Requested FEC: RS-FEC, Negotiated FEC: RS-FEC, Autoneg: False, Flow Control: None
[46] ice1: link state changed to UP
Nope, that's great news.
I've worked today on enabling the upgrade path to 26.1.11 -> 26.7.7. It looks good from my perspective so expecting this to be live later today.
Cheers,
Franco
Quote from: paoba on October 14, 2026, 12:43:48 PMwell that worked better than expected... after I set both tunables, I could upgrade without issues!
thanks alot for the help! love this community!
So I guess it's better to keep the tunables in the future? is there anything you need from my side?
Yes just keep them.
Something in BSD ICE driver doesn't properly negotiate FEC when network switch is in Auto mode.
I've always had this problem on E810 card.
Linux ICE driver doesn't have this issue.