Steam for Linux

Steam for Linux

Bazzite KDE mounted NTFS drives not being added to Steam
Only 2 out of 4 NTFS partitions get mounted even though I select the correct ones. I had the game mode version of bazzite before and it added the partitions fine and was able to use them.
I used KDE Partition manager to auto-mount the partitions the same way as before.
< >
Showing 1-9 of 9 comments
You should not be able to properly use NTFS partitions for gaming on Steam with Proton in normal conditions on any Linux distribution, simply out of the FS and OS not supporting fundamental features of each other... or rather the FS under this OS, specifically symlinks, and the requirement to assign a user or group ownership of the partition, before said user (or group members) can access the contents of said drive. Symlinks are core for Wine (and hence Proton) operation in regards to the prefixes. Sure you can keep the data (common) for games directory in one location (even an [ex]FAT partition) and have Proton and Wine use a native FS location for the prefix (which is one way to circumvent this limitation), but I am not aware of a default configuration that would perform this. Maybe Bazzite has gone the extra mile in this regard?
I double checked and 3 of 4 partitions now show in steam, I tried to CHOWN the one partition that's not being added and it made no difference
Originally posted by thetargos:
You should not be able to properly use NTFS partitions for gaming on Steam with Proton in normal conditions on any Linux distribution, simply out of the FS and OS not supporting fundamental features of each other... or rather the FS under this OS, specifically symlinks, and the requirement to assign a user or group ownership of the partition, before said user (or group members) can access the contents of said drive. Symlinks are core for Wine (and hence Proton) operation in regards to the prefixes. Sure you can keep the data (common) for games directory in one location (even an [ex]FAT partition) and have Proton and Wine use a native FS location for the prefix (which is one way to circumvent this limitation), but I am not aware of a default configuration that would perform this. Maybe Bazzite has gone the extra mile in this regard?
I was running a game off of the partition without even reinstalling it before, working fine. I'm not sure what the difference is this time.
You cannot chown an NTFS partition once mounted, rather the process is done to the mount point directory, and uid/gid passed as options during mount process
Last edited by thetargos; Feb 5 @ 4:48pm
Cray Feb 6 @ 4:26am 
there's already several threads here and articles online about running games off of ntfs drives. you should have a look. basically:

-wasn't designed to work this way, and isn't recommended
-sometimes it'll work and often it won't
-some games may seem to work for a while and then not
-don't expect help/support with it
Originally posted by Cray:
there's already several threads here and articles online about running games off of ntfs drives. you should have a look. basically:

-wasn't designed to work this way, and isn't recommended
-sometimes it'll work and often it won't
-some games may seem to work for a while and then not
-don't expect help/support with it
sure, just odd it worked on one build of bazzite but not the other. Baffling even that it would show up one boot and then not on another boot without changing anything.
consider ntfs support in linux as emergency tool for accessing data. it works well enough for simple data access purposes, but it is not to be relied on. also if you try to do anything with compressed data (ntfs transparent compression) from linux, it can corrupt data. keep that in mind
Cray Feb 8 @ 8:57am 
Originally posted by sinephase:
Originally posted by Cray:
there's already several threads here and articles online about running games off of ntfs drives. you should have a look. basically:

-wasn't designed to work this way, and isn't recommended
-sometimes it'll work and often it won't
-some games may seem to work for a while and then not
-don't expect help/support with it
sure, just odd it worked on one build of bazzite but not the other. Baffling even that it would show up one boot and then not on another boot without changing anything.

it's pretty finnicky touchy feely unreliable, from what ppl reported. not too surprising.
if you have to use the drives as they are, creating a virtual filesystem inside an image file and mounting it is probably the only way to get it reliable.
One of the partitions had no label, so it showed up in the list of drives but wouldn't get added to steam when clicking to add it. Once I gave it a label they all seem to be working now.
EDIT: restarted to double check it's still showing in steam and added, it is. All partitions are now working.
Last edited by sinephase; Feb 8 @ 10:35am
< >
Showing 1-9 of 9 comments
Per page: 1530 50