-
Notifications
You must be signed in to change notification settings - Fork 37
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
CL_PLATFORM_NOT_FOUND_KHR #5
Comments
UPDATE 08.06.22
Original response below Do you have GPUs? |
No I do not have GPUs. I'm still having the same issue with the :nvidia-full tag. I have removed the other images as described in the previous ticket as well. |
Then it means OpenCL driver is not properly installed for your graphics card or hashcat simply does not support your graphics card -- or rather it cannot/does not know how to talk with linux Intel OpenCL driver in Is your graphics card integrated Intel? Otherwise, If yes, try installing Intel OpenCL driver as described here hashcat/hashcat#1207 or building the driver manually https://software.intel.com/en-us/articles/opencl-drivers#latest_CPU_runtime. Make sure you're running Ubuntu 16.x -- driver complains that it does not support Ubuntu 18.x, however, in my case, it either works for both 16.x and 18.x or works for neither of them (as I currently experience with AWS CPU instances). |
After installing Intel CPU OpenCL runtime, please download hashcat-v5.1.0 archived source code, extract it and build hashcat manually. It's very straightforward - |
Just a small question, when I run the command "nvidia-smi" it shows me CUDA version: 11.0 instead of 10.2 |
@fa1rid maybe because you've installed CUDA 11 on your host system, which is shared with docker containers, and then a docker container picks 11 in favor of installed 10.2 at runtime. |
Confirmed fixed using |
POCL should be the last resort. |
Running hashcat command works on my mac but errors out on clGetPlatformIDs(): CL_PLATFORM_NOT_FOUND_KHR when running on ubuntu 18.04 Bionic. I have tried both intel-cpu and latest tagged images and both have the same errors. I see this is related to #2, is the fix the same?
The text was updated successfully, but these errors were encountered: