Nvidia GTX GPU not working
#1
Hi guys,

pretty new here

so im having problems with running hashcat with my Nvidia graphics, currently running 1 Titan X Pascal

i have installed these:

//The-Distribution-Which-Does-Not-Handle-OpenCL-Well (Kali) setup
apt-get install nvidia-kernel-dkms
sed 's/quiet/quiet nouveau.modeset=0/g' -i /etc/default/grub
///////////////////////////////////////////////////////////////////

apt install nvidia-opencl-icd
apt install nvidia-cuda-toolkit nvidia-opencl-icd
apt install libxnvctrl-dev
apt install nvidia-opencl-dev
apt install libgmp3-dev
apt install libgmp10-doc
apt install opencl-headers
apt-get install nvidia-xconfig
apt-get install nvidia-settings
nvidia-xconfig
apt-get install nvidia-kernel-$(uname -r)
apt-get install nvidia-detect
apt-get install nvidia-libopencl1
apt-get install gtk2.0

apt-get install nvidia-cuda-*

also tried changing the xorg.config file but im still unable to run hashcat with my GPU why???? very frustrated

right now nothing seems to want to run with the GPU, although i have check that it renders

Please help... or maybe suggest alternatives

ThanksSmile

Scatchy
#2
(12-30-2016, 02:05 PM)Scatchy Wrote: Hi guys,

pretty new here

so im having problems with running hashcat with my Nvidia graphics, currently running 1 Titan X Pascal

i have installed these:

//The-Distribution-Which-Does-Not-Handle-OpenCL-Well (Kali) setup
apt-get install nvidia-kernel-dkms
sed 's/quiet/quiet nouveau.modeset=0/g' -i /etc/default/grub
///////////////////////////////////////////////////////////////////

apt install nvidia-opencl-icd
apt install nvidia-cuda-toolkit nvidia-opencl-icd
apt install libxnvctrl-dev
apt install nvidia-opencl-dev
apt install libgmp3-dev
apt install libgmp10-doc
apt install opencl-headers
apt-get install nvidia-xconfig
apt-get install nvidia-settings
nvidia-xconfig
apt-get install nvidia-kernel-$(uname -r)
apt-get install nvidia-detect
apt-get install nvidia-libopencl1
apt-get install gtk2.0

apt-get install nvidia-cuda-*

also tried changing the xorg.config file but im still unable to run hashcat with my GPU why???? very frustrated

right now nothing seems to want to run with the GPU, although i have check that it renders

Please help... or maybe suggest alternatives

ThanksSmile

Scatchy
https://hashcat.net/wiki/doku.php?id=fre...hould_i_do

also u remove cuda, since u dont need it
#3
apt-get update
apt-get dist-upgrade
apt-get install -y linux-headers-$(uname -r)
sed 's/quiet/quiet nouveau.modeset=0/g' -i /etc/default/grub
chmod +xNVIDIA-Linux-x86_64-375.26.run
update-grub
reboot
./NVIDIA-Linux-x86_64-375.26.run
#4
You can also run hashcat on windows
#5
(12-30-2016, 02:44 PM)xiaobai Wrote: apt-get update
apt-get dist-upgrade
apt-get install -y linux-headers-$(uname -r)
sed 's/quiet/quiet nouveau.modeset=0/g' -i /etc/default/grub
chmod +xNVIDIA-Linux-x86_64-375.26.run
update-grub
reboot
./NVIDIA-Linux-x86_64-375.26.run

everything is updated but when i get to the installer it says im already running nvidia-dkms, nvidia kernel
and says installation failed
#6
i dont know why, running hashcat --benchmark works with the GPU but when i execute it with the files

gives me this

hashcat (v3.10) starting...

OpenCL Platform #1: NVIDIA Corporation
======================================
- Device #1: TITAN X (Pascal), 3047/12189 MB allocatable, 28MCU
- Device #1: WARNING! Kernel exec timeout is not disabled, it might cause you errors of code 702
See the wiki on how to disable it: https://hashcat.net/wiki/doku.php?id=timeout_patch

OpenCL Platform #2: Mesa, skipped! No OpenCL compatible devices found

Hashes: 1 hashes; 1 unique digests, 1 unique salts
Bitmaps: 16 bits, 65536 entries, 0x0000ffff mask, 262144 bytes, 5/13 rotates
Rules: 1
Applicable Optimizers:
* Zero-Byte
* Single-Hash
* Single-Salt
* Slow-Hash-SIMD
Watchdog: Temperature abort trigger set to 90c
Watchdog: Temperature retain trigger set to 75c

