Fixing Keyboard Layout Issues in Arch Linux Emergency Mode

To fix keyboard layout issues in Arch Linux emergency mode, manually load the correct keymap using the loadkeys command before attempting to unlock your LUKS container. This bypasses the default US layout often assigned during early boot stages, ensuring special characters like accents or brackets are interpreted correctly by the shell.

Understanding Emergency Mode Keymaps

When an Arch Linux system drops into emergency mode, it typically does so because a critical service failed to start or a filesystem could not be mounted. At this stage, the kernel has loaded basic drivers, but the full userspace environment is minimal. A common pain point for non-US keyboard users is that the console defaults to a generic US English layout. If you are typing a passphrase with characters specific to your language, such as Spanish ñ or ú, the input will be misinterpreted, leading to authentication failures. The underlying mechanism relies on the vconsole configuration. In a normal boot sequence, systemd reads /etc/vconsole.conf to apply the correct keymap. However, in emergency mode, this file might not be parsed correctly if the root filesystem is encrypted and requires manual intervention first. Therefore, you must explicitly tell the kernel console driver which layout to use. The tool responsible for this is loadkeys, which is part of the kbd package and is available in the initial ramdisk (initramfs) environment.

Step-by-Step Fix for Spanish Layouts

Follow these steps to restore proper keyboard functionality in the emergency shell. Ensure you are connected to the network or have access to the local terminal where you can type commands.

1. Identify Your Current State: When you see the prompt asking for the root password or LUKS passphrase, try typing a character that is difficult on a US layout, such as 'ñ'. If it appears as a different symbol, your layout is incorrect.
2. Load the Correct Keymap: Type the following command exactly:

   loadkeys es

   This command loads the Spanish keyboard layout into the virtual console. The abbreviation 'es' refers to the standard ISO layout used in Spain. If you are using a different variant, check the list of available layouts in /usr/share/kbd/keymaps/.
3. Verify the Change: After running the command, test your keyboard again. Type the same difficult character. It should now appear correctly on the screen. You may need to press Enter to refresh the display if the buffer was already queued.
4. Unlock Your System: With the correct layout active, proceed to enter your LUKS passphrase or root password. The characters will now be translated accurately by the cryptsetup utility.

If you are using a laptop with a non-standard layout, such as a Dvorak or Colemak arrangement, replace 'es' with the appropriate code from the keymap directory. For example, loadkeys dvorak-es might be necessary for specific regional variants.

Permanent Configuration Prevention

While loading the keymap manually solves the immediate problem, you should configure your system to apply this setting automatically during boot. This prevents the issue from recurring after updates or reboots. The primary configuration file for virtual console settings in Arch Linux is /etc/vconsole.conf. Edit this file using a text editor available in the initramfs, such as nano or vi, or mount your root filesystem and edit it from within the recovered system. Add or modify the following line:

KEYMAP=es

Ensure that no other conflicting settings override this value. Additionally, verify that the systemd-vconsole-setup.service is enabled. This service is responsible for applying vconsole settings early in the boot process. You can check its status with:

systemctl status systemd-vconsole-setup.service

If the service is masked or disabled, enable it with:

systemctl enable systemd-vconsole-setup.service

After making these changes, regenerate your initramfs to ensure the new keymap is embedded in the early boot environment. Use the mkinitcpio command with your current preset configuration:

sudo mkinitcpio -P

This step is crucial because the emergency mode runs entirely within the initramfs. If the keymap is not present in the initramfs, the system will revert to the default US layout every time it enters emergency mode, regardless of your host system's configuration. For more complex hardware configurations, such as external USB keyboards that do not match the built-in layout, you may need to adjust the HOOKS array in /etc/mkinitcpio.conf to include udev and autodetect properly. This ensures that the correct driver is loaded for your specific keyboard hardware. If you encounter persistent issues with bootloader recognition, consider checking your BIOS settings as outlined in our guide on BIOS won't recognize bootloader: Troubleshooting Guide.

Troubleshooting Common Errors

Sometimes, even after loading the correct keymap, you might experience delayed input or garbled characters. This is often due to the console font or terminal emulator settings rather than the keymap itself. Ensure that your terminal supports UTF-8 encoding. In most cases, simply reloading the keymap resolves the issue. If loadkeys returns an error saying the keymap cannot be found, it means the keymap file is missing from your initramfs. This usually happens if you removed the keymap hook from your mkinitcpio configuration. Re-add it to the HOOKS array and regenerate the image. Another common issue is confusion between the layout for the bootloader (GRUB) and the layout for the OS. As noted in discussions about Keyboard not working in Windows or Fedora 37 but works in Grub, mismatched layouts between GRUB and the Linux kernel can cause frustration. While GRUB handles its own input independently, once you pass control to the Linux kernel, the kernel uses its own vconsole settings. Ensuring consistency between your GRUB config (GRUB_CMDLINE_LINUX) and your Arch vconsole settings helps maintain a smooth experience across all boot stages.

Frequently Asked Questions

Why does my keyboard work in GRUB but not in Arch Linux?

GRUB uses its own internal keyboard driver and configuration, separate from the Linux kernel. If you configured GRUB for a Spanish layout but did not set up /etc/vconsole.conf or the initramfs keymap, the kernel will fall back to the default US layout once it takes over boot control.

Can I use a different Spanish layout variant like "es" vs "es_cat"?

Yes, you can use any valid keymap name. The standard "es" layout is suitable for most users, but if you use a Catalan-specific layout, you should use "es_cat". Check /usr/share/kbd/keymaps/ for the exact filename corresponding to your preferred layout.

What if I forget the root password after fixing the layout?

Fixing the keyboard layout does not affect password storage. If you forget your password, you will need to boot from a live USB or use the Arch Linux installation media to chroot into your system and reset the password using the passwd command.

Does regenerating mkinitcpio take a long time?

The process depends on your system speed and the number of modules included, but it typically takes less than a minute on modern hardware. It is a one-time operation required only when you change hooks or add new keymaps to the initramfs.

Is there a way to test the keymap without rebooting?

Yes, you can use the loadkeys command directly in the terminal while logged in. To revert to the previous layout, you can run loadkeys us to switch back to US English, or specify any other valid keymap name to test different configurations instantly.