hashcat Forum
Warnings in hashcat v3 not present in cudaHashcat v2.01 - should I care? - Printable Version

+- 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: Warnings in hashcat v3 not present in cudaHashcat v2.01 - should I care? (/thread-5681.html)

Pages: 1 2

RE: Warnings in hashcat v3 not present in cudaHashcat v2.01 - should I care? - voideater - 07-27-2016

Sure. Setup is

2x Intel(R) Xeon(R) CPU E5-2603 v3
32GB DDR4
3x NVIDIA GeForce GTX 980 Ti

I assume kernel is 4.4.0-31-generic, but since I'm no expert in the Linux world;
uname-a: 4.4.0.-31-linux-generic
cat /proc/version_signature: 4.4.0-31.50-generic 4.4.13
Only used NVIDIA driver 367.35 so far.

I've tried now with both (desktop) 14.04 TLS and (server) 16.04 TLS, and on both versions hashcat v3.0 issues these warnings (and won't retain the temperature specified with the flag**), whereas cudaHashcat v2.01 works just fine without issuing any warnings, which is frustrating since everything else is the same; drivers; installed libraries, etc.

If I set gpu-temp-retain=0, hashcat prints this during the initial phase;
Watchdog: Temperature abort trigger set to 90c
Watchdog: Temperature retain trigger set to 75c

While running under these settings, the temperatures stabilize at about {76c/77c | 83c | 78c/79c} ({device0|device1|device2}).

Some times setting gpu-retain-flag=0 (or a small number) results in no warnings about initial fan speed, but other times the warnings are issued. Kinda confusing.

But just to be clear about it, system works and is stable at the temperatures I've mentioned above (e.g. getting about 18791 MH/s total for all three devices for SHA1 during benchmark and about 17000 MH/s for brute force attack on unsalted SHA1; not sure how that is compared to tuned setups with the same devices, but at least it does the job for my need atm). So in that sense, this isn't a "big" deal, but it'd be nice to find out what causes this and how it can be "fixed". Obviously something isn't as it should be.

RE: Warnings in hashcat v3 not present in cudaHashcat v2.01 - should I care? - atom - 07-27-2016

Please post your xorg.conf

RE: Warnings in hashcat v3 not present in cudaHashcat v2.01 - should I care? - voideater - 07-27-2016

Here you go

Code:
cat /etc/X11/xorg.conf
# nvidia-xconfig: X configuration file generated by nvidia-xconfig
# nvidia-xconfig:  version 367.35  (buildmeister@swio-display-x64-rhel04-01)  Mon Jul 11 23:51:45 PDT 2016


Section "ServerLayout"
   Identifier     "Layout0"
   Screen      0  "Screen0" 0 0
   Screen      1  "Screen1" RightOf "Screen0"
   Screen      2  "Screen2" RightOf "Screen1"
   InputDevice    "Keyboard0" "CoreKeyboard"
   InputDevice    "Mouse0" "CorePointer"
EndSection

Section "Files"
EndSection

Section "InputDevice"

   # generated from default
   Identifier     "Mouse0"
   Driver         "mouse"
   Option         "Interactive" "False"
   Option         "Protocol" "auto"
   Option         "Device" "/dev/psaux"
   Option         "Emulate3Buttons" "no"
   Option         "ZAxisMapping" "4 5"
EndSection

Section "InputDevice"

   # generated from default
   Identifier     "Keyboard0"
   Driver         "kbd"
   Option         "Interactive" "False"
EndSection

Section "Monitor"
   Identifier     "Monitor0"
   VendorName     "Unknown"
   ModelName      "Unknown"
   HorizSync       28.0 - 33.0
   VertRefresh     43.0 - 72.0
   Option         "DPMS"
EndSection

Section "Monitor"
   Identifier     "Monitor1"
   VendorName     "Unknown"
   ModelName      "Unknown"
   HorizSync       28.0 - 33.0
   VertRefresh     43.0 - 72.0
   Option         "DPMS"
EndSection

Section "Monitor"
   Identifier     "Monitor2"
   VendorName     "Unknown"
   ModelName      "Unknown"
   HorizSync       28.0 - 33.0
   VertRefresh     43.0 - 72.0
   Option         "DPMS"
EndSection

Section "Device"
   Identifier     "Device0"
   Driver         "nvidia"
   VendorName     "NVIDIA Corporation"
   BoardName      "GeForce GTX 980 Ti"
   BusID          "PCI:3:0:0"
EndSection

Section "Device"
   Identifier     "Device1"
   Driver         "nvidia"
   VendorName     "NVIDIA Corporation"
   BoardName      "GeForce GTX 980 Ti"
   BusID          "PCI:129:0:0"
EndSection

Section "Device"
   Identifier     "Device2"
   Driver         "nvidia"
   VendorName     "NVIDIA Corporation"
   BoardName      "GeForce GTX 980 Ti"
   BusID          "PCI:130:0:0"
EndSection

Section "Screen"
   Identifier     "Screen0"
   Device         "Device0"
   Monitor        "Monitor0"
   DefaultDepth    24
   Option         "AllowEmptyInitialConfiguration" "True"
   Option         "RegistryDwords" "PerfLevelSrc==0x2222"
   Option         "Interactive" "False"
   Option         "Coolbits" "12"
   SubSection     "Display"
       Depth       24
   EndSubSection
EndSection

Section "Screen"
   Identifier     "Screen1"
   Device         "Device1"
   Monitor        "Monitor1"
   DefaultDepth    24
   Option         "AllowEmptyInitialConfiguration" "True"
   Option         "RegistryDwords" "PerfLevelSrc==0x2222"
   Option         "Interactive" "False"
   Option         "Coolbits" "12"
   SubSection     "Display"
       Depth       24
   EndSubSection
EndSection

Section "Screen"
   Identifier     "Screen2"
   Device         "Device2"
   Monitor        "Monitor2"
   DefaultDepth    24
   Option         "AllowEmptyInitialConfiguration" "True"
   Option         "RegistryDwords" "PerfLevelSrc==0x2222"
   Option         "Interactive" "False"
   Option         "Coolbits" "12"
   SubSection     "Display"
       Depth       24
   EndSubSection
EndSection

The RegistryDwords and other settings under the various screens stem from the commands posted here https://hashcat.net/forum/thread-3717-post-23470.html#pid23470 .

Let me know if you want/need more information.

RE: Warnings in hashcat v3 not present in cudaHashcat v2.01 - should I care? - voideater - 07-29-2016

Tried with the latest source from github, still issuiing the same warnings. Starting to run out of ideas :x

RE: Warnings in hashcat v3 not present in cudaHashcat v2.01 - should I care? - meatball - 08-12-2016

I have a similar setup as you guys do. Running into the same problems. Here is what I did to resolve. Hopefully this helps...

Attempted to run xhost + in terminal, received MAGIC COOKIE error. This confirmed that .Xauthority has issues.

I found the path to the auth file that X was using with the following command:
Code:
ps awwux | grep X

for me, this path was:
Code:
/usr/bin/X :0 vt7 -nolisten tcp -auth /var/lib/xdm/authdir/authfiles/A:0-IFUW01

I then set XAUTHORITY to the proper path:
Code:
export XAUTHORITY=/var/lib/xdm/authdir/authfiles/A:0-IFUW01

then I was able to perform the following X configurations:
Code:
xset -dpms
xset s off
xhost +

After performing the above (and installing libxnvctrl0 and libxnvctrl-dev) I was able to have hashcat control fan speed with no errors.

RE: Warnings in hashcat v3 not present in cudaHashcat v2.01 - should I care? - voideater - 08-22-2016

Thanks, that did the trick!