On Die, 2003-01-14 at 01:59, Ronald Hummelink wrote: > On Tue, 2003-01-14 at 01:24, Michel D�nzer wrote: > > > > Does Option "XaaNoScanlineCPUToScreenColorExpandFill" fix it? > > > > > > It "fixes" it yes, but older releases from 4.0.2 and newer on didn't > > > need to disable this acceleration routine. > > > > Until recently, the radeon driver didn't accelerate this with DRI > > enabled in the first place. Does it also happen with DRI disabled? > > That explains ;) > > Commented load "DRI" > still need the Option "Xaa... to avoid the corruption
Then I have no idea what the problem is unfortunately, haven't seen this before. > Don't think dri was enabled in the first place, getting some LibGL > error: InitDriver Failed running glxinfo and glxgears and the framerates > sure seem like its software. That's client side, what matters for the X server is whether the log says (II) RADEON(0): Direct rendering enabled or disabled. > (possible the too old kernel module that comes with 2.4.20 (compiled in) > that is complained about in my log? I originally thought of this possibility, but the DRM doesn't matter with DRI disabled. -- Earthling Michel D�nzer (MrCooper)/ Debian GNU/Linux (powerpc) developer XFree86 and DRI project member / CS student, Free Software enthusiast _______________________________________________ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
