Package Details: opencl-amd 1:6.0.2-1

Git Clone URL: https://aur.archlinux.org/opencl-amd.git (read-only, click to copy)
Package Base: opencl-amd
Description: ROCr OpenCL stack, supports Vega 10 and later products - Legacy OpenCL stack (Proprietary), supports legacy products older than Vega 10 - This package is intended to work along with the free amdgpu stack.
Upstream URL: http://www.amd.com
Keywords: amd amdgpu computing gpgpu opencl radeon
Licenses: custom:AMD
Conflicts: comgr, hip, hip-dev, hip-doc, hip-runtime-amd, hip-samples, hipcc, hsa-amd-aqlprofile, hsa-rocr, hsa-rocr-dev, hsakmt-roct, hsakmt-roct-dev, libdrm-amdgpu-amdgpu1, openmp-extras-runtime, rocm-clang-ocl, rocm-cmake, rocm-core, rocm-dbgapi, rocm-debug-agent, rocm-device-libs, rocm-gdb, rocm-hip-runtime, rocm-language-runtime, rocm-ocl-icd, rocm-opencl, rocm-opencl-dev, rocm-opencl-runtime, rocm-smi-lib, rocm-utils, rocminfo, rocprofiler, rocprofiler-dev, rocprofiler-plugins, roctracer, roctracer-dev
Provides: comgr, hip, hip-dev, hip-doc, hip-runtime-amd, hip-samples, hipcc, hsa-amd-aqlprofile, hsa-rocr, hsa-rocr-dev, hsakmt-roct, hsakmt-roct-dev, libdrm-amdgpu-amdgpu1, opencl-driver, openmp-extras-runtime, rocm-clang-ocl, rocm-cmake, rocm-core, rocm-dbgapi, rocm-debug-agent, rocm-device-libs, rocm-gdb, rocm-hip-runtime, rocm-language-runtime, rocm-ocl-icd, rocm-opencl, rocm-opencl-dev, rocm-opencl-runtime, rocm-smi-lib, rocm-utils, rocminfo, rocprofiler, rocprofiler-dev, rocprofiler-plugins, roctracer, roctracer-dev
Submitter: grmat
Maintainer: sperg512 (luciddream)
Last Packager: luciddream
Votes: 131
Popularity: 0.076405
First Submitted: 2016-12-01 03:45 (UTC)
Last Updated: 2024-02-02 22:43 (UTC)

Required by (109)

Sources (35)

Pinned Comments

nho1ix commented on 2023-12-29 08:43 (UTC) (edited on 2024-02-10 07:13 (UTC) by nho1ix)

Note for anyone who has a Polaris GPU (Radeon RX 5xx) debugging issues with this package; Packages that use OpenCL like clinfo or davinci-resolve-studio will need you to downgrade opencl-amd to 1:5.7.1-1 as well as amdgpu-pro-oglp to 23.10_1620044-1 to avoid coredumps & segfaults.

DVR would not open unless these 2 packages were downgraded (along with their dependencies). Had to figure it out the hard way after hours using valgrind and rebooting over and over. Hopefully someone else will not have to pull their hair out trying to resolve their issue.

luciddream commented on 2021-12-26 15:14 (UTC) (edited on 2024-02-02 22:44 (UTC) by luciddream)

Current release is for ROCm 6.0.2 opencl-amd package includes only OpenCL / HIP runtime. You also need to use opencl-amd-dev package for ROCm LLVM compiler, OpenCL and HIP SDK. Please relog / reboot after installing so your PATH gets updated

There are now official packages available: rocm-opencl-sdk for OpenCL and rocm-hip-sdk for HIP - You might have better luck with these packages depending on your GPU.

Latest Comments

« First ‹ Previous 1 .. 5 6 7 8 9 10 11 12 13 14 15 .. 76 Next › Last »

luciddream commented on 2023-02-12 18:07 (UTC)

@blueman I'm not sure, I've never used it, and I don't plan to use it at the moment. I will still keep updating opencl-amd for whomever needs to use it. But it's good to have more options.

@merlock yeah, as I commented on the sticky comment legacy support is broken for this release (as usual). Stick to 5.4.1 for now.

merlock commented on 2023-02-12 13:56 (UTC)

Folding at home won't start GPU folding with 5.4.3.

I guess it doesn't make any sense to test/try the community repo.

blueman commented on 2023-02-12 13:50 (UTC)

Thanks for all your hard work @luciddream!

Are the correct steps to replace this package with all rocm-* packages from community repo or is there anything special required?

luciddream commented on 2023-02-12 12:39 (UTC)

I've updated the package to 5.4.3. I also noticed that ROCm is now on the community repository, so I make this comment as a reminder that people might want to switch to the official repository instead of using opencl-amd pacakge.

luciddream commented on 2023-02-07 21:45 (UTC)

5.4.3 is out with really tiny changes. I will probably make a new release on the weekend.

wsippel commented on 2023-01-19 21:53 (UTC)

@Mushoz I'm not sure those few patches are all that's needed, gfx11 hasn't been added to the main makefile yet as far as I can tell for example. I don't think there's any harm in trying though, but I can't even figure out how to compile it (tpkessler's official packages don't seem to include all the files required to build MIOpen). That said, it looks like ROCm 5.5 shouldn't be too far off, anyway - minor updates get released every two to four months, and 5.4 came out in November. Early February would be my guess. That's also the due date for the 5.5 milestone in the MIOpen repo.

Mushoz commented on 2023-01-19 15:51 (UTC)

Slightly offtopic, so my apologies. @wsippel a week ago RDNA3 changes were merged for MIOpen: https://github.com/ROCmSoftwarePlatform/MIOpen/commits/develop

See the 11th of January.

Do you reckon we could build MIOpen from source and get tensorflow to work? Or do we need more in order to get RDNA3 to finally run Tensorflow and Pytorch?

luciddream commented on 2023-01-16 16:32 (UTC)

And I'm not sure @luciddream will still maintain this package by then, considering there are official Arch packages in testing now. So thank you for all the hard work man, it's really appreciated!

I'll probably keep updating it as long as I have an AMD GPU, even if it's meant as a backup to the official packages. So no worries about that :)

wsippel commented on 2023-01-15 21:54 (UTC)

I thought 5.4.2 might contain fixes for RDNA3 cards, but what didn't work on 5.4.1 doesn't seem to work on 5.4.2, either - namely MIOpen, and therefore Torch and Tensorflow. That will have to wait until 5.5. And I'm not sure @luciddream will still maintain this package by then, considering there are official Arch packages in testing now. So thank you for all the hard work man, it's really appreciated!

luciddream commented on 2023-01-14 16:03 (UTC)

Hi all, unless I'm missing something important, I'm going to skip 5.4.2 since there is no changes and I see no point in forcing users to update for no reason.