The dkms package's shim integration only happens in
/usr/lib/dkms/common.postinst. It appears this code is only triggered
on installation of a dkms package; this code path is not used as part of
the kernel postinst hook when building modules for a newly-installed
kernel - that hook only calls /usr/lib/dkms/dkms_autoinstaller .
Marking this critical, since this means users will lose their dkms
modules on kernel upgrade.
** Changed in: dkms (Ubuntu)
Status: New => Triaged
** Changed in: dkms (Ubuntu)
Importance: High => Critical
--
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/1772950
Title:
dkms key enrolled in mok, but dkms module fails to load
Status in dkms package in Ubuntu:
Triaged
Bug description:
At my last reboot, I was prompted to enable SecureBoot, so I did.
When I booted, however, I noticed that the virtualbox service failed
to start because it couldn't load its kernel module. If I attempt the
same thing, I see that there's an issue with keys:
$ sudo modprobe vboxdrv
modprobe: ERROR: could not insert 'vboxdrv': Required key not available
I do have keys enrolled; `mokutil --list-enrolled` produces
http://paste.ubuntu.com/p/rntTQr5XJV/
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1772950/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
