Issue Summary
Hi everyone, I’m experiencing an issue with my new Framework Laptop 13 (DIY Edition) running Bluefin GTS, where my Digital Microphone (Mic1) is detected but remains in a “SUSPENDED” state and won’t activate consistently.
What I’ve Tried So Far
- The microphone is recognized by PipeWire but stays unavailable.
pactl list sources
shows Mic1 but labels its availability as “unknown”.- I was briefly able to record using Mic1, but the success wasn’t persistent—it reverted to SUSPENDED afterward.
- Switching audio profiles (
pactl set-card-profile 43 "HiFi (Mic1, Mic2, Speaker)"
) didn’t resolve the issue. - PipeWire logs suggest modules aren’t loading properly, showing errors like:
pw.context: no modules loaded from context.modules
pw.conf: can't find factory adapter
default: failed to create context: No such file or directory
- Reinstalling PipeWire (
dnf remove/install pipewire wireplumber
) didn’t change the behavior.
Additional Issue: Overheating Concerns
Yesterday, I experienced major overheating (100°C) on my laptop during testing of Google Meet, which I downloaded from Software Center. While I haven’t reproduced it today, it’s possible that thermal issues are affecting the microphone or other components. Below is my current sensor output after 3 hours of uptime:
cros_ec-isa-0000
Adapter: ISA adapter
fan1: 0 RPM
local_f75303@4d: +44.9°C
cpu_f75303@4d: +48.9°C
ddr_f75303@4d: +38.9°C
cpu@4c: +52.9°C
(Sensors output continues…)
Of course, I installed Bluefin as soon as I could ! I used the recommended
Anaconda
installer. I had some pre-booting warning messages but after I installed Secure Boot, I no longer have any pre-booting warning messages.
System Details Report
Report details
- Date generated: 2025-05-12 09:09:05
Hardware Information:
- Hardware Model: Framework Laptop 13 AMD Ryzen AI 300 Series
- Memory: 64.0 GiB
- Processor: AMD Ryzen™ AI 9 HX 370 w/ Radeon™ 890M × 24
- Graphics: AMD Radeon™ Graphics
- Disk Capacity: 2.0 TB
Software Information:
- Firmware Version: 03.03
- OS Name: Bluefin (Version: gts-41.20250511 / FROM Fedora Silverblue 41)
- OS Build: ea35c6a
- OS Type: 64-bit
- GNOME Version: 47
- Windowing System: Wayland
- Kernel Version: Linux 6.13.8-200.fc41.x86_64
- Audio Stack: PipeWire with WirePlumber
- Current Default Microphone: Family 17h/19h/1ah HD Audio Controller Digital Microphone
- Active Card Profile: HiFi (Headset, Mic1, Speaker)
- Output from
pactl list cards
:
Card #42
Active Profile: off
Card #43
Active Profile: HiFi (Headset, Mic1, Speaker)
Questions for the Community:
- Could this be a missing firmware issue?
- Is there a Bluefin-specific PipeWire configuration that might be affecting this?
- Has anyone encountered similar microphone issues with Framework laptops?
- Could my overheating issue be linked to the microphone issue?
- Any deeper debugging suggestions for PipeWire or ALSA that I should try next?
Update 1:
Here is a reproducible test to get Mic1 working temporarily:
- Verify PipeWire sees the microphone:
pactl list sources | grep -A 10 'Source #52'
Because Source 52 is listed, but remains SUSPENDED, proceed to the next step.
- Manually start a recording session (this forces activation):
arecord -D hw:0,0 -f S32_LE -r 48000 -c 2 -d 5 test.wav
Then, play back the recorded audio:
aplay test.wav
- Check if Mic1 stays active after recording:
pactl list sources | grep -A 10 'Source #52'
Because If it reverts to SUSPENDED afterward, this confirms PipeWire is not keeping it active.
It proves that the microphone itself works, meaning the issue is likely software-related. Unless maybe it is related to the DIY Bezel installation?
Update 2:
Fedora 42 Live: Audio works perfectly (one sound bar, no crashes).
Bluefin:
- Two sound bars appear (one mute, one active).
- Audio mutes randomly until reboot.
- Logs show
"error": null
spam (14x).
Question: Known fix for the dual sound bar bug?
Update 3:
Another FW13 user has the internal microphone issue:
https://community.frame.work/t/solved-headset-mic-on-amd-fw13-running-fedora-39/38847/24
Another FW13 user has the high temperature issue:
https://community.frame.work/t/cpu-boiling-during-heavy-use-compilation/68967/12