Comment # 63 on bug 1175626 from 
> 
> 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.

All are empty. I shut my machine off every night and reboot in the morning with
SecureBoot disabled. Updates come through in that mode, so I wonder if they
don't try to setup the certificates/keys. Although I can sometimes boot with
SecureBoot (I tried again a couple of days ago), I cannot get the nVidia driver
to be enrolled. This is not an option for me as I write Cuda-based codes.

I count not care less about having SecureBoot (why would anyone?), but I
figured I would try to help debug this issue. The certificate file is available
for the nvidia driver, so I can be imported with mokutil again. This may force
MOK to pause and let me enroll it. If there is nothing to enroll, what is MOK
Manager supposed to do on a boot? Is its supposed to: a) do nothing and pass
control to grub; b) flash MOC screen and move on; or c) show MOC screen and
wait a few seconds?


> 
> > 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.

I should probably get out of X11 and full uninstall the drivers, and reinstall
them.


> 
> 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: