From: Vojtech Pavlik <vojtech@suse.cz>
To: Voluspa <lista3@comhem.se>
Cc: linux-kernel@vger.kernel.org
Subject: Re: atkbd.c: Unknown key released
Date: Tue, 27 Jan 2004 09:33:38 +0100 [thread overview]
Message-ID: <20040127083338.GA490@ucw.cz> (raw)
In-Reply-To: <200401270716.i0R7Gxw21819@d1o408.telia.com>
On Tue, Jan 27, 2004 at 08:16:59AM +0100, Voluspa wrote:
> > > I keep getting the following in my syslog whenever I startx:
>
> In fact, it is preemptively written even _before_ I start X :-)
> I'm using an ancient IBM PS2 swedish keyboard, and this 0x7a crap began
> showing somewhere at 2.6.1 (then without blaming X). Now it is - and the
> blame on X came with 2.6.2-rc2:
>
> Booting:
>
> Jan 26 16:29:10 loke kernel: atkbd.c: Unknown key released (translated
> set 2, code 0x7a on isa0060/serio0).
> Jan 26 16:29:10 loke kernel: atkbd.c: This is an XFree86 bug. It
> shouldn't access hardware directly.
> Jan 26 16:29:11 loke kernel: atkbd.c: Unknown key released (translated
> set 2, code 0x7a on isa0060/serio0).
> Jan 26 16:29:11 loke kernel: atkbd.c: This is an XFree86 bug. It
> shouldn't access hardware directly.
Do you use 'kbdrate' in your bootup scripts? That's another one touching
the keyboard controller directly, when there are ioctls for that.
I guess I should modify to make the message not point not directly to X,
but 'some application'.
> Starting X:
>
> Jan 26 16:33:50 loke kernel: atkbd.c: Unknown key released (translated
> set 2, code 0x7a on isa0060/serio0).
> Jan 26 16:33:50 loke kernel: atkbd.c: This is an XFree86 bug. It
> shouldn't access hardware directly.
> Jan 26 16:33:50 loke kernel: atkbd.c: Unknown key released (translated
> set 2, code 0x7a on isa0060/serio0).
> Jan 26 16:33:50 loke kernel: atkbd.c: This is an XFree86 bug. It
> shouldn't access hardware directly.
--
Vojtech Pavlik
SuSE Labs, SuSE CR
next prev parent reply other threads:[~2004-01-27 8:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-27 7:16 atkbd.c: Unknown key released Voluspa
2004-01-27 8:33 ` Vojtech Pavlik [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-01-27 17:10 Voluspa
2004-01-26 23:37 David Sanders
2004-01-27 5:25 ` Ralf Hildebrandt
2004-01-27 6:09 ` yoann
2004-01-27 7:12 ` 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=20040127083338.GA490@ucw.cz \
--to=vojtech@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=lista3@comhem.se \
/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