We are well beyond the point of a majority of common hardware having built-in kernel drivers and userland software for extra stuff like RGB control that the best advice is rather avoiding Linux, to instead avoid the trash hardware (NVidia for the time being, GoXLR, Broadcom, etc.). My GPU, audio hardware, network interfaces are both popular products and have worked out of the box for years now.

Assuming you are installing your Steam library on your ext4 partition rather than ntfs one for your Windows install, BeamNG will likely be the easier game to diagnose for your game crashes on launch. The log file to find for BeamNG is located by default in steamapps/compatdata/284160/pfx/drive_c/users/steamuser/AppData/Local/BeamNG.drive/0.32/ as beamng.log. By default in a standard Steam install, your steam library is located at ~/.steam/root/. I am unsure if Bazzite installs Steam as a Flatpak. If it does, the default Steam library should be at ~/.var/app/com.valvesoftware.Steam/data/Steam/. If you chose a custom location for your Steam library, it will be wherever you chose it to be.

How are these games (Lethal Company, BeamNG) installed? If they came from a Windows install on NTFS, just reinstall them on a proper filesystem and then you will be able to play them through proton. Roblox just doesn’t work so it’s not worth testing.

2-2-1 still insinuates having a remote backup. I don’t see how this particular threat destroys a 2-2-1 setup.

Add SKSE manually, add it as an executable option in MO2.

I’d imagine mpd with one of many frontends would work well enough. You’d just need to use a dummy music library directory with symlinks to your four music storages for mpd to pick up and catalog everything.

On my Fedora KDE install on 40, hibernate is now an available power option. The install has been in upgrade cycles since 35 at this point. I would imagine that barring different DEs showing different power options being a possibility, it is more on detecting hardware compatibility for functional hibernation.

Tiny 11 comes in two variants:

Tiny11 Core is not suitable for use on physical hardware as it outright disables updates. It’s best used for short-term VM instances.

Tiny11 also has problems with updates. The advantages gained through Tiny11 will erode with applying Windows updates. The installer is more tolerable than Windows 11 by not forcing an online account (but still needing to touch telemetry settings). Components like Edge and One drive will inevitably rebuild themselves back in with cumulative updates. If this is something that coerces you to not update your system, don’t subject yourself to using Tiny11. Additionally Tiny11 fails to apply some cumulative updates out of the box, which could be a further security risk.

I recently tested the main Tiny11 in a VM based on a different user recommending it in a now deleted thread. I was skeptical knowing the history of Tiny10 onward that 11 would actually be able to update properly, and NY findings backed up my initial skepticism of functional updates.

Use the OCI through podman or docker.

What compositor (desktop environment) and distro are you running for things to behave that poorly?

Bazzite pulls its kernel (fsync) from https://copr.fedorainfracloud.org/coprs/sentry/kernel-fsync/packages/. In this case, it is based on kernel 6.8.1.

For rpm-based immutable images, you can always check the project’s Containerfile for what package is being pulled for the kernel. On most normal distros, you can also boot into the live image, pull the package cache and check the latest package version for the kernel.

EDIT:

An example for fedora in this instance of ‘traditional distro’ would be to dnf makecache && dnf info kernel.