Open Skyrent opened 3 months ago
Bump. Never tested on SteamOS, but can confirm that the Cclk and GFXclk settings are ignored. TDP overrides on Deck are properly respected, just the clock speeds.
Did you happen to use any modifications to SteamOS to allow for the clocks to reach the new limits?
Edit: i was able to get the GfxClk override to work, just needed to override PowerTools to make it happen, but cpuclk is still stuck <3500MHz
Once a upper limit is set from the BIOS, SteamOS allows, without further steps, to exceed the value of 3500mhz for the CPU (cpuclk). However, this only happens for the OLED version. The LCD version requires a tool capable of modifying the hardcoded value in the AMD Van Gogh kernel.
Perhaps Bazzite inherits this limit from the LCD kernel and shares it with the OLED version?
Further and more detailed information are available here - https://gitlab.freedesktop.org/drm/amd/-/issues/2638 .
SteamOS LCD and OLED are one in the same, so there might be a tweak missing from fsync
At least you're getting 3500 my oled refuses to go over 2225 and I checked every setting possible , factory reset and did a repaste. It's not thermal throttling and it doesn't matter tdp it just refuses to clock up to even base clocks and games run worse for it
Describe the bug
My OLED deck CPU can't exceed 3500MHz according to Gamescope, even though the BIOS and terminal show the maximum value as 4000MHz.
The amdgpu drivers for vangogh currently hard code the maximum clock frequency. If a steam deck is overclocked, then the AMD PowerPlay interface can only be set up to this hard coded limit, rather than the true maximum clock.
However this limitation wasn't present on the OLED version of SteamOS, but it appeared after switching to Bazzite.
What did you expect to happen?
that the CPU can exceed the value of 3500, especially in combination with tools such powertools.
Output of
rpm-ostree status
Hardware
Galileo
Extra information or context
No response