I have new Dell Inspiron 8600. I am using gentoo-dev-sources-2.6.8-r7. I get very poor performance when using any GL. When I run glxgears I get 690 FPS on an average. I am attaching my xorg.conf. I havent couldnt get 1.5336 build to work at all, Xorg wouldnt start. Any help on this is appreciated. Reproducible: Always Steps to Reproduce: 1. 2. 3.
Created attachment 41439 [details] xorg.conf that I am using Attaching my xorg.conf for the bug
First can you attach your configs as plain/text for future reference. Im not exactly sure what to say here in regards to the bug, like a Go6650 is not exactly a powerful card... 690fps is probably accuratish.... What sort of GL issues are you experiencing? Try adding the following to /etc/modules.d/nvidia options nvidia NVreg_EnableAGPSBA=1 NVreg_EnableAGPFW=1
I enabled both SBA and FastWrite by uncommenting the options line for nvidia in /etc/modules.d/nvidia. No improvement in performance. If I run any GL application say the screensaver I use GLMatrix and turn on the framerate option, I get something like 4-5 frames a second on an average. This card gives a framerate of around 35-40 on an average in windows. I am not able to understand why I get low performance in linux.
I did more hacking around, when I use color depth as 16 I get good GL performance but when I use 24bit Color depth then the GL performance is really bad. Not sure why this is happening.
Does your card actually say it supports 24bit colour modes?
The card does support 24bit Color depth. I upgraded to the new drivers 1.0.6229 the glxgear performance has improved but the GL performance is still the same.
Of course in depth 24 mode compared to 16 the card is much slower, it has to do much more work, the performance of 690fps is ok for that card, so I do not see any bug or error here.
If the speed changes over colour depth changes then there is little we can do but wait for the drivers to be updated...
Is this fixed in any of the newer versions of the drivers?
Re-assigning to -drivers.
I am sorry I dont have the hardware any more to test it anymore.
Alrighty Anyone else who comes across this issue should feel free to re-open this bug.