i need some info an advice on using TUXEDO os for my custom build ryzen pc
right now i cant seem to get kde neon to install even with the latest stable release
a script fail at 89% keps f’ing me up
so i wanted a os that had kde base that supports wayland & vrr an hdr the way neon does
so i went with tuxedo but id like to know some things an get some advice so i dont have to go back to
to Ubuntu
i want to know a few things
does it support vrr ?
does it support gpt with btrfs filing system ?
does it have zram enabled or can i install it an enable ?
can i add an enable btrfs with force compression with zstd to the custom partitions
an in fstab how should that per partition string look ?
is this a custom fstab string that will work in tuxedo
So I don’t know the things on the list.
But for kde with plasma(I am new to this)
VRR
Zram
I use nobara.
I am currently not using the more customized weebara one(I messed up after getting rid of Windows).
One issue to point out for me.
On the non weeb nobara I get more kde plasma crashes. Don’t know if there is a major difference between the two versions of nobara.
for the native kde neon no just offline installer , but for tuxedo yes although something went wrong when updating vi the the discovery app after reboot the network can access the internet but can still access the home network it printer an nas
space_cache=v2 afaik is deprecated as of latest kernels.
compress-force is questionable choice because it asks the filesystem implementation to not give up on compressing data it can obviously detect is not compressable
It’s not deprecated, it’s the new default. So there’s no point specifying it explicitly.
You’re overthinking the btrfs parameters IMO. The developers have a pretty good sense what good defaults are, there’s usually no point changing them unless you have a specific reason and know what you’re doing. E.g. async discard is default too (if an ssd is detected). commit=90 will only risk losing more data in a crash, and I fail to see the point especially for a desktop system; you use nodiratime (why?), while still having access times for files. Compress-force is rarely a good idea, since it will even compress uncompressible data (e.g. video/audio that’s already compressed), etc.
I don’t use KDE personally but I think it has vrr support. But linux being linux that may depend on your GPU as well.