From: Ciaran McCreesh <ciaranm@gentoo.org>
To: Alwin Meschede <ameschede@gmx.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Numbersign key dysfunctional in 2.6.1-rc
Date: Thu, 8 Jan 2004 17:21:50 +0000 [thread overview]
Message-ID: <20040108172150.418251dd@snowdrop.home> (raw)
In-Reply-To: <3FFD82E2.7090105@gmx.de>
[-- Attachment #1: Type: text/plain, Size: 1197 bytes --]
On Thu, 08 Jan 2004 17:18:42 +0100 Alwin Meschede <ameschede@gmx.de>
wrote:
| until kernel version 2.6.1-rc1, the numbersign/tilde key on my
| Logitech USB keyboard used to generate the scancode 0x2b. Under
| 2.6.1-rc1 and newer versions, it generates 0x54, which I suppose to
| collide with SysRQ or something like that (I found some information
| indicating this in
| http://www.ussg.iu.edu/hypermail/linux/kernel/0003.2/0721.html ). As
| result, the numbersign key causes things like switching from one
| console to another instead of printing a numbersign...
My Microsoft Natural (USB, GB layout) keyboard is similarly broken. The
onboard keyboard (IBM ThinkPad T30, GB layout) is quite happy with #~,
but with the USB keyboard I get no output.
xev tells me:
KeyPress event, serial 23, synthetic NO, window 0x1a00001,
root 0x48, subw 0x0, time 67813064, (211,112), root:(460,399),
state 0x0, keycode 111 (keysym 0xff61, Print), same_screen YES,
XLookupString gives 0 bytes:
XmbLookupString gives 0 bytes:
XFilterEvent returns: False
Everything works as expected with 2.6.0.
--
Ciaran McCreesh
Mail: ciaranm at gentoo.org
Web: http://dev.gentoo.org/~ciaranm
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2004-01-08 17:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-08 16:18 Numbersign key dysfunctional in 2.6.1-rc Alwin Meschede
2004-01-08 17:21 ` Ciaran McCreesh [this message]
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=20040108172150.418251dd@snowdrop.home \
--to=ciaranm@gentoo.org \
--cc=ameschede@gmx.de \
--cc=linux-kernel@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).