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)

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.

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).

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.

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.

Note

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