No Actual Sound Output in sys-audio (Intel Cannon Lake PCH cAVS on ThinkPad X1 Extreme Gen1)

User Support General
1

Hi!

I’m setting up sys-audio qube, I’ve followed the instructions mentioned in many sys-audio related discussions.

However I am having internal audio driver issues. There’s no actual hardware sound output at all from internal speakers but if I attach bluetooth headphones they work.

speaker-test -c 2 -t wav in sys-audio is completely silent.

My laptop is Lenovo ThinkPad X1 Extreme Gen-1

Audio device is 00:1f.3 Audio device [0403]: Intel Corporation Cannon Lake PCH cAVS [8086:a348] (rev 10)

Audio card don’t get loaded with just --option no-strict-reset=True I had to add --option permissive=True to load the card

but there is no sound from the hardware

In alsamixer Speaker channel stuck at 00 there are no bars and arrows do nothing.

amixer controls | grep -i speaker gave no output

Tried overriding every unconnected pin to Internal speaker using hdajackretask with no luck

/proc/asound/card*/codec#* is empty there is no codec dump

dmesg is giving this output:

sudo dmesg | grep -E 'snd|sof|audio|hda'
[    0.177273] Performance Events: unsupported p6 CPU model 158 no PMU driver, software events only.
[    3.931432] snd_hda_intel 0000:00:07.0: spurious response 0x0:0x2, last cmd=0x000000
[    4.932600] snd_hda_intel 0000:00:07.0: azx_get_response timeout, switching to polling mode: last cmd=0x000f0000
[    5.934150] snd_hda_intel 0000:00:07.0: No response from codec, disabling MSI: last cmd=0x000f0000
[    6.937157] snd_hda_intel 0000:00:07.0: Codec #0 probe error; disabling it...
[    6.937189] snd_hda_intel 0000:00:07.0: no codecs initialized

I’ve also installed firmware-sof-signed in sys-audio template but no luck again.

Is there a solution at all?

2

Nobody? :disappointed:

3

I hope you have figured this out already, but if you haven’t, it sounds to me like a driver issue.

Some troubleshooting,

  • OpenVolume Controlinsys-audio, and first check under thePlaybacktab that theVUM(Volume Unit Meter) of the Qube is following the audio pattern coming from the Qube.
  • In theOutput Devicetab, make sure theVUM also follows the audio input from the Qube.
  • In theConfigutationtab, make sure your device is coming up, and if so try differentProfilesto see if any of them work.

The last point is the one I had trouble with. The driver (Profiles) is not always correctly recognized on startup.