tball: I have a Mobility FireGL v5700 wich is a HD3650...
Here is the suport thread I started on ubuntuforums for my laptop if you would like to see all the stuff I have to do to get it to work.
It looks simple now that I worte that thread but it took me over a month to figure it all out (the catalyst I just found the last few tweeks for) I consider having to use a patched Xserver a major tweek.
But ya was to genoral about the catlayst not working. It dosn't work with my card with any of the suported distors with out major tweeking.
But ya isn't Arch the s/h/i/t :)
Note, the Intel wifi driver problem is not a problem with the driver it is a problem with Ubuntu. It works fine in Arch. Flash is also a problem in Ubuntu but works fine is Arch. In Ubuntu when I play video games like supertuxkart the game thinks I am pressing joydown all the time but in Arch that is not a problem
The release cycal should not be based on things Like Ubuntu's LTR cycle. They should base it on owe... every other kernel and every Xserver. Also, from what I remember reading, the arch dev in charge of calalyst support and on the mailling list didn't think they were addressing any of the problems that were making it so hard to work with. So, new catalyst driver update every month was probably just adding to the problem not solving it.
As I understand it, kernel devs don't like standardizing the internal interfaces because they don't want to be put in a position where out-of-tree concerns end up holding more sway over the internal kernel architecture than in-tree concerns. They want to be free to reorganize, tear down and rebuild anything they think they can improve within the kernel, without being pressured to support every version of every interface going back a decade or more. OTOH they take standardization of userland<->kernel interfaces pretty seriously.