Intel Ethernet Adapter Complete Driver Pack 28.3

New Software Features:

- Added info on issue with CrashDump observed on 4.10.x or 4.9.5 IAVF driver with the combination of 1.13.7 ICE driver
- The Linux ice driver now support internal temperature reading.
- The Linux ice and irdma driver now works together in Active/Active link aggregation group mode.
- The UEFI driver now restores factory settings for Port Options, Virtualization Mode, Transmit Balancing, Wakeon-LAN features.
- EPCT tool enables to enables power delivery control for SFP/QSFP cages.
- The FreeBSD driver now allows to capture RDMA traffic.
- Support for FreeBSD 14.0

New Firmware Support:

Intel Ethernet E810 Series:
- Supports Log of MNG packets for debugging purposes.
- Supports the Redfish base registry and the Error Messages from the registry.
- Supports PLDM Type 4s for FRU data.
- The E810-CQDA2T adapter now supports 2x2x25 Gbps configuration.
- Supports reduced PTP jitter by improved timestamp accuracy and Port timer compensation.
- E810-XXVDA4T and E810-CQDA2T now support DPLL updates.
- Supports shorter DPLL lock time.

Intel Ethernet E820 Series:
- Supports 10GBASE-T copper SFP+ transceivers.
- Supports 100GBASE-KR4 PHY type.

Removed Features:

- Removed Autorun.exe and its associated files from the software download
- End of support for Microsoft Windows Server 2012 and Windows Server 2012 R2
- End of support for Intel I354 Gigabit Ethernet Controller and the E1S driver. This device is no longer supported on any operating system.
- End of support for NVMCheck.

Intel Ethernet 810 Series Fixed Issues:

Linux Driver:
- Previously, when using devlink-rate and custom TX scheduler tree topology in switch mode, setting a node's/leaf's tx_priority ('devlink port function rate set pci// tx_priority 1') along with a BW limitation (for example, tx_max - 'devlink port function rate set pci// tx_max 1Gbit' - on the parent node) could result in starvation of the node/leaf (0 BW on Tx), with a lower priority set, and trigger a Tx hang detection.
- Resolved an issue when DCB configuration was changed to use the firmware agent in willing mode on the first port of a two port card, lldpad core dumps, and the second port of the reported the following messages: [3784.370726] ice 0000:af:00.1: Commit DCB Configuration to the hardware [3784.393109] INFO: Flow control is disabled for this traffic class (0) on this vsi [3784.458480] 8021q: Adding VLAN 0 to HW filter on device eth3. The messages would repeat forever.
- Previously, with the 810 Series 3.2 NVM in the Intel Ethernet Network Adapter E810-CQDA2 card, if the 810 Series 2.2 iavf driver was installed, a fatal error was generated related to pci-aspm.h, and the installation failed.
- Resolved an issue where double VLAN traffic might RSS into the first queue. If configuring VLAN interfaces on PF in a way that results in double VLAN tagging, received double VLAN packets would be concentrated on the first queue of interface.
- Fixed a firmware issue that could result in a firmware reset when some, but not all, ports have flow control enabled.
- Previously, there were unexpected FW logs during some special environments, such as tx_timeout or NVM update.
- Improved driver's robustness when bringing interface up/down with link-down-on-close flag is set and recoverable non-critical error occurs.
- Corrected an issue where upon creating new VLAN devices or setting the port VLAN for the VF device, and the irdma module is also loaded, a system hang might occur.

Firmware/NVM/NVM Update:
- Previously, the PLDM Type 5 Command "Activate Firmware" could potentially cause a subsequent PLDM Type 2 event.
- Resolved an issue where during an ActiveFirmware request coming from Update Agent (BMC) PLDM Type2, a PlatformEventMessage was generated by the Firmware Device (Network Adapter). As a result, the response did not happen, and Update Agent (BMC) treated it as Update Failed.
- Fixed an issue where the UEFI HII interface could not save the setting of virtualization mode.
- Previously, in PLDM Platform Monitoring and Control, the sensor_data_size field of SFP thermal sensor PDR was containing wrong value: unsigned instead of signed char/byte.
- Previously, during ActiveFirmware request coming from Update Agent (BMC) PLDM Type2 PlatformEventMessage was generated by our Firmware Device (Network Adapter). As a result, response did not happen and Update Agent (BMC) treated it as Update Failed.
- Firmware now acquires semaphore before "Load Factory Settings to PFA" and releases it immediately after.
- Firmware now returns PLDM_ERROR_NOT_READY Completion Code instead of generic 0x01(PLDM Base: Error) when firmware is not fully ready after platform reboot.
- Previously, when BMC subscribed to PLDM events, the NIC issued two equivalent redfish events for the different origins (Network Adapter and Port) caused by the same trigger (link state change for given port). This issue caused unnecessary redfish event flood. The resolution was to change firmware design in order to avoid sending multiple redfish events for the same trigger.
- Previously, in Network Controller Sideband Interface after EnableChannel command invoked, the OEM command IANA=0x02A2 GetLldp occasionally returned LLDP TLVs with missing mandatory values for chassis_id and port_id.
- Set packageID SDP to correct values for E810-CQDA1.
- Now the patched property of NetworkDeviceFunction.Ethernet.MACAddress is persistent during reboot. Users can restore to PermanentMACAddress with ResetSettingsToDefaults.

