Hello all!
I am a fairly new Linux user, a Windows refugee.
I have tried a few distros, which helped me see what I like and don’t like.
This is what I have now:
Arch, with btrfs snapshots (which also show up in GRUB), secure boot, metapac for declarative package management (uses pacman under the hood, and is also cross distro), Steam, custom Proton (I use the CachyOS version and no, I don’t care about their kernel after some benchmarking). I installed a few other things but it’s mostly a gaming desktop where I do also some video production. Because I have an AMD RDNA 4 card, my mesa drivers need to be fairly recent.
But recently, after a BIOS update deleted my secure boot keys (I had used sbctl), and going down the shim + MOK route (which survives the BIOS updates) caused Windows to constantly ask for a new PIN, I have been considering going back to Fedora, which is what I used for a while before Arch.
I have fixed the secure boot thing in Arch, it’s just annoying to know that I will have to fix it again if the BIOS update in the future (it will only take me about 20 minutes, but it still makes me feel like I shouldn’t have to).
Fedora of course has secure boot and SELinux out of the box. Trying to get AppArmor set up on Arch made me want to throw my PC out of the Window, and in fact, I managed to mess it up and ended up having to chroot into my Arch to fix it ![]()
But I found a few niggles with Fedora that Arch doesn’t have when you install it with Archinstall:
- Codecs
- The mesa drivers fall behind towards the end of the 6 months cycle, that means I need to use a COPR
- Not hard to use a COPR (for example Fyra Labs is a pretty good one for that), but I just feel mesa is a core thing and I shouldn’t need to tinker to have the latest stuff
- I used to get some random Python crashes when using KDE, nothing seemed to actually ever break though; KDE on Arch just worked
- The btrfs subvolumes and snapshots would require manual set up that Arch does in a few clicks via Archinstall (I know how to do it in Fedora, it’s just laborious compared to Arch)
- Steam requires RPM fusion (I mean… It’s easy enough to turn on, but still)
Paradoxically, Arch installed with Archinstall gives me a system that just works in a way that is better than Fedora for me (due to the above). The only thing I need to do is install and activate the firewall and install Flatpak (one easy command). Discover comes installed with their default KDE installation, and it works after that. The sticking point mostly is secure boot… Which again I fixed, but something in the back of my head is saying it’s not a perfect solution and that little voice won’t shut up. I should also say that whenever Arch broke is because of something I did. Otherwise it has been rock solid.
However, take the AppArmor example, those things that I ended up breaking are rather difficult (for me at least) – and in that example Fedora and OpenSuse would mean I don’t need to worry. The secure boot thing, again, I didn’t even touch Arch this time, but I had to go fix it because of a BIOS update. While those aren’t Arch issues, they are Arch quirks. They are the result of the Arch philosophy. It’s a philosophy that I love until I don’t, and that takes me back to Arch when something else has a different philosophy I don’t like… I can’t win ![]()
I was considering perhaps trying OpenSuse Tumbleweed. It comes with SELinux, btrfs snapshots and is a rolling release.
But given that Leap dropped support for 32 bit (yes I know you can turn it on), I wonder how long it will be before that happens to OpenSuse. I only care because of Steam, no other reason. I know there is the Flatpak, humour me and let’s say I want to install it via the distro package manager as it has some advantages (happy to use Flatpaks for other stuff).
I also wonder how much faster Tumbleweed is compared to Fedora, last time I checked it out their kernel version was the same as Fedora’s (6.15 something), where Arch and NixOS were both on the latest (6.16 I think). Again because some of these kernels improve driver support, I would like to be on the latest. Also I seem to recall their mesa drivers were behind.
Has anyone tried Tumbleweed and Arch and how easy is it to tinker in Tumbleweed? How are community repos? How do they compare with COPRs generally speaking? How is dependency handling? I heard it can be dependency hell with some community repos on Tumbleweed, but I don’t know where those comments came from, and the user I saw mention this didn’t specify what they were trying to install.
I would love to know about your experiences.
Thanks!