Package Details: opencl-amd 1:6.3.2-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, libdrm-amdgpu-amdgpu1, openmp-extras-runtime, rocdecode, rocdecode-dev, rocjpeg, rocjpeg-dev, 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, libdrm-amdgpu-amdgpu1, opencl-driver, openmp-extras-runtime, rocdecode, rocdecode-dev, rocjpeg, rocjpeg-dev, 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: 132
Popularity: 0.21
First Submitted: 2016-12-01 03:45 (UTC)
Last Updated: 2025-01-29 20:12 (UTC)

Required by (128)

Sources (38)

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 2025-01-29 20:13 (UTC) by luciddream)

Current release is for ROCm 6.3.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 .. 48 49 50 51 52 53 54 55 56 57 58 .. 79 Next › Last »

luciddream commented on 2020-11-20 11:10 (UTC) (edited on 2020-11-20 11:11 (UTC) by luciddream)

@coxackie I'm not sure where you get that extension from. Can you try to remove opencl-mesa and then reinstall opencl-amd package - if you haven't tried that in that order? My platform does not have the offline extension.

Number of platforms                               1
  Platform Name                                   AMD Accelerated Parallel Processing
  Platform Vendor                                 Advanced Micro Devices, Inc.
  Platform Version                                OpenCL 2.0 AMD-APP (3188.4)
  Platform Profile                                FULL_PROFILE
  Platform Extensions                             cl_khr_icd cl_amd_event_callback 
  Platform Extensions function suffix             AMD

coxackie commented on 2020-11-20 10:57 (UTC) (edited on 2020-11-20 11:02 (UTC) by coxackie)

@luciddream Thanks - I tried AMD's clinfo, but there was no illuminating info. I then checked the output of clinfo --offline (arch clinfo package - showing all potential supported devices), and I got this. Looking through the platforms, it appears that Navi is not supported? (Presumably I should see gfx1010 somewhere there? But nowhere to be found). This looks like the same issue that opencl-mesa has.

Of course, the AMD webpage does mention support. I have all requirements - llvm 11, kernel 5.9.9, mesa 20.2.2.

Could anyone else check the output of their clinfo --offline?

luciddream commented on 2020-11-20 10:48 (UTC) (edited on 2020-11-20 10:56 (UTC) by luciddream)

opencl-amd follows the AMDGPU-Pro upstream releases. If the latest version is not working for your system, you can download and install the 20.40 version. The link to the 20.40 PKGBUILD is here

From AMDGPU-Pro 20.45 release notes - Blender 2.90.1 users may experience page faults (details in dmesg log).

luciddream commented on 2020-11-20 10:18 (UTC) (edited on 2020-11-20 10:24 (UTC) by luciddream)

hey guys, we must be in different timezones because I'm usually sleeping when the batch of these emails arrive :D

Blender is not a good example to test the package, since it's a known bug of the driver. Of course it might work for some people but we are just packaging the drivers, we can't fix them. Maybe we can add a warning to the pinned comment @sperg512

@sperg512 about clinfo, both have similar output from what I can see, and both are open source. Arch upstream - AMD clinfo - I'm neutral on what to choose, but Arch one seems more active.

@apaz you can download it from here, then add it from Blender as a zip addon. I'm not sure if it worked with the previous AMDGPU-pro version, that's why I downloaded it. You will also have to configure it because the original configuration is fast but not so good. The manual is here

@coxackie can you also try the clinfo from AMD and see if it gives any meaningful errors? I've uploaded for you here

coxackie commented on 2020-11-20 08:51 (UTC)

so, yeah. For 5700:

On one hand, opencl-mesa does work; clinfo gives:

fatal error: cannot open file '/usr/lib/clc/gfx1010-amdgcn-mesa-mesa3d.bc': No such file or directory

On the other hand, the latest version 20.45 of opencl-amd also does not discover the card. I tried quite a lot, but I will just stick with 20.40 for the foreseeable future, as it seems to be the only one working. I am quite puzzled as to how 5700XT appears to have no problems. Is there some dependency I am missing?

undu commented on 2020-11-20 08:49 (UTC)

Using a Radeon R9 Nano here, trying to load the scene crashes blender immediatly. I can make blender crash by going into options and clicking on the OpenCL tab inside System, this produces a logand more information, fortunately.

https://paste.debian.net/1173564/

I'll have more time later in the day so I hope I can dig deeper into the meaning of the crash

apaz commented on 2020-11-20 08:12 (UTC)

@luciddream Excuse the OT, but I wanted to ask you how you made RadeonPro Render work in Blender. Is there an installation guide? (I'm referring to the images you posted in the commentary 2020-11-19 14:16)

apaz commented on 2020-11-20 08:11 (UTC)

@Recompiler You can try to contact Bridgman on the Phoronix forum; he is one of the developers of ROCm and sometimes intervenes on the forum. The thread is as follows: https://www.phoronix.com/scan.php?page=article&item=amd-rx6800-opencl&num=1

An example of an answer from him: "Question: then for having opencl driver the 5000 amd wait a year, nice and to use this we need the closed driver? They already resolve the hangs in navi cards or Iwill need to wait another year?

Answer: We did the OpenCL-over-ROCR work for 5000 and 6000 series in parallel, although in the last couple of weeks before launch we prioritized the 6000 issues since the 5000 series already had OpenCL support via the PAL paths. AFAIK we managed to resolve nearly all of the 5000 series issues as well - I'm not sure if we are going to recommend cutting over to ROCR back end for Navi1x in the 20.45 release or wait until the subsequent release."

merlock commented on 2020-11-20 06:14 (UTC)

I think I did this right.

Downloaded from https://cloud.blender.org/p/gallery/5dd6d7044441651fa3decb56.

Opened in blender. First run I think used the CPU, and it rendered fine. Figured out how to set it to use the GPU/OpenCL...not so fine.

No coredump, but after seeing no advance on the timer, I escaped out of blender, and this was in the journal:

http://ix.io/2EMg

sperg512 commented on 2020-11-20 05:53 (UTC)

@merlock You pretty much just pacman -S blender, download the scene, then open it. Should automatically open in Blender. If it doesn't try running blender <junk shop scene filename>.scene and find any relevant output (segfaults, etc)

« First ‹ Previous 1 .. 48 49 50 51 52 53 54 55 56 57 58 .. 79 Next › Last »