Date: Wed, 13 Feb 2019 15:55:40 -0700 From: Rebecca Cran <rebecca@bluestop.org> To: Yuri Pankov <yuripv@yuripv.net> Cc: freebsd-current@freebsd.org Subject: Re: memstick images install broken bootx64.efi Message-ID: <72d714de-6d7b-9faf-e5d2-36591a6fcecb@bluestop.org> In-Reply-To: <etPan.5c61cada.643c9869.1067@bluestop.org> References: <52071637-f330-677b-2d27-487830a7823c@yuripv.net> <etPan.5c61cada.643c9869.1067@bluestop.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2/11/19 12:18 PM, Rebecca Cran wrote: > I’ll take a look later today, since it’s likely related to my changes. > > > On January 26, 2019 at 6:43:49 PM, Yuri Pankov (yuripv@yuripv.net(mailto:yuripv@yuripv.net)) wrote: > >> Looks like installations from snapshot memstick images (tried all >> available ones for amd64 from >> http://ftp.freebsd.org/pub/FreeBSD/snapshots/ISO-IMAGES/13.0/) put >> broken bootx64.efi to ESP -- the system in question simply tries to boot >> via PXE. Fixing this is simple -- mounting the ESP, and copying >> /boot/loader.efi from installation media (the same memstick) to >> efi/boot/bootx64.efi. And diff shows that the two actually differ, >> having the same size and file(1) output though. >> >> Anyone seeing the same and/or knows what's wrong here (before I try >> looking into that)? Sorry for the delay. I just tried booting the FreeBSD-13.0-CURRENT-amd64-20190123-r343372-memstick.img on my MinnowBoard Turbot and it worked. Could your download have been corrupted? -- Rebecca Cran
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?72d714de-6d7b-9faf-e5d2-36591a6fcecb>