From: Roland S. <rsc...@hi...> - 2005-02-02 19:56:51
|
Thorsten wrote: > On Wednesday 02 February 2005 20:18, Alex Deucher wrote: > >>On Wed, 2 Feb 2005 19:00:47 +0100, Thorsten <kne...@gm...> wrote: >> >>>Ok, >>>I tried it once again, but witch no success. >>>I used the cvs dri-drivers of Mesa and drm. >> >>make sure glxgears is using the same libGL as glxinfo. You might also >>want to try setting your agpmode to 4x. >> >>Alex >> > > they both use the same libGl. > > and > > agpgart: Found an AGP 3.5 compliant device at 0000:00:00.0. > agpgart: Putting AGP V3 device at 0000:00:00.0 into 4x mode > agpgart: Putting AGP V3 device at 0000:01:00.0 into 4x mode > [drm] Loading R200 Microcode > > > It runs in 4x, > > The last time I got it running, glxgears gives me 1200fps! > > any suggestions? Is this actually really a problem? glxgears scores can be flaky. For instance, if I run some computing app in the background (even at the lowest priority), glxgears score easily drops by a factor of 20. I think that's due to the frame throttling code which will thus preempt glxgears. "Slower" apps (quake3 for example) do not suffer from that however. Also, if irq's are not available, that could have similar effects afaik. Roland |