You are not logged in.

#1 2022-10-30 13:12:55

rebeltg
Member
Registered: 2022-10-29
Posts: 3

Keyboard failure at LUKS prompt on cold boot

I have an Acer spin SP314 laptop setup with an encrypted root. The keyboard does not work at the LUKS prompt from a cold boot (system was cleanly shut down and left for more than a few seconds). The keyboard works in GRUB, EFI shell, UFEI settings, and after using an external keyboard (which only works sometimes). However, if the system is rebooted or hibernated, the keyboard works just fine. It also works if I boot from the Arch install media and then reboot. I've tried various hook orders, modules, and command line switches suggested in threads where the keyboard doesn't work at all. It does not work from the fallback image. I have even tried switching between GRUB and EFISTUB for boot. I have what I think are the relevant config files below. Has anyone seen this before? Am I missing something in troubleshooting this?

mkinitcpio.info

MODULES=(ext4 hid hid_generic i2c_hid i2c_i801 atkbd xhci_pci i8042 i915 serio serio_raw acer_wmi)
BINARIES=()
FILES=()
HOOKS=(base udev keyboard keymap autodetect modconf block encrypt lvm2 resume filesystems keymap fsck)

/etc/kernel/cmdline

loglevel=3 cryptdevice=/dev/nvme0n1p2:luks:allow-discards resume=/dev/mapper/ArchGroup-swap root=/dev/mapper/ArchGroup-ArchRoot i8042.nopnp i8042.reset rw 

/etc/mkinitcpio.d/linux.preset

ALL_config="/etc/mkinitcpio.conf"
ALL_kver="/boot/vmlinuz-linux"
ALL_microcode="/boot/*-ucode.img"
PRESETS=('default' 'fallback')
#default_config="/etc/mkinitcpio.conf"
default_image="/boot/initramfs-linux.img"
default_efi_image="/boot/EFI/Linux/archlinux-linux.efi"
#default_options=""
#fallback_config="/etc/mkinitcpio.conf"
fallback_image="/boot/initramfs-linux-fallback.img"
fallback_efi_image="/boot/EFI/Linux/archlinux-linux-fallback.efi"
fallback_options="-S autodetect"

edit: added formatting

Last edited by rebeltg (2022-11-01 21:16:33)

Offline

#2 2022-10-30 20:55:34

xerxes_
Member
Registered: 2018-04-29
Posts: 1,063

Re: Keyboard failure at LUKS prompt on cold boot

If I were you I would change order of hooks into something like this (and you have two times keymap! Why?):

HOOKS=(base udev autodetect modconf block encrypt lvm2 resume filesystems keyboard keymap fsck)

Command 'mkinitcpio -H keyboard' says:
==> Help for hook 'keyboard':
This hook loads the necessary modules for keyboard devices. As a side-effect
modules for some non-keyboard input devices might also be added, but this should
not be relied on. Detection will take place at runtime. To minimize the modules
in the image, add the autodetect hook prior to this hook.

When you change /etc/mkinitcpio.conf file don't forget to run mkinitcpio.

Last edited by xerxes_ (2022-10-30 21:06:59)

Offline

#3 2022-10-30 23:59:42

cfr
Member
From: Cymru
Registered: 2011-11-27
Posts: 7,171

Re: Keyboard failure at LUKS prompt on cold boot

xerxes_ wrote:

If I were you I would change order of hooks into something like this (and you have two times keymap! Why?):

HOOKS=(base udev autodetect modconf block encrypt lvm2 resume filesystems keyboard keymap fsck)

Don't do this. See https://wiki.archlinux.org/title/Dm-cry … mkinitcpio. The reason the hook information recommends putting autodetect first is to reduce the size of the initramfs. But, as the link says, doing this can disable keyboards you want to use to decrypt root. This is especially bad advice if somebody is relying on external keyboards to decrypt.

However, having keymap twice is at least unnecessary.


CLI Paste | How To Ask Questions

Arch Linux | x86_64 | GPT | EFI boot | refind | stub loader | systemd | LVM2 on LUKS
Lenovo x270 | Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz | Intel Wireless 8265/8275 | US keyboard w/ Euro | 512G NVMe INTEL SSDPEKKF512G7L

Offline

#4 2022-10-31 01:09:58

rebeltg
Member
Registered: 2022-10-29
Posts: 3

Re: Keyboard failure at LUKS prompt on cold boot

Ah, the fastest way to find a typo is to post on the internet. Thank you both, xerxes_ and cfr for that one. Fixing the extra keymap and trying keyboard both before and after autodetect doesn't resolve the issue on a cold boot, however.

Offline

#5 2022-10-31 04:34:38

cfr
Member
From: Cymru
Registered: 2011-11-27
Posts: 7,171

Re: Keyboard failure at LUKS prompt on cold boot

Are you booting a combined image or a traditional initramfs? Your config looks as if you're making combined images? If so, maybe try using the separate kernel/initramfs approach to rule that out as a source of trouble?

Please edit your posts to use [ code ] tags [ /code ] (without the spaces) as it makes it easier to read.

Last edited by cfr (2022-10-31 04:36:15)


CLI Paste | How To Ask Questions

Arch Linux | x86_64 | GPT | EFI boot | refind | stub loader | systemd | LVM2 on LUKS
Lenovo x270 | Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz | Intel Wireless 8265/8275 | US keyboard w/ Euro | 512G NVMe INTEL SSDPEKKF512G7L

Offline

#6 2022-11-01 11:52:53

rebeltg
Member
Registered: 2022-10-29
Posts: 3

Re: Keyboard failure at LUKS prompt on cold boot

I have been booting a combined image. I generated a separate set again and have the same problems booting from GRUB and using the regular and fallback intramfs images.

Offline

Board footer

Powered by FluxBB