taaz

Nvidia module won’t build

how/why?

If you have 13/14 Gen Intel and it errors out with random SIGILL errors you are being hit by the Intel instability problem.

At least for me that was the only place where the instability surfaced before bios updates and tweaks.

Yeah that has always been the downside, you have to pay for the "custom device you can geek out yourself"

Yeah geek material is probably the best tag and category for Turris, and I feel you with that old hardware, wish I had the same thing with just a bit better/modern soc and more ram.

I've returned back to it, when Prime came there were few in the community that stopped as I did.
The reason for me now is to get myself to move/walk a bit more (has been somewhat successful in that) but I don't play it super actively and completely ignore the new scouting thing which is basically just "be our street-view monkey so that we can sell actual data".

Also if I didn't have active community where I play I don't think it would last too long at all.

:)

Optimally we wouldn't I think but it usually boils down to being the lesser evil.

Uv is currently only a pip replacement as a dependency resolver (and downloader), it was actually adopted by astral from a different dev afaik

You could also (hard) limit the total (virtual) memory process will use (but the system will hard kill it if tries to get more) with this:
systemd-run --user --scope -p MemoryMax=8G -p MemorySwapMax=0 prismlauncher

You would have to experiment with how much Gs you want to specify as max so that it does not get outright killed. If you remove MemorySwapMax the system will not kill the process but will start aggressively swapping the processes' memory, so if you do have a swap it will work (an depending on how slow the disk of the swap is, start lagging).

In my case I have a small swap partition on an m2 disk (which might not be recommended?) so I didn't notice any lagging or stutters once it overflow the max memory.
So in theory, if you are memory starved and have swap on a fast disk, you could instead use MemoryHigh flag to create a limit from where systemd will start the swapping without any of the OOM killing (or use both, Max has to be higher then High obv).

Fabric is one of many mod loaders ala Forge. It's newer and less bulky then Forge (but afaik it already did have it's own drama so now we also have a fork called Quilt, the same goes for Forge and NeoForge).

The mods I've specified above can be considered as a suite replacement for the (old) OptiFine.

E: For example this all the mod loaders modrinth (mod hosting website, curseforge alternative) currently lists:

As a side note and a little psa, if you need to squeeze out more overall performance of out of MC (and you are playing vanilla or Fabric modpack) I very much recommend using these Fabric mods: Sodium, Lithium, FerriteCore and optionally Krypton (server-only), LazyDFU, Entity Culling, ImmediatelyFast.

Big modpacks that add a lot of different blocks will also always explode the memory usage as at the start, Minecraft pre-bakes all the 3d models of the blocks.