Unable to lower memory frequency on Steam Deck LCD #162
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Expected Behaviour
Memory frequency remains unchanged (800MHz)
Actual Behaviour
Memory frequency changed to 400MHz
Steps To Reproduce
Anything else?
Hi, I'm not able to change the memory frequency to 400MHz from last week. It has been working fine for the last few months; maybe a fresh SteamOS/Powertools update changed something. I'm using the latest stable SteamOS and memory was overclocked to 6400 MT/s.
Version
2.0.3
Platform
SteamDeck
OS
SteamOS 3 (Stable)
I have this problem too,but afrter a moment it back to before ,change any
frequency value will lead memory run on 400mhz
There is currently some buggy behaviour with the interface for the LCD model. I've updated the limits on my server to the least buggy option without completely disabling the memory clock.
@NGnius is there anything I can test without building myself from dev branch? I saw your commit
ec02a65571
and I tried to create limits_override.ron file and put there quirks:quirks: ["pp_dpm_fclk-static"],
or
quirks: ["pp_dpm_fclk-not-updated-on-LCD", "pp_dpm_fclk-static"],
But still have the same behaviour (not able to change to 400 MHz).
UPD:
I was able to build it myself, and it's working. I will be waiting for the official release. Thanks
You can manually set the quirks in the limits_cache.ron file, but they'll get reset when the cache expires (downloaded from the limits server). The commit you referenced is missing a quirk though. There isn't a commit for the correct quirks yet (I forgot about it), but the limits server has it. The
pp_dpm_fclk-reversed
quirk was missing.There won't be a new release for this since it's unnecessary.
Thanks, it wasn't obvious for me that there is a separate API call to get these limits. I probably wiped out limits_cache.ron when I have installed my custom build and this solves the problem (I got new limits from your server).