From: Emmanuel Beffara <manu@beffara.org>
To: help-guix@gnu.org
Subject: Grub installation and configuration
Date: Fri, 3 Mar 2023 18:47:20 +0100 [thread overview]
Message-ID: <20230303184720.GG2153@beffara.org> (raw)
Hello again,
Continuing on my adventures with installing Guix System on LVM on LUKS with
Grub as bootloader, I would like to suggest a few adujstments to how Grub is
installed in Guix:
- Install the keymaps in the EFI partition like the Grub modules, so that the
proper keymap is setup early in the boot process.
In the context of full-disk encryption, this is very important because in
the current state of things, one has to enter the passphrase using the
default US layout before the proper keymap can be loaded from the encrypted
store. One can manage working around that with a bit of training, but having
to enter a passphrase with an incorrect keymap is objectively a broken
behaviour.
Furthermore, when the kernel later requires the passphrase again, it has to
be entered in the proper layout. This is inconsistent.
- Set the terminal_output before any user input is required (and in particular
the passphrase request), for proper interaction.
In my case, the laptop has a HiDPI display and Grub starts with a nice
terminal in 3840x2160 resolution with very small characters. Not only is
it unreadable, but Grub is also known to be extremely slow with high
resolutions [1], which makes interaction painful.
[1] https://askubuntu.com/questions/1227735/grub-is-extremely-slow-1-second-per-key-input
- Offer the option to put kernels and initrds in the EFI partition (and also
any resource needed by Grub like the background picture, locales etc), so
that Grub can be fully functional without decrypting. Apart from solving the
issue of having to enter the passphrase twice and with different keymaps,
this would also allow having Guix System in an encrypted partition while
allowing to boot other systems without requiring its passphrase.
I would love to propose patches for that but I am too much of a beginner with
Guix to be able to do that right now…
--
Emmanuel
next reply other threads:[~2023-03-03 17:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-03 17:47 Emmanuel Beffara [this message]
2023-03-07 16:12 ` Grub installation and configuration Ludovic Courtès
2023-03-07 17:41 ` Emmanuel Beffara
2023-03-07 22:52 ` Vagrant Cascadian
2023-03-08 3:25 ` Felix Lechner via
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230303184720.GG2153@beffara.org \
--to=manu@beffara.org \
--cc=help-guix@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).