-
-
Notifications
You must be signed in to change notification settings - Fork 263
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[FEAT]: Create API for AMD GPUs #827
Comments
Would this help? It's documentation for using ADLX with C#: |
Status update: I tried both the ADLX library and older ADL library, and either I am totally missing something or most stats are not reported. I made two branches: Here are also two reports from LibreHardwareMonitor: which seem to confirm that information like max clocks, max temp etc. are not reported. Either I am completely missing something or AMD APIs are just really funky and weird. I also updated the issue, to better list required features to complete the implementation. Any help is appreciated, but please stick to specific solutions, information or code samples, having above information in mind. EDIT: I also cleaned up less relevant comments, to clean up the thread here, nothing personal. |
Hello, you can use my implementation from G-Helper https://github.com/seerge/g-helper/blob/main/app/Gpu/AMD/AmdGpuControl.cs :) I mainly read only GPU temp and GPU load, but ADL2_New_QueryPMLogData_Get method reports bunch of other sensors that you can also use. |
But it doesn't return everything needed. Verified with librehardwaremonitor. |
@BartoszCichecki this is what I manage to get from my Radeon 6800S I can imagine it could be different per device tho, but from your desired list it already has clocks, temps, load %, power usage (in watts) You can check for monitors attached to GPU as well, but via different method.
|
Rules
Version
All
OS
All
Device
All Legions with AMD graphics
Is your feature request related to a problem?
Currently GPU specific features are not supported by LLT on AMD GPUs. It would be nice to change this. Features that need to be supported:
How would you like the problem to be solved?
Implement an API that is easy to use with C#.
What alternatives have you considered?
n/a
Additional information
n/a
The text was updated successfully, but these errors were encountered: