Comment # 61 on bug 1175626 from John Shaw

(In reply to Martin Wilck from comment #60)
> (In reply to John Shaw from comment #59)
> > Unfortunately I can't really confirm what the exact version was for the
> > nVidia update that came through. I tried hunting thoughout the saved
> > snapshots, but only succeeded in hanging the yast snapshot tool after
> > looking for differences between saved pairs. This is the first time that has
> > happened, it may be that there were a LOT of differences in the pair I was
> > examining. The current version for the nVidia driver is 450.66, but I doubt
> > that  helps much.
> 
> You chose quite a complex method to figure this out ;-) 
> I'd just run "grep -i nvidia /var/log/zypp/history"; possibly prepend
> /.snapshots/$X/snapshot with the snapshot where the problem first occured.
> 
> > I finally found compiled efi shell (from the Arch Linux repos) and copied it
> > to by UEFI partition. I should be able to get into to from the BIOS. I can
> > try to boot the opensusi shim.efi file and see what happens.
> 
> Thanks a lot for your cooperation!


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

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

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.