I did it. For a few years now I’ve wanted to make the jump but lazyness and a bit of worry that my main game wouldn’t work very well kept me from it.
Then some effing windows update caused ridiculous stuttering on games (or maybe it was a auto-update of some other hidden thing, I couldn’t figure it out) so I decided that if I needed a system wipe, might as well as try gaming on linux.
Honestly? Much easier than I expected. Install Steam, turn two options on and 90% of your library is ready to go. I had to tinker with getting freesync to work (ended up just switching to wayland, which just worked) but other than the plugins I use for my main game requiring a bit of more work, smooth as butter really.
So yeah, if you are a lazy gamer like I am, next time you do a system wipe or get a new computer, try installing linux first. Don’t even bother Dual booting it, if you don’t like it just reinstall (setup your usb drive with ventoy and the images you want to try out.)
Have you been able to try a more recent kernel version? It may have improvements in the driver situation.
Even 6.9 does not have the fix yet. Seems one of the two bugs is on roadmap for 6.11
Do you know what your Intel connectivity chip is? I’m curious.
Intel ax211 was the first one. Ax210 had same problem, as did the ax411.
But the bug has something to do with how the motherboard initializes the devices.
They all work fine in other laptops
I have the ax210 installed. Interesting. Is this an intel chip on this mobo? I wonder if you’re running out of PCI address space to map the devices as there have been some changes to how this work in the kernel. You migth try
intel_iommu=off
as a shot in the dark if it’s not getting detected at all, if you have an intel chip. Doeslspci
see the device at all?It’s an AMD machine, lspci sees the devices. It just can seem to initialize it, sometimes. Every now and again it just starts working if the machine was unpowered for a few days.