- Device #1: Kernel m02500.8da3f9da.kernel not found in cache! Building may take a while...
- Device #1: Kernel amp_a0.8da3f9da.kernel not found in cache! Building may take a while...

WARNING: Failed to set initial fan speed for device #1
Cache-hit dictionary stats /root/Documents/The-Distribution-Which-Does-Not-Handle-OpenCL-Well (Kali)/Dictionary/darkc0de.lst: 17975854 bytes, 1707612 words, 1707612 keyspace

INFO: approaching final keyspace, workload adjusted


Session.Name...: hashcat
Status.........: Exhausted
#7
(12-30-2016, 11:49 PM)Scatchy Wrote: i dont know why, running hashcat --benchmark works with the GPU but when i execute it with the files

gives me this

hashcat (v3.10) starting...

OpenCL Platform #1: NVIDIA Corporation  
======================================
- Device #1: TITAN X (Pascal), 3047/12189 MB allocatable, 28MCU
- Device #1: WARNING! Kernel exec timeout is not disabled, it might cause you errors of code 702
            See the wiki on how to disable it: https://hashcat.net/wiki/doku.php?id=timeout_patch

OpenCL Platform #2: Mesa, skipped! No OpenCL compatible devices found

Hashes: 1 hashes; 1 unique digests, 1 unique salts
Bitmaps: 16 bits, 65536 entries, 0x0000ffff mask, 262144 bytes, 5/13 rotates
Rules: 1
Applicable Optimizers:
* Zero-Byte
* Single-Hash
* Single-Salt
* Slow-Hash-SIMD
Watchdog: Temperature abort trigger set to 90c
Watchdog: Temperature retain trigger set to 75c

- Device #1: Kernel m02500.8da3f9da.kernel not found in cache! Building may take a while...
- Device #1: Kernel amp_a0.8da3f9da.kernel not found in cache! Building may take a while...

WARNING: Failed to set initial fan speed for device #1
Cache-hit dictionary stats /root/Documents/The-Distribution-Which-Does-Not-Handle-OpenCL-Well (Kali)/Dictionary/darkc0de.lst: 17975854 bytes, 1707612 words, 1707612 keyspace

INFO: approaching final keyspace, workload adjusted      

                                                         
Session.Name...: hashcat
Status.........: Exhausted

I'm kinda new here so take my advice with a grain of salt.  It would help me to see the parameters you used to launch hashcat.  A keyspace of 1.7 million on your card should only take seconds.  The status "exhausted" may mean it completed without finding a match.
#8
(12-31-2016, 12:09 AM)duhblow7 Wrote:
(12-30-2016, 11:49 PM)Scatchy Wrote: i dont know why, running hashcat --benchmark works with the GPU but when i execute it with the files

gives me this

hashcat (v3.10) starting...

OpenCL Platform #1: NVIDIA Corporation  
======================================
- Device #1: TITAN X (Pascal), 3047/12189 MB allocatable, 28MCU
- Device #1: WARNING! Kernel exec timeout is not disabled, it might cause you errors of code 702
            See the wiki on how to disable it: https://hashcat.net/wiki/doku.php?id=timeout_patch

OpenCL Platform #2: Mesa, skipped! No OpenCL compatible devices found

Hashes: 1 hashes; 1 unique digests, 1 unique salts
Bitmaps: 16 bits, 65536 entries, 0x0000ffff mask, 262144 bytes, 5/13 rotates
Rules: 1
Applicable Optimizers:
* Zero-Byte
* Single-Hash
* Single-Salt
* Slow-Hash-SIMD
Watchdog: Temperature abort trigger set to 90c
Watchdog: Temperature retain trigger set to 75c

- Device #1: Kernel m02500.8da3f9da.kernel not found in cache! Building may take a while...
- Device #1: Kernel amp_a0.8da3f9da.kernel not found in cache! Building may take a while...

WARNING: Failed to set initial fan speed for device #1
Cache-hit dictionary stats /root/Documents/The-Distribution-Which-Does-Not-Handle-OpenCL-Well (Kali)/Dictionary/darkc0de.lst: 17975854 bytes, 1707612 words, 1707612 keyspace

INFO: approaching final keyspace, workload adjusted      

                                                         
Session.Name...: hashcat
Status.........: Exhausted

I'm kinda new here so take my advice with a grain of salt.  It would help me to see the parameters you used to launch hashcat.  A keyspace of 1.7 million on your card should only take seconds.  The status "exhausted" may mean it completed without finding a match.

