The 580 legacy driver is DKMS, so there shouldn’t be any maintenance beyond what is already required for any other DKMS driver, which would be handled by pacman anyways. So no need to worry about kernel updates

If you’re adamant on keeping those GPUs, Nouveau would be the only path forward - eventually paired with NVK for Vulkan acceleration once that’s good enough for primetime. Pascal was dropped because of the lack of a GSP module as well as age, so the newer Nova driver won’t support it either

100%. I don’t mind the idea of a halo 4 it’s just that it didn’t have to be chief in it. 343 just uses chief as a crutch because they fundamentally misunderstand Halo

I did think bringing back the halo wars crew was a good idea i just wished halo 5 had nothing to do with it. Maybe continuing from there with Jerome taking the spotlight wouldn’t have been so bad

Also the TV show. It still boggles my mind how that fucking thing was made despite all the lore Halo has. But having a TV show or movie in itself wasn’t a bad idea. Following a crew of ODSTs through the covenant war would have been pretty awesome

Generally speaking, most if not all hardware running Win 10 will be able to work on any Linux distribution making a few exceptions where external drivers can be found. Normally though, this will not be necessary as it will be pre baked into the kernel with no interference from you

That being said - Mint runs an older version of the kernel compared to the current state of desktop Linux and may not contain certain drivers for hardware that came out after that specific kernel version was released. You can use a distro that favors being up to date over long term support, such as Fedora or Arch (if you’re willing to put up with setting up Arch) if that crops up. But generally, if you’re running win 10 still this shouldn’t be a problem

Without knowing your hardware, i can’t really say more though. Just try mint or any other distribution on a live usb and if it works there, then it will work when installed

Yeah. The behavior i stated was how it works in Gnome. In KDE since Xorg passthrough is a formal thing, the behavior is different based on those options

Xorg global shortcuts will work for anything using Xwayland, but not in anything thats wayland native

For example, in a game (using wine, which uses Xorg by default currently) your global shortcut will work. But in a wayland native window like Firefox, it will not if its the active window

The patches exist for Wayland/Xwayland but the Compositor itself has to be patched as well for it to completely work. KDE does not have its fix for explicit sync merged in yet so its not patched as of Plasma 6.0.1. It did make things slightly better but all it did was make the flickering less frequent, but its still there.

Yeah. I have a multi-monitor VRR setup as well and happened to have a 3090 and not being able to take advantage of Wayland really sucks. And its not like Xorg is any good in that department either so you’re just stuck between a rock and a hard place until explicit sync is in

Lets see what will happen first- me getting a 7900xtx or this protocol being merged

Better, but still shit. The main holdup right now to what I see is wayland-protocols and the WMs adding Explicit Sync support as the proprietary driver does not have implicit sync support. Its part of a larger move for the graphics stack to move to explicit sync:

https://gitlab.freedesktop.org/wayland/wayland-protocols/-/merge_requests/90

Once this is in, the flickering issues will be solved and NVIDIA wayland being a daily driver in most situations