Good day, is hellcp:ROCm repository a valid and working ROCm? Are there any plans for ROCm?
Also i noticed that there is no Freesync with Kernel:stable 5.0.0 - khnazile:video 19.1.0 and the VariableRefresh option.
Good day, is hellcp:ROCm repository a valid and working ROCm? Are there any plans for ROCm?
Also i noticed that there is no Freesync with Kernel:stable 5.0.0 - khnazile:video 19.1.0 and the VariableRefresh option.
You might be better of asking the maintainers of those packages directly.
Your ROCm link points eventually to a fully working repository
https://download.opensuse.org/repositories/home:/hellcp:/ROCm/openSUSE_Tumbleweed/
Don’t know about your other question, I think you are asking about what has been built into the default kernel.
If what you’re looking for might be considered exotic, you might look at other kernels or if the feature is very new you might look at other available kernels. If you don’t find your answer, as @knurpht says you can message maintainers of that feature or maybe get on the kernel mail list.
TSU
Hello, it does contain ROCm but it also contains Clover. Is there a way to disable/remove Clover only?
> clinfo
Number of platforms 1
*** Platform Name Clover***
*** Platform Vendor Mesa***
*** Platform Version OpenCL 1.1 Mesa 19.1.0-devel***
*** Platform Profile FULL_PROFILE***
*** Platform Extensions cl_khr_icd***
*** Platform Extensions function suffix MESA***
*** Platform Name Clover***
Number of devices 1
*** Device Name Radeon RX 570 Series (POLARIS10, DRM 3.27.0, 4.20.13-1-default, LLVM 7.0.1)***
*** Device Vendor AMD***
*** Device Vendor ID 0x1002***
*** Device Version OpenCL 1.1 Mesa 19.1.0-devel***
*** Driver Version 19.1.0-devel***
*** Device OpenCL C Version OpenCL C 1.1 ***
*** Device Type GPU***
*** Device Profile FULL_PROFILE***
*** Device Available Yes***
*** Compiler Available Yes***
*** Max compute units 32***
*** Max clock frequency 1244MHz***
*** Max work item dimensions 3***
*** Max work item sizes 256x256x256***
*** Max work group size 256***
*** 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 4294967296 (4GiB)***
*** Error Correction support No***
*** Max memory allocation 3435973836 (3.2GiB)***
*** 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 number of constant args 16***
*** Max constant buffer size 2147483647 (2GiB)***
*** 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 Radeon RX 570 Series (POLARIS10, DRM 3.27.0, 4.20.13-1-default, LLVM 7.0.1)***
*** clCreateContextFromType(NULL, CL_DEVICE_TYPE_CPU) No devices found in platform***
*** clCreateContextFromType(NULL, CL_DEVICE_TYPE_GPU) Success (1)***
*** Platform Name Clover***
*** Device Name Radeon RX 570 Series (POLARIS10, DRM 3.27.0, 4.20.13-1-default, LLVM 7.0.1)***
*** 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 Radeon RX 570 Series (POLARIS10, DRM 3.27.0, 4.20.13-1-default, LLVM 7.0.1)***
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.1***
I believe that Tumbleweed should change a little. I don’t understand why libLLVM7 doesn’t overlap libLLVM6 and the same goes on with 8. The same happened before with Python 3.6 and 3.7. Also the graphical updater should automatically use zypper DUB when its time. Even when i try to update all packages to a specific repository it shouldn’t ask me to verify every single package. My time is eaten every time, this isn’t a normal Rolling Release.
Apparently there is no way to disable Clover completely once it’s been compiled into Mesa3D…
But according to the following, you can prevent calls to it, so that should be a very minor improvement.
Maybe you can contact the maintainer and request a build without clover since it’s a reasonable and desired configuration…
Else, the only way to not have clover completely is to build yourself for now
Only someone who has looked closely at the compile flow can say why there isn’t a command line option to disable clover.
TSU