RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 2020927 - GRUB_TERMINAL_INPUT=at_keyboard makes grub stay on boot menu instead of starting the timeout
Summary: GRUB_TERMINAL_INPUT=at_keyboard makes grub stay on boot menu instead of start...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: grub2
Version: 8.4
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: rc
: ---
Assignee: Bootloader engineering team
QA Contact: Release Test Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-11-07 12:18 UTC by Pradeep Jagtap
Modified: 2023-02-16 11:06 UTC (History)
5 users (show)

Fixed In Version: grub2-2.02-114.el8
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-05-10 15:31:42 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
Patch fixing the issue (1.02 KB, patch)
2021-11-09 09:44 UTC, Renaud Métrich 		no flags Details | Diff
No countdown with 2.02-106.el8.x86_64 (5.00 KB, image/png)
2022-02-15 13:56 UTC, Renaud Métrich 		no flags Details
Countdown with 2.02-114.el8.x86_64 (5.63 KB, image/png)
2022-02-15 13:57 UTC, Renaud Métrich 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-101907 0 None None None 2021-11-07 12:18:28 UTC
Red Hat Issue Tracker RTT-4234 0 None None None 2022-02-14 14:43:46 UTC
Red Hat Issue Tracker RTT-4235 0 None None None 2022-02-14 14:43:56 UTC
Red Hat Knowledge Base (Solution) 6494601 0 None None None 2021-11-12 10:02:08 UTC
Red Hat Product Errata RHSA-2022:2110 0 None None None 2022-05-10 15:32:26 UTC

Description Pradeep Jagtap 2021-11-07 12:18:11 UTC 
Description of problem:
 GRUB_TERMINAL_INPUT=at_keyboard makes grub stay on boot menu instead of starting the timeout

Version-Release number of selected component (if applicable):
grub2-pc-2.02-99.el8_4.1.x86_64

How reproducible:
Steps to Reproduce:
1. Add below line in /etc/default/grub fi;e
         GRUB_TERMINAL_INPUT="at_keyboard"
2. Regenerate grub.cfg file
       # grub2-mkconfig -o /boot/grub2/grub.cfg
3. Reboot the system

Actual results:
Grub menu is shown, no timeout available, need to manually select the kernel

Expected results:
Grub menu with timeout
Comment 3 Renaud Métrich 2021-11-08 16:21:08 UTC 
Argh! I'll work on this tomorrow.
Actually I'm not sure this was ever tested since I was more concerned with making sure "a" prints a "a" in non-us keyboards, than verifying timeout was still working ...
Comment 4 Renaud Métrich 2021-11-09 08:53:56 UTC 
I confirm I can reproduce as well.

A workaround is to use the following property in /etc/default/grub and rebuild the menu:
-------- 8< ---------------- 8< ---------------- 8< ---------------- 8< --------
GRUB_TIMEOUT_STYLE="countdown"
-------- 8< ---------------- 8< ---------------- 8< ---------------- 8< --------
Comment 5 Renaud Métrich 2021-11-09 09:43:54 UTC 
This was fixed Upstream by:

commit 33203ca3484717712b54e199c46ae8a818374284
Author: Michael Bideau <mica.devel>
Date:   Wed Oct 2 23:48:10 2019 +0200

    at_keyboard: Fix unreliable key presses
    
    This patch fixes an issue that prevented the at_keyboard module to work
    (for me). The cause was a bad/wrong return value in the
    grub_at_keyboard_getkey() function in grub-core/term/at_keyboard.c file
    at line 237. My symptoms were to have an unresponsive keyboard. Keys
    needed to be pressed 10x and more to effectively be printed sometimes
    generating multiple key presses (after 1 or 2 sec of no printing). It
    was very problematic when typing passphrase in early stage (with
    GRUB_ENABLE_CRYPTODISK). When switched to "console" terminal input
    keyboard worked perfectly. It also worked great with the GRUB 2.02
    packaged by Debian (2.02+dfsg1-20). It was not an output issue but an
    input one.
    
    I've managed to analyze the issue and found that it came from the commit
    216950a4e (at_keyboard: Split protocol from controller code.). Three
    lines where moved from the fetch_key() function in
    grub-core/term/at_keyboard.c file to the beginning of
    grub_at_keyboard_getkey() function (same file). However, returning -1
    made sense when it happened in fetch_key() function but not anymore in
    grub_at_keyboard_getkey() function which should return GRUB_TERM_NO_KEY.
    I think it was just an incomplete cut-paste missing a small manual
    correction. Let's fix it.

See also attached patch.
Comment 6 Renaud Métrich 2021-11-09 09:44:30 UTC 
Created attachment 1840840 [details]
Patch fixing the issue
Comment 10 Renaud Métrich 2022-02-15 13:56:36 UTC 
Created attachment 1861249 [details]
No countdown with 2.02-106.el8.x86_64
Comment 11 Renaud Métrich 2022-02-15 13:57:07 UTC 
Created attachment 1861250 [details]
Countdown with 2.02-114.el8.x86_64
Comment 12 Renaud Métrich 2022-02-15 13:59:00 UTC 
I can confirm it works with 2.02-114.el8.x86_64 compared to 2.02-106.el8.x86_64.

Screenshots attached.

Procedure:

1. Configure at_keyboard with FR keyboard and reboot (https://access.redhat.com/solutions/5624811)

  --> no countdown

2. Update to 2.02-114.el8.x86_64 and execute "grub2-install" and reboot

  --> 5 seconds countdown
Comment 14 Petr Janda 2022-02-17 17:42:15 UTC 
Verified: tested based on comment 12
Comment 19 errata-xmlrpc 2022-05-10 15:31:42 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Low: grub2 security, bug fix, and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2022:2110
Note You need to log in before you can comment on or make changes to this bug.