https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=214282
Bug ID: 214282
Summary: UEFI boot fails due to boot1.efifat's volume label
"EFI "
Product: Base System
Version: 11.0-RELEASE
Hardware: Any
OS: Any
Status: New
Severity: Affects Some People
Priority: ---
Component: misc
Assignee: freebsd-bugs@FreeBSD.org
Reporter: bugzilla.free...@omnilan.de
At least on Intel single socket servers the UEFI firmware can't handle the
msdosfs (FAT12) volume label"EFI ", which is currently used with
"/boot/boot1.efifat" image (tested on 11-release, most likely also on
10.3-release).
Firmware's boot process somehow confused the label "EFI" with the boot path,
also containing EFI (as far as I remember the meaning of the failure message).
Affected systems are S1200BT and S1200v3RP e.g.
Simply reformatting with a different volume label solved the problem.
According to Dimitry Andric, it's easily fixable for build process by changing
the label name in "sys/boot/efi/boot1/generate-fat.sh".
Sorry, I don't have sources handy right now, so no patch attached. Could
suggest one of course, but would take longer to process the one from here
instead of direct edit I guess ;-)
Besides changing boot1.efifat, bsdinstall could be modified to work arround;
but that's not the right thing IHMO.
People affected (or unsure if they also suffer from this firmware obstacle)
could try the following (assuming index 1 of /dev/da0's GPT is the
EFI-sys-part):
'newfs_msdos -L DA0BOOT1 /dev/da0p1 && mount /dev/msdosfs/DA0BOOT1 /mnt'
'mkdir -p /mnt/EFI/BOOT && cp /boot/boot1.efi /mnt/EFI/BOOT/BOOTx64.efi'
'echo "BOOTx64.efi" > mnt/EFI/BOOT/startup.nsh && umount /mnt'
Just in case this report is found while people are searching for solution…
-harry
--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
