Intel PROSet/Network Adapter Driver 27.0 for Windows 8.1 64-bit

What's New in This Release:

 
- Microsoft Windows Server 2022 support for devices based on the following controllers: Intel Ethernet Controller X552 and Intel Ethernet Controller X553

Intel Ethernet 800 Series Fixed Issues:

- Linux: 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: When changing the RSS queue value in VM while Double VLAN is configured, rx_vlano [rx-vlanoffload] may stop incrementing correctly.
- Linux: 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: Rapid unloading and loading of the irdma and ice drivers may cause a kernel panic.
- Linux: 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: 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: 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: QoS bandwidth shaping and priority tagging may not be functional in CentOS 7.2.
- Linux: 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: 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.
- Linux RDMA: RDMA stability at application close is improved with NVM version 3.1+.
- Linux RDMA: Prior to the combination of ice 1.7.16/irdma 1.7.72/NVM 3.1 from Release 26.8, PFC for RDMA traffic was only functional on TC0. With NVMs and drivers (ice-1.7.16 and irdma-1.7.72) from the current Release 26.8, RDMA traffic can be configured for PFC on TCs other than TC0
- Linux RDMA: There might be a PSoD appearing during PF-reset when the NVMe to RDMA connection is active.
- Linux RDMA: 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: 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”.
- ADQ: VXLAN stateless offloads (checksum, TSO) and TC filters directing traffic to a VXLAN interface are not supported with Linux v5.9 or later.
- ADQ: 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 82579LM Gigabit Ethernet PHY
- Intel 82579V 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 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 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 Controller X550-AT2
- Intel Ethernet Controller X550-BT2
- Intel Ethernet Server Adapter I350-F2
- Intel Ethernet Server Adapter I350-T4V2
- Intel Ethernet Network Adapter I350-T4 for OCP 3.0
- 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 82580EB Gigabit Ethernet Controller
- Intel 82599EN 10 Gigabit Ethernet Controller
- Intel Ethernet Controller I210-AT
- Intel Ethernet Server Adapter I350-T2V2
- Intel Ethernet Controller X550-AT
- 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 Server Adapter X520-DA2
- 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.

  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.