view the rest of the comments
Linux
Welcome to c/linux!
Welcome to our thriving Linux community! Whether you're a seasoned Linux enthusiast or just starting your journey, we're excited to have you here. Explore, learn, and collaborate with like-minded individuals who share a passion for open-source software and the endless possibilities it offers. Together, let's dive into the world of Linux and embrace the power of freedom, customization, and innovation. Enjoy your stay and feel free to join the vibrant discussions that await you!
Rules:
-
Stay on topic: Posts and discussions should be related to Linux, open source software, and related technologies.
-
Be respectful: Treat fellow community members with respect and courtesy.
-
Quality over quantity: Share informative and thought-provoking content.
-
No spam or self-promotion: Avoid excessive self-promotion or spamming.
-
No NSFW adult content
-
Follow general lemmy guidelines.
If the cable made a difference, then that may still be the limiting factor. It's not totally unheard of for Windows drivers to be a little more fault tolerant or better tuned for suboptimal cable connections. If you aren't already doing that, try using a certified cable that supports the bandwidth and features you require for your setup. Besides that I guess you could only try the newest kernel version you can reasonably install.
The cable only made a difference on Linux, not that it worked completely even with the other cable. On Windows, it worked with either cable.
I know, I did read your entire post. As I said, it's not unheard of for Windows drivers to be more fault tolerant in suboptimal conditions. For example: Windows GPU drivers in the early days of HDMI 2.1 needed a lot of tuning for tiny oltage adjustments to ensure signal integrity if your cable wasn't exactly up to spec, basically compensating for a "bad" cable, whereas the Linux drivers at the time didn't really try to do that. This doesn't have to be the case for you, but it should be relatively easy to test.