• 0 Posts
  • 111 Comments
Joined 7 months ago
cake
Cake day: June 23rd, 2025

help-circle






  • The system update needs to be on a FAT32 drive without a label. The label shouldn’t matter. The update needs to look like a single folder on the root of the drive called $SystemUpdate. Plug it in, reboot the console.

    If your console is modded it will specifically stop that process unless you rename that folder, but if you don’t know what you are doing then don’t mess with anything that touches the nand. Updating a modded box is its own process.

    Also, just a fair warning, the Xbox compatibility files don’t come from a system update anyway, you need to use a program like Xploder to add the compatibility partition to your drive and manually copy it over. You should take some time and read up on SevenSins how to proceed.


  • You need to set an override in your environment variables to force it to use the gfx1030 kernel modules, but otherwise you shouldn’t have too many issues.

    It’s unofficial, but the 6700xt uses the exact same core as one of the supported enterprise cards, so just using the drivers for it generally works just fine. I use a 6800M personally.

    If you are struggling to get rocm installed at all then stop using the amd guides and just install the pre built binaries directly. Fedora packages them in their repository and in my experience rocm just works once you run dnf install rocm*.








  • New instructions and only having to deal with one codebase are big, but there are some fringe reasons regarding security that I could see also being a factor. A 32-bit processor means something like a thunderbird athlon on the high end, maybe an old Pentium 4. Single core and pushing 30 in the best cases. You need an operating system that supports that chip, and there really is only so much you can do to make that setup even work in 2025.

    It’s more a matter of why support that? Trying to run steam on a single core Athlon from 2000 would be painfully slow, to the point of being unusable. You couldn’t reasonably even keep steam running with a game, it would hog too much CPU. It’s possible to try it if you have an ancient tower laying around (don’t use your real steam account online with something like windows XP, it will be compromised in seconds connecting to the internet).

    People with systems like that are going to need to use gog installers or use period accurate methods to install games. 32-bit only processors were already on the chopping block when steam came out, they really can’t handle modern steam. It would be a bit unreasonable to expect them to add a separate version for those chips, especially with the vulnerable operating systems they require going online being an issue, so we are left with a vestigial feature of 32-bit support for no great reason.

    It really just makes more sense to cut it than keep it for the sake of novelty. There is some liability in keeping it, as well as technical overhead.

    Sorry for the ramble.