LUKS unlock uses wrong keyboard layout

[yannl35133]

My disk (except for /boot) is encrypted using LUKS; I use a non-US keyboard layout.
Up until last Friday, I could unlock my disk using my preferred keyboard layout, but today I can’t and the keyboard uses US layout. What happened? From my understanding, this is either from me going from Linux 7.0 to 7.1, or the updates to package base. Also, how can I see what layout my keyboard has when I unlock my disk, the best way I found was to open the GRUB console?

/etc/mkinitcpio.conf:

MODULES=()
BINARIES=()
FILES=()
HOOKS=(base udev autodetect microcode modconf kms keyboard keymap consolefont block plymouth encrypt lvm2 filesystems fsck)

/etc/vconsole.conf:

KEYMAP=fr
FONT=
FONT_MAP=

/proc/cmdline:
BOOT_IMAGE=/vmlinuz-7.1-x86_64 root=/dev/mapper/vglinux-root rw cryptdevice=UUID=<uuid>:luks-<uuid> quiet splash udev.log_priority=3

[pwx]

Have you read this thread yet?

Boot keymap changed to US (?) → password error, following Stable Update 2026-06-26

boot keyboardmapping changed to US (?) → password error on boot I get a password error when decrypting my luks encrypted partition. I have a german keyboard. I can only start when I type in the ‘&’ from the US keyboard position. My keyboard configuration is localectl System Locale: LANG=de_DE.UTF-8 VC Keymap: de X11 Layout: de X11 Model: pc105 X11 Options: terminate:ctrl_alt_bksp What changed with the update is /etc/mkinitcpio.conf # before update - now locks the system, chroo…

[linux-aarhus]

The grub efi stub located in /EFI/boot/bootx64.efi and /EFI/Manjaro/grubx64.efi uses US keymap and has always done so.

It is possible to change keymap - but it is a manual process - and it may create other issues ad-hoc - e.g. the customised image get’s overwritten by an update process.

Manual configuration of core image for early boot - GRUB/Tips and tricks -...

when using full disk encryption

There is various other (better) options to have the same keymap in init as is configured in /etc/vconsole.

HOOKS=(base udev autodetect microcode modconf kms keyboard keymap consolefont block plymouth encrypt lvm2 filesystems fsck)

Change to

HOOKS=(base systemd autodetect microcode modconf kms keyboard block plymouth sd-vconsole sd-encrypt lvm2 filesystems fsck)

Then run mkinitcpio -P

It that doesn’t do it - you can use unified kernel image (UKI) instead - keeping the changes to mkinitcpio.conf and configure UKI in /etc/mkinitcpio.d/<kernel>.preset file.

My personal setup is using a kernel EFI loader and either refind or loading directly from efi firmware (efibootmgr)

[yannl35133]

Solution to the issue linked by @pwx (thank you)

https://forum.manjaro.org/t/boot-keymap-changed-to-us-password-error-following-stable-update-2026-06-26/188603/6