Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#36735 - usb keyboard hook and input doesn't work unless mkinitcpio is run twice

Attached to Project: Arch Linux
Opened by Divan Santana (divansantana) - Friday, 30 August 2013, 06:25 GMT
Last edited by Dave Reisner (falconindy) - Saturday, 31 August 2013, 13:37 GMT
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To No-one
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
usb keyboard hook and input doesn't work unless mkinitcpio is run twice.

Additional info:
* mkinitcpio 0.15.0-1 although this has been occuring for several releases.
* config /etc/mkinitcpio.conf


Steps to reproduce:
Have existing kernel installed and keyboard hook enabled in mkinitcpio.conf .
Then do a system upgrade, see a new kernel. New kernel is upgraded and installed and you reboot.
You type in your encryption password on usb keybord and notice the usb keyboard input does not work.

To resolve this one needs to recreate the initial ramdisk, `mkinitcpio -p linux`, then reboot and the problem is resolved.
It is a bug because on every upgrade the usb keyboard input stops and requires a user to recreate the keyboard input hook.
This task depends upon

Closed by  Dave Reisner (falconindy)
Saturday, 31 August 2013, 13:37 GMT
Reason for closing:  Not a bug
Additional comments about closing:  Autodetect is a whitelist. If you need things whitelisted, they need to be present at the time autodetection takes place.
Comment by Dave Reisner (falconindy) - Friday, 30 August 2013, 15:29 GMT
I think it's more likely that you're upgrading the kernel without your USB keyboard plugged in. You're seeing the "intended" behavior of the autodetect hook. It cannot possibly whitelist what isn't available.

Regardless, the bug description isn't sufficient for me to replicate this failure.
Comment by Divan Santana (divansantana) - Saturday, 31 August 2013, 13:34 GMT
It looks like the problem is like you suggest, which is not how I understood the HOOKS line(looks like I misunderstood it).

Basically with my config set like so:
HOOKS="base udev autodetect modconf block encrypt lvm2 filesystems keyboard fsck"
Then after a kernel upgrade, even though it diplays " -> Running build hook: [keyboard]" while upgrading, the usb keyboard input doesn't work during boot, IF the usb keyboard input wasn't plugged in during that kernel upgrade.

After reading the mkinitcpio wiki, it suggests putting the hook before autodetect which resolves the issue.
HOOKS="base udev keyboard autodetect modconf block encrypt lvm2 filesystems fsck"
Now if I upgrade my kernel without usb keyboard plugged in, my usb keyboard still works during boot up.

If the above makes sense and is the intended behaviour (I now think it is), then it's not a bug and can be closed.

Thanks,
Divan

Loading...