Date: Tue, 27 Jan 2004 08:16:59 +0100 (CET)
Message-Id: <200401270716.i0R7Gxw21819@d1o408.telia.com>
From: "Voluspa" <lista3@comhem.se>
Reply-To: "Voluspa" <lista3@comhem.se>
To: linux-kernel@vger.kernel.org
Subject: Re: atkbd.c: Unknown key released
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1467
Lines: 40

On 2004-01-27 it was written:

> > 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.

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.

Mvh
Mats Johannesson


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