© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
1b1ed1a
(Get the code!)
BugLink: https:/
[Impact]
Due to fips for jammy not being available yet, users with requirements to be fips certified or fips compliant have to use focal, and many are finding certain hardware devices do not work on their brand new laptops.
I know of several users who use the following laptops who are missing Ethernet NIC support. In Sustaining Engineering we started a spreadsheet to track them all, and their hardware.
Laptops:
Dell Precision 7670
Dell Precision 5560
Ideally we try and get the Ethernet NIC working by enabling PCI IDs for the Intel e1000e driver, so users can run focal until jammy-fips is available.
[Fix]
commit fb776f5d57ee0f5
Author: Sasha Neftin <email address hidden>
Date: Wed Oct 16 11:08:38 2019 +0300
Subject: e1000e: Add support for Tiger Lake
commit 59e466888038dcb
Author: Sasha Neftin <email address hidden>
Date: Sun Jan 19 13:57:13 2020 +0200
Subject: e1000e: Add support for Alder Lake
commit 563212224b7e7b7
Author: Vitaly Lifshits <email address hidden>
Date: Tue Jan 21 15:46:28 2020 -0800
Subject: e1000e: Add support for Tiger Lake device
commit 639e298f432fb05
Author: Sasha Neftin <email address hidden>
Date: Wed Sep 22 09:55:42 2021 +0300
Subject: e1000e: Fix packet loss on Tiger Lake and later
commit ffd24fa2fcc76ec
Author: Sasha Neftin <email address hidden>
Date: Thu Feb 3 14:21:49 2022 +0200
Subject: e1000e: Correct NVM checksum verification flow
[Testcase]
Use a laptop with a Intel Tiger Lake or Intel Alder Lake architecture, for example:
Dell Precision 7670
Dell Precision 5560
Start the machine up and see if Ethernet comes up and functions.
There is a test kernel available in the following ppa:
If you install the test kernel and reboot, ethernet should work properly.
[Where Problems could occur]
We are enabling hardware support on an older kernel by enabling PCI IDs. There will be users out there with currently broken hardware, and by enabling the NIC to function, will find that their ethernet will suddenly start working. This might be bad if they use wifi or usb ethernet and are not expecting network changes. Users can solve this by unplugging the ethernet cable.
There is also a chance that in some hardware combinations, there might be missing driver support, which causes ethernet to misbehave.
If a regression were to occur, users would need to use the ip command to disable their interfaces while a fix is investigated.