OpenCL 1.2 finally in Mesa - please test
Moderators: Site Moderators, FAHC Science Team
-
- Site Moderator
- Posts: 6986
- Joined: Wed Dec 23, 2009 9:33 am
- Hardware configuration: V7.6.21 -> Multi-purpose 24/7
Windows 10 64-bit
CPU:2/3/4/6 -> Intel i7-6700K
GPU:1 -> Nvidia GTX 1080 Ti
§
Retired:
2x Nvidia GTX 1070
Nvidia GTX 675M
Nvidia GTX 660 Ti
Nvidia GTX 650 SC
Nvidia GTX 260 896 MB SOC
Nvidia 9600GT 1 GB OC
Nvidia 9500M GS
Nvidia 8800GTS 320 MB
Intel Core i7-860
Intel Core i7-3840QM
Intel i3-3240
Intel Core 2 Duo E8200
Intel Core 2 Duo E6550
Intel Core 2 Duo T8300
Intel Pentium E5500
Intel Pentium E5400 - Location: Land Of The Long White Cloud
- Contact:
Re: OpenCL 1.2 finally in Mesa - please test
When it comes to GPU detection in Windows VS Linux, I have a vague recollection that Linux might be disabled by default since there's more work involved in it than Windows... this was the assumption many years ago so I am not sure if that's the reason why the default behavior between Windows and Linux stems from. Of course, I could have an over-active imagination and this was purely fictional so take it with a decent amount of salt
ETA:
Now ↞ Very Soon ↔ Soon ↔ Soon-ish ↔ Not Soon ↠ End Of Time
Welcome To The F@H Support Forum Ӂ Troubleshooting Bad WUs Ӂ Troubleshooting Server Connectivity Issues
Now ↞ Very Soon ↔ Soon ↔ Soon-ish ↔ Not Soon ↠ End Of Time
Welcome To The F@H Support Forum Ӂ Troubleshooting Bad WUs Ӂ Troubleshooting Server Connectivity Issues
Re: OpenCL 1.2 finally in Mesa - please test
Do we know whether that system has OpenCL 1.1 or >=1.2 on it?ajm wrote:Quick test: I installed FAH 7.6.21 on a Win 10 laptop with 2 GPUs (Intel + Nvidia). Expert, start manually...
Posting FAH's log:
How to provide enough info to get helpful support.
How to provide enough info to get helpful support.
Re: OpenCL 1.2 finally in Mesa - please test
OpenCL 1.2 (according to Geeks3D GPU Caps Viewer)
Re: OpenCL 1.2 finally in Mesa - please test
After several restarts it suddenly worked. No dirver changes, but maybe some silent windows updates.Joe_H wrote:The only other thing I can think of is the driver. [...] so you may need to drop back a version or two with the Windows driver.
I noticed it working by poor performance in Solid Edge CAD and let it finish one WU.
The 7970 was showing around 350.000 PPD while being a really hot piece of circuit board.
24/7
1x i5 3470 @2Cores
1x GTX750 (GM107)
2x GTX750Ti (GM107)
1x i5 3470 @2Cores
1x GTX750 (GM107)
2x GTX750Ti (GM107)
-
- Posts: 3
- Joined: Sat Mar 07, 2020 2:28 pm
- Hardware configuration: AMD Ryzen 5 2400G, NVidia 1030 2GB - driver 440.59 (manual install), 16GB DDR4 2933 RAM, Linux (Ubuntu 19.10) Kernel 5.5.8
Re: OpenCL 1.2 finally in Mesa - please test
Putting my hand up, to show that I am also a Linux-user with mesa drivers and installed opencl-icd, and still are unable to fold with the GPU part of my AMD 2400G.
I waited one year after my initial post about it, and it seems nothing happened to make use of all the integrated AMD graphics users on a linux (default - mesa) system. Seems no one on their team is giving a male chicken's donkey about it.
Prerequisites should be fine, just folding isn't:
mesa-opencl-icd 21.2~git2105081800.d81a6e~oibaf~f
ocl-icd-libopencl1 2.2.11-1ubuntu1
ocl-icd-libopencl1:i386 2.2.11-1ubuntu1
opencl-c-headers 2.2~2019.08.06-g0d5f18c-1
clinfo:
$ clinfo
Number of platforms 1
Platform Name Clover
Platform Vendor Mesa
Platform Version OpenCL 1.1 Mesa 21.2.0-devel (git-d81a6e5 2021-05-08 focal-oibaf-ppa)
Platform Profile FULL_PROFILE
Platform Extensions cl_khr_icd
Platform Extensions function suffix MESA
Platform Name Clover
Number of devices 1
Device Name AMD Radeon(TM) Vega 11 Graphics (RAVEN, DRM 3.40.0, 5.12.2-051202-generic, LLVM 12.0.0)
Device Vendor AMD
Device Vendor ID 0x1002
Device Version OpenCL 1.1 Mesa 21.2.0-devel (git-d81a6e5 2021-05-08 focal-oibaf-ppa)
Driver Version 21.2.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 11
Max clock frequency 1250MHz
Max work item dimensions 3
Max work item sizes 256x256x256
Max work group size 256
Preferred / native vector sizes
char 16 / 16
short 8 / 8
int 4 / 4
long 2 / 2
half 0 / 0 (n/a)
float 4 / 4
double 2 / 2 (cl_khr_fp64)
Half-precision Floating-point support (n/a)
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 3221225472 (3GiB)
Error Correction support No
Max memory allocation 2254857830 (2.1GiB)
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 67108864 (64MiB)
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_extended_versioning
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 Radeon(TM) Vega 11 Graphics (RAVEN, DRM 3.40.0, 5.12.2-051202-generic, LLVM 12.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 Radeon(TM) Vega 11 Graphics (RAVEN, DRM 3.40.0, 5.12.2-051202-generic, LLVM 12.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 Radeon(TM) Vega 11 Graphics (RAVEN, DRM 3.40.0, 5.12.2-051202-generic, LLVM 12.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.1
I waited one year after my initial post about it, and it seems nothing happened to make use of all the integrated AMD graphics users on a linux (default - mesa) system. Seems no one on their team is giving a male chicken's donkey about it.
Prerequisites should be fine, just folding isn't:
mesa-opencl-icd 21.2~git2105081800.d81a6e~oibaf~f
ocl-icd-libopencl1 2.2.11-1ubuntu1
ocl-icd-libopencl1:i386 2.2.11-1ubuntu1
opencl-c-headers 2.2~2019.08.06-g0d5f18c-1
clinfo:
$ clinfo
Number of platforms 1
Platform Name Clover
Platform Vendor Mesa
Platform Version OpenCL 1.1 Mesa 21.2.0-devel (git-d81a6e5 2021-05-08 focal-oibaf-ppa)
Platform Profile FULL_PROFILE
Platform Extensions cl_khr_icd
Platform Extensions function suffix MESA
Platform Name Clover
Number of devices 1
Device Name AMD Radeon(TM) Vega 11 Graphics (RAVEN, DRM 3.40.0, 5.12.2-051202-generic, LLVM 12.0.0)
Device Vendor AMD
Device Vendor ID 0x1002
Device Version OpenCL 1.1 Mesa 21.2.0-devel (git-d81a6e5 2021-05-08 focal-oibaf-ppa)
Driver Version 21.2.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 11
Max clock frequency 1250MHz
Max work item dimensions 3
Max work item sizes 256x256x256
Max work group size 256
Preferred / native vector sizes
char 16 / 16
short 8 / 8
int 4 / 4
long 2 / 2
half 0 / 0 (n/a)
float 4 / 4
double 2 / 2 (cl_khr_fp64)
Half-precision Floating-point support (n/a)
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 3221225472 (3GiB)
Error Correction support No
Max memory allocation 2254857830 (2.1GiB)
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 67108864 (64MiB)
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_extended_versioning
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 Radeon(TM) Vega 11 Graphics (RAVEN, DRM 3.40.0, 5.12.2-051202-generic, LLVM 12.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 Radeon(TM) Vega 11 Graphics (RAVEN, DRM 3.40.0, 5.12.2-051202-generic, LLVM 12.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 Radeon(TM) Vega 11 Graphics (RAVEN, DRM 3.40.0, 5.12.2-051202-generic, LLVM 12.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.1
-
- Site Moderator
- Posts: 6349
- Joined: Sun Dec 02, 2007 10:38 am
- Location: Bordeaux, France
- Contact:
Re: OpenCL 1.2 finally in Mesa - please test
Same player, try again ...Rev wrote:clinfo:
$ clinfo
Number of platforms 1
Platform Name Clover
Platform Vendor Mesa
Platform Version OpenCL 1.1 Mesa 21.2.0-devel (git-d81a6e5 2021-05-08 focal-oibaf-ppa)
Platform Profile FULL_PROFILE
Platform Extensions cl_khr_icd
Platform Extensions function suffix MESA
Platform Name Clover
Number of devices 1
Device Name AMD Radeon(TM) Vega 11 Graphics (RAVEN, DRM 3.40.0, 5.12.2-051202-generic, LLVM 12.0.0)
Device Vendor AMD
Device Vendor ID 0x1002
Device Version OpenCL 1.1 Mesa 21.2.0-devel (git-d81a6e5 2021-05-08 focal-oibaf-ppa)
Driver Version 21.2.0-devel
Device OpenCL C Version OpenCL C 1.1
Device Type GPU
Device Profile FULL_PROFILE
FAH only supports proprietary drivers downloaded from the manufacturer (AMD or nVidia) website.
Re: OpenCL 1.2 finally in Mesa - please test
and FAH requires OpenCL 1.2. OpenCL 1.1 is insufficient.
Posting FAH's log:
How to provide enough info to get helpful support.
How to provide enough info to get helpful support.
Re: OpenCL 1.2 finally in Mesa - please test
I can only write about my GPU that supports1.2 and is running within windows.bruce wrote:and FAH requires OpenCL 1.2.
The Mesamatrix https://mesamatrix.net/#OpenCL1.2 is listing most extensions build in.
But I also get "1.1" by using clinfo.
Could someone from the FAH Team proof if the build in extensions are enough to use FAH?
If someone declares all components should meet the requirements Im willing to contact the Mesa developers.
24/7
1x i5 3470 @2Cores
1x GTX750 (GM107)
2x GTX750Ti (GM107)
1x i5 3470 @2Cores
1x GTX750 (GM107)
2x GTX750Ti (GM107)
-
- Posts: 2522
- Joined: Mon Feb 16, 2009 4:12 am
- Location: Greenwood MS USA
Re: OpenCL 1.2 finally in Mesa - please test
[I am just a folder like you, this is not an official policy, just my opinion]
Let’s decide to learn form the Past.
There is an Nvidia architecture called Fermi, none of the Fermi GPUs do all of OpenCL 1.2
However the phase 2* Fermi chips do part of OpenCL 1.2, let say 75% of proteins complete and 25% fail.
The problems with this are many.
“I have a Fermi GPU and he has a Fermi GPU and HE gets to fold, and I don’t”
“F@H is ‘broken’ because my GPU fails so often”
“I lose my bonus points because I did not complete 80% of my Work Units”
It is hard to black list a GPU which is still mostly working.
Projects would complete faster if they rejected Fermi GPUs at startup, rather than waiting for a slow chip to fail later.
Because Nvidia uses multiple GPUs in a card they name the same, some GT 730s are first phase Fermi, which never works, some are Kepler, which always works. The folder feels we are picking on him.
F@H still suffers from Fermi, I refuse to help make phase 2 Fermi work, I don’t want F@H to work badly. And I can’t make it right.
https://en.wikipedia.org/wiki/Fermi_(microarchitecture)
* chips named GF11x where x is some number
Until Mesa fully supports OpenCL 1.2, we have a similar problem, fortunately, we have an ‘easy’ solution, use the proprietary driver which DOES work.
Let’s decide to learn form the Past.
There is an Nvidia architecture called Fermi, none of the Fermi GPUs do all of OpenCL 1.2
However the phase 2* Fermi chips do part of OpenCL 1.2, let say 75% of proteins complete and 25% fail.
The problems with this are many.
“I have a Fermi GPU and he has a Fermi GPU and HE gets to fold, and I don’t”
“F@H is ‘broken’ because my GPU fails so often”
“I lose my bonus points because I did not complete 80% of my Work Units”
It is hard to black list a GPU which is still mostly working.
Projects would complete faster if they rejected Fermi GPUs at startup, rather than waiting for a slow chip to fail later.
Because Nvidia uses multiple GPUs in a card they name the same, some GT 730s are first phase Fermi, which never works, some are Kepler, which always works. The folder feels we are picking on him.
F@H still suffers from Fermi, I refuse to help make phase 2 Fermi work, I don’t want F@H to work badly. And I can’t make it right.
https://en.wikipedia.org/wiki/Fermi_(microarchitecture)
* chips named GF11x where x is some number
Until Mesa fully supports OpenCL 1.2, we have a similar problem, fortunately, we have an ‘easy’ solution, use the proprietary driver which DOES work.
Tsar of all the Rushers
I tried to remain childlike, all I achieved was childish.
A friend to those who want no friends
I tried to remain childlike, all I achieved was childish.
A friend to those who want no friends
Re: OpenCL 1.2 finally in Mesa - please test
I do understand your frustration, but unfortunately, drivers are the responsibility company that supports your hardware.
Mesa support must be obtained from AMD.com.
FAH does not support any GPU drivers. All we can do is t tell you to get the proprietary drivers and refer you to AMD .com or NVIdia.com or Intel.com or Mac.com
We do have other volunteers who visit this site who may have worked through such problems who may (or may not) be able to help.
Mesa support must be obtained from AMD.com.
FAH does not support any GPU drivers. All we can do is t tell you to get the proprietary drivers and refer you to AMD .com or NVIdia.com or Intel.com or Mac.com
We do have other volunteers who visit this site who may have worked through such problems who may (or may not) be able to help.
Posting FAH's log:
How to provide enough info to get helpful support.
How to provide enough info to get helpful support.