Bug 2228891 - Disk encryption password not accepting input in kernel 6.4.7
Summary: Disk encryption password not accepting input in kernel 6.4.7
Keywords:
Status: NEW
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 38
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-08-03 14:13 UTC by Andy Wang
Modified: 2023-08-10 03:11 UTC (History)
16 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Andy Wang 2023-08-03 14:13:15 UTC
1. Please describe the problem:
After upgrading to kernel-6.4.7-200.fc38.x86_64 upon initial boot I'm unable to input my disk encryption password using my laptops built-in keyboard.

It works fine when I boot 6.4.6: 
Linux 6.4.6-200.fc38.x86_64 #1 SMP PREEMPT_DYNAMIC Mon Jul 24 20:51:12 UTC 2023

It appears that a USB keyboard "may" work (I have a yubikey attached but no other usb keyboard right now but tapping the yubikey sends the yubikey token to the disk encryption password dialog)

It's possible this issue is unique to my device - asus Zenbook S13 OLED UM5302TA model.

I'm not even sure how to debug this or get any kernel messages at this stage of the boot process.

Comment 2 Hans de Goede 2023-08-09 08:15:54 UTC
(In reply to Andy Wang from comment #1)
> https://bugzilla.kernel.org/show_bug.cgi?id=217718
> and
> https://bugzilla.kernel.org/show_bug.cgi?id=217726

Right this does sound like it is the same issue as those bugs.

The Fedora 6.4.9 kernel update which came out yesterday reverts the changes causing those bugs when going from 6.4.6 > 6.4.7 or 6.4.8 . So if you install the Fedora 6.4.9 kernel update then this issue should be gone.

Comment 3 Andy Wang 2023-08-10 03:11:59 UTC
Confirmed.  install 6.4.9 from updates-testing and the issue is gone. Thank you!!


Note You need to log in before you can comment on or make changes to this bug.