Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 786303 - Cannot boot with full disk encryption and Logitech wireless keyboard
Cannot boot with full disk encryption and Logitech wireless keyboard
Product: Fedora
Classification: Fedora
Component: dracut (Show other bugs)
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: dracut-maint
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2012-01-31 20:23 EST by Robert Buchholz
Modified: 2012-02-20 07:33 EST (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2012-02-20 07:33:10 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Robert Buchholz 2012-01-31 20:23:13 EST
Description of problem:
Since upgrading Fedora 16 from kernel 3.1 to kernel 3.2 (3.2.2-1.fc16.x86_64 specifically), the keyboard is not usable at the boot prompt anymore. It is usable in Grub before and in the console after booting.

The reason seems to be that since Kernel 3.2, the USB device has its own driver to support multiple hid devices from one usb device (hid_logitech_dj) and does not use the regular usbhid anymore:

In /etc/dracut.conf set
and then run
 /sbin/dracut -f /boot/initramfs-3.2.2-1.fc16.x86_64.img 3.2.2-1.fc16.x86_64

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

How reproducible:

Steps to Reproduce:
1. Plug in Logitech keyboard with Unifying Receiver
2. Upgrade to Kernel >=3.2
3. Reboot
Actual results:
Cannot enter password in initramfs

Expected results:
Keyboard is usable in initramfs

Additional info:
Comment 1 Harald Hoyer 2012-02-20 07:33:10 EST
workaround for F16:

edit /etc/dracut.conf:

add_drivers+=" hid-logitech-dj "

F17/rawhide dracut version has it hardcoded right now.

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