No output or input devices found

Ask Fedora
, ,
1

Hello, I’m new here and hope someone can help me out.

Every morning, when I open my laptop, I usually run the command sudo dnf update -y to check for any updates, followed by a reboot.

Today, after the reboot, I noticed a red line on my sound icon. When I clicked on it, the message “No output or input devices found” appeared. Additionally, I can’t increase or decrease the volume using the respective keys—nothing appears on the screen.

This issue started after the update. The problem is, I don’t know what was updated since I usually run the command without paying much attention. I understand it’s my fault.

If someone could guide me through a solution, I would appreciate it. Thank you.

5ee56b069343a6b38448e4fb759932946a10a21f.png
5ee56b069343a6b38448e4fb759932946a10a21f.png783×462 70.3 KB

(I’m a new user so I can only upload one embedded media item)

2

You are not limited if you were to post that as text. Graphics images are mostly discouraged since they may be difficult to read, cannot be simply copied and pasted, cannot have portions quoted. All this makes a response to portions of the post much more difficult for others to do. Please post text from the screen as preformatted text using the </> button above to tag it appropriately.

What can you tell about sound by using the audio control panel instead of the keyboard? (you are using KDE and I use Gnome so there is a difference in the desktop controls)

1 Like
3

Can you gives us the output of pw-cli info all in a preformatted, code, or Hide Details block?

1 Like
6

Can you post the following as pre-formatted text.
systemctl status --no-pager --user wireplumber.service
systemctl status --no-pager --user pipe*.service
journalctl -b -g 'snd|sound'

Do you know what was upgraded?
You can find out by:
If that was the last DNF transaction that was done
sudo dnf history info last

If not:
sudo dnf --reverse history
you will want to find the ID (number on the left) of the transaction where you ran the update.
sudo dnf history info "ID NUMBER"
should tell you what was upgraded.

alsa, pipewire, wireplumber and the kernel could all be related to this issue.
Thanks

7

Of course! Here is the output for all three of the commands.

systemctl status --no-pager --user wireplumber.service gives me this:

* wireplumber.service - Multimedia Service Session Manager
     Loaded: loaded (/usr/lib/systemd/user/wireplumber.service; enabled; preset: enabled)
     Active: active (running) since Mon 2023-01-16 12:03:10 CET; 2h 38min ago
   Main PID: 6950 (wireplumber)
      Tasks: 5 (limit: 9340)
     Memory: 10.3M
        CPU: 40ms
     CGroup: /user.slice/user-1000.slice/user@1000.service/session.slice/wireplumber.service
             |-1473 /usr/bin/wireplumber
             `-6950 /usr/bin/wireplumber

gen 16 12:03:10 fugaku systemd[1229]: Started wireplumber.service - Multimedia Service Session Manager.
gen 16 12:03:20 fugaku wireplumber[6950]: Failed to set scheduler settings: Operation not permitted
gen 16 12:03:20 fugaku wireplumber[6950]: SPA handle 'api.libcamera.enum.manager' could not be loaded; is it installed?
gen 16 12:03:20 fugaku wireplumber[6950]: PipeWire's libcamera SPA missing or broken. libcamera not supported.

systemctl status --no-pager --user pipe*.service gives me this:

* pipewire-pulse.service - PipeWire PulseAudio
     Loaded: loaded (/usr/lib/systemd/user/pipewire-pulse.service; disabled; preset: disabled)
     Active: active (running) since Mon 2023-01-16 10:59:31 CET; 3h 46min ago
TriggeredBy: * pipewire-pulse.socket
   Main PID: 2014 (pipewire-pulse)
      Tasks: 2 (limit: 9340)
     Memory: 2.3M
        CPU: 526ms
     CGroup: /user.slice/user-1000.slice/user@1000.service/session.slice/pipewire-pulse.service
             `-2014 /usr/bin/pipewire-pulse

gen 16 10:59:31 fugaku systemd[1229]: Started pipewire-pulse.service - PipeWire PulseAudio.

* pipewire.service - PipeWire Multimedia Service
     Loaded: loaded (/usr/lib/systemd/user/pipewire.service; disabled; preset: disabled)
    Drop-In: /usr/lib/systemd/user/pipewire.service.d
             `-00-uresourced.conf
     Active: active (running) since Mon 2023-01-16 12:03:10 CET; 2h 43min ago
TriggeredBy: * pipewire.socket
   Main PID: 6948 (pipewire)
      Tasks: 2 (limit: 9340)
     Memory: 1.5M
        CPU: 19ms
     CGroup: /user.slice/user-1000.slice/user@1000.service/session.slice/pipewire.service
             `-6948 /usr/bin/pipewire

gen 16 12:03:10 fugaku systemd[1229]: Started pipewire.service - PipeWire Multimedia Service.

journalctl -b -g 'snd|sound' gives me this:

gen 16 10:59:11 fugaku kernel: snd_hda_intel 0000:00:1f.3: DSP detected with PCI class/subclass/prog-if info 0x040100
gen 16 10:59:11 fugaku kernel: snd_hda_intel 0000:00:1f.3: Digital mics found on Skylake+ platform, using SST driver
gen 16 10:59:11 fugaku kernel: snd_soc_skl 0000:00:1f.3: DSP detected with PCI class/subclass/prog-if info 0x040100
gen 16 10:59:11 fugaku kernel: snd_soc_skl 0000:00:1f.3: Digital mics found on Skylake+ platform, using SST driver
gen 16 10:59:11 fugaku kernel: snd_soc_skl 0000:00:1f.3: bound 0000:00:02.0 (ops i915_audio_component_bind_ops [i915])
gen 16 10:59:11 fugaku kernel: snd_soc_skl 0000:00:1f.3: Direct firmware load for 9d71-ACRSYS-ACRPRDCT-2-tplg.bin failed with error -2
gen 16 10:59:11 fugaku kernel: snd_soc_skl 0000:00:1f.3: tplg fw 9d71-ACRSYS-ACRPRDCT-2-tplg.bin load failed with -2, trying alternative tplg name skl_hda_dsp_generic-tplg.bin
gen 16 10:59:11 fugaku kernel: snd_hda_codec_realtek ehdaudio0D0: autoconfig for ALC256: line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker
gen 16 10:59:11 fugaku kernel: snd_hda_codec_realtek ehdaudio0D0:    speaker_outs=0 (0x0/0x0/0x0/0x0/0x0)
gen 16 10:59:11 fugaku kernel: snd_hda_codec_realtek ehdaudio0D0:    hp_outs=1 (0x21/0x0/0x0/0x0/0x0)
gen 16 10:59:11 fugaku kernel: snd_hda_codec_realtek ehdaudio0D0:    mono: mono_out=0x0
gen 16 10:59:11 fugaku kernel: snd_hda_codec_realtek ehdaudio0D0:    inputs:
gen 16 10:59:11 fugaku kernel: snd_hda_codec_realtek ehdaudio0D0:      Internal Mic=0x1a
gen 16 10:59:11 fugaku kernel: snd_hda_codec_realtek ehdaudio0D0:      Headset Mic=0x19
gen 16 10:59:11 fugaku kernel: input: hda-dsp Front Headphone as /devices/platform/skl_hda_dsp_generic/sound/card0/input26
gen 16 10:59:11 fugaku kernel: input: hda-dsp HDMI/DP, pcm=17 Jack as /devices/platform/skl_hda_dsp_generic/sound/card0/input27
gen 16 10:59:11 fugaku kernel: input: hda-dsp HDMI/DP, pcm=18 Jack as /devices/platform/skl_hda_dsp_generic/sound/card0/input28
gen 16 10:59:11 fugaku kernel: input: hda-dsp HDMI/DP, pcm=19 Jack as /devices/platform/skl_hda_dsp_generic/sound/card0/input29
gen 16 10:59:11 fugaku systemd[1]: alsa-restore.service - Save/Restore Sound Card State was skipped because of a failed condition check (ConditionPathExists=!/etc/alsa/state-daemon.conf).
gen 16 10:59:11 fugaku systemd[1]: Started alsa-state.service - Manage Sound Card State (restore and store).
gen 16 10:59:11 fugaku systemd[1]: Reached target sound.target - Sound Card.
gen 16 11:17:17 fugaku konsole[2915]: kf.notifications: Failed to play sound with canberra: IO error
gen 16 11:17:59 fugaku konsole[2915]: kf.notifications: Failed to play sound with canberra: IO error
gen 16 11:18:46 fugaku konsole[2915]: kf.notifications: Failed to play sound with canberra: IO error
gen 16 11:52:53 fugaku konsole[2915]: kf.notifications: Failed to play sound with canberra: IO error
gen 16 11:59:01 fugaku konsole[6176]: kf.notifications: Failed to play sound with canberra: IO error

Unfortunately I can’t remember what was upgraded, I’ll try to follow your instructions.

This happened the 15-01, it was almost lunch time for me so I think I found the ID of the transaction (57).
Using the command that you have given me I receive this output:

