Keyboard gets inactive just before luksOpen

General system Kernel, boot, graphics & hardware
1

Coming from arcolinux i now work for 1 month with EOS without any issues, now all the sudden the keyboard is dead right after the boot process comes to the passphrase in cryptography setup - the keyboard worked seconds before e.g. within the boot delay screen for the kernel choice (i can choose the failsafe kernel but it runs into the same problem).

I then booted from installer image, chrooted to my mounted partition and updated all packages but the strange behaviour did not change. Journalctl shows no fails or issues with keyboard, input device or USB ports, dracut is 111_something.

What can i do or try next ?

2

see this Possible Manual Intervention Required After xkeyboard-config 2.48-1 Update

3

You also rebuild initramfs?

systemd-boot:

reinstall-kernels

Grub:

dracut-rebuild

In case it’s also about USB settings in bios? May Bios is reset to default.

4

right you are, next step is rebuild initramfs and systemd-boot and report back asap, thank you

5

i will check the mkinitcpio config file for modules load order, thx

6

EndeavourOS using dracut btw:
https://discovery.endeavouros.com/system-rescue/dracut/2022/12/

7

This did not solve the issue for me. The problem is that the keyboard kernel module is not loaded at that point.

To fix it with systemd-boot and dracut I did the following:

Step 0: chroot into the system.

Step 1: Figure out which module your keyboard uses. I did this with

dmesg | grep hid

lsmod | grep hid

In my case, the module was hid_apple.

Step 2: Follow https://wiki.archlinux.org/title/Dracut#Early_kernel_module_loading by making the file “myflags.conf” in /etc/dracut.conf.d/ and writing into it

force_drivers+=" hid_apple "

(replace “hid_apple” with the module that you require.)

Step 3: Run

dracut -f --regenerate-all

reinstall-kernels

Done!

8

Welcome to the EndeavourOS forum. :handshake: I hope you enjoy your time here.

Pudge

9

The added line worked great! I just wonder why it did not need the myflags-entry before, maybe some kernel module was altered with an update and this led to a side-effect ? Anyway, thank you for the precise solution :heart_hands: