[Kernel-packages] [Bug 1748983] Re: Generate per-machine MOK for dkms signing
This seems to be causing a regression with the bcmwl driver, see https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1818134 for further details. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dkms in Ubuntu. https://bugs.launchpad.net/bugs/1748983 Title: Generate per-machine MOK for dkms signing Status in dkms package in Ubuntu: Fix Released Status in shim-signed package in Ubuntu: Fix Released Status in dkms source package in Trusty: Fix Released Status in shim-signed source package in Trusty: Fix Released Status in dkms source package in Xenial: Fix Released Status in shim-signed source package in Xenial: Fix Released Bug description: [SRU Justification] Move to using self-signed keys for signing DKMS modules, along with the wizard / guide to make this work properly, to let third-party modules be signed and loaded by enforcing kernels, rather than disabling Secure Boot altogether. [Test case] 1) Install Ubuntu in UEFI mode. 2) Install bbswitch-dkms (or another -dkms package if useful on your system). 3) Follow the steps in the debconf prompts (enter a password, remember the password for next boot). 4) Reboot; follow the steps in MokManagerL 4a) Pick Enroll MOK: add the new key, enter the password when prompted to do so. 4b) If a dkms package was previously installed on the system (so Secure Boot is currently disabled in shim), pick "Change Secure Boot state". Follow the prompts to enter password characters. The option will only show up if Secure Boot validation was found to be disabled. 5) Pick "Reboot". 6) Log in and verify that the dkms module is loaded, using "lsmod | grep ". 7) Run 'modprobe ' to validate that the module can be loaded explicilty. 8) Validate that there are no errors from modprobe or errors in dmesg concerning signing keys. [Regression potential] If anything currently relies on Secure Boot validation being disabled in order to correctly run with an enforcing kernel, or grub is used in enforcing mode, custom / third-party kernels and modules may fail to load. --- shim-signed's update-secureboot-policy should allow creating a machine-owner key, and using this for signing kernel modules built via DKMS. Key generation and enrolling should be made as easy as possible for users. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1748983/+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
[Kernel-packages] [Bug 1818134] Re: modprobe: ERROR: could not insert 'wl': Package not installed ubuntu14.04.5LTS kernel 3.13.0-165-generic
I've done some more investigation this morning, and I think I've narrowed down the problem slightly further. It seems I *can* upgrade 'dkms' (and also install 'shim'), as long as I leave 'shim-signed' uninstalled, although this has a few caveats... It seems if I 'sudo apt-get purge bcmwl-kernel-source && sudo apt-get install bcmwl-kernel-source' while the 'shim-signed' package is installed, then this builds a "broken" 'wl' module which always gives the message 'modprobe: ERROR: could not insert 'wl': Package not installed' when you try to modprobe it (even after purging 'shim-signed' and rebooting). However if I 'sudo apt-get purge bcmwl-kernel-source && sudo apt-get install bcmwl-kernel-source' while the 'shim-signed' package is NOT installed, then this builds a 'wl' module which works (even after installing 'shim-signed'). I also updated the BIOS on my XPS 13 9343 to version A19, but this made no difference. Because installing or uninstalling 'shim-signed' doesn't automatically rebuild DKMS modules, this means you can easily get into some confusing "conflicting" states, e.g. you can purge-and-install 'bcmwl-kernel- source' while 'shim-signed' isn't installed (to get a working 'wl' module), and then install 'shim-signed', and your WiFi will remain working (with the old module), but the next time your DKMS modules get rebuilt your WiFi will suddenly stop working (with the newly-built module). I know very little about kernel modules and secureboot, but from what I can tell this is possibly a regression caused by https://bugs.launchpad.net/ubuntu/+source/shim-signed/+bug/1748983 interacting with e.g. https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1572659 ** Also affects: shim-signed (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1818134 Title: modprobe: ERROR: could not insert 'wl': Package not installed ubuntu14.04.5LTS kernel 3.13.0-165-generic Status in bcmwl package in Ubuntu: Confirmed Status in shim-signed package in Ubuntu: New Bug description: when installing bcmwl-kernel-source to build wl.ko package version: 6.30.223.248+bdcom-0ubuntu0.2 Expected behavior: kernel module wl.ko loads. What happened: finit_module returns ENOPKG My device is: BCM4352 [14e4:43b1] (rev 03) Happened after latest OS update, downgrading kernel to 164 did not fix, downgrading package did not work. secure boot mode is off. A few others are having this issue https://ubuntuforums.org/showthread.php?t=2413303 There is a possibility it is a modaliases problem -- 2015 chagelog states that there was a capitalization problem, but I don't know how to check this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1818134/+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
[Kernel-packages] [Bug 1818134] Re: modprobe: ERROR: could not insert 'wl': Package not installed ubuntu14.04.5LTS kernel 3.13.0-165-generic
I had a look at my Updates history in Ubuntu Software Centre for the
last couple of weeks to see if I could spot any "likely culprits", and I
see that on the 18th February the 'dkms' package got bumped from
2.2.0.3-1.1ubuntu5.14.04.9 to 2.2.0.3-1.1ubuntu5.14.04.10 and the 'shim-
signed' package got bumped from 1.33.1~14.0.4.3+13-0ubuntu2 to
1.33.1~14.0.4.4+13-0ubuntu2
I found https://askubuntu.com/questions/138284/how-to-downgrade-a
-package-via-apt-get and 'apt-cache policy dkms' tells me that only
versions 2.2.0.3-1.1ubuntu5.14.04.10 , 2.2.0.3-1.1ubuntu5.14.04.5 and
2.2.0.3-1.1ubuntu5 are available (not 2.2.0.3-1.1ubuntu5.14.04.9), so I
tried 'sudo aptitude install dkms=2.2.0.3-1.1ubuntu5.14.04.5` and got
the following output:
The following packages will be DOWNGRADED:
dkms
0 packages upgraded, 0 newly installed, 1 downgraded, 0 to remove and 0 not
upgraded.
Need to get 65.4 kB of archives. After unpacking 3,072 B will be freed.
The following packages have unmet dependencies:
shim-signed : Breaks: dkms (< 2.2.0.3-1.1ubuntu5.14.04.10) but
2.2.0.3-1.1ubuntu5.14.04.5 is to be installed.
The following actions will resolve these dependencies:
Remove the following packages:
1) shim-signed
Accept this solution? [Y/n/q/?]
The following packages will be DOWNGRADED:
dkms
The following packages will be REMOVED:
shim{u} shim-signed{a}
0 packages upgraded, 0 newly installed, 1 downgraded, 2 to remove and 0 not
upgraded.
Need to get 65.4 kB of archives. After unpacking 3,743 kB will be freed.
Do you want to continue? [Y/n/?]
Get: 1 http://gb.archive.ubuntu.com/ubuntu/ trusty-security/main dkms all
2.2.0.3-1.1ubuntu5.14.04.5 [65.4 kB]
Fetched 65.4 kB in 0s (469 kB/s)
(Reading database ... 483437 files and directories currently installed.)
Removing shim-signed (1.33.1~14.04.4+13-0ubuntu2) ...
Removing shim (13-0ubuntu2) ...
dpkg: warning: downgrading dkms from 2.2.0.3-1.1ubuntu5.14.04.10 to
2.2.0.3-1.1ubuntu5.14.04.5
(Reading database ... 483420 files and directories currently installed.)
Preparing to unpack .../dkms_2.2.0.3-1.1ubuntu5.14.04.5_all.deb ...
Unpacking dkms (2.2.0.3-1.1ubuntu5.14.04.5) over (2.2.0.3-1.1ubuntu5.14.04.10)
...
Processing triggers for man-db (2.6.7.1-1ubuntu1) ...
Setting up dkms (2.2.0.3-1.1ubuntu5.14.04.5) ...
I then rebooted, and Wifi still wasn't working, so I did 'sudo apt-get purge
bcmwl-kernel-source && sudo apt-get install bcmwl-kernel-source' and the Wifi
device re-appeared in my Connections menu but said "device not ready" so I did
another reboot, and my Wifi is now working again! Hooray :-D
So there's obviously some strange "interaction" between bcmwl-kernel-
source, dkms and shim-signed ? I have no idea which package this bug
should be filed against / moved to.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bcmwl in Ubuntu.
https://bugs.launchpad.net/bugs/1818134
Title:
modprobe: ERROR: could not insert 'wl': Package not installed
ubuntu14.04.5LTS kernel 3.13.0-165-generic
Status in bcmwl package in Ubuntu:
Confirmed
Bug description:
when installing bcmwl-kernel-source to build wl.ko
package version: 6.30.223.248+bdcom-0ubuntu0.2
Expected behavior: kernel module wl.ko loads.
What happened: finit_module returns ENOPKG
My device is: BCM4352 [14e4:43b1] (rev 03)
Happened after latest OS update, downgrading kernel to 164 did not
fix, downgrading package did not work.
secure boot mode is off.
A few others are having this issue
https://ubuntuforums.org/showthread.php?t=2413303
There is a possibility it is a modaliases problem -- 2015 chagelog
states that there was a capitalization problem, but I don't know how
to check this.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1818134/+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
[Kernel-packages] [Bug 1818134] Re: modprobe: ERROR: could not insert 'wl': Package not installed ubuntu14.04.5LTS kernel 3.13.0-165-generic
I'm also seeing the same problem on a Dell XPS 13 9343 - Wifi is suddenly non-functional, whereas it'd otherwise been working fine for many years (I'm unsure exactly when the problem started, as I mostly use my laptop via wired ethernet, but it's definitely broken within the last couple of weeks). I've tried booting the previous kernel 3.19.0-80-generic from the grub boot menu, but that also results in non-functional wifi. I've included (hopefully) relevant info below, but please let me know if there's anything else I can do to help. $ cat /etc/issue Ubuntu 14.04.5 LTS \n \l $ uname -a Linux shyknee 3.19.0-82-generic #90~14.04.1-Ubuntu SMP Thu Feb 23 01:12:44 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux $ sudo lshw -C network *-network UNCLAIMED description: Network controller product: BCM4352 802.11ac Wireless Network Adapter vendor: Broadcom Corporation physical id: 0 bus info: pci@:02:00.0 version: 03 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress cap_list configuration: latency=0 resources: memory:f720-f7207fff memory:f700-f71f *-network description: Ethernet interface physical id: 2 logical name: eth1 serial: 00:50:b6:0f:5d:ca size: 100Mbit/s capacity: 100Mbit/s capabilities: ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=asix driverversion=22-Dec-2011 duplex=full firmware=ASIX AX88772B USB 2.0 Ethernet ip=192.168.0.54 link=yes multicast=yes port=MII speed=100Mbit/s $ sudo apt-get purge bcmwl-kernel-source Reading package lists... Done Building dependency tree Reading state information... Done The following packages will be REMOVED bcmwl-kernel-source* 0 to upgrade, 0 to newly install, 1 to remove and 0 not to upgrade. After this operation, 8,045 kB disk space will be freed. Do you want to continue? [Y/n] (Reading database ... 483437 files and directories currently installed.) Removing bcmwl-kernel-source (6.30.223.248+bdcom-0ubuntu0.2) ... Removing all DKMS Modules Done. update-initramfs: deferring update (trigger activated) Purging configuration files for bcmwl-kernel-source (6.30.223.248+bdcom-0ubuntu0.2) ... update-initramfs: deferring update (trigger activated) Processing triggers for initramfs-tools (0.103ubuntu4.11) ... update-initramfs: Generating /boot/initrd.img-3.19.0-82-generic $ sudo apt-get install bcmwl-kernel-source Reading package lists... Done Building dependency tree Reading state information... Done The following NEW packages will be installed bcmwl-kernel-source 0 to upgrade, 1 to newly install, 0 to remove and 0 not to upgrade. Need to get 0 B/1,511 kB of archives. After this operation, 8,045 kB of additional disk space will be used. Selecting previously unselected package bcmwl-kernel-source. (Reading database ... 483359 files and directories currently installed.) Preparing to unpack .../bcmwl-kernel-source_6.30.223.248+bdcom-0ubuntu0.2_amd64.deb ... Unpacking bcmwl-kernel-source (6.30.223.248+bdcom-0ubuntu0.2) ... Setting up bcmwl-kernel-source (6.30.223.248+bdcom-0ubuntu0.2) ... Loading new bcmwl-6.30.223.248+bdcom DKMS files... First Installation: checking all kernels... Building only for 3.19.0-82-generic Building for architecture x86_64 Building initial module for 3.19.0-82-generic Secure Boot not enabled on this system. Done. wl: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/3.19.0-82-generic/updates/dkms/ depmod DKMS: install completed. modprobe: ERROR: could not insert 'wl': Package not installed update-initramfs: deferring update (trigger activated) Processing triggers for initramfs-tools (0.103ubuntu4.11) ... update-initramfs: Generating /boot/initrd.img-3.19.0-82-generic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1818134 Title: modprobe: ERROR: could not insert 'wl': Package not installed ubuntu14.04.5LTS kernel 3.13.0-165-generic Status in bcmwl package in Ubuntu: Confirmed Bug description: when installing bcmwl-kernel-source to build wl.ko package version: 6.30.223.248+bdcom-0ubuntu0.2 Expected behavior: kernel module wl.ko loads. What happened: finit_module returns ENOPKG My device is: BCM4352 [14e4:43b1] (rev 03) Happened after latest OS update, downgrading kernel to 164 did not fix, downgrading package did not work. secure boot mode is off. A few others are having this issue https://ubuntuforums.org/showthread.php?t=2413303 There is a possibility it is a modaliases problem -- 2015 chagelog states that there was a capitalization problem, but I don't know how to check this. To manage notifications about this bug go to:
