[no subject]

[Andries . Brouwer]

: with 2.6.x:
: Loading /etc/console/boottime.kmap.gz
: KDSKBENT: Invalid argument
: failed to bind key 265 to value 638

You must be using a non-standard loadkeys, or an old loadkeys
compiled against new kernel headers.

The 2.6 situation is broken in several respects and one of
the bugs is a NR_KEYS that is 512, which the keys involved
are unsigned characters and cannot be larger than 255.

My opinion is that NR_KEYS must be decreased to 256, and maybe
I have seen patches by Vojtech somewhere that already did this,
but looking at current bk source it seems that they have not been
applied yet.

Anyway, I released kbd-1.10 last week or so, and it ignores the
kernel NR_KEYS but tries to adapt dynamically to the kernel.
It would not come with this error message, I suppose.

: with 2.4.20 & 2.4.22-ck2 the value is increasing from 128 to 511

: failed to bind key 128 to value 512

2.4 has NR_KEYS equal to 128, so key 128 and higher do not exist.

So, so far all is well understood.

: atkbd.c: Unknown key pressed (translated set 2, code 0x91 on isa0060/serio0)
: atkbd.c: Unknown key released (translated set 2, code 0x91 on isa0060/serio0)
: atkbd.c: Unknown key pressed (translated set 2, code 0x92 on isa0060/serio0)
: atkbd.c: Unknown key released (translated set 2, code 0x92 on isa0060/serio0)

This is something different, a key without associated keycode.
That is normal. If it really has high bit set it is a bit unusual.
(What does showkey -s show?)

Maybe you can make this addressable using setkeycodes.

Andries
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/