[kbd] Broken bkeymap

[kbd] Broken bkeymap

[Thorben]

Hi list,

I'm new to the topic of keymaps and everything around it so I hope to
find some help.

For my Gentoo I'm building my own initramfs, but last week I came across
a strange problem: Entering my passphrase for LUKS was not possible. The
layout was broken.
Eventually I found out that the file generated for loadkmap did changed
but I don't know why. The difference can be seen in this screenshot
(just a URL as I don't want to generate huge traffic by attaching the
file):
https://chaos.social/system/media_attachments/files/104/723/346/690/219/791/original/a5fea93d1f356d8d.png

The first thing I noticed is that the number of null bytes changed from
1 to 3 (from 2 bytes to 4 bytes in total).

Can someone help me to understand why it did changed and why my
initramfs (loadkmap via busybox) is unable to process the new file? Are
both versions even valid?

Thanks
Thorben

Re: [kbd] Broken bkeymap

[Alexey Gladkov]

On Sun, Aug 23, 2020 at 09:26:14AM +0200, Thorben wrote:
> Hi list,
> 
> I'm new to the topic of keymaps and everything around it so I hope to
> find some help.
> 
> For my Gentoo I'm building my own initramfs, but last week I came across
> a strange problem: Entering my passphrase for LUKS was not possible. The
> layout was broken.
> Eventually I found out that the file generated for loadkmap did changed
> but I don't know why. The difference can be seen in this screenshot
> (just a URL as I don't want to generate huge traffic by attaching the
> file):
> https://chaos.social/system/media_attachments/files/104/723/346/690/219/791/original/a5fea93d1f356d8d.png
> 
> The first thing I noticed is that the number of null bytes changed from
> 1 to 3 (from 2 bytes to 4 bytes in total).
> 
> Can someone help me to understand why it did changed and why my
> initramfs (loadkmap via busybox) is unable to process the new file? Are
> both versions even valid?

What architecture was the initramfs image created on?
What architecture was the initramfs used on?
What are the busybox and kbd versions?

-- 
Rgrds, legion

Re: [kbd] Broken bkeymap

[Thorben Went]

On 8/29/20 12:40 PM, Alexey Gladkov wrote:
> 
> What architecture was the initramfs image created on?
> What architecture was the initramfs used on?
> What are the busybox and kbd versions?

Hey Alexey,

thanks for replying.

Everything was build on and for x84_64.

I've seen this problem after upgrading from kbd 2.0.4 to 2.2.0.
The busybox version on my system is 1.31.1

For testing I downgraded to 2.0.4 and it seems that this kbd version
creates the 2-byte version which my initramfs can read.

Here a screenshot of bkeymaps generated in both kbd versions.
https://trash.libcrypt.so/kbd204_vs_kbd220.png

Thanks
Thorben

Re: [kbd] Broken bkeymap

[Thorben]

On 8/31/20 8:39 PM, Thorben Went wrote:
> I've seen this problem after upgrading from kbd 2.0.4 to 2.2.0.

Hey again,

I've pinned down the commit between those two versions and found out
that since commit a3751c107088884126a4838af32f3a5859c76b33 loadkeys
generates the file my initramfs has problems with.

Thanks
Thorben

Re: [kbd] Broken bkeymap

[Thorben]

On 8/31/20 10:04 PM, Thorben wrote:
> I've pinned down the commit between those two versions and found out
> that since commit a3751c107088884126a4838af32f3a5859c76b33 loadkeys
> generates the file my initramfs has problems with.

Sorry for the spam. I've found out that there was a problem with the
commit mentioned above which got already fixed in 2.2.90/2.3.0 with
commit c994c7763b390d28ac92223eaa6176a136ad7b58.

As Gentoos latest stable version of kbd is 2.2.0 I've created a ticket
in Gentoos Bugtracker to bump the version. For me this issue is now solved.

Thanks and sorry again for this many mails coming from me,
Thorben