Difference between revisions of "Talk:AMD Catalyst"

From ArchWiki
Jump to: navigation, search
(Binary blob modifications)
(Thanks: Close log.)
(29 intermediate revisions by 11 users not shown)
Line 1: Line 1:
 +
== Notes on major overhaul ==
 +
Hm, I didn't know there was a behind-the-scene page we could discuss this. I had already mentioned some points on the forums I wasn't sure about when I did the major overhaul and update. I will also list them here so other people that don't use the forum can see it (plus my post it already amongst dozens of older ones in the ATI Grill)
 +
 +
* Xorg example file; is it needed? And if it is, most entries are uncommented and I think we should at least provide some information on the options if we decide to keep it.
 +
* Installing from AMD. Should we even instruct this? It's absolutely unrecommended and I for one don't know if the instructions are correct.
 +
 +
Thanks for working on this article everyone!
 +
 +
[[User:Unia|Unia]] 00:29, 14 October 2012 (Amsterdam)
 +
 +
== <s> Thanks </s> ==
 
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.
 
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.
  
Line 12: Line 23:
  
 
[[User:Foutrelis|Foutrelis]] 15:35, 18 August 2010 (EDT)
 
[[User:Foutrelis|Foutrelis]] 15:35, 18 August 2010 (EDT)
 
