Steam for Linux

Steam for Linux

Trapacid Sep 12, 2018 @ 3:04pm
The ultimate guide for fps, system-wide performance, fixing issues, etc!
I've spent about a week making this beautiful guide as I wanted to see if I can help many Linux users with their issues and to share my Linux knowledge with everyone else.

This is the ultimate Linux guide for improving FPS, improving system-wide task and performance, troubleshoot and fix issues with your system, and much more.

https://steamcommunity.com/sharedfiles/filedetails/?id=1502890492

I am constantly updating this as I discover and learn more things. User feedback is appreciated with respect as well as additional tips and tricks I haven't found out about.

I also plan to make more guides dedicated to Linux.
< >
Showing 1-15 of 21 comments
thetargos Sep 12, 2018 @ 4:16pm 
Interesting. I'll have a look in depth as soon as I can.
meheezen Sep 12, 2018 @ 4:27pm 
well, i am one of those who recommends aways having a swap file/partition, even if small.
i'll take a better look at the guide when i got more time
Trapacid Sep 12, 2018 @ 4:36pm 
Originally posted by meheezen:
well, i am one of those who recommends aways having a swap file/partition, even if small.
i'll take a better look at the guide when i got more time
If you have an SSD and/or a LOT of RAM, it's kind of useless IMO.
meheezen Sep 12, 2018 @ 4:51pm 
^i've had issues in the past when running machines with no swap (even with "lots of RAM"), if you ever need to use stand-by or hibernate with no swap, be prepared for some issues.
Trapacid Sep 12, 2018 @ 4:59pm 
Originally posted by meheezen:
^i've had issues in the past when running machines with no swap (even with "lots of RAM"), if you ever need to use stand-by or hibernate with no swap, be prepared for some issues.
Huh. Weird. I never have any issues with no swap.

What ever works for you.
WarnerCK Sep 12, 2018 @ 5:13pm 
Originally posted by meowie:
Make sure you are the root user and if you're not, be sure to get the password from the owner with their permission.

This is inaccurate. No user should be root. Most distros specifically don't have a root password. I suspect that you are mixing up user permissions with the Windows concept of Administrator accounts.
Trapacid Sep 12, 2018 @ 5:19pm 
Originally posted by WarnerCK:
Originally posted by meowie:
Make sure you are the root user and if you're not, be sure to get the password from the owner with their permission.

This is inaccurate. No user should be root. Most distros specifically don't have a root password. I suspect that you are mixing up user permissions with the Windows concept of Administrator accounts.
Yeah. I didn't really type that well. What I meant to say was:
Make sure you have the root password for commands that require to be ran as root.

Sorry, I'll fix that ASAP!
thetargos Sep 12, 2018 @ 5:24pm 
Just a quick observation on the whole admin thing. Make sure the user is part of the wheel group (some distros don't use it, though, but it is even available on MacOS) and the /etc/sudoers file
Trapacid Sep 12, 2018 @ 5:28pm 
Originally posted by thetargos:
Just a quick observation on the whole admin thing. Make sure the user is part of the wheel group (some distros don't use it, though, but it is even available on MacOS) and the /etc/sudoers file
I'll be sure to add that. I completely forgot about the important things first for some reason >.>
thetargos Sep 12, 2018 @ 7:36pm 
Hey, we all build this guide ;)

Oh, it may be worth mentioning that some distributions/tools (GUI tools) allow creating users as "administrators" (automatically adding them to the wheell group and sudoers file) besides the whole useradd options, which is obviously the most robust approach.
Trapacid Sep 13, 2018 @ 4:11am 
Originally posted by thetargos:
Hey, we all build this guide ;)

Oh, it may be worth mentioning that some distributions/tools (GUI tools) allow creating users as "administrators" (automatically adding them to the wheell group and sudoers file) besides the whole useradd options, which is obviously the most robust approach.
Yeah, I'm using Arch Linux and I never really used any sort of GUI-based system (except for Kali Linux when I thought I was cool a year ago LOL!) and I just did it all by command line and then installed a desktop and such.

