this post was submitted on 05 Aug 2024
22 points (89.3% liked)

Linux Gaming

15789 readers
5 users here now

Gaming on the GNU/Linux operating system.

Recommended news sources:

Related chat:

Related Communities:

Please be nice to other members. Anyone not being nice will be banned. Keep it fun, respectful and just be awesome to each other.

founded 4 years ago
MODERATORS
 

I'm on Kubuntu 24.04, rocking a build that was pretty darn high end in 2021 with an AMD 6800 XT, and of course, Wolfenstein: The New Order was already old news by then. Proton does miracles, but this game freezes my entire machine. The last time I saw something like this happen was with Monster Hunter World in 2018, on a much older version of Proton. I can reliably get the game to freeze my machine in the opening level of The New Order, even across multiple versions of Proton, even with the renderapi launch parameter that should switch it back to OpenGL. Of course, even if I report this to Steam support, they'll tell me that they only support Steam Deck and not bespoke Linux desktops, and the game works fine on my Steam Deck, but would they be interested in some logs and a bug reported against the GitHub project? This is assuming no one here has an easy fix, of course. But if not, how would I get the logs? I wouldn't know what I'm looking at in those logs, personally. I'm also not sure if they'll write out correctly. Because it freezes the entire machine, I end up having to hard shut down the computer by the power button, and once or twice during my experiments, it failed to mount my game SSD (a separate drive from where my OS is installed) at boot, and I had to set up the automatic mount in the partition manager again. So assuming that doesn't impact the ability to write out the logs, I can collect them with some instructions, if you kind strangers in the know wouldn't mind providing them, please. And if Valve is interested in looking at them.

you are viewing a single comment's thread
view the rest of the comments
[–] kugmo@sh.itjust.works 2 points 3 months ago

If it's an amdgpu bug try reporting it to the amd linux gitlab