Description of problem: I ended up with dvorak as the default console keymap somewhere along the way this rawhide cycle. Not sure which package is responsible for loading the keymap but it's really hard to type a password when you have no visual feedback and no idea where the letters are placed :-) Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
What does your /etc/sysconfig/i18n have? If you do 'mkinitrd -v -f ...', what keymap is it putting in the initrd?
[kmaraas@localhost interfaces]$ cat /etc/sysconfig/keyboard KEYBOARDTYPE="pc" KEYTABLE="no" LAYOUT="no" MODEL="pc105" OPTIONS="" VARIANT="" mkinitrd... resolving for MODULES and that has items of resolving for availmodules and that has items of /etc/sysconfig/keyboard -> /tmp/initrd.VIV5tK/etc/sysconfig/keyboard /bin/loadkeys -> /tmp/initrd.VIV5tK/bin/loadkeys /lib/kbd/keymaps/i386/dvorak/no.map.gz -> /tmp/initrd.VIV5tK/lib/kbd/keymaps/i386/dvorak/no.map.gz /lib/kbd/keymaps/i386/include/linux-with-alt-and-altgr.inc -> /tmp/initrd.VIV5tK/lib/kbd/keymaps/i386/include/linux-with-alt-and-altgr.inc /lib/kbd/keymaps/i386/include/linux-keys-bare.inc -> /tmp/initrd.VIV5tK/lib/kbd/keymaps/i386/include/linux-keys-bare.inc /etc/sysconfig/i18n -> /tmp/initrd.VIV5tK/etc/sysconfig/i18n /bin/setfont -> /tmp/initrd.VIV5tK/bin/setfont /lib/kbd/consolefonts/latarcyrheb-sun16.psfu.gz -> /tmp/initrd.VIV5tK/lib/kbd/consolefonts/latarcyrheb-sun16.psfu.gz
There's two keymaps with the same name. Well, that's not good. Not sure how mkinitrd is supposed to decide which one to use automatically, so pushing to kbd.
Thanks for report. There are few other keymaps with conflicting names, I'll make them unique. I know this problem was discussed on kbd mailing list a time ago and I wonder that it's still not fixed in upstream package.