Nah. I’m just gonna hope distros once the paper I’m submitting is accepted and I don’t need this machine again. I think I’m going to go fedora so I can stay closer to bleeding edge on the kernel.
I have linux issues every time I have a “new” machine, and it makes sense. Linux is a volunteer/ opensource project. It isn’t getting chipsets before, and building drivers in advance of hardware releases (at least it mostly isn’t; I understand that some times it does).
Because of that, the newer your harder, the crappier it works. The longer your hardware has been around, in-general, my experience is that Linux becomes an “it just works experience”.
I built a new 9950x3d + x870e system last year. trying to use the motherboard’s wifi would kernel panic things. couldnt turn bluetooth on and off. couldn’t control the RGB.
Now, WiFi works great. Bluetooth works great. OpenRGB supports the RGB. Things are great. Took time to get here, but we got here.
I use ethernet for everything, so even now I don’t use WiFi. I only figured out it worked because my internet was out a few months later and needed to connect to a hotspot, and was pleasantly surprised that it was not crashing. I also don’t really mess with RGB or bluetooth, so I cant really comment on those either. The motherboard itself always worked, it was just the integrated chips (it was new wifi 7 chip) that I wasn’t actually using anyway. It may have been fixed in days, weeks… who knows, I wasnt testing it.
tl;dr - sorry, I don’t have a good answer. The board always “worked” for my use case.
The strong irony is that when high core count and asymmetrical multi-CCD chips started rolling out, they were having CCD pinning issues in windows. But since Linux has a scheduler that has been NUMA awareness for ages… Linux was actually just fine with these things.
Linux was actually better for bleeding edge hardware for once.
Why is my Bluetooth stuttering
That can have several reasons. Workarounds typically are:
Find out what Bluetooth or wifi chipset you have. Then research and try various things.
try disabling bluetooth power saving
try libspa-bluetooth if pipewire
force A2DB profile in pavucontrol or blueman
make sure you have bluez and bluez-utils?
Nah. I’m just gonna hope distros once the paper I’m submitting is accepted and I don’t need this machine again. I think I’m going to go fedora so I can stay closer to bleeding edge on the kernel.
Just use Arch or a derivative like CachyOS, it’s not as scary as you might think
Yours too?
I have linux issues every time I have a “new” machine, and it makes sense. Linux is a volunteer/ opensource project. It isn’t getting chipsets before, and building drivers in advance of hardware releases (at least it mostly isn’t; I understand that some times it does).
Because of that, the newer your harder, the crappier it works. The longer your hardware has been around, in-general, my experience is that Linux becomes an “it just works experience”.
Also, fuck you mediatek 7925e.
I built a new 9950x3d + x870e system last year. trying to use the motherboard’s wifi would kernel panic things. couldnt turn bluetooth on and off. couldn’t control the RGB.
Now, WiFi works great. Bluetooth works great. OpenRGB supports the RGB. Things are great. Took time to get here, but we got here.
How long did it take to work?
I use ethernet for everything, so even now I don’t use WiFi. I only figured out it worked because my internet was out a few months later and needed to connect to a hotspot, and was pleasantly surprised that it was not crashing. I also don’t really mess with RGB or bluetooth, so I cant really comment on those either. The motherboard itself always worked, it was just the integrated chips (it was new wifi 7 chip) that I wasn’t actually using anyway. It may have been fixed in days, weeks… who knows, I wasnt testing it.
tl;dr - sorry, I don’t have a good answer. The board always “worked” for my use case.
🤤
The strong irony is that when high core count and asymmetrical multi-CCD chips started rolling out, they were having CCD pinning issues in windows. But since Linux has a scheduler that has been NUMA awareness for ages… Linux was actually just fine with these things.
Linux was actually better for bleeding edge hardware for once.
Try changing the audio codec in the hardware profile.
That’s the best thing bluetooth audio can do for you. Much better than anything it does to music.
Because it’s nervous and under a lot of pressure. Go easy on it.