Ticket #1671 (closed defect: fixed)

Opened 3 years ago

Last modified 3 years ago

Compiling the keymap into the kernel can cause the CTRL key to not work.

Reported by: ken@linuxfromscratch.org Assigned to: lfs-book@linuxfromscratch.org
Priority: lowest Milestone:
Component: Book Version: 6.1
Severity: normal Keywords:
Cc:

Description

The URI also references somebody else who had a similar problem. The common factor seems to be using fr-latin9.

There is a textual comment about Control in the fr-latin9 keymap, but my French

isn't good enough to be sure I'm understanding it correctly. Certainly, all four variants of the french maps assign Control to keys 29 and 97. Perhaps something else in the keytables is influencing this.

More information required, such as which control key, and is only

azerty/fr-latin9 affected ?

Change History

12/14/05 08:00:57 changed by alexander@linuxfromscratch.org

My first version if the 8-bit i18n patch had the option of keymap compilation into the kernel dropped because I never tested this possibility. Then someone re-added this option. This shouldn't have happened.

I.e.: the bug is valid. Preferred solution: don't mention that it is possible to compile the keymap into the kernel.

The UTF-8 book already dropped this option because there is no way to do this procedure with UTF-8 keymaps.

12/14/05 08:55:18 changed by alexander@linuxfromscratch.org

Also, the command in the book,

loadkeys -m /usr/share/kbd/keymaps/i386/qwerty/nl.map.gz > \

drivers/char/defkeymap.c

is suboptimal. The following command will do exactly the same:

loadkeys -m nl >drivers/char/defkeymap.c

The question whether it works is open.

12/14/05 13:01:19 changed by yves@neuf.fr

Comment from Yves who first mentionned this bug : As I am right-handed, I just noticed that it was the left CTRL key that was not working.

12/15/05 08:05:10 changed by matthew@linuxfromscratch.org

I too have had problems before with keymaps. I forget which kernel it was, but one of them caused the '£' (i.e. shift+3) to output '\n' instead of the desired pound sterling symbol. I don't know whether this too would have been "fixed" had I used the bootscript to load the keymap rather than compiling it in the kernel. Maybe we should just drop that command from the book and just support loading keymaps from the bootscript?

01/25/06 14:30:30 changed by matthew@linuxfromscratch.org

  • status changed from new to closed.
  • resolution set to fixed.

This looks like it was fixed with the UTF-8 merge. I certainly can't see a loadkeys command example in the book at the moment. Please reopen if I've missed something!