The AMD/ATI Bar & Grill

Vi0L0 · 2014-03-10 20:11:01

what about:
pacman -Sy
pacman -S catalyst-utils catalyst-libgl opencl-catalyst
?

s0l1dsnak3123 · 2014-03-10 20:15:05

Running that gave me:

λ ruby-2.1.0 →  orion lib → pacman -S catalyst-utils catalyst-libgl opencl-catalyst
resolving dependencies...
looking for inter-conflicts...

Packages (3): catalyst-libgl-14.2-2  catalyst-utils-14.2-2  opencl-catalyst-14.2-2

Total Download Size:    33.83 MiB
Total Installed Size:   148.23 MiB
Net Upgrade Size:       0.06 MiB

:: Proceed with installation? [Y/n] 
:: Retrieving packages ...
 catalyst-utils-14.2-2-x86_64                                           24.5 MiB   776K/s 00:32 [########################################################] 100%
 catalyst-libgl-14.2-2-x86_64                                         1440.0   B  0.00B/s 00:00 [########################################################] 100%
 opencl-catalyst-14.2-2-x86_64                                           9.4 MiB   779K/s 00:12 [########################################################] 100%
(3/3) checking keys in keyring                                                                  [########################################################] 100%
(3/3) checking package integrity                                                                [########################################################] 100%
(3/3) loading package files                                                                     [########################################################] 100%
(3/3) checking for file conflicts                                                               [########################################################] 100%
error: failed to commit transaction (conflicting files)
catalyst-libgl: /usr/lib/libEGL.so exists in filesystem
catalyst-libgl: /usr/lib/libEGL.so.1 exists in filesystem
catalyst-libgl: /usr/lib/libEGL.so.1.0.0 exists in filesystem
catalyst-libgl: /usr/lib/libGLESv2.so exists in filesystem
catalyst-libgl: /usr/lib/libGLESv2.so.2 exists in filesystem
catalyst-libgl: /usr/lib/libGLESv2.so.2.0.0 exists in filesystem
Errors occurred, no packages were upgraded.
λ ruby-2.1.0 →  orion lib →

I removed the symlinks to libEGL* and libGLESv* and tried again:

λ ruby-2.1.0 →  orion lib → pacman -S catalyst-utils catalyst-libgl opencl-catalyst                               
resolving dependencies...
looking for inter-conflicts...

Packages (3): catalyst-libgl-14.2-2  catalyst-utils-14.2-2  opencl-catalyst-14.2-2

Total Installed Size:   148.23 MiB
Net Upgrade Size:       0.06 MiB

:: Proceed with installation? [Y/n] 
(3/3) checking keys in keyring                                                                  [########################################################] 100%
(3/3) checking package integrity                                                                [########################################################] 100%
(3/3) loading package files                                                                     [########################################################] 100%
(3/3) checking for file conflicts                                                               [########################################################] 100%
(3/3) checking available disk space                                                             [########################################################] 100%
(1/3) upgrading catalyst-utils                                                                  [########################################################] 100%
-------------------------- SPLIT -------------------------------
catalyst-utils is now splitted into:
catalyst-utils
catalyst-libgl
opencl-catalyst

You MOST probably want to also install catalyst-libgl
----------------------------------------------------------------
New optional dependencies for catalyst-utils
    catalyst-libgl: Catalyst drivers libraries symlinks. [pending]
    opencl-catalyst: OpenCL implemention for AMD Catalyst [pending]
(2/3) installing catalyst-libgl                                                                 [########################################################] 100%
(3/3) installing opencl-catalyst                                                                [########################################################] 100%
Optional dependencies for opencl-catalyst
    opencl-headers: headers necessary for OpenCL development
λ ruby-2.1.0 →  orion lib →

Thanks

Last edited by s0l1dsnak3123 (2014-03-10 20:16:11)

joelisntmyname · 2014-03-10 20:16:20

Yep that worked. I needed to also update mesa beforehand as I was avoiding updating mesa. I got a few similar errors about

catalyst-libgl: /usr/lib/libGLESv2.so exists in filesystem

before updating mesa alongside the rest.

SteveK · 2014-03-10 20:17:36

I installed the new packages at the same time as updating:

pacman -Syu lib32-catalyst-libgl catalyst-libgl lib32-catalyst-utils catalyst-utils opencl-catalyst

That worked for me.

tybo · 2014-03-10 22:05:41

Hi,

It seems the following packages yield a 404 http error when pacman tries to download them:
lib32-catalyst-utils-14.2-2-x86_64.pkg.tar.xz
lib32-catalyst-libgl-14.2-2-x86_64.pkg.tar.xz
lib32-opencl-catalyst-14.2-2-x86_64.pkg.tar.xz

I also could not find them in the package list here:
http://catalyst.wirephire.com/repo/catalyst/x86_64/

Seems the only available version is 13.12, which seems odd..
Perhaps a mishap when the packages where updated?

Anyway thanks for the repo! It's really convenient!

Cheers!

Vi0L0 · 2014-03-10 22:13:42

Should be fine now, I will check all repos one more time

tybo · 2014-03-10 22:17:34

Yep! Everything is working fine now!

Thanks a lot for the great work!

DarksideEE7 · 2014-03-11 00:41:21

Vi0L0 wrote:

I recently bought "MSI 290X Gaming" and have this "lag" whenever I'm scrolling text in text editor or scrolling in file manager. In both KDE and GNOME3 (on Gnome it's even more painfull), no matter if compositing is enabled or disabled.
Definitelly something bad is going on with ATI's 2D Acceleration.
There's no problem with web browsers - scrolling works perfectly, also on chromium with aura (edit: I said it too early, scrolling works fine only in chromium and opera, sucks in qupzilla and firefox)
I checked 13.111, 14.1 and 14.2, tried disabling and enabling some options, nothing helped.
Can some owner of 290(X) (probably also 260X) confirm? I searched bugzilla but didn't find a tip, so I would like to report it.
Open source drivers also aren't working well with 290X - scrolling in editor or file manager is much better, yes, but it's not that well on chromium, also 3d performance is terrible...
Well... it looks like I did it again - I bought AMD hardware too quickly . I was waiting months but, just like with 7850, it was not enought. Now I would have to patently wait for a salvation ;P...
Edit: here's bug report

As for the 14.1 - I can see that I removed it from the repo too quickly... I didn't notice any problems, there should be no regression is such a small update, but if someone will confirm Jannis' problems I think I will reup 14.1 repo again (as an archive)

I tested with 3 290Xs on 14.2 with a fully updated system and I don't have this. I've been running this setup for a few months now and the only problem I have is %100 CPU usage on a single logical CPU from kwin. This is on 3 monitor portrait, not that it probably matters.

lano1106 · 2014-03-11 06:15:35

Hi guys,

I have released glcs, a spin of glc allowing to pipe its output directly to ffmpeg generating much smaller output file. ie: My first 1080P capture of 6 mins is smaller than 200 MB. This also open up a bunch of new possibilities such as live gamecasting through RTMP.

If you are interested in trying it out, here is the official thread:
https://bbs.archlinux.org/viewtopic.php … 0#p1391030

My first 1080P capture is at:
https://www.youtube.com/watch?v=EYYeIefOgq0

video quality could have been better as I wanted to leverage my second 7970 card to use openCL during H.264 encoding but because of the shitty catalyst 14.2 release, it isn't possible for now:
http://ati.cchtml.com/show_bug.cgi?id=1038

Lockheed · 2014-03-11 11:53:53

I am running catalyst-total-hd234k form the repository on xorg112.
Pacman says:

$ pacman -Qi catalyst-total-hd234k
Name           : catalyst-total-hd234k
Version        : 13.1-20

However, I just checked in the WiKi, and it says:

xorg113
Catalyst < 13.6 doesn't support xorg-server 1.14.
xorg112
Catalyst < 12.10 and Catalyst Legacy do not support xorg-server 1.13.

which would suggest, that with catalyst-total-hd234k v.13.1, I should be able to upgrade to xorg 113. So in pacman.conf, I changed repo xorg112 to xorg113, but system update results in:

:: catalyst-total-hd234k: requires xorg-server<1.13.0

Do I get this wrong and catalyst-total-hd234k 13.1 still requires xorg 1.12?

Last edited by Lockheed (2014-03-11 11:54:23)

Armadillux · 2014-03-11 17:35:17

SteveK wrote:

I installed the new packages at the same time as updating:
pacman -Syu lib32-catalyst-libgl catalyst-libgl lib32-catalyst-utils catalyst-utils opencl-catalyst
That worked for me.

Nice one, worked for me too!

scjet · 2014-03-11 18:50:06

Linux 3.13.5-1-ARCH x86_64 GNU/Linux
X.Org X Server 1.15

catalyst-test 14.2-2 (from AUR)

yaourt catalyst-test

...
Error: failed to commit transaction (conflicting files)
catalyst-test: /usr/lib/libEGL.so exists in filesystem
catalyst-test: /usr/lib/libEGL.so.1 exists in filesystem
catalyst-test: /usr/lib/libEGL.so.1.0.0 exists in filesystem
catalyst-test: /usr/lib/libGLESv1_CM.so exists in filesystem
catalyst-test: /usr/lib/libGLESv1_CM.so.1 exists in filesystem
catalyst-test: /usr/lib/libGLESv1_CM.so.1.1.0 exists in filesystem
catalyst-test: /usr/lib/libGLESv2.so exists in filesystem
catalyst-test: /usr/lib/libGLESv2.so.2 exists in filesystem
catalyst-test: /usr/lib/libGLESv2.so.2.0.0 exists in filesystem
catalyst-test: /usr/lib32/libEGL.so exists in filesystem
catalyst-test: /usr/lib32/libEGL.so.1 exists in filesystem
catalyst-test: /usr/lib32/libEGL.so.1.0.0 exists in filesystem
catalyst-test: /usr/lib32/libGLESv1_CM.so exists in filesystem
catalyst-test: /usr/lib32/libGLESv1_CM.so.1 exists in filesystem
catalyst-test: /usr/lib32/libGLESv1_CM.so.1.1.0 exists in filesystem
catalyst-test: /usr/lib32/libGLESv2.so exists in filesystem
catalyst-test: /usr/lib32/libGLESv2.so.2 exists in filesystem
catalyst-test: /usr/lib32/libGLESv2.so.2.0.0 exists in filesystem
Errors occurred, no packages were upgraded.
...

I tried removing "just" the symlinks, as mentioned elsewehere here, of which I obviously made it worse, it failed with:

error: failed to commit transaction (conflicting files)
catalyst-test: /usr/lib/libEGL.so.1.0.0 exists in filesystem
catalyst-test: /usr/lib/libGLESv1_CM.so.1.1.0 exists in filesystem
catalyst-test: /usr/lib/libGLESv2.so.2.0.0 exists in filesystem
catalyst-test: /usr/lib32/libEGL.so.1.0.0 exists in filesystem
catalyst-test: /usr/lib32/libGLESv1_CM.so.1.1.0 exists in filesystem
catalyst-test: /usr/lib32/libGLESv2.so.2.0.0 exists in filesystem
Errors occurred, no packages were upgraded.

catalyst-test has been fine, give or take, for quite a while now, and using "yaourt" successfully,
except, for this.
sorry, but I've tried what I could decipher from the potential, but varied "fixes", mentioned here, but to no avail

Should I try and use this [repo] -> https://aur.archlinux.org/packages/catalyst-test/ instead of my usual AUR via "yaourt" ?

Last edited by scjet (2014-03-11 19:06:15)

Vi0L0 · 2014-03-11 19:14:10

DarksideEE7 wrote:

Vi0L0 wrote:
I recently bought "MSI 290X Gaming" and have this "lag" whenever I'm scrolling text in text editor or scrolling in file manager. In both KDE and GNOME3 (on Gnome it's even more painfull), no matter if compositing is enabled or disabled.
Definitelly something bad is going on with ATI's 2D Acceleration. (...)
I tested with 3 290Xs on 14.2 with a fully updated system and I don't have this. I've been running this setup for a few months now and the only problem I have is %100 CPU usage on a single logical CPU from kwin. This is on 3 monitor portrait, not that it probably matters.

Interesting... do you know what's the manufacturer of memory chips on your gfxes?

I just noticed that the problem of slow 2d Acceleration is gone whenever I start glxgears xD... it bumps clocks, eats more energy and it's not worth it but it is working, LOL.

Lockheed wrote:

Catalyst < 12.10 and Catalyst Legacy do not support xorg-server 1.13.
Do I get this wrong and catalyst-total-hd234k 13.1 still requires xorg 1.12?

You did forget that catalyst-total-hd234k = Catalyst Legacy

scjet wrote:

error: failed to commit transaction (conflicting files)
catalyst-test: /usr/lib/libEGL.so.1.0.0 exists in filesystem
catalyst-test: /usr/lib/libGLESv1_CM.so.1.1.0 exists in filesystem
catalyst-test: /usr/lib/libGLESv2.so.2.0.0 exists in filesystem
catalyst-test: /usr/lib32/libEGL.so.1.0.0 exists in filesystem
catalyst-test: /usr/lib32/libGLESv1_CM.so.1.1.0 exists in filesystem
catalyst-test: /usr/lib32/libGLESv2.so.2.0.0 exists in filesystem
Errors occurred, no packages were upgraded.

Are you sure that you updated mesa before this update? mesa package should be at least in version 10.1.0-2
You may check package owner of a file with (this could help you in many cases):
pacman -Qo /usr/lib/libEGL.so.1.0.0

PhotonX · 2014-03-11 20:24:11

Recent mesa upgrade to 10.1.0 has broken the entire system some days ago (Xorg terminated immediately after starting). Is it expected that things work properly if upgrading both mesa and catalyst? Don't want to experiment much since reverting the upgrade of catalyst seems to be a bit messy after the splitting of catalyst-utils.

scjet · 2014-03-11 20:50:40

Vi0L0 wrote:

scjet wrote:
error: failed to commit transaction (conflicting files)
catalyst-test: /usr/lib/libEGL.so.1.0.0 exists in filesystem
catalyst-test: /usr/lib/libGLESv1_CM.so.1.1.0 exists in filesystem
catalyst-test: /usr/lib/libGLESv2.so.2.0.0 exists in filesystem
catalyst-test: /usr/lib32/libEGL.so.1.0.0 exists in filesystem
catalyst-test: /usr/lib32/libGLESv1_CM.so.1.1.0 exists in filesystem
catalyst-test: /usr/lib32/libGLESv2.so.2.0.0 exists in filesystem
Errors occurred, no packages were upgraded.
Are you sure that you updated mesa before this update? mesa package should be at least in version 10.1.0-2
You may check package owner of a file with (this could help you in many cases):
pacman -Qo /usr/lib/libEGL.so.1.0.0

TY for reply,
right now, a "pacman -Qo /usr/lib/libEGL.so.1.0.0" gives me:
/usr/lib/libEGL.so.1.0.0 is owned by mesa 10.0.3-1

I'm now testing this on a spare Desktop, since whenever I tried previously above, "X' and/or Mesa ? crapped out, due to my attempted changes, and I couldn't even bring up a web browser.
Basically I'm just using the standard repo's : core, community, extra, multilib, and of course AUR, via "yaourt", for catalyst-test.

I'll try it again, when I can, but should I add your [repo], or download/makepkg..., to be able to get your latest mesa ?,
even though, I've usually had good results with just a "yaourt catalyst-test", in the past.
but I think I understand now, why it's doing it, as per other explanations here.

I would try "catalyst-total", but I would prefer to stay with latest Xorg-server-(1.15).

Last edited by scjet (2014-03-11 20:59:39)

clfarron4 · 2014-03-11 21:52:22

PhotonX wrote:

Recent mesa upgrade to 10.1.0 has broken the entire system some days ago (Xorg terminated immediately after starting). Is it expected that things work properly if upgrading both mesa and catalyst? Don't want to experiment much since reverting the upgrade of catalyst seems to be a bit messy after the splitting of catalyst-utils.

Upgrading Mesa and then upgrading Catalyst seems to be fixed now, in that the last set of updates Vi0L0 has done seems to have fixed the problems.

DarksideEE7 · 2014-03-12 01:19:43

Vi0L0 wrote:

DarksideEE7 wrote:
Vi0L0 wrote:
I recently bought "MSI 290X Gaming" and have this "lag" whenever I'm scrolling text in text editor or scrolling in file manager. In both KDE and GNOME3 (on Gnome it's even more painfull), no matter if compositing is enabled or disabled.
Definitelly something bad is going on with ATI's 2D Acceleration. (...)
I tested with 3 290Xs on 14.2 with a fully updated system and I don't have this. I've been running this setup for a few months now and the only problem I have is %100 CPU usage on a single logical CPU from kwin. This is on 3 monitor portrait, not that it probably matters.
Interesting... do you know what's the manufacturer of memory chips on your gfxes?
I just noticed that the problem of slow 2d Acceleration is gone whenever I start glxgears xD... it bumps clocks, eats more energy and it's not worth it but it is working, LOL.
Lockheed wrote:
Catalyst < 12.10 and Catalyst Legacy do not support xorg-server 1.13.
Do I get this wrong and catalyst-total-hd234k 13.1 still requires xorg 1.12?
You did forget that catalyst-total-hd234k = Catalyst Legacy
scjet wrote:
error: failed to commit transaction (conflicting files)
catalyst-test: /usr/lib/libEGL.so.1.0.0 exists in filesystem
catalyst-test: /usr/lib/libGLESv1_CM.so.1.1.0 exists in filesystem
catalyst-test: /usr/lib/libGLESv2.so.2.0.0 exists in filesystem
catalyst-test: /usr/lib32/libEGL.so.1.0.0 exists in filesystem
catalyst-test: /usr/lib32/libGLESv1_CM.so.1.1.0 exists in filesystem
catalyst-test: /usr/lib32/libGLESv2.so.2.0.0 exists in filesystem
Errors occurred, no packages were upgraded.
Are you sure that you updated mesa before this update? mesa package should be at least in version 10.1.0-2
You may check package owner of a file with (this could help you in many cases):
pacman -Qo /usr/lib/libEGL.so.1.0.0

I don't know which memory ICs I have....my cards are watercooled so I could have checked I guess. There is a memory IC tool that reports what IC you have, but I can't recall the name of the software.

hippieben · 2014-03-12 07:13:46

Hey guys, I'm back on the catalyst driver. Performance just isn't consistent with radeon.

PhotonX · 2014-03-12 09:28:12

@clfarron4: Thanks, upgrading mesa first and then doing a full upgrade as scribed by SteveK worked perfectly.

scjet · 2014-03-12 12:52:52

[SOLVED] -Thankyou

scjet wrote:

Vi0L0 wrote:
scjet wrote:
error: failed to commit transaction (conflicting files)
catalyst-test: /usr/lib/libEGL.so.1.0.0 exists in filesystem
catalyst-test: /usr/lib/libGLESv1_CM.so.1.1.0 exists in filesystem
catalyst-test: /usr/lib/libGLESv2.so.2.0.0 exists in filesystem
catalyst-test: /usr/lib32/libEGL.so.1.0.0 exists in filesystem
catalyst-test: /usr/lib32/libGLESv1_CM.so.1.1.0 exists in filesystem
catalyst-test: /usr/lib32/libGLESv2.so.2.0.0 exists in filesystem
Errors occurred, no packages were upgraded.
Are you sure that you updated mesa before this update? mesa package should be at least in version 10.1.0-2
You may check package owner of a file with (this could help you in many cases):
pacman -Qo /usr/lib/libEGL.so.1.0.0
TY for reply,
right now, a "pacman -Qo /usr/lib/libEGL.so.1.0.0" gives me:
/usr/lib/libEGL.so.1.0.0 is owned by mesa 10.0.3-1
I'm now testing this on a spare Desktop, since whenever I tried previously above, "X' and/or Mesa ? crapped out, due to my attempted changes, and I couldn't even bring up a web browser.
Basically I'm just using the standard repo's : core, community, extra, multilib, and of course AUR, via "yaourt", for catalyst-test.
I'll try it again, when I can, but should I add your [repo], or download/makepkg..., to be able to get your latest mesa ?,
even though, I've usually had good results with just a "yaourt catalyst-test", in the past.
but I think I understand now, why it's doing it, as per other explanations here.
I would try "catalyst-total", but I would prefer to stay with latest Xorg-server-(1.15).

--------------------------------

So, I tried again this morning and "mesa" finally upgraded to
pacman -Ss mesa | grep -i install
-> extra/mesa 10.1.0-2 [installed]
-> multilib/lib32-mesa 10.1.0-2 [installed]

Then, a simple "yaourt catalyst-test", ..., and boom baby, eveything is fine again.

-The only explanation that I can think of is that, I only had a couple (Canada) mirrors UN-commented in mirrorlist,
and for some reason these primary mirrors weren't sync'd up, at that time. the other day ?

anyway, thanks again all, and for putting up with my yaourtness.
----------------------------
[EDIT]: on a minor note, I'm still having these same recent issues, of catalyst-test", with the default "extra/vlc 2.1.4-1" crashing my "X", at times ???
and as a test/comparison, I used "xf86-video-ati" on the same box with the same vlc, and it played the same dvd (audio and video), just fine.

But, as others suggested here, (in VLC with catyalyst-test), I used Video -> "OpenGL GLX Video output (XCB)", and for Audio -> had to point it back to proper audio device...,
and VLC now appears to working fine, so far.

Thanks.

Last edited by scjet (2014-03-12 14:23:33)

Vi0L0 · 2014-03-12 16:31:59

DarksideEE7 wrote:

Vi0L0 wrote:
DarksideEE7 wrote:
I tested with 3 290Xs on 14.2 with a fully updated system and I don't have this. I've been running this setup for a few months now and the only problem I have is %100 CPU usage on a single logical CPU from kwin. This is on 3 monitor portrait, not that it probably matters.
Interesting... do you know what's the manufacturer of memory chips on your gfxes?
I just noticed that the problem of slow 2d Acceleration is gone whenever I start glxgears xD... it bumps clocks, eats more energy and it's not worth it but it is working, LOL.
I don't know which memory ICs I have....my cards are watercooled so I could have checked I guess. There is a memory IC tool that reports what IC you have, but I can't recall the name of the software.

Finding soft for linux which will show this has become a tough task... Anybody seen such a thing?
On windows you can use memory info, hawaiiinfo, or simple GPU-Z

scjet wrote:

But, as others suggested here, (in VLC with catyalyst-test), I used Video -> "OpenGL GLX Video output (XCB)", and for Audio -> had to point it back to proper audio device...,
and VLC now appears to working fine, so far.

Downgrading xorg-server to 1.14 (ie from [xorg114] repo) will solve all problems with xv output.

hippieben · 2014-03-12 17:44:39

What's the difference between catalyst-test and [catalyst]?

Vi0L0 · 2014-03-12 18:42:45

repo contains separated packages, while catalyst-test is 1 package which consists of 3 packages, but not for long. I want catalyst-test to be a splitted package. repo contains additional packages ie for opencl developement.

integrating -pxp into regular catalyst package
I've been thinking about moving powerXpress functionality into catalyst-libgl package. Thanks to Arch devs and their work on moving libgl.so into mesa-libgl.so and libglx.so into libglx.xorg (thanks [1] I found it so quickly ) we no longer need to modify LD_LIBRARY_PATH and xorgs ModulePath. We can do this by simple symlinks change.
catalyst-libgl would come with 3 additional files - 3 scripts - 2 of them (switchlibGL and switchlibglx) are needed because aticonfig is calling them and one (pxp_switch_catalyst) is mine, created to help users. Scripts are only changing the targets of symlinks:
- libGL.so could point to fglrx-libGL.so or mesa-libGL.so
- libglx.so could point to libglx.fglrx or libglx.xorg
depending on users choice.
Edit: It won't change a thing for non-pxp users, scripts are not used in PKGBUILD or .install files.
Now because intel-dri depends on mesa-libgl and catalyst-libgl is in conflict with mesa-libgl, catalyst-libgl would have to provide mesa-libgl. And it won't be a lie, because after running `pxp_switch_catalyst intel` catalyst-libgl would point to mesa libs in just the same way as mesa-libgl is.
Scripts won't create new files, so for pacman everything will be fine.
There's only one disadvantage - users won't be able to switch from regular mesa-libgl to mesa-libgl-git (from [mesa-git] repo) easily. They are able to do this with current -pxp packages, but it won't be that easy with catalyst-libgl. Because while catalyst-libgl could provide mesa-libgl with no problems, problems could appear if catalyst-libgl would provide both mesa-libgl and mesa-libgl-git. Because mesa-libgl-git could point to mesa-git libs in newer versions than regular mesa provides (i don't know how often mesa devs are bumping libs versions).
Creating additional package "catalyst-libgl-git" which would provide mesa-libgl-git would solve this. But then someone would have to monitor mesa-libgl-git ...
Anyhow it sounds good for me, it's saving my time on building -pxp packages and servers disk space and is making catalysts packages more "consistent, coherent". Edit: also new solution is not messing in systems configuration like current -pxp packages do.
Edit: I found one other disadvantage: after every catalyst-libgl update it would point to catalyst libs, so if you were using intel you would have to run `pxp_switch_catalyst intel`.
What do you think about it?
Because I never had hardware with pxp support I'm not able to test it. I can only say that switching between catalyst and radeon works fine.
You can take a look at the source here. I uploaded it yesterday and need to add replaces=('mesa-libgl') but other than this it should be fine.

[1] put here whoever/whatever you believe

Last edited by Vi0L0 (2014-03-12 19:52:11)

Alexander · 2014-03-12 22:51:27

Hi everybody!
May you help me? I have the kernel version 3.13.6-1 , xorg 1.14.5-11 and catalyst-utils 13.12-4. When I try to change the brightness using fn-keys, a problem appears: my computer becomes too slow and i can't turn it off. And when the notebook plugged in, the temperature of the graphic card increases to 70-73 oC, but normally it should be 43-45. Please give me some tip. Should I downgrade my driver?

Last edited by Alexander (2014-03-12 22:58:00)

clfarron4 · 2014-03-13 14:48:11

Alexander wrote:

Hi everybody!
May you help me? I have the kernel version 3.13.6-1 , xorg 1.14.5-11 and catalyst-utils 13.12-4. When I try to change the brightness using fn-keys, a problem appears: my computer becomes too slow and i can't turn it off. And when the notebook plugged in, the temperature of the graphic card increases to 70-73 oC, but normally it should be 43-45. Please give me some tip. Should I downgrade my driver?

Try different combinations of kernels and drivers and report what works.

Also, what card(s) are you using?

Arch Linux

#6351 2014-03-10 20:11:01

Re: The AMD/ATI Bar & Grill

#6352 2014-03-10 20:15:05

Re: The AMD/ATI Bar & Grill

#6353 2014-03-10 20:16:20

Re: The AMD/ATI Bar & Grill

#6354 2014-03-10 20:17:36

Re: The AMD/ATI Bar & Grill

#6355 2014-03-10 22:05:41

Re: The AMD/ATI Bar & Grill

#6356 2014-03-10 22:13:42

Re: The AMD/ATI Bar & Grill

#6357 2014-03-10 22:17:34

Re: The AMD/ATI Bar & Grill

#6358 2014-03-11 00:41:21

Re: The AMD/ATI Bar & Grill

#6359 2014-03-11 06:15:35

Re: The AMD/ATI Bar & Grill

#6360 2014-03-11 11:53:53

Re: The AMD/ATI Bar & Grill

#6361 2014-03-11 17:35:17

Re: The AMD/ATI Bar & Grill

#6362 2014-03-11 18:50:06

Re: The AMD/ATI Bar & Grill

#6363 2014-03-11 19:14:10

Re: The AMD/ATI Bar & Grill

#6364 2014-03-11 20:24:11

Re: The AMD/ATI Bar & Grill

#6365 2014-03-11 20:50:40

Re: The AMD/ATI Bar & Grill

#6366 2014-03-11 21:52:22

Re: The AMD/ATI Bar & Grill

#6367 2014-03-12 01:19:43

Re: The AMD/ATI Bar & Grill

#6368 2014-03-12 07:13:46

Re: The AMD/ATI Bar & Grill

#6369 2014-03-12 09:28:12

Re: The AMD/ATI Bar & Grill

#6370 2014-03-12 12:52:52

Re: The AMD/ATI Bar & Grill

#6371 2014-03-12 16:31:59

Re: The AMD/ATI Bar & Grill

#6372 2014-03-12 17:44:39

Re: The AMD/ATI Bar & Grill

#6373 2014-03-12 18:42:45

Re: The AMD/ATI Bar & Grill

#6374 2014-03-12 22:51:27

Re: The AMD/ATI Bar & Grill

#6375 2014-03-13 14:48:11

Re: The AMD/ATI Bar & Grill

Board footer