View Single Post
Old 12-29-03, 07:25 PM   #3
eswan
Registered User
 
Join Date: Dec 2003
Posts: 23
Default

Just tried with the 32bit Mesa-5.0.1 libs and that works-

# glxinfo32
name of display: :0.0
display: :0 screen: 0
direct rendering: No
server glx vendor string: Brian Paul
server glx version string: 1.4 Mesa 5.0.1
...

# glxgears32
997 frames in 5.0 seconds = 199.400 FPS
1091 frames in 5.0 seconds = 218.200 FPS
1093 frames in 5.0 seconds = 218.600 FPS
...

# glxinfo
glxinfo
name of display: :0.0
display: :0 screen: 0
direct rendering: Yes
server glx vendor string: NVIDIA Corporation
server glx version string: 1.3
...

# glxgears
2578 frames in 5.0 seconds = 515.600 FPS
3835 frames in 5.0 seconds = 767.000 FPS
3937 frames in 5.0 seconds = 787.400 FPS
...
All in the same session. Even tried both at the same time- about 4 fps, but works.
Maybe there's problems using 32bit libs that try to use the 64bit DRI? Would like to hear from Nvidia on this- it'd be interesting to try a matching 64/32 set of libs. I'll have to try mismatched 32bit libs/kernel module on my 32bit system and see if I get the same 'unknown cmd' error.

Nvidia's scores seem low, mesa's seem high. Running at 3200x1200 dual head, 24bpp. glxgears with the nvidia driver seems to 'stall' badly when input focus changes. This is a dual cpu system (tyan K8W), so maybe it's taking a big hit
if the process changes cpus. More tweaking, have to lookup the 'stay on one cpu' magic.
eswan is offline   Reply With Quote