No Hardware Output device in dom0 audio mixer in output devices.
Just did installation using Kernel latest option.
What to do now?
1 Like
Found these errors in the journalctl
Dec 09 22:47:33 dom0 kernel: sof-audio-pci-intel-mtl 0000:00:1f.3: SOF firmware and/or topology file not found.
Dec 09 22:47:33 dom0 kernel: sof-audio-pci-intel-mtl 0000:00:1f.3: Supported default profiles
Dec 09 22:47:33 dom0 kernel: sof-audio-pci-intel-mtl 0000:00:1f.3: - ipc type 1 (Requested):
Dec 09 22:47:33 dom0 kernel: sof-audio-pci-intel-mtl 0000:00:1f.3: Firmware file: intel/sof-ipc4/arl/sof-arl.ri
Dec 09 22:47:33 dom0 kernel: sof-audio-pci-intel-mtl 0000:00:1f.3: Topology file: intel/sof-ace-tplg/sof-hda-generic-2ch.tplg
Dec 09 22:47:33 dom0 kernel: sof-audio-pci-intel-mtl 0000:00:1f.3: Check if you have 'sof-firmware' package installed.
Dec 09 22:47:33 dom0 kernel: sof-audio-pci-intel-mtl 0000:00:1f.3: Optionally it can be manually downloaded from:
Dec 09 22:47:33 dom0 kernel: sof-audio-pci-intel-mtl 0000:00:1f.3: https://github.com/thesofproject/sof-bin/
Dec 09 22:47:33 dom0 kernel: sof-audio-pci-intel-mtl 0000:00:1f.3: error: sof_probe_work failed err: -2
1 Like
uname -r
If kernel version is below 6.10 then no love.
If higher, try
sudo qubes-dom0-update alsa-sof-firmware
2 Likes
Did not workâŚ
@dom0 ~]$ uname -r
6.12.11-1.qubes.fc37.x86_64
@dom0 ~]$ sudo qubes-dom0-update alsa-sof-firmware
Using sys-firewall as UpdateVM for Dom0
Downloading packages. This may take a whileâŚ
Updating and loading repositories:
Fedora 37 - x86_64 - Updates 100% | 11.8 MiB.0 B
Qubes Host Repository (updates) 100% | 604.2 KiB
Fedora 37 - x86_64 100% | 34.0 MiB
_[?25hRepositories loaded.
Package âalsa-sof-firmware-2023.09.1-1.fc37.noarchâ is already installed.
Nothing to do.
No packages downloaded
Qubes OS Repository for Dom0 0.0 B/s | 0 B 00:00
Errors during downloading metadata for repository âqubes-dom0-cachedâ:
- Curl error (37): Couldnât read a file:// file for file:///var/lib/qubes/updates/repodata/repomd.xml [Couldnât open file /var/lib/qubes/updates/repodata/repomd.xml]
Error: Failed to download metadata for repo âqubes-dom0-cachedâ: Cannot download repomd.xml: Cannot download repodata/repomd.xml: All mirrors were tried
Ignoring repositories: qubes-dom0-cached
Package alsa-sof-firmware-2023.09.1-1.fc37.noarch is already installed.
Dependencies resolved.
Nothing to do.
Complete!
Just googled around to find that newer versions are available for alsa-sof-firmware but I do not know how this work internally in Qubes. I am very new and want to stick to standard offerings.
https://bodhi.fedoraproject.org/updates/?packages=alsa-sof-firmware
My another question is when I tried to update the alsa-sof-firmware as suggested, it used Fedora 37 as you can read in the log above.
When I do qvm-template list I find many Fedora versions last being fedora-42.
Why my alsa-sof-firmware update did not use fedora 42 ? that way I could have got alsa-sof-firmware-2025.05.1-1.fc42 it seems to have created for fedora 42 as per the bodhi site. What do you guys think?
When I run cat /etc/fedora-release in default-dvm I see Fedora 41.
I think I am all over the place on this and do not understand much.
Please help if you can get me having my audio
Try this
sudo qubes-dom0-update --action=upgrade alsa-sof-firmware
But for Arrow Lake kernel 6.15+ is recomended.
Try r4.3rc4
It did nothing.
when I do uname -r I get the following
6.17.9-1.qubes.fc37.x86_64
Yesterday I ran update for dom0 I guess it moved me from
6.12.11-1.qubes.fc37.x86_64 to 6.17.9-1.qubes.fc37.x86_64
When I try your command it says - nothing to do. When I try with action=upgrade alsa-sof-firmware command it says alsa-sof-firmware-2023.09.1-1.fc37.noarch is already installed.
I think I need alsa-sof-firmware-2025.05.1-1.fc42 or fc41 for my audio to work.
Any other way to get this without upgrading to r4.3rc4. I am always in favour of having the release stable ( specially new user) but having no audio is an issue I cant ignore.
You donât need an audio device in dom0âs audio mixer to have sound. You only need it if dom0 serves as audiovm of the qube you are trying to play sound from. You can check it with:
qvm-prefs name_of_your_qube audiovm
If it returns nothing, audiovm is not set.
Assuming you havenât set up an audiovm yet, you can simply pass (attach) an audio device to whatever qube you want to listen to. Depending on what audio device you want to use, see: