https://bugzilla.suse.com/show_bug.cgi?id=1231591 https://bugzilla.suse.com/show_bug.cgi?id=1231591#c4 --- Comment #4 from Michael Chang <mchang@suse.com> --- (In reply to Andrei Borzenkov from comment #2)

(In reply to Alexander Hucke from comment #0)

...

I've checked for the file bli.mod, it is present.

Module loading is disabled in the signed grub.efi and bli module is included only in the separate grubbls.efi.

I do not understand why we have /etc/grub.d/25_bli at all. BLS is managed by sdbootutil and sdbootutil expects and installs grubbls.efi so the bli.mod is guaranteed to be present. When using grub.efi module loading is disabled so this is useless. If running plain non-signed grub2 with BLS is supported at all, at the very least /etc/grub.d/25_bli should have the same guard on GRUB_ENABLE_BLSCFG as /etc/grub.d/10_linux.

Yes, it is intentional that bli.mod is not built into grub.efi and is only included in grubbls.efi. The reason is that it previously caused a critical bug in grub 2.12, which would crash the system. Additionally, it serves no real purpose since we don't use systemd DPS or the systemd-gpt-auto-generator for GPT partition auto-mounting. Enabling it in grub alone could lead to unexpected side effects without further testing of all pieces put together (also concerns in older code streams like Leap/SLE). The /etc/grub.d/25_bli is provided by upstream directly, but I believe it should be disabled in rpm to avoid the "file not found" error. It can be re-enabled in the future when we see fit. -- You are receiving this mail because: You are on the CC list for the bug.