According to https://github.com/legionus/kbd/commit/c994c7763b390d28ac92223eaa6176a136ad7b58 there seems to have been a change in the binary format expected by recent (sorry I cannot provide an exact version.. I *think* it is this current 1.31.1 and 1.30.1 still worked) busybox. I am using mkinitramfs-ll, which uses sys-apps/kbd's "loadkeys -b" option to generate a binary keymap which in turn gets loaded by busybox's "loadkmap" applet when booting. The resulting keyboard map is completely broken/rearranged with missing keys. Reproducible: Always Steps to Reproduce: On a tty, do the following (warning, have a backup SSH session and a working busybox/kbd combination handy or you'll not be able to use the tty or even switch away from it!) 1. Using the mentioned versions above, loadkeys -b /usr/share/keymaps/i386/qwertz/de-latin1-nodeadkeys.map.gz >de-latin1-nodeadkeys.bin 2. busybox loadkmap < de-latin1-nodeadkeys.bin Actual Results: Type and see ;-) Every other key is a ?, keys are completely mixed up. Expected Results: The keymap should be correctly loaded. Fix: Emerge ~sys-apps/kbd-2.3.0-r1. Either busybox 1.31.x has to be marked unstable for the time being or kbd has to be bumped to >= 2.3.0 or >=2.2.90 (at least those are the tags in the linked commit)
Earliest sys-apps/kbd in tree is currently 2.4.0, so this bug is obsolete.
