From: Bernardo Innocenti <bernie@develer.com>
To: Fredrik Olausson <fredrik@olaussons.net>
Cc: lkml <linux-kernel@vger.kernel.org>, vojtech@suse.cz
Subject: Re: bad scancode for USB keyboard
Date: Wed, 07 Jan 2004 03:27:42 +0100 [thread overview]
Message-ID: <3FFB6E9E.6040500@develer.com> (raw)
In-Reply-To: <3FFB6A5D.9030606@olaussons.net>
Fredrik Olausson wrote:
(I've re-posted to lkml in case someone else finds it useful)
> Bernardo Innocenti wrote:
>> I have a USB keyboard (Logitech Internet Navigator).
>> This keyboard has two "backslash + bar" keys, one of which
>> is located next to the RETURN key.
>>
>> The backslash key always worked fine in 2.4.x, but in 2.6.x
>> and 2.6.0, the scancode reported by showkey is "84", which is
>> usually associated with the "Prevconsole" function in most
>> keymaps.
>>
>> Editing the keymap fixes the problem, but of course this must
>> be a bug in the kernel driver. I compared the 2.4.23 version
>> of kbdmap.c with 2.6.0, but didn't find any obvious reason for
>> this difference.
>
> I have the same problem with a Logitech cordless desktop.
> I can easily change the keycode to generate the right characters when in
> console-mode, but XFree gives that key and the Print Screen key the same
> keycode.
> After changing the xmodmap I can get the unmodified character,
> but modifiers doesn't work, it just gives me the same character not
> matter what modifier I use (shift, alt, alt_gr etc.)
I had fixed my console keymap too, but I've not been able to
figure out how to change the X keymap. I've been looking in
the /usr/X11R6/lib/X11/xkb/ directory, but perhaps XKB is not
being used for old-style keyboard mapping?
Could you provide detailed instructions? C coding with missing
backslash and bar keys is quite hard :-)
Of course, I still thing its' a 2.6 kernel bug and it should be
fixed. Vojtech, do you have an idea why it's happening?
--
// Bernardo Innocenti - Develer S.r.l., R&D dept.
\X/ http://www.develer.com/
next prev parent reply other threads:[~2004-01-07 2:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-03 16:37 bad scancode for USB keyboard Bernardo Innocenti
[not found] ` <3FFB6A5D.9030606@olaussons.net>
2004-01-07 2:27 ` Bernardo Innocenti [this message]
2004-01-07 8:51 ` Vojtech Pavlik
2004-01-07 19:35 ` Bernardo Innocenti
2004-01-09 0:31 ` Fredrik Olausson
2004-01-09 1:58 ` Bernardo Innocenti
2004-01-11 16:30 ` Eduard Bloch
2004-01-11 18:44 ` [PATCH] " Vojtech Pavlik
2004-01-14 13:54 ` Olaf Hering
2004-01-14 13:59 ` Vojtech Pavlik
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3FFB6E9E.6040500@develer.com \
--to=bernie@develer.com \
--cc=fredrik@olaussons.net \
--cc=linux-kernel@vger.kernel.org \
--cc=vojtech@suse.cz \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.