[[ context trimmed ]] On Fri, Jul 27, 2018 at 12:03 PM, Warner Losh <imp_at_bsdimp.com> wrote: > > > On Fri, Jul 27, 2018 at 11:05 AM, O. Hartmann <ohartmann_at_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!... WarnerReceived on Fri Jul 27 2018 - 16:20:29 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:41:17 UTC