Created attachment 886733 [details] Grub screenshot When grub is merged without use=fonts, an EFI enabled system seems unable to boot. Other than updating my system and running grub-mkconfig I ended up in a state where I couldn't read any error message without using a camera recording and stepping through it frame by frame. The missing unicode.pf2 is recovered when installing grub with USE=fonts. Adding a timeout would be convenient with these kind of 'reboot directly' errors.
What version of grub?
Anyway, it should be technically possible to boot without a font on an EFI system, assuming nothing else goes wrong. The USE flag is enabled by default, so I'm not too concerned about this being an issue.
sys-boot/grub-2.12-r2:2
I just confirmed that I was able to boot a qemu-based VM with OVMF (UEFI) using sys-boot/grub[-fonts]. The boot menu appeared and worked as expected.
If you would remove bli.mod, would it still boot?
Why would I remove bli.mod?
Because that is what the screenshot suggests.
It's not clear why it's missing, though. Obviously removing it is going to break it, but why was it missing to begin with?
It is also not clear to me why an upgrade without any issues suddenly breaks while only a use flag is different. But to be honest, I don't find it very obviously that it would break without that file at all. It I can make a video recording of the screen, it obviously has output...
I would guess that you upgraded from grub-2.06 to grub-2.12 without running grub-install afterward. The "bli" module was added in grub-2.12. If you didn't run grub-install, it would not exist in /boot/grub. Regardless, I don't think a failure to load the bli module would cause a boot failure. Something else probably went wrong.
