Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 6 Sep 2019 21:27:11 -0400
From:      Eric McCorkle <eric@metricspace.net>
To:        FreeBSD Hackers <freebsd-hackers@freebsd.org>
Subject:   GRUB port refurbish patch
Message-ID:  <aa2322ee-ec4c-2ad3-23e1-661ff5a0eeec@metricspace.net>

next in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--eRpFVxelQ1DMrIyASvIhohwJ3X8ZZ2naV
Content-Type: multipart/mixed; boundary="BMOWnQN7yDMKIneGE2E8KYlALjnMXRHtk";
 protected-headers="v1"
From: Eric McCorkle <eric@metricspace.net>
To: FreeBSD Hackers <freebsd-hackers@freebsd.org>
Message-ID: <aa2322ee-ec4c-2ad3-23e1-661ff5a0eeec@metricspace.net>
Subject: GRUB port refurbish patch

--BMOWnQN7yDMKIneGE2E8KYlALjnMXRHtk
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable

I've posted a review for my work on refurbishing the GRUB port:

https://reviews.freebsd.org/D21558

I don't consider this all the way ready at this point, but it can be
tested by others at this point.

As it currently stands, this fixes things to where grub-install will
actually work again, and I have used the resulting install to boot on
real UEFI hardware.

The port also adds the QEMU target (which I haven't tested), as well as
a Coreboot target (which can't really be tested right now)

Current issues:

At present, GRUB doesn't seem to be passing the necessary information to
the kernel to initialize the EFI frame buffer, so the screen will be
blank until my system switches to the intel graphics drivers.  I suspect
this is because GRUB lacks the ability to create the parameter modules
used to do this (and also to pass in keys via keybufs).  I will add this
ability, but that's really more of a GRUB patch.  Aside from that, the
UEFI mode seems to work.

grub-install doesn't auto-detect the modules to build into the grub
image; you'll need to use the --modules argument to do that, or you'll
end up with an unbootable system.

grub-install also tries to use efibootmgr to set up efi vars, which
isn't present on FreeBSD.  You'll have to give it the --no-nvram
argument (I'll probably add a patch to make that the default).


--BMOWnQN7yDMKIneGE2E8KYlALjnMXRHtk--

--eRpFVxelQ1DMrIyASvIhohwJ3X8ZZ2naV
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----

iHUEARYIAB0WIQQb+/zC31sP34DGxX/pjibYt+BVsgUCXXMHdAAKCRDpjibYt+BV
splMAP4+gSW89yuWWkoAgM33W9T5XYn+VrfO7JqwZeZElaiv4AD+Pa72UFwVDGZU
qJTbpeVIlftxq7vQfRGuis4n/7Q/BAs=
=vLEe
-----END PGP SIGNATURE-----

--eRpFVxelQ1DMrIyASvIhohwJ3X8ZZ2naV--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?aa2322ee-ec4c-2ad3-23e1-661ff5a0eeec>