In my experience, Seagate exos are only “loud/clicky” when under HEAVY write loads. Mostly they’re pretty quiet with a very low drone at worst. In any decent case it’ll be pretty negligible. With headphones on doubly so.

Absolutely this. Relatively quick and clean, no messing with installation or reconfiguration. That is, assuming your data isn’t completely corrupted and the old drive doesn’t just outright fail during transfer… But if that happens you were screwed to begin with.

If you’re gaming you might as well just jump on Bazzite if you’re already interested in Kinoite. Very similar base, but Bazzite has some extras Kinoite doesn’t and it makes a transition into an immutable distro easier.

AMD with ray tracing isn’t great. Not as bad as it used to be, but pretty lackluster overall compared to Nvidia (and to a lesser extent Intel’s GPU offerings). Linux ray tracing via Proton is also not as optimized at present, so that can take something “passable” in windows and make it unplayable on an AMD card in Linux. If you get something overkill for the resolution you’re playing at that can somewhat make up the difference.

If you’re doing 1080p the 6600 is pretty solid. Or 7600, really. It CAN do higher resolutions, but then you’d need to start doing FSR scaling or drop settings to keep things smooth/consistent.

I’m just here to say Bazzite all the way. No clue what that poster meant by breaking issues or problems with rollback… Bazzite is literally designed to be the antithesis of both. The ONLY time I’ve had a problem with it was rebasing my laptop between Silverblue and Bazzite. Technically allowed, but I wouldn’t advise it as that did cause me stability problems. I’d blame Silverblue more than Bazzite in that case, however. A clean Bazzite install has been solid ever since.

Possibly dumb question: why not use an Authentik outpost with a reverse proxy to enforce SSO? It wouldn’t be “baked in” so to speak, but it would be fully OIDC and as long as you’re just running it through a web browser. Biggest downside is you’d need 2 logins (one for the outpost and one for the app). I’d assume the sso is specifically for the extra security though, so that shouldn’t be a problem outside of it being a little hassle.

Remnant 2. Gotta finish Cyberpunk 2077 (again) first though. The damn DLC adding extra achievements has thrown everything off!

Isn’t AMD’s HEVC/265 still decent, specifically? I feel like I read that somewhere years back. 264 has always been a weak spot for them, however.

Software-wise, it seems that the relatively fast adoption of flatpaks and other containerized formats somewhat solves the typical dependency hell that was so common in Linux just a few years back (and to some extent still is an issue today depending on your distro and use case). The hardware support side is a little harder. That’s going to be up to vendors to play nice with the Kernel team and/or introduce reasonable userland software that doesn’t break the golden rule. Until Linux gets more market share the latter isn’t likely to happen. A nice side benefit of the emergence of immutable and/or atomic distros is that users can play around and try things with much lower risk of bricking their systems, so I’d also consider that a step closer in the “it just works” department.

Very true. But brute force checking through tons of different settings for each camera you need to configure is not fun. I couldn’t seem to find any kind of “known working configs” database or anything either. Every camera seems to be different in what it expects, outputs, authenticates, etc. Once it’s set up, I agree, maintaining the config is easier. Having all your cameras match in model and firmware version probably makes the whole endeavor MUCH easier.

AmCrest and Frigate together are SO good. Integrating Frigate with Home Assistant was also insanely easy for quick viewing and notifications. That initial Frigate config is a bit of a bear- but once you’re past that I cannot speak more highly of it.

hunter2

My friends and I all LOVED the pick-up nature of SG1. We’re all adults with busy lives, so hopping into a ~5 minute casual match was just so easy. And the casual nature made it feel like we could have success without “grinding” the game. I guess that is explicitly not the intent of SG2.

The shift from “we’re making a fun and relatively casual arena shooter with a neat gimmick and extremely rewarding fundamentals” to “we’re making a generic e sport shooter” was swift and, frankly, uncalled for.

Even with nvme drives which supposedly “don’t need” to use BFQ, I STILL always swap it since it maintains responsiveness across the system during heavy IO loads. I used to have similar full system freezes when downloading steam games which notoriously overload your IO in Linux. BFQ was the solution every single time.

Edit Try following the instructions detailed in this post to add a systemd rule to set the scheduler: https://stackoverflow.com/questions/1009577/selecting-a-linux-i-o-scheduler

The second answer that shows an actual rules.d file example has always worked for me. If using nvme or old school spinning rust you’ll need to change it up a bit. Instead of “noop” set it to “BFQ”.

Try swapping to BFQ io scheduler and see if that makes a difference.

Anyone who ritualistically buys Dell. I believe Intel is on the record as having called Dell “the best friend money can buy.”

Are you on Gnome, KDE, or some other desktop environment? I know KDE Wayland and Nvidia do NOT play nice (presently).

Are you running it through Lutris? Steam with Proton? That error seems decidedly like a Wine specific problem, which Proton should have ironed out at this stage for this particular game.

*Unless you’re trying to play on hardware with incomplete Vulkan support. Then it’s a hardware support problem that is unlikely to be fixed in a reasonable timeframe.