On Friday 08 October 2004 05:24, Ric Otte wrote:
I now wonder if I would have listed the agp_via module somehow in
/etc/modules if that would have helped, or if it doesn't work as a
module.
I just posted further up the thread that that is exactly what you have to do.
--
Alan Chandler
[EMAIL
Things are very slow for me under 2.6 kernels. Under 2.4.16 I was able to
play tuxracer just fine, but under 2.6.6 things are so slow that it is
unplayable (a second or so pause between command and action). I ran glxgears
under 2.4.16 and got output like:
2430 frames in 5.0 seconds = 486.000
On Thursday 07 October 2004 07:15, Ric Otte wrote:
Things are very slow for me under 2.6 kernels. Under 2.4.16 I was able
to play tuxracer just fine, but under 2.6.6 things are so slow that it is
unplayable (a second or so pause between command and action). I ran
glxgears under 2.4.16 and
Things are very slow for me under 2.6 kernels. Under 2.4.16 I was
able to
play tuxracer just fine, but under 2.6.6 things are so slow that it is
unplayable (a second or so pause between command and action). I ran glxgears
under 2.4.16 and got output like:
2430 frames in 5.0 seconds =
On Thu, Oct 07, 2004 at 10:19:39AM -0600, Justin Guerin wrote:
Just a guess, but did you reconfigure X to run at a nice value of 0? The
2.4 kernels ran best when X was niced to -10, but with the 2.6 anticipatory
scheduler, it turns out to be a bad thing.
Also, check out your /etc/modules
On Thu, Oct 07, 2004 at 04:34:54PM -0400, Andrew Schulman wrote:
Try the suggested fix at
http://home.comcast.net/~andrex/Debian-nVidia/troubleshooting.html#nodri
(I know you're not using an nVidia card, but the fix described there is
generic).
This was quite interesting, but didn't work.
I recompiled the kernel, compiling in AGP_VIA directly and not as a
module. This then turned on direct rendering when I booted up, and
glxgears is about twice as fast:
glxgears
1900 frames in 5.0 seconds = 380.000 FPS
2266 frames in 5.0 seconds = 453.200 FPS
2267 frames in 5.0
7 matches
Mail list logo
