Bug 1978104 - No keyboard when prompted for luks password on macbook
Summary: No keyboard when prompted for luks password on macbook
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Fedora
Classification: Fedora
Component: dracut
Version: 34
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: dracut-maint-list
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-07-01 07:02 UTC by Ken Fallon
Modified: 2022-06-09 08:36 UTC (History)
9 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2022-06-07 20:44:41 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Ken Fallon 2021-07-01 07:02:17 UTC
Description of problem:
After a fresh install of F34 on a MacBook, the Laptop keyboard works in grub, but when the LUKS prompt is displayed the Laptop keyboard is not working.

Using an external usb keyboard allows the password to be entered, and once past the LUKS prompt the keyboard works again.

I've seen the same issue reported on the ARC forums and they say "In the configure system stage, edit /etc/mkinitcpio.conf and ensure the keyboard hook is in the HOOKS line somewhere after the autodetect hook. This will load the drivers for your keyboard in case you need to use it before Arch boots (e.g. entering a LUKS password or using the troubleshooting shell)."

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Install fedora on a MacBook
2. Enable encryption on the disk
3. Reboot

Actual results:
Can not use the Laptop Keyboard to enter LUKS password

Expected results:
Can use the Laptop Keyboard to enter LUKS password

Additional info:
- https://wiki.archlinux.org/title/Mac
- https://unix.stackexchange.com/questions/342353/problem-keyboard-layout-in-boot-with-luks
- https://bugzilla.redhat.com/show_bug.cgi?id=867693

Comment 1 Vladimír Slávik 2021-09-20 13:31:09 UTC
Reassigning to dracut - we didn't change anything related to keyboards.

Comment 2 Ben Cotton 2022-05-12 15:05:02 UTC
This message is a reminder that Fedora Linux 34 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 34 on 2022-06-07.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
'version' of '34'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 34 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

Comment 3 Ben Cotton 2022-06-07 20:44:41 UTC
Fedora Linux 34 entered end-of-life (EOL) status on 2022-06-07.

Fedora Linux 34 is no longer maintained, which means that it
will not receive any further security or bug fix updates. As a result we
are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release.

Thank you for reporting this bug and we are sorry it could not be fixed.

Comment 4 Ken Fallon 2022-06-09 08:36:00 UTC
For those coming to this later, the issue is fixed in some update. Sorry I have no more information than that.


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