Arch: How to set keyboard mapping for full disk encryption with dm-crypt and LUKS

0

2

I try to install arch linux with full disk encryption.

After switching to my locale keyboard layout (de-latin1) I entered my password which contains several special characters.

Unfortunatelly after reboot it seems not to use my keyboard layout so LUKS tells me there is "no key available with this passphrase".

I tried to set the options in

/boot/loader/entries/arch.conf

to

options cryptdevice=UUID=********-****:vg0 root=/dev/mapper/vg0-root resume=/dev/mapper/vg0-swap rw intel_pstate=no_hwp lang=de-latin1 locale=de_DE.UTF-8

or

options cryptdevice=UUID=********-****:vg0 root=/dev/mapper/vg0-root resume=/dev/mapper/vg0-swap rw intel_pstate=no_hwp lang=de locale=de_DE.UTF-8

both did not help.

What am I doing wrong?

kitingChris

Posted 2019-03-14T21:13:02.013

Reputation: 101

Answers

0

<UUID> is your partition UUID, not the placeholder.

michael g

Posted 2019-03-14T21:13:02.013

Reputation: 101

Of course... But I did not post it ;-) Perhaps I better use asterix for clarification... – kitingChris – 2019-05-06T19:09:37.333

If I had the UUID wrong arch would not even have been booted. But the error is not "arch not booting" but "arch not using the right keymapping after booting". – kitingChris – 2019-05-06T19:12:55.577

im not saying its the complete answer but it is part of your problem. – michael g – 2019-05-14T15:51:28.590

no it is not. Please re-read my last comments ;-) The Problem is NOT a wrong UUID. If I did that wrong it would not even boot. The Problem is that on booting the wrong keymap was loaded which caused troubles with unlocking the encrypted device. That was the core of my question. – kitingChris – 2019-05-15T06:43:07.203