[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAAufJG5zGgYwyT5y8rF2-V8dBG9xmWp5ZVX6F6K680Gt-6KrTQ@mail.gmail.com>
Date: Sat, 27 Apr 2013 15:22:39 -0300
From: Claudio André <claudioandre.br@...il.com>
To: john-users@...ts.openwall.com
Subject: Re: Re: 'close' to getting opencl working
Does it make sense in your environment?
CPU only support on Intel® Core™ 2 processor family and Intel® Xeon®
processors is limited to Intel® microarchitecture that supports the Intel®
Streaming SIMD Extensions 4.1 (Intel® SSE 4.1) or higher.
----
http://stackoverflow.com/questions/15499533/error-cl-device-not-available-when-calling-clcreatecontext-intel-core2duo-inte
Claudio
2013/4/27 <jfoug@....net>
>
> ---- "Claudio André" <claudioandre.br@...il.com> wrote:
> > Just to keep an answer here on '-users':
> > Seems a problem is happening at context creation. If you enable DEBUB, we
> > might confirm that (on bleeding).
> >
> > Claudio
>
> Yes, I get the same under bleeding (compiled with -DDEBUG) as under
> unstable. I will have to keep looking at what or why the CPU intel OpenCL
> is not working under VB. It 'should', I thought, but apparently there is
> something not right.
>
> $ ../run/john -test -form=wpapsk-opencl
> OpenCL platform 0: Intel(R) OpenCL, 1 device(s).
> OpenCL platform 0: Intel(R) OpenCL, 1 device(s).
> Error creating context for device 0 (0:0): CL_DEVICE_NOT_AVAILABLE
> No OpenCL devices found
>
>
> cc: claudio (who is not onlist).
>
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.
