Issues with p106-090 pg410 driver and hashcat 6.1.1 - Printable Version +- hashcat Forum (https://hashcat.net/forum) +-- Forum: Misc (https://hashcat.net/forum/forum-15.html) +--- Forum: Hardware (https://hashcat.net/forum/forum-13.html) +--- Thread: Issues with p106-090 pg410 driver and hashcat 6.1.1 (/thread-9471.html) |
Issues with p106-090 pg410 driver and hashcat 6.1.1 - SquirrelHasher - 08-26-2020 Hello, can anyone help me to find p106-090 pg410 driver which would work correctly with hashcat 6.1.1. I have used 388.59 driver but hashcat 6.1.1 informing me about issues with CUDA and the speed is much slower then with hashcat 5.1.0. Can someone help me?) RE: Issues with p106-090 pg410 driver and hashcat 6.1.1 - philsmd - 08-26-2020 is this some kind of cloud provider ? what is the output of hashcat -I ? what is the output of clinfo ? RE: Issues with p106-090 pg410 driver and hashcat 6.1.1 - SquirrelHasher - 08-27-2020 (08-26-2020, 06:23 PM)philsmd Wrote: is this some kind of cloud provider ? Device #1: Unstable OpenCL driver detected! * Device #2: CUDA SDK Toolkit installation NOT detected. CUDA SDK Toolkit installation required for proper device support and utilization Falling back to OpenCL Runtime * Device #3: CUDA SDK Toolkit installation NOT detected. CUDA SDK Toolkit installation required for proper device support and utilization Falling back to OpenCL Runtime * Device #4: CUDA SDK Toolkit installation NOT detected. CUDA SDK Toolkit installation required for proper device support and utilization Falling back to OpenCL Runtime * Device #5: CUDA SDK Toolkit installation NOT detected. CUDA SDK Toolkit installation required for proper device support and utilization Falling back to OpenCL Runtime * Device #6: CUDA SDK Toolkit installation NOT detected. CUDA SDK Toolkit installation required for proper device support and utilization Falling back to OpenCL Runtime * Device #7: CUDA SDK Toolkit installation NOT detected. CUDA SDK Toolkit installation required for proper device support and utilization Falling back to OpenCL Runtime OpenCL Info: ============ OpenCL Platform ID #1 Vendor..: Intel(R) Corporation Name....: Intel(R) OpenCL HD Graphics Version.: OpenCL 2.1 Backend Device ID #1 Type...........: GPU Vendor.ID......: 8 Vendor.........: Intel(R) Corporation Name...........: Intel(R) HD Graphics 510 Version........: OpenCL 2.1 NEO Processor(s)...: 12 Clock..........: 1000 Memory.Total...: 1593 MB (limited to 796 MB allocatable in one block) Memory.Free....: 1529 MB OpenCL.Version.: OpenCL C 2.0 Driver.Version.: 27.20.100.7990 OpenCL Platform ID #2 Vendor..: NVIDIA Corporation Name....: NVIDIA CUDA Version.: OpenCL 1.2 CUDA 9.1.104 Backend Device ID #2 Type...........: GPU Vendor.ID......: 32 Vendor.........: NVIDIA Corporation Name...........: P106-090 Version........: OpenCL 1.2 CUDA Processor(s)...: 5 Clock..........: 1531 Memory.Total...: 3006 MB (limited to 751 MB allocatable in one block) Memory.Free....: 2880 MB OpenCL.Version.: OpenCL C 1.2 Driver.Version.: 388.59 Backend Device ID #3 Type...........: GPU Vendor.ID......: 32 Vendor.........: NVIDIA Corporation Name...........: P106-090 Version........: OpenCL 1.2 CUDA Processor(s)...: 5 Clock..........: 1531 Memory.Total...: 3006 MB (limited to 751 MB allocatable in one block) Memory.Free....: 2880 MB OpenCL.Version.: OpenCL C 1.2 Driver.Version.: 388.59 Backend Device ID #4 Type...........: GPU Vendor.ID......: 32 Vendor.........: NVIDIA Corporation Name...........: P106-090 Version........: OpenCL 1.2 CUDA Processor(s)...: 5 Clock..........: 1531 Memory.Total...: 3006 MB (limited to 751 MB allocatable in one block) Memory.Free....: 2880 MB OpenCL.Version.: OpenCL C 1.2 Driver.Version.: 388.59 Backend Device ID #5 Type...........: GPU Vendor.ID......: 32 Vendor.........: NVIDIA Corporation Name...........: P106-090 Version........: OpenCL 1.2 CUDA Processor(s)...: 5 Clock..........: 1531 Memory.Total...: 3006 MB (limited to 751 MB allocatable in one block) Memory.Free....: 2880 MB OpenCL.Version.: OpenCL C 1.2 Driver.Version.: 388.59 Backend Device ID #6 Type...........: GPU Vendor.ID......: 32 Vendor.........: NVIDIA Corporation Name...........: P106-090 Version........: OpenCL 1.2 CUDA Processor(s)...: 5 Clock..........: 1531 Memory.Total...: 3006 MB (limited to 751 MB allocatable in one block) Memory.Free....: 2880 MB OpenCL.Version.: OpenCL C 1.2 Driver.Version.: 388.59 Backend Device ID #7 Type...........: GPU Vendor.ID......: 32 Vendor.........: NVIDIA Corporation Name...........: P106-090 Version........: OpenCL 1.2 CUDA Processor(s)...: 5 Clock..........: 1531 Memory.Total...: 3006 MB (limited to 751 MB allocatable in one block) Memory.Free....: 2880 MB OpenCL.Version.: OpenCL C 1.2 Driver.Version.: 388.59 RE: Issues with p106-090 pg410 driver and hashcat 6.1.1 - SquirrelHasher - 08-27-2020 (08-26-2020, 06:23 PM)philsmd Wrote: is this some kind of cloud provider ? No) p106-090 pg410 is Nvidia graphic card. And I am using Windows, so I guess I have no clinfo. RE: Issues with p106-090 pg410 driver and hashcat 6.1.1 - philsmd - 08-27-2020 There are even clinfo.exe binary releases here for users that are not able to compile it themself: https://github.com/Oblomov/clinfo#windows-support RE: Issues with p106-090 pg410 driver and hashcat 6.1.1 - philsmd - 08-27-2020 I think this is not really an error, you are just not aware (misunderstanding) that hashcat 6.0.0 and above recommend using CUDA. I'm not sure if your "professional" GPU supports it (I pretty much would assume so, otherwise it wouldn't make sense to buy these professional cards that are mostly used in some datacenters - or of course a few years ago in mining rigs etc - and by cloud providers etc, but of course there are exceptions). Download CUDA from https://developer.nvidia.com/cuda-downloads and the warning message will disappear if you correclty installed it. RE: Issues with p106-090 pg410 driver and hashcat 6.1.1 - SquirrelHasher - 08-27-2020 (08-27-2020, 09:19 AM)philsmd Wrote: I think this is not really an error, you are just not aware (misunderstanding) that hashcat 6.0.0 and above recommend using CUDA.Yes, thank you for reply. This error appeared only on one machine. I just reinstalled the CUDA toolkit on it. And the error has disappeared. Thanks for help) |