[sasha@fugaku ~]$ sudo dnf history info 57
Transaction ID : 57
Begin time     : dom 15 gen 2023, 12:58:33
Begin rpmdb    : 0d0493b5ddede13ffea94c338006e02eaf7f18171ee20d712923553abe4b3a29
End time       : dom 15 gen 2023, 12:59:52 (79 seconds)
End rpmdb      : a9e0fd3e361fc13c2a120e92e86a148eb08b2fdd7b41de4da4db3b8ecb423e5c
User           : Sasha <sasha>
Return-Code    : Success
Releasever     : 37
Command Line   : update -y
Comment        : 
Packages Altered:
    Install       kernel-6.1.5-200.fc37.x86_64                @updates
    Install       kernel-core-6.1.5-200.fc37.x86_64           @updates
    Install       kernel-modules-6.1.5-200.fc37.x86_64        @updates
    Install       kernel-modules-extra-6.1.5-200.fc37.x86_64  @updates
    Upgrade       glibc-2.36-9.fc37.i686                      @updates
    Upgraded      glibc-2.36-8.fc37.i686                      @@System
    Upgrade       glibc-2.36-9.fc37.x86_64                    @updates
    Upgraded      glibc-2.36-8.fc37.x86_64                    @@System
    Upgrade       glibc-all-langpacks-2.36-9.fc37.x86_64      @updates
    Upgraded      glibc-all-langpacks-2.36-8.fc37.x86_64      @@System
    Upgrade       glibc-common-2.36-9.fc37.x86_64             @updates
    Upgraded      glibc-common-2.36-8.fc37.x86_64             @@System
    Upgrade       glibc-devel-2.36-9.fc37.x86_64              @updates
    Upgraded      glibc-devel-2.36-8.fc37.x86_64              @@System
    Upgrade       glibc-gconv-extra-2.36-9.fc37.i686          @updates
    Upgraded      glibc-gconv-extra-2.36-8.fc37.i686          @@System
    Upgrade       glibc-gconv-extra-2.36-9.fc37.x86_64        @updates
    Upgraded      glibc-gconv-extra-2.36-8.fc37.x86_64        @@System
    Upgrade       glibc-headers-x86-2.36-9.fc37.noarch        @updates
    Upgraded      glibc-headers-x86-2.36-8.fc37.noarch        @@System
    Upgrade       glibc-langpack-en-2.36-9.fc37.x86_64        @updates
    Upgraded      glibc-langpack-en-2.36-8.fc37.x86_64        @@System
    Upgrade       kernel-headers-6.1.5-200.fc37.x86_64        @updates
    Upgraded      kernel-headers-6.0.5-300.fc37.x86_64        @@System
    Upgrade       libnsl-2.36-9.fc37.i686                     @updates
    Upgraded      libnsl-2.36-8.fc37.i686                     @@System
    Upgrade       libnsl-2.36-9.fc37.x86_64                   @updates
    Upgraded      libnsl-2.36-8.fc37.x86_64                   @@System
    Upgrade       poppler-22.08.0-3.fc37.x86_64               @updates
    Upgraded      poppler-22.08.0-2.fc37.x86_64               @@System
    Upgrade       poppler-cpp-22.08.0-3.fc37.x86_64           @updates
    Upgraded      poppler-cpp-22.08.0-2.fc37.x86_64           @@System
    Upgrade       poppler-glib-22.08.0-3.fc37.x86_64          @updates
    Upgraded      poppler-glib-22.08.0-2.fc37.x86_64          @@System
    Upgrade       poppler-qt5-22.08.0-3.fc37.x86_64           @updates
    Upgraded      poppler-qt5-22.08.0-2.fc37.x86_64           @@System
    Upgrade       poppler-utils-22.08.0-3.fc37.x86_64         @updates
    Upgraded      poppler-utils-22.08.0-2.fc37.x86_64         @@System
    Upgrade       discord-0.0.23-1.fc37.x86_64                @rpmfusion-nonfree-updates
    Upgraded      discord-0.0.22-1.fc37.x86_64                @@System
    Reason Change Box2D-2.4.1-8.fc37.x86_64                   @anaconda
    Removed       kernel-6.0.16-300.fc37.x86_64               @@System
    Removed       kernel-core-6.0.16-300.fc37.x86_64          @@System
    Removed       kernel-modules-6.0.16-300.fc37.x86_64       @@System
    Removed       kernel-modules-extra-6.0.16-300.fc37.x86_64 @@System

Hope this can be of any help, thank you for you time.

1 Like
8

You may want to try:
sudo tee /etc/modprobe.d/dspcfg.conf <<< 'options snd-intel-dspcfg dsp_driver=1'

to remove:
sudo rm /etc/modprobe.d/dspcfg.conf

You may also want to try falling back to an older kernel.
You should be able to hold shift during boot and to get to the grub menu and then select an older kernel.

Thanks

9

OK, thank you for your help so far, I’ll try doing that.