Originally posted by alec
View Post
Announcement
Collapse
No announcement yet.
Arch Linux Revolts Against ATI Catalyst Driver
Collapse
X
-
Last edited by hunterthomson; 09 June 2009, 03:47 AM.
-
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.
Aloha ):P by, HunterThomson - HowTo's that WORK ! The Open Source ATI driver xf86-video-ati is a far better driver then the Catalyst. However, it has poor power saving support, so could run hotter. Also, has poor 3D support but can play Quake Live, Tribal Trouble 2, Super Tux Kart, Open Arena. However, EVERYTHING ells is SUPER. KVM 2D, Video, All that is really good. However, I am happy to say we got EVERYTHING working on this laptop. Well all but the fingerprint reader but from what I
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 problemLast edited by hunterthomson; 09 June 2009, 03:56 AM.
Comment
-
Originally posted by hunterthomson View PostIf it is so hard then why dose Intel never have a problem with Linux suport? All there drivers for Wireless, Graphics,... are always rock sold and upto date. ATI need to retool there drivers so they don't rely on stuff that is going to change in the next kernel or Xserver. They need to make it more modular so changes can be made with less effort.
Comment
-
Originally posted by mirv View PostATI have probably done that as much as they can - but then we start getting into standardising interfaces, which the kernel devs don't like doing, and is one of the key issues of fglrx / kernel incompatibility. They probably do have support easily for new stuff, but due to their development cycle it'll bake for a month or two before being released (by which time things can change again). That's a con - a pro is that we get updated drivers every month!
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.Last edited by hunterthomson; 09 June 2009, 04:47 AM.
Comment
-
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.
Comment
-
Originally posted by Ex-Cyber View PostAs 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.Last edited by hunterthomson; 09 June 2009, 04:51 AM.
Comment
Comment