Problem solved! It was indeed a mesa problem, since libgl1-mesa-dri wasn't installed (I did a regular etch installation that I dist-upgraded to sid). Once I installed it, glxinfo reports "direct rendering yes" and glxgears works beautifully giving me around 650 fps. Cpu load is about the same when
On Fri, Jul 28, 2006 at 04:51:25AM -0700, Land Haj wrote:
> When I do 'glxinfo | grep rendering' in sarge and sid, it says direct
> rendering is not enabled.
That's odd, because the X log definately says everything is fine.
> In sid, doing glxgears results in very slowy and choppily turning wheel
On Fri, Jul 28, 2006 at 04:51:25 -0700, Land Haj wrote:
> When I do 'glxinfo | grep rendering' in sarge and sid, it says direct
> rendering is not enabled.
>
> In sid, doing glxgears results in very slowy and choppily turning
> wheels and no fps gets reported. This is not the case with sarge -- I
On Fri, Jul 28, 2006 at 03:44:42AM -0700, Land Haj wrote:
> If one is to believe top's over-all cpu report, sid and sarge are equal
> when I run at 16 bit, but if one is to believe the info on single
> processes, sarge is still very much lower.
It sounds like the process accounting in the new sid
4 matches
Mail list logo