Comment 26 for bug 1384973
Revision history for this message
| Steve Langasek (vorlon) wrote Re: [Bug 1384973] Re: shim prints "Booting in insecure mode" when booting without SecureBoot enabled | #26 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
On Fri, Jul 22, 2016 at 08:58:53PM -0000, Mark wrote:
> I triggered this situation when trying to install a proprietary NVIDIA
> driver. This driver cannot be loaded into the kernel. First must its key
> being registered in the bios. During install of the driver I'm asked to
> switch off UEFI secure boot and then reboot. On reboot a blue screen
> appears with MOK management. The process is failing, the driver is not
> installed correctly and also brings this problem with "Booting in insecure
> mode".
This bug was about shim printing a warning about booting in insecure mode
when SecureBoot was not enabled in your firmware. That is not why you are
seeing this message. You are seeing this message because *you have
configured your system to boot in insecure mode*, overriding SecureBoot in
MOK, which is a prerequisite for newer kernels to load unsigned modules
(such as the nvidia driver).
If you are seeing this message on boot, *and* the nvidia driver is not
loading for you, then there is a bug somewhere other than shim and you
should file a new bug report about this.