summaryrefslogtreecommitdiff
path: root/config/grub/nvme/patches/0010-keylayouts-don-t-print-Unknown-key-message.patch
blob: ed3c1f4a1c4cce950772b354a5668df7b571507a (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
From 4e89b0da7213b710bfb4d95a20e34b193f39e58c Mon Sep 17 00:00:00 2001
From: Leah Rowe <leah@libreboot.org>
Date: Tue, 31 Oct 2023 10:33:28 +0000
Subject: [PATCH 10/14] keylayouts: don't print "Unknown key" message

on keyboards with stuck keys, this results in GRUB just
spewing it repeatedly, preventing use of GRUB.

in such cases, it's still possible to use the keyboard,
and we should let the user at least boot.

it often appears when people plug in faulty usb keyboards,
but can appear for laptop keyboards too; one of my e6400
has stuck keys.

with this patch, grub should be a bit more reliable in
terms of user experience, when the keyboard is faulty.

Signed-off-by: Leah Rowe <leah@libreboot.org>
---
 grub-core/commands/keylayouts.c | 1 -
 1 file changed, 1 deletion(-)

diff --git a/grub-core/commands/keylayouts.c b/grub-core/commands/keylayouts.c
index aa3ba34f2..445fa0601 100644
--- a/grub-core/commands/keylayouts.c
+++ b/grub-core/commands/keylayouts.c
@@ -174,7 +174,6 @@ grub_term_map_key (grub_keyboard_key_t code, int status)
   key = map_key_core (code, status, &alt_gr_consumed);
 
   if (key == 0 || key == GRUB_TERM_SHIFT) {
-    grub_printf ("Unknown key 0x%x detected\n", code);
     return GRUB_TERM_NO_KEY;
   }
 
-- 
2.39.2