Application Device Queues (ADQ):
- Previously, ADQ dynamically registered and unregistered queue group-specific devlink parameters. Newer kernels (6.2.x and later) expect all devlink parameters to be registered during probe time and unregistered upon device removal. As a result, warning messages were to be expected when ADQ queue groups were created or destroyed for the first time.

Intel Ethernet 820 Series Fixed Issues:

Firmware/NVM/NVM Update:
- Resolved an issue where promiscuous mode did not see all packets; it saw only those packets arriving over the wire; that is, not sent from the same physical function (PF) but a different virtual function (VF).
- Previously, the DCB-MAP Configuration was not displaying on the SUT Interface from the Extreme Switch after enabling the firmware Mode in the SUT.
- Previously, using the EPCT tool to change port configuration required 2 reboots to complete the programming process. Blank mode or PTP initialization failures may be observed after a single reboot and will be resolved after performing a second reboot.
- Resolved an issue where the Get LLDP command (0x28) response used to contain only 2 TLV types. The new implementation requires a third TLV type, which contains a copy of the whole LLDP frame payload.
- Resolved an issue where the BMC was unable to receive packets when DHCPv6 server to client multicast filter is enabled.

Linux Driver:
- Previously, it had been observed in certain scenarios where inner VLAN traffic would concentrate on a single queue, creating packet drops.
- Resolved an issue where drop action was not properly offloaded in hardware when setting was done using Open vSwitch.

Windows Driver:
- Previously, with a Windows host and Linux virtual machine (VM), the last transmit (Tx) queue might not increment when there are multiple Tx queues.
- Fixed an issue when using hardware timestamp an incorrect behavior was observed on the receive (Rx) side. Timestamp was received and no error messages were reported, however its value was 0 and therefore was considered as faulty.

FreeBSD Driver:
- Previously, when a driver was loaded with an empty cage, an Admin Queue (AQ) error was recorded instead of the expected AHS link messages.

LANConf Tool:
- Resolved a limitation of the LANConf tool that only allowed the user to program ID EEPROM on Quad 0. This also meant that each attempt to program ID EEPROM on Quad 1 would cause an update on Quad 0

Intel Ethernet 700 Series Fixed Issues:

Linux Driver:
- Resolved an issue where the DMARemappingCompatible registry was missing in the previous driver.
- Resolved an issue that failed to detect temperature status with latest OOB driver.

Firmware/NVM/NVM Update:
- Previously, for XXV710DA2_9p30_CFGID12p0_OEMGEN_J65979 the configuration files did not contain mention of 0x8000DECD, which is the original factory program image.
- Resolved an issue where POST to the NetworkAdapter.ResetSettingsToDefault looked successful from postman, but after reboot the adapter's Port 1 LLDP setting did not reset to default.
- Previously, there were cases of Fortville disappearing from the PCIe bus during reboot stress testing reported on Icelake-based platforms. These platforms performed a PCIe Hot Reset before asserting PERST# as part of the warm reboot cycle. PERST# is asserted at approximately the end of the Hot Reset, but due mostly to the Fortville LCB implementation, there was a variation in the relative timing of about 65 us, so many edge cases could occur.
- Fixed a wrong demsg message from i40e driver of unsupported SFP+ module type was detected when eeupdate upgrade NVM of x710t2l or x710t4l.

Windows Driver:
- Previously, setting PHY debug mode with disabling link during initialization caused link to go down.
- Previously, during the NVM update the adapter was getting disabled for a long time due to lock in OID_INTEL_FLASH_INFO. As result, the driver was unable to access the NVM timed out quickly.
- Resolved an issue where a rare PCI speed degradation with Gen3 to Gen2 had been seen during extensive link tests after a reset was caused by a core reset on an ICX-D platform.
- NDIS i40eb (X722 NIC) component now supports Japanese in advanced tab language.
- Resolved an issue in Windows Server 2022 where the E1R driver didn't disable auto-negotiation when choosing a specific speed and duplex setting. 

