Bug 867693 - USB keyboard deactivated during LUKS passphrase prompt
Summary: USB keyboard deactivated during LUKS passphrase prompt
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel-module-thinkpad
Version: 30
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Jason Carpenter
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-10-18 05:53 UTC by rob
Modified: 2019-06-17 15:18 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-06-17 15:18:49 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1211309 0 unspecified CLOSED No keyboard at boot/LUKS password prompt after upgrade to kernel 3.19.3-100 2021-02-22 00:41:40 UTC

Internal Links: 1211309

Description rob 2012-10-18 05:53:30 UTC
Description of problem:
When trying to boot the kernel-3.6.1-1.fc17.x86_64 my usb keyboard is deactivated during the LUKS passphrase prompt. No passphrase can be given. The keyboard was available in Grub to select a Kernel and it works after F17 is done booting.

The usb keyboard worked (during the LUKS passphrase prompt) in all previous versions (up to kernel-3.5.6-1.fc17.x86_64).

Version-Release number of selected component (if applicable):
kernel-3.6.1-1.fc17.x86_64

How reproducible:

Steps to Reproduce:
1. Start Laptop
2. Select kernel-3.6.1-1.fc17.x86_64 at Grub selection screen
3. Try to enter the required LUKS passphrase
  
Actual results:
No passphrase can be given. As a workaround I now switched back to kernel-3.5.6-1.fc17.x86_64  

Expected results:
Ability to enter the passphrase.

Additional info:
Using a Lenovo Thinkpad T420 icw a Lenovo Thinkpad USB Keyboard (SK-8855)

Comment 1 rob 2012-10-22 09:41:38 UTC
This also applies to kernel-3.6.2-4.fc17.x86_64

Comment 2 rob 2012-10-30 06:38:39 UTC
This also applies to kernel-3.6.3-1.fc17.x86_64

Comment 3 rob 2012-11-09 07:57:43 UTC
This also applies to kernel-3.6.5-1.fc17.x86_64

I noticed that this issue does not occur icw a similar keyboard which is the: IBM Thinkpad USB Keyboard (SK-8845). In both cases I am using the exact same USB port.

Note: The IBM version of this keyboard is much older than the Lenovo one.

I hope this additional information helps to determine the root cause of this issue.

Comment 4 rob 2012-11-26 08:09:19 UTC
This also applies to kernel-3.6.7-4.fc17.x86_64

Comment 5 rob 2012-12-03 11:36:08 UTC
This also applies to 3.6.8-2.fc17.x86_64

Comment 6 rob 2013-01-07 13:46:39 UTC
This still applies to 3.6.11-1.fc17.x86_64

Comment 7 rob 2013-01-21 06:44:05 UTC
Still applies to 3.6.11-5.fc17.x86_64

Comment 8 rob 2013-01-31 07:56:10 UTC
This issue still applies to 3.7.4-204.fc18.x86_64 (after upgrade to Fedora 18, using fedup).

Comment 9 Jacobo Aragunde 2013-09-19 08:15:56 UTC
I have the same issue with a SK-8855 keyboard, using F19 with any of the kernel versions it provides (currently 3.10.11).

I have also noticed that other external keyboards don't have this problem (I've tried several makes and models).

Comment 10 Fedora End Of Life 2013-12-21 09:08:40 UTC
This message is a reminder that Fedora 18 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 18. 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 WONTFIX if it remains open with a Fedora 
'version' of '18'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 18's end of life.

Thank you for reporting this issue and we are sorry that we may not be 
able to fix it before Fedora 18 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, you are encouraged  change the 'version' to a later Fedora 
version prior to Fedora 18's end of life.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 11 Jacobo Aragunde 2013-12-22 11:26:18 UTC
This bug still happens in F19 with 3.11.10-200.fc19.x86_64 kernel.

Comment 12 Fedora End Of Life 2014-02-05 12:37:29 UTC
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 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. If you experience problems, please add a comment to this
bug.

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

Comment 13 Dominic Delabruere 2019-06-17 11:24:09 UTC
I had not experienced this bug in Fedora 29 but am now experiencing it in Fedora 30 on a new laptop for the past few minor kernel releases, now on kernel.x86_64 5.1.8-300.fc30. Just as the original reporter described, I can use my USB keyboard during GRUB selection and at the display manager login screen, but not at the LUKS password prompt. This has been broken since I initially installed the Fedora 30 RC on this laptop (Lenovo ThinkPad T480s) when it was new, so I have not tried reverting to a previous kernel version. The USB keyboard I'm using is a Logitech MK710, connected to the laptop via a wireless USB dongle inserted into the Thunderbolt dock, but inserting the dongle directly into the laptop has not addressed the problem. The only workaround I have so far is to use the laptop's built-in keyboard to complete the LUKS password prompt.

Comment 14 Dominic Delabruere 2019-06-17 15:18:49 UTC
Update: The problem as I experienced it on my laptop unexpectedly resolved itself after I reopened the issue this morning, despite no configuration changes or RPM updates on my end. Closing this bug again as I cannot reliably reproduce it any longer.


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