Bug 5266 - dracut does not set default keymap
Summary: dracut does not set default keymap
Status: RESOLVED DUPLICATE of bug 5192
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Colin Guthrie
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-04-07 12:55 CEST by Nicolas Vigier
Modified: 2012-04-27 01:48 CEST (History)
0 users

See Also:
Source RPM: dracut
CVE:
Status comment:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Nicolas Vigier 2012-04-07 12:55:18 CEST 
I am using an encrypted rootfs, and my keyboard is configured in dvorak. In Mageia 1 the password to mount the root fs was asked during boot, and I could type it in dvorak. In Mageia 2 with initrd generated by dracut, the password is still asked, but I need to type it in qwerty.

I don't know how it can be done, but I think dracut should set the default keymap in the initrd. In Mageia 1 with mkinitrd it seems it was done by including the file /etc/sysconfig/keyboard in the initrd. In dracut initrd, after looking at file lib/dracut/hooks/cmdline/20parse-i18n.sh it seems to be possible to set the keymap with kernel argument KEYMAP, vconsole.keymap or KEYTABLE. So if it's not possible to set default keymap in dracut, it can be set with kernel parameter in the bootloader when the kernel is installed.
Comment 1 Colin Guthrie 2012-04-07 13:09:02 CEST 
As I don't fully understand all the keymapping stuff, can you take a look in here:

/usr/lib/dracut/modules.d/10i18n/module-setup.sh


This is the file that decides what to install in your initrd. It doesn't look in sysconfig but perhaps we can migrate sysconfig file to something else, or patch the above to look in our current location?
Comment 2 Nicolas Vigier 2012-04-08 12:38:27 CEST 
After looking at /usr/lib/dracut/modules.d/10i18n/module-setup.sh it seems it creates /etc/vconsole.conf in the initrd. And after updating the kernel, the file /etc/vconsole.conf was correctly created in the new initrd. But this file was not created in the previous initrd generated while updating from Mageia 1 to Mageia 2, so it looks like a problem that only happens while updating from Mageia 1 to Mageia 2.
Comment 3 Colin Guthrie 2012-04-08 13:00:21 CEST 
Hmm, I don't have a vconsole.conf on my system... 

/me wonders where it is generated...
Comment 4 Nicolas Vigier 2012-04-09 19:58:25 CEST 
(In reply to comment #3)
> Hmm, I don't have a vconsole.conf on my system... 

Yes, me neither, it is only inside the initrd, and is generated by /usr/lib/dracut/modules.d/10i18n/module-setup.sh.
Comment 5 Colin Guthrie 2012-04-27 01:48:39 CEST 
There is another bug about this. Having done test installs, I cannot reproduce. If you can provide more info, please reopen the other bug.

*** This bug has been marked as a duplicate of bug 5192 ***

Status: NEW => RESOLVED
Resolution: (none) => DUPLICATE
Note You need to log in before you can comment on or make changes to this bug.