Vega 64 - Voltage not applying after PC restart about lact

[mbrowars]

@ilya-zlobintsev Im sorry but I wasnt able to find a hint for the last working version. As it turns out it was enough to delete the the /etc/lact/config.yaml and reinstall the tool. Now everything works fine again. I might have messed things up in the config.

[ilya-zlobintsev]

After the system boots and the voltage value is not applied, can you try restarting the service (sudo systemctl restart lactd) - does it change anything?

I'm also unable to reproduce this on a Vega 56.

[Covin90]

I tried to issue the command but it doesn't change the behavior, the voltage is still locked at 1.2v even though I've set 1.1v in the app.

This is a screenshot right after the pc booted,

This one instead after I run and close a game, it seems like the voltage and memory clock value gets locked at the highest power state.

[ilya-zlobintsev]

Hmm, it looks like the voltage is actually configured (as you can see in the sliders - those show the value from the GPU, not just what you've configured it to before), but the problem is that the GPU doesn't always use this voltage.

LACT does not control specifically what voltage the GPU runs on, it just sets the voltage values at the appropriate p-states, and then the GPU clocks itself according to those p-states. So I'm afraid this is a GPU firmware issue, and there's not much that can be done on LACT's side.

You can also try changing the performance level or disabling certain power states to see if it changes this behaviour.

[mbrowars]

Same problem exists on my vega56.

But in addition the voltage isnt changed at all even after i try to reapply the setting.

It worked some versions before but im unable to tell at which version this behaviour started.

As it turns out the p-states might be set correctly..

[ilya-zlobintsev]

@mbrowars could you be more specific which version you're currently running, and with which version it worked before?