F35 rawhide installation of Fedora, setting the KEYTABLE= on the kernel command line fails

[stan]

I use a custom keytable uneaf.  I put it in
/usr/lib/kbd/keymaps/xkb/uneaf.map.gz/. I can then load it using
loadkeys uneaf
But when I ask the kernel to load it via a setting of 
KEYTABLE=uneaf on the kernel command line, so it comes up by default, it
does not work. Has this changed in some way from earlier versions of
Fedora where this did work?

[Adam Williamson]

On Mon, 2021-06-28 at 10:48 -0700, stan via test wrote:
> I use a custom keytable uneaf.  I put it in
> /usr/lib/kbd/keymaps/xkb/uneaf.map.gz/. I can then load it using
> loadkeys uneaf
> But when I ask the kernel to load it via a setting of 
> KEYTABLE=uneaf on the kernel command line, so it comes up by default, it
> does not work. Has this changed in some way from earlier versions of
> Fedora where this did work?

I'd never actually heard of this before. Googling it seems to be a
pretty old thing, it's plausible that whatever was handling it just
decided to deprecate it, I'm not sure.

`man dracut.cmdline` notes it as deprecated and replaced by
`vconsole.keymap`, so you could try using that instead.

You can also set it permanently in /etc/vconsole.conf; there's a
"KEYMAP" line there. After changing it there you would also need to
regenerate the initramfs with `dracut -f` in order for the same layout
to be used in the initramfs phase of boot (e.g. when entering
passphrase to decrypt the system partition, if encrypted).

[stan]

On Mon, 28 Jun 2021 11:56:22 -0700
Adam Williamson  wrote:
> You can also set it permanently in /etc/vconsole.conf; there's a
> "KEYMAP" line there. After changing it there you would also need to
> regenerate the initramfs with `dracut -f` in order for the same layout
> to be used in the initramfs phase of boot (e.g. when entering
> passphrase to decrypt the system partition, if encrypted).

Thanks for your answer. I was just posting a message to say that I had
done exactly this, and the keymap setting was working, when I read your
message.  I did both, changed the setting /etc/vconsole.conf and
recreating the initramfs custom for my system.  It seems I can remove
KEYTABLE from the kernel options line, as it is doing nothing except
being ignored.

[stan]

On Mon, 28 Jun 2021 20:10:25 -0700
stan via test  wrote:
> recreating the initramfs custom for my system.  It seems I can remove
> KEYTABLE from the kernel options line, as it is doing nothing except
> being ignored.

I booted and edited the kernel command line to remove KEYTABLE=uneaf,
and everything still worked.  So, confirmed that this is a meaningless
setting.