+- 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: timeout patch hangs ubuntu 22.04 on boot (/thread-11216.html)
timeout patch hangs ubuntu 22.04 on boot - toner - 12-26-2022
Good afternoon everybody, trying to turn a 12x 3070 mining rig into a hashcat machine. I have installed hashcat, nvdia cuda toolkit, etc and when I run hashcat -b I get the following errors. I have also tried the timeout patch https://hashcat.net/wiki/doku.php?id=timeout_patch but then ubtuntu won't boot (hangs on logo screen) and I need to recovery/terminal in, delete the 20-nvidia.conf file I made, reboot, then ubuntu boots again. Not sure what I am doing wrong here. Thanks!
hashcat -b
hashcat (v6.2.5) 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.
* Device #1: WARNING! Kernel exec timeout is not disabled.
This may cause "CL_OUT_OF_RESOURCES" or related errors.
To disable the timeout, see: https://hashcat.net/q/timeoutpatch
* Device #2: WARNING! Kernel exec timeout is not disabled.
This may cause "CL_OUT_OF_RESOURCES" or related errors.
To disable the timeout, see: https://hashcat.net/q/timeoutpatch
* Device #3: WARNING! Kernel exec timeout is not disabled.
This may cause "CL_OUT_OF_RESOURCES" or related errors.
To disable the timeout, see: https://hashcat.net/q/timeoutpatch
* Device #4: WARNING! Kernel exec timeout is not disabled.
This may cause "CL_OUT_OF_RESOURCES" or related errors.
To disable the timeout, see: https://hashcat.net/q/timeoutpatch
* Device #5: WARNING! Kernel exec timeout is not disabled.
This may cause "CL_OUT_OF_RESOURCES" or related errors.
To disable the timeout, see: https://hashcat.net/q/timeoutpatch
* Device #6: WARNING! Kernel exec timeout is not disabled.
This may cause "CL_OUT_OF_RESOURCES" or related errors.
To disable the timeout, see: https://hashcat.net/q/timeoutpatch
* Device #7: WARNING! Kernel exec timeout is not disabled.
This may cause "CL_OUT_OF_RESOURCES" or related errors.
To disable the timeout, see: https://hashcat.net/q/timeoutpatch
* Device #8: WARNING! Kernel exec timeout is not disabled.
This may cause "CL_OUT_OF_RESOURCES" or related errors.
To disable the timeout, see: https://hashcat.net/q/timeoutpatch
* Device #9: WARNING! Kernel exec timeout is not disabled.
This may cause "CL_OUT_OF_RESOURCES" or related errors.
To disable the timeout, see: https://hashcat.net/q/timeoutpatch
* Device #10: WARNING! Kernel exec timeout is not disabled.
This may cause "CL_OUT_OF_RESOURCES" or related errors.
To disable the timeout, see: https://hashcat.net/q/timeoutpatch
* Device #11: WARNING! Kernel exec timeout is not disabled.
This may cause "CL_OUT_OF_RESOURCES" or related errors.
To disable the timeout, see: https://hashcat.net/q/timeoutpatch
* Device #12: WARNING! Kernel exec timeout is not disabled.
This may cause "CL_OUT_OF_RESOURCES" or related errors.
To disable the timeout, see: https://hashcat.net/q/timeoutpatch
* Device #13: WARNING! Kernel exec timeout is not disabled.
This may cause "CL_OUT_OF_RESOURCES" or related errors.
To disable the timeout, see: https://hashcat.net/q/timeoutpatch
* Device #14: WARNING! Kernel exec timeout is not disabled.
This may cause "CL_OUT_OF_RESOURCES" or related errors.
To disable the timeout, see: https://hashcat.net/q/timeoutpatch
* Device #15: WARNING! Kernel exec timeout is not disabled.
This may cause "CL_OUT_OF_RESOURCES" or related errors.
To disable the timeout, see: https://hashcat.net/q/timeoutpatch
* Device #16: WARNING! Kernel exec timeout is not disabled.
This may cause "CL_OUT_OF_RESOURCES" or related errors.
To disable the timeout, see: https://hashcat.net/q/timeoutpatch
* Device #17: WARNING! Kernel exec timeout is not disabled.
This may cause "CL_OUT_OF_RESOURCES" or related errors.
To disable the timeout, see: https://hashcat.net/q/timeoutpatch
* Device #18: WARNING! Kernel exec timeout is not disabled.
This may cause "CL_OUT_OF_RESOURCES" or related errors.
To disable the timeout, see: https://hashcat.net/q/timeoutpatch
* Device #19: WARNING! Kernel exec timeout is not disabled.
This may cause "CL_OUT_OF_RESOURCES" or related errors.
To disable the timeout, see: https://hashcat.net/q/timeoutpatch
* Device #20: WARNING! Kernel exec timeout is not disabled.
This may cause "CL_OUT_OF_RESOURCES" or related errors.
To disable the timeout, see: https://hashcat.net/q/timeoutpatch
* Device #21: WARNING! Kernel exec timeout is not disabled.
This may cause "CL_OUT_OF_RESOURCES" or related errors.
To disable the timeout, see: https://hashcat.net/q/timeoutpatch
* Device #22: WARNING! Kernel exec timeout is not disabled.
This may cause "CL_OUT_OF_RESOURCES" or related errors.
To disable the timeout, see: https://hashcat.net/q/timeoutpatch
* Device #23: WARNING! Kernel exec timeout is not disabled.
This may cause "CL_OUT_OF_RESOURCES" or related errors.
To disable the timeout, see: https://hashcat.net/q/timeoutpatch
* Device #24: WARNING! Kernel exec timeout is not disabled.
This may cause "CL_OUT_OF_RESOURCES" or related errors.
To disable the timeout, see: https://hashcat.net/q/timeoutpatch
CUDA API (CUDA 12.0)
====================
* Device #1: NVIDIA GeForce RTX 3070, 7811/7973 MB, 46MCU
* Device #2: NVIDIA GeForce RTX 3070, 7811/7973 MB, 46MCU
* Device #3: NVIDIA GeForce RTX 3070, 7811/7973 MB, 46MCU
* Device #4: NVIDIA GeForce RTX 3070, 7811/7973 MB, 46MCU
* Device #5: NVIDIA GeForce RTX 3070, 7811/7973 MB, 46MCU
* Device #6: NVIDIA GeForce RTX 3070, 7811/7973 MB, 46MCU
* Device #7: NVIDIA GeForce RTX 3070, 7811/7973 MB, 46MCU
* Device #8: NVIDIA GeForce RTX 3070, 7811/7973 MB, 46MCU
* Device #9: NVIDIA GeForce RTX 3070, 7811/7973 MB, 46MCU
* Device #10: NVIDIA GeForce RTX 3070, 7811/7973 MB, 46MCU
* Device #11: NVIDIA GeForce RTX 3070, 7811/7973 MB, 46MCU
* Device #12: NVIDIA GeForce RTX 3070, 7811/7973 MB, 46MCU
OpenCL API (OpenCL 3.0 CUDA 12.0.89) - Platform #1 [NVIDIA Corporation]
=======================================================================
* Device #13: NVIDIA GeForce RTX 3070, skipped
* Device #14: NVIDIA GeForce RTX 3070, skipped
* Device #15: NVIDIA GeForce RTX 3070, skipped
* Device #16: NVIDIA GeForce RTX 3070, skipped
* Device #17: NVIDIA GeForce RTX 3070, skipped
* Device #18: NVIDIA GeForce RTX 3070, skipped
* Device #19: NVIDIA GeForce RTX 3070, skipped
* Device #20: NVIDIA GeForce RTX 3070, skipped
* Device #21: NVIDIA GeForce RTX 3070, skipped
* Device #22: NVIDIA GeForce RTX 3070, skipped
* Device #23: NVIDIA GeForce RTX 3070, skipped
* Device #24: NVIDIA GeForce RTX 3070, skipped
Benchmark relevant options:
===========================
* --optimized-kernel-enable
-------------------
* Hash-Mode 0 (MD5)
-------------------
Killed
this is what i tried for the "patch" that caused no boot to login screen:
Newer versions of Ubuntu (and maybe other distributions as well) do not use xorg.conf any longer. Alternatively they use the folder /usr/share/X11/xorg.conf.d/ where you can put in snippets of the config. Create a new file, call it “20-nvidia.conf” and put in the following content:
ection "Device"
Identifier "MyGPU"
Driver "nvidia"
Option "Interactive" "0"
EndSection
You may need to restart the system afterwards.
RE: timeout patch hangs ubuntu 22.04 on boot - toner - 12-26-2022
If I run hashcat with the -d 1,2,3,4,5,6,7,8,9,0,1,12 then it works but still shows the error at start about the possible CL OUT OF RESOURCES, I'll let her rip like this and see what happens
