Thank you.

I ran the Week 14 update today. After the update, there was an "analog stereo" or something brief notification in the middle of the screen, that I've often noticed after an update completes.

Then the audio was working fine.

I restarted. And it's back to showing "No output or input devices found" if I click on the audio icon in the tray.

6 days later

This issue appears to have resolved itself somehow, as the last two times I started up, the local audio device is showing up fine.

3 months later

fixed:
hi, this morning I updated the system and I lost the sound after rebooting.
and I found a simple solution:

reinstalling sof-firmware,
you can do it from terminal:

sudo eopkg remove sof-firmware
sudo eopkg install sof-firmware

or through Software Center.
then restart , and voilà, now the sound it's working again!

  • Gwen replied to this.

    walid Same problem for me, on both my computers. Your solution worked, thank you!

        a month later

        Gwen hi Gwen, this workaround is not working anymore for me. since last update I have no sound again (dummy output only).

            Can everyone that has audio issue, after this week update, comment on this issue on github? The comment should contain at minimum : your hardware specs (inxi -b) and whether or not rolling back to previous kernel, pipewire, sof-firmware or other package helps. Cheers!

            Only the inbuilt Microphones didn't work for me anymore.
            I TEMP fixed mine by reverting the Kernel version until a permanent fix is found.
            I will hide the details due to the valid concerns posted by @Harvey below.

            sudo clr-boot-manager list-kernels
            This returned the following two Kernels with the latest default kernel marked with an asterisk *
            *com.solus-project.current.6.9.12-297
            com.solus-project.current.6.9.10-295

            To change to the previous kernel I used the below cmd.
            sudo clr-boot-manager set-kernel com.solus-project.current.6.9.10-295
            Now reboot and you should be back on the previous Kernel to check.
            sudo clr-boot-manager list-kernels
            com.solus-project.current.6.9.12-297
            *com.solus-project.current.6.9.10-295

            To revert
            sudo clr-boot-manager set-kernel com.solus-project.current.6.9.12-297

            WARNING:PLEASE USE YOUR OWN RETURNED KERNEL VERSIONS.

            The above workaround is not recommended. The old kernel if it exists is there as a safety option for recovery purposes only. This old kernel will get cleared out periodically and using it could expose you to security issues and other headaches.

            For example if you have an nvidia video card using the proprietary driver switching to an older kernel boot option instead of doing a rollback for the updates will break video output since the driver is built against the kernel.

            So it would be better to switch to the linux-lts kernel (6.6.43 at the time of writing) as a more concrete workaround. Nvidia users on the proprietary driver will need to install the appropriate driver for that kernel (It will not have -current in its name). i.e if you are using nvidia-glx-driver-current you need nvidia-glx-driver to work with the linux-lts kernel.

            After that is setup you can reboot and spam the space bar to get a boot menu to appear where you will be able to select the -lts kernel. You can make that the new default kernel to boot once logged in by running sudo clr-boot-manager update

              Harvey I am using linux-lts and the issue is happening there too.

                I just have a problem with the audio of a video file not working with VLC only, but it must be a coincidence, it's the first time VLC won't read something to me.

                main playlist: playlist is empty
uint DBusMenuExporterDBus::GetLayout(int, int, const QStringList&, DBusMenuLayoutItem&): Condition failed: menu
libva info: VA-API version 1.22.0
libva error: vaGetDriverNames() failed with unknown libva error
[00007fccb40015a0] glconv_vaapi_x11 gl error: vaInitialize: unknown libva error
libva info: VA-API version 1.22.0
libva info: Trying to open /usr/lib64/dri/nvidia_drv_video.so
libva info: va_openDriver() returns -1
[00007fccb40015a0] glconv_vaapi_drm gl error: vaInitialize: unknown libva error
libva info: VA-API version 1.22.0
libva info: Trying to open /usr/lib64/dri/nvidia_drv_video.so
libva info: va_openDriver() returns -1
[00007fccb40015a0] glconv_vaapi_drm gl error: vaInitialize: unknown libva error
libva info: VA-API version 1.22.0
libva info: Trying to open /usr/lib64/dri/iHD_drv_video.so
libva info: Found init function __vaDriverInit_1_22
libva info: va_openDriver() returns 0
[00007fccc0c0f580] main video output error: video output creation failed
[00007fccc0c06100] main decoder error: failed to create video output
[ass] libass API version: 0x1702000
[ass] libass source: tarball: 0.17.2
[ass] Shaper: FriBidi 1.0.12 (SIMPLE) HarfBuzz-ng 9.0.0 (COMPLEX)
[ass] Using font provider fontconfig
[00007fccc0c69c50] opus decoder error: cannot read Opus header
[00007fccc0c69c50] opus decoder error: initial Opus header is corrupted
[00007fccc0c69c50] opus decoder error: cannot read Opus header
[00007fccc0c69c50] opus decoder error: initial Opus header is cor

                  FAb7D

                  Audio problems with VLC (and not the whole system) is a separate issue. Please look to see if there's an issue on the tracker. If not, please create a new one so we can look into it. Thanks.

                      I got my sound device working again by rolling back to update 17
                      lspci | grep -i audio
                      0000:00:1f.3 Multimedia audio controller: Intel Corporation Alder Lake PCH-P High Definition Audio Controller (rev 01)

                      sudo eopkg history -t 17
                      This has fixed it for me (Vivobook 14 from 2022)
                      Aug. 17th edit:
                      I tried the update again and this time - no issues. Sound is fine. Not sure what has changed or if something just went wrong tha last time. I hope it stays that way.

                      The latest update fixed it momentarily until I rebooted. Then back to dummy output.