|
Search Results
|
| Post |
Author |
Forum |
Replies |
Views |
Posted
[asc]
|
| |
|
Thread: clEnqueueNDRangeKernel(): CL_MEM_OBJECT_ALLOCATION_FAILURE only for -m 2500
Post: RE: clEnqueueNDRangeKernel(): CL_MEM_OBJECT_ALLOCA...
| Hi there, Increasing the swap was not the right fixed. I reinstalled the OS and it's giving me same "clEnqueueNDRangeKernel(): CL_MEM_OBJECT_ALLOCATION_FAILURE" for wpa2, zip etc. md5, sha1 are workin... |
|
w3soul |
hashcat
|
5 |
10,615 |
07-31-2018, 03:30 PM |
| |
|
Thread: OpenCL Platform #3: The pocl project
Post: RE: OpenCL Platform #3: The pocl project
|
atom Wrote: (07-30-2018, 07:44 PM)
--
If you have Intel OpenCL runtime then pocl will be disabled because its slower and more unstable. If you want to try out pocl remove the Intel OpenCL runtime and... |
|
w3soul |
hashcat
|
5 |
13,791 |
07-30-2018, 09:41 PM |
| |
|
Thread: clEnqueueNDRangeKernel(): CL_MEM_OBJECT_ALLOCATION_FAILURE only for -m 2500
Post: RE: clEnqueueNDRangeKernel(): CL_MEM_OBJECT_ALLOCA...
| FIXED!!!
Less swap memory was causing the error. I increased swap size from 50GB to 200 GB and that resolved the issue.
Thanks for your help atom!! |
|
w3soul |
hashcat
|
5 |
10,615 |
07-30-2018, 02:12 AM |
| |
|
Thread: OpenCL Platform #3: The pocl project
Post: RE: OpenCL Platform #3: The pocl project
|
Lars Wrote: (07-29-2018, 08:34 PM)
--
-D 1,2
--
Thanks Lars, But i did try -D 1,2 and also -D 1, -D 2, --opencl-platforms=1,2 but it still show up as Device#3 along with the same warning message.
... |
|
w3soul |
hashcat
|
5 |
13,791 |
07-29-2018, 09:30 PM |
| |
|
Thread: OpenCL Platform #3: The pocl project
Post: OpenCL Platform #3: The pocl project
| Hi there,
Running The-Distribution-Which-Does-Not-Handle-OpenCL-Well (Kali) 2018.2, 64bit (Standalone OS, not VM) with latest hashcat 4.1.0.
Nvidia GTX 960 and Intel OpenCL Runtime are installed.
... |
|
w3soul |
hashcat
|
5 |
13,791 |
07-29-2018, 08:30 PM |
| |
|
Thread: clEnqueueNDRangeKernel(): CL_MEM_OBJECT_ALLOCATION_FAILURE only for -m 2500
Post: RE: clEnqueueNDRangeKernel(): CL_MEM_OBJECT_ALLOCA...
| Actually i tried some other formats as well and they are giving the same error "clEnqueueNDRangeKernel(): CL_MEM_OBJECT_ALLOCATION_FAILURE" e.g zip, office, wpa.
Only working formats are md5, sha51... |
|
w3soul |
hashcat
|
5 |
10,615 |
07-29-2018, 07:29 PM |
| |
|
Thread: Disable Cracking performance lower than expected?
Post: RE: Disable Cracking performance lower than expect...
| Thanks atom and Daniel,
Both solutions worked for me!! |
|
w3soul |
hashcat
|
3 |
11,348 |
07-29-2018, 07:10 PM |
| |
|
Thread: clEnqueueNDRangeKernel(): CL_MEM_OBJECT_ALLOCATION_FAILURE only for -m 2500
Post: RE: clEnqueueNDRangeKernel(): CL_MEM_OBJECT_ALLOCA...
|
atom Wrote: (07-29-2018, 01:29 PM)
--
Add more host memory, use 64 bit OS
--
Thanks atom,
I am already running The-Distribution-Which-Does-Not-Handle-OpenCL-Well (Kali) 2018.2 64 bit with 32GB o... |
|
w3soul |
hashcat
|
5 |
10,615 |
07-29-2018, 06:19 PM |
| |
|
Thread: Disable Cracking performance lower than expected?
Post: Disable Cracking performance lower than expected?
| Hi there,
After a few seconds of hashcat running a message pops up:
Cracking performance lower than expected?
* Append -w 3 to the commandline.
This can cause your screen to lag.
* ... |
|
w3soul |
hashcat
|
3 |
11,348 |
07-29-2018, 10:33 AM |
| |
|
Thread: clEnqueueNDRangeKernel(): CL_MEM_OBJECT_ALLOCATION_FAILURE only for -m 2500
Post: clEnqueueNDRangeKernel(): CL_MEM_OBJECT_ALLOCATION...
| Hi,
The-Distribution-Which-Does-Not-Handle-OpenCL-Well (Kali) 2018.2 Fresh install. Nvidia driver installed using https://docs.The-Distribution-Which-Does-Not-Handle-OpenCL-Well (Kali).org/general... |
|
w3soul |
hashcat
|
5 |
10,615 |
07-29-2018, 08:48 AM |
