Re: [gentoo-user] xfree fails with kernel 2.6.3-rc2-mm1
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
Re: [gentoo-user] xfree fails with kernel 2.6.3-rc2-mm1
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. Glück Auf Volker -- Conclusions In a straight-up fight, the Empire squashes the Federation like a bug. Even with its numerical advantage removed, the Empire would still squash the Federation like a bug. Accept it. -Michael Wong -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] xfree fails with kernel 2.6.3-rc2-mm1
On Sun, 15 Feb 2004 09:56:44 -0800 (PST) Jakob "Schiøtz" <[EMAIL PROTECTED]> 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. > These messages were added to the later 2.6 releases. The same condition existed silently in earlier releases. The messages are not critical on my system, but apparently some people have non-working keyboards related to this. You need to check your/var/log/XFree86.0.log to see why X will not start. -- Collins Richey - Denver Area gentoo 2004 2.6.3_r2 nptl udev -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] xfree fails with kernel 2.6.3-rc2-mm1
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 am using the nvidia driver (the xfree one does not work with this card), and I have the problem both with version 1.0.4496-r3 and 5336-r1 (both work fine with the vanilla 2.4.23 kernel). I am using the latest xfree (4.3.0-r5). My machine is a Dell Inspiron 5150 laptop with an nVidia gforce graphics adapter. Does anyone know what could be causing this? Thanks for any help! Jakob Did you try reinstalling nvidia? -- Kathy Wills + + Genealogy Web Site: http://www.brannanorwills.com + + + + -- [EMAIL PROTECTED] mailing list
[gentoo-user] xfree fails with kernel 2.6.3-rc2-mm1
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 am using the nvidia driver (the xfree one does not work with this card), and I have the problem both with version 1.0.4496-r3 and 5336-r1 (both work fine with the vanilla 2.4.23 kernel). I am using the latest xfree (4.3.0-r5). My machine is a Dell Inspiron 5150 laptop with an nVidia gforce graphics adapter. Does anyone know what could be causing this? Thanks for any help! Jakob = Jakob Schiotz, CAMP and Dept. of Physics, Tech. Univ. of Denmark, DK-2800 Lyngby, Denmark. This email address is used for newsgroups and mailing lists (spam protection). Official email: my-last-name at fysik dot dtu dot dk When spammed too much, I'll move on to [EMAIL PROTECTED] __ Do you Yahoo!? Yahoo! Finance: Get your refund fast by filing online. http://taxes.yahoo.com/filing.html -- [EMAIL PROTECTED] mailing list
