Bug 228922 - UEFI boot loader loose ends
Summary: UEFI boot loader loose ends
Status: New
Alias: None
Product: Base System
Classification: Unclassified
Component: bin (show other bugs)
Version: CURRENT
Hardware: Any Any
: --- Affects Many People
Assignee: Warner Losh
URL:
Keywords:
Depends on:
Blocks: 228911
  Show dependency treegraph
 
Reported: 2018-06-12 09:01 UTC by Rodney W. Grimes
Modified: 2018-12-25 03:01 UTC (History)
3 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Rodney W. Grimes freebsd_committer 2018-06-12 09:01:47 UTC
UEFI boot loader loose ends
Comment 1 Conrad Meyer freebsd_committer 2018-06-12 17:43:07 UTC
Any specifics, so we don't forget the ideas from BSDCan?
Comment 2 Warner Losh freebsd_committer 2018-06-12 17:51:03 UTC
my current list:

Chain booting to multiple levels (loader.efi needs to look at BootXXXX)

Sane fallback when nothing left to do (either due to BootOrder exhaustion or protocol violations)

/boot/efi/root would be nice
Comment 3 Ed Maste freebsd_committer 2018-07-24 15:26:38 UTC
r336656 Finalize the boot manager protocol support for next-stage boot loading.
Comment 4 Rebecca Cran freebsd_committer 2018-12-25 02:20:43 UTC
Is this still relevant? I wonder if instead of supporting chain booting, we should exit and allow the system to try other BootXXXX entries itself instead?
Comment 5 Warner Losh freebsd_committer 2018-12-25 03:01:59 UTC
Yes. It is still relevant. UEFI still can't read UFS or ZFS filesystems. When we load loader.efi directly, we have to then load a kernel using it. BootNext can never help this situation because the kernel is not an EFI loader. Chain booting isn't used here in the narrow loader.efi sense of the chain boot command, but in the larger sense of loading the next thing.