Description of problem: It would be useful to know if an updated version of RHEL 8.2 includes a newer i40e driver and if the driver is available. Version-Release number of selected component (if applicable): The Intel 2.11.29 i40e driver README.txt is the actual release note info -- not the "release note" links I posted previously. See https://downloadmirror.intel.com/29744/eng/README.txt . This is dated April 10, 2020. The Intel 2.12.6 i40e driver README.txt is dated June 18, 2020. See https://downloadmirror.intel.com/29945/eng/readme.txt For reference, the base Intel 2.11.21 driver (which is the same as the Red Hat 2.8.20-k i40e driver) is dated January 7, 2020. See https://downloadmirror.intel.com/29659/eng/README.txt I see from https://access.redhat.com/articles/3078#RHEL8 that the RHEL8.2 was GA on April 28, 2020, and RHEL8.3 was GA on November 3, 2020. This explains why RHEL8.2 included the Red Hat 2.8.20-k i40e driver. How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Upstream linux no longer reports a i40e driver version. It is confusing an misleading because there is no relation between the upstream i40e version and Intels sourceforge driver version. They are 2 different drivers that cannot be compared easily. in RHEL8.4 the driver version changed to report the UTS_RELEASE version instead. Here's the corresponding upstream commit info. commit 34a2a3b83e2caf18ab85627f9c6a78bc0a1d1520 Author: Jeff Kirsher <jeffrey.t.kirsher> Date: Fri May 29 00:18:33 2020 -0700 net/intel: remove driver versions from Intel drivers As with other networking drivers, remove the unnecessary driver version from the Intel drivers. The ethtool driver information and module version will then report the kernel version instead. For ixgbe, i40e and ice drivers, the driver passes the driver version to the firmware to confirm that we are up and running. So we now pass the value of UTS_RELEASE to the firmware. This adminq call is required per the HAS document. The Device then sends an indication to the BMC that the PF driver is present. This is done using Host NC Driver Status Indication in NC-SI Get Link command or via the Host Network Controller Driver Status Change AEN. What the BMC may do with this information is implementation-dependent, but this is a standard NC-SI 1.1 command we honor per the HAS.