so i reinstalled xserver and its now ligthdm restarted it also rebooted the system, also installed intel drivers so hash now recognizes it

what im getting is
clGetDeviceIDs(): CL_DEVICE_NOT_FOUND


this is my input and outputs

root@The-Distribution-Which-Does-Not-Handle-OpenCL-Well (Kali):~/Documents/The-Distribution-Which-Does-Not-Handle-OpenCL-Well (Kali)/hashcat-3.20# ./hashcat64.bin -m 2500 '/root/Documents/The-Distribution-Which-Does-Not-Handle-OpenCL-Well (Kali)/AP/Optus_25444A/done.hccap' '/root/Documents/The-Distribution-Which-Does-Not-Handle-OpenCL-Well (Kali)/Dictionary/darkc0de.lst'
hashcat (v3.20) starting...

clGetDeviceIDs(): CL_DEVICE_NOT_FOUND

clGetDeviceIDs(): CL_DEVICE_NOT_FOUND

OpenCL Platform #1: NVIDIA Corporation
======================================
* Device #1: TITAN X (Pascal), 2047/12189 MB allocatable, 28MCU

OpenCL Platform #2: Intel(R) Corporation
========================================
* Device #2: Intel(R) Core(TM) i7-6700K CPU @ 4.00GHz, skipped

OpenCL Platform #3: Mesa, skipped or no OpenCL compatible devices found

Hashes: 1 digests; 1 unique digests, 1 unique salts
Bitmaps: 16 bits, 65536 entries, 0x0000ffff mask, 262144 bytes, 5/13 rotates
Rules: 1

Applicable Optimizers:
* Zero-Byte
* Single-Hash
* Single-Salt
* Slow-Hash-SIMD

Watchdog: Temperature abort trigger set to 90c
Watchdog: Temperature retain trigger set to 75c

Cache-hit dictionary stats /root/Documents/The-Distribution-Which-Does-Not-Handle-OpenCL-Well (Kali)/Dictionary/darkc0de.lst: 17975854 bytes, 1707612 words, 1707612 keyspace

INFO: approaching final keyspace, workload adjusted       

Session..........: hashcat                                
Status...........: Exhausted
Hash.Type........: WPA/WPA2
Hash.Target......: OPTUS_25444A (90:72:82:25:44:4b <-> 60:f8:1d:11:20:fe)
Time.Started.....: Sat Dec 31 09:42:04 2016 (3 secs)
Time.Estimated...: Sat Dec 31 09:42:07 2016 (0 secs)
Input.Base.......: File (/root/Documents/The-Distribution-Which-Does-Not-Handle-OpenCL-Well (Kali)/Dictionary/darkc0de.lst)
Input.Queue......: 1/1 (100.00%)
Speed.Dev.#1.....:   517.4 kH/s (4.86ms)
Recovered........: 0/1 (0.00%) Digests, 0/1 (0.00%) Salts
Progress.........: 1707612/1707612 (100.00%)
Rejected.........: 559595/1707612 (32.77%)
Restore.Point....: 1707612/1707612 (100.00%)
Candidates.#1....: $HEX[73636173736163617a7a69] -> $HEX[887465706574887465]
HWMon.Dev.#1.....: Temp: 51c Fan: 33% Util: 94% Core:1771Mhz Mem:4513Mhz Lanes:16

Started: Sat Dec 31 09:42:03 2016
Stopped: Sat Dec 31 09:42:07 2016
#9
I'm not sure why it is throwing that error but hashcat ran.  It only took 3 seconds to run through your password list of 1.7 million and it did not find a match.

The default for most OPTUS routers is 20 characters.  The first 15 are capital A-Z and the last 5 are numeric.

A mask of:

?u?u?u?u?u?u?u?u?u?u?u?u?u?u?u?d?d?d?d?d

should cover it but it is a huge keyspace.
#10
(12-31-2016, 01:30 AM)duhblow7 Wrote: I'm not sure why it is throwing that error but hashcat ran.  It only took 3 seconds to run through your password list of 1.7 million and it did not find a match.

The default for most OPTUS routers is 20 characters.  The first 15 are capital A-Z and the last 5 are numeric.

A mask of:

?u?u?u?u?u?u?u?u?u?u?u?u?u?u?u?d?d?d?d?d

should cover it but it is a huge keyspace.

thanks for the help guys its working but i cant seem to figure out why it has a CL_DEVICE_NOT_FOUND

and im getting a really really low hash rate of average 500kH/s

any thoughts?