- Support for the Intel Ethernet Connection (20) I219-LM
- Support for the Intel Ethernet Connection (24) I219-LM
- Support for the Intel Ethernet Connection (25) I219-LM
- Support for the Intel Ethernet Connection (26) I219-LM
- Support for the Intel Ethernet Connection (27) I219-LM
- Support for the Intel Ethernet Connection (20) I219-V
- Support for the Intel Ethernet Connection (24) I219-V
- Support for the Intel Ethernet Connection (25) I219-V
- Support for the Intel Ethernet Connection (26) I219-V
- Support for the Intel Ethernet Connection (27) I219-V
- Support for the Intel Ethernet Network Adapter I226-T1
- Resolved an issue where when using certain DDP package versions, 802.1ad type VLANs might not be correctly enabled on SIOV or SR-IOV interfaces.
- Resolved an issue where running traffic via Open vSwitch (when an SR-IOV VF have specific ipv6 address assigned), works for 20min (until the neighbor table is clean on the switch/router) then it stops until IPv6 from VF is deleted.
- Previously, the Switchdev feature's VF to VF communication was not functional in the ice driver versions 1.10.1.2, 1.10.1.2.2, and 1.11.14.
- Resolved an issue where the NVM update process would need Power On Reset on PTP devices unless the user manually turned off PTP activity before the NVM update process was started.
- Resolved an issue where a performance issue caused the GNSS write commands to be delayed and not delivered until the next commands appeared.
- Resolved an issue where modifying inner or outer VLAN offload caps while the link is down might break communications when the link is later brought back up. .
- Resolved an issue for Linux ice driver v1.7.16+ on E810 four-port SKUs where VF could not be created on certain high-core count platform because PF had exhausted all the MSIX interrupts.
- Resolved an issue where repeatedly adding/deleting a VF from a namespace while also repeatedly changing its trust mode status could result in call trace after a significant number of iterations.
- Previously an issue existed in the IAVF driver where the VF couldn’t communicate on inner or outer VLANs if the number of rx queues was modified after switching off VLAN offloads.
- Resolved an issue when spoofchk was turned on, the VF device driver would have pending DMA allocations while it was released from the device.
- Previously a UEFI PXE installation of Red Hat Enterprise Linux 8.4 on a local disk resulted with the system failing to boot.
- Resolved an issue where sometimes the EMP reset via devlink didn't work and consequently the E810 NVM image update with the nvmupdate tool reported an error.
- Resolved an issue where auxiliary module conflicts would be reported between i40e and ice during the generation and installation of Linux rpm packages.
- Resolved an issue where "ethtool -L/G" made E810 link down in Linux Anolis 8.6.
- Previously, during a power cycle, in low probability, E810 25 G adapters showed the wrong media type as other by command "ethtool port-name."
- Resolved an issue where unloading a driver without a DDP profile would disable PF interfaces.
- Limiting the Maximum Bitrate for a Transmit Queue can be enabled by using following sysfs /sys/class/net/
- Previously, the set_irq_affinity script reported errors when more than 64 queues were configured on a server with >64 local cores. This also applies when trying to access any TX queues >=64.
- Windows 11 base driver icea.sys was being placed in system32 instead of the driver store.
- Resolved an issue were an incorrectly interpreted BDF during MCTP Endpoint discovery led to sending PLDM events to a non-existing device.
- Resolved an issue where a failed RDE operation was improperly terminated, and blocked subsequent RDE operations.
- Resolved an issue where the id field of Event BEJ was changed from the originating resource Id as the resource number to a deferred binding resource Id.
- A "Cannot initialize port" failure occurs when running nvmupdate 1.39.32.6 in SLES15SP3, because the tool doesn't support ioctl.
- A SyncE-related transaction between driver and device may cause a PHY loading failure, during NVM upgrade. Subsequently, PHY errors are reported to UEFI driver during reboot, resulting in a BIOS hang.
- Resolved an issue where E810-XXV-4T didn't expose one of the On Chip thermal sensors via PLDM. The sensor was not visible via BMC.
- Resolved an issue where CVL4.1 and CVL4.2 had a problem with Recovery Clock configuration on port 4, in the case of fully reversed PF<>MAC mapping. Other configurations were not impacted.
- Resolved an issue where the NC-SI "Reset Channel" (0x05) command was not reverting the port link state change made by for Real Time Comprehensive Embedded Management "Network Port Control' (0x34) command.
- Resolved an issue where, during communication via PLDM Type 6, FW did not move the operation to the failed state and did not return INVALID_DATA. Instead, it returned UNSUPPORTED in the case of an invalid payload.
- Reverted an incorrectly added strict handling of the payload-less action.
- Resolved an issue where the Network Device and Port Metrics are disabled due to an BMC issue and missing support on BMC side.
- Resolved an issue where in order to change the Forward Error Correction setting in the UEFI HII the user needs to change the Media detection setting, save the changes, and then change the FEC setting.
- Previously, promiscuous mode did not see all packets; it only saw those packets arriving over the wire (that is, not sent from the same physical function (PF) but a different virtual function (VF).
- Resolved an issue where during the second time of a POST operation, NetworkAdapter.ResetSettingsToDefault failed with the BMC reporting "Internal Server Error."
- Resolved an issue when both RMII-based transport (RBT) and Management Component Transport Protocol (MCTP) were enabled, and PT was enabled on RBT, then OEM command 0x26 (config LLDP) was being rejected from NC-SI over MCTP with reason code 0x5081.
- Corrected an issue where updating an NVM image of E810 could result in a "PHY NVM is not supported in devlink" warning message.
- Previously, E8102CQDA2 adapter showed Linkcap width as x16.
- Support for ioctl in interactive mode was added in version 1.39.45.2
- Previously during MCTP Endpoint discovery, an incorrectly interpreted BDF led to sending PLDM events to non-existing devices.
- Resolved an issue where on some systems, after making the NVMUpdate with delayed reboot, FW reset (EMPR) was required to complete the update and might fail.
- Resolved an issue where excessive VF reset might cause multicast ping from VF to fail.
- Resolve the issue where the output of the PTP signal might have a period different than the one configured.
- Previously, encapsulated packets with inner packet padding were reported as packets with incorrect checksum. Driver collected these statistics and passed to the networking stack, which resulted in high pNIC error alarm raised by the OS.
- Resolved an issue where during successive driver unload/load cycles, single-port adapters might experience initialization failure when 5-layer topology is enabled.
- Resolved an issue where at the end of an NVMUpdate or NURA tool execution, after the NVM has finished updating, the tool might indicate that an EMP reset failed while the adapter continues to work normally and NVMupdate indicates that the update was successful.
- Resolved several errors seen in dmesg when trying to re-establish link after an nvmupdate.
- Corrected an issue where eeupdate could not update the serial mac address of E810 when port 0 mac address was changed.
- Resolved an issue where a PHY DOWNGRADE configuration file entry was incorrectly handled in some scenarios.
- Resolved an issue where cage power limit was not properly reported when NVM had a lower limit than the netlist, which could potentially could result in a power over-budget.
- Resolved issue where the AQ commands Get Input Frequency List (0x0C6C) and Get Output Frequency List (0x0C6D) returned an empty list of allowed frequencies. The commands now return the correct list of allowed frequencies.
- Resolved an issue where Real Time Comprehensive Embedded Management NC-SI command "Get Temperature" (0x13) was always responding with Response Code: Command Completed (0x3), Reason Code: Unknown/Unsupported Command Type (0x7fff), without providing values.
- Resolved an issue where a power over limit was not reported in the 'Invalid node max power limit' bit (Byte1, bit7) of the Get Link Status AQ output.
- Resolve an issue where the Subvendor ID and Subsystem ID in pcie space was not overridden with the value configured in IDEEPROM after upgrade MezzCard EEPROM. Now SVID and SSID application flow is implemented in FW.
- Resolved an issue where it was possible to use out-of-range clock_ref values in commands 0x0C62/0x0C63/0x0C64/0x0C65. Now input is allowed only within range of 0x00-0x1F and everything outside this range will cause EINVAL.
- Resolved an issue where using the EPCT tool, after switching the QSFP PKVL VMC to 4x25, resulting in the driver no longer being able to attach to interfaces. The only way to restore the device was to re-flash the NVM using LanConf.
- Resolved an issue where you might encounter the following situation:
a) Update is done on a device with an external programmable PHY FW.
b) Update is for a new MAC FW, but PHY FW included in the update is identical to that already on the device.
- Resolved an issue where changing the FEC value from BaseR to RS resulted in an error message in dmesg, and might result in link issues.
- Resolved an issue where all POR CFGs with the Coppervale (CPVL) Phy like CFG2.1, CFG5.x and CFG7.0-CPVL wouldn't link after forcing link mode with ethtool.
- It is no longer expect that the Single Root I/O Virtualization interface (SR-IOV) might fail when running with a 50 G image on 100 G Si.
- Resolved an issue where after a power reset, or update, FW phy/link commands decline requests during this time resulting in PHY NVM update failing due to incomplete link initialization procedure.
- Resolved an issue where DefaultQueueVmmqQueuePairs for the virtual switch could not be set to more than 2 for default/main vport. Now, the number of queue pair for the default vport provided during creating a virtual switch is honored and setting the queue count accordingly.
- Resolved an issue where a ptp4l run failure with multi-master was causing a limitation, and the user needed to avoid running multiple ptp4l instances in one quad.
- Resolved an issue with ptp4l run timeout in non-pf0 ports with the ice 1.11.3 driver.
- Resolved an issue where a rare PCI speed degradation with Gen3 to Gen2 was seen during extensive link tests after a reset is caused by a core reset on an ICX-D platform.
- Resolved an issue where in RDE's LLDPEnabled implementation, the function responsible for the NVM write does not check the validity bit of the settings saved in NVM. This caused a skip of write to NVM in some cases.
- Resolved an issue where during a write, with http PATCH method triggered, the LLDP Disable Valid bit was ignored, which resulted in a skip of write in all scenarios instead of just for the same LLLDP Enabled value.
- Resolved an issue where if BMC bonding was disabled, NCSI mode was set to a Manual Switch Mode (depending on the platform), and BMC share port has changed before doing a power cycle, recovery mode would occur. Other prerequisites include disabled WOL, disabled LLDP, enabled PXE no drop, and disabled auto power-on after power loss (in BIOS).
- Fixed an issue where the processing port id was always the same as the mac address.
- Previously, the addition of PCIe re-timers added to the total channel latency causing replay timer timeout correctable errors.
- Resolved an issue where PLDM type MCTP packets were not accepted due to missing configuration for PCIe VDM.
- Resolved an issue where the following message was appearing in the system log: For Intel I350 NIC, "Source:NDIS, ID:10400" of warning log will be registered on system log on Windows Server 2019.
- Previously, DIRID DefaultDestDir values were showing 11 on Windows 11 instead of 13.
- Intel 82579LM Gigabit Ethernet PHY
- Intel Ethernet Connection I217-LM
- Intel Ethernet Connection I218-LM
- 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 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 Controller X550-BT2
- 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 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 Converged Network Adapter X550-T2
- Intel Ethernet Network Adapter XXV710-DA1
- Intel Ethernet Controller X710-AT2
- 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 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-XXVDA2 for OCP 3.0
- Intel Ethernet Controller I210-AS
- Intel Ethernet Controller I210-IS
- Intel Ethernet Controller XL710-BM1
- Intel Ethernet Controller XL710-BM2
- Intel Ethernet Controller X710-BM2
- 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 Controller I210-AT
- Intel Ethernet Server Adapter I350-T2V2
- Intel Ethernet Network Adapter E810-CQDA1 for OCP
- Intel Ethernet Server Adapter X710-DA2 for OCP
- Intel 82599ES 10 Gigabit Ethernet Controller
- Intel Ethernet Controller X550-AT
- Intel Ethernet Controller XXV710-AM1
- Intel 82599EN 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 Controller XXV710-AM2
- Intel Ethernet Controller XL710-AM1
- Intel Ethernet Server Adapter X520-DA2
- Intel Ethernet Connection X557-AT
- Intel Ethernet Converged Network Adapter X520-SR1
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.
Top 4 Download periodically updates information of Intel PROSet/Network Adapter Driver 28.2 for Server 2016 full driver from the manufacturer, but some information may be slightly out-of-date.
Using warez version of Intel PROSet/Network Adapter Driver 28.2 for Server 2016 driver is hazardous. Our driver download links are directly from our mirrors or publisher's website, Intel PROSet/Network Adapter Driver 28.2 for Server 2016 torrent files or shared files from free file sharing and free upload services, including Rapidshare, HellShare, HotFile, FileServe, MegaUpload, YouSendIt, MailBigFile, DropSend, MediaMax, zUpload, MyOtherDrive, SendSpace, DepositFiles, Letitbit, LeapFile, DivShare or MediaFire, are not allowed!
It is not recommended to download drivers from illegal sites which distribute a keygens, key generators, pirate keys, serial numbers, warez full versions or cracks for Intel PROSet/Network Adapter Driver 28.2 for Server 2016. These drivers might corrupt your computer installation or breach your privacy. A driver might contain a trojan horse opening a backdoor on your computer. Hackers can use this backdoor to take control of your computer, copy data from your computer or to use your computer to distribute viruses and spam to other people.
Download Now
Update All Drivers