To preface: I'm not looking to disable secure boot as I have a second hard drive with Windows 10 installed. The two OSes exist on two separate drives and are isolated from each other during runtime. Windows Boot Manager and GRUB exist on their own respective drives and are completely unaware of each other.

The relevant system configuration is:

  • OS: Ubuntu 17.04 - Kernel: 4.10.0-32-generic
  • Motherboard: Asrock Taichi X99
  • GPU: GTX 1080

So, I've been trying to use mokutil to enroll my own certificate so I can use it to load signed Nvidia drivers, but I've run into troubles with getting the whole procedure to work.

So the steps I took were:

  1. Enable secure boot support in Ubuntu.
  2. Create an x509 certificate with openssl.
  3. Ran mokutil --enable-validation and entered a password.
  4. Used mokutil --import to add the newly created certificate to the secure boot keys list.
  5. Used the signing script under the efi directory to sign kernel modules using the private key and certificate pair I created.
  6. Rebooted the system.
  7. Selected the boot entry with shimx64.efi
  8. Pressed key to enter mok management
  9. Got stuck on the screen I've attached ![MOK Management proceed screen on boot]1
  • When you say you "got stuck," what happens when you press a key? Is the keypress ignored and the countdown continues? Does the system hang? Does the system reboot? Do you see an error message? Something else? – Rod Smith Aug 28 '17 at 16:49
  • @RodSmith The countdown stops, effectively MOK Management opens, there just isn't any output to the display of the interface. Based on the screenshots of what should be there, pressing enter once continues boot. I managed to enroll a key by pressing keys and entering the password according to screenshots, but there is no visual display of anything. – Perse95 Aug 28 '17 at 17:09
  • This sounds like an EFI video driver problem. You mention an Nvidia GPU. Is this on a plug-in card, or built into the motherboard? If the former, you might try unplugging the card, just to enroll the key. If the latter, you could poke around in the firmware settings for relevant video options, and you might want to report it as a bug to the motherboard manufacturer. – Rod Smith Aug 29 '17 at 13:16
  • It's a plug-in card, but I have no integrated graphics nor another card that would also work to see if it's a motherboard or video card driver issue. I think I will report it tho, it seems like a very annoying bug. – Perse95 Aug 29 '17 at 13:19
  • Ah, I see. Be sure that the card provides EFI firmware, then. It could be that the card was designed for BIOS-based computers and is relying on the computer's CSM (BIOS compatibility layer), which might be flaking out a bit, particularly when you're trying to do something related to Secure Boot. Some manufacturers provide video card firmware updates to enable EFI compatibility, so you might look for that, too. – Rod Smith Aug 29 '17 at 13:34

Your Answer

By clicking "Post Your Answer", you acknowledge that you have read our updated terms of service, privacy policy and cookie policy, and that your continued use of the website is subject to these policies.

Browse other questions tagged or ask your own question.