Date: Tue, 6 Sep 2016 12:26:11 -0400 From: Allan Jude <allanjude@freebsd.org> To: freebsd-current@freebsd.org Subject: Re: The state of UEFI support in the Kernel and installer Message-ID: <ca94d250-8c50-09e0-bdd2-5d86b972b613@freebsd.org> In-Reply-To: <SN1PR10MB08452638665D7EB6A064D57090F90@SN1PR10MB0845.namprd10.prod.outlook.com> References: <SN1PR10MB08452638665D7EB6A064D57090F90@SN1PR10MB0845.namprd10.prod.outlook.com>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --mNxnrJ4fGqWfLG3HIRdiEhov8OFAD9vCl Content-Type: multipart/mixed; boundary="gxMvDEDTBC0SuMUdEEfK3vT6rBDXIRia0" From: Allan Jude <allanjude@freebsd.org> To: freebsd-current@freebsd.org Message-ID: <ca94d250-8c50-09e0-bdd2-5d86b972b613@freebsd.org> Subject: Re: The state of UEFI support in the Kernel and installer References: <SN1PR10MB08452638665D7EB6A064D57090F90@SN1PR10MB0845.namprd10.prod.outlook.com> In-Reply-To: <SN1PR10MB08452638665D7EB6A064D57090F90@SN1PR10MB0845.namprd10.prod.outlook.com> --gxMvDEDTBC0SuMUdEEfK3vT6rBDXIRia0 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable On 2016-09-06 12:16, fpqc ?? wrote: > I was reading this article from the 2013 Dev summit on UEFI: >=20 > https://wiki.freebsd.org/201305DevSummit/UEFI >=20 > In particular, I wanted to ask what is the status on these two goals (f= rom the article): >=20 > The following issues exist: > - The installer needs to be taught about creating EFI System Partitions= (if needed) or selecting an EFI System Partition to install our first- a= nd second-stage boot code. The installer (both partedit and zfs auto mode), creates and EFI system partition as required. Currently, this is an 800kb partition that has /boot/boot1.efifat written to it as an image. We would like to change this to a larger partition and deal with it as a filesystem rather than as a slot for a small bootcode file to be written = to. > - The installer needs to be taught about creating EFI boot entries for = our boot code once the kernel has an API for this. >=20 > Right now, as of the latest -Current image, the installer does not ask = if an EFI System partition already exists, which is rather scary. When d= oing a manual (expert) partitioning scheme, the installer should ask for = the location of the ESP if it exists, and if no ESP is specified for moun= ting, the installer should warn that no bootloader will be installed. =20 This is rather complicated for the FreeBSD installer. If there is no ESP on the current drive, it is left to the user to install boot1.efi manuall= y. The same goes for if the user wishes to reuse an existing ESP. If bsdinstall creates the ESP for you (it does if you boot the installer under UEFI and do not tell it otherwise), then it will install the proper bootcode to the ESP. >=20 > The other problem is that as far as I can tell, there is no code that c= reates the EFI boot entry in any case. By default, the installer just mo= ves either boot1.efi or loader.efi (not sure) to: > (ESP)/EFI/bootx64.efi, > which is the default location for EFI firmware. I was wondering if the= kernel has the requisite API/driver for adding EFI boot entries yet. On= (Arch) Linux, you can add an entry to the NVRAM with a tool called bootc= tl, which is part of the sd-boot package. =20 >=20 > Also, wondering if FreeBSD has any plan to add something like initramfs= /EFIStub booting, which allows for much easier bootloader configuration w= ith sd-boot than the current FreeBSD EFI bootloader, which must be chainl= oaded and has its configuration stored off of the ESP. =20 >=20 For historic reasons, users expect to configure the loader via /boot/loader.conf not by modifying files on the ESP. > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.o= rg" >=20 --=20 Allan Jude --gxMvDEDTBC0SuMUdEEfK3vT6rBDXIRia0-- --mNxnrJ4fGqWfLG3HIRdiEhov8OFAD9vCl Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (MingW32) iQIcBAEBAgAGBQJXzu4mAAoJEBmVNT4SmAt+bV0P/jZDBabWY7DzsP+hOw87TYep oJbT4YnBY+ieM+HQPQLh0pU1v6r+KjOXZbBgGtT55sJnXJiSGkpHVQaatrZL4gQL SM/2KOXIE2tZxXC3ZHCDu5encqQhF4zhfi8Dclg6gtbLBTnAaMj9SqQxLZaPTyZQ Z42FJgFuBcklO00KSAP8dKZIFNn3Oz7uopy00As0M6LeVcSluiNg0jz7dMEqjy5y 103Ls9aNNDYlCBgRYPuCiBRkWxSoSu0E00fxk49eAdyj7dYVQF/5U1hlGEPAPIPM URAFEOF+eKxo/t1LXY0o9XRMTombwuV6jTfvX0stS++Aqm8eYllXWPowkYFTDRPw /wnCWwFbxiIj4I2yE0XpaGvEJXmn3KjrjAHs2zOmv0OJtT1tKXu3e/JM03gMwFzA gQJcmTdYPDQyD4KRzw1RAaoNuFW5ZZasZGl6wvnts1pIexQZPvp7yIBDmiIwQ0kh oRxwP9zNaAPXu5i8nwqFqa3lhhKiKmuUvbbFUL9bYziNFLDdtDJq/fGnvYAalaO9 EsEj9YvYcR3lQAId5joixk/HUzZWCIcYibAUE5gy2iXJ43i+ffeyqhkkKzafVBwE /Z0rEAiriTxp37NbPSCHplBwh0e06nYb2RqKWhYkvvWy5NO+yZb3qm8TZGiAkt5L 2D0AkUzlThXBN1iKmdxh =cdZx -----END PGP SIGNATURE----- --mNxnrJ4fGqWfLG3HIRdiEhov8OFAD9vCl--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?ca94d250-8c50-09e0-bdd2-5d86b972b613>