using sys-audio, mod.qubes-audio: no /qubes-audio-domain-xid entry in QubesDB

[bi0shacker001]

Qubes OS release

Qubes OS 4.2

Brief summary

When launching sys-audio, audio devices are detected properly, vu meters are peaking properly in pavucontrol, but no sound output occurs. Using ASUS ROG strix laptop on linux kernel 6.11. Audio support functioned properly before systemwide updates.

Steps to reproduce

1.Start sys-audio, then vm with content 2.play content 3.

Expected behavior

Expect audio output from built-in speakers

Actual behavior

No sound output at all (input still works) journalctl shows:

Jan 20 14:06:05 sys-audio pipewire[1093]: mod.qubes-audio: no /qubes-audio-domain-xid entry in QubesDB
Jan 20 14:06:05 sys-audio pipewire[1093]: mod.qubes-audio: unknown peer domain, cannot create stream
Jan 20 14:06:05 sys-audio pipewire[1093]: mod.qubes-audio: unknown peer domain, cannot create stream

[bi0shacker001]

I tried nuking sys-audio, resetting audiovm to dom0, and testing. Speaker output works in dom0. After recreating sys-audio (using the same template as before), setting audiovm again, and testng, still no sound from the built-in speakers. Tested with bluetooth audio, sound works over bluetooth, so the issue is purely with the built-in speakers. Alright, this is probably a device-specific issue, which is weird. This model of laptop has controller CS35L41, which didn't have kernel patches until 6.7 (which I waited for, and when I updated, that fixed the audio the first time). Those patches should still be in the kernel, so I'm not sure what additional troubleshooting I should try

[ptitdoc]

Same problem there with a ThinkPad X1 (21KC).

I'm using Qubes 4.3 and my sys-audio is based on debian-13-xfce and pipewire installed instead of pulseaudio.

My sys-audio has the audio device attached:

dom0:~$ qvm-run -p sys-audio lspci -v
00:06.0 Audio device: Intel Corporation Meteor Lake-P HD Audio Controller (rev 20) (prog-if 80)
	Subsystem: Lenovo Device 231e
	Physical Slot: 6
	Flags: bus master, fast devsel, latency 64, IRQ 73
	Memory at f2200000 (64-bit, non-prefetchable) [size=16K]
	Memory at f2000000 (64-bit, non-prefetchable) [size=2M]
	Capabilities: <access denied>
	Kernel driver in use: snd_hda_intel
	Kernel modules: snd_hda_intel, snd_sof_pci_intel_mtl

and also the bluetooth usb device:

dom0:~$ qvm-run -p sys-audio lsusb 
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU Tablet
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 004: ID 8087:0033 Intel Corp. AX211 Bluetooth
Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub

The setup seems to be correct as I can see all my appvms in pavucontrol and I can listen to music from my bluetooth headset.

However it's not possible to get any information on how to play sound on my speakers or wired headset. I have the same journalctl error than @bi0shacker001 .

[marmarek]

Is the correct output device selected in pavucontrol in sys-audio? What if you try to play something in sys-audio itself? (there are some example sounds in /usr/share/sounds, paplay too should work)

BTW the no /qubes-audio-domain-xid entry in QubesDB message is just about (not) sending audio to dom0 - which is okay here, since you have audio devices connected to sys-audio directly.

[ptitdoc]

I tried both, sound playing from sys-audio with aplay, and sound playing from my personal qube with a music player.

Paplay from sys-audio is not working when I only have the pc speakers, so I'm checking if it is an hardware/alsa issue, probably not related to sys-audio setup.

[ptitdoc]

Some links of things I already through about/tested for reference: https://thesofproject.github.io/latest/getting_started/intel_debug/introduction.html https://github.com/alsa-project/alsa-ucm-conf/issues/614 https://wiki.archlinux.org/title/Lenovo_Yoga_7i#Speaker_audio

[ptitdoc]

Ok, I got some success with SOF drivers.

The idea is to disable intel hda drivers altogether. I have no clue if it is a bad BIOS settings or if it's just the new way of getting sound on intel.

On my template I use for sys-audio:

$ cat /etc/modprobe.d/50-snd_intel.conf 
options snd-intel-dspcfg dsp_driver=3

Note that there are no snd_hda_intel options anymore.

Also you need to install SOF firmwares in your template:

apt install firmware-sof-signed

Now I can see "Meteor Lake-P HD Audio Controller Speaker" in pavucontrol.

Sadly, it does not solve this issue: https://github.com/QubesOS/qubes-issues/issues/10063

So sound is now there, but still crappy because of inter-vm communication (sound is clear if directly played into audio-vm).