1

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?

Kaz Wolfe
  • 33,802
  • 20
  • 111
  • 168
b264
  • 339
  • 1
  • 3
  • 16
  • 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?](http://askubuntu.com/questions/762254/why-do-i-get-required-key-not-available-when-install-3rd-party-kernel-modules) – 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

0 Answers0