-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
AMD GPU on Linux doesn't work with Mesa's OpenCL drivers #239
Comments
The GPU is not supported with out OpenCL. What happens if you run |
I will have to get home to send it, but I've checked and everything seems to be correct. Geekbench's OpenCL benchmark also completes with no issues. |
If the client says it has now OpenCL support for the GPU it means that it was either not able to access OpenCL at all or it was not able to match the GPU it found in the system to a device in OpenCL. The later can occur if the driver does not supply PCI bus information. You may need to install AMD's drivers to get the GPU to work with F@H. |
Yeah, I'm using AMD's rocm driver to fold currently, and it works fine (as long as I delete the libraries bundled with the core to make it use the system libraries, I'll make a separate issue for that later). I just made this issue to try to find out why Mesa's implementation doesn't work. |
Someone else had mesa drivers and their GPU was disabled. clinfo indicated that FP64 was not supported by mesa opencl. |
OK, I'll make sure to send my |
Forgot to send it, sorry. This is using Mesa's Still greyed out in folding@home though, with the same message in the log as previously. Could it be because
|
Yes. OpenCL 1.2 or later is required. |
There is a flag to tenable FP64 with Rusticl since Mesa 23.2-devel, but I don't have the hardware to test it : https://www.phoronix.com/news/Rusticl-OpenCL-FP64-Doubles |
Lack of OpenCL v1.2 and FP64 support are both problems that would prevent the GPU from getting an assignment on F@H. However, I believe the real reason the client marks the GPU as unsupported is because the driver does not support either the |
Will test this when I'm back home, and send the Edit: Tested it on the integrated graphics in my laptop, and FP64 support does show up. If you look at the
|
New
|
Did you restart |
Yeah, I did. I’m not at home right now (will be back in 2 days), and I’ll post it then. |
|
Is this still not supported? I see |
I wonder if that is really sorted now. I saw similar issues with other distributed computing projects, where Mesa drivers are highly problematic. |
I believe the Mesa drivers still have emulated FP64 |
Ok, i think i made it work. First i add this to the
but then i add to compile the client myself, because i had to comment some part of the code, i don't why (maybe this could help investigate), i'm not a c++ developer neither an opencl developer. |
Any chance of performance comparison numbers between AMD opencl and mesa? If there is no difference, then this would be great. Though currently AMD opencl on Linux is quite broken as is performance wise :( |
Sadly, rusticl doesn't seem to be stable enough, my computer rebooted after 20 minutes (around 2.5~3.0%). I didn't had this problem when i was using the amdgpu opencl |
is there a specific reason this line doesn't mention fp32? |
There not fp32 feature_flag in the list So i changed |
Heat would have been an issue even with AMD drivers. |
I think |
When trying to use Mesa's implementation of OpenCL, the gpu is greyed out in the devices list like so:
I can also see
being printed out in the log. There is a similar line in
gpus.json
:Could this simply be a case of something setting the type field incorrectly (and FAH thus thinking the GPU is unsupported)?
The text was updated successfully, but these errors were encountered: