device local mem size is too small, use anyway?
#5
Thanks you for the advise.
I installed from Debain Jessie the OpenCL runtime (apt-get install ocl-icd-libopencl1 opencl-headers clinfo).
With the new hashcat version I got this message (without nvida-legacy-340xx-driver. Nvidia driver is it must to install to use hashcat with CPU?):

root@The-Distribution-Which-Does-Not-Handle-OpenCL-Well (Kali):~# hashcat -b
hashcat (v3.00) starting in benchmark-mode...

OpenCL Platform #1: Mesa
========================
- Device #1: WARNING: Device local mem size is too small
- Device #1: NV86, skipped

OpenCL Platform #2: Advanced Micro Devices, Inc.
================================================
- Device #2: WARNING: Not a native Intel OpenCL runtime, expect massive speed loss
            You can use --force to override this but do not post error reports if you do so
- Device #2: Intel(R) Core(TM)2 Duo CPU     T5450  @ 1.66GHz, skipped

ERROR: No devices found/left

and then:
root@The-Distribution-Which-Does-Not-Handle-OpenCL-Well (Kali):~# hashcat -b --opencl-platforms=2 --force
hashcat (v3.00) starting in benchmark-mode...

OpenCL Platform #1: Mesa, skipped

OpenCL Platform #2: Advanced Micro Devices, Inc.
================================================
- Device #1: Intel(R) Core(TM)2 Duo CPU     T5450  @ 1.66GHz, 1003/1003 MB allocatable, 2MCU

Hashtype: MD4
Speed.Dev.#1.: 52427.2 kH/s (95.51ms)
Hashtype: MD5
Speed.Dev.#1.: 34775.0 kH/s (95.06ms)
Hashtype: Half MD5
Speed.Dev.#1.: 22713.3 kH/s (95.09ms)

So it is too slow.
I will try to install the OpenCL runtime library from Debian Wheezy, too. Maybe I can use somehow the new hashcat....


Messages In This Thread
RE: device local mem size is too small, use anyway? - by freeroute - 07-22-2016, 05:17 PM