Hello Anthony, or anyone else affected, Accepted wireless-regdb into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/wireless- regdb/2018.05.09-0ubuntu1~18.04.1 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: wireless-regdb (Ubuntu Bionic) Status: New => Fix Committed ** Tags removed: verification-done-bionic ** Tags added: verification-needed verification-needed-bionic ** Changed in: wireless-regdb (Ubuntu Xenial) Status: New => Fix Committed ** Tags removed: verification-done-xenial ** Tags added: verification-needed-xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to wireless-regdb in Ubuntu. https://bugs.launchpad.net/bugs/1769980 Title: Intel WiFi Linux driver update for ETSI 5GHz Adaptivity Requirement Status in HWE Next: In Progress Status in OEM Priority Project: Triaged Status in crda package in Ubuntu: Invalid Status in linux package in Ubuntu: Confirmed Status in linux-firmware package in Ubuntu: Fix Released Status in linux-oem package in Ubuntu: New Status in wireless-regdb package in Ubuntu: Fix Released Status in crda source package in Xenial: Invalid Status in linux source package in Xenial: Won't Fix Status in linux-firmware source package in Xenial: Fix Released Status in linux-oem source package in Xenial: In Progress Status in wireless-regdb source package in Xenial: Fix Committed Status in crda source package in Bionic: Invalid Status in linux source package in Bionic: Confirmed Status in linux-firmware source package in Bionic: Fix Released Status in linux-oem source package in Bionic: In Progress Status in wireless-regdb source package in Bionic: Fix Committed Bug description: Intel wireless driver and firmware require updates in order to meet the new ETSI regulation [1] for OEM machines shipped from factories. Intel provided us the following information for what are required to update: 1. Kernel driver: https://patchwork.kernel.org/patch/10322121/ https://patchwork.kernel.org/patch/10312731/ https://patchwork.kernel.org/patch/10312735/ https://patchwork.kernel.org/patch/10312733/ - 7260, 7265, 7265D and 3168 NICs, 4.15 plus above driver patches - 8000 series requires 4.16. - 9000 series requires 4.17. 2. linux-firmware Requires latest versions from linux-firmware.git 3. wireless-regdb update [1] http://www.etsi.org/deliver/etsi_en/301800_301899/301893/02.01.01_60/en_301893v020101p.pdf ----------------------------------------------------------------------- == SRU Justification for linux-firmware == [Impact] Intel released these firmware updates to support the new ETSI 5GHz Adaptivity Requirement, OEM has to meet it in order to ship. [Test Case] Check dmesg to confirm the correct firmware is loaded, make sure the revision is correct, and check wifi can functions properly. [Regression Potential] It is possible that there is regression introduced by Intel's firmware, so should make sure wifi still works properly after the new firmware is used. We have verified the new firmwares of 7260 and 7265D on 4.4 and 4.15 kernels. The 8000 and 9000 series firmwares have newer API versions and will need to confirm with subsequent driver changes. --- wireless-regdb SRU Justification Impact: New regulatory requirements in the EU necessitate updating our wireless regulatory database. Fix: New upstream release. Test Case: Minimal testing would be to reload the regdb (can be done with iw built from git or by rebooting) and verifying that you are able to change regulatory domains (e.g., sudo iw reg set US; iw reg get). Regression Potential: Minimal. Biggest risk would be the inability to load the new database due to the changes in signing, however testing will confirm that appropriate key is present. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1769980/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