Supported operating systems:

- Microsoft Windows Server 2022
- Microsoft Windows Server 2019, Version 1903
- Microsoft Windows Server 2016
- Microsoft Azure Stack HCI
- Microsoft Windows 11
- Microsoft Windows 10 version 21H2 (build 19044)
- Microsoft Windows 10 RS5, Version 1809 (build 17763)
- Microsoft Windows 10 RS1, Version 1607 (build 14393)
- VMWare ESXi 8.0
- VMware ESXi 7.0 
- Linux Real Time Kernel 5.x and 4.x (only on Intel Ethernet E810 Series)
- Linux, v2.4 kernel or higher
- Red Hat Enterprise Linux (RHEL) 9.3
- Red Hat Enterprise Linux 8.9
- SUSE Linux Enterprise Server (SLES) 15 SP5
- SUSE Linux Enterprise Server 12 SP5
- Canonical Ubuntu 22.04 LTS
- Canonical Ubuntu 20.04 LTS
- Debian 11
- FreeBSD 14.0
- FreeBSD 13.1

This download is valid for the products listed below:

- Intel 82583V Gigabit Ethernet Controller
- Intel 82580DB Gigabit Ethernet Controller
- Intel 82580EB Gigabit Ethernet Controller
- Intel 82579LM Gigabit Ethernet PHY
- Intel 82579V Gigabit Ethernet PHY
- Intel Ethernet Controller I210-AS
- Intel Ethernet Controller I210-AT
- Intel Ethernet Controller I210-CL
- Intel Ethernet Controller I210-CS
- Intel Ethernet Controller I210-IS
- Intel Ethernet Controller I210-IT
- Intel Ethernet Controller I211-AT
- Intel Ethernet Connection I219-LM
- Intel Ethernet Connection I219-V
- Intel Ethernet Connection I218-LM
- Intel Ethernet Connection I218-V
- Intel Ethernet Connection I217-LM
- Intel Ethernet Connection I217-V
- Intel Ethernet Network Connection I347-AT4
- Intel Ethernet Network Adapter I350-T4 for OCP 3.0
- Intel Ethernet Server Adapter I350-F2
- Intel Ethernet Server Adapter I350-F4
- Intel Ethernet Server Adapter I350-T2V2
- Intel Ethernet Server Adapter I350-T4V2
- Intel Ethernet Server Adapter I210-T1
- Intel Ethernet Connection X557-AT
- Intel Ethernet Connection X557-AT2
- Intel Ethernet Connection X557-AT4
- Intel Ethernet Controller X550-AT
- Intel Ethernet Controller X550-AT2
- Intel Ethernet Controller X550-BT2
- Intel Ethernet Controller X540-AT2
- Intel Ethernet Controller X540-BT2
- Intel 82599EB 10 Gigabit Ethernet Controller
- Intel 82599EN 10 Gigabit Ethernet Controller
- Intel 82599ES 10 Gigabit Ethernet Controller
- Intel Ethernet Converged Network Adapter X520-DA1
- Intel Ethernet Converged Network Adapter X520-DA2
- Intel Ethernet Converged Network Adapter X520-LR1
- Intel Ethernet Converged Network Adapter X520-QDA1
- Intel Ethernet Converged Network Adapter X520-SR1
- Intel Ethernet Converged Network Adapter X520-SR2
- Intel Ethernet Converged Network Adapter X520-T2
- Intel Ethernet Server Adapter X520-DA1 for Open Compute Project
- Intel Ethernet Server Adapter X520-DA2
- Intel Ethernet Server Adapter X520-DA2 for Open Compute Project
- Intel Ethernet Converged Network Adapter X550-T1
- Intel Ethernet Converged Network Adapter X550-T2
- Intel Ethernet Controller XXV710-AM1
- Intel Ethernet Controller XXV710-AM2
- Intel Ethernet Controller XL710-AM1
- Intel Ethernet Controller XL710-AM2
- Intel Ethernet Controller XL710-BM1
- Intel Ethernet Controller XL710-BM2
- Intel Ethernet Controller V710-AT2
- Intel Ethernet Controller X710-AM2
- Intel Ethernet Controller X710-AT2
- Intel Ethernet Controller X710-BM2
- Intel Ethernet Controller X710-TM4
- Intel Ethernet Converged Network Adapter XL710-QDA1
- Intel Ethernet Converged Network Adapter XL710-QDA2
- Intel Ethernet Server Adapter XL710-QDA1 for Open Compute Project
- Intel Ethernet Server Adapter XL710-QDA2 for Open Compute Project
- Intel Ethernet Network Adapter I710-T4L for OCP 3.0
- Intel Ethernet Network Adapter I710-T4L
- Intel Ethernet Network Adapter E810-XXVDA2
- Intel Ethernet Network Adapter E810-XXVDA2 for OCP 3.0
- Intel Ethernet Network Adapter E810-XXVDA4
- Intel Ethernet Network Adapter E810-XXVDA4 for OCP 3.0
- Intel Ethernet Network Adapter E810-XXVDA4T
- Intel Ethernet Network Adapter E810-2CQDA2
- Intel Ethernet Network Adapter E810-CQDA1
- Intel Ethernet Network Adapter E810-CQDA1 for OCP
- Intel Ethernet Network Adapter E810-CQDA1 for OCP 3.0
- Intel Ethernet Network Adapter E810-CQDA2
- Intel Ethernet Network Adapter E810-CQDA2 for OCP 3.0
- Intel Ethernet Network Adapter E810-CQDA2T
- Intel Ethernet Controller E810-CAM1
- Intel Ethernet Controller E810-CAM2
- Intel Ethernet Controller E810-XXVAM2
- Intel Ethernet Network Adapter I226-T1
- Intel Ethernet Network Adapter I225-T1
- Intel Ethernet Converged Network Adapter X540-T2
- Intel Ethernet Converged Network Adapter X540-T1
- Intel Ethernet Controller I225-LM
- Intel Ethernet Network Adapter XXV710-DA2
- Intel Ethernet Controller I350-AM2
- Intel Ethernet Controller I350-BT2
- Intel Ethernet Controller I350-AM4
- Intel Ethernet Converged Network Adapter X710-DA4
- Intel Ethernet Converged Network Adapter X710-T4
- Intel Ethernet Converged Network Adapter X710-DA2
- Intel Ethernet Network Adapter XXV710-DA1
- Intel Ethernet Controller I225-IT
- Intel Ethernet Network Adapter XXV710-DA1 for OCP
- Intel Ethernet Network Adapter XXV710-DA2 for OCP
- Intel Ethernet Controller I225-V
- Intel Ethernet Network Adapter X710-DA2 for OCP 3.0
- Intel Ethernet Network Adapter X710-T2L
- Intel Ethernet Network Adapter X710-T2L for OCP 3.0
- Intel Ethernet Network Adapter X710-T4L
- Intel 82598EB 10 Gigabit Ethernet Controller
- Intel Ethernet Network Adapter X710-DA4 for OCP 3.0
- Intel Ethernet Network Adapter X710-T4L for OCP 3.0
- Intel Ethernet Network Adapter XXV710-DA2T
- Intel Ethernet Server Adapter X710-DA2 for OCP
- Intel PRO 1000 PT Dual Port Server Adapter
- Intel PRO 1000 PT Quad Port Low Profile Server Adapter
- Intel PRO 1000 PT Quad Port Server Adapter
- Intel PRO 1000 MF Server Adapter
- Intel PRO 1000 MF Server Adapter (LX)
- Intel PRO 1000 MF Dual Port Server Adapter
- Intel 82597EX 10 Gigabit Ethernet Controller
- Intel Ethernet Connection C827-AM1
- Intel Ethernet Connection C827-IM1
- Intel Ethernet Network Connection OCP X557-T2
- Intel Ethernet Connection XL827-AM1

About Network Adapter Drivers:

When connected, the operating system usually installs a generic driver that helps the computer to recognize the newly attached device.

However, proper software must be applied if you want to make use of all features that the network adapter has available. This task also allows computers to properly recognize all device characteristics such as manufacturer, chipset, technology, and others.

Updating the adapter's drivers and utilities version might improve overall performance and stability, increase transfer speeds, fix different compatibility problems and several network-related errors, as well as bring various other changes.

To install this release, simply get the package, extract it if necessary, run the setup, and follow the instructions displayed on-screen. When done, don't forget to perform a system restart and reconnect the network adapter to make sure that all changes take effect properly.

Without further ado, if you intend to apply this version, click the download button and install the package. Moreover, check with our website as often as possible so that you don't miss a single new release.