The logs show the new kernel being installed, but show no dkms module
building at time of kernel install. That seems strange to me. We
should figure out what generated
/lib/modules/4.15.0-22-generic/updates/dkms/vboxdrv.ko and when and why
it's not correctly signed.
** Changed in: dkms (Ubuntu)
Status: New => Incomplete
--
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 : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
