this post was submitted on 31 Dec 2024
40 points (97.6% liked)

Linux Gaming

15602 readers
413 users here now

Discussions and news about gaming on the GNU/Linux family of operating systems (including the Steam Deck). Potentially a $HOME away from home for disgruntled /r/linux_gaming denizens of the redditarian demesne.

This page can be subscribed to via RSS.

Original /r/linux_gaming pengwing by uoou.

Resources

WWW:

Discord:

IRC:

Matrix:

Telegram:

founded 2 years ago
MODERATORS
[email protected]
40
Degraded gaming performance after waking from sleep. (lemmy.world)
submitted 1 week ago by [email protected] to c/[email protected]
15 comments fedilink hide all child comments
 
Operating System: Arch Linux 
KDE Plasma Version: 6.2.4
KDE Frameworks Version: 6.9.0
Qt Version: 6.8.1
Kernel Version: 6.12.7-arch1-1 (64-bit)
Graphics Platform: Wayland
GPU: NVIDIA GeForce RTX 4090/PCIe/SSE2
GPU DRIVER: 565.77

Pretty straight forward issue.
Rocket League for example: Butter smooth game play before sleep. After sleep mild to moderate stuttering.

  • Looking at processes, I don't see anything hung or stuck using high resources...
  • I've tried restarting sddm and kwin_wayland --replace.
  • Scanned logs before and after sleep, didn't see anything stand out.

I feel like this started happening around the first release of the 6.12 kernel. Or maybe last couple NVIDIA driver releases. With that in mind, since it's the 6.12 kernel, I have set my scheduler to "scx_lavd --autopilot".

Anyone experiencing similar issues?

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 1 points 3 days ago* (last edited 3 days ago)

Unfortunately these chips had voltage issues on launch. Whenever I do a new build I manually tweak my CPU in the bios while also testing my configuration using stress / torture tests on prime95 (mprime). They have since released bios updates that address the voltage issue. My understanding is the chips do not "degrade" over time, but instead could experience "damage" when used on a unpatched bios. More so when using the advanced overclock settings.

that could be your problem and there’s nothing you can really do about it since the CPU itself is flawed.

I don't think so. This is a Linux bug. This bug doesn't exist when booting into Windows.