| I built myself a new PC recently and jumped straight to installing Linux on it. Unfortunately the experience isn't quite as plug and play there either... In terms of everything I had to do: - Disable iGPU in BIOS because on a cold boot the system would "latch on" to the iGPU (iGPU was GPU 0 and dGPU was GPU 1, which some programs I guess interpret as "GPU 0 == primary GPU"). Everything is fine on a warm reboot where it assigns dGPU to the 0 slot and iGPU to the 1 slot - Get a special dongle to get 4k120Hz support over HDMI because the driver doesn't support it. The dongle should also enable VRR but needs multiple kernel patches to do that. Applying the patches causes varying levels of graphical glitches - On waking from S3 the HDMI audio is dead. I tried various kernel arguments related to power management that various people had reported working for them but ultimately none of them ended up working for me so this one is still broken. Gave up on HDMI audio out and used an SPDIF cable instead (my AVR has been a magical problem solver here but most people aren't going to have a separate device to do that for them) - On waking from S3 the wifi doesn't automatically reconnect. Solved with a systemd unit that just toggles it off and back on - The audio out kept changing away from the one I set. As far as I can tell there's no easy way to set the "default" like you can in macOS or Windows, so I had to fudge the priorities of the built in devices a bit with a Wireplumber config While debugging all the issues I've been bouncing back and forth between various kernel versions and patches. The fact that you can do that is awesome, but the fact that you have to do it to fix and debug issues is unfortunate. Just as an example, while debugging the audio problems I found a ticket that looked like it could be related on the amdgpu driver issue tracker where someone reported a similar problem, and the response from AMD was "please bisect the kernel"... That's just not something that most people are going to be willing or able to do. AMD GPUs are even supposed to be the well supported platform compared to Nvidia. I will say though, this whole debacle with the dongle sure had me wishing I could just stick an opaque-but-vendor-supported blob in like you do with Nvidia and get HDMI 2.1 working out of the box. At least on Windows, IME Microsoft ironed out a lot of these types of driver issues in the Windows 7/10 era so that things like sleep just tended to work. It's been a while since you had to track down the right driver for your hardware manually. They just kept going downhill from that point forward with boneheaded decisions like sticking React Native or whatever in the start menu and forcing shovelware down people's throats. Even though I was having all these problems with Linux I personally won't go back to Windows, but I'll think twice about recommending it to my non-tech friends and family. |