[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <UXR6AQuYZHZ753R6DiSTa3JuVhtx6wNLxRqdKEp-LzzQw3g6zFgrBGY1m2CgO2owVQy_HM9WM5NJOndBqjqQy4csKw2gNzQmqoBk6rhiiBk=@protonmail.ch>
Date: Sat, 22 Aug 2020 12:13:07 +0000
From: freeroute <freeroute@...tonmail.ch>
To: "john-users@...ts.openwall.com" <john-users@...ts.openwall.com>
Subject: Re: OpenCl lib not detected
Thank you for your quick response.
I think its solved.
as written in /john/doc/INSTALL-OPENCL file.
"The new autoconf (./configure) should find your OpenCL installation and enable it. If it doesn't, you may need to pass some parameters about where it's located..."
So I used these parameters:
"./configure LDFLAGS=-L/usr/local/cuda-11.0/targets/x86_64-linux/lib CFLAGS=-I/usr/local/cuda-11.0/targets/x86_64-linux/include
make -sj4"
and now I have GPU support.
Note: I always use git clone in /usr/local/src/ directory. I think the autoconf did not find the OpenCL lib.
Sent with ProtonMail Secure Email.
‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Saturday, August 22, 2020 2:04 PM, Solar Designer <solar@...nwall.com> wrote:
> Hi,
>
> On Fri, Aug 21, 2020 at 08:43:54PM +0000, freeroute wrote:
>
> > OpenCL support ............................. no
>
> Can you show the full output of ./configure? In particular, we need
> these lines:
>
> checking CL/cl.h usability... yes
> checking CL/cl.h presence... yes
> checking for CL/cl.h... yes
> checking OpenCL/cl.h usability... no
> checking OpenCL/cl.h presence... no
> checking for OpenCL/cl.h... no
> [...]
> checking for OpenCL library... -lOpenCL
>
> The above example is from a build that successfully detects OpenCL - we
> need to see how your output differs.
>
> > So what parameters should I give to enable it?
>
> I'd start by seeing the above and tweaking the system to allow for
> automatic detection.
>
> > Output of: sudo updatedb && locate CL/cl.h && locate libOpenCL.so
> > [sudo] password for freeroute:
> > /usr/include/CL/cl.h
> > /usr/include/CL/cl.hpp
> > /usr/local/cuda-11.0/targets/x86_64-linux/include/CL/cl.h
>
> Can you show the output of:
>
> ls -ld /usr/include/CL /usr/local/cuda-11.0/targets/x86_64-linux/include/CL
> ls -ld /usr/include/CL/cl.h /usr/local/cuda-11.0/targets/x86_64-linux/include/CL/cl.h
>
> > Note: I updated the drivers according this https://hashcat.net/forum/thread-9313-post-49247.html#pid49247, but OpenCl still not recognized by JtR. Hashcat working well.
>
> hashcat bundles its own copy of OpenCL headers:
>
> > /usr/local/src/hashcat/deps/OpenCL-Headers/CL/cl.h
>
> so it doesn't depend on the system having working OpenCL headers.
>
> BTW, we normally recommend to build and run JtR as non-root, but now
> that you've already started building as root you should probably
> continue with that for now (not to introduce even more uncertainty into
> the troubleshooting) or start over as non-root with a fresh git clone.
> This is most likely unrelated to the OpenCL problem you're having - it's
> just another detail I noticed.
>
> Alexander
Download attachment "publickey - freeroute@...tonmail.ch - 0xDA223267.asc" of type "application/pgp-keys" (1794 bytes)
Download attachment "signature.asc" of type "application/pgp-signature" (510 bytes)
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
