You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 23, 2021. It is now read-only.
Today we only use grub as bootloader. It might be good to test more bootloaders. For instance:
Linux as bootloader (aka EFI stub)
systemd boot
This could help to uncover issues as by the time Linux boots the bootloader has already interatected with the firmware (e.g., grub called by this point the UEFI Boot time service ExitBootServices()).
The text was updated successfully, but these errors were encountered:
@meghadey suggested that a good quick test is to change the EFI_PROVIDER from "luv-efi" to "systemd-boot" here [1] and see how the boot partition is populated; or at least see what things break when building.
At a later stage we would need to wire things up to run BITS from systemd-boot, implement configurations for netconsole, tests suites to run, etc.
Today we only use grub as bootloader. It might be good to test more bootloaders. For instance:
Linux as bootloader (aka EFI stub)
systemd boot
This could help to uncover issues as by the time Linux boots the bootloader has already interatected with the firmware (e.g., grub called by this point the UEFI Boot time service ExitBootServices()).
The text was updated successfully, but these errors were encountered: