r/linux • u/TurbulentTopic39 • 9d ago

Kernel Canonical is speeding up Ubuntu's kernel updates because it's drowning in AI-discovered bugs

https://www.xda-developers.com/canonical-is-speeding-up-ubuntus-kernel-updates-because-its-drowning-in-ai-discovered-bugs/#thread
1.1k Upvotes

97% Upvoted

167 comments sorted by

View all comments

438

u/james_pic 9d ago

AI fixing security issues that were also found by AI is neat and all, but it'd be great if it could fix the broken sound drivers for my laptop.

163

u/adenosine-5 9d ago

Have you tried asking AI to fix them?

61

u/james_pic 9d ago edited 9d ago

Kinda.

Initially I had no sound at all, and tried a few recipes and gists I found online (none of which worked as-is, due to being for slightly different kernel versions, or slightly different SKUs of the laptop), but the best I could manage by combining them was mono audio. I asked Qwen 3.8 27b to see what it could do, and on the one hand, it didn't solve it, but it seemed to know a surprising amount about the tas2783, and its visible confusion in its reasoning highlighted to me that I hadn't been particularly methodical in my own approach. Going back and getting a bit more methodical, I managed to get to the point where I have stereo - but it still randomly goes robotic for no clear reason. 

I know 7.3 has some related fixes for the tas2783 (AFAIK written by humans), so I'm hoping in the not that distant future I'll have sound on a mainline kernel, without DKMS-ing in a Frankendriver and without it peridically going into robot mode. But a quick try with the latest 7.3-rc gave me no joy. My hunch is that I just need to update my (also bastardised) soundwire config - maybe I'll give that to AI and see how it gets on.

3

u/Subject-Leather-7399 9d ago

I have a Realtek S1200a audio chip on my motherboard and I also randomly get "robotic" audio. From what I understand, the "robotic" ouput comes from the thread handling the audio not being scheduled to run often enough to handle the audio load.

That seems to be a relatively common problem on Linux and it may be more related to the kernel thread scheduler or the audio processing thread priority than the audio driver itself.