CPU Stuck at 800mhz (powersaver governor)
bug
I've been running bazzite on my pc for a few months now. around mid afternoon today for no explicable reason, my CPU downclocked itself to 800mhz and stayed there. I rebooted, still stuck. I installed todays system update and when that didn't work, downgraded back to the release from the 10th. I installed the latest bios for my motherboard. I rebooted a few more times hoping it would fix itself. I booted back into windows 10, and of course the CPU had no problem running at it's full frequency there. After a lot of back and forth with an AI, I manged to figure out the cpufreq governor was stuck in powersaver mode, and running a tuned command allowed me to manually force it back to performance mode. it would have been nice if that was the end of it, but it doesn't persist with reboots. gemini thinks it's a good idea to create a systemd service that runs "tuned-adm profile throughput-performance" at startup but that seems silly. I'd rather my computer just work correctly normally.
Also for some reason bazzite thinks my main display is my hdmi 1080p side monitor instead of my displayport 1440p gaming monitor even though the DP monitor is set as the primary display, but that's a whole other problem.
Specs:
MB: ASUS Prime B660M-A D4
CPU: Intel i5 12600KF
RAM: Corsair Vengeance LPX 2x16GB DDR4-4000 (XMP is enabled)
GPU: Sapphire Pulse RX 9070
Also for some reason bazzite thinks my main display is my hdmi 1080p side monitor instead of my displayport 1440p gaming monitor even though the DP monitor is set as the primary display, but that's a whole other problem.
Specs:
MB: ASUS Prime B660M-A D4
CPU: Intel i5 12600KF
RAM: Corsair Vengeance LPX 2x16GB DDR4-4000 (XMP is enabled)
GPU: Sapphire Pulse RX 9070
