http://bugzilla.suse.com/show_bug.cgi?id=1123525
http://bugzilla.suse.com/show_bug.cgi?id=1123525#c21
Thomas Blume
# rpm -qf /usr/share/kbd/keymaps/xkb/us.map.gz kbd-2.0.4-lp150.6.2.armv7hl # lsinitrd | grep '\.map' -rw-r--r-- 1 root root 249 May 8 2018 usr/share/kbd/keymaps/legacy/i386/include/euro1.map -rw-r--r-- 1 root root 2004 May 8 2018 usr/share/kbd/keymaps/legacy/i386/qwerty/us.map -rw-r--r-- 1 root root 121059 May 8 2018 usr/share/kbd/keymaps/xkb/us.map # more /etc/vconsole.conf KEYMAP=us.map.gz rpi2150hon:~ #
Please remove the .gz suffix from the keymap name, otherwise systemd-vconsole-setup will fail:
When I change the above to KEYMAP=us.map I get an error message: jan 15 11:05:22 rpi2150hon systemd-vconsole-setup[160]: /usr/bin/loadkeys failed with error code 1. jan 15 11:05:22 rpi2150hon systemd-vconsole-setup[160]: cannot open file us.map.gz jan 15 11:05:22 rpi2150hon systemd[1]: systemd-vconsole-setup.service: Main process exited, code=exited, status=1/FAILURE jan 15 11:05:22 rpi2150hon systemd[1]: Failed to start Setup Virtual Console. jan 15 11:05:22 rpi2150hon systemd[1]: systemd-vconsole-setup.service: Unit entered failed state.
So KEYMAP=us.map.gz seems OK.
Hm, that is pretty strange. The lsinitrd above shows that there is no file us.map.gz in the initrd. When I set: KEYMAP=us.map.gz on my testmachine. I get in the debug logs: --> Feb 05 09:32:33 linux-s9lv systemd-vconsole-setup[130]: cannot open file us.map.gz [...] Feb 05 09:32:33 linux-s9lv systemd-vconsole-setup[130]: Executing "/usr/bin/loadkeys -q -C /dev/tty1 -u us.map.gz"... [...] Feb 05 09:32:33 linux-s9lv systemd-vconsole-setup[130]: /usr/bin/loadkeys failed with error code 1. --< So in my tests, the keymap setup in the initrd fails, when using the .gz suffix. Could you please set: KEYMAP=us.map in /etc/vconsole.conf then run: mkinitrd and reboot with the boot option "quiet" removed and the boot option "debug" set? Afterwards, please attach the output of: journalctl -axb | grep systemd-vconsole-setup -- You are receiving this mail because: You are on the CC list for the bug.