Unfortunately that is the target frame rate for steam deck most of the time.

So runs like crap is more like “runs as intended”

If the CPU clocks are dropping to ~200-300 MHz while the temps are 40-45C (like in the screenshot) then it’s not thermal throttling. The clockspeed would go back up when the temps go down. And it would only throttle enough to keep the temps under the desired temp.

I would investigate what performance profile the CPU is using.

There is a tool called cpupower that will list out all the information about the CPU clock states.

I have a Ryzen CPU so the desired governor is going to be different than an Intel laptop, but for example, the output of cpupower frequency-info for me:

analyzing CPU 13:
  driver: amd-pstate-epp
  CPUs which run at the same hardware frequency: 13
  CPUs which need to have their frequency coordinated by software: 13
  energy performance preference: balance_performance
  hardware limits: 600 MHz - 5.76 GHz
  available cpufreq governors: performance powersave
  current policy: frequency should be within 2.98 GHz and 5.76 GHz.
                  The governor "powersave" may decide which speed to use
                  within this range.
  current CPU frequency: 4.39 GHz (asserted by call to kernel)
  boost state support:
    Supported: yes
    Active: yes
  amd-pstate limits:
    Highest Performance: 166. Maximum Frequency: 5.76 GHz.
    Nominal Performance: 124. Nominal Frequency: 4.30 GHz.
    Lowest Non-linear Performance: 86. Lowest Non-linear Frequency: 2.98 GHz.
    Lowest Performance: 18. Lowest Frequency: 600 MHz.
    Preferred Core Support: 1. Preferred Core Ranking: 231.

Which you can see lists the hardware clock range, the current governor’s policy frequency range, the actual current CPU frequency, and how it picks different frequency ranges.

I used to use cpupower on an old laptop to force it into the performance governor, because it would not clock up high enough without it. This obviously does negatively affect battery life, but i was plugged in most of the time anyway.

But either way, look into cpupower for determining the governor/power profile and also figuring out which governor you should actually be using.

Sure.you figure out which parts to scale when.

But point being that it quickly pivots into automating away tasks you were previously doing by hand.

I didnt notice at first but a friend pointed it out: it’s the same game loop as cookie clicker. This is just an idle/clicker game. You start manual dealing/clicking. And then you automate it. and it turns into a game of managing your automations rather than actually clicking yourself.

“I was expecting it to be a joke 20 minutes then throw away game, but holy crap, this is actually pretty deep and well thought out.” - Also my friend.

AMD doesnt have any software for controlling RGB on windows. They don’t make graphics cards, they only make the GPU chip that goes onto the card (and the GPU chip doesn’t have any LEDs on it).

The LED controllers on the cards are per brand. If you have a Sapphire card, it’s Sapphire software that controls the RGB. XFX card -> XFX software, etc.

I have an XFX 9070xt, and it doesnt have any RGB on it. so I haven’t had to disable it.

OpenRGB is going to be your best bet for Linux RGB management. Sometimes they dont have every device supported (especially newer ones), so you might not be able to change everything immediately. But it’s mostly just a “scan devices, set color values” once it’s working.

And the iGPU you can probably disable in the UEFI config.

My take is that Windows experience sucks so bad that even HP won’t touch it. But “HP sucks” is a very valid point.

This can go one of two ways:

• More devices running SteamOS/Linux means more support, and helps Linux
• HP manages to make a device so bad that it makes SteamOS look bad, and hurts Linux

The second way shouldn’t even be possible, but never underestimate HP’s ability to make something worse than you thought possible.