Description of problem:
anaconda sets the encryption passphrase by reading what the user typed in, under
X with whatever X keymap is appropriate for the locale.
boot reads the passphrase with whatever keymap the BIOS is using, as we haven't
set any keymaps at that point.
That's going to cause issues somewhere.
Version-Release number of selected component (if applicable):
dlehman had been looking at this... getting the ckbcomp stuff in for console
keymaps so that we can better match the X maps would make things a lot easier
Any passphrase with the special Hungarian Letters fails..... as above expected
Most of Hungarian keys will make an * when entering the passphrase.
However, none of the top row keys that use the <Alt GR> key function.
No *, just a beep.
Very odd as the top row keys normaly work with X just fine.
Now that a default install for F9-Alpha uses encryption this issue with keymap
should (I feel) be raised to a higher priority (which I've done, let me know if
If we don't solve this, or at least tell users only to use ordinary numbers and
letters, we're going to have a lot of boxes that people install only to be be
told they have the wrong passphrase.
I know, I've just hit it twice :o) Then found this bug.
*** Bug 432398 has been marked as a duplicate of this bug. ***
Per the bug that I just dup'ed to this, this is also a problem if the user
wishes to use a Dvorak keyboard.
Problem (obviously) also exists with Finnish/Swedish keyboard
dlehman committed something to support keymaps in the initrd and I'll be
rebuilding mkinitrd hopefully in the next hour or two
Does this still happen? Jeremy did a mkinitrd build a while ago, just need to
verify that it's fixed.
I've noticed that there is a message that the keymap is loaded now. Since I
don't have any keyboard other than US English, I can't test that it actually
loads some other keymap if configured to do so.
This is fixed on my F9/rawhide box now--it successfully loads the dvorak
keymap and lets me type in my passphrase in the layout I used to do the
Closing based on comment #10.
*** Bug 443061 has been marked as a duplicate of this bug. ***