unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Tobias Geerinckx-Rice <me@tobias.gr>
Cc: 39288@debbugs.gnu.org
Subject: bug#39288: Wrong keyboard layout to decrypt hard drive
Date: Mon, 27 Jan 2020 22:39:51 +0100	[thread overview]
Message-ID: <87o8uofujc.fsf@gnu.org> (raw)
In-Reply-To: <877e1epfro.fsf@nckx> (Tobias Geerinckx-Rice's message of "Sun, 26 Jan 2020 13:24:11 +0100")

Hi,

Tobias Geerinckx-Rice <me@tobias.gr> skribis:

> Could you check whether your system configuration's
> bootloader-configuration actually contains a keyboard-layout field?
>
>       (bootloader (bootloader-configuration
>                     (bootloader grub-efi-bootloader)
>                     (target "/boot/efi")
>       -->           (keyboard-layout keyboard-layout)))

I've heard people using the French keyboard layout like this and having
an encrypted root say that GRUB (stage1) would indeed ignore the chosen
keyboard layout.  (I believe GRUB stage2, where the menu and command
line editing features are present, works fine, but that’s after the
passphrase has been entered.)

A quick search yields:

  https://superuser.com/questions/974833/change-the-keyboard-layout-of-grub-in-stage-1

… which suggests using ‘grub-mkstandalone’ (which is undocumented but
looks like a tiny superset of ‘grub-install’) and explicitly adding the
keyboard layout file to the on the command line.  Should we do that?

Problem is, ‘install-grub-efi’ isn’t passed the configuration.

Thanks,
Ludo’.

      reply	other threads:[~2020-01-27 21:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-26 11:41 bug#39288: Wrong keyboard layout to decrypt hard drive Damien Cassou
2020-01-26 12:24 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
2020-01-27 21:39   ` Ludovic Courtès [this message]

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=87o8uofujc.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=39288@debbugs.gnu.org \
    --cc=me@tobias.gr \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

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).