Package Details: opencl-amd 1:6.1.1-1

Git Clone URL: https://aur.archlinux.org/opencl-amd.git (read-only, click to copy)
Package Base: opencl-amd
Description: ROCm components repackaged from AMD's Ubuntu releases (ROCr runtime, ROCm runtime, HIP runtime) - 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: amd-smi-lib, 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, rocdecode, rocdecode-dev, 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-icd-loader, rocm-opencl-runtime, rocm-smi-lib, rocm-utils, rocminfo, rocprofiler, rocprofiler-dev, rocprofiler-plugins, rocprofiler-register, roctracer, roctracer-dev
Provides: amd-smi-lib, 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, rocdecode, rocdecode-dev, 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-icd-loader, rocm-opencl-runtime, rocm-smi-lib, rocm-utils, rocminfo, rocprofiler, rocprofiler-dev, rocprofiler-plugins, rocprofiler-register, roctracer, roctracer-dev
Submitter: grmat
Maintainer: sperg512 (luciddream)
Last Packager: luciddream
Votes: 131
Popularity: 0.66
First Submitted: 2016-12-01 03:45 (UTC)
Last Updated: 2024-05-09 21:58 (UTC)

Required by (114)

Sources (39)

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-05-09 22:00 (UTC) by luciddream)

Current release is for ROCm 6.1.1 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 .. 8 9 10 11 12 13 14 15 16 17 18 .. 77 Next › Last »

luciddream commented on 2022-11-30 22:57 (UTC)

Busy week again, I will make the new release tomorrow night. I will also change the release numbering to 5.4.0 although I still don't trust AMD about it.

magicgoose commented on 2022-11-11 11:42 (UTC)

Pinned comment advises to install opencl-amd-polaris, but there's no such package - I only get 404 error page. What happened to it and is there an alternative?

<deleted-account> commented on 2022-10-23 17:08 (UTC)

Since using Linux 6.0 I run into the problem of

dlerror: libamdocl-orca64.so: cannot open shared object file: No such file or directory
Segmentation fault (core dumped)

A quick find also didn't return anything for it.

EDIT: Seems like I need the legacy support. Downgrading solved my issue :-)

wsippel commented on 2022-10-07 13:09 (UTC)

I tested and verified my suspicion: If you want to use the Arch Blender package with HIP, you need amd-opencl-dev. It will then compile the kernel at runtime - takes a minute the first time you use it.

@apaz Maybe a stupid suggestion, but if the card is recognized and there are no errors or crashes, are you sure you actually selected the GPU as your compute device? Blender will still default to the CPU even with HIP enabled, unless you specifically select 'GPU Compute' in 'Render Properties' -> 'Scene' -> 'Device'.

apaz commented on 2022-10-04 16:34 (UTC)

@luciddream @wsippel I too use the Blender.org binary, both version 3.3 since it was in development and 3.4 which is now in development. I must have something wrong with my system because the board is recognized and there are no errors, but the rendering is done by the CPU alone. I will try to investigate...

magicgoose commented on 2022-10-03 13:52 (UTC)

@luciddream RX 590 so your theory must be correct

luciddream commented on 2022-10-03 09:48 (UTC)

@AndyRTR If I'm not wrong RX460 is using the legacy driver which is broken in this release. So either revert to the previous release or wait for an AMD fix.

@wsippel no, I just forgot to comment it out, I actually had to spend a lot of time with opencl-amd-dev because of the changes in the archive files, and I was too tired after. I don't think it's a problem though.

wsippel commented on 2022-10-03 08:39 (UTC)

@luciddream I don't know if it's really hurting anything, but is there a reason you create amdocl-orca64.icd, considering it's not actually included in this release?

AndyRTR commented on 2022-10-03 08:35 (UTC)

I can confirm the darktable segfault with latest opencl driver. My card is a RX460.

luciddream commented on 2022-10-03 07:38 (UTC)

@magicgoose what GPU do you have? I didn't try darktable to be honest with latest opencl-amd. I will try to do it this tonight. It doesn't always mean it's a driver problem though, sometimes the applications need to change some code in order to be compatible. AMD also forgot to upload legacy proprietary drivers for opencl, so if you have an older GPU you will have to wait for a new release I'm afraid. I usually don't upgrade to versions that are "broken" like this, but with these slow updates that AMD is providing it's better to have something than nothing.