![]() Name : AMD Accelerated Parallel Processing Hashmode: 2500 - WPA-EAPOL-PBKDF2 (Iterations: 4096)ĬlCreateContext(): CL_DEVICE_NOT_AVAILABLE * Device #1: GeForce GT 430, 512/2048 MB allocatable, 2MCU To disable the optimized kernel code in benchmark mode, use the -w option. Note: Using optimized kernel code limits the maximum supported password length. You can use it in your cracking session by setting the -O option. Hashcat (v5.1.0) starting in benchmark mode.īenchmarking uses hand-optimized kernel code by default. Name : Intel(R) Xeon(R) CPU X5482 3.20GHz Name : Intel(R) CPU Runtime for OpenCL(TM) Applications It shows that hashcat does not run with Intel drivers ( clCreateContext(): CL_DEVICE_NOT_AVAILABLE), but runs fine with AMD. Is there a way for me to use the Intel driver? Is there a better driver than AMD 3.0? Do you know why AMD driver works with Intel Xeon CPU, but Intel drivers don't? I thought it should be the opposite. Today I found that hashcat works with AMD APP SDK v3.0, but I could not make it work with any Intel OpenCL driver (18.1, 16.1.1, 16.1.2). I was not able to run hashcat on Intel Xeon X5482 CPU, because the processor is old. I've asked similar question about 2 years ago. Hash.Type.: TrueCrypt PBKDF2-HMAC-SHA512 + XTS 512 bit Unless you supply more work, your cracking speed will drop.Īpproaching final keyspace - workload adjusted. This means that hashcat cannot use the full parallel power of your device(s). The wordlist or mask that you are using is too small. ![]() Watchdog: Temperature abort trigger set to 90c Maximum password length supported by kernel: 64 Minimum password length supported by kernel: 0 Hashes: 1 digests 1 unique digests, 1 unique saltsīitmaps: 16 bits, 65536 entries, 0x0000ffff mask, 262144 bytes, 5/13 rotates OpenCL Platform #2: Advanced Micro Devices, Inc. ![]() * Device #1: GeForce GTX 780 Ti, 768/3072 MB allocatable, 15MCU NvmlDeviceGetUtilizationRates(): Not Supported NvmlDeviceGetTemperatureThreshold(): Not Supported NvmlDeviceGetCurrPcieLinkWidth(): Not Supported You can use -force to override, but do not report related errors. * Device #2: Not a native Intel OpenCL runtime. This may cause "CL_OUT_OF_RESOURCES" or related errors. * Device #1: WARNING! Kernel exec timeout is not disabled. * Device #1: This hardware has outdated CUDA compute capability (3.5).įor modern OpenCL performance, upgrade to hardware that supportsĬUDA compute capability version 5.0 (Maxwell) or higher. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |