NG-SD-Plugins/PowerTools
NG-SD-Plugins/PowerTools
4
4
Fork 3
Code Issues 19 Pull requests 1 Projects Releases 24 Wiki Activity

GPU stuck at 200Mhz after Rebooting Steam Deck #76

New issue
Closed
opened 2023-02-20 14:31:26 +00:00 by tobio225 · 10 comments
tobio225 commented 2023-02-20 14:31:26 +00:00 (Migrated from github.com)
Copy link

Please confirm

  • I have searched existing issues
  • This issue is not a duplicate of an existing one
  • I will fill this out to the best of my ability

Expected Behaviour

GPU Clock not being stuck after Reboot.

Actual Behaviour

GPU Clock is stuck at 200 Mhz after Reboot. After changing the clock speed manually either in Deck overlay or Powertools Plugin, the GPU is behaving normally again.

Steps To Reproduce

  1. Install Powertools Plugin
  2. Tinker with GPU Clock Speed
  3. Turn the altered GPU Clocks off again (so that the Clockspeed is variable again)
  4. Reboot Steam Deck
  5. GPU Clock is stuck at 200Mhz (CPU is still behaving normally)

Anything else?

No response

Version

1.1.0 (Latest stable)

Platform

Steam Deck

OS

SteamOS 3 (Stable)

### Please confirm - [X] I have searched existing issues - [X] This issue is not a duplicate of an existing one - [X] I will fill this out to the best of my ability ### Expected Behaviour GPU Clock not being stuck after Reboot. ### Actual Behaviour GPU Clock is stuck at 200 Mhz after Reboot. After changing the clock speed manually either in Deck overlay or Powertools Plugin, the GPU is behaving normally again. ### Steps To Reproduce 1. Install Powertools Plugin 2. Tinker with GPU Clock Speed 3. Turn the altered GPU Clocks off again (so that the Clockspeed is variable again) 4. Reboot Steam Deck 5. GPU Clock is stuck at 200Mhz (CPU is still behaving normally) ### Anything else? _No response_ ### Version 1.1.0 (Latest stable) ### Platform Steam Deck ### OS SteamOS 3 (Stable)
NGnius commented 2023-02-20 16:25:18 +00:00 (Migrated from github.com)
Copy link

I took a look at this with the performance overlay enabled in the menu, and I noticed something slightly different from what you're describing: the GPU will boost above 200MHz, but under light to moderate loads it doesn't. Seems like the boost behaviour is just very conservative at the minimum.

Can you confirm this is what's happening for you too? It may take a bit of work to get the GPU under enough load to boost above 200MHz (I found that selecting an item in the News section of Home, then waiting a second and watching the GPU clock worked).

I took a look at this with the performance overlay enabled in the menu, and I noticed something slightly different from what you're describing: the GPU will boost above 200MHz, but under light to moderate loads it doesn't. Seems like the boost behaviour is just very conservative at the minimum. Can you confirm this is what's happening for you too? It may take a bit of work to get the GPU under enough load to boost above 200MHz (I found that selecting an item in the News section of Home, then waiting a second and watching the GPU clock worked).
tobio225 commented 2023-02-20 16:57:08 +00:00 (Migrated from github.com)
Copy link

For me launching and trying to play a game (Dirt Rally 2.0) didn't even force the GPU to go higher than 200Mhz. With these 200Mhz the GPU was at 100% load in game and the game stuttered. Only thing that helped was manually adjusting the GPU clock. I can try to go to the News menu and see what happens tomorrow and report.

For me launching and trying to play a game (Dirt Rally 2.0) didn't even force the GPU to go higher than 200Mhz. With these 200Mhz the GPU was at 100% load in game and the game stuttered. Only thing that helped was manually adjusting the GPU clock. I can try to go to the News menu and see what happens tomorrow and report.
NGnius commented 2023-02-20 17:22:49 +00:00 (Migrated from github.com)
Copy link

Ok I'm definitely not seeing that. I launched Stray to check and it got the GPU to boost higher as well.

Can you upload your logs and, if persistent, the PowerTools config for the games that are having the issue?

Ok I'm definitely not seeing that. I launched Stray to check and it got the GPU to boost higher as well. Can you upload your logs and, if persistent, the PowerTools config for the games that are having the issue?
tobio225 commented 2023-02-20 17:28:26 +00:00 (Migrated from github.com)
Copy link

Sure, i will get back to you tomorrow. Where do i find the log and profile files?

Sure, i will get back to you tomorrow. Where do i find the log and profile files?
NGnius commented 2023-02-20 18:55:56 +00:00 (Migrated from github.com)
Copy link

the log file /tmp/powertools-rs.log
the config files are in ~/.config/powertools (each <ID>.json corresponds to the game ID used by Steam)

the log file `/tmp/powertools-rs.log` the config files are in `~/.config/powertools` (each `<ID>.json` corresponds to the game ID used by Steam)
tobio225 commented 2023-02-21 06:38:54 +00:00 (Migrated from github.com)
Copy link

OK, so here are the log files. I don't have a powertools-folder in .config, so i cannot find the config files...

before_reboot_powertools-rs.log
after_reboot_powertools-rs.log

Here's what i did:

  1. File "before reboot":
  • Install Powertools plugin from decky (was uninstalled from the day before to confirm the stuck GPU resulted from the plugin)
  • tried to the plugin from decky --> got an error screen with the message to hit refresh
  • hit refresh --> decky was gone from the (...)-menu
  • reboot steam deck
  • decky was back, powertools plugin could be opened (despite the reboot, the GPU clock was behaving normally)
  • start Dirt Rally 2.0
  • adjusted GPU max. clock for testing
  • setting GPU max. Clock back to default 1600Mhz
  • close game
  • safe the log file
  • reboot steam deck
  1. File "after reboot":
  • Deck rebooted --> GPU Clock was stuck at 200Mhz in Steam
  • hovering around the menus, trying to push load on the GPU did not boost the clock (~75% load)
  • start Dirt Rally 2.0
  • GPU Clock still stuck at 200Mhz
  • Open Powertools plugin and adjust min. GPU Clock to 300Mhz
  • GPU started boosting like normal immediately
  • close game
  • safe log file.

Rebooting afterwards gave me back the stuck GPU at 200Mhz. Uninstalling the powertools plugin and rebooting again fixed it.

OK, so here are the log files. I don't have a powertools-folder in .config, so i cannot find the config files... [before_reboot_powertools-rs.log](https://github.com/NGnius/PowerTools/files/10790401/before_reboot_powertools-rs.log) [after_reboot_powertools-rs.log](https://github.com/NGnius/PowerTools/files/10790400/after_reboot_powertools-rs.log) Here's what i did: 1. File "before reboot": - Install Powertools plugin from decky (was uninstalled from the day before to confirm the stuck GPU resulted from the plugin) - tried to the plugin from decky --> got an error screen with the message to hit refresh - hit refresh --> decky was gone from the (...)-menu - reboot steam deck - decky was back, powertools plugin could be opened (despite the reboot, the GPU clock was behaving normally) - start Dirt Rally 2.0 - adjusted GPU max. clock for testing - setting GPU max. Clock back to default 1600Mhz - close game - safe the log file - reboot steam deck 2. File "after reboot": - Deck rebooted --> GPU Clock was stuck at 200Mhz in Steam - hovering around the menus, trying to push load on the GPU did not boost the clock (~75% load) - start Dirt Rally 2.0 - GPU Clock still stuck at 200Mhz - Open Powertools plugin and adjust min. GPU Clock to 300Mhz - GPU started boosting like normal immediately - close game - safe log file. Rebooting afterwards gave me back the stuck GPU at 200Mhz. Uninstalling the powertools plugin and rebooting again fixed it.
NGnius commented 2023-02-22 00:40:17 +00:00 (Migrated from github.com)
Copy link

If you set the minimum GPU clock to 300 or 400MHz permanently, does the GPU still refuse to boost after a reboot?

If you set the minimum GPU clock to 300 or 400MHz permanently, does the GPU still refuse to boost after a reboot?
tobio225 commented 2023-02-22 06:32:50 +00:00 (Migrated from github.com)
Copy link

No, that didnt work either. After setting min. Clock to 300mhz and rebooting, the GPU is still stuck at 200Mhz. Also the decky loader disappeared completely from the (...)-menu after the reboot. Another reboot brought decky back, the gpu stuck at 200mhz and the setting of 300mhz Was not saved in the powertools plugin....

No, that didnt work either. After setting min. Clock to 300mhz and rebooting, the GPU is still stuck at 200Mhz. Also the decky loader disappeared completely from the (...)-menu after the reboot. Another reboot brought decky back, the gpu stuck at 200mhz and the setting of 300mhz Was not saved in the powertools plugin....
NGnius commented 2023-02-22 12:59:35 +00:00 (Migrated from github.com)
Copy link

Did you also set the persistent profile toggle?

Did you also set the persistent profile toggle?
tobio225 commented 2023-02-22 13:51:57 +00:00 (Migrated from github.com)
Copy link

nope, i hadn't. Seems to work now with that switch on. Even seems to work with GPU minimum clock set to 200Mhz.... Did a couple of reboots and it seems fine.

As soon as i toggle that switch off again, the GPU is stuck at 200Mhz after next reboot...

I also tested the behaviour with the toggle for GPU frequency limit --> if toggled on (and persistent profile toggled on) there seems to be no problem. If toggled off (no matter if persistent profile is on or off) --> GPU stuck again at 200Mhz.

nope, i hadn't. Seems to work now with that switch on. Even seems to work with GPU minimum clock set to 200Mhz.... Did a couple of reboots and it seems fine. As soon as i toggle that switch off again, the GPU is stuck at 200Mhz after next reboot... I also tested the behaviour with the toggle for GPU frequency limit --> if toggled on (and persistent profile toggled on) there seems to be no problem. If toggled off (no matter if persistent profile is on or off) --> GPU stuck again at 200Mhz.
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
dev
decky
v2.0.3
v2.0.2
v2.0.1
v2.0.0
v1.4.0
v1.3.1
v1.3.0
v1.2.0
v1.1.1
v1.1.0
v1.0.5
v1.0.4
v1.0.3
v1.0.2
v1.0.1
v1.0.0
v0.7.0
v0.6.0
v0.5.0
v0.4.1
v0.4.0
v0.3.0
v0.2.0
v0.1.1
v0.1.0
Labels
Clear labels   
???

Missing information

  
bug

Something isn't working as intended

  
docs

Improvements or additions to documentation

  
enhancement

New feature or request

  
help wanted

Great for new/external code contributors

  
indev

Selected for development; coming soon

  
question

Information request

  
research

Further investigation required

  
tbr

To be released (complete)

  
wontfix

This will not be worked on

No labels
???
bug
docs
enhancement
help wanted
indev
question
research
tbr
wontfix
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
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#76
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?