On Sunday 08 February 2004 08:38 pm, Grendel wrote: > On Sun, 8 Feb 2004, Ernie Schroder wrote: > > Hmmm, I hadn't thought to check the AGP status. I found that > > forcing NvAGP with: > > > > Option "NvAGP" "1" > > > > results in: > > > > $ cat /proc/driver/nvidia/agp/status > > Status: Disabled > > Well I did some benchmakrs and found that glxgears is not a good > benchmarking option, it probably doesnt use AGP that much, thats > why you get the same results even when agp is turned off. > > However if you take a game like NeverWiner nights which uses a lot > of textures, then on my amd 3000xp ti4200, the opening prelude > gives > > 1. AGP off = ~42 fps > 2. NVIDIA AGP = ~80-85 fps > 3. AGPGART = ~80-85 fps > > glxgears is giving me 3446 fps on all agp settings. > > > Any ideas? > > To try out nvagp you have to start x without the agpgart and the > nvidia_modules loaded, if they are loaded then the nvidia driver > cant use NVAGP. Thats why it was failed to use NVAGP when you > specified it in XF86 file, the agpgart was already loaded. > > > Bye, > Grendel
Checking things out, I find that agpgart and nvidia-agp (both built as modules) are loaded at boot and trying to rmmod them fails saying they are in use. Does this happen due to frame buffer? CONFIG_FB_VESA=y Soooo, I renamed agpgart and played around a bit. With my current config, (1600x1200 16 bit color) I'm seeing 5200 f/sec with no AGP, 5550 with agpgart and 5600 f/sec using nvidia-agp. The older drivers on 2.4.20 ran about the same with agpgart and no AGP but they gave me just under 6000 f/sec with nvidia-agp. I should qualify that with the fact that the 6000 f/sec framerate was on a Leadtek motherboard (also nforce2 chipset) and an XP2100 processor (now running XP2400) 24 bit color takes the 5600 f/sec number down to 3670 f/sec. I don't do games here but I need the graphics for Pro/E Wildfire. (anybody got a Quadro4 card for sale cheap?) -- Regards, Ernie 100% Microsoft and Intel free -- [EMAIL PROTECTED] mailing list
