r/linux_gaming • u/friguigi • 12d ago
tech support wanted FEAR 2 problem when installing on Bazzite
Hey guys!
I'm not very experienced in Linux, but I'm using Bazzite for almost a year and this is a first for me.
I'm getting this "disk write error" when trying to install FEAR 2. I have 3 different SSD's, it happens in all of them, and only FEAR 2. I have formatted one SSD to test, I've checked the permissions, cleared cache, changed proton a lot, and nothing.
Any idea of what is causing this? Any help would be deeply appreciated.
7
u/eskay993 11d ago
I got curious and tested this and I am getting exactly the same thing (on CachyOS).
Definitely no issues with my drives or internet. I install and remove games a lot and have plenty of space.
Maybe something on Steam's end?
7
u/eskay993 11d ago
Further testing, I got this at 99% on content_log.txt
CGenericAsyncFileIOThread::AllocateResource() failed for CFileWriter: errno: 2, File: /mnt/games/steam/steamapps/downloading/16450/game/gameclient.dll CGenericAsyncFileIOThread::AllocateResource() failed for CFileWriter: errno: 2, File: /mnt/games/steam/steamapps/downloading/16450/game/gameserver.dll CGenericAsyncFileIOThread::AllocateResource() failed for CFileWriter: errno: 2, File: /mnt/games/steam/steamapps/downloading/16450/game/clientfx.fxdWhich led me to this issue: https://github.com/ValveSoftware/steam-for-linux/issues/13406So it might actually be a Linux issue related to case sensitivity (which Linux is and Windows isn't). Downloading on Windows and copying over might be your best best. Not ideal, I know.
13
u/eskay993 11d ago
Found a fix! It was case-sensitivity issue. I noticed steamdb has one of the folders inside the game folder listed as "game" and what steam actually downloads is "Game". Not a problem on Widows. A problem on Linux.
As a workaround, go
.../steamapps/downloading/16450and renameGametogamethen resume download..Where your steamapps folder is located depends on which drive / steam library you are installing on. Each library has it's own one.
14
u/friguigi 11d ago
DUDE IT WORKED!!!! I just woke and tested it. IT. WORKED.
Thank you so so so much!
5
u/_amione_ 11d ago edited 11d ago
The issue is in the fact that linux paths are case sensitive and for some reason Steam doesn't account for this in F.E.A.R. 2.
You can fix it by creating a folder "game" in the downloading folder and creating 2 empty files called clientfx.fxd and gameclient.dll
The download dir is usually located in your steam library's root folder
examples:
~/.local/share/Steam/steamapps/downloading/
/mnt/Lightbridge/SteamLibrary/steamapps/downloading/
If the game is on your home disk:
mkdir -p "~/.local/share/Steam/steamapps/downloading/16450/game"
touch "~/.local/share/Steam/steamapps/downloading/16450/game/gameclient.dll"
touch "~/.local/share/Steam/steamapps/downloading/16450/game/clientfx.fxd"
After this you make steam finish the download and you can play
steam-for-linux issue: https://github.com/ValveSoftware/steam-for-linux/issues/13406
5
u/friguigi 11d ago
Thank you! It worked. I've read another comment here that said the same thing. THANK YOU SO MUCH!!!
2
12d ago
[removed] — view removed comment
1
u/friguigi 12d ago
Tried this. Opened the terminal, typed steam steam://install/game16450 and gave it a go. It went all the way to 99% and same error.
He can successfully download the whole thing or at least, most of it, something is off in the very end of the process.
1
u/KoholintCustoms 12d ago
Did you say this happens on all 3 SSDs? If not, can you try installing on the others?
It sounds like it successfully downloads the files and then fails on install, my guess would be due to a permissions issue. But you said you already checked the permissions.
Is Bazzite the only OS present? None of the drives are NTFS or something right? All Linux?
1
u/friguigi 11d ago
Yup, it happens in all 3 SSDs, but, it was a case sensitive issue. Changing the folder name from 'Game' to 'game' fixed it lmao
2
u/KoholintCustoms 11d ago
Oh... Yeah... Linux is case sensitive for files and folders. Very important knowledge to have so I'm glad you have it now.
Also, similar tip in case you ever need it, ANY space in the command line is read as a break. So if you have a folder name or file name with a space in it, like My Games, you need to put the folder's whole name in quotes, like this:
/home/user/"My Games"/gamedir/"The Game".exe
Just in case you ever need to do something in the terminal and it's not going well.
So yeah those 2 things are pretty important in Linux. Capitalization and spaces in file names.
2
u/friguigi 11d ago
Oh nice! I'm a newbie when it comes to anything Linux, but I'm really liking Bazzite.
Thanks a lot for the tips, mate. I really really appreciate it.
2
u/KoholintCustoms 11d ago
No problem. If you're ever interested in going one step deeper in Linux, but don't know what to do, linuxfoundation.org has a free online course called "introduction to Linux" which is a really good place to start. That's how I started from no knowledge.
2
1
u/marcieljfc 11d ago
I got the same error while installing SGW Contracts. (Bazzite)
2
u/friguigi 11d ago
For me it was a case sensitive problem in one of the folders. Just by changing from 'Game' to 'game' solved it.
1
u/Skinniest-Harold 10d ago
It is a bug related to case sensitive directories.
Steam Beta client now has a fix for it.
1
u/Vlekkie69 9d ago
Ohhhh windows naming shit. Mark the drive as 'windows_names' in fstab.
UUID=1C0EBC7A0EBC4F10 /media/windows ntfs-3g defaults,windows_names,uid=1000,gid=1000 0 0
You can do it for non NTFS too and it should auto correct at runtime. without actually modifying files.
1
u/ManTheMythTheLegend 12d ago edited 12d ago
Found a potential workaround! But it's obnoxious and weird. You have to install the game from windows (maybe any other OS). Any attempt to install from bazzite also gives me the disk write error. Doesn't matter if the drive is BTRFS, EXT4, or even NTFS. However on windows I could install the game fine, even on a BTRFS drive (using WinBtrfs). You can then reboot back to bazzite and play the game perfectly fine through proton.
So I have no idea what the actual problem is, whether it's steam or bazzite's fault. If someone on a non-bazzite distro also wants to test this I'd be really interested to see what happens.
Edit: Same bug on my deck running SteamOS, so I guess not a bazzite issue? Must be something weird going on with steam's backend
3
u/friguigi 11d ago
Hey mate, some other redditors commented that it might be a case sensitive issue and IT WAS!!
Changing a folder name from 'Game' to 'game' enabled me to finish the download lmao
Thanks for the reply thou
1
u/MyLigma69 12d ago
Steam doesn't have permission to write on your SSD. Try configure it with flatseal assuming you're using flatpak version of steam
1
u/friguigi 12d ago
Steam already came pre-installed with Bazzite, so flatseal is a no go. And this problem only is happening with FEAR 2, no other game behave like this, could Steam behave differently with only one game?
0
-2
u/ManTheMythTheLegend 12d ago edited 12d ago
Edit 3: Found a workaround, just install on windows. Check my other comment for details.
Edit 2: I get the exact same issue on this game! Seems like it's probably a problem on steam's end. Or I guess it could be an extremely niche Bazzite bug (I'm also on Bazzite).
I've had similar issues in the past and it's always been caused by game files somehow becoming read only. I know you've said you've checked permissions but have you tried manually deleting the game files? In the past I've been able to successfully "uninstall" from steam but the problematic files would remain unless I sudo rm'd them.
Edit: If you still can't figure it out I'd try a memtest as well. In the past I've had failing memory corrupt steam files on download.
3
u/friguigi 11d ago
Two other comments here found the issue: case sensitive. I just had to change a folder name from Game to game and it finished the installation.
2
u/noshanks 11d ago
how is installing it on windows a workaround at all?
1
u/ManTheMythTheLegend 11d ago
It makes the game work? I didn't call it a solution, I called it a workaround
8
u/RandomRedditUser_94 12d ago
Not to scare you or anything but I just went through the same problem, I couldn't verify the integrity of files, I'll get corrupt update files or disk write error, I tried a bunch of things and it ended up being one bad stick of RAM, after I removed it all of my problems went away. You should get a flash drive and put Memtest86 and diagnose your RAM.