Using r300g from Mesa 7.7 is like eating a two-year-old undercooked pizza. Bon appetit.
Originally Posted by curaga
I use a 64 bit system exclusively.
Originally Posted by nhaehnle
Wow, I didn't know Counter Strike is working with r300g. Are there any visual errors? If you want some more performance, try the following branch, it's still hot:
Originally Posted by pejakm
I was testing it with a friend yesterday, and HoN was very close to working. The menu was almost-perfect (all in color, etc), we noticed very few visual bugs, but when we tried to start a game, after the loading bar hit 100% the game bailed out.
Originally Posted by Zhick
But still, comparing it with your all-black-with-text-on-it screenshot, it's getting there!
I can get Yo Frankie! working with very minor glitching.
Exciting, I know.
I make it, but it gives
Originally Posted by madman2k
OpenGL vendor string: Advanced Micro Devices, Inc.
OpenGL renderer string: Mesa DRI R600 (RS780 9614) 20090101 TCL DRI2
OpenGL version string: 1.4 (2.0 Mesa 7.8-devel)
at glxinfo. Also says
"direct rendering: No"
with this hack.
you have to remove fglrx (or workaround its libGL)
I don't have fglrx for the months. And removed it already.
And I can verify that my libGL is from mesa trunk.
I run glxinfo utility with strace and see that:
open("/home/compile/svn/gallium/lib64/gallium/r600_dri.so", O_RDONLY) = 4
and doesn't try to open any other r600_dri.so,
So I think radeong_dri.so initiated successfully but gallium doesn't want to run I think.
Not so wierd, I think. Nobody has written a Gallium3D driver for 6xx and up yet. Jerome (aka "glisse") has started work on a 600g driver but AFAIK that's it :
The people talking about running the Gallium3D driver here are on 3xx-5xx hardware.