Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

This sounds like a firmware bug. I think shim tries to work around this for some machines, so it could be that shim needs to be extended. But I would look first at getting the system firmware updated with a manufacturer supplied update. In the meantime what do you get for

rpm -qa | grep grub2-efi rpm -qa | grep shim

This sounds like a firmware bug. I think shim tries to work around this for some machines, so it could be that shim needs to be extended. But I would look first at getting the system firmware updated with a manufacturer supplied update. In the meantime what do you get for

 rpm -qa | grep grub2-efi
 rpm -qa | grep shim

This sounds like a firmware bug. I think shim tries to work around this for some machines, so it could be that shim needs to be extended. But I would look first at getting the system firmware updated with a manufacturer supplied update. In the meantime what do you get for

rpm -qa | grep grub2-efi
 rpm -qa | grep shim
efibootmgr -v

This sounds like a firmware bug. bug, related to NVRAM garbage collection. I think shim tries to work around this for some machines, so it could be that shim needs to be extended. But I would look first at getting the system firmware updated with a manufacturer supplied update. In the meantime what do you get for

rpm -qa | grep grub2-efi
rpm -qa | grep shim
efibootmgr -v