Additionally, Steam is still mostly (or entirely) 32 bit so the system is working much differently than it does with native 64 bit apps.
As far as I understand it, the situation is a bit more nuanced than “Steam is 32 bit”.
The Steam client has been transitioning to 64bit, but Steam still has 32 bit components and, more importantly, the Linux client still requires 32bit userspace libraries (including 32bit glibc and graphics drivers).
Regardless, testing the Flatpak version of Steam would be an interesting experiment in this case, since it could help determine whether the issue is related to the host’s 32bit userspace rather than Steam itself, since heroic launcher seems to work?
Heroic has been installed from the GitHub via Konsole magic spells.
Also:
Today’s test:
I’ve use the Windows SSD to install SM2. It completely installed without issues and could launch and get in a level.
It’s because during the "
" I’ve used the older Kernels in Grub2 too, and they, tl;dr , “worked just as well (BAD, just as BAD, it’s a joke), and ALL presented the SAME errors”.
Just by pure chance and “luck” (if this situation overall can be considered lucky) it then booted normally in 7.1.12.200.and I could re-install 7.1.13.200.
Now we have the 7.2.4-200.fc44.x86_64 (64-bit) Kernel and it does the same.
Opened the PC. Checked the Sata Data connections. They were all fine.
I’ve updated the system.
I tried installing SM2 through Steam.
Black screen.
Reboot.
I tried installing Dead Space 1 on the Boot SSD, goes fine.
I tried installing Dead Space 2 on the HDD, goes fine.
I tried convalidating Death Stranding DC’sE on the same SM2 SSD: it didn’t give any problem.
Maybe it was because it had enough space to work, now that SM2 was completely gone, or because it was just convalidating instead of writing…
- With SM2 installed the free space was 15 of the 500gb. With it uninstalled it’s around 110gb.
That said, I’ve then copied SM2 from the W10 SSD to the 500gb one.
As you can see, it can copy it whole without any issue.
After the copy ended I had to copy the appmanifest_2183900.acf file from another PC to this one[1].
I convalidated the files (to rebuild any folder which may miss) and then tried lauching it.
It could launch and get in a level.
My hypotheses:
Since Steam and Dolphin faced the same challenge (writing down SM2) I think Steam is at fault here.
The cause:
Steam first downloads, unpacks and installs new files in a “Download” folder, to then move it in the “Common” folder.
It could be that it either takes too much space, or my version of Steam is borked and I need to reinstall it.
I may or may not test the FlatPack version of Steam if this can’t be solved, but at this point I am pretty sure that a reinstall of the OS may just fix this.
An old issue I had with this same hardware was this:
, because Steam doesn’t have a “add Steam game which is already present” button. If you want to add a game by installing it, to then convalidate it, you must have enough free space for Steam to allow you to do it (in this case, 90-ish gb) ↩︎
Just watched a video which talked about “systemd-nspawn” in case of a bricked update.
Would this help here in any way (either if the PC suffers a “final bricking” or if I wanted to “solve the black screen issue”)?
I must ask instead of thinking because I don’t feel well enough to grind my mind gears right now…
Update:
Some days ago I was once again using the PC, updating OS and games alike…
Steam made the desktop disappear again.
At this point unless someone has some suggestion I will just reinstall the OS to see if the problem persists, because I can’t really do a “deep diagnosis with electrical probes and whatnot”.
It could be that the case is so messed up that it’s giving problems to the PC, but I can’t say for certain.
As soon as I’ve enough strength once more, I’ll reinstall the OS. Luckily I have the data which is annoying to get back on different partitions and disks. There is TWO games which may need to be reinstalled if they got corrupted, but that’s life.