glxgears nonsense on F11

Dave Stevens geek at uniserve.com
Thu Jun 18 00:30:43 UTC 2009


I have used glxgears for several years, most recently on F7. I've just  
moved to F11 x86_64 on a new hard drive and the system is now up to  
date. When I run glxgears I get the gear display in the yop left  
corner, just as I expect but instead of getting the frame rate display  
in the terminal window I get endless ream of this:

CS section size missmatch start at (r300_cmdbuf.c,emit_cb_offset,254) 16 vs 7
CS section end at (r300_cmdbuf.c,emit_cb_offset,264)
CS section size missmatch start at (r300_cmdbuf.c,emit_cb_offset,254) 16 vs 7
CS section end at (r300_cmdbuf.c,emit_cb_offset,264)
CS section size missmatch start at (r300_cmdbuf.c,emit_cb_offset,254) 16 vs 7
CS section end at (r300_cmdbuf.c,emit_cb_offset,264)
CS section size missmatch start at (r300_cmdbuf.c,emit_cb_offset,254) 16 vs 7
CS section end at (r300_cmdbuf.c,emit_cb_offset,264)
CS section size missmatch start at (r300_cmdbuf.c,emit_cb_offset,254) 16 vs 7
CS section end at (r300_cmdbuf.c,emit_cb_offset,264)
CS section size missmatch start at (r300_cmdbuf.c,emit_cb_offset,254) 16 vs 7
CS section end at (r300_cmdbuf.c,emit_cb_offset,264)
CS section size missmatch start at (r300_cmdbuf.c,emit_cb_offset,254) 16 vs 7
CS section end at (r300_cmdbuf.c,emit_cb_offset,264)
CS section size missmatch start at (r300_cmdbuf.c,emit_cb_offset,254) 16 vs 7
CS section end at (r300_cmdbuf.c,emit_cb_offset,264)

and no frame rate display. Does anyone know what this is or what to do?

Dave


-- 
In the world?s anti-Bush zones it is fashionable to regard him as an  
imperialist
redneck of limited intellectual capacities. -- George Ross in Le Monde  
Diplomatique




More information about the fedora-list mailing list