git: 0b7472b3d8d2 - main - Mount the EFI system partition (ESP) on newly-installed systems.

[Mark Millard]

Nathan Whitehorn nwhitehorn at FreeBSD.org wrote on
Tue Feb 23 21:24:30 UTC 2021 :

> +# Update the ESP (EFI System Partition) with the new bootloader if we have an ESP
> +if [ -d "$BSDINSTALL_CHROOT/boot/efi" ]; then
>  	case $(uname -m) in
>  	    arm64)	ARCHBOOTNAME=aa64 ;;
>  	    amd64)	ARCHBOOTNAME=x64 ;;
> @@ -136,55 +60,33 @@ if [ "$(uname -m)" = "arm64" ] || [ "$(uname -m)" = "riscv" ] || [ "$X86_BOOTMET
>  	BOOTNAME="${BOOTDIR}/boot${ARCHBOOTNAME}.efi"
>  	FREEBSD_BOOTDIR="/efi/freebsd"
>  	FREEBSD_BOOTNAME="${FREEBSD_BOOTDIR}/loader.efi"
> +	mntpt="$BSDINSTALL_CHROOT/boot/efi"

where older history has:

	BOOTDIR="/efi/boot"

The below is mostly an FYI in case it has
implications or users need instrutions.

While I've not checked recently, my
environment has the following sorts of
paths/filenames involved because of past
examples of failure to work with alternate
capitalizations, such as the u-boot or
uefi/ACPI involved being picky for some
reason.

Some also have a startup.nsh that contains
the name (not path) and I have those
tracking the capitalization shown.

Rock64:         EFI/BOOT/bootaa64.efi
(MBR fat32lba, u-boot placement requirements block GPT use
 if I remember right.)

RPi4B:          EFI/BOOT/BOOTAA64.EFI
(GPT efi)       EFI/BOOT/bootaa64.efi
                (As I remember it was the directories that
                 mattered here. I sometimes use the RPi4B
                 with https://github.com/pftf/RPi4 edk2
                 UEFI/ACPI materials.)

OverDrive 1000: efi/boot/BOOTaa64.efi
(GPT efi)

MACCHIATObin Double Shot: efi/boot/BOOTaa64.efi
(GPT efi, the UEFI/ACPI is one I was given/pointed-to)

RPi3B: not currently accessible to look up the details.
       (Probable match to RPi4B? Again edk2 materials,
        but from https://github.com/pftf/RPi3 .)

===
Mark Millard
marklmi at yahoo.com
( dsl-only.net went
away in early 2018-Mar)