Talk:AMD Catalyst

From ArchWiki
Jump to: navigation, search


The default selection on installation of catalyst from Vi0L0's repos is set on catalyst-daemon, this page needs a section about the new daemon which as I understand is to replace catalyst-hook?

Double Screen

The link to "Ati Documentation" in this section seems dead, and I think examples of xorg.conf are welcome. Mikhaddo (talk) 11:22, 8 October 2013 (UTC)

A kind request

People, please edit a whole section if you change a paragraph! Do not just edit one line and leave it: re-read the whole paragraph (and chapter header!) so see if everything still corresponds. Example: previous edit to "installing from the official repositories"; the header still said this was the most easiest approach as you need only the official repositories - after the latest edit this was not the case anymore as we request people to use catalyst-utils from the AUR! Be thorough when editing, please!Unia (talk) 11:25, 20 April 2013 (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!


Is catalyst-dkms working fine without the additional mkinitcpio-dkms package?

By working fine i mean will it compile fglrx module for freshly installed kernel in the background?

Building module while system start is not safe. You system will probably start X before module will be build and so X will fail terribly. AFAIK last related post on the forums in telling that the additional mkinitcpio-dkms package is needed.

If it's needed then such information should be added to the wiki.

Even more - if it's needed then i would say that mkinitcpio-dkms package should be added to the community and catalyst-dkms should depend on it, otherwise it's hard to consider catalyst-dkms as "safe". --Vi0L0 (talk) 10:22, 22 March 2013 (UTC)

What's more of an issue for now, is if catalyst-dkms will remain available in the repositories now that xorg-server 1.14 became available. Do you have contact with its maintainer?Unia (talk) 15:07, 22 March 2013 (UTC)

There was a threat on arch-dev-public: [1]. Looks like it will stay.--Vi0L0 (talk) 19:28, 22 March 2013 (UTC)

Content duplication

There is already a catalyst wiki and we'd have to check in how far this article duplicates it... -- Alad (talk) 01:50, 1 September 2014 (UTC)

Unclear note

Note: To adhere to the new config location use # aticonfig [...] --output to adapt the Device section to /etc/X11/xorg.conf.d/20-radeon.conf. The drawback is that many aticonfig options rely on an xorg.conf, and will be unavailable.

This is confusing. What is being recommended to do? Can somebody clarify this on the wiki page please? --Qubodup (talk) 20:35, 28 April 2015 (UTC)

pxp packages removal

Since 15.7 catalyst itself provides powerXpress support, so pxp packages were removed from Vi0L0's repository. But I was unable to get my hybrid graphics work with standard package set. The information on wiki has to be updated --Jqrsd (talk) 19:13, 19 August 2015 (UTC)

Conflicting dependency information

It is not clear from the information on the page if the Catalyst driver works with Xorg Server 1.17 or not. "The legacy Catalyst driver does not support Xorg Server 1.17." seems to imply that it works. "Catalyst does not support xorg-server 1.17" means it doesn't. I use catalyst with Xorg Server 1.17 and it seems to work. Andrimne (talk) 22:19, 26 September 2015 (UTC)

More contradictions:] and [2]. -- Alad (talk) 17:00, 23 October 2015 (UTC)


Re [3], several issues:

  1. Incompatible Xorg and kernel versions seems to be a recurring theme with these drivers, so instructions how to handle it should be featured prominently. Not by placing them right in the middle of a supermassive Troubleshooting section. Incidentally, there's already AMD_Catalyst#Xorg_repositories.
  2. It's enough to post the relevant few error messages, not the complete log.
  3. How do those Ubuntu instructions work in Arch? Oh, it's

-- Alad (talk) 16:41, 23 October 2015 (UTC)

Running two x-servers with hybrid-graphic system


can anyone please update this discription Running two X servers ? An example is needed. Otherwise this text makes no sense for the most of the people. For ex. I am running a MATE-Desktop with lightdm, I realy have no Idea how to set the idea up. BTW: Starting Game in a separte X server is more specific, but I think this is not what meant in the first case. With regards YaH (talk) 20:30, 18 April 2016 (UTC)

Warn about depreciation

Catalyst is not updated anymore and therefore require downgrading Xorg and the kernel. For newer cards there is amd-gpu or amd-gpupro. For older cards xf86-ati or the Xorg modesetting driver will give the same performance. The wiki should warn to avoid this driver unless there is no other options for some reasons.

—This unsigned comment is by Olive (talk) 08:04, 8 June 2017‎. Please sign your posts with ~~~~!

The warning is already in the 3rd paragraph on the page, closing. -- Lahwaacz (talk) 14:24, 8 June 2017 (UTC)