GNU bug report logs -
#35585
GRUB does not work with USB keyboards when using keyboard-layout
Previous Next
To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 35585 in the body.
You can then email your comments to 35585 AT debbugs.gnu.org in the normal way.
Toggle the display of automated, internal messages from the tracker.
Report forwarded
to
bug-guix <at> gnu.org
:
bug#35585
; Package
guix
.
(Sun, 05 May 2019 17:37:01 GMT)
Full text and
rfc822 format available.
Acknowledgement sent
to
"pelzflorian (Florian Pelz)" <pelzflorian <at> pelzflorian.de>
:
New bug report received and forwarded. Copy sent to
bug-guix <at> gnu.org
.
(Sun, 05 May 2019 17:37:02 GMT)
Full text and
rfc822 format available.
Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/plain, inline)]
In the bootloader menu, input from a USB external keyboard or a
Macbook’s built-in USB keyboard is ignored by GRUB. This makes it
impossible to choose which generation to boot. The passphrase of an
encrypted boot partition can be entered though (with US English
keyboard layout instead of the chosen layout).
The attached patch makes the USB keyboard work in the bootloader menu,
but it uses US English layout instead of the chosen layout too. Also
the patch is just imitating what is already in gnu/bootloader/grub.scm
but I do not actually know what I’m doing.
Regards,
Florian
[0001-bootloader-grub-Support-USB-keyboards-when-using-a-k.patch (text/plain, attachment)]
Information forwarded
to
bug-guix <at> gnu.org
:
bug#35585
; Package
guix
.
(Tue, 07 May 2019 16:13:01 GMT)
Full text and
rfc822 format available.
Message #8 received at 35585 <at> debbugs.gnu.org (full text, mbox):
Hi,
"pelzflorian (Florian Pelz)" <pelzflorian <at> pelzflorian.de> skribis:
> From c0c8167cf4f7ddd68567618effc665dd950c2f93 Mon Sep 17 00:00:00 2001
> From: Florian Pelz <pelzflorian <at> pelzflorian.de>
> Date: Sun, 5 May 2019 17:38:47 +0200
> Subject: [PATCH] bootloader: grub: Support USB keyboards when using a
> keyboard-layout.
>
> With this USB keyboards are recognized again, the layout does not currently
> get used by GRUB though.
>
> * gnu/booloader/grub.scm (keyboard-layout-config): Add usb_keyboard terminal
> to terminal_input command.
Oh, interesting. I guess on “PCs” the BIOS/UEFI emulates AT keyboard
even when the keyboard is really an external USB keyboard, which is why
we don’t see that problem.
> --- a/gnu/bootloader/grub.scm
> +++ b/gnu/bootloader/grub.scm
> @@ -360,7 +360,7 @@ entries corresponding to old generations of the system."
> (keyboard-layout-file layout #:grub grub))))
> (when keymap
> (format port "\
> -terminal_input at_keyboard
> +terminal_input at_keyboard usb_keyboard
What do others think? Danny?
I’d like to make sure this is as harmless as it looks.
Ludo’.
Information forwarded
to
bug-guix <at> gnu.org
:
bug#35585
; Package
guix
.
(Tue, 07 May 2019 16:40:02 GMT)
Full text and
rfc822 format available.
Message #11 received at 35585 <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/plain, inline)]
Hi Ludo,
On Tue, 07 May 2019 18:11:55 +0200
Ludovic Courtès <ludo <at> gnu.org> wrote:
> > --- a/gnu/bootloader/grub.scm
> > +++ b/gnu/bootloader/grub.scm
> > @@ -360,7 +360,7 @@ entries corresponding to old generations of the system."
> > (keyboard-layout-file layout #:grub grub))))
> > (when keymap
> > (format port "\
> > -terminal_input at_keyboard
> > +terminal_input at_keyboard usb_keyboard
>
> What do others think? Danny?
>
> I’d like to make sure this is as harmless as it looks.
AT keyboard should also match USB bootp keyboards, but I guess the mac doesn't
support bootp. (USB keyboards have a "bootloader" protocol (BOOTP) and
a "normal" protocol with the rationale being that the "normal" protocol is
too compliated to fit into the bootloader - hence, USB keyboard should support
both--and, when talked to using the bootloader protocol, the PC firmware should
transform it into AT keyboard commands in order to further simplify the
bootloader's job)
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?
[Message part 2 (application/pgp-signature, inline)]
Information forwarded
to
bug-guix <at> gnu.org
:
bug#35585
; Package
guix
.
(Tue, 07 May 2019 17:26:02 GMT)
Full text and
rfc822 format available.
Message #14 received at 35585 <at> debbugs.gnu.org (full text, mbox):
On Tue, May 07, 2019 at 06:11:55PM +0200, Ludovic Courtès wrote:
> Oh, interesting. I guess on “PCs” the BIOS/UEFI emulates AT keyboard
> even when the keyboard is really an external USB keyboard, which is why
> we don’t see that problem.
>
Not for my external USB keyboard on my PC (using an Asus P8H67
motherboard).
Regards,
Florian
Information forwarded
to
bug-guix <at> gnu.org
:
bug#35585
; Package
guix
.
(Tue, 07 May 2019 17:50:02 GMT)
Full text and
rfc822 format available.
Message #17 received at 35585 <at> debbugs.gnu.org (full text, mbox):
On Tue, May 07, 2019 at 07:25:39PM +0200, pelzflorian (Florian Pelz) wrote:
> On Tue, May 07, 2019 at 06:11:55PM +0200, Ludovic Courtès wrote:
> > Oh, interesting. I guess on “PCs” the BIOS/UEFI emulates AT keyboard
> > even when the keyboard is really an external USB keyboard, which is why
> > we don’t see that problem.
> >
>
> Not for my external USB keyboard on my PC (using an Asus P8H67
> motherboard).
>
Sorry, I was wrong. It works on my PC on Guix System installer 1.0.
When it did not work before, I must have done something wrong; my USB
hub is a little flaky.
Sorry.
Information forwarded
to
bug-guix <at> gnu.org
:
bug#35585
; Package
guix
.
(Tue, 07 May 2019 22:11:02 GMT)
Full text and
rfc822 format available.
Message #20 received at 35585 <at> debbugs.gnu.org (full text, mbox):
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
Information forwarded
to
bug-guix <at> gnu.org
:
bug#35585
; Package
guix
.
(Wed, 08 May 2019 10:04:01 GMT)
Full text and
rfc822 format available.
Message #23 received at 35585 <at> debbugs.gnu.org (full text, mbox):
Hi Danny,
Danny Milosavljevic <dannym <at> scratchpost.org> skribis:
> 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?
I don’t know. I added it in 8d058e7b1b1a409d3d9cc29c5650a98db4e78783,
which was inspired by a patch posted by nee, but in hindsight I think
this has nothing to do here. So I’m happy to remove that
“terminal_input” line.
Florian, can you check whether removing the line fixes the issue for
you?
We should make sure it also works for the rest of us.
Thanks for your feedback, Danny!
Ludo’.
Information forwarded
to
bug-guix <at> gnu.org
:
bug#35585
; Package
guix
.
(Wed, 08 May 2019 12:25:01 GMT)
Full text and
rfc822 format available.
Message #26 received at 35585 <at> debbugs.gnu.org (full text, mbox):
On Wed, May 08, 2019 at 12:03:21PM +0200, Ludovic Courtès wrote:
> Florian, can you check whether removing the line fixes the issue for
> you?
>
Yes, it fixes having no keyboard input at all on my Macbook (the
layout is not applied though).
On Wed, May 08, 2019 at 12:09:45AM +0200, pelzflorian (Florian Pelz) wrote:
> 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
>
>
>
Regards,
Florian
Reply sent
to
Ludovic Courtès <ludo <at> gnu.org>
:
You have taken responsibility.
(Thu, 09 May 2019 10:16:02 GMT)
Full text and
rfc822 format available.
Notification sent
to
"pelzflorian (Florian Pelz)" <pelzflorian <at> pelzflorian.de>
:
bug acknowledged by developer.
(Thu, 09 May 2019 10:16:03 GMT)
Full text and
rfc822 format available.
Message #31 received at 35585-done <at> debbugs.gnu.org (full text, mbox):
"pelzflorian (Florian Pelz)" <pelzflorian <at> pelzflorian.de> skribis:
> On Wed, May 08, 2019 at 12:03:21PM +0200, Ludovic Courtès wrote:
>> Florian, can you check whether removing the line fixes the issue for
>> you?
>>
>
> Yes, it fixes having no keyboard input at all on my Macbook (the
> layout is not applied though).
I’ve removed the ‘terminal_input at_keyboard’ line in
cae0725b809449dcdebc2d84cf997e051e689e06.
Ludo’.
Information forwarded
to
bug-guix <at> gnu.org
:
bug#35585
; Package
guix
.
(Thu, 09 May 2019 12:53:02 GMT)
Full text and
rfc822 format available.
Message #34 received at 35585-done <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/plain, inline)]
Hi Florian,
> "pelzflorian (Florian Pelz)" <pelzflorian <at> pelzflorian.de> skribis:
> Yes, it fixes having no keyboard input at all on my Macbook (the
> layout is not applied though).
As for the layout not being applied, can you please report a bug with grub
upstream? I've checked grub-core/term/usb_keyboard.c and they usually do
call grub_term_map_key in parse_keycode--so it should work. Hmm...
(Your Grub config is in /boot/grub/grub.cfg--maybe they want it)
[Message part 2 (application/pgp-signature, inline)]
Information forwarded
to
bug-guix <at> gnu.org
:
bug#35585
; Package
guix
.
(Mon, 13 May 2019 14:00:02 GMT)
Full text and
rfc822 format available.
Message #37 received at 35585-done <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/plain, inline)]
Ludovic Courtès <ludo <at> gnu.org> writes:
[...]
> I’ve removed the ‘terminal_input at_keyboard’ line in
> cae0725b809449dcdebc2d84cf997e051e689e06.
the commit message states
bootloader: grub: Remove unneeded 'terminal_output'
but I guess should be 'terminal_input' :-)
Gio'
[...]
--
Giovanni Biscuolo
Xelera IT Infrastructures
[signature.asc (application/pgp-signature, inline)]
Information forwarded
to
bug-guix <at> gnu.org
:
bug#35585
; Package
guix
.
(Mon, 13 May 2019 20:35:03 GMT)
Full text and
rfc822 format available.
Message #40 received at 35585-done <at> debbugs.gnu.org (full text, mbox):
Giovanni Biscuolo <g <at> xelera.eu> skribis:
> Ludovic Courtès <ludo <at> gnu.org> writes:
>
> [...]
>
>> I’ve removed the ‘terminal_input at_keyboard’ line in
>> cae0725b809449dcdebc2d84cf997e051e689e06.
>
> the commit message states
>
> bootloader: grub: Remove unneeded 'terminal_output'
>
> but I guess should be 'terminal_input' :-)
Oops, indeed, sorry for the confusion!
Ludo’.
bug archived.
Request was from
Debbugs Internal Request <help-debbugs <at> gnu.org>
to
internal_control <at> debbugs.gnu.org
.
(Tue, 11 Jun 2019 11:24:10 GMT)
Full text and
rfc822 format available.
This bug report was last modified 4 years and 320 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.