Peter Stuge <peter <at> stuge.se> writes:
mentions "In 2008, more x86-64 systems have adopted UEFI. While many of these systems still allow booting only the BIOS-based OSes via the Compatibility Support Module (CSM) (thus does not appear to the user that the system is UEFI-based)"
Ah okay. But what if the firmware doesn’t contain it, or it’s broken, or disables it when Restricted Boot is enabled?
For that case, I’d prefer a somewhat same BIOS implementation (and from talking with some people at several events and trying it, I know SeaBIOS probably is one, for as much as you can use the words sane and BIOS in the same sentence) on top of regular EFI, which can then be loaded by the firmware or, if in Restricted Boot mode, by OpenSuSE’s signed version of shim in its Physical Access Override mode. And then, I can ship these two files with MirBSD.
bye, //mirabilos