Bug 839075

Summary: USB keyboard doesn't work for entering password pre root pivot with 3.5 kernels (3.4 works OK)
Product: [Fedora] Fedora Reporter: Bruno Wolff III <bruno>
Component: dracutAssignee: dracut-maint
Status: CLOSED RAWHIDE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: bruno, dracut-maint, harald, jonathan, mbroz, robatino, udovdh
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-07-12 08:21:32 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 752654    
Attachments:
Description Flags
lsusb -v output
none
lsmod output
none
lsmod output under 3.4 kernel none

Description Bruno Wolff III 2012-07-10 20:52:43 UTC
Created attachment 597423 [details]
lsusb -v output

Description of problem:
When I boot 3.5 kernels I can't use a USB keyboard to enter the rootfs password. Once I get past the root pivot, I can use them. (To work around this I have a PS/2 keyboard.)
When I boot 3.4 kernels (using the same dracut version to build the initramfs) then I can use USB keyboards.

Version-Release number of selected component (if applicable):
dracut-020-70.git20120710.fc18.x86_64
kernel-3.4.4-3.fc17.x86_64
kernel-3.5.0-0.rc6.git0.2.fc18.x86_64
systemd-186-2.fc18.x86_64
plymouth-0.8.6-1.fc18.x86_64


How reproducible:
Seems to happen every boot

I marked this as a potential blocker, but that may depend on how much USB hardware is affected.

Comment 1 Bruno Wolff III 2012-07-10 21:43:20 UTC
Since I was testing plymouth, I tried again with dracut-020-72.git20120710.fc18 and am seeing the same problem.

Comment 2 Harald Hoyer 2012-07-11 06:27:22 UTC
(In reply to comment #1)
> Since I was testing plymouth, I tried again with
> dracut-020-72.git20120710.fc18 and am seeing the same problem.

Can you give me a "lsmod" once your USB keyboard is working? Or just the list of modules, which are needed for it to work?

Comment 3 Bruno Wolff III 2012-07-11 12:18:22 UTC
Created attachment 597547 [details]
lsmod output

Comment 4 Bruno Wolff III 2012-07-11 18:09:38 UTC
Created attachment 597643 [details]
lsmod output under 3.4 kernel

Just in case it helps find out what changed I have included lsmod output from under a 3.4 kernel.

Comment 5 Bruno Wolff III 2012-07-11 18:43:44 UTC
I tested dracut-020-84.git20120711.fc18.x86_64 and still no joy.

Comment 6 Bruno Wolff III 2012-07-11 21:25:42 UTC
adding the following in /etc/dracut.conf fixes the issue for me:
add_drivers+="hid_generic"

hid_generic stood out on the list of modules loaded under the 3.5 kernel that weren't loaded under the 3.4 kernel. So I tried manually including it and it did the trick.

Comment 7 Harald Hoyer 2012-07-12 08:21:32 UTC
(In reply to comment #6)
> adding the following in /etc/dracut.conf fixes the issue for me:
> add_drivers+="hid_generic"
> 
> hid_generic stood out on the list of modules loaded under the 3.5 kernel
> that weren't loaded under the 3.4 kernel. So I tried manually including it
> and it did the trick.

Thanks! Will be in the next dracut!

Comment 8 Bruno Wolff III 2012-07-12 19:33:43 UTC
The kernel guys are talking about making sure hid_generic gets built as part of the kernel again and not as a module.

Comment 9 Harald Hoyer 2012-07-16 08:40:23 UTC
(In reply to comment #8)
> The kernel guys are talking about making sure hid_generic gets built as part
> of the kernel again and not as a module.

no problem, if it's builtin, it will just be a noop

Comment 10 udo 2012-11-04 13:48:42 UTC
or add a dracut.conf.d/usbkayboard.conf:

add_drivers+="hid-generic"