+- 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: Total GPU Noob here (/thread-9541.html)
Total GPU Noob here - thatgal - 10-04-2020
First time gpu owner (sry, i know, late to the game lol. better late than never!)
I have:
AMD Radeon RX 5700 xt
ADM Ryzen 9 3900X.
WIN 10 Pro
So far I am very impressed with the speed improvement when using hashcat w/GPU, I mean very impressed vs. CPU.
I do notice that when I run the baseline command:
Code:
.\hashcat.exe -b -O -w 4I get the following red output re GPU. I am concerned I am doing something wrong and I dont want to break my new card because I am an idiot.
Basicly I am asking is ADL_Overdrive5_CurrentActivity_Get(): -8 something to be concerned about?
PS C:\Users\system admins\Documents\hashcat> .\hashcat.exe -b -O -w 4
hashcat (v6.1.1) starting in benchmark mode...
ADL_Overdrive5_CurrentActivity_Get(): -8
ADL_Overdrive5_CurrentActivity_Get(): -8
ADL_Overdrive5_CurrentActivity_Get(): -8
ADL_Overdrive5_CurrentActivity_Get(): -8
ADL_Overdrive5_CurrentActivity_Get(): -8
ADL_Overdrive5_CurrentActivity_Get(): -8
ADL_Overdrive5_CurrentActivity_Get(): -8
ADL_Overdrive5_CurrentActivity_Get(): -8
ADL_Overdrive5_CurrentActivity_Get(): -8
ADL_Overdrive5_CurrentActivity_Get(): -8
ADL_Overdrive5_CurrentActivity_Get(): -8
ADL_Overdrive5_CurrentActivity_Get(): -8
OpenCL API (OpenCL 2.1 AMD-APP (3110.7)) - Platform #1 [Advanced Micro Devices, Inc.]
=====================================================================================
* Device #1: gfx1010, 8112/8176 MB (6732 MB allocatable), 20MCU
* Device #2: gfx1010, 8112/8176 MB (6732 MB allocatable), 20MCU
* Device #3: gfx1010, 8112/8176 MB (6732 MB allocatable), 20MCU
Benchmark relevant options:
===========================
* --optimized-kernel-enable
* --workload-profile=4
Hashmode: 0 - MD5
Speed.#1.........: 8170.2 MH/s (134.28ms) @ Accel:1024 Loops:1024 Thr:64 Vec:1
Speed.#2.........: 7966.5 MH/s (138.04ms) @ Accel:1024 Loops:1024 Thr:64 Vec:1
Speed.#3.........: 7900.9 MH/s (139.63ms) @ Accel:1024 Loops:1024 Thr:64 Vec:1
Speed.#*.........: 24037.5 MH/s
Hashmode: 100 - SHA1
Speed.#1.........: 3122.0 MH/s (390.04ms) @ Accel:1024 Loops:1024 Thr:64 Vec:1
Speed.#2.........: 3143.2 MH/s (393.32ms) @ Accel:1024 Loops:1024 Thr:64 Vec:1
Speed.#3.........: 3212.8 MH/s (385.87ms) @ Accel:1024 Loops:1024 Thr:64 Vec:1
Speed.#*.........: 9478.0 MH/s
etc.....
Thanks in advance for your kind help!
RE: Total GPU Noob here - ntrain2k - 10-07-2020
I get the same thing with my setup (3 5700XT's).
RE: Total GPU Noob here - weeeeeeeeee - 01-20-2021
Not to resurrect a dead thread but I looked into this as well as I was getting this error message as well. I did some digging and the API responsible for this function is found here: https://gpuopen-librariesandsdks.github.io/adl/group__OVERDRIVE5API.html#ga82b75de3cab6eb9fa3ed2a9078ab276c, which can be linked back to this page from AMD here: https://gpuopen.com/adl/.
A correct return value is ADL_OK which is as "0", the error code we are getting back is -8 and that links to ADL_ERR_NOT_SUPPORTED. Which basically states from the API: Function not supported by the driver.
If this will do damage to the call, I dont' think so as the code in hashcat does the following with it
https://github.com/hashcat/hashcat/blob/ad7fc1a3fefc28b9e8ad4030e907c87034735a58/src/hwmon.c#L1202
Which the return value is consumed by:
https://github.com/hashcat/hashcat/blob/ad7fc1a3fefc28b9e8ad4030e907c87034735a58/src/hwmon.c#L1809
Which is then consumed by:
https://github.com/hashcat/hashcat/blob/ad7fc1a3fefc28b9e8ad4030e907c87034735a58/src/status.c#L1965
This call just prints to the terminal that there are no busses available (for what reason, I dunno, will look at code later).
Second consumer of the call:
https://github.com/hashcat/hashcat/blob/ad7fc1a3fefc28b9e8ad4030e907c87034735a58/src/hwmon.c#L2744
This seems to setup the hwmonitor context. I'd be worried if this was temperature related but to me it doesn't seem to be, however you can do a quick look of the code yourself and play along as well
