"Dummy Output", no audio after installation of Fedora

Once I install the OS I have no audio and in the settings under audio output devices only “Dummy Output” is shown. HDMI or AUX also didn’t work, only connecting a Bluetooth device works.

I just bought a new Laptop and installed a few Linux distros right after, and I am now landing on Fedora (I’m here to stay). I’ve had this problem with all the distros I have tried (Mint, Arch, Manjaro, PopOs).

I have tried finding the solution on other forums, but nothing seems to be working for me.

Here some device info:


mmatic@fedora:~$ inxi -bAE
System:
  Host: fedora Kernel: 6.10.3-200.fc40.x86_64 arch: x86_64 bits: 64
  Desktop: GNOME v: 46.4 Distro: Fedora Linux 40 (Workstation Edition)
Machine:
  Type: Laptop System: Acer product: Swift SFG14-72 v: V1.01
    serial: <superuser required>
  Mobo: MTL model: Coral_MTH v: V1.01 serial: <superuser required>
    UEFI: Insyde v: 1.01 date: 11/06/2023
Battery:
  ID-1: BAT1 charge: 64.9 Wh (100.0%) condition: 64.9/64.9 Wh (100.0%)
CPU:
  Info: 16-core (6-mt/10-st) Intel Core Ultra 7 155H [MST AMCP] speed (MHz):
    avg: 549 min/max: 400/4800:4600:3800:2500
Graphics:
  Device-1: Intel Meteor Lake-P [Intel Arc Graphics] driver: i915 v: kernel
  Device-2: Quanta ACER QHD User Facing driver: uvcvideo type: USB
  Display: wayland server: X.Org v: 24.1.2 with: Xwayland v: 24.1.2
    compositor: gnome-shell driver: dri: iris gpu: i915 resolution:
    1: 1920x1080~60Hz 2: 2880x1800~90Hz
  API: OpenGL v: 4.6 vendor: intel mesa v: 24.1.5 renderer: Mesa Intel Arc
    Graphics (MTL)
Audio:
  Device-1: Intel Meteor Lake-P HD Audio driver: sof-audio-pci-intel-mtl
  API: ALSA v: k6.10.3-200.fc40.x86_64 status: kernel-api
  Server-1: PipeWire v: 1.0.7 status: active
  Server-2: PulseAudio v: 16.1 status: active
Network:
  Device-1: Intel Meteor Lake PCH CNVi WiFi driver: iwlwifi
Bluetooth:
  Device-1: Intel AX211 Bluetooth driver: btusb type: USB
  Report: btmgmt ID: hci0 state: up address: C4:3D:1A:F5:C9:76 bt-v: 5.3
Drives:
  Local Storage: total: 953.87 GiB used: 5.96 GiB (0.6%)
Info:
  Memory: total: 16 GiB available: 15.28 GiB used: 3.84 GiB (25.1%)
  Processes: 487 Uptime: 2m Shell: Bash inxi: 3.3.34


mmatic@fedora:~$ wpctl status
PipeWire 'pipewire-0' [1.0.7, mmatic@fedora, cookie:3307048294]
 └─ Clients:
        31. WirePlumber                         [1.0.7, mmatic@fedora, pid:2458]
        39. WirePlumber [export]                [1.0.7, mmatic@fedora, pid:2458]
        46. uresourced                          [1.0.7, mmatic@fedora, pid:2614]
        47. gnome-shell                         [1.0.7, mmatic@fedora, pid:2686]
        48. xdg-desktop-portal                  [1.0.7, mmatic@fedora, pid:3282]
        49. wpctl                               [1.0.7, mmatic@fedora, pid:5427]

Audio
 ├─ Devices:
 │  
 ├─ Sinks:
 │  
 ├─ Sources:
 │  
 ├─ Filters:
 │  
 └─ Streams:

Video
 ├─ Devices:
 │  
 ├─ Sinks:
 │  
 ├─ Sources:
 │  
 ├─ Filters:
 │  
 └─ Streams:

Settings
 └─ Default Configured Devices:
         0. Audio/Sink    auto_null

1 Like

Please :cry: I need help, does anyone know what may help? I am happy to answer any questions you have.

It looks like this problem has been reported here before:

Does the provided workaround not work for you?

Edit: Nevermind, I see that you said that you were able to get it to work with a bluetooth device and that is as far as the other users got as well. You might ping that other thread and ask if there has been any further progress on getting your audio device to work, but it has only been about a month since the last update, so I wouldn’t get my hopes up.

Thank you for the reply. Someone just posted something there that may help. I will look into it, thanks :slight_smile:

You might want to consider looking at hardware information and device drivers.

  • Hardware information

It is always useful to include detailed information on your sound hardware when filing a sound-related problem. To produce this information, run this command:

$ alsa-info.sh --no-upload

It will generate a file containing detailed information about your sound hardware with the name /tmp/alsa-info.txt. Attach this file here (Ctrl + e to insert preformatted text).

  • Check which Kernel driver is in use by PCI devices

To display kernel drivers handling each device, use the lspci (List PCI) command with the option -k.

$ sudo lspci -k

1 Like

thanks for wanting to help.

I didn’t see any trace of Linux recognizinig any audio device.

I just gave up and tried installing windows to see if it was maby a hardware issue, and I also had a lot problems with that. Windows boot stick didn’t recognize the SSD, I solved that, but then after installing windows didn’t recognize my Touchpad, Audio card, or Wifi card. So I just gave up and returned the Laptop, just wanted to say this for anyone having this issue with the same Laptop.

Thanks again for trying to help. :slight_smile:

1 Like