Audio Expansion Card Disconnects and Reconnect Loops
Summary
The Framework Audio Expansion Card (USB audio adapter) disconnects during active use and enters a reconnect loop with UAC2 (USB Audio Class 2) clock negotiation failures. The card eventually vanishes from USB entirely and cannot be recovered without a full system reboot. The issue affects both the Framework Laptop 16 and Framework Desktop, and has been tracked for over 18 months with 120+ community posts and no fix12.
Symptoms
- Audio Expansion Card disconnects during active use — audio cuts out mid-playback12
- Card enters a reconnect loop: disconnects, reconnects, disconnects again1
dmesgshows UAC2 clock negotiation failures:uac_clock_source_is_valid: clock source validation failedcannot get freq at ep 0x1- After several reconnect attempts, the card vanishes from USB entirely1
- Software USB hub resets, replugging the card, and
modprobecycling all fail to recover it1 - Only a full system reboot restores the card1
- Issue can take hours or days to manifest; appears random1
Affected Models
- Framework Laptop 16 (AMD Ryzen 7040 Series) — GitHub issue #1612
- Framework Laptop 16 (AMD Ryzen AI 300 Series)1
- Framework Desktop (AMD Ryzen AI Max) — GitHub issue #2031
Confirmed not laptop-specific — the same card exhibits the issue across different Framework products, pointing to a card firmware or USB host controller issue1.
Root Cause
The root cause has not been definitively identified. The UAC2 clock source validation failures suggest the card's internal firmware fails to respond to USB audio clock queries within the required timeout, causing the USB host to drop the device1.
The fact that software USB resets and replugging fail to recover the card (but a reboot does) suggests the USB host controller itself enters a bad state that only a full controller reset (which happens during reboot) can clear1.
Framework has not publicly acknowledged this issue or provided a firmware update for the Audio Expansion Card1.
Diagnosis
-
Check kernel logs for UAC2 errors:
sudo dmesg | grep -E '(uac_clock|clock source|cannot get freq|usb.*disconnect)' -
Monitor USB device presence:
watch -n5 "lsusb | grep -i audio"If the device disappears and reappears, the reconnect loop is active.
-
Check USB subsystem for errors:
sudo dmesg | grep -E '(xhci|usb).*error' -
Try a manual USB device reset:
# Find the USB bus/device numberlsusb | grep -i audio# Reset (replace 001/002 with bus/device)echo 0 | sudo tee /sys/bus/usb/devices/1-1/authorizedsleep 2echo 1 | sudo tee /sys/bus/usb/devices/1-1/authorizedIf this does not recover the card, only a reboot will.
Workarounds & Fixes
| Solution | Effectiveness | Notes |
|---|---|---|
| Full system reboot1 | Always works | Only reliable recovery method. Not practical for ongoing use |
| Move card to a different expansion slot | May reduce frequency | Some users report the issue is less frequent on certain slots, possibly due to different USB controller routing |
| Use 3.5mm audio jack instead | Reliable workaround | The built-in 3.5mm TRRS jack on all Framework laptops is not affected |
| Use a Bluetooth audio device | Reliable workaround | Bypasses the USB audio path entirely |
| Use a different USB audio adapter | Reliable workaround | Third-party USB-C or USB-A audio adapters may not exhibit the same firmware bug |
Resolution
No fix exists. The issue has been tracked for over 18 months with 120+ community posts1. Framework has not released a firmware update for the Audio Expansion Card or publicly acknowledged the issue.
GitHub issues #161 (FW16) and #203 (Desktop) are both still open12.
Related
- GitHub Issue #203 — Audio Expansion Card disconnects (Desktop) — GitHub (Apr 14, 2026)
- GitHub Issue #161 — Audio Expansion Card disconnects (FW16) — GitHub
- Audio Expansion Card Community tracking thread — Framework Community