cross-posted from: https://lemmy.world/post/16149785
Cross-posting here for more opinions.
Gentlemen, just for context, I usually use Linux. I have been a user of Debian, Ubuntu, and Fedora for a few years.
Recently, I acquired a decent graphics card (GeForce RTX 4070) and decided to uninstall my Windows and install Linux.
I saw that Pop!_OS already has an image with everything pre-configured for Nvidia. Is this pre-configuration worth it, are the games more stable on this distribution, or is it the same as manually installing Nvidia’s proprietary drivers on Manjaro?
If you get an update, and after that update your system doesnt graphically boot anymore or something, you can use
sudo ostree admin pin 1
andrpm-ostree rollback
to switch back to the working version and make sure it never disappears.Then you can wait for a next update (still no good update info mechanism afaik) to fix it, try it, unpin the saved version and go on.
But there is no automatic repair voodoo anywhere, on any distro. That driver is proprietary, only NVIDIA can fix it. rpmfusion packages it to work on Fedora, Fedora Atomic helps making this very unstable mechanism more failsafe.
But you are still relying on 3 entities (NVIDIA, rpmfusion, Fedora, (uBlue)), with NVIDIA not caring about Linux that much, instead of 1 (Fedora) like with AMD, where drivers are FOSS and can be adapted for Fedora specifically.
AMD does not opensource a lot, and ROCM or the entire amdgpu-pro driver is a similar situation. But at least the basics work.
Consider to revisit this, cuz this is basically (at least for me) most of uBlue’s schtick:
“No more building drivers on your laptop, dealing with signing, akmods, third party repo conflicts, or any of that. We’ve fully automated it so that if there’s an issue, we fix it in GitHub, for everyone.”
And the way it’s setup, is so that you don’t get the broken update ever on your device in the first place.
So, contrary to what you might expect, this black magic (or just excellent engineering) somehow does exist.
uBlue does not repair anything, they dont automatically detect a broken driver on your system and block an update.
This would be possible, but slow down boot (running some GPU benchmark on every boot via a systemd service, if it fails run the commands that I mentioned).
rpm-ostree is awesome, and has the potential to do that.
In theory yes, but this would mean uBlue is some kind of stable distro. I dont know, at least their base images just get updates.
Their big advantage is that they dont have the legal restrictions, so they can ship 1:1 the system you run. I dont know if they do, but having some automated benchmark tests on real hardware with these devices would be useful.
But that costs a lot of money. uBlues trick is that they can run their whole huge project for free on Github.
But for sure, the dependency issues will not occur. But this does not guarantees that there are no issues on bare metal.
Or a stable branch, Bazzite was longer on F39 for example. I use the
:latest
branch which automatically gets upgraded to the latest version, which they determine. So having an:testing
branch that is up to date, and slowing down the releases of the latest branch, could help.I think we’re misunderstanding eachother. So perhaps consider to outline if you agree with the following:
testing
branch; even Bazzite has.Yes agreed.
I didnt know they have testing images, but makesbsense in their flagship variants.
I miss the old website with the full image list.