-
Notifications
You must be signed in to change notification settings - Fork 43
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
Vega 56 voltages might not apply #5
Comments
Hi there @FKleinebreil. Can you please share:
(please try to wrap these outputs in "Insert code" when adding comments, for clarity) BTW, you should not worry too much about |
Thank you for the fast reply! I removed the
However, WattmanGTK still reports a vddgfx (which I assume is core voltage) of 1.2V and temps reach 80°C under load quickly, as I said. Or to say it differently: Temps are identical before and after after the change. |
I have no clue about WattmanGTK, just to be sure it is sane, compare the output of (as root) |
Sorry, this is my first time using the github forum. There were proper new lines before the I cross checked with the command you gave me and it too reports a VDDGFX of 1200mV, while the changed memory clock (940 MHz) seems to be applied correctly. Typical output:
|
Thanks for the output fix! According to the output, noting wrong with the script itself, the clocks and voltages are being set correctly. As of the VDDGFX report, it is indeed strange, it could be related to requirement to set the clock and voltages in order (see ROCm/ROCm#463 for details). Perhaps you can test applying the following
reboot before you try, and check the output of Also, as I don't have Vega to test the thing, but I know that Polaris for example have some strange limitations when it comes to relation between state and memory voltages (highest voltage of current SCLK and MCLK will "prevail" as VDDGFX), Vega 56/64 may also have some weird things to consider, so try with simpler custom states first (changing just one state at a time) and see what result you end up with. |
I edited
So the issue remains. However, I get that the issue is not with your script but somewhere else. So there is probably not much you can do about it. I will see if I can find someone with similar issues. Thank you very much for your time! |
If you really applied that custom state I suggested correctly, that output of |
I don't have other software active and only a single Vega 56. No iGPU either, CPU is a Ryzen 5 3600. However, I consider the issue closed as it's mostly likely not due to your script. |
This seems to be the bug affecting you, and apparently the fix was just applied to 5.4 RC: |
Thank you very much for the Update! |
I have 5.15.28 kernel, but I think I have the same issue with Vega56 |
I'm using an Asus Vega 56 Strix with Ubuntu Budgie 19.04. I wanted to use your tool (which is nevertheless great btw!) to undervolt the card and overclock the memory. I have the suspicion that while clocks apply, voltages don't.
My custom power states (core clocks as they were + custom voltages (1.2V -> 1.0V for P7), overclocked P3 memory):
OD_SCLK:
0: 852Mhz 800mV
1: 991Mhz 900mV
2: 1138Mhz 906mV
3: 1269Mhz 912mV
4: 1312Mhz 918mV
5: 1474Mhz 975mV
6: 1538Mhz 987mV
7: 1590Mhz 1000mV
OD_MCLK:
0: 167Mhz 800mV
1: 500Mhz 800mV
2: 700Mhz 900mV
3: 940Mhz 975mV
OD_RANGE:
SCLK: 852MHz 2400MHz
MCLK: 167MHz 1500MHz
VDDC: 800mV 1000mV
After running the script /sys/class/drm/cardX/device/pp_od_clk_voltage is identical to /etc/default/amdgpu-custom-state.card0 except:
VDDC: 800mV 1200mV
1200mV was the default value, too.
When I use WattmanGTK to monitor the Vega 56 during Unigine Superposition the reported vddgfx is 1.2V. Also the GPU temperature hits 80°C, which should not happen if 1.0V were actually applied. The memory clock is read correctly at 940MHz.
Do you have any idea what is going on? Many thanks in advance!
The text was updated successfully, but these errors were encountered: