On Mon, 16 Feb 2004 00:46:07 +0100 "Hemmann, Volker Armin" <[EMAIL PROTECTED]> wrote:
> On Sunday 15 February 2004 18:56, Jakob Schi�tz wrote: > > Hi! > > > > I (finally) decided to try the 2.6 kernels, but I ran into a > > problem. X cannot start, I get the following messages in dmesg, and > > I only see the nVidia spash screen, then it is back in text-mode. > > > > atkbd.c: Unknown key released (translated set 2, code 0x7a on > > isa0060/serio0). > > atkbd.c: This is an XFree86 bug. It shouldn't access hardware > > directly. atkbd.c: Unknown key released (translated set 2, code 0x7a > > on isa0060/serio0). > > atkbd.c: This is an XFree86 bug. It shouldn't access hardware > > directly. > > > > I get this message, if I hit one of my programmable keys and the wrong > layer is active. > This message does not and will not mean any critical error that could > kill X. Have a look into /var/log/XF86.0.log there you'll find your > problem. > Apparently the kernel developers don't agree with you. You can google for their comments. I get these messages every time I start X. Apparently X code is making some sort of (big no no) direct access to the keyboard that should be handled via more standard methods. In some cases this has even led to unusable keyboards. In my case, it's just an annoyance, but who knows where this will lead. I don't know whether or not the kernel developers have communicated this fact to the xfree developers. According to what I read, the kernel used to silently ignore this problem, but they have decided to log the occurrences in the hope that this will be fixed. HTH, -- Collins Richey - Denver area gentoo 2004 2.6.3_r2 nptl udev -- [EMAIL PROTECTED] mailing list
