Date: Sat, 19 Jan 2019 21:27:56 -0700 From: Rebecca Cran <bcran@freebsd.org> To: freebsd-current@freebsd.org, Lev Serebryakov <lev@freebsd.org> Cc: Emmanuel Vadot <manu@bidouilliste.com>, Warner Losh <imp@bsdimp.com>, "Rodney W. Grimes" <freebsd-rwg@pdx.rh.cn85.dnsmgr.net> Subject: Re: GPT boot has less features than legacy MBR-based one (Was: UEFI, loader.efi and /boot.config) Message-ID: <4636753.YNO7O01DYZ@photon.int.bluestop.org> In-Reply-To: <1951151017.20190119235425@serebryakov.spb.ru> References: <912985968.20190119125228@serebryakov.spb.ru> <etPan.5c433dd9.327b23c6.1973@bluestop.org> <1951151017.20190119235425@serebryakov.spb.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
--nextPart2906384.bT80LyP3VS Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" On Saturday, 19 January 2019 13:54:25 MST Lev Serebryakov wrote: > Yes, I know. But what should I do next? There is no "Set UEFI Boot Var" > item in it. You could select different physical drives (but not partitions > of the drives) and network cards (if PXE is enabled), and, sometimes, "EFI > Shell" which is not documented anywhere, and it doesn't work always. > > When I google "ASUS EFI Shell", for example, all results says about > preparing USB stick with EFI shell and such, not about commands and > variables of EFI shell. > > I don't say, that it is impossible, I only could not find good (or any) > documentation. Yeah, the documentation is definitely lacking. If you want to specifically run the EFI Shell, then you'll need to either install Shell_Full.efi from https://github.com/tianocore/edk2/tree/UDK2014.SP1/ EdkShellBinPkg/FullShell/X64 as Shellx64.efi on a USB stick formatted as FAT16 or FAT32 - or, install the shell as EFI/BOOT/BOOTx64.efi on an ESP. For booting FreeBSD, you might want to consider installing rEFInd (http:// www.rodsbooks.com/refind/), since it can find the loader in EFI/freebsd/ loader.efi and displays the FreeBSD logo - see https://bluestop.org/files/ rEFInd_FreeBSD.jpeg . For comparison, my ASUS UEFI firmware doesn't find FreeBSD at all in /EFI/freebsd, and when installed as /EFI/boot/BOOTx64.efi just displays a "UEFI OS" entry. Ultimately, UEFI doesn't care about disks and partitions: it only really knows about ESPs -- FAT12/16/32 formatted partitions that contain the EFI directory structure. For now, that means /EFI/BOOT/BOOT{x64,i386,aa64,arm}.efi, the Microsoft boot loader in /EFI/Microsoft and GRUB/shim in /EFI/fedora, /EFI/ opensuse etc. -- Rebecca Cran --nextPart2906384.bT80LyP3VS Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part. Content-Transfer-Encoding: 7Bit -----BEGIN PGP SIGNATURE----- iQIzBAABCAAdFiEEH7l9m2RN073jRiviDQIrUxG+ECAFAlxD+MwACgkQDQIrUxG+ ECBoiBAAskf/dj536XfYcD1VQmNQP6pW+ujkuyb4ovpEFyiAH2niLDfcOPCFtiIk CYV25+delL4F5gO3DBC5G/VhF/8Vk6xz4OOZ0ySvWCoLl+1BfFwiVWliu6jf3EjS OguEkJqNoWOHdV4YEfoZpMdiNQerVMCsbAxaK1Rp8O6JFXfDTFFvkfNObr7jYI2b YOdev7QpWCRiOBqWqJsdlPp8WarskGqfaA/0bo9D75DqGYDZDSU7KBgSK265QupT 8zSxvQr5wHVLg0HIm4jHAaRnnZuW/uS18FaznGTnDHdrv9No0VloMt9vWVxpW480 +VRTNB4mvt/MvwcYZqRuF7PKuDLKBA1ZqkBmOpHELHCtSwvTQvo0LJt+TFxwIxyU tBghFTcL1fnDR4eQUnR208Q0OgmVkLNuovJrNuw+0zxoxcf3U8u3G30z5G4qHOtb o1YSQJuWG8ASIiFbGN7/YdZ0qqttG+5f41Rmod3IJwnyx4EIPqNFm9EmJZ9GGEN6 sAlg3ZDK9raAQXmKIqykwewyWeJx/gyFQPoWubV6IeOuguXhbApffiBLsyhmbLTr N3LPOlG5qu0z8FxRct07in2B4RdcJUTDi9b4Nkjh9+c8JzArbgbjRnxJsfziZ42Y yrIzQS1NYXxZjDorePtFcmv16By61tK/O09RnXFsc2ivGtZpo/c= =lfgo -----END PGP SIGNATURE----- --nextPart2906384.bT80LyP3VS--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4636753.YNO7O01DYZ>