+- hashcat Forum (https://hashcat.net/forum)
+-- Forum: Support (https://hashcat.net/forum/forum-3.html)
+--- Forum: hashcat (https://hashcat.net/forum/forum-45.html)
+--- Thread: Hashcat 6.1.1 Upgrade Broke My Install (/thread-9446.html)
Hashcat 6.1.1 Upgrade Broke My Install - Dawbs - 08-09-2020
Hi,
I had been running HC 6 beta and then 6.0.0 with no problems. Installed all the CUDA drivers & everything was fine except for a CPU error (outdated pocl) which just notified in red but still ran fine.
I upgraded to 6.1.1 a few days ago and ever since then every time I start hashcat it hangs for about 45 seconds after displaying (in yellow):
`Benchmarking uses hand-optimized kernel code by default.
You can use it in your cracking session by setting the -O option.
Note: Using optimized kernel code limits the maximum supported password length.
To disable the optimized kernel code in benchmark mode, use the -w option.`
It then continues to run fine but does now also has a delay if I either q out or press ^c
I have updated the CPU driver (No longer shows red) / Uninstalled HC & reinstalled both 6.0.0 & 6.1.1 but still hangs for 45 seconds.
Tried running with both --backend-ignore-opencl which makes no difference & --backend-ignore-cuda which still takes 45 seconds but now displays (in yellow):
Device #1: CUDA SDK Toolkit installation NOT detected.
CUDA SDK Toolkit installation required for proper device support and utilization
Falling back to OpenCL Runtime
Device #2: CUDA SDK Toolkit installation NOT detected.
CUDA SDK Toolkit installation required for proper device support and utilization
Falling back to OpenCL Runtime
and the same for Device 3, 4
Any advice before I wipe the whole machine & start all over again?
Many thanks in advance
Additional info:
O/S: Ubuntu 20.04
Full (startup) output of hashcat
hashcat (v6.0.0) starting in benchmark mode...
Benchmarking uses hand-optimized kernel code by default.
You can use it in your cracking session by setting the -O option.
Note: Using optimized kernel code limits the maximum supported password length.
To disable the optimized kernel code in benchmark mode, use the -w option.
***HANGS AT THIS POINT FOR 45 SECONDS***
CUDA API (CUDA 9.1)
===================
* Device #1: GeForce GTX 1080 Ti, 10997/11177 MB, 28MCU
* Device #2: GeForce GTX 1080 Ti, 11015/11178 MB, 28MCU
* Device #3: GeForce GTX 1080 Ti, 11015/11178 MB, 28MCU
* Device #4: GeForce GTX 1080 Ti, 11015/11178 MB, 28MCU
OpenCL API (OpenCL 1.2 CUDA 9.1.84) - Platform #1 [NVIDIA Corporation]
======================================================================
* Device #5: GeForce GTX 1080 Ti, skipped
* Device #6: GeForce GTX 1080 Ti, skipped
* Device #7: GeForce GTX 1080 Ti, skipped
* Device #8: GeForce GTX 1080 Ti, skipped
OpenCL API (OpenCL 2.1 LINUX) - Platform #2 [Intel(R) Corporation]
==================================================================
* Device #9: Intel(R) Xeon(R) CPU E7- 4860 @ 2.27GHz, skipped
Benchmark relevant options:
===========================
* --optimized-kernel-enable
Hashmode: 0 - MD5
RE: Hashcat 6.1.1 Upgrade Broke My Install - ZerBea - 08-10-2020
remove
$HOME/.nv
$HOME/.hashcat
and try again.
BTW:
Your CUDA API (CUDA 9.1) is very, very old - we are on CUDA 11 and NVIDIA 450.57
Code:
$ hashcat -I
hashcat (v6.1.1-20-gdc9a2468) starting...
CUDA Info:
==========
CUDA.Version.: 11.0
$ pacman -Q | grep cuda
cuda 11.0.2-1
$ pacman -Q | grep nvidia
nvidia 450.57-6
nvidia-settings 450.57-1
nvidia-utils 450.57-2
opencl-nvidia 450.57-2RE: Hashcat 6.1.1 Upgrade Broke My Install - Dawbs - 08-10-2020
Many thanks. I have been removing as many OpenCL & CUDA drivers as possible & will re-install the latests.
I removed the /.hashcat but not the /.nv I will try rhat and report back.
Regards.
RE: Hashcat 6.1.1 Upgrade Broke My Install - Dawbs - 08-15-2020
Well linux became unstable and the repo's all got corrupted. Rebuilt with Cuda 11 and works perfect now.
Thanks for the note about Cuda @zerbea. I missed that completely.
RE: Hashcat 6.1.1 Upgrade Broke My Install - ZerBea - 08-15-2020
Glad to hear that.
Most of the problems (nearly all) are related to old distribution versions (inclusive old drivers), broken package system or misconfiguration (inexperienced Linux users). Luckily this can be easy fixed.