[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1748983 Title: Generate per-machine MOK for dkms signing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1748983/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1818134/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu
Bugs, which is subscribed to 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
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1818134/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1818134/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1450490] Re: Initial installer run on Dell XPS13 (9343), crash while creating recovery media
So, after filing this bug report (and being left with only a top menu- bar and no side applications-menu) I rebooted the laptop, and was able to login as the user I created during the setup before it crashed (although there was also still an "OEM" user listed as an option, which I didn't use). I tried running the Dell Recovery program again to create a recovery USB stick, and it again crashed! So then I installed all the pending updates (which itself needed an 'sudo apt-get install -f' to complete properly), did a reboot, logged in, and again tried running the Dell Recovery program. This time it worked! It "did it's stuff", and then tried writing the recovery image to my 2GB USB drive, but complained it didn't have enough space. Turns out that my 2GB USB flash drive was only 1.9GB, but the recovery image needed 2.1GB of space. (I've got no idea if this was the reason for the original crash?) So then I found up a 16GB USB flash drive and installed the recovery image to that instead. All worked fine. Then I used the Dell Recovery program to reset the laptop to the factory state (restored from the recovery partition - worked flawlessly). Rebooted and ran through the initial setup process again, this time choosing *not* to make a recovery USB disk during the setup, and it all worked absolutely fine (the OEM user from the previous attempt no longer existed). And I was able to install all the pending software updates without needing to do 'sudo apt-get install -f'. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1450490 Title: Initial installer run on Dell XPS13 (9343), crash while creating recovery media To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1450490/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1450490] [NEW] Initial installer run on Dell XPS13 (9343), crash while creating recovery media
Public bug reported: Newly-received Dell XPS 13 (9343), UK model CNX4313 with Ubuntu 14.04 pre-installed. Very first power-on, and running through the initial 'setup' process. Inserted a 2GB USB Flash drive, and chose to create recovery media. Process started chugging away, and then suddenly crashed for no apparent reason. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: ubiquity 2.18.8kittyhawk2somerville2 ProcVersionSignature: Ubuntu 3.13.0-37.64bdw1-generic 3.13.11.7 Uname: Linux 3.13.0-37-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 Date: Thu Apr 30 15:08:18 2015 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-20140620-0 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi boot=casper automatic-ubiquity noprompt quiet splash -- InstallationDate: Installed on 2015-04-24 (6 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20140620-04:25 ProcEnviron: LANGUAGE=en_GB.UTF-8 TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.init.ubiquity.conf: 2015-04-24T13:24:35.518107 ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug oem-config trusty ubiquity-2.18.8kittyhawk2 ** Attachment added: "/var/log/syslog" https://bugs.launchpad.net/bugs/1450490/+attachment/4388350/+files/syslog -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1450490 Title: Initial installer run on Dell XPS13 (9343), crash while creating recovery media To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1450490/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 368594] Re: mythbuntu: can't shutdown from MythTV
Karel: I believe this is the relevant bug for mythtv in Karmic: https://bugs.launchpad.net/ubuntu/+source/consolekit/+bug/445953 It contains a simple fix that "worked for me" :) -- mythbuntu: can't shutdown from MythTV https://bugs.launchpad.net/bugs/368594 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 445953] Re: shutdown asks for password with only 1 user logged in
After upgrading from Jaunty to Karmic, I had this problem too. After eventually tracking down this bug report (took me a while to work out that mythtv was to blame!), I followed the instructions from comment #17, and that fixed the problem for me. -- shutdown asks for password with only 1 user logged in https://bugs.launchpad.net/bugs/445953 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