== Cleanup ==
 
 
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. --[[User:Doc Angelo|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.
 
--[[User:Vi0L0|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... --[[User:t1nk3r3r|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 ;) -- [[User:Kynikos|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. --[[User:T1nk3r3r|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 <u>try</u> 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 :) -- [[User:Kynikos|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... --[[User:Vi0L0|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? --[[User:T1nk3r3r|T1nk3r3r]] 01:45, 19 September 2011 (EDT)
 
  
 
== deleted note on nomodeset warning ==
 
== deleted note on nomodeset warning ==
Line 39: Line 29:
 
[[User:4javier|4javier]] 07:50, 25 April 2011 (EDT)
 
[[User:4javier|4javier]] 07:50, 25 April 2011 (EDT)
  
== Binary blob modifications ==
+
== HD 6870 ==
 +
 
 +
I think the problems with Radeon HD 6870 are outdated, I use that graphics card and I didn't have any problems at all, even OpenCL works fine. -- [[User:Lykos42|Lykos42]] 14:04, 14 March 2012 (EDT)
 +
:Added [[Template:Accuracy]], please next time don't be afraid of adding status templates by yourself :) -- [[User:Kynikos|Kynikos]] 07:59, 15 March 2012 (EDT)
 +
I cannot speak for speak for the HD 6870 but I can confirm that the problem still exists for the E-350 (APU with a HD 6310), and that the posted solution works if the device name is changed (and perhaps without changing it, I didn't test). I have therfore removed the disputed banner and generalized the answer. (As is suspect the fix works for virtually any "unsupported" device). If someone could confirm the naming scheme for the Xorg identifier I would appreciate it. --[[User:Eric Vuhl|Eric Vuhl]] ([[User talk:Eric Vuhl|talk]]) 12:19, 21 July 2012 (UTC)
 +
 
 +
== Compatibility table ==
 +
 
 +
I've been thinking for a while it might be nice to have a compatibility table or something to see which version of Catalyst works with which versions of X and the Linux kernel. Would this be totally off? Is there a better place to see this information? Would there be a better place to store this information? --[[User:Freso|Freso]] ([[User talk:Freso|talk]]) 11:01, 22 October 2012 (UTC)
 +
 
 +
--
 +
 
 +
I'm not sure for the need of this, why would people want to use an older version? AFAIK there are no major problems with Catalyst 12.9 nor with Catalyst-legacy. For those two, the information is already there:
 +
 
 +
1. Users with Radeon HD {2,3,4}xxx can only use catalyst-legacy which supports Xorg <= 1.12 (use [xorg112] repo)
 +
2. Users with Radeon HD => 5xxx should use catalyst which supports Xorg 1.13
 +
 
 +
Of course, the more info the better, so if you want to add this feel free to do so! ==[[User:Unia|Unia]]
 +
 
 +
== vaapi with smplayer ==
  
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.
+
I found smplayer config to use mplayer-vaapi not right.
--[[User:T1nk3r3r|T1nk3r3r]] 02:23, 16 September 2011 (EDT)
+
If you set Video output Driver to vaapi or vaapi:gl, you'll not need to add extra options -vo vaapi to mplayer options
: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 --[[User:Vi0L0|Vi0L0]] 10:32, 18 September 2011 (EDT)
+
Mplayer won't work if both -lavadopts and -vo vaapi are set.
::Yes, I use *only* the original installer.  I am referring to the scripts. And I have it working now. --[[User:T1nk3r3r|T1nk3r3r]] 01:55, 19 September 2011 (EDT)
+
So we need to turn off -lavadopts option (useful when decode by CPU, but usesless with GPU) by set "Threads for decoding" to 1 in Performance section.
 +
Therefore I decided to edit wiki section about using smplayer. Hope this will be useful for someone!

Revision as of 02:58, 25 November 2012

Notes on major overhaul

Hm, I didn't know there was a behind-the-scene page we could discuss this. I had already mentioned some points on the forums I wasn't sure about when I did the major overhaul and update. I will also list them here so other people that don't use the forum can see it (plus my post it already amongst dozens of older ones in the ATI Grill)

  • Xorg example file; is it needed? And if it is, most entries are uncommented and I think we should at least provide some information on the options if we decide to keep it.
  • Installing from AMD. Should we even instruct this? It's absolutely unrecommended and I for one don't know if the instructions are correct.

Thanks for working on this article everyone!

Unia 00:29, 14 October 2012 (Amsterdam)

Thanks

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)

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)

HD 6870

I think the problems with Radeon HD 6870 are outdated, I use that graphics card and I didn't have any problems at all, even OpenCL works fine. -- Lykos42 14:04, 14 March 2012 (EDT)

Added Template:Accuracy, please next time don't be afraid of adding status templates by yourself :) -- Kynikos 07:59, 15 March 2012 (EDT)

I cannot speak for speak for the HD 6870 but I can confirm that the problem still exists for the E-350 (APU with a HD 6310), and that the posted solution works if the device name is changed (and perhaps without changing it, I didn't test). I have therfore removed the disputed banner and generalized the answer. (As is suspect the fix works for virtually any "unsupported" device). If someone could confirm the naming scheme for the Xorg identifier I would appreciate it. --Eric Vuhl (talk) 12:19, 21 July 2012 (UTC)

Compatibility table

I've been thinking for a while it might be nice to have a compatibility table or something to see which version of Catalyst works with which versions of X and the Linux kernel. Would this be totally off? Is there a better place to see this information? Would there be a better place to store this information? --Freso (talk) 11:01, 22 October 2012 (UTC)

--

I'm not sure for the need of this, why would people want to use an older version? AFAIK there are no major problems with Catalyst 12.9 nor with Catalyst-legacy. For those two, the information is already there:

1. Users with Radeon HD {2,3,4}xxx can only use catalyst-legacy which supports Xorg <= 1.12 (use [xorg112] repo) 2. Users with Radeon HD => 5xxx should use catalyst which supports Xorg 1.13

Of course, the more info the better, so if you want to add this feel free to do so! ==Unia

vaapi with smplayer

I found smplayer config to use mplayer-vaapi not right. If you set Video output Driver to vaapi or vaapi:gl, you'll not need to add extra options -vo vaapi to mplayer options Mplayer won't work if both -lavadopts and -vo vaapi are set. So we need to turn off -lavadopts option (useful when decode by CPU, but usesless with GPU) by set "Threads for decoding" to 1 in Performance section. Therefore I decided to edit wiki section about using smplayer. Hope this will be useful for someone!