I keep getting the following in my syslog whenever I startx:
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.
--
David Sanders
[email protected]
* David Sanders <[email protected]>:
> 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.
--
Ralf Hildebrandt (Im Auftrag des Referat V a) [email protected]
Charite - Universit?tsmedizin Berlin Tel. +49 (0)30-450 570-155
Gemeinsame Einrichtung von FU- und HU-Berlin Fax. +49 (0)30-450 570-916
Referat V a - Kommunikationsnetze - AIM. ralfpostfix
>>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
On Tue, Jan 27, 2004 at 07:09:56AM +0100, yoann wrote:
> >>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)
2.4 just keeps its mouth shut and doesn't complain.
Hopefully someone fixes X.
--
Vojtech Pavlik
SuSE Labs, SuSE CR
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
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
citerar Vojtech Pavlik:
> 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 :-)
[...]
> 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'.
Yes, 'kbdrate' is used here.
Mvh
Mats Johannesson