Linux Gaming

19363 readers

273 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.

No memes/shitposts/low-effort posts, please.

Resources

WWW:

Discord:

IRC:

Gaming on Linux

Matrix:

Telegram:

Gaming on Linux

founded 2 years ago

MODERATORS

[email protected]

Help with Cyberpunk 2077 on Mint (lemmy.world)

submitted 1 month ago* (last edited 1 month ago) by [email protected] to c/[email protected]

57 comments fedilink hide all child comments

Hey gang, I'm having trouble running this game. I have a Ryzen 7 7800X3D, RTX 4070 Ti Super, 64GB DDR5 RAM, on a B650 motherboard. My issue is frequent crashing/freezing, meaning I can't play longer than a few minutes at a time. I have tried re-installing the game, Steam, the entire OS, and then fully wiping the drives to remove Windows dual partition and only installing Mint. Then I was pointed to the drivers, so I tried updating using the ppa(?) driver availability as Mint only offered the nVidia 550 through Driver Manager. I tried each of the separate drivers, rebooting between each load, and still having the same issue. For reference, I was able to run through character creator and early intro of the Streetkid after many failed attempts. But then I get to the ride-along with Dexter DeShawn which does not have skippable sections and takes too long. So the length of that conversation is too long before the game either freezes or outright crashes.

Any suggestions are welcome, it's really really annoying me and pretty disheartening after hearing how everything just works on Linux (other than competitive online games, which I don't really play anyway).

Edit to add: I also tried the different Proton versions available through Steam, where I purchased the game.

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 2 points 1 month ago (4 children)

Hm this part of the log doesn't look like the error. Those messages usually show up after the process has crashed. If there is nothing that looks like it's gamecrash related to you further above in the log, type sudo dmesg --follow in a terminal. This display the logs of all device drivers on a kernel level. While that is open, start the game and wait for it to freeze and see if any errors show up.

Also, if you post log messages again please put them in a

codeblock

by typing it like this:
```
codeblock
```
Should be more readable. If the log is rather long just put it into a pastebin or some other text sharing service.

[–] [email protected] 2 points 1 month ago (3 children)

Okay will do. And yes because I had to Force Stop it through steam rather than it crashing on its own I didn't see any super helpful logs. I will try the command you sent when I am able!

[–] [email protected] 2 points 1 month ago (2 children)

When you run steam from the terminal, you want to use -d to get the debugging info:

steam -d

[–] [email protected] 1 points 1 week ago (1 children)

I know this is revisiting an old post, I've been unable to game for some time. When I try this I don't get any other information. However, I have seen a lot of other issues system wide that just make it feel unstable. Like when playing I will have system wide freezes not just the game freeze (unable to move mouse/keyboard is unresponsive/etc.), I've had issues in Firefox where pages will just freeze or be non-responsive and have to force close the program or again it's system wide freezes. So I'm pretty sure it's not Steam related and is just the whole OS. I can't really get logs because when the system freezes my only option seems to be hard shut down then reboot.

[–] [email protected] 1 points 1 week ago

In Steam, add this to the launch options games where you crash in order to enable logging to a text file:

 PROTON_LOG=1 %command%

(-from: https://github.com/ValveSoftware/Proton/wiki/Proton-FAQ)

Then there will be a log file of the game in your home directory, named steam-$GAMEID.log.

When you're reading that log, the error that causes the freeze should be in the end of the log somewhere.

If you just want to log the output of the Steam -d command (if you can't find a crash in the proton log, for example) you can use tee, explained here since you should not just run random terminal commands you find online without knowing what they do: https://www.geeksforgeeks.org/tee-command-linux-example/

 steam -d | tee ~/steam.log

It'll write the output of steam -d to the terminal so you can read it, and also to the steam.log in your home directory.