01-20-2021, 06:10 PM
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....9078ab276c, 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/...on.c#L1202
Which the return value is consumed by:
https://github.com/hashcat/hashcat/blob/...on.c#L1809
Which is then consumed by:
https://github.com/hashcat/hashcat/blob/...us.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/...on.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
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/...on.c#L1202
Which the return value is consumed by:
https://github.com/hashcat/hashcat/blob/...on.c#L1809
Which is then consumed by:
https://github.com/hashcat/hashcat/blob/...us.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/...on.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