New Software Support:

- Generic update for FVL, CVL and CPK NIC OEM and FreeBSD 14.1
- New OS support: FreeBSD 14.1
- OpenEuler ARM architecture compatibility
- Introduced ICE driver migration for Linux DPLL interface usage in kernel 6.7
- Devlink support for tools algorithm improvement
- Ethtool flow-type ether support
- 40G ESXi new default VMDq loopback behavior and module parameter
- Message logs related to Health Status 0x110 updated

New Firmware Support:

- Disable Optical Module Laser when Link/Port is disabled on E810
- GET_LLDP type command : get all ports LLDP information on E810.
- Disabling of port 0 (as long it’s not associated with PF 0).
- Use Rx Loss to detect cable disconnect from Module on E810
- Expanding i2c write handling to enable 4 bytes on E810

Hardware/Feature Support:

- UEFI UNDI AVF driver support.
- Removed 100G ESXi configuration of VMDq loopback via intcli

Fixed Issues Intel Ethernet 810 Series:

- General: Fixed probing VF driver on ARM systems.
- General: Empire Flats (E810CQDA2OCPV3G and L) MultiPort power class limits to 3.5W should only be present in CVL4.4, the fix increasing the limit back to 4.5W was taken in all CVL4.5 and later builds. The module’s power requirements exceed the device’s power supply.
- Firmware/NVM/NVM Update: RAMON specific workaround implemented in DreadnoughtLake scripts in case of caui4 no FEC links, was modified being applied only when outer phy is RAMON (and not Parkvale).
- Firmware/NVM/NVM Update: The NetworkDeviceFunction.MTUSize property is changed to reflect the current OS defaults before the user configures specific value.
- Firmware/NVM/NVM Update: Fixed a rare timing issue of nc-si oem command: plug-out optics and plug-in again, BMC can NOT get temperature by reason code 0x5089.
- Firmware/NVM/NVM Update: Removed the need for EMPR after temperature fatal threshold is exceeded.
- Firmware/NVM/NVM Update: When link goes down, recovered clock switches to an incorrect frequency, and the external DPLL shifts the system timing.
- Firmware/NVM/NVM Update: FW incorrectly mapped NC-SI channels to Physical ports when responding to the Intel OEM NC-SI command 0x26 (no other command affected).
- Firmware/NVM/NVM Update: Unsupported SMBus write command caused HW to trigger improperly handled FW behavior, which blocked subsequent SMBus writes other than MCTP.
- Firmware/NVM/NVM Update: If user configured 1G and needs to go back to 10G, not able to do so.
- Firmware/NVM/NVM Update: Fixed PTP Time Error to be under 5 ns when running PTP in Boundary Mode between PF with PKVL PHY and PF w/o PKVL PHY.
- Linux: Celo process may not be ended or killed while exiting application. As the result current console is non responsive. Stability of the system is not endangered and user can start next console session.
- Linux: Fixed adding VF to namespace and setting it to up status producing an error in dmesg, VF now works normally

Fixed Issues Intel Ethernet 700 Series:

- Firmware/NVM/NVM Update: PATCH request with request to change FlowControlConfiguration property returns success, but do not really apply changes.
- Firmware/NVM/NVM Update: LLDP receive property preserves the last received data, even when LLDP traffic doesn't contain the TLV item/data.
- Firmware/NVM/NVM Update: NetworkDeviceFunction schema Ethernet. The MACAddress property is not updated to the value in PATCH JSON. This is a regression. The issue is under investigation.
- Firmware/NVM/NVM Update: PATCH request with request to to change FlowControlConfiguration property returns success, but do not really apply changes. The issue is under investigation.
- Firmware/NVM/NVM Update: Fixed an issue where X710DA2 cannot get SFF temperature when another port is empty.
- ESX Driver: Multicast packets sent from VF are not visible on vmkernel interface connected to the first NIC port in ENS mode. The problem results in packet drop only on vmkernel interface (packets are not seen). This does not affect vf-vf traffic, and this is only an issue when sending multicast packets from VM to vmkernel.
- ESX Driver: When SR-IOV is enabled and VMDQ Loopback is disabled packets between VF-PF and VF-VMXNET3 can be dropped by the hardware when non-default RX queue is used for PF or VMXNet3, so VF-PF and VF-VMXNET3 traffic is disallowed for this configuration.

This download is valid for the products listed below:

- Intel Ethernet Network Adapter E810-XXVDA4 for OCP 3.0
- Intel Ethernet Network Adapter E810-XXVDA2 for OCP 3.0
- Intel Ethernet Network Adapter E810-XXVDA2
- Intel Ethernet Network Adapter E810-XXVDA4
- Intel Ethernet Network Adapter E810-XXVDA4T
- Intel Ethernet Network Adapter I225-T1
- Intel Ethernet Server Adapter I210-T1
- Intel Ethernet Converged Network Adapter X540-T2
- Intel Ethernet Converged Network Adapter X540-T1
- Intel Ethernet Controller X540-AT2
- Intel Ethernet Converged Network Adapter X520-DA1
- Intel Ethernet Converged Network Adapter X550-T1
- Intel Ethernet Controller I350-AM2
- Intel Ethernet Controller I350-BT2
- Intel Ethernet Controller I350-AM4
- Intel Ethernet Controller X540-BT2
- Intel Ethernet Controller X550-AT2
- Intel Ethernet Controller X550-BT2
- Intel Ethernet Server Adapter I350-F2
- Intel Ethernet Server Adapter I350-T4V2
- Intel Ethernet Converged Network Adapter X550-T2
- Intel Ethernet Controller I210-CL
- Intel Ethernet Converged Network Adapter X520-SR2
- Intel Ethernet Converged Network Adapter X520-DA2
- Intel Ethernet Converged Network Adapter X520-LR1
- Intel Ethernet Converged Network Adapter X520-T2
- Intel Ethernet Controller I210-AS
- Intel Ethernet Controller I210-IS
- Intel Ethernet Controller I210-AT
- Intel Ethernet Server Adapter I350-T2V2
- Intel Ethernet Controller X550-AT
- Intel 82599EN 10 Gigabit Ethernet Controller
- 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 82599EB 10 Gigabit Ethernet Controller
- Intel Ethernet Controller I210-CS
- Intel Ethernet Converged Network Adapter X520-SR1
- Intel Ethernet Controller I211-AT

About Wireless LAN Drivers:

Windows OSes usually apply a generic driver that allows systems to recognize the wireless component. However, in order to use all available features of this hardware, you must install the appropriate drivers.

Enabling the wireless card allows systems to read chipset information and manufacturer name, as well as connect to a network without using an Ethernet cable.

Updating the driver version can resolve different compatibility issues, fix related errors spotted throughout the product's usage, add support for new operating systems, improve transfer speed, as well as bring various other changes.

As for applying this release, the installation steps should not pose to much of a challenge since each producer intends to make the procedure as easy as possible: just download the package, run the setup, and follow the on-screen instructions.

Bear in mind that we do not recommend you install this release on OSes other than the specified ones even though other platforms might also be suitable. Also, when the update has finished, do perform a restart to ensure that all changes take effect properly.

Therefore, if you wish to apply this package, click the download button, and setup the wireless card on your system. Moreover, if you want to stay “updated one minute ago,” check with our website as often as possible.