USB or docked keyboard dead at the LUKS passphrase prompt (keyboard hook after autodetect)
The Mkinitcpio wiki (raw) supports the cause: the keyboard hook must sit before autodetect for systems booted with different hardware, and xhci_hcd for a USB 3 hub and i2c_hid_acpi for some laptop keyboards. Archinstall issue 630 and forum thread 280596 both report the fix as moving keyboard before autodetect. On this machine /etc/mkinitcpio.conf.d/omarchy_hooks.conf assigns HOOKS=(base udev plymouth keyboard autodetect ... encrypt ...) so the Omarchy branch is right, and a MODULES+= drop-in sorting after it is safe because omarchy_hooks.conf only reads MODULES. The defect is the plain Arch example. The stock /etc/mkinitcpio.conf in mkinitcpio 41.1 is systemd-based (base systemd autodetect microcode modconf kms keyboard sd-vconsole block filesystems fsck), and an encrypted systemd setup uses sd-encrypt with rd.luks options. The record gave a full busybox line with udev and encrypt to paste in, which on such a system swaps the init and the unlock hook, so the root device is never unlocked and the machine does not boot. The fix now says to move keyboard within the existing line and gives both variants. The Omarchy verify was also missing. Not exercised: no initramfs was rebuilt.
Rebuilding the initramfs with a broken HOOKS line can make the machine unbootable. Keep the fallback image on plain Arch (/boot/initramfs-linux-fallback.img is built by the default preset), and have a live USB ready.
Symptom
"At boot it asks for my disk password but my external keyboard does nothing." Typical setups are a laptop with a USB keyboard, a keyboard behind a USB 3 hub or dock, or a desktop where the keyboard was swapped. The keyboard works once the system is up. Often hit right after an archinstall install.
Cause
mkinitcpio's keyboard hook adds keyboard drivers to the initramfs. Placed after autodetect, it includes only the drivers for hardware present when the image was built. A keyboard on a different controller (a USB 3 hub needing xhci_hcd, an I2C laptop keyboard needing i2c_hid_acpi, a dock) has no driver in early userspace. The Arch wiki says the hook must come before autodetect on systems booted with different hardware configurations.
Fix
## Plain Arch, EndeavourOS, CachyOS
In /etc/mkinitcpio.conf, move keyboard (and keymap or sd-vconsole with it) before autodetect. **Keep your existing init and encryption hooks**: do not change systemd to udev or sd-encrypt to encrypt, or the root device will not unlock.
Systemd-based line (the mkinitcpio default since version 39), for example:
HOOKS=(base systemd keyboard sd-vconsole autodetect microcode modconf kms block sd-encrypt filesystems fsck)
Busybox-based line, for example:
HOOKS=(base udev keyboard keymap consolefont autodetect microcode modconf kms block encrypt filesystems fsck)
For a keyboard behind a USB 3 hub, or a laptop keyboard on I2C, also add the module:
MODULES=(xhci_hcd i2c_hid_acpi)
Then rebuild:
sudo mkinitcpio -P
## Omarchy 4
Editing /etc/mkinitcpio.conf has no effect, because /etc/mkinitcpio.conf.d/omarchy_hooks.conf assigns HOOKS wholesale and already places keyboard before autodetect. If a keyboard is still dead on Omarchy, the cause is different. See i8042-builtin-keyboard-dead-at-luks-prompt for a built-in PS/2 keyboard and bluetooth-keyboard-cannot-unlock-luks for Bluetooth. An I2C keyboard can get its module through a drop-in that sorts last:
echo 'MODULES+=(i2c_hid_acpi)' | sudo tee /etc/mkinitcpio.conf.d/zz-keyboard.conf
sudo limine-mkinitcpio
Verify
Plain Arch: lsinitcpio /boot/initramfs-linux.img | grep -E 'xhci|hid' lists the drivers. Omarchy: grep -n HOOKS /etc/mkinitcpio.conf.d/omarchy_hooks.conf shows keyboard before autodetect, and sudo limine-mkinitcpio finishes without skipping.. On either, reboot with only the external keyboard attached and type the passphrase.