Package Details: opencl-amdgpu-pro-pal 20.20_1098277-2

Git Clone URL: https://aur.archlinux.org/amdgpu-pro-installer.git (read-only, click to copy)
Package Base: amdgpu-pro-installer
Description: AMDGPU Pro OpenCL driver PAL
Upstream URL: https://www.amd.com/en/support/kb/release-notes/rn-amdgpu-unified-linux-20-20
Licenses: custom: AMDGPU-PRO EULA
Groups: Radeon_Software_for_Linux
Provides: opencl-driver
Submitter: LEW21
Maintainer: Ashark
Last Packager: Ashark
Votes: 92
Popularity: 2.29
First Submitted: 2016-03-28 22:44
Last Updated: 2020-07-30 09:42

Dependencies (3)

Required by (23)

Sources (1)

Pinned Comments

Ashark commented on 2019-12-09 20:52

PKGBUILD generator is located here: https://github.com/Ashark/archlinux-amdgpu-pro

AMDGPU PRO wiki page: https://wiki.archlinux.org/index.php/AMDGPU_PRO

Latest Comments

1 2 3 4 5 6 ... Next › Last »

ganthore commented on 2020-07-30 04:28

@gardotd426 ...aaaand I now I finally understand the root of the problem per your criticism. Seriously, I was like "WAT, I read the comments, what's he on about??"

Anyway, my initial Google search for amdgpu-pro-installer dropped me on page 5 of the comments for some silly reason. That shows me for trusting stuff on the first click.

ganthore commented on 2020-07-30 04:15

@gardotd426 I did read prior comments. This response was specifically aimed at the very recent 20.20 upgrade, not older versions where people tried to force upgrades by manually editing the PKGBUILD to stuff pre 20.20. Note that the last 19.30* stuff was working fine.

By working fine, I mean Davinci Reslove still worked. Gutting this entire stack and attempting to run off the opencl-amdgpu package results in instant crashing.

For now, I'm just reverting to 370d39c63ddc using the 19.30* stuff so I can continue editing videos.

gardotd426 commented on 2020-07-29 08:29

Lord, I looked into debtap, and it's a complete dumpster fire unless you're just flat converting .debs. Using it to create PKGBUILDs is a nightmare, it'll flat-out fail if the package doesn't contain a ./usr/bin directory (so if it's a package without any binaries, like a lib package, or something that goes in /opt or /etc), because of the way they wrote the script.

Someone filed a bug report on the github for it, and the dude didn't read it, said "if you don't have a /usr/bin, your installation is broken, you need to reinstall," and closed the issue - seriously. When it's actually the script itself that's broken.

That sucks, I was super excited to find a script that would create PKGBUILDs from .deb packages. It does seem to work fine for flat-out conversion from .deb to .pkg.tar though, so there's that.

gardotd426 commented on 2020-07-29 05:58

@Ashark

"It was because of strange behavior of debtap. Previously, there was libgcc1 dependency, which was converted to None by debtap. But current version has libgcc-s1 dependency, which is converted to gcc by debtap."

Yeah I've always used dpkg-deb -c instead of debtap, it doesn't pull dependencies, and it takes more work, but it also doesn't cause broken stuff to get added. I just run dpkg-deb -c package.deb and get a list of the file list, then in the PKGBUILD I have the command to move those to the .pkg, and figure out the dependencies some other way. Unfortunately there's no real good solution, I wish we had better dependency conversion tools/databases, where you could search for a dependency on Debian/Ubuntu and find it's alternative on Arch or wherever else.

gardotd426 commented on 2020-07-29 05:52

@ganthore read the previous comments before posting, please.

Both of your issues have already been discussed.

The dependencies missing are an error, they're not supposed to be in the PKGBUILD, and you can't use the full AMDGPU PRO stack on Arch Linux anyway, only the standalone bits (so the OpenCL driver, the vulkan drivers, etc., but not the libgl driver or the full stack).

ganthore commented on 2020-07-29 03:36

libgl1 and lib32-gcc have no deps available in aur and results with the following error before installation:

❯ makepkg -si --skippgpcheck --skipchecksums --nocheck --ignorearch ==> WARNING: The package group has already been built, installing existing packages... ==> Installing amdgpu-pro-installer package group with pacman -U... loading packages... resolving dependencies... warning: cannot resolve "libgl1", a dependency of "amf-amdgpu-pro" warning: cannot resolve "lib32-gcc", a dependency of "lib32-amdgpu-pro-libgl" warning: cannot resolve "lib32-gcc", a dependency of "lib32-opencl-amdgpu-pro-orca" warning: cannot resolve "lib32-gcc", a dependency of "lib32-vulkan-amdgpu-pro" :: The following packages cannot be upgraded due to unresolvable dependencies: amf-amdgpu-pro lib32-amdgpu-pro-libgl lib32-opencl-amdgpu-pro-orca lib32-vulkan-amdgpu-pro

I'm also noticing a black screen after force upgrading. I expect SDDM to load. Using an RX580. Removing the packages allows SDDM to load correctly.

apaz commented on 2020-07-28 14:14

"DaVinci Resolve doesn't work with just the OpenCL driver? I wasn't aware it required the OpenGL driver as well."

DaVinci Resolve needs his specific OpenGL profile (under license?). This is only present in amdgpu-pro and not in amdgpu.

Ashark commented on 2020-07-28 13:25

It's just a matter of removing lib32-gcc from the dependencies

I have also noticed, that it has some mess with detecting hwe vs non-hwe version, so I should fix that as well.

I'm not sure why it was added, it wasn't there before.

It was because of strange behavior of debtap. Previously, there was libgcc1 dependency, which was converted to None by debtap. But current version has libgcc-s1 dependency, which is converted to gcc by debtap.

gardotd426 commented on 2020-07-28 02:39

@kode54 I actually tried that a while back, wouldn't work, but you'd think it would. It might be because I didn't install the full stack and just the libgl, vulkan, and opencl components.

I wish there was a way to make the full stack work on Arch, but it seems like it's just flat-out incompatible, which is rare to find (though usually when you do find it, it's proprietary).

kode54 commented on 2020-07-28 00:02

In that case, a dirty trick you can do, if you're feeling particularly nutty:

You can log into your desktop environment, then install the amdgpu pro libgl packages, and then all successively launched apps will use those libgl drivers.

You then have to remove them before you can log back into another session, or before you restart your desktop manager, if you use one.