Please note, this is a STATIC archive of website hashcat.net from October 2020, cach3.com does not collect or store any user information, there is no "phishing" involved.

hashcat Forum

Full Version: Run 3 opencl devices at once
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
Hello,can someone tell me,how do i run this:


Device #1: Intel(R) UHD Graphics Coffee Lake Halo GT2, skipped.

OpenCL Platform #2: NVIDIA Corporation
======================================
* Device #2: GeForce GTX 1050, 1010/4040 MB allocatable, 5MCU

OpenCL Platform #3: Intel(R) Corporation
========================================
* Device #3: Intel(R) Core(TM) i7-8750H CPU @ 2.20GHz, skipped.

OpenCL Platform #4: Intel(R) Corporation
========================================
* Device #4: Intel(R) Core(TM) i7-8750H CPU @ 2.20GHz, skipped.

OpenCL Platform #5: The pocl project
====================================
* Device #5: pthread-Intel(R) Core(TM) i7-8750H CPU @ 2.20GHz, skipped.

Thanks!
What are you trying to do?
By default, hashcat only uses GPUs when available. You can modify that with these flags.

Code:
$ hashcat --help | grep opencl-device
-d, --opencl-devices           | Str  | OpenCL devices to use, separated with commas         | -d 1
-D, --opencl-device-types      | Str  | OpenCL device-types to use, separated with commas    | -D 1

$ hashcat --help | grep -A 4 Device
- [ OpenCL Device Types ] -

  # | Device Type
===+=============
  1 | CPU
  2 | GPU
  3 | FPGA, DSP, Co-Processor
i think --force would be work

try add --force
No, --force would have no effect on not skipping a given platform. Only -D and -d will do that.
(11-10-2018, 11:46 PM)erikass Wrote: [ -> ]i think --force would be work

try add --force

Never use --force to resolve an issue, there's a reason hashcat isn't for the simple minded.

He just needs to enable the devices using -d 1,2,3,4 which will tell hashcat NOT to skip those devices.
In order to use CPU devices, you need -D 1. In order to use CPU+GPU, you need to use -D 1,2 instead. Do not use -d in this case because you would enable opencl runtimes for the same device but with less dedicated instruction support. It's unclear if -D 1,2 works faster in non-brute force mode because of the 100% cpu bug on NV.
Ah, I didn't know about the instruction consequences of using -d. Interesting.
Thanks a lot to everyone.
2 royce ,2 Atom - with you help problem solved ,it was -D 1,2.
It possible to close the thread.