I’m going to try to take this in the spirit that it was provided, but you’re using a lot of "…"s, and a lot of implications that what I’m saying is obvious, for a person trying to provide earnest assistance. I wasn’t requesting technical support or expressing surprise at these things, I was merely expressing that these were the things I was generally encountering difficulty with my transition to Linux as a daily driver.

The DisplayLink driver for instance is running, and basically functional, but ends up running slowly, with distortions, and instability. It also isn’t signed, so my plan to still run Secure Boot with the distro I’m using alongside Windows is out (without a lot of faff), but that largely won’t matter excusing some specific work setups that I don’t currently have to worry about. Having useful AMD specific driver level tools on Windows that don’t exist in Linux isn’t a surprise, it is a discouragement.

Forum content and non-Reddit content are a pain to locate, especially when you don’t know how to frame your problem in Linux syntax, as you say. Communities are either open but in specific places that I will never find without already knowing about it, or happening in places that aren’t accessible without having already joined, like the Discord of the specific software I need guidance on. My experience has been that there is basic info and there is advanced info out there, but intermediate info that lets you bridge the gap is a challenge to locate, especially with subtle differences in certain steps that are distro/package manager specific. Yet I press on.