- cross-posted to:
- linux@lemmy.ml
- cross-posted to:
- linux@lemmy.ml
You must log in or register to comment.
I’ve noticed a lot more talk about Bazzite lately and I’ve been wanting to at least give it a try as a daily driver. I’m not us gaming though I do dev work and what have you. For people on Bazzite that also do that, how is it? easy to set up for that like say using Doom Emacs or what have you?
I use Bazzite for my HTPC (AMD NUC).
For a “set it and forget it” gaming console experience? It is awesome. It feels like I already have a GabeCube under my TV (that I bought for probably half the price…). And when I have to do more complicated things than “run the update once a month”, I just ssh in from either my desktop or laptop.
But… it is an immutable/atomic distro. So if the packages you want to add are flatpaks or appimages? You are probably fine. Otherwise? You get into a mess where you are adding packages to your layers (?) and kinda feel like you are playing with fire. I did that to get iperf3 installed to test some networking upgrades and it was mostly painless but it was also a really bad experience versus
sudo dnf install iperf3. And… even on machines where I spend 90% of my time ssh’ing into servers, I still tend to want to install a good amount of local packages as a developer.So my suggestion would be to stick to Bazzite for gaming first platforms and continue to use whatever distro you like (Fedora for the win!) for “real” computers.
Also, if you aren’t as annoyed by atomic distros as I am, I would still be wary of Bazzite. They have a lot of different SKUs and I don’t care enough to try to parse what each one does. But the common use case is to basically treat a machine like a Steam Deck… which means you boot into Big Picture with essentially no login screens or a REALLY insecure pin code. And then you switch to desktop mode with a single click.
There are ways to harden that (and very much an argument of whether you need to harden a machine in your home). And Linux, generally, has very good protections by actually requiring auth for
sudo. But I already feel sketchy that I am logged into Steam/GoG on a box with almost no protections. But I also live in an environment where I don’t have to worry about someone buying 10k in fortnite bucks on my TV.bazzite is an excellent all-round linux distro for contemporary spec computer (gpu, >=16GB ram)
i use it for rust and c# dev work using distrobox. all gui ide’s and tooling run in the containers with excellent performance
i also layer a handful of packages on the “immutable” or atomic base os for some carefully chosen tools i want. the base os is generally well fitted out
very highly recommend as daily dev driver and also gaming
Bazzite comes with no dev tools pre-installed and a lot of gaming-related stuff.
Of course you can add what you need through flatpaks, containers or image layering, but why not choose a distro aimed at dev work in the first place?Bluefin and Auroa are for you, changed how I program and organise, our you can make your own template and just pop everything you’re missing in the containerfile similar to how nix pkgs works
I’m a huge fan of Aurora, the least popular ublue desktop OS. Bazzite is great, too. But I prefer Aurora.
Hell, even my wife uses it and has no complaints.
If you don’t mind a learning
curvecliff, NixOS is great for development, and I haven’t had any issues gaming either.Recommending someone who’s curious about Bazzite to maybe check out NixOS instead is… Certainly something lol
AMD is more stable in games where Proton/Native Linux builds have weird issues, sometimes leading to a 9070xt leading a 5080 (even beating a 5090 in like starfield but like, lol.) Raytracing still heavily prefers Nvidia.
Does not directly compare to windows benchmarks. Low V-ram causes failures. Some native versions for linux are actively worse than running windows through Proton Loading Shaders before launching game can take long (longer on Nvidia cards), and can be required very often.
Suggest watching the last 10m where they talk about these issues if you don’t have time for the whole video.
I’m so happy to see some big channels doing these Linux tests. I know it’s probably way more difficult since there are thousands of distros to try!
You don’t need to test every distro.
Honestly you could capture 90 percent of the market with just arch and Debian/Ubuntu.
You could add 2 or 3 of the gaming focused distros for comparison however since they tend to be built on top of the two above things are more likely going to vary based on configuration more than which distro or de you are using.
solving anti-cheat would basically seal the Dingus
Enabling anticheat means the user must sacrifice many of their core freedoms just to play a video game. And in principle anticheat will never fully prevent cheating short of pointing a camera at the user and watch them the whole time they are playing.
I hope Linux community can push back. This whole thing is idiotic and harms the consumers.
Enabling anticheat means the user must sacrifice many of their core freedoms just to play a video game.
Lots of games support anti-cheat in Linux. It’s critical to note that anti-cheat in general is not the issue.
Kernel-level anti-cheat however is. It’s a massive security issue and something that everyone, including Windows users, should roundly reject.
I really like that now some Content Creators are working on providing useful information for Linux gamers. Especially information like bad Frame pacing or “unreasonable” bad performance for some certain games for certain hardware is a very important information to make a good decision when buying a card.
Me personally I am not very interested in the performance comparison between Linux and Windows. I choose Linux as my daily driver for specific reasons, and game performance was not a high priority. But knowing which Hardware might have strange performance problems compared to other Hardware if I wamt to game is always a very nice thing.
I liked that the Intel B580 was included in the charts. This gave me some usefull information for comparing it to a AMD 9060 XT. Only thing I am missing is if it is the 8GB or 16GB version of the Sapphire Pulse. But I did not check their Blog/Site post yet.
100% this. I’ve been on Linux longer than Steam has, and I’m not changing anytime soon. I’m probably also not going to buy Nvidia (I value FOSS drivers), but maybe I will if the performance gap is significant enough.
If nividia just dropped a driver the quality of their windows one randomly one day. I would expect like 70%+ of the Linux community would suddenly be buying a Nvidia card no questions asked.
https://www.youtube.com/watch?v=ovOx4_8ajZ8&t=2746
I’m not sure I quite understand the issue Steve has with things updating when adding new cards.
Sure, updates during a single benchmark series is a problem but what is the issue with the system being updated for the next benchmarks?
Proton/amdgpu/Mesa receiving updates is no different than installing newer “Game Ready” drivers when a new GPU comes out.
I assume they don’t go out of their way to install older (potentially incompatible) drivers on Windows just so they can compare two separate benchmarks.
Besides that, after disabling Flatpak and rpm-ostree updates in Bazzite, the only remaining variable is Proton. Which should be easily fixed by manually copying a fixed Proton version to their compatibility tools and using that.
Without re-testing their entire suite of cards for every new card review (which is cost prohibitive), performance changing from updates would make the comparisons between cards less useful, as it cannot be determined if the newer card being tested is better or worse purely on the merits of the hardware itself, since newer software may be artificially making it look better or worse than the tested cards that came before, and thus the actual integrity and usefulness of the testing comes into question.
They are trying to assemble a like-for-like dataset that doesn’t require their entire catalog of cards to be regularly retested to ensure that it remains like-for-like. Keeping all the software the same across tests ensures that they can add new data piecemeal and still retain an apples-to-apples comparison.
That makes sense.
So the best option seems to be to note updates for newer cards down until the automated testing can be done on Linux as well.
AFAIK, It’s not an issue of automated testing, and I don’t believe they re-test all their cards on Windows with every new review either. Instead, they maintain the same versions of software on Windows as well until enough time has passed and enough updates have piled up that they do finally re-test everything with new games to create a new dataset to compare against. They’re trying to do the same methodology on Linux.
Instead, they maintain the same versions of software on Windows as well until enough time has passed and enough updates have piled up that they do finally re-test everything
I’m not that involved with their testing procedure but doesn’t that put newer cards at a disadvantage?
They lack any sort of driver optimization if the release drivers are never installed.
That’s a good point. I went back to the video to rewatch it, and turns out I totally missed where they said they only freeze things during a testing phase, then unfreeze it after they’re done and allow updates to commence as normal.
They mentioned that due to Linux receiving more frequent updates often with meaningful performance improvements, they’ll have to throw away older data and re-test more often on Linux, as Windows doesn’t really change much in performance between updates. So I would guess that they would use release drivers with new cards, and likely would only re-test their entire suite if the release driver also gave a big performance boost on older cards.
