From: yoann <informatique-nospam@mistur.org>
To: linux-kernel@vger.kernel.org
Subject: Re: atkbd.c: Unknown key released
Date: Tue, 27 Jan 2004 07:09:56 +0100 [thread overview]
Message-ID: <bv4vbb$ru3$1@sea.gmane.org> (raw)
In-Reply-To: <20040127052507.GF18411@charite.de>
>>I keep getting the following in my syslog whenever I startx:
>
> Which hardware?
>
>>Jan 26 13:43:56 debian kernel: atkbd.c: Unknown key released (translated set 2, code 0x7a on isa0060/serio0).
>>Jan 26 13:43:56 debian kernel: atkbd.c: This is an XFree86 bug. It shouldn't access hardware directly.
>>Jan 26 13:43:57 debian kernel: atkbd.c: Unknown key released (translated set 2, code 0x7a on isa0060/serio0).
>>Jan 26 13:43:57 debian kernel: atkbd.c: This is an XFree86 bug. It shouldn't access hardware directly.
>>
>>I don't get the error with the 2.4.24 kernel.
>
> Same here.
same here with a 2.6.2-rc1-mm2
Xfree86 Version: 4.2.1-15 (debian sid)
Yoann
next prev parent reply other threads:[~2004-01-27 6:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-26 23:37 atkbd.c: Unknown key released David Sanders
2004-01-27 5:25 ` Ralf Hildebrandt
2004-01-27 6:09 ` yoann [this message]
2004-01-27 7:12 ` Vojtech Pavlik
-- strict thread matches above, loose matches on Subject: below --
2004-01-27 7:16 Voluspa
2004-01-27 8:33 ` Vojtech Pavlik
2004-01-27 17:10 Voluspa
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='bv4vbb$ru3$1@sea.gmane.org' \
--to=informatique-nospam@mistur.org \
--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