> What if you set SHIM_VERBOSE in firmware, using 'sudo mokutil --set-verbosity true' after booting with just grub?
This command fail with "This system doesn't support Secure Boot". On a side note I found that attempt to boot with installed shim-signed fail with both of Secure Boot enabled and disabled.
Also I guess I need to mention that Snapdragon-based laptops currently boot only with "efi=novamap": Bug 1814982
Does it make sense to patch mokutil.c to ignore Secure Boot state (line 2413) or it expected to fail somewhere else due to issue described in Bug 1814982?
> What if you set SHIM_VERBOSE in firmware, using 'sudo mokutil --set-verbosity true' after booting with just grub?
This command fail with "This system doesn't support Secure Boot". On a side note I found that attempt to boot with installed shim-signed fail with both of Secure Boot enabled and disabled.
Also I guess I need to mention that Snapdragon-based laptops currently boot only with "efi=novamap": Bug 1814982
Does it make sense to patch mokutil.c to ignore Secure Boot state (line 2413) or it expected to fail somewhere else due to issue described in Bug 1814982?