Intel Ethernet Adapter Complete Driver Pack 26.8

What's New in This Release:

 
- Linux support for Intel Ethernet Network Adapter E810-XXV-4T
- Intel Ethernet 800 Series devices support RDMA in a Linux VF on a Microsoft Windows or Linux host 
- FreeBSD drivers now support DCB on Intel Ethernet 800 Series devices
- Support for Red Hat Enterprise Linux (RHEL) 8.5 on Intel Ethernet 800 Series devices 
- Limited support for the Linux ice driver on CentOS/RHEL 7.2. No new features were added; only limited regression to find and address issues with the ice driver.
- Support for Red Hat Enterprise Linux (RHEL) 8.5.
- The Intel Ethernet Network Adapter E810-XXV-2 for OCP 2.0 is no longer supported. Release 26.7 is the last release that supports Intel Ethernet Network Adapter E810-XXV-2 for OCP 2.0

Intel Ethernet 800 Series Fixed Issues:

- Linux Driver: Linux ice driver versions 1.4.x through 1.6.x have a performance regression that affects NVMe over Fabric baseline TCP performance using interrupt mode. This issue impacts interrupt mode workloads only; there is no impact to workloads using busy poll mode, such as ADQ. Fixed in ice 1.7.x and above.
- Linux Driver: When changing the RSS queue value in VM while Double VLAN is configured, rx_vlano [rx-vlanoffload] may stop incrementing correctly.
- Linux Driver: For configurations in which a VF is attached to a VM, avoid setting the MTU value of the VF within the range of 9199-9202. When the MTU is set to one of these values the VM may experience a memory leak leading to kernel panic when TCP traffic is running from a link partner to the VF.
- Linux Driver: Rapid unloading and loading of the irdma and ice drivers may cause a kernel panic.
- Linux Driver: There was a statistics issue where ifconfig/ip -s link show could potentially show overall statistics counting backwards due to a timing issue in stats collection. Ethtool -S statistics were unaffected by this issue and would show correct counts. This issue is fixed in ice driver 1.7.x and above.
- Linux Driver: Packets received during the driver load are displayed as dropped because the packet drop counter was started before the driver was fully loaded. This was a cosmetic issue with no functional impact other than an increase in the dropped packets count. This issue is fixed in 1.7.x and above
- Linux Driver: On CentOS 7.2, ethtool may report Speed as Unknown and you may see warnings in dmesg log. This does not affect traffic or device functionality.
- Linux Driver: QoS bandwidth shaping and priority tagging may not be functional in CentOS 7.2.
- Linux Driver: When double VLAN or Queue in Queue feature is enabled, the inner most traffic source might need to be limited to an MTU size of 1496 or less to avoid connection issues.
- Linux Driver: When using Double VLAN configuration with a specific non-Intel link partner, TCP traffic might fail to pass through the inner VLAN interface when the MTU of this interface matches the MTU of the outer VLAN interface. Workaround: change MTU of inner VLAN to be 4 bytes less than the MTU of the outer VLAN.
- Windows Driver: Running the command /dxsetup.exe PROSET=0 ANS=0 was resulting in an initialization of a logging subsystem that is no longer used. Subsequently, this resulted in the file rule.txt being created on the system under C:. The issue has been resolved and the rule.txt file is no longer created.
- Linux RDMA Driver: RDMA stability at application close is improved with NVM version 3.1+.
- Linux RDMA Driver: Prior to the combination of ice/irdma/nvm (insert 3.1 versions here), PFC for RDMA traffic was only functional on TC0. With nvm 3.1+/ice 1.7.x+/irdma 1.7.x (insert 3.1 versions here), RDMA traffic can be configured for PFC on TCs other than TC0.
- Linux RDMA Driver: There might be a PSoD appearing during PF-reset when the NVMe to RDMA connection is active.
- Linux RDMA Driver: In order to send or receive RDMA traffic, the network interface associated with the RDMA device must be up. If the network interface experiences a link down event (for example, a disconnected cable or ip link set down), the associated RDMA device is removed and no longer available to RDMA applications. When the network interface link is restored, the RDMA device is automatically re-added.
- Linux RDMA Driver: After a system reboot, an Intel Ethernet Network Adapter E810 RDMA device in RoCEv2 mode might occasionally become active with a missing or incorrect GID. To correct the GID value, unload and reload the irdma driver.
- Firmware: FW treated SFI C2C as type SFF PHY, which caused a BMC link down.
- Firmware: When the admin queue command was executed to get the PHY recovery clock (0x0631), it was missing the Port number in the AQC.
- Firmware: The interface type was displayed as twisted pair instead of optical fiber.
- Firmware: Fixed an issue on the Intel Ethernet Network Adapter XXVDA4T where external PHYs do not report temperature correctly.
- Firmware: The PackageID0 SDP0 and PackageID1 SDP1 no longer have wrong assignments to the SDP PINs.
- Firmware: The NC-SI OEM command (0x4B) no longer fails.
- Firmware: Fixed an issue when the FW has not been properly mapped from the physical port to logical to get interface sensors.
- Firmware: Fixed an issue when the FW tries to read the PHY threshold even when the module does not that sensor.
- Firmware: Fixed an issue where the FW was trying to get power consumer parameters on a module that was not present.
- Firmware: Fixed an issue where the FW was handling GPIO interrupts before the board initialization was complete.
- Firmware: Fixed an issue where the FW PLDM command GetFirmwareParameters contains additional null characters.
- Firmware: Fixed an issue where the FW was reporting a module power value of module from an incorrect location.
- Firmware: FW maps the wrong cage index to logical port 0. As a result, customers may see the link API get an incorrect indication for the cage index related to logical port 0.
- Firmware: For PLDM Type 2 the device reports the port thermal sensor PDR and status for all types of connectivity; even those without temp sensor (temperature and thresholds reported as zeros).
- Manageability: When bifurcation is enabled on the Chapman Beach adapter, both Intel Ethernet 800 Series Adapters set the NC-SI Package ID as “0”.
- Application Device Queues (ADQ): VXLAN stateless offloads (checksum, TSO) and TC filters directing traffic to a VXLAN interface are not supported with Linux v5.9 or later.

Intel Ethernet 700 Series Fixed Issues:

- When using multiple Traffic Classes (TCs) for ADQ application traffic, adding ntuple rules to the first queue of TC2 or higher does not work as expected. The ethtool ntuple rule fails for the first queue. This does not affect ntuple rules on TC1.

This download is valid for the products listed below:

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

About Ethernet Drivers:

Windows platforms generally apply a generic driver that allows motherboards to recognize the Ethernet component.

However, in order to make use of all network card (adapter) features, you must install a proper LAN driver that enables the hardware. This task enables systems to connect to a network, as well as collect all component characteristics such as manufacturer and chipset.

If you intend to update the driver version, know that this process can add support for new OSes, fix different compatibility problems, resolve related errors encountered during the product's lifetime, as well as include various other changes.

When it comes to the actual installation procedure, we should note that most producers try to make it as easy as possible, so following the steps should be a breeze: just get the downloadable package, run the setup, and follow the on-screen instructions.

There is a chance that other OSes could also be suitable, but it is not advisable that you install this release on platforms other than the specified ones. Remember to perform a system reboot once done, to allow all changes to take effect properly.

Therefore, if you wish to apply this version, click on the download button and enable your network card. To stay up to speed with the latest updates, check back with our website as often as possible.

  It is highly recommended to always use the most recent driver version available.

Try to set a system restore point before installing a device driver. This will help if you installed an incorrect or mismatched driver. Problems can arise when your hardware device is too old or not supported any longer.