E: please read the entire post before replying…
Hi all. For the last several years I’ve been using Bazzite/Gamescope on my desktop, and even before that I was using it with ChimeraOS. It’s been really great and I’ve enjoyed it thoroughly. Unfortunately I’ve begun to experience issues with games freezing. Within an hour of firing up a game, the image freezes. Audio continues playing on a loop. I’m able to pull up the menu and exit out of the game no problem. But then I fire it up and the same thing happens again.
I don’t really know how to diagnose this issue but I reinstalled Bazzite fresh, same issue. Installed CachyOS-Handheld, same issue. However I tried launching games from the desktop mode and I’ve now spent ~20 hours gaming with no issue, but this is certainly not ideal. Any ideas on potential fixes?
E: AMD 5700x + 6800XT 16GB
You must log in or register to comment.
Others have basically already pointed out how you should go about diagnosing the problem. Which, by itself, is already very valuable.
Below, I will try to touch upon some tips and tricks that are worth noting in this context, assuming Bazzite*.
- Pinning a specific deployment to return back to. As we’ll be doing some time traveling in a bit, it’s definitely recommended to pin your latest deployment (just in case) before you do anything else. See this entry in Bazzite’s documentation on that.
- Rolling back to images from a certain day. So, IIRC, all of the uBlue products keep around 90 days worth of images you can rollback to. See Bazzite’s documentation on
brhfor more information. With this (and some effort), you can literally pinpoint the exact date from which you started to have problems with gamescope/game mode. - Looking into the exact changes between two deployments. So, after you’ve identified the last properly working deployment and the first deployment that started misbehaving, you can invoke the
rpm-ostree db diffcommand to see what has changed between the two deployments. Note two things on this:- That the hashes coincide with the ones you actually want to compare.
- The command catches only changes in packages. However, a config diff applied by Bazzite’s maintainers will not be shown here.
- Asking help from community channels. You can even start here. But basically, a project’s discord/discourse is undoubtedly better equipped in helping you out. See this entry on Bazzite’s documentation for links.
Wish ya good luck fam 😉!
Yeah, they have. The problem is that I don’t know understand anything they’re talking about. And I’m not interested in starting a new career. So I guess I should have known better.
I already wiped Bazzite. But the only communities they support are Reddit, Github, and Discord. None of which I have any interest in participating in. The top pinned thread in their Discourse says no one looks at issues there, and to go to the corporate platforms for support.
I appreciate the effort though.
TL;DR
Install an archival version of Bazzite or whatever else that corresponds to a date when you know it worked correctly.
Bazzite in particular makes this fairly easy. They have straight forward instructions on how to roll back to a given version.
If that fixes it, just use that version and don’t update.
If you want to stick with Cachy, you can use the Arch Archive to downgrade your entire system to an earlier date, or just Gamescope.
You can access those past images/snapshots even from a new install ;) .
As it seems to have been some time since it started, I’d suggest trying out the oldest still accessible snapshot/image.
Are you saying games work fine without invoking the third-party tools?
This sounds more like a general hardware or hearing issue. Monitor your temps, and run a memory test at a minimum. Make sure you don’t have a bunch of stuff stacked on your machine or vents clogged.
I don’t know what “third party tools” you speak of. If it was a hardware issue, surely it would persist in Plasma?
If it’s heat or hardware it may not show up until CPU, Mem, or GPU are under heavy utilization. That’s why I said monitor your temps and test your memory.
Gamescope is the extra tool.
Step one for me whenever I run into an issue, is to load up an earlier system snapshot and see if that fixes it.
If it does, it was an update that changed something. If it doesn’t, it’s likely a hardware issue.
How is a snapshot going to help me identify an issue with Gamescope vs. Plasma? And would persist across entirely different distros?
By going back in time to a version that you know worked.
If that doesn’t fix it, then you can be sure the problem is hardware related, because it still happens on the exact same software that used to work.
And if it does work on older software, then you can go forward one update/snapshot at a time, until you find the change that causes the problem.
What you need to do is compare different points in TIME (older versions), not the same software just installed differently.
because it still happens on the exact same software that used to work.
It also doesn’t happen on different software, which suggests it’s not a hardware issue.
I don’t have the slightest clue how to do anything with snapshots and it’s been months since it began anyway so I wouldn’t even know where to start. And even if I did know which version caused the problem, I wouldn’t know where to go from there.
I don’t have the slightest clue how to do anything with snapshots and it’s been months since it began anyway so I wouldn’t even know where to start
Well, if you didn’t create any, you can’t go back to them.
My suggestion is to find the archival ISOs of older versions and try them WITHOUT updating after installing them offline.
Though, if you end up having to install gamescope from the internet, then you’re likely getting the exact same latest version no matter what distro you use.
Hence, maybe just easier to learn how to install older versions of packages on cachy. The Arch archive repo makes that quite doable.
And even if I did know which version caused the problem, I wouldn’t know where to go from there.
You pin the package/system and prevent it from updating so it keeps working for you. And report the bug so it can be fixed.
All of this stuff is a community effort. You can wait for someone else to figure out the problem of course, but the fastest solution is usually to volunteer yourself.
A different distro is not different software. Distros are really just different ways to install the same exact software.
Gamescope on Bazzite is the same as Gamescope on Cachy. Same for Plasma/KDE.
Why would they be different?
A different distro is not different software.
…what!? LOL
Gamescope on Bazzite is the same as Gamescope on Cachy. Same for Plasma/KDE.
Gamescope on either is also not the same as Plasma.
Yes.
A distro or distribution is just a collection of software packages, and usually a package manager.
The actual software itself is the same. The list can be different, but where the items overlap, they are the same. How up to date they are can vary, but Plasma 6 on Bazzite is the exact same as Plasma 6 on Cachy.
Systemd is the same systemd across arch, ubuntu, mint, endeavour, fedora, and any others that use it.
Is this not obvius?
Changing the distro does not tell you much. Especially as you’re running the exact same program in the exact same DE, you should absolutely expect the same result.
Is this not obvius?
Not only is it not obvious, it’s not accurate.
A distro or distribution is just a collection of software packages
Software packages that are different . That’s what makes one distro different from another. Is that not obvious?
I haven’t used either, so I don’t have any firsthand help to give. But if you want useful help, you’ll need more specific details. Crash logs, hardware info, etc.
I don’t know how to get crash logs
Start with googling how to use journalctl, filter it based on time, errors, or specific processes.
What does BIOS say about your hardware?
What do you mean?
