Comment # 62 on bug 1175626 from
(In reply to John Shaw from comment #61)

> From what I can tell, it looks like the driver went from 450.57 to 450.66
> which would be a version change.

Ok, so my theory is void again :-/

> The current state of the machine (which I need for work, so I can't afford
> to screw it up too much;) is that if I enable SecureBoot, it DOES now flash
> what is likely a MOK message (what else could it be?).

Sometimes the BIOS itself prints something on the screen. MokManager output
would typically be blue color, and centered on the screen.

>  This is almost
> certainly due to the nVidia driver. However, flash is the operative word. I
> cannot read it and I cannot catch it with a key press.

Sure enough, that looks like a malfunction of MokManager. But only on your
system. Strange. 

> I tried a couple of
> times, but the message is up for maybe 1/10th of a second. What this thing
> needs is to pause for a few seconds. The boot process at least gets past
> this and drops into grub. If I boot suse, it fails to load the nvidia
> driver. I tried to reinstall the driver, but I can't find a way to get MOK
> to enroll it.

Be careful with "reinstalling", as noted above that procedure is a bit flawed
in the current release. It's better to uninstall and install again.

Please provide output of mokutil --list-enrolled, mokutil --list-new, mokutil
--list-delete.

> Booting with SecureBoot disabled still works.
> 
> I could not boot the shellx86.efi from my /boot/efi partition. The bios
> gives the option to boot it from  a USB drive, so I guess I can try that. As
> you suggest, I could try and add a boot entry with efibootmgr, but the USB
> option is safer.

Sorry that this is such a hassle for you. Using efibootmgr for this is actually
not so dangerous because it will create a new boot entry, and if that one can't
be booted, the EFI bootloader will fall back to the next working one. But I can
understand that you're wary after your recent experience.

I'd do it roughly like this (note that you need to adapt disk (-d), partition
(-p) and path (-l)):

> efibootmgr -c -L 'UEFI Shell' -d /dev/sda -p 1 -l '\EFI\shell\shellx64.efi'


You are receiving this mail because: