Date: Fri, 27 Jul 2018 12:20:26 -0600 From: Warner Losh <imp@bsdimp.com> To: "O. Hartmann" <ohartmann@walstatt.org> Cc: Toomas Soome <tsoome@me.com>, "Rodney W. Grimes" <freebsd-rwg@pdx.rh.cn85.dnsmgr.net>, freebsd-current <freebsd-current@freebsd.org>, Allan Jude <allanjude@freebsd.org> Subject: Re: [UEFI] Boot issues on some UEFI implementations Message-ID: <CANCZdfqc9gwcf35a%2BgQu3PeDpUAPFv9OPrKa=3oqu89JKxVzWQ@mail.gmail.com> In-Reply-To: <CANCZdfrQiJTMOa4HbQve6YW531h__AQKc1nwkr4Fg%2BYKNRaBwQ@mail.gmail.com> References: <1E6058D2-5804-480B-B6AF-66AA02CDD7AD@me.com> <201807251430.w6PEUWPn041286@pdx.rh.CN85.dnsmgr.net> <20180726155821.6f9906e9@freyja.zeit4.iv.bundesimmobilien.de> <7FA45CAF-6869-4DF6-AA93-5F96F83EF958@me.com> <20180727074558.75b2d730@freyja.zeit4.iv.bundesimmobilien.de> <6C5D21D2-59C6-42DB-AC75-79D98BA5E62B@me.com> <20180727120232.270e1d9f@freyja.zeit4.iv.bundesimmobilien.de> <2A5E5E42-8595-44E9-A51E-504C9C2C7FA7@me.com> <20180727190555.55439fb3@thor.intern.walstatt.dynvpn.de> <CANCZdfrQiJTMOa4HbQve6YW531h__AQKc1nwkr4Fg%2BYKNRaBwQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
[[ context trimmed ]] On Fri, Jul 27, 2018 at 12:03 PM, Warner Losh <imp@bsdimp.com> wrote: > > > On Fri, Jul 27, 2018 at 11:05 AM, O. Hartmann <ohartmann@walstatt.org> > wrote: > >> >> Just to add another success on ASRock Z77-Pro4 (800k ESP, FAT12) and >> ASRock Z77-Pro4M >> (300mb ESP, FAT32). >> >> On this firmware, I did not have to define/copy the bootloader >> within /efi/freebd/BOOTx64.efi. It was sufficient to add an EFI variable >> as described in >> the manpage efibootmgr(8). >> >> The only pitfall on this firmware (very old, last functional update 2013, >> Spectre/Meltodown mitigation only May 2018) was that I wasn't able to >> activate variable >> "0000"! Creating >> >> efibootmgr -c -l /mnt/efi/boot/BOOTx64.efi -L FreeBSD-12 >> >> which results in "Boot0000" >> >> and followed by >> >> efibootmgr -a 0000 >> >> or >> >> efibootmgr -n 0000 >> >> resulted in "No such variable" or similar. >> > > Yes. that's a bogus sanity check in the code. I've removed it and will > commit in a moment. > that should be fixed as of r336768. > I had to perform the very same task again to gain variable 0001 and then I >> was able to >> "activate" variable 0000. This might be due to the fact the only variable >> defined at all >> was Boot0005 pointing to the most recent USB flash device with 12-CURRENT >> from 2018-07-26 >> I just prepared. >> > That part is weird.... > Now, also those boxes boot via UEFI (one, 800k ESP with the /efi/boot >> folder, the other, >> 300mb ESP, with a copy /efi/freebsd as I had to do on the Fujitsu ESPRIMO >> Q956 firmware). > > > OK. > Cool!... Warner
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CANCZdfqc9gwcf35a%2BgQu3PeDpUAPFv9OPrKa=3oqu89JKxVzWQ>