On Fri, Apr 30, 2004 at 09:30:05AM +0000, slaven peles wrote: > On April 30, 2004 06:00 am, Branden Robinson wrote: > > On Thu, Apr 29, 2004 at 09:14:58AM +0000, slaven peles wrote: > > > Apr 29 08:25:01 ivor kernel: atkbd.c: Unknown key released (translated > > > set 2, code 0x7a on isa0060/serio0). > > > Apr 29 08:25:01 ivor kernel: atkbd.c: This is an XFree86 bug. It > > > shouldn't access hardware directly. > > > Apr 29 08:25:01 ivor kernel: atkbd.c: Unknown key released (translated > > > set 2, code 0x7a on isa0060/serio0). > > > Apr 29 08:25:01 ivor kernel: atkbd.c: This is an XFree86 bug. It > > > shouldn't access hardware directly. Please note that this has absolutely nothing to do with the ATI/Radeon driver or firmware in the kernel. The message you see when you have the ATI/Radeon firmware problem appears in the XFree86 problem, and looks like this: (EE) RADEON(0): RADEONCPGetBuffer: CP GetBuffer -1020 (EE) RADEON(0): GetBuffer timed out, resetting engine... (EE) RADEON(0): RADEONCPGetBuffer: CP reset -1020 (EE) RADEON(0): RADEONCPGetBuffer: CP start -1020 [repeat ad nauseam] Please see <http://bugs.debian.org/246901> for more on this problem. If you're still setting the "This is an XFree86 bug. It shouldn't access hardware directly." bug in 4.3.0.dfsg.1-1, that is an entirely different issue. -- G. Branden Robinson | For every credibility gap, there is Debian GNU/Linux | a gullibility fill. branden@debian.org | -- Richard Clopton http://people.debian.org/~branden/ |
Attachment:
signature.asc
Description: Digital signature