Ubuntu 21.10 / Tiger Lake sound?

Any tips on getting this thing to output sound / use the mic? It doesn’t seem to work, having only “Dummy Output” as an option.

The lspci line:

00:1f.3 Audio device: Intel Corporation Tiger Lake-LP Smart Sound Technology Audio Controller (rev 20)

sudo hwinfo --sound:

18: PCI 1f.3: 0403 Audio device                                 
  [Created at pci.386]
  Unique ID: nS1_.aKE9YmzGtVF
  SysFS ID: /devices/pci0000:00/0000:00:1f.3
  SysFS BusID: 0000:00:1f.3
  Hardware Class: sound
  Model: "Intel Tiger Lake-LP Smart Sound Technology Audio Controller"
  Vendor: pci 0x8086 "Intel Corporation"
  Device: pci 0xa0c8 "Tiger Lake-LP Smart Sound Technology Audio Controller"
  SubVendor: pci 0xf111 
  SubDevice: pci 0x0001 
  Revision: 0x20
  Driver: "snd_hda_intel"
  Driver Modules: "snd_hda_intel"
  Memory Range: 0x605d1c8000-0x605d1cbfff (rw,non-prefetchable)
  Memory Range: 0x605d000000-0x605d0fffff (rw,non-prefetchable)
  IRQ: 16 (116731 events)
  Module Alias: "pci:v00008086d0000A0C8sv0000F111sd00000001bc04sc03i80"
  Driver Info #0:
    Driver Status: snd_hda_intel is active
    Driver Activation Cmd: "modprobe snd_hda_intel"
  Driver Info #1:
    Driver Status: snd_sof_pci_intel_tgl is active
    Driver Activation Cmd: "modprobe snd_sof_pci_intel_tgl"
  Config Status: cfg=new, avail=yes, need=no, active=unknown

sudo dmesg -k | grep snd_hda_intel

[    2.743599] snd_hda_intel 0000:00:1f.3: DSP detected with PCI class/subclass/prog-if info 0x040380
[    2.743666] snd_hda_intel 0000:00:1f.3: enabling device (0000 -> 0002)
[    3.824749] snd_hda_intel 0000:00:1f.3: bound 0000:00:02.0 (ops i915_audio_component_bind_ops [i915])
[    4.875220] snd_hda_intel 0000:00:1f.3: azx_get_response timeout, switching to polling mode: last cmd=0x000f0000
[    5.878989] snd_hda_intel 0000:00:1f.3: No response from codec, disabling MSI: last cmd=0x000f0000
[    6.895004] snd_hda_intel 0000:00:1f.3: Codec #0 probe error; disabling it...

May be a stupid question, but have you toggled the mic kill switch up at the top next to the camera? If it’s red, that means it’s disconnected.

Yes.

Incidentally, does the mic switch also cut off the audio output? Because that doesn’t work.

Hmm, okay, then it’s not the kill switch (that switch only disables the mic, not sound output).

I’d use this guide to make sure the audio cable is plugged in all the way (go up to step 5 and then close it back up, since you’re not replacing the audio board).

No luck there. It was very well-seated; I cycled both ends of the ribbon cable, but I still only see “Dummy output”

Just FYI, I have sound but no microphone on mine as well. I suspect driver issue because microphone used to work. I’m on openSUSE with 5.15.1

@Bryan_Elliott U21.10 works ok for me. The dmesg output you shared is a little unusual since it shows no response from codec.

$ uname -a 
  Linux***5.13.0-22-generic #22-Ubuntu SMP Fri Nov 5 13:21:36 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

$ sudo dmesg -k | grep snd_hda_intel
[  258.312185] snd_hda_intel 0000:00:1f.3: DSP detected with PCI class/subclass/prog-if info 0x040380
[  258.312239] snd_hda_intel 0000:00:1f.3: enabling device (0000 -> 0002)
[  258.315667] snd_hda_intel 0000:00:1f.3: bound 0000:00:02.0 (ops i915_audio_component_bind_ops [i915])

What bios version do you have? Do you have a Tempo mainboard or Realtek Mainboard?

   sudo dmidecode --type bios

For the mainboard type: you can run

sudo dmidecode --type chassis 

And share the first 10 digits of the serial number.

1 Like

uname -a

Linux sproket 5.13.0-22-generic #22-Ubuntu SMP Fri Nov 5 13:21:36 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

sudo dmidecode --type bios

# dmidecode 3.3
Getting SMBIOS data from sysfs.
SMBIOS 3.3.0 present.

Handle 0x0000, DMI type 0, 26 bytes
BIOS Information
	Vendor: INSYDE Corp.
	Version: 03.06
	Release Date: 10/18/2021
	Address: 0xE0000
	Runtime Size: 128 kB
	ROM Size: 12 MB
	Characteristics:
		PCI is supported
		BIOS is upgradeable
		BIOS shadowing is allowed
		Boot from CD is supported
		Selectable boot is supported
		8042 keyboard services are supported (int 9h)
		CGA/mono video services are supported (int 10h)
		ACPI is supported
		USB legacy is supported
		BIOS boot specification is supported
		Targeted content distribution is supported
		UEFI is supported
	BIOS Revision: 3.6

Handle 0x0011, DMI type 13, 22 bytes
BIOS Language Information
	Language Description Format: Long
	Installable Languages: 4
		en|US|iso8859-1,0
		fr|FR|iso8859-1,0
		zh|TW|unicode,0
		ja|JP|unicode,0
	Currently Installed Language: en|US|iso8859-1,0

sudo dmidecode --type chassis | sed -e 's/\(Serial Number\|Asset Tag\): \([[:alnum:]]\{10\}\)[[:alnum:]]*$/\1: \2********/'

# dmidecode 3.3
Getting SMBIOS data from sysfs.
SMBIOS 3.3.0 present.

Handle 0x0003, DMI type 3, 22 bytes
Chassis Information
	Manufacturer: Framework
	Type: Notebook
	Lock: Not Present
	Version: AA
	Serial Number: FRANBMCPAA********
	Asset Tag: FRANBMCPAA*********
	Boot-up State: Safe
	Power Supply State: Safe
	Thermal State: Safe
	Security Status: None
	OEM Information: 0x00000000
	Height: Unspecified
	Number Of Power Cords: 1
	Contained Elements: 0
	SKU Number: FRANBMCP0A

Wanna hear something fun? Last night just before bed, I had sound working (through no action but a couple reboots), and I figured I’d report back after work. I put it to sleep to switch to my company computer and when I woke it back up: no sound again.

Hey everyone,

I’m new here and pretty new to Ubuntu as well but wanted to share how I fixed my dummy output issue. Initially I had the same issue where my Output device was designated as Dummy Output and nothing was visible in the Input Device, even after toggling the physical switch. The issue turned out the me with the official instructions for how to make the 3.5mm jack support, here. After Removing:
options snd-hda-intel model=dell-headset-multi
from:
/etc/modprobe.d/alsa-base.conf
Everything started working perfectly.
Hope this helps,
Cheers!

My laptop seems to be affected by the same issue and since upgrading to Ubuntu 22.04 didn’t fix it (my secret hope), I’d hope for some support in the forums.

So:

  • “aplay” on a wav file runs but gives no audio output
  • My Pulseaudio setup only shows “Dummy Ausgabe” (German for “Dummy Output”) as an output device. Sound typically can’t be heard. Listing via command line ‘pacmd list-sinks’:
1 sink(s) available.
  * index: 0
	name: <auto_null>
	driver: <module-null-sink.c>
	flags: DECIBEL_VOLUME LATENCY DYNAMIC_LATENCY
	state: RUNNING
	suspend cause: (none)
	priority: 1000
	volume: front-left: 65536 / 100% / 0.00 dB,   front-right: 65536 / 100% / 0.00 dB
	        balance 0.00
	base volume: 65536 / 100% / 0.00 dB
	volume steps: 65537
	muted: no
	current latency: 1648.55 ms
	max request: 344 KiB
	max rewind: 344 KiB
	monitor source: 0
	sample spec: s16le 2ch 44100Hz
	channel map: front-left,front-right
	             Stereo
	used by: 1
	linked by: 1
	configured latency: 2000.00 ms; range is 0.50 .. 2000.00 ms
	module: 13
	properties:
		device.description = "Dummy-Ausgabe"
		device.class = "abstract"
		device.icon_name = "audio-card"
  • My Framework is running Ubuntu 22.04 but the issue was already there on Ubuntu 21.10.
  • I’m on BIOS v3.07 which should be current:
# dmidecode 3.3
Getting SMBIOS data from sysfs.
SMBIOS 3.3.0 present.

Handle 0x0000, DMI type 0, 26 bytes
BIOS Information
	Vendor: INSYDE Corp.
	Version: 03.07
	Release Date: 12/14/2021
	Address: 0xE0000
	Runtime Size: 128 kB
	ROM Size: 12 MB
	Characteristics:
		PCI is supported
		BIOS is upgradeable
		BIOS shadowing is allowed
		Boot from CD is supported
		Selectable boot is supported
		8042 keyboard services are supported (int 9h)
		CGA/mono video services are supported (int 10h)
		ACPI is supported
		USB legacy is supported
		BIOS boot specification is supported
		Targeted content distribution is supported
		UEFI is supported
	BIOS Revision: 3.7

Handle 0x0011, DMI type 13, 22 bytes
BIOS Language Information
	Language Description Format: Long
	Installable Languages: 4
		en|US|iso8859-1,0
		fr|FR|iso8859-1,0
		zh|TW|unicode,0
		ja|JP|unicode,0
	Currently Installed Language: en|US|iso8859-1,0
  • my chassis information (I’m impressed by the ‘sed’ expression):
# dmidecode 3.3
Getting SMBIOS data from sysfs.
SMBIOS 3.3.0 present.

Handle 0x0003, DMI type 3, 22 bytes
Chassis Information
	Manufacturer: Framework
	Type: Notebook
	Lock: Not Present
	Version: AA
	Serial Number: FRANBMCPAA********
	Asset Tag: FRANBMCPAA********
	Boot-up State: Safe
	Power Supply State: Safe
	Thermal State: Safe
	Security Status: None
	OEM Information: 0x00000000
	Height: Unspecified
	Number Of Power Cords: 1
	Contained Elements: 0
	SKU Number: FRANBMCP0A
  • what seems weird to me is that the snd_hda_intel module reports a codec issue:
[   14.326522] snd_hda_intel 0000:00:1f.3: DSP detected with PCI class/subclass/prog-if info 0x040380
[   14.326582] snd_hda_intel 0000:00:1f.3: enabling device (0000 -> 0002)
[   14.326817] snd_hda_intel 0000:00:1f.3: bound 0000:00:02.0 (ops i915_audio_component_bind_ops [i915])
[   15.343764] snd_hda_intel 0000:00:1f.3: azx_get_response timeout, switching to polling mode: last cmd=0x000f0000
[   16.351890] snd_hda_intel 0000:00:1f.3: No response from codec, disabling MSI: last cmd=0x000f0000
[   17.355750] snd_hda_intel 0000:00:1f.3: Codec #0 probe error; disabling it...
  • I’ve tried with and without the “dell-headset-multi” option in ‘/etc/modprobe.d/alsa-base.conf’ but I see no effect there.
  • I cannot really tell what makes the sound work sometimes… and sometimes not work. Could these really be loose cables on the sound board!?

To be clear, I still don’t have a solution for this. Whether sound works is kinda random on boot and, if I’m lucky enough to have it working, I try very hard not to shut the laptop down or suspend it.

It kinda sucks. The model setting for snd_hda_intel doesn’t do anything.

I have the exact same behavior here except mine is not intermittent - it has literally never worked (My framework is gen-less, Tempo chip, I5, bought about 3 weeks ago).

But it works on Windows 10 using the standard MS driver, and it works on Windows 10 inside a QEMU VM with the Tiger Lake sound device passed through to the VM. It doesn’t matter what OS I use - everything down to 18.04 Ubuntu, Void, Manjaro, Debian, Arch all display the exact same behaviour outlined in the logs.

I suspect this is an initialization bug in the BIOS or linux driver for some reason, and has been worked around in Windows. Why it only affects some Frameworks and not others is an absolute mystery to me and so far, Framework support have been rather silent on the matter. I don’t know much about SOF / the Intel HDA driver but I’ve been poking around in the kernel source / Tempo data sheet to see if I can work out what’s going on, but since I can’t see what Windows is doing differently it’s kinda flying blind.

Using

snd-hda-intel model=dell-headset-multi

is not needed on mainboards with the Tempo codec. I think this may pass some invalid parameters to the codec.

However This does not sound like the root cause of issues most people are experiencing in this thread.

The Mic switch only cuts off the mic, not audio output.

If someone could enable hda tracing and unload and reload the snd_hda_intel module, it might shed some light onto what is happening.

echo 1 > /sys/kernel/debug/tracing/events/hda/enable

reload the snd_hda_intel module

cat /sys/kernel/debug/tracing/trace

And lets see what shows up

modprobe -r -f -a snd_hda_intel fails with

FATAL: Module snd_intel_dspcfg is in use

So does modprobe -r -f -a snd_intel_dspcfg