You are not logged in.
- Topics: Active | Unanswered
#1 2017-12-06 15:53:42
- greenbigfrog
- Member
- Registered: 2017-12-06
- Posts: 33
Can't get OpenCL to work on OS stack with vega 56
Hi!
I'm unable to get OpenCL to work with my vega 56.
Gonna list below what I'm running with versions (none, is latest from AUR):
- linux-mainline: Linux isdumb 4.15.0-rc2-mainline #1 SMP PREEMPT Tue Dec 5 19:36:13 CET 2017 x86_64 GNU/Linux
- mesa-git
- llvm-svn
- opencl-amd
Also made sure the PCIe slot is running at x16 and everything latest gen.
$ clinfo
Number of platforms 0Card is working nicely besides the lack of OpenCL.
Not sure how to proceed here. Kind of out of ideas. Any ideas?
Offline
#2 2017-12-08 11:36:37
- greenbigfrog
- Member
- Registered: 2017-12-06
- Posts: 33
Re: Can't get OpenCL to work on OS stack with vega 56
I've been wondering if there might be some leftovers somewhere, from when I had a nvidia gfx card installed.
Offline
#3 2017-12-08 13:31:29
- Lone_Wolf
- Administrator
- From: Netherlands, Europe
- Registered: 2005-10-04
- Posts: 13,096
Re: Can't get OpenCL to work on OS stack with vega 56
for testing purpose remove opencl-amd and install opencl-mesa-git (if you run my aur mesa-git package you only need to remove opencl-amd) .
post output of clinfo
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
#4 2017-12-10 16:24:08
- greenbigfrog
- Member
- Registered: 2017-12-06
- Posts: 33
Re: Can't get OpenCL to work on OS stack with vega 56
So I removed opencl-amd and rebooted (since I'm using the mesa-git package). Output of clinfo is still the same.
$ clinfo
Number of platforms 0Offline
#5 2017-12-10 17:03:23
- Lone_Wolf
- Administrator
- From: Netherlands, Europe
- Registered: 2005-10-04
- Posts: 13,096
Re: Can't get OpenCL to work on OS stack with vega 56
That indicates a problem with the opencl setup, as clover should be listed as a platform (likely without any usable devices).
post pacman -Qs opencl output, ls -l /etc/OpenCL/vendors , dmesg and/or journalctl -b , xorg log .
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
#6 2017-12-10 17:10:52
- greenbigfrog
- Member
- Registered: 2017-12-06
- Posts: 33
Re: Can't get OpenCL to work on OS stack with vega 56
$ pacman -Qs opencl
local/clinfo-git 2.2.17.10.25.r0.g2eb26fc-1
Print all known information about all available OpenCL platforms and devices in the system
local/lib32-ocl-icd 2.2.11-1
OpenCL ICD Bindings (32-bit)
local/lib32-opencl-nvidia 387.34-1
OpenCL implemention for NVIDIA (32-bit)
local/libclc 0.2.0+374+0c31bd5-1
Library requirements of the OpenCL C programming language
local/mesa-git 17.4.0_devel.97255.529cdce799-1
an open-source implementation of the OpenGL specification, git version
local/ocl-icd 2.2.11-1
OpenCL ICD Bindings
local/opencl-headers 2:2.2.20170516-1
OpenCL (Open Computing Language) header files
local/opencl-nvidia 387.34-1
OpenCL implemention for NVIDIA$ ls -l /etc/OpenCL/vendors
total 8
-rw-r--r-- 1 root root 19 Nov 2 19:20 mesa.icd
-rw-r--r-- 1 root root 22 Nov 25 03:34 nvidia.icddmesg: https://gist.github.com/greenbigfrog/af … 3da8ac6d62
$ journalctl -b
Hint: You are currently not seeing messages from other users and the system.
Users in groups 'adm', 'systemd-journal', 'wheel' can see all messages.
Pass -q to turn off this notice.
-- Logs begin at Tue 2017-06-13 16:35:31 CEST, end at Sun 2017-12-10 18:03:50 CET. --
Dec 10 17:22:00 isdumb systemd[904]: Listening on GnuPG cryptographic agent (ssh-agent emulation).
Dec 10 17:22:00 isdumb systemd[904]: Reached target Timers.
Dec 10 17:22:00 isdumb systemd[904]: Listening on GnuPG cryptographic agent and passphrase cache (restricted).
Dec 10 17:22:00 isdumb systemd[904]: Listening on Sound System.
Dec 10 17:22:00 isdumb systemd[904]: Reached target Paths.
Dec 10 17:22:00 isdumb systemd[904]: Listening on GnuPG cryptographic agent and passphrase cache.
Dec 10 17:22:00 isdumb systemd[904]: Listening on GnuPG cryptographic agent and passphrase cache (access for web browsers).
Dec 10 17:22:00 isdumb systemd[904]: Starting D-Bus User Message Bus Socket.
Dec 10 17:22:00 isdumb systemd[904]: Listening on GnuPG network certificate management daemon.
Dec 10 17:22:00 isdumb systemd[904]: Listening on D-Bus User Message Bus Socket.
Dec 10 17:22:00 isdumb systemd[904]: Reached target Sockets.
Dec 10 17:22:00 isdumb systemd[904]: Reached target Basic System.
Dec 10 17:22:00 isdumb systemd[904]: Starting Update XDG user dir configuration...
Dec 10 17:22:00 isdumb systemd[904]: Started Update XDG user dir configuration.
Dec 10 17:22:00 isdumb systemd[904]: Reached target Default.
Dec 10 17:22:00 isdumb systemd[904]: Startup finished in 84ms.
Dec 10 17:22:01 isdumb systemd[904]: Started D-Bus User Message Bus.
Dec 10 17:22:01 isdumb dbus-daemon[954]: [session uid=1000 pid=954] Successfully activated service 'org.freedesktop.systemd1'
Dec 10 17:22:02 isdumb dbus-daemon[954]: [session uid=1000 pid=954] Activating service name='org.xfce.Xfconf' requested by ':1.2' (uid=1000 pid=984 comm="thunar --daemon ")
Dec 10 17:22:02 isdumb dbus-daemon[954]: [session uid=1000 pid=954] Successfully activated service 'org.xfce.Xfconf'
Dec 10 17:22:02 isdumb dbus-daemon[954]: [session uid=1000 pid=954] Activating via systemd: service name='org.gtk.vfs.Daemon' unit='gvfs-daemon.service' requested by ':1.4' (uid=1000 pid=978 comm="termite -e weechat --class=Weechat ")
Dec 10 17:22:02 isdumb systemd[904]: Starting Virtual filesystem service...
Dec 10 17:22:02 isdumb dbus-daemon[954]: [session uid=1000 pid=954] Successfully activated service 'org.gtk.vfs.Daemon'
Dec 10 17:22:02 isdumb systemd[904]: Started Virtual filesystem service.
Dec 10 17:22:02 isdumb dbus-daemon[954]: [session uid=1000 pid=954] Activating via systemd: service name='org.a11y.Bus' unit='at-spi-dbus-bus.service' requested by ':1.9' (uid=1000 pid=978 comm="termite -e weechat --class=Weechat ")
Dec 10 17:22:02 isdumb systemd[904]: Starting Accessibility services bus...
Dec 10 17:22:02 isdumb dbus-daemon[954]: [session uid=1000 pid=954] Successfully activated service 'org.a11y.Bus'
Dec 10 17:22:02 isdumb systemd[904]: Started Accessibility services bus.
Dec 10 17:22:02 isdumb at-spi-bus-launcher[1089]: dbus-daemon[1096]: Activating service name='org.a11y.atspi.Registry' requested by ':1.0' (uid=1000 pid=978 comm="termite -e weechat --class=Weechat ")
Dec 10 17:22:02 isdumb at-spi-bus-launcher[1089]: dbus-daemon[1096]: Successfully activated service 'org.a11y.atspi.Registry'
Dec 10 17:22:02 isdumb at-spi-bus-launcher[1089]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry
Dec 10 17:22:03 isdumb systemd[904]: Starting Sound Service...
Dec 10 17:22:05 isdumb systemd[904]: Started Sound Service.
Dec 10 17:22:28 isdumb dbus-daemon[954]: [session uid=1000 pid=954] Activating service name='org.gnome.GConf' requested by ':1.30' (uid=1000 pid=980 comm="/usr/lib/thunderbird/thunderbird ")
Dec 10 17:22:28 isdumb dbus-daemon[954]: [session uid=1000 pid=954] Successfully activated service 'org.gnome.GConf'
Dec 10 17:24:27 isdumb sudo[2776]: pam_unix(sudo:auth): conversation failed
Dec 10 17:24:27 isdumb sudo[2776]: pam_unix(sudo:auth): auth could not identify password for [frog]
Dec 10 17:30:22 isdumb dbus-daemon[954]: [session uid=1000 pid=954] Reloaded configuration
Dec 10 17:30:22 isdumb dbus-daemon[954]: [session uid=1000 pid=954] Reloaded configuration
Dec 10 17:30:22 isdumb dbus-daemon[954]: [session uid=1000 pid=954] Reloaded configuration
Dec 10 17:30:22 isdumb dbus-daemon[954]: [session uid=1000 pid=954] Reloaded configuration
Dec 10 17:33:35 isdumb sudo[17640]: pam_unix(sudo:auth): authentication failure; logname= uid=1000 euid=0 tty=/dev/pts/3 ruser=frog rhost= user=frog
Dec 10 18:01:41 isdumb dbus-daemon[954]: [session uid=1000 pid=954] Activating service name='org.freedesktop.Notifications' requested by ':1.52' (uid=1000 pid=21808 comm="./MEGAsync/src/MEGASync/megasync ")
Dec 10 18:01:41 isdumb org.freedesktop.Notifications[954]: could not open '/home/frog/.notify-osd'. using default settings.
Dec 10 18:01:41 isdumb dbus-daemon[954]: [session uid=1000 pid=954] Successfully activated service 'org.freedesktop.Notifications'xorg log: https://gist.github.com/greenbigfrog/c0 … 825ad02331
Offline
#7 2017-12-11 11:55:58
- Lone_Wolf
- Administrator
- From: Netherlands, Europe
- Registered: 2005-10-04
- Posts: 13,096
Re: Can't get OpenCL to work on OS stack with vega 56
Nothing stands out in the logs, the pacman and ls output do have clues.
$ pacman -Fs nvidia.icd
extra/opencl-nvidia 387.34-1
etc/OpenCL/vendors/nvidia.icd
extra/opencl-nvidia-304xx 304.137-1
etc/OpenCL/vendors/nvidia.icd
extra/opencl-nvidia-340xx 340.104-1
etc/OpenCL/vendors/nvidia.icd
$remove opencl-nvidia and lib32-opencl-nvidia , then check clinfo output again.
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
#8 2017-12-11 16:02:51
- greenbigfrog
- Member
- Registered: 2017-12-06
- Posts: 33
Re: Can't get OpenCL to work on OS stack with vega 56
remove opencl-nvidia and lib32-opencl-nvidia , then check clinfo output again.
Still the same output (0 Platforms)
Offline
#9 2017-12-11 16:42:35
- greenbigfrog
- Member
- Registered: 2017-12-06
- Posts: 33
Re: Can't get OpenCL to work on OS stack with vega 56
Interesting. After removing following packes and reinstalling mesa-git from the AUR, I'm finally getting a proper clinfo output:
nvidia-settings lib32-nvidia-utils nvidia-utilsOffline
#10 2017-12-11 16:43:29
- greenbigfrog
- Member
- Registered: 2017-12-06
- Posts: 33
Re: Can't get OpenCL to work on OS stack with vega 56
$clinfo
Number of platforms 1
Platform Name Clover
Platform Vendor Mesa
Platform Version OpenCL 1.1 Mesa 17.4.0-devel (git-6469669beb)
Platform Profile FULL_PROFILE
Platform Extensions cl_khr_icd
Platform Extensions function suffix MESA
Platform Name Clover
Number of devices 1
Device Name AMD VEGA10 (DRM 3.23.0 / 4.15.0-rc2-mainline, LLVM 6.0.0)
Device Vendor AMD
Device Vendor ID 0x1002
Device Version OpenCL 1.1 Mesa 17.4.0-devel (git-6469669beb)
Driver Version 17.4.0-devel
Device OpenCL C Version OpenCL C 1.1
Device Type GPU
Device Available Yes
Device Profile FULL_PROFILE
Max compute units 56
Max clock frequency 1590MHz
Max work item dimensions 3
Max work item sizes 256x256x256
Max work group size 256
Compiler Available Yes
=== CL_PROGRAM_BUILD_LOG ===
fatal error: cannot open file '/usr/lib/clc/gfx900-amdgcn-mesa-mesa3d.bc': No such file or directory
Preferred work group size multiple <getWGsizes:523: build program : error -11>
Preferred / native vector sizes
char 16 / 16
short 8 / 8
int 4 / 4
long 2 / 2
half 8 / 8 (cl_khr_fp16)
float 4 / 4
double 2 / 2 (cl_khr_fp64)
Half-precision Floating-point support (cl_khr_fp16)
Denormals No
Infinity and NANs Yes
Round to nearest Yes
Round to zero No
Round to infinity No
IEEE754-2008 fused multiply-add No
Support is emulated in software No
Single-precision Floating-point support (core)
Denormals No
Infinity and NANs Yes
Round to nearest Yes
Round to zero No
Round to infinity No
IEEE754-2008 fused multiply-add No
Support is emulated in software No
Correctly-rounded divide and sqrt operations No
Double-precision Floating-point support (cl_khr_fp64)
Denormals Yes
Infinity and NANs Yes
Round to nearest Yes
Round to zero Yes
Round to infinity Yes
IEEE754-2008 fused multiply-add Yes
Support is emulated in software No
Address bits 64, Little-Endian
Global memory size 8568094720 (7.98GiB)
Error Correction support No
Max memory allocation 5997666304 (5.586GiB)
Unified memory for Host and Device No
Minimum alignment for any data type 128 bytes
Alignment of base address 32768 bits (4096 bytes)
Global Memory cache type None
Image support No
Local memory type Local
Local memory size 32768 (32KiB)
Max constant buffer size 2147483647 (2GiB)
Max number of constant args 16
Max size of kernel argument 1024
Queue properties
Out-of-order execution No
Profiling Yes
Profiling timer resolution 0ns
Execution capabilities
Run OpenCL kernels Yes
Run native kernels No
Device Extensions cl_khr_byte_addressable_store cl_khr_global_int32_base_atomics cl_khr_global_int32_extended_atomics cl_khr_local_int32_base_atomics cl_khr_local_int32_extended_atomics cl_khr_int64_base_atomics cl_khr_int64_extended_atomics cl_khr_fp64 cl_khr_fp16
NULL platform behavior
clGetPlatformInfo(NULL, CL_PLATFORM_NAME, ...) Clover
clGetDeviceIDs(NULL, CL_DEVICE_TYPE_ALL, ...) Success [MESA]
clCreateContext(NULL, ...) [default] Success [MESA]
clCreateContextFromType(NULL, CL_DEVICE_TYPE_DEFAULT) Success (1)
Platform Name Clover
Device Name AMD VEGA10 (DRM 3.23.0 / 4.15.0-rc2-mainline, LLVM 6.0.0)
clCreateContextFromType(NULL, CL_DEVICE_TYPE_CPU) No devices found in platform
clCreateContextFromType(NULL, CL_DEVICE_TYPE_GPU) Success (1)
Platform Name Clover
Device Name AMD VEGA10 (DRM 3.23.0 / 4.15.0-rc2-mainline, LLVM 6.0.0)
clCreateContextFromType(NULL, CL_DEVICE_TYPE_ACCELERATOR) No devices found in platform
clCreateContextFromType(NULL, CL_DEVICE_TYPE_CUSTOM) No devices found in platform
clCreateContextFromType(NULL, CL_DEVICE_TYPE_ALL) Success (1)
Platform Name Clover
Device Name AMD VEGA10 (DRM 3.23.0 / 4.15.0-rc2-mainline, LLVM 6.0.0)
ICD loader properties
ICD loader Name OpenCL ICD Loader
ICD loader Vendor OCL Icd free software
ICD loader Version 2.2.11
ICD loader Profile OpenCL 2.1Offline
#11 2017-12-11 18:01:26
- greenbigfrog
- Member
- Registered: 2017-12-06
- Posts: 33
Re: Can't get OpenCL to work on OS stack with vega 56
Switching to libclc-git from the AUR removed the error:
$ clinfo
Number of platforms 1
Platform Name Clover
Platform Vendor Mesa
Platform Version OpenCL 1.1 Mesa 17.4.0-devel (git-6469669beb)
Platform Profile FULL_PROFILE
Platform Extensions cl_khr_icd
Platform Extensions function suffix MESA
Platform Name Clover
Number of devices 1
Device Name AMD VEGA10 (DRM 3.23.0 / 4.15.0-rc2-mainline, LLVM 6.0.0)
Device Vendor AMD
Device Vendor ID 0x1002
Device Version OpenCL 1.1 Mesa 17.4.0-devel (git-6469669beb)
Driver Version 17.4.0-devel
Device OpenCL C Version OpenCL C 1.1
Device Type GPU
Device Available Yes
Device Profile FULL_PROFILE
Max compute units 56
Max clock frequency 1590MHz
Max work item dimensions 3
Max work item sizes 256x256x256
Max work group size 256
Compiler Available Yes
Preferred work group size multiple 64
Preferred / native vector sizes
char 16 / 16
short 8 / 8
int 4 / 4
long 2 / 2
half 8 / 8 (cl_khr_fp16)
float 4 / 4
double 2 / 2 (cl_khr_fp64)
Half-precision Floating-point support (cl_khr_fp16)
Denormals No
Infinity and NANs Yes
Round to nearest Yes
Round to zero No
Round to infinity No
IEEE754-2008 fused multiply-add No
Support is emulated in software No
Single-precision Floating-point support (core)
Denormals No
Infinity and NANs Yes
Round to nearest Yes
Round to zero No
Round to infinity No
IEEE754-2008 fused multiply-add No
Support is emulated in software No
Correctly-rounded divide and sqrt operations No
Double-precision Floating-point support (cl_khr_fp64)
Denormals Yes
Infinity and NANs Yes
Round to nearest Yes
Round to zero Yes
Round to infinity Yes
IEEE754-2008 fused multiply-add Yes
Support is emulated in software No
Address bits 64, Little-Endian
Global memory size 8568094720 (7.98GiB)
Error Correction support No
Max memory allocation 5997666304 (5.586GiB)
Unified memory for Host and Device No
Minimum alignment for any data type 128 bytes
Alignment of base address 32768 bits (4096 bytes)
Global Memory cache type None
Image support No
Local memory type Local
Local memory size 32768 (32KiB)
Max constant buffer size 2147483647 (2GiB)
Max number of constant args 16
Max size of kernel argument 1024
Queue properties
Out-of-order execution No
Profiling Yes
Profiling timer resolution 0ns
Execution capabilities
Run OpenCL kernels Yes
Run native kernels No
Device Extensions cl_khr_byte_addressable_store cl_khr_global_int32_base_atomics cl_khr_global_int32_extended_atomics cl_khr_local_int32_base_atomics cl_khr_local_int32_extended_atomics cl_khr_int64_base_atomics cl_khr_int64_extended_atomics cl_khr_fp64 cl_khr_fp16
NULL platform behavior
clGetPlatformInfo(NULL, CL_PLATFORM_NAME, ...) Clover
clGetDeviceIDs(NULL, CL_DEVICE_TYPE_ALL, ...) Success [MESA]
clCreateContext(NULL, ...) [default] Success [MESA]
clCreateContextFromType(NULL, CL_DEVICE_TYPE_DEFAULT) Success (1)
Platform Name Clover
Device Name AMD VEGA10 (DRM 3.23.0 / 4.15.0-rc2-mainline, LLVM 6.0.0)
clCreateContextFromType(NULL, CL_DEVICE_TYPE_CPU) No devices found in platform
clCreateContextFromType(NULL, CL_DEVICE_TYPE_GPU) Success (1)
Platform Name Clover
Device Name AMD VEGA10 (DRM 3.23.0 / 4.15.0-rc2-mainline, LLVM 6.0.0)
clCreateContextFromType(NULL, CL_DEVICE_TYPE_ACCELERATOR) No devices found in platform
clCreateContextFromType(NULL, CL_DEVICE_TYPE_CUSTOM) No devices found in platform
clCreateContextFromType(NULL, CL_DEVICE_TYPE_ALL) Success (1)
Platform Name Clover
Device Name AMD VEGA10 (DRM 3.23.0 / 4.15.0-rc2-mainline, LLVM 6.0.0)
ICD loader properties
ICD loader Name OpenCL ICD Loader
ICD loader Vendor OCL Icd free software
ICD loader Version 2.2.11
ICD loader Profile OpenCL 2.1I think this a good sign...
Offline
#12 2017-12-12 11:46:38
- greenbigfrog
- Member
- Registered: 2017-12-06
- Posts: 33
Re: Can't get OpenCL to work on OS stack with vega 56
Ok. So the clinfo seams to finally work and be correct. But everything I can use to test openCL still doesn't work.
eg darktable-cltest reports "[opencl_init] discarding device 0 `AMD VEGA10 (DRM 3.23.0 / 4.15.0-rc2-mainline, LLVM 6.0.0)' due to missing image support."
Kinda lost here.
Offline
#13 2017-12-12 17:50:01
- Lone_Wolf
- Administrator
- From: Netherlands, Europe
- Registered: 2005-10-04
- Posts: 13,096
Re: Can't get OpenCL to work on OS stack with vega 56
That's probably because libclc / Clover only supports OpenCL 1.1 .
Now the OpenCL base setup is correct, re-install opencl-amd .
I expect/hope clinfo will then see two platforms .
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
#14 2017-12-12 17:56:15
- greenbigfrog
- Member
- Registered: 2017-12-06
- Posts: 33
Re: Can't get OpenCL to work on OS stack with vega 56
I just installed opencl-amd from the AUR, and still only one platform:
$ clinfo
Number of platforms 1
Platform Name Clover
Platform Vendor Mesa
Platform Version OpenCL 1.1 Mesa 17.4.0-devel (git-6469669beb)
Platform Profile FULL_PROFILE
Platform Extensions cl_khr_icd
Platform Extensions function suffix MESA
Platform Name Clover
Number of devices 1
Device Name AMD VEGA10 (DRM 3.23.0 / 4.15.0-rc3-mainline, LLVM 6.0.0)
Device Vendor AMD
Device Vendor ID 0x1002
Device Version OpenCL 1.1 Mesa 17.4.0-devel (git-6469669beb)
Driver Version 17.4.0-devel
Device OpenCL C Version OpenCL C 1.1
Device Type GPU
Device Available Yes
Device Profile FULL_PROFILE
Max compute units 56
Max clock frequency 1590MHz
Max work item dimensions 3
Max work item sizes 256x256x256
Max work group size 256
Compiler Available Yes
Preferred work group size multiple 64
Preferred / native vector sizes
char 16 / 16
short 8 / 8
int 4 / 4
long 2 / 2
half 8 / 8 (cl_khr_fp16)
float 4 / 4
double 2 / 2 (cl_khr_fp64)
Half-precision Floating-point support (cl_khr_fp16)
Denormals No
Infinity and NANs Yes
Round to nearest Yes
Round to zero No
Round to infinity No
IEEE754-2008 fused multiply-add No
Support is emulated in software No
Single-precision Floating-point support (core)
Denormals No
Infinity and NANs Yes
Round to nearest Yes
Round to zero No
Round to infinity No
IEEE754-2008 fused multiply-add No
Support is emulated in software No
Correctly-rounded divide and sqrt operations No
Double-precision Floating-point support (cl_khr_fp64)
Denormals Yes
Infinity and NANs Yes
Round to nearest Yes
Round to zero Yes
Round to infinity Yes
IEEE754-2008 fused multiply-add Yes
Support is emulated in software No
Address bits 64, Little-Endian
Global memory size 8568094720 (7.98GiB)
Error Correction support No
Max memory allocation 5997666304 (5.586GiB)
Unified memory for Host and Device No
Minimum alignment for any data type 128 bytes
Alignment of base address 32768 bits (4096 bytes)
Global Memory cache type None
Image support No
Local memory type Local
Local memory size 32768 (32KiB)
Max constant buffer size 2147483647 (2GiB)
Max number of constant args 16
Max size of kernel argument 1024
Queue properties
Out-of-order execution No
Profiling Yes
Profiling timer resolution 0ns
Execution capabilities
Run OpenCL kernels Yes
Run native kernels No
Device Extensions cl_khr_byte_addressable_store cl_khr_global_int32_base_atomics cl_khr_global_int32_extended_atomics cl_khr_local_int32_base_atomics cl_khr_local_int32_extended_atomics cl_khr_int64_base_atomics cl_khr_int64_extended_atomics cl_khr_fp64 cl_khr_fp16
NULL platform behavior
clGetPlatformInfo(NULL, CL_PLATFORM_NAME, ...) Clover
clGetDeviceIDs(NULL, CL_DEVICE_TYPE_ALL, ...) Success [MESA]
clCreateContext(NULL, ...) [default] Success [MESA]
clCreateContextFromType(NULL, CL_DEVICE_TYPE_DEFAULT) Success (1)
Platform Name Clover
Device Name AMD VEGA10 (DRM 3.23.0 / 4.15.0-rc3-mainline, LLVM 6.0.0)
clCreateContextFromType(NULL, CL_DEVICE_TYPE_CPU) No devices found in platform
clCreateContextFromType(NULL, CL_DEVICE_TYPE_GPU) Success (1)
Platform Name Clover
Device Name AMD VEGA10 (DRM 3.23.0 / 4.15.0-rc3-mainline, LLVM 6.0.0)
clCreateContextFromType(NULL, CL_DEVICE_TYPE_ACCELERATOR) No devices found in platform
clCreateContextFromType(NULL, CL_DEVICE_TYPE_CUSTOM) No devices found in platform
clCreateContextFromType(NULL, CL_DEVICE_TYPE_ALL) Success (1)
Platform Name Clover
Device Name AMD VEGA10 (DRM 3.23.0 / 4.15.0-rc3-mainline, LLVM 6.0.0)
ICD loader properties
ICD loader Name OpenCL ICD Loader
ICD loader Vendor OCL Icd free software
ICD loader Version 2.2.11
ICD loader Profile OpenCL 2.1Offline
#15 2017-12-12 18:42:19
- Lone_Wolf
- Administrator
- From: Netherlands, Europe
- Registered: 2005-10-04
- Posts: 13,096
Re: Can't get OpenCL to work on OS stack with vega 56
Hmm, is this your sole videocard in this system ?
post lspci -k .
What are the contents of /etc/ld.so.conf.d/ ?
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
#16 2017-12-12 18:45:25
- greenbigfrog
- Member
- Registered: 2017-12-06
- Posts: 33
Re: Can't get OpenCL to work on OS stack with vega 56
Yes. The vega 56 is the only gfx card installed in my system currently.
lspci -k
00:00.0 Host bridge: Intel Corporation 4th Gen Core Processor DRAM Controller (rev 06)
Subsystem: ASUSTeK Computer Inc. 4th Gen Core Processor DRAM Controller
Kernel driver in use: hsw_uncore
00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor PCI Express x16 Controller (rev 06)
Kernel driver in use: pcieport
Kernel modules: shpchp
00:14.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB xHCI (rev 05)
Subsystem: ASUSTeK Computer Inc. 8 Series/C220 Series Chipset Family USB xHCI
Kernel driver in use: xhci_hcd
Kernel modules: xhci_pci
00:16.0 Communication controller: Intel Corporation 8 Series/C220 Series Chipset Family MEI Controller #1 (rev 04)
Subsystem: ASUSTeK Computer Inc. 8 Series/C220 Series Chipset Family MEI Controller
Kernel driver in use: mei_me
Kernel modules: mei_me
00:1a.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #2 (rev 05)
Subsystem: ASUSTeK Computer Inc. 8 Series/C220 Series Chipset Family USB EHCI
Kernel driver in use: ehci-pci
Kernel modules: ehci_pci
00:1b.0 Audio device: Intel Corporation 8 Series/C220 Series Chipset High Definition Audio Controller (rev 05)
Subsystem: ASUSTeK Computer Inc. 8 Series/C220 Series Chipset High Definition Audio Controller
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel
00:1c.0 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #1 (rev d5)
Kernel driver in use: pcieport
Kernel modules: shpchp
00:1c.2 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #3 (rev d5)
Kernel driver in use: pcieport
Kernel modules: shpchp
00:1c.3 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #4 (rev d5)
Kernel driver in use: pcieport
Kernel modules: shpchp
00:1c.4 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #5 (rev d5)
Kernel driver in use: pcieport
Kernel modules: shpchp
00:1d.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #1 (rev 05)
Subsystem: ASUSTeK Computer Inc. 8 Series/C220 Series Chipset Family USB EHCI
Kernel driver in use: ehci-pci
Kernel modules: ehci_pci
00:1f.0 ISA bridge: Intel Corporation H87 Express LPC Controller (rev 05)
Subsystem: ASUSTeK Computer Inc. H87 Express LPC Controller
Kernel driver in use: lpc_ich
Kernel modules: lpc_ich
00:1f.2 SATA controller: Intel Corporation 8 Series/C220 Series Chipset Family 6-port SATA Controller 1 [AHCI mode] (rev 05)
Subsystem: ASUSTeK Computer Inc. 8 Series/C220 Series Chipset Family 6-port SATA Controller 1 [AHCI mode]
Kernel driver in use: ahci
Kernel modules: ahci
00:1f.3 SMBus: Intel Corporation 8 Series/C220 Series Chipset Family SMBus Controller (rev 05)
Subsystem: ASUSTeK Computer Inc. 8 Series/C220 Series Chipset Family SMBus Controller
Kernel driver in use: i801_smbus
Kernel modules: i2c_i801
03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 0c)
Subsystem: ASUSTeK Computer Inc. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
Kernel driver in use: r8169
Kernel modules: r8169
04:00.0 SATA controller: Marvell Technology Group Ltd. 88SE9172 SATA 6Gb/s Controller (rev 11)
Subsystem: ASUSTeK Computer Inc. 88SE9172 SATA 6Gb/s Controller
Kernel driver in use: ahci
Kernel modules: ahci
05:00.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Device 1470 (rev c3)
Kernel driver in use: pcieport
Kernel modules: shpchp
06:00.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Device 1471
Kernel driver in use: pcieport
Kernel modules: shpchp
07:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Vega 10 XT [Radeon RX Vega 64] (rev c3)
Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Vega 10 XT [Radeon RX Vega 64]
Kernel driver in use: amdgpu
Kernel modules: amdgpu
07:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Device aaf8
Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Device aaf8
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel$ ls /etc/ld.so.conf.d/
50-ffmpeg2.8.conf android-sdk.conf fakeroot.conf lib32-glibc.conf opencascade.conf opencollada.conf vtk6.confOffline
#17 2017-12-12 18:53:33
- Lone_Wolf
- Administrator
- From: Netherlands, Europe
- Registered: 2005-10-04
- Posts: 13,096
Re: Can't get OpenCL to work on OS stack with vega 56
Are you running libdrm-git or stock libdrm ?
If stock, does installing libdrm-git make a difference ?
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
#18 2017-12-12 19:10:54
- greenbigfrog
- Member
- Registered: 2017-12-06
- Posts: 33
Re: Can't get OpenCL to work on OS stack with vega 56
I was running stock libdrm and just switched to libdrm-git. Didn't change anything rly: https://www.diffchecker.com/LVN93pIE
Offline
#19 2017-12-13 13:07:47
- Lone_Wolf
- Administrator
- From: Netherlands, Europe
- Registered: 2005-10-04
- Posts: 13,096
Re: Can't get OpenCL to work on OS stack with vega 56
your /etc/OpenCL/vendors/ folder should have a mesa.icd file in it.
temporary move/rename it, post clinfo .
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
#20 2017-12-13 15:17:36
- greenbigfrog
- Member
- Registered: 2017-12-06
- Posts: 33
Re: Can't get OpenCL to work on OS stack with vega 56
Copied mesa.icd to mesa, rebooted and clinfo is back to 0 Platforms.
Offline
#21 2017-12-13 15:43:21
- Lone_Wolf
- Administrator
- From: Netherlands, Europe
- Registered: 2005-10-04
- Posts: 13,096
Re: Can't get OpenCL to work on OS stack with vega 56
/etc/OpenCL/vendors/amdocl64.icd (comes with opencl-amd) is present ?
if yes, create /etc/ld.so.conf.d/00-usrlib.conf
/etc/ld.so.conf.d/00-usrlib.conf
/usr/libverify clinfo again, if it still can't find the platform revert to stock mesa to see if that finds it.
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
#22 2017-12-13 15:51:29
- greenbigfrog
- Member
- Registered: 2017-12-06
- Posts: 33
Re: Can't get OpenCL to work on OS stack with vega 56
/etc/OpenCL/vendors/amdocl64.icd is present, I created /etc/ld.so.conf.d/00-usrlib.conf and clinfo was showing 0 platforms.
Moving mesa back to mesa.icd is showing 1 platform again.
Offline
#23 2017-12-13 16:00:49
- Lone_Wolf
- Administrator
- From: Netherlands, Europe
- Registered: 2005-10-04
- Posts: 13,096
Re: Can't get OpenCL to work on OS stack with vega 56
Ok, time to figure out whether my mesa-git is the culprit .
Revert to stock mesa package or lordheavy's unoffical mesa-git repo.
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
#24 2017-12-13 16:07:00
- greenbigfrog
- Member
- Registered: 2017-12-06
- Posts: 33
Re: Can't get OpenCL to work on OS stack with vega 56
With stock mesa package, you are reffering to the "mesa" package I'm assuming.
When trying to install mesa, I get following error. Not that experienced how to properly handle dependencies...
pacaur -S mesa
[sudo] password for frog:
resolving dependencies...
looking for conflicting packages...
:: mesa and mesa-git are in conflict (mesa-libgl). Remove mesa-git? [y/N] y
error: failed to prepare transaction (could not satisfy dependencies)
:: mesa: requires libtxc_dxtnWith lordheavy's repo you are referring to https://wiki.archlinux.org/index.php/Un … s#mesa-git ?
Offline
#25 2017-12-13 16:49:50
- Lone_Wolf
- Administrator
- From: Netherlands, Europe
- Registered: 2005-10-04
- Posts: 13,096
Re: Can't get OpenCL to work on OS stack with vega 56
yes to both.
For LH's repo you'll need to enable testing & multi-lib testing repos, mesa from [extra] repo is probably somewhat easier.
first, please use pacman for this. replacing my mesa-git with official mesa can be tricky, let the official tool do it.
Also do this as root from console , not with sudo or su from x-terminal .
(Trying to minimize chances of things going wrong )
My mesa-git / lib32-mesa-git have everything in 1 package, but mesa & LH mesa-git use a split package approach .
Switching from one of them to my mesa-git is easy, the reverse is a lot trickier .
run pacman -Syu
check if you have lib32-mesa-git installed, if so remove it .
If there are packages that depend on it, remove them temporarily.
run pacman -S mesa libtxc_dxtn
If pacman complains vulkan-intel / vulkan-radeon / libva-mesa-driver / mesa-vdpau are needed , add them to the pacman line.
Last edited by Lone_Wolf (2017-12-13 16:50:47)
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline