Talk:AMD Catalyst

From ArchWiki
Revision as of 15:49, 19 September 2011 by Vi0L0 (talk | contribs) (Cleanup)
Jump to: navigation, search

I love you guys for putting this wiki entry together and maintaining the repositories with the Catalyst driver and the patched mplayer with support for hardware acceleration. It would have taken me many, many hours to make it work as flawlessly as it does.

Foutrelis 06:11, 21 June 2010 (EDT)

XvBA-Video Repository

Note to editors: DO NOT REMOVE that since it works and helps users getting it working!

Why keep it around if the information is obsolete now?

Foutrelis 15:35, 18 August 2010 (EDT)


I think the page needs a good portion of reconstruction. The "Installation" chapter is bloated and cluttered with alot of information one does not necessarily need. Maybe its a good idea to make an new page about the usage details for the script catalyst_build_module. "Troubleshooting" is cluttered and one time even doubled. I am going to make the page more straightforward and vanilla, putting any additional info in new chapters or pages. If no one complains, that is. --Doc Angelo 06:06, 22 August 2010 (EDT)

I made some cleanup...

  • Removed about 20% of article (mainly repo section).
  • Troubleshooting isn't doubled now but still a little bit cluttered (still i think it got very usefull infos).
  • catalyst_build_module script info is simpler and shorter.

--Vi0L0 16:59, 8 February 2011 (EST)

After referring to this article many times for my own use, I believe the place to start is dividing between 'fglrx from AUR' and 'fglrx straight from binary'. Maybe going so far as to making a separate page. And then the bloat can tackled with gusto, with some things reorganized and others clarified/reworded. I will work on this myself if I find the time... --t1nk3r3r --- Since previous efforts have stalled, I will take upon myself to clean up this article. I have already drawn up an outline with only four main sections while retaining as much info as possible. Major changes in the next several days... --t1nk3r3r 4 August 2011 (PST) ---

I'm not using ATI, so I can't help you with possible mistakes, but I suggest you to split your work in as many edits (i.e. revisions) as possible, so that people can understand more easily your changes ;) -- Kynikos 04:40, 6 August 2011 (EDT)
Sorry, this is my first serious wiki editing session. But I will be more mindful in the future, making incremental updates that can be scrutinzed more easily. I just didn't want a million edits on the history page (although that may be what it needs). Changes included: Reorganizing the Installation section to differentiate the two methods; Combining/rewording the first paragraph, making it clearer and more neutral in tone; removing several "troubleshooting" entries as redundant with proper installation; removing alot of "ie" and "eg" that really aren't necessary; removing other "word fluff" making instructions more concise; Adding a "features" section for recommended settings in xorg.conf; removing some instructions on using AUR when it has it's own page with how to use it; Moving "Unofficial repos" to the AUR method where they belong; added steps to the second method (based on personal experience/success). As to future edits, I plan to consolidate the AUR method/tool section further (excepting ViOLO's objection). And expanding the Configuration while removing pertinent Troubleshooting entries. Minor edits would be mostly adjustments to wording/language. --T1nk3r3r 12:47, 6 August 2011 (EDT) ---
Eheh now don't take me literally, with "as many edits as possible" I meant that you should try not to group together different kind of edits like sentence rewording and, say, deprecated content removal. Just always remember to prefer writing in the edit summary the reason for your changes, more than really a summary, although I see you're already doing it well :) -- Kynikos 05:30, 7 August 2011 (EDT)
Overall good job! :) I only changed some things that i noticed: moved repositories out from AUR since it's not logicall for me to place it there; + i put catalyst-generator into main manu again cuz i rly like this tool... --Vi0L0 10:26, 18 September 2011 (EDT)
So the "Unofficial Repositories" section is basically Catalyst binaries that have been extracted and rebuilt into installable Arch packages? --T1nk3r3r 01:45, 19 September 2011 (EDT)
Yes, catalyst and other packages, current list of packages is:
amdoverdrivectrl 1.2.1-1
catalyst 11.8-1
catalyst-daemon 11.8-1
catalyst-generator 11.8-1
catalyst-hook 11.8-1
catalyst-utils 11.8-1
lib32-catalyst-utils 11.8-1
xorg-server-catalyst-maximize-fix 1.10.4-1
xvba-video 0.7.8-4
True - you will find packages' PKGBUILDs which were used to build those packages on AUR, but "Unofficial repositories" are not AUR: --Vi0L0 11:47, 19 September 2011 (EDT)

deleted note on nomodeset warning

the nomodeset option si mandatory using catalyst, cause this driver doesn't support kms. The note is useless. 4javier 07:50, 25 April 2011 (EDT)

Binary blob modifications

Using Catalyst 11.8 with kernel 3.0 appears to be broken, at least as far as the built-in scripts are concerned. Anyone have issue with additional instructions in the wiki as I get it working? Initial experimentation shows the generated module is at least partially usable. Tweaks to the scripts may make it usable again (until AMD updates the process). I know this article has been helpful to me since before I even started using Arch, and hope it can ease the headache of others. --T1nk3r3r 02:23, 16 September 2011 (EDT)

Why broken? By 'built-in scripts' you mean those from originall AMD's installer? I'm asking cuz i don't have any problems, and now i'm using 3.1-rc6 --Vi0L0 10:32, 18 September 2011 (EDT)
Yes, I use *only* the original installer. I am referring to the scripts. And I have it working now. --T1nk3r3r 01:55, 19 September 2011 (EDT)