Opened 4 years ago
Closed 3 years ago
#16946 closed bug (duplicate)
Ensure EFI bootloader gets placed onto filesystem
Reported by: | kallisti5 | Owned by: | nobody |
---|---|---|---|
Priority: | normal | Milestone: | Unscheduled |
Component: | System/Boot Loader | Version: | R1/beta2 |
Keywords: | haiku_loader efi bios_ia32 | Cc: | |
Blocked By: | #15918 | Blocking: | |
Platform: | All |
Description
The bios_ia32 bootloader gets placed at /boot/system/haiku_loader.bios_ia32. However, the EFI bootloader doesn't make it into the haiku_loader package. (thus isn't updatable post-install)
The way our boot process is designed, the bios_ia32 loader has to be the "first" file within the haiku_loader hpkg... however the EFI bootloader could be added afterwards.
I remember doing this in the past, but it was reverted because the bios_ia32 wasn't guarenteed to be first with our current tooling causing inconsistent booting issues.
tldr; we need to ensure all bootloaders for a platform get into haiku_loader... and the bios_ia32 is always the "first entry" in the package as a special one-off. (or we need to create multiple haiku_loader packages and adjust our MBR code to search for the haiku_loader_bios_ia32 one)
Change History (1)
comment:1 by , 3 years ago
Blocked By: | 15918 added |
---|---|
Resolution: | → duplicate |
Status: | new → closed |