Bug 2483179 - Microphone not working on Thinkpad X1 Carbon Gen14 [NEEDINFO]
Summary: Microphone not working on Thinkpad X1 Carbon Gen14
Keywords:
Status: NEW
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 44
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Justin M. Forbes
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: 2184978
TreeView+ depends on / blocked
 
Reported: 2026-05-29 09:10 UTC by Kamil Páral
Modified: 2026-06-06 04:54 UTC (History)
16 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Type: Bug
Embargoed:
kparal: needinfo? (mpearson)


Attachments (Terms of Use)
kernel log (141.25 KB, text/plain)
2026-05-29 09:12 UTC, Kamil Páral
no flags Details
full system journal (331.89 KB, text/plain)
2026-05-29 09:12 UTC, Kamil Páral
no flags Details

Description Kamil Páral 2026-05-29 09:10:59 UTC
1. Please describe the problem:
Microphone doesn't work at all on Thinkpad X1 Carbon Gen14. There is no detected sound, even though the microphone device itself is visible, e.g. in gnome-control-center. I see the following error messages repeatedly appear in journal while trying to use the microphone:

May 29 10:42:21 chronos kernel: snd_soc_sdca_class_function snd_soc_sdca.SmartMic.0: PDE 11: power transition failed: 3
May 29 10:42:21 chronos kernel: sof_sdw sof_sdw: ASoC: POST_PMU: cs42l45 PDE 11 event failed: -110
May 29 10:42:36 chronos kernel: soundwire_intel soundwire_intel.link.3: prepare clock stop failed -110
May 29 10:42:36 chronos kernel: soundwire_intel soundwire_intel.link.3: intel_stop_bus: cannot stop clock: -110


2. What is the Version-Release number of the kernel:
kernel-7.0.10-200.fc44.x86_64

Firmware versions:
UEFI version:  N4OET47W (1.10 ) 03/30/2026
System version: N4OSG16W  (1.16)
EC version: N4OHT37W (1.07)
ME version: 21.0.2.1482

Machine type model: 21V8ZDJLUS

3. Did it work previously in Fedora? If so, what kernel version did the issue
   *first* appear?  Old kernels are available for download at
   https://koji.fedoraproject.org/koji/packageinfo?packageID=8 :
No

4. Can you reproduce this issue? If so, please provide the steps to reproduce
   the issue below:
Run gnome-control-center or any app trying to record sound, you get no input signal

5. Does this problem occur with the latest Rawhide kernel? To install the
   Rawhide kernel, run ``sudo dnf install fedora-repos-rawhide`` followed by
   ``sudo dnf update --enablerepo=rawhide kernel``:
Yes. Tested with kernel-7.1.0-0.rc5.260527geb3f4b7426cf.37.fc45.x86_64 .

6. Are you running any modules that not shipped with directly Fedora's kernel?:
No

7. Please attach the kernel logs. You can get the complete kernel log
   for a boot with ``journalctl --no-hostname -k > dmesg.txt``. If the
   issue occurred on a previous boot, use the journalctl ``-b`` flag.

Comment 1 Kamil Páral 2026-05-29 09:12:00 UTC
Created attachment 2143327 [details]
kernel log

Comment 2 Kamil Páral 2026-05-29 09:12:12 UTC
Created attachment 2143328 [details]
full system journal

Comment 3 Kamil Páral 2026-05-29 09:13:25 UTC
CC @mpearson

Comment 4 Kamil Páral 2026-06-01 10:34:42 UTC
As a workaround, I tried to put headphones+microphone into the Jack socket on the laptop, but that seems to be completely ignored. I see no new input/output devices, there's no new message in journactl on connection, just no-op. I tried multiple headphones (TRS and TRRS), no change. The kernel problem with the sound card seem to affect the Jack socket as well.

And interestingly, I can't even make headphones+mic work through Jack socket in a docking station (connected through usb-c), also no-op. 

Another option would be native usb-c headphones, but I don't have any, so can't test that.

Comment 5 Mark Pearson 2026-06-06 04:54:55 UTC
Hi Kamal,

Sorry took so long to get to this (still travelling - back home on Monday)
I believe we need to update your FW - there are some settings missing in the version you have.

I'll figure out what to get you (I was doing a scan of emails and there have been some updates whilst I was away, so want to make sure I get you the right version). Once updated I think it will fix it.

Mark


Note You need to log in before you can comment on or make changes to this bug.