mirror of
https://codeberg.org/canoeboot/cbmk.git
synced 2025-01-10 17:19:57 +00:00
581d4a66ac
remove nvme support from the "default" grub tree now there are three trees: * default: no xhci or nvme patches * nvme: contains nvme support * xhci: contains xhci and nvme support this is in case a bug like lbmk issue #216 ever occurs again, as referenced before during lbmk audit 5 there is no indication that the nvme patch causes any issues, but after previous experience i want to be sure Signed-off-by: Leah Rowe <leah@libreboot.org>
38 lines
1.2 KiB
Diff
38 lines
1.2 KiB
Diff
From 0a6abeb40ac4284fbff6ef5958989d561b6290a7 Mon Sep 17 00:00:00 2001
|
|
From: Leah Rowe <leah@libreboot.org>
|
|
Date: Tue, 31 Oct 2023 10:33:28 +0000
|
|
Subject: [PATCH 1/1] 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
|
|
|