CPU minimum not sticking after reboot #138

Closed
opened 2023-12-17 19:25:14 +00:00 by Shise · 8 comments

Expected Behaviour

CPU minimum clock should be at 400mhz or whatever it was set to when it was enabled

Actual Behaviour

The 400mhz or set minimum should be whatever it was set to, however after a reboot the minimum clock defaults to 1400mhz instead of the set Mhz

Steps To Reproduce

  1. Enable limit clock speed for CPU, put to 400mhz (should default to it), enabled persistant profile if testing with a game.

  2. Reboot deck, launch the game, the minimum is now 1400mhz

Anything else?

N/A

Version

1.4.0

Platform

SteamDeck

OS

SteamOS 3 (Stable)

### Expected Behaviour CPU minimum clock should be at 400mhz or whatever it was set to when it was enabled ### Actual Behaviour The 400mhz or set minimum should be whatever it was set to, however after a reboot the minimum clock defaults to 1400mhz instead of the set Mhz ### Steps To Reproduce 1) Enable limit clock speed for CPU, put to 400mhz (should default to it), enabled persistant profile if testing with a game. 2) Reboot deck, launch the game, the minimum is now 1400mhz ### Anything else? N/A ### Version 1.4.0 ### Platform SteamDeck ### OS SteamOS 3 (Stable)
Shise added the
bug
label 2023-12-17 19:25:14 +00:00
Owner

Unless this is just #128 (and you've got your default profile set to 1400 and you're not checking the profile name), I cannot reproduce this with that information.

Unless this is just #128 (and you've got your default profile set to 1400 and you're not checking the profile name), I cannot reproduce this with that information.
NGnius added the
???
label 2023-12-17 22:17:24 +00:00
Author

Unless this is just #128 (and you've got your default profile set to 1400 and you're not checking the profile name), I cannot reproduce this with that information.

Hi see video, you can see my min is set at 400mhz with persistant profile, rebooted the device and now 1400mhz.

> Unless this is just #128 (and you've got your default profile set to 1400 and you're not checking the profile name), I cannot reproduce this with that information. Hi see video, you can see my min is set at 400mhz with persistant profile, rebooted the device and now 1400mhz.
Author

Unless this is just #128 (and you've got your default profile set to 1400 and you're not checking the profile name), I cannot reproduce this with that information.

do you need a log file or is the video above enough

> Unless this is just #128 (and you've got your default profile set to 1400 and you're not checking the profile name), I cannot reproduce this with that information. do you need a log file or is the video above enough
Owner

That's plenty, thanks. I managed to reproduce it by running the latest release of PowerTools.

Turns out I had already fixed this in 05f927dc0f, which is why I couldn't reproduce it on the development version.

That's plenty, thanks. I managed to reproduce it by running the latest release of PowerTools. Turns out I had already fixed this in https://git.ngni.us/NG-SD-Plugins/PowerTools/commit/05f927dc0f3e1587089c787a2f7736a1c0d057c0, which is why I couldn't reproduce it on the development version.
NGnius added
tbr
and removed
???
labels 2023-12-19 13:42:02 +00:00
Author

That's plenty, thanks. I managed to reproduce it by running the latest release of PowerTools.

Turns out I had already fixed this in 05f927dc0f, which is why I couldn't reproduce it on the development version.

Is it possible to use this ver.? Like a beta/testing option in Decky Loader?

> That's plenty, thanks. I managed to reproduce it by running the latest release of PowerTools. > > Turns out I had already fixed this in https://git.ngni.us/NG-SD-Plugins/PowerTools/commit/05f927dc0f3e1587089c787a2f7736a1c0d057c0, which is why I couldn't reproduce it on the development version. Is it possible to use this ver.? Like a beta/testing option in Decky Loader?
Owner

Only by building it yourself. The dev branch is not recommended for regular use since it's not guaranteed to even be in a working state. Once most features for the next release are implemented, I'll start putting pre-release versions on my custom store.

Only by building it yourself. The dev branch is not recommended for regular use since it's not guaranteed to even be in a working state. Once most features for the next release are implemented, I'll start putting pre-release versions on my custom store.
Author

Only by building it yourself. The dev branch is not recommended for regular use since it's not guaranteed to even be in a working state. Once most features for the next release are implemented, I'll start putting pre-release versions on my custom store.

Okay no problem, hopefuilly soon, I can see the commits have fixed the battery limit issue too. So looks like a good update coming!

> Only by building it yourself. The dev branch is not recommended for regular use since it's not guaranteed to even be in a working state. Once most features for the next release are implemented, I'll start putting pre-release versions on my custom store. Okay no problem, hopefuilly soon, I can see the commits have fixed the battery limit issue too. So looks like a good update coming!

I have same behaviour. When i set min cpu limit below 1400mhz, it set 1400 in config file. I'm not very knowledgeable in Rust, but it looks like range at backend/src/settings/steam_deck/oc_limits.rs was set wrong at line 112 and in pt_oc.json file too.

I have same behaviour. When i set min cpu limit below 1400mhz, it set 1400 in config file. I'm not very knowledgeable in Rust, but it looks like range at backend/src/settings/steam_deck/oc_limits.rs was set wrong at line 112 and in pt_oc.json file too.
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#138
No description provided.