Date: Mon, 07 Nov 2016 09:27:38 +0100 From: Harry Schmalzbauer <freebsd@omnilan.de> To: "Patrick M. Hausen" <hausen@punkt.de> Cc: freebsd-stable@freebsd.org Subject: Re: boot1.efifat's FAT12 volume label prevents booting (some systems) Message-ID: <58203AFA.3000507@omnilan.de> In-Reply-To: <4AF66F83-EAC7-4744-ABE3-C7AE73500C0D@punkt.de> References: <581F4748.9030706@omnilan.de> <B2D1285B-917A-43DA-9A45-EFA92E0C9463@FreeBSD.org> <6230313A-3141-44F9-B056-4CAD8536B6FE@punkt.de> <5820359F.7050307@omnilan.de> <4AF66F83-EAC7-4744-ABE3-C7AE73500C0D@punkt.de>
next in thread | previous in thread | raw e-mail | index | archive | help
Bezüglich Patrick M. Hausen's Nachricht vom 07.11.2016 09:12 (localtime): > Hi, > >> Am 07.11.2016 um 09:04 schrieb Harry Schmalzbauer <freebsd@omnilan.de>: >>> create the EFI boot volume like this? >>> >>> gpart add -t efi -l efi -a 512k -s 512k <device> >>> newfs_msdos /dev/gpt/efi >>> mount_msdosfs /dev/gpt/efi /mnt >>> mkdir -p /mnt/efi/boot >>> cp /boot/boot1.efi /mnt/efi/boot/bootx64.efi >> >> You are missing startup.nsh... >> See >> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=214282https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=214282 > > Care to elaborate? This is what we use in production - all > systems booting just fine ;-) Of course you can boot UEFI systems without startup.nsh, but it does offers another way processing the boot sequence – the most sensible in my opinion. And it's what FreeBSD Releng-Team decided to provide out of the box, so heplful hint's shouldn't do it any other. -Harry
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?58203AFA.3000507>