I have used Ubuntu in the past, though never really enjoyed.
PLAYMAKER Sep 13, 2018 @ 7:33am 
Thank you, you really put a lot of work into this guide.
New linux users will have a lot to play around with :) Great! Keep it going.
Fibbs Sep 13, 2018 @ 8:42am 
Just had a glance through it. The section on swap partitions seems to completely misunderstand what they're for. Having a swap partition is in no way ever going to slow down your PC. It is, at the most basic level, just an overflow area for when your RAM gets full.
Omega Sep 13, 2018 @ 9:27am 
Steam is acting strange and it doesn't allow me to post in the comments on the guide. THis is what I was trying to post:



I quickly skimmed though this guide and it looks pretty nice. :47_thumb_up:


DRI_PRIME, https://wiki.archlinux.org/index.php/PRIME
I am usure if it's a bug or just how this stuff is configured by default but laptops don't seem to always be willing to switch heavy workloads over to the discrete GPU, adding "DRI_PRIME=1 %command%" (Without ") to the Steam game launch options will make the discrete GPU enable while running the game to which this launch option is set.

And under security tweaks you could also mention a firewall such as the Uncomplicated Firewall. People always forget about the firewall. Simply install UFW and run "ufw enable" in the terminal. If you prefer a graphical front-end to enable/disable UFW I recommend Gufw.
petri.piira Sep 13, 2018 @ 12:20pm 
I'll echo the comments here. Mostly a very nice guide, but recommending against swap is not going to cause anything good. Not necessarily anything bad either, but see below.

Yes, if you can guarantee that you always have more memory then the processes you are running would ever need, you don't need swap.

Also, if you type "free" on the command prompt and see that you actually have used swap (assuming you have it), that is a sign that you are occasionally going over the amount of memory you have. Maybe you need to consider bying more. Maybe not, see below.

Linux (unlike some other operating systems) is very good in using swap and memory.

Basically, as long as you have "free" real memory, linux will try to use that memory as extra buffers and caches, to speed up what you are doing. So, it is perfectly normal to see "all memory is in use" - whatever was not needed by your processes was allocated to speed up things you might potentially be doing next.

But if you actually need that memory, it will be taken away from that buffering/caching, and your processes will get it.

Now, the swap is typically only used if your processes need more memory than you have. Without swap, linux will in that case just coldly murder some process to be able to keep the others running.

With swap, in that case, linux will swap out some memory of some process which does not seem to be doing anything useful with it. In many cases, those processes are not actually doing anything time critical - if they want to do something with that memory, they will get it back when needed - which is slow, yes.

But, linux would never swap out memory from a process which is actually doing heavy work with it (like your game). As long as you have enough memory for all of the processes which actually do heavy work with the memory they use.

So, normally:
- with swap: some of the lazier processes will become slower if you run out of memory.
- without swap: some process (maybe your game) will just die if you run out of memory.

If you have swap, you can run efficiently all of the things which need to be run efficiently, and in addition to that, you can run some stuff which is not so critical even if the total memory used would be more than you have. If you don't have swap, something just dies when you use more memory than you have.

Swap has a bad reputation because some operating systems were very bad in using it - I hear some even used it for caches ... swapping a memory cache for disk to disk, so that the disk reads would be sped up by reading from the disk, instead of reading from the disk ... and swapping critical processes out so that it could get that cache back to memory so that the critical procss could read from that cache... even if the process was just slowed by a factor of 1000 by being swapped out ... ???

Even those operating systems are not as bad as that anymore, if they ever were.

But with linux, having swap will only help. Not at all, if you have more memory than you need, but if you ever overflow slightly, you will not suffer. If you overflow a lot, you will be slowed. But better that than processes just dying from the lack of memory.
Last edited by petri.piira; Sep 13, 2018 @ 12:34pm
< >
Showing 1-15 of 21 comments
Per page: 1530 50

Date Posted: Sep 12, 2018 @ 3:04pm
Posts: 21