I tried to get a screenshot of it but it wouldn't work with FGLRX loaded, there were rainbows and static everywhere like being on acid or something,
Originally Posted by mirv
and the framerate was like half of what the open source radeon driver gives me.
Nvidia's blob manages to run GNOME Shell, what the hell is wrong with AMD? Could they lift a finger to fix their mess? Please? If you want some fun with KDE, force the OpenGL 2 backend in KDE 4.7 and watch the fun begin. vsync or tear free desktop make it painfully slow, so disable them and it seems to run fine until you load a game and it destroys X. (which also happens in GNOME.
KDE 4.7 feeds FGLRX the obsolete OpenGL 1.4 backend to make it shut up and work. Should it have to?
Who's to blame for FGLRX not working in Gnome Shell? Is it the Gnome devs or AMD? Either way, AMD should probably step up and put some effort into fixing the problem.
And GNOME should put in some effort to fix things too. I should probably make a disclaimer at this point: I don't deal directly with opengl interaction with X, so I'm not sure of what magic is done in there. I just wanted to point out that people are so quick to blame AMD for everything that they forget the other side - gnome. Who's to "blame"? Well, don't know that one. Maybe one, maybe the other, maybe both. People love to bandy nvidia's name about, but they conveniently forget that developers have had time to work around nvidia's driver problems (and new ones to crop up from time to time too). See wine for additional examples of that.
Originally Posted by gururise
If something is broken in the way gnome does things, AMD shouldn't have to break their drivers to be compatible. Vice versa. Same applies with nvidia. Same with any open source driver.
Or put in another way: blaming AMD when you don't actually know what the problem is, doesn't make any sense. Blame them when you know what their driver is doing wrong, blame gnome when they're doing something wrong (maybe FBO attachments aren't the same bit-depth, stuff like that), and equally blame nvidia for what's broken in their drivers.
I'm with mirv
I have not encountered any big problems for a year at least. When I switched from nvidia to amd, for me it was getting better and better. I have nice story about PM issues with nvidia for 2 years on nvnews... No fix... AMD is actually done a lot better job for me than nvidia.
No need to blame AMD when there is no proof that actually they are responsible for the bug.
The big one to me seems to be gnome-shell slowness and corruption, KDE 4.7 works perfectly for me or I'm just lukcy (why not others?). I have mobility 3650, works nice, really. No issues with the driver.
Of want to blame anyone, get a proof and blame, that's the rule, else it's speculation and FUD
been using amd since beginning of 2010 (ati 5770). havent had any major driver issues.
only bug that im having is the mouse cursor stuck thingy. last 3 drivers with that bug.
native games have been working fine with amd and some wine games too. compiz works and no issues with tearing anymore aswell.
with nvidia i had more wine games working tho. with amd its little problematic. but those probably some wine bugs.
don't have problems with kde 4.7
Originally Posted by DaemonFC
what is wrong in using the ogl 1,4 renderer until the openGL2 or openGL2ES renderer works ?
Originally Posted by DaemonFC
well it is an fglrx issue since nvidia blob, nouveau, intel dri and r600g run the opengl2 path in kwin perfectly but my 4850x2 with catalyst any version (properly installed) just get really funky here, is not like i care too much on my side since i trully love r600g
Originally Posted by Qaridarium
btw i check catalyst not for masochist (you need to be) but because i got some clients i can't convince to abandon firepro for some good supported quadro cards, so i have to check from time to time if fglrx is stable to avoid shoot myself in the foot offering me to upgrade their drivers