Talk:AMD Catalyst

From ArchWiki
Jump to navigation Jump to search

catalyst-daemon

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?

—This unsigned comment is by 0X1A (talk) 18:55, 10 June 2014‎ (UTC). Please sign your posts with ~~~~!

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!

catalyst-dkms

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: https://wiki.archlinux.org/index.php?title=AMD_Catalyst&diff=406279&oldid=406278] and [2]. -- Alad (talk) 17:00, 23 October 2015 (UTC)

Structure

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 paste.ubuntu.com.

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

Running two x-servers with hybrid-graphic system

Hello,

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)

Xorg repository not working anymore

After adding the repo, pacman -Syuu returns

pacman -Syuu
:: Synchronizing package databases...
 catalyst is up to date
 xorg117 is up to date
 core is up to date
 extra is up to date
 community is up to date
 multilib is up to date
:: Starting full system upgrade...
warning: cogl: downgrading from version 1.22.6-1 to version 1.22.2+10+g3baa2d7a-1.1
:: Replace lib32-mesa with catalyst/lib32-mesa-noglvnd? [Y/n] Y
:: Replace mesa with catalyst/mesa-noglvnd? [Y/n] Y
warning: mutter: downgrading from version 3.36.2-1 to version 3.24.3-1.1
:: Replace opencl-mesa with catalyst/opencl-mesa-noglvnd? [Y/n] Y
warning: xf86-input-libinput: downgrading from version 0.30.0-1 to version 0.15.0-1
warning: xf86-video-ati: downgrading from version 1:19.1.0-2 to version 1:7.5.0-2
warning: xorg-server: downgrading from version 1.20.8-2 to version 1.17.4-2
warning: xorg-server-common: downgrading from version 1.20.8-2 to version 1.17.4-2
warning: xorg-server-xephyr: downgrading from version 1.20.8-2 to version 1.17.4-2
warning: xorg-server-xvfb: downgrading from version 1.20.8-2 to version 1.17.4-2
warning: xorg-server-xwayland: downgrading from version 1.20.8-2 to version 1.17.4-2
resolving dependencies...
warning: cannot resolve "xproto", a dependency of "libxfont"
warning: cannot resolve "fontsproto", a dependency of "libxfont"
warning: cannot resolve "libxfont", a dependency of "xorg-server"
warning: cannot resolve "xproto", a dependency of "libxfont"
warning: cannot resolve "fontsproto", a dependency of "libxfont"
warning: cannot resolve "libxfont", a dependency of "xorg-server"
warning: cannot resolve "xorg-server<1.18.0", a dependency of "catalyst-utils"
warning: cannot resolve "catalyst-utils", a dependency of "lib32-catalyst-utils"
warning: cannot resolve "lib32-libtxc_dxtn", a dependency of "lib32-mesa-noglvnd"
warning: cannot resolve "xproto", a dependency of "libxfont"
warning: cannot resolve "fontsproto", a dependency of "libxfont"
warning: cannot resolve "libxfont", a dependency of "xorg-server"
warning: cannot resolve "xproto", a dependency of "libxfont"
warning: cannot resolve "fontsproto", a dependency of "libxfont"
warning: cannot resolve "libxfont", a dependency of "xorg-server-xephyr"
warning: cannot resolve "xproto", a dependency of "libxfont"
warning: cannot resolve "fontsproto", a dependency of "libxfont"
warning: cannot resolve "libxfont", a dependency of "xorg-server-xvfb"
warning: cannot resolve "xproto", a dependency of "libxfont"
warning: cannot resolve "fontsproto", a dependency of "libxfont"
warning: cannot resolve "libxfont", a dependency of "xorg-server-xwayland"
:: The following packages cannot be upgraded due to unresolvable dependencies:
      lib32-mesa-noglvnd  xorg-server  xorg-server-xephyr  xorg-server-xvfb  xorg-server-xwayland

:: Do you want to skip the above packages for this upgrade? [y/N] n
error: failed to prepare transaction (could not satisfy dependencies)
:: unable to satisfy dependency 'xproto' required by libxfont
:: unable to satisfy dependency 'fontsproto' required by libxfont
:: unable to satisfy dependency 'libxfont' required by xorg-server
:: unable to satisfy dependency 'xproto' required by libxfont
:: unable to satisfy dependency 'fontsproto' required by libxfont
:: unable to satisfy dependency 'libxfont' required by xorg-server
:: unable to satisfy dependency 'xorg-server<1.18.0' required by catalyst-utils
:: unable to satisfy dependency 'catalyst-utils' required by lib32-catalyst-utils
:: unable to satisfy dependency 'lib32-libtxc_dxtn' required by lib32-mesa-noglvnd
:: unable to satisfy dependency 'xproto' required by libxfont
:: unable to satisfy dependency 'fontsproto' required by libxfont
:: unable to satisfy dependency 'libxfont' required by xorg-server
:: unable to satisfy dependency 'xproto' required by libxfont
:: unable to satisfy dependency 'fontsproto' required by libxfont
:: unable to satisfy dependency 'libxfont' required by xorg-server-xephyr
:: unable to satisfy dependency 'xproto' required by libxfont
:: unable to satisfy dependency 'fontsproto' required by libxfont
:: unable to satisfy dependency 'libxfont' required by xorg-server-xvfb
:: unable to satisfy dependency 'xproto' required by libxfont
:: unable to satisfy dependency 'fontsproto' required by libxfont
:: unable to satisfy dependency 'libxfont' required by xorg-server-xwayland

Tallero (talk) 22:17, 1 June 2020 (UTC)

Archiving this page

I am in favor of archiving this page.

  1. Catalyst is too old now. It is unsupported and this may cause dangerous situations.
  2. It requires an old Xorg version, it does not get security patches anymore.
  3. AMD Catalyst#Unsupported Xorg Version basically states "Let us downgrade Xorg even more" and the resulting setup is even more unsupported.
  4. Partial upgrades are unsupported.
  5. Seems like the repos needed for this do not work anymore, too.
  6. Cards which need Catalyst are so old that no one will probably even bother with acceleration because it requires all these unsupported steps

Unless someone comes up with a magical solution to fix at least most of the things I stated, I do not think there are reasons for keeping this page anymore.

-- NetSysFire (talk) 07:41, 17 April 2021 (UTC)

There's plenty of unsupported stuff on the wiki and it's up to readers/users to decide whether they want to risk it or not. Break it, keep the pieces. To me a more relevant factor is if the approach still works and someone maintains it. As mentioned, according to #Xorg repository not working anymore that's no longer the case, especially when the required Xorg versions are not in AUR either.
As such, I'd suggest to file deletion requests for catalystAUR and related packages and archive this page afterwards. -- Alad (talk) 21:49, 19 April 2021 (UTC)
All the AUR packages have been removed. There are still pages that link to this page, which need to be modified. When this is done the page can, in my opinion, be archived.
-- NetSysFire (talk) 18:28, 7 May 2021 (UTC)