Date: Sun, 6 Nov 2016 18:14:06 +0100 From: Dimitry Andric <dim@FreeBSD.org> To: Harry Schmalzbauer <freebsd@omnilan.de> Cc: freebsd-stable@freebsd.org Subject: Re: boot1.efifat's FAT12 volume label prevents booting (some systems) Message-ID: <B2D1285B-917A-43DA-9A45-EFA92E0C9463@FreeBSD.org> In-Reply-To: <581F4748.9030706@omnilan.de> References: <581F4748.9030706@omnilan.de>
next in thread | previous in thread | raw e-mail | index | archive | help
--Apple-Mail=_8C4E640B-E13B-42AC-B90A-2F2408D90117 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=us-ascii On 06 Nov 2016, at 16:07, Harry Schmalzbauer <freebsd@omnilan.de> wrote: > > Recently I played with bsdinstall and UEFI setup, which left the system > unbootable (11.0-Release). > The culprit is the MS-DOS volume lable "EFI " of the EFI partition. > At least on Intel Single-Socket Servers (for Xeon E3 IvyBridge/BearToot > + Haswell/RainbowPass), the UEFI firmware can't handle the identical > path/volumelabel. That is pretty weird. I wasn't aware that any firmware even used this label for anything? Maybe they mount it under a directory named after the label, or something. > Simply reformatting with a different volume label (EFIFAT e.g.) solves > that problem! > Shall I file a bug report? Please do, so it is not forgotten. It is relatively easy to change the volume label, by editing sys/boot/efi/boot1/generate-fat.sh, and then regenerating the FAT templates. > Btw, can someone explain in short words why BOOT64.EFI seems to be > boot1.efi, but padded with 0x20 up to 128k? At buildworld time, pre-populated FAT file system templates are used, instead of playing games with mounting ramdisks and creating file systems in them. The build process just inserts the contents of boot1.efi into a fixed location into the existing FAT template. And the template is pre-propulated with a 128kiB bootx64.efi file. -Dimitry --Apple-Mail=_8C4E640B-E13B-42AC-B90A-2F2408D90117 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.30 iEYEARECAAYFAlgfZOsACgkQsF6jCi4glqP61ACdHXwQ3P/7jowVRlYirJcLF2kC AeIAnRFHtfd4viqYDqCH8pYog/8HRSev =hqvK -----END PGP SIGNATURE----- --Apple-Mail=_8C4E640B-E13B-42AC-B90A-2F2408D90117--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?B2D1285B-917A-43DA-9A45-EFA92E0C9463>