From: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>
To: Danny Milosavljevic <dannym@scratchpost.org>
Cc: 35585@debbugs.gnu.org
Subject: bug#35585: GRUB does not work with USB keyboards when using keyboard-layout
Date: Wed, 8 May 2019 00:09:45 +0200 [thread overview]
Message-ID: <20190507220944.fg7e72wbuqmcmku7@pelzflorian.localdomain> (raw)
In-Reply-To: <20190507183914.615660dc@scratchpost.org>
On Tue, May 07, 2019 at 06:39:14PM +0200, Danny Milosavljevic wrote:
> Why is it specified at all? If it's not specified, it will default to
> the "platform native" inputs which means the ones available in the source code
> for that platform. So aren't we complicating our life for no reason by
> specifying it in the first place?
On my Macbook, omitting the terminal_input line works fine; I can use
the keyboard. The layout for passphrase and boot menu remains US
English though, as it always was for the passphrase and as it was with
terminal_input usb_keyboard. But this is much better than no
keyboard in the boot menu at all (and I prefer US English anyway).
Thank you for sharing your expertise Danny!
Regards,
Florian
next prev parent reply other threads:[~2019-05-07 22:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-05 17:35 bug#35585: GRUB does not work with USB keyboards when using keyboard-layout pelzflorian (Florian Pelz)
2019-05-07 16:11 ` Ludovic Courtès
2019-05-07 16:39 ` Danny Milosavljevic
2019-05-07 22:09 ` pelzflorian (Florian Pelz) [this message]
2019-05-08 10:03 ` Ludovic Courtès
2019-05-08 12:23 ` pelzflorian (Florian Pelz)
2019-05-09 10:14 ` Ludovic Courtès
2019-05-09 12:52 ` Danny Milosavljevic
2019-05-13 13:59 ` Giovanni Biscuolo
2019-05-13 20:34 ` Ludovic Courtès
2019-05-07 17:25 ` pelzflorian (Florian Pelz)
2019-05-07 17:48 ` pelzflorian (Florian Pelz)
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=20190507220944.fg7e72wbuqmcmku7@pelzflorian.localdomain \
--to=pelzflorian@pelzflorian.de \
--cc=35585@debbugs.gnu.org \
--cc=dannym@scratchpost.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.
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).