That has been established a long time ago. It even fails if you insert a third-party USB C to jack adapter into the USB C module. The question merely is which part of it. And only the part inside the Kernel or does user space software also have any influence? And why does it seem to only happen on FW16? Does it use Audio alt mode, which barely any other device use, or is one of the USB hub chips on the motherboard the cause that’s poorly supported by software?
Ok. Thanks for that. So it is indeed the FW16 USB stack itself.
On a side note, I have a wireless mouse that connects over a USB-A dongle, and I’ve noticed some lag. It’s like the pointer movement has inconsistent latency, but this only happens when using the USB dongle. In Bluetooth mode, it works fine.
This issue occurs not only on Linux but on Windows as well. Though i mostly use it for casual games.
Also, my expansion slot audio card might have failed once or twice on Windows, but I could be wrong about that.
I’ll have to go back to 6.14.11 for now because the amdgpu issue of the whole UI just freezing up is very bad on 6.12 and for the next few days I need more stability than it offers.
Have you tried BIOS 03.07? That one cleared up the amdgpu freezes for me even with older kernels, although I’m still not completely sure what was going on with all the ins and outs of it.
1 Like
Same issue on Linux Elizabeth 6.17.6-zen1-1-zen #1 ZEN SMP PREEMPT_DYNAMIC Wed, 29 Oct 2025 22:23:44 +0000 x86_64 GNU/Linux.
Sometimes it works, sometimes it just doesn’t work and spams the dmesg.
A reboot fixes this usually but this is really annoying.
I hope this gets properly fixed soon.
[ +0.371430] input: Framework Audio Expansion Card Consumer Control as /devices/pci0000:00/0000:00:08.1/0000:c2:00.3/usb1/1-2/1-2.3/1-2.3:1.3/0003:32AC:0010.0015/input/input31
[ +0.050836] hid-generic 0003:32AC:0010.0015: input,hidraw19: USB HID v1.11 Device [Framework Audio Expansion Card] on usb-0000:c2:00.3-2.3/input3
[ +17.885851] usbhid 1-2.3:1.3: can't add hid device: -71
[ +0.000040] usbhid 1-2.3:1.3: probe with driver usbhid failed with error -71
[ +0.022089] usb 1-2.3: uac_clock_source_is_valid(): cannot get clock validity for id 9
[ +0.000006] usb 1-2.3: clock source 9 is not valid, cannot use
[ +0.000360] usb 1-2.3: 1:1: cannot get freq (v2/v3): err -71
[ +0.000377] usb 1-2.3: 1:1: cannot set freq 48000 (v2/v3): err -71
[ +0.000372] usb 1-2.3: uac_clock_source_is_valid(): cannot get clock validity for id 9
[ +0.000003] usb 1-2.3: clock source 9 is not valid, cannot use
[ +0.000374] usb 1-2.3: 1:1: cannot get freq (v2/v3): err -71
[ +0.000375] usb 1-2.3: 1:1: cannot set freq 48000 (v2/v3): err -71
[ +0.000374] usb 1-2.3: uac_clock_source_is_valid(): cannot get clock validity for id 9
[ +0.000002] usb 1-2.3: clock source 9 is not valid, cannot use
[ +0.000374] usb 1-2.3: 1:1: cannot get freq (v2/v3): err -71
[ +0.000372] usb 1-2.3: 1:1: cannot set freq 48000 (v2/v3): err -71
[ +0.000379] usb 1-2.3: uac_clock_source_is_valid(): cannot get clock validity for id 9
[ +0.000004] usb 1-2.3: clock source 9 is not valid, cannot use
[ +0.000377] usb 1-2.3: 1:1: cannot get freq (v2/v3): err -71
[ +0.000370] usb 1-2.3: 1:1: cannot set freq 48000 (v2/v3): err -71
[ +0.000380] usb 1-2.3: uac_clock_source_is_valid(): cannot get clock validity for id 9
[ +0.000005] usb 1-2.3: clock source 9 is not valid, cannot use
[ +0.000368] usb 1-2.3: 1:1: cannot get freq (v2/v3): err -71
[ +0.000372] usb 1-2.3: 1:1: cannot set freq 48000 (v2/v3): err -71
I’m on BIOS 04.02, I updated yesterday, but also yesterday it froze for me. Before that I was on 03.07 and it froze over and over again (on 6.12.48+deb13-amd64). I’m going to continue this testing until next monday, then I have 14 days of no audio expansion card issues on the upstream kernel. Then I’ll go to whatever Testing delivers at that point and report my findings to Debian.
Upgraded to Debian Forky, running Linux 6.17.8+deb14-amd64 and boom I have the issue today.
Unplugging/replugging the jack does not help.
Unplugging/replugging the expansion card does not help.
Rebooting fixed it (until it happen again).
Yes, the fix seems to be currently only present in their 6.12.x branch. I’ve already submitted my findings with the suggestion to upstream whatever they came up with.
I’m on trixie backports 6.17.8 right now. No issues but I only updated today. I actually had issues on 6.12.57 when I tested it, but that was before the 4.02 BIOS update and I’ve not revisited since. Hope you get a response from the upstream maintainers
Interesting. I’m currently trying to trigger the amdgpu driver freeze on a Fedora Live ISO, though sadly I have yet to find a reliably reproducible trigger. Once I’ve that figured out, I’ll look at the latest 6.12 kernel from Debian, I did my testing with 6.12.48.
I can confirm, Debian’s kernel 6.12.57 is also affected. Worse than ever, it happened in two consecutive boots as soon as anything tried to play audio.
Well folks, a similar thing happens on Windows. But on Windows, it reloads/reenumerates all USB devices at random.
I’ve used many laptops over the years: lenovo, hp, asus, macs. My Framework 16 is currently the second worst I’ve owned. It only beaten by the 2017 macbook pro. Given that the MBP had the butterfly keyboard, swelling batteries, and dead charging chips, that’s an incredibly low bar. Just today, the Framework’s USB froze up three times in one Google Meet call.
What is wrong with it? What should I do to make this piece of shit, built from faulty parts in a mismatched aluminium enclosure, stop hanging up in the middle of important calls?
And the icing on the cake: if you restart your Framework 16 with a debug-enabled Android Pixel phone connected, it somehow hangs on power-on. The fans whir, but the screen stays dark. A very cool thing to figure out while you’re restarting the machine because your audio cut out in the middle of an important call-all because some idiot screwed up the whole USB stack. This progressive piece of junk, made from recycled aluminum parts, all replacable, “educates” you by forcing you to troubleshoot it in the middle of a call. How nice of you Framework. Good job! Which part should I even replace? At this point, maybe the whole laptop?
I have a similar strange audio problem.
Using Windows and Zoom, after some minutes, there is no sound anymore. I can use bluetooth speakers or any other output when connected, but the built in speakers won’t work anymore.
I have now updated my support request with Framework were the last information they provided was “well, things happen. Fedora 42 isn’t affected, deal with it yourself”. F42 is only supported until May '26, so in less than half a year no officially supported Linux distro that’s still under active support. I recommend at least to @Marc_Fauser and @Baka_Gaijin to do the same, as you guys indicating that even Windows is affected now proves that the cause can only be either in Hardware, BIOS or maybe firmware (if somehow the same issue ended up in the formware for both Windows and Linux), so it is up to FW to fix this highly annoying issue. Of course everybody else in here should better do the same, so FW finally sees how big this issue is and are pressured to act.
Howdy everyone. Sorry this was on the back burner for so long. There’s a lot of justified frustration here and I don’t want to minimize it at all. We’ve had some particular trouble with BIOS 4.02 on the Framework Laptop 16 and it’s made these issues that you all have been reporting more obvious and exposed the full scope of the issue to us. This is something we’re actively looking into and hope to address with the next update, pending some internal testing. If you open support tickets, we can provide you with a template and then add the information you share with us to our Issue Tracker on Github.
1 Like
@Jesse_Darnley will you please post an update here when the bug information has been posted to the Firmware Issue Tracker? It doesn’t appear the information is posted yet.
Hi @sounds, this section of the GH tracker has been pretty active. If you have a bug you can share if you are not seeing it yet, please report it here. Thanks! 
If an experienced issue has been reported, then we will have what we need from there.
I know this feels like we’re not hearing you. But, if there is a firmware issue, we need to have it filed in the GH tracker please. And for issues filed already, please know our firmware team is working hard to get this sorted out asap.
That’s the issue. How are we supposed to be able to tell where the issue is even located? Only since the first two people using Windows chimed in on this thread in December that they have the same or similar issues, we can tell that it must at least be a firmware/BIOS issue, but none of us could rule out it’s not even a hardware issue.
The same with the notorious screen flicker and freeze bugs that have been around for at least a year. The cause could be located literally anywhere.
Besides these points, Jesse and you mentioning that repo in this thread are the only times I ever came across this. So if you want people to report bugs there, it needs to become a lot more known.
1 Like
My thought too.
Or other typees of (maybe) bugs, is there a dedicated place to report them? There might want to be a dedicated category(s) page that is very obvious?
Hi @Richard and @ValiantCM ,
Thanks for the feedback; that is a completely valid point.
At this stage, our main priority is ensuring this gets directly in front of the engineering team in the specific area where they track firmware and BIOS issues. Since the team does not use the forums for active bug tracking, they have expressly asked that we direct these reports to the official Firmware Tracker.
Once filed, the engineering team will be able to triage the report and address the specific symptoms and technical details directly.
I know this adds an extra step and isn’t the ideal workflow, but I genuinely appreciate your willingness to help us get this sorted out.
Thank you
I’ve now created an issue for this just for tracking purposes.
1 Like