https://bugzilla.suse.com/show_bug.cgi?id=1195508 https://bugzilla.suse.com/show_bug.cgi?id=1195508#c13 Antonio Feijoo <antonio.feijoo@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |antonio.feijoo@suse.com Assignee|dracut-maintainers@suse.de |jeos-internal@suse.de --- Comment #13 from Antonio Feijoo <antonio.feijoo@suse.com> --- (In reply to Franck Bui from comment #12)
I can see 2 issues:
1. /etc/vconsole defines KEYMAP= which was initialized with a filename with extensions (.map.gz). I think that's incorrect and only the mapping name should be used, 'us' in that case.
The reason is that systemd-vconsole-setup calls and passes the value of KEYMAP to loadkeys(1), "us.map.gz" in this case. However loadkeys(1) basically uses the passed value as it was specified to find the mapping table on the disk.
Hence by defining KEYMAP=us.map.gz, it (installer ?) strongly makes assumption on how the mapping file is saved (compressed in this case) on the disk. Which leads to the second issue...
2. for some reasons, the mapping tables were embedded in initrd uncompressed (see comment #8). I don't think that's correct neither and dracut should keep the mapping files as they are saved on the host especially if they were compressed (smaller).
So I think this is a dracut issue, hence can you please take it over Antonio ?
For issue #1, it may deserve a new bug report of its own.
I would say issue #1 is the owner of this bug report: whoever wrote an incorrect value in /etc/vconsole (which I verified to be root cause of the systemd-vconsole-setup failure), made us aware of comment #6 fix and maybe what you noticed as issue #2. So, I'll investigate if issue #2 deserves a separate bug report or if it's done on purpose, and reassign this one to the JeOS team (I'm not sure if they know who writes this wrong configuration value). -- You are receiving this mail because: You are on the CC list for the bug.