| Summary: | dracut does not set default keymap | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Nicolas Vigier <boklm> |
| Component: | RPM Packages | Assignee: | Colin Guthrie <mageia> |
| Status: | RESOLVED DUPLICATE | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | ||
| Version: | Cauldron | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | dracut | CVE: | |
| Status comment: | |||
|
Description
Nicolas Vigier
2012-04-07 12:55:18 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? 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. Hmm, I don't have a vconsole.conf on my system... /me wonders where it is generated... (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. 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 |