FS#34492 - USB keyboard is not detected in early boot-process (Kernel 3.8.x)

Attached to Project: Arch Linux
Opened by Robin de Silva Jayasinghe (rjayasinghe) - Wednesday, 27 March 2013, 12:01 GMT
Last edited by Dave Reisner (falconindy) - Wednesday, 27 March 2013, 19:28 GMT
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To No-one
Architecture x86_64
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
I add the keyboard hook to the HOOKS section of mkinitcpio.conf, regenerated the image with mkinitcpio -p linux and reboot. The keyboard is accessible in BIOS and syslinux. However, it cannot be used when I want to enter the passphrase for my LUKS partition.

When I add ehci_hcd to the MODULES section of mkinitcpio, the keyboard is accessible. As the issue has an easy workaround i would not rate it as a severe bug. However it indicates that something is wrong with loading modules based on the keyboard HOOK.

My hardware is

* Thinkpad x230
* Cherry keyboard, Logitech illuminated keyboard (both with the same issue).

Additional info:
* package version(s)
* mkinitcpio.conf with ehci_hcd in MODULES (remove it to reproduce)
* syslinux.cfg

Steps to reproduce:
* prerequisite: have a LUKS partition mounted at / (with a seperate unencrypted /boot partition) that wants to be decrypted and mounted during boot
* remove ehci_hcd from MODULES in attached mkinitcpio.conf
* mkinitcpio -p linux
* reboot
This task depends upon

Closed by  Dave Reisner (falconindy)
Wednesday, 27 March 2013, 19:28 GMT
Reason for closing:  Not a bug
Additional comments about closing:  autodetect cannot possibly whitelist hardware it doesn't know about.
Comment by Dave Reisner (falconindy) - Wednesday, 27 March 2013, 12:30 GMT
Did you regenerate the image with the keyboard plugged in? If not, there's absolutely no way the autodetect trimmed image will ever know that you needed USB host support from ehci_hcd (ehci_pci, really).
Comment by Robin de Silva Jayasinghe (rjayasinghe) - Wednesday, 27 March 2013, 12:53 GMT
This sounds reasonable. However, for someone who does not understand the underlying mechanics and just follows the installation documentation this is a pitfall. I will validate this and close the bug-report if this helps.

Best Regards,
Robin
Comment by Dave Reisner (falconindy) - Wednesday, 27 March 2013, 19:27 GMT
I don't think it's unreasonable to expect that auto detection only detects what's present on the system. If you need to ensure that a module is included regardless of your current configuration, then you've already found the solution -- add the module to your mkinitcpio.conf.

Loading...