Date: Fri, 27 Mar 2020 14:49:49 -0700 From: Chris <bsd-lists@BSDforge.com> To: freebsd-current <freebsd-current@freebsd.org> Subject: When will the FreeBSD (u)EFI work? Message-ID: <1dd9599e57a5371aa569ecdcedaa220e@udns.ultimatedns.net>
next in thread | raw e-mail | index | archive | help
On an experiment of the FreeBSD EFI implementation=2E I installed
a copy of releng/12 from install media=2E Which left me with:
# gpart show ada0
=3D> 40 312581728 ada0 GPT (149G)
40 409600 1 efi (200M)
409640 31047680 2 freebsd-ufs (15G)
31457320 7680000 3 freebsd-swap (3=2E7G)
74788904 237792864 - free - (141G)
On this Intel based system, I can stab the F12 key to pick
my UEFI bootable OS, or let it boot according to the order
I setup in the BIOS=2E So far, so good=2E
I needed a copy of releng/13 to also work with=2E Installed a copy
from install media=2E Which left me with:
# gpart show ada0
=3D> 40 312581728 ada0 GPT (149G)
40 409600 1 efi (200M)
409640 31047680 2 freebsd-ufs (15G)
31457320 7680000 3 freebsd-swap (3=2E7G)
39137320 532480 4 efi (260M)
39669800 35119104 5 freebsd-ufs (17G)
74788904 237792864 - free - (113G)
I *assumed* that the install would activate the new install, and I
would boot straight into it=2E But no=2E I am still on the previous
install, and worse, I can't get into the new install -- even if
picking it via stabbing the F12 key=2E I *still* end up in the previous
install=2E So looking at what might be causing it=2E I found the following:
# releng/12
# mount -t msdosfs /dev/ada0p1 /mnt/
# ls /mnt/efi/boot/
BOOTx64=2Eefi
startup=2Ensh
# cat /mnt/efi/boot/startup=2Ensh
BOOTx64=2Eefi
# umount /mnt/
releng/13
# mount -t msdosfs /dev/ada0p4 /mnt/
# ls /mnt/EFI/freebsd/
loader=2Eefi
Why the difference? When will FreeBSD (u)EFI work as expected?
Thanks in advance for any insights!
--Chris
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1dd9599e57a5371aa569ecdcedaa220e>