Unable to lower memory frequency on Steam Deck LCD #162

Closed
opened 2024-06-24 21:46:28 +01:00 by NRiche · 5 comments

Expected Behaviour

Memory frequency remains unchanged (800MHz)

Actual Behaviour

Memory frequency changed to 400MHz

Steps To Reproduce

  1. Go to Powertools
  2. Activate 'Downclock Memory'
  3. Set frequency to 400MHz

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)

### Expected Behaviour Memory frequency remains unchanged (800MHz) ### Actual Behaviour Memory frequency changed to 400MHz ### Steps To Reproduce 1. Go to Powertools 2. Activate 'Downclock Memory' 3. Set frequency to 400MHz ### 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)
NRiche added the
bug
label 2024-06-24 21:46:28 +01:00

I have this problem too,but afrter a moment it back to before ,change any
frequency value will lead memory run on 400mhz

I have this problem too,but afrter a moment it back to before ,change any frequency value will lead memory run on 400mhz
Owner

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.

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.
Author

@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

@NGnius is there anything I can test without building myself from dev branch? I saw your commit https://git.ngni.us/NG-SD-Plugins/PowerTools/commit/ec02a65571955764efeb084ae7ee29fdd6219876 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
Owner

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.

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.
Author

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).

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).
NGnius referenced this issue from a commit 2024-06-29 16:12:50 +01:00
NGnius referenced this issue from a commit 2024-07-29 23:19:01 +01:00
Sign in to join this conversation.
No milestone
No project
No assignees
3 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: NG-SD-Plugins/PowerTools#162
No description provided.