UEFI Secure Boot is not compatible with the use of third-party drivers

Asked Aug 15 '16 at 16:26

Active Aug 29 '16 at 21:49

Viewed 2,381 times

An ongoing issue with Ubuntu 14.04 where Virtualbox wouldn't run on the 3.13.0-92 kernel appears to have maybe been fixed in the newest update to 3.13.0-93. However, after the GUI update failing (locking up) and doing a command-line update instead, there were some dialogue boxes, one of which asked for a password. However, I rebooted and did not press a key in time before the "Press any key to perform MOK management" dialogue disappeared. Now it seems impossible to get back to this. How do I continue the update process? I reran the updater and this has not come back. I was told I'd need to put the same password into the MOK management dialogue upon reboot but not told I'd have to press a key to get to it within a couple seconds, and that there would only be one chance to do this...

How do I get back to the MOK management dialouge so I can enable the virtualbox kernel module?

edited Aug 29 '16 at 21:49

Kaz Wolfe

34,122
21
114
172

asked Aug 15 '16 at 16:26

b264

VirtualBox suggests running "sudo /etc/init.d/vboxdrv setup" which only works on kernel 3.13.0-91 and prior. – b264 Aug 15 '16 at 16:51
Disable Secure Boot in BIOS. – Pilot6 Aug 29 '16 at 21:50
1

Possible duplicate of Why do I get "Required key not available" when install 3rd party kernel modules or after a kernel upgrade? – Pilot6 Aug 29 '16 at 21:51
Disabling Secure Boot in BIOS did make VirtualBox work on the newer Linux, but the question was specifically "How do I get back to the MOK management dialouge ... ?" – b264 Sep 13 '16 at 16:58
There is an answer. You could enable validation by mokutil and re-install vitrualbox or re-configure it. – Pilot6 Sep 13 '16 at 17:00

UEFI Secure Boot is not compatible with the use of third-party drivers

0 Answers0