I was trying to fix some noise floor issues with my DAC+IEM combo with alsamixer and somehow completely broke pipewire. I managed to get pipewire working again but now it shows only dummy output.
I deleted all remnants of earlier pipewire changes (all confs of pipewire & wireplumber -> reemerged), deleted .asoundrc and all other alsa remnants. My sound card is getting detected in dmesg and even alsamixer seems to find them. Enabling pipewire-alsa doesn't fix it and pipewire was always working without that USE flag.
I seriously have no idea how I broke it in the first place and now no idea why it's not detecting my sound cards. I've tried both gentoo-pipewire-launcher and the openrc user services to start.
emerge --info: https://bpa.st/UKZQ
wpctl status: https://bpa.st/KW7Q
pactl list: https://bpa.st/D6QA
dmesg: https://bpa.st/LTBQ
pipewire USE flags: +dbus +sound-server +ssl
Pipewire Dummy Output
Message
I'm not a PA/PW SME. I try to avoid these complexities whenever possible.
That said,
I have no idea where your larger module numbers are originating from, but let's overlook that for the time being.
Now look at Sink #34 and Source #34, Owner Module: 4294967295. This is for Dummy Output and Monitor of Dummy Output, respectively.
Your pipewire output is showing syncing to dummy. Your pulseaudio output is showing mappings of the above. See the problem(s)?
Here's a simple(?) example of mine on a basic install:
See the 1-1 mappings and no outliers on Owners vs Modules available?
Likewise, no sink is set established:
That said,
Code: Select all
$ wpctl status
PipeWire 'pipewire-0' [1.4.9, linthalo@L1NTHALO_GENTOO, cookie:459216326]
└─ Clients:
32. pipewire [1.4.9, linthalo@L1NTHALO_GENTOO, pid:19916]
33. waybar [1.4.9, linthalo@L1NTHALO_GENTOO, pid:1669]
35. waybar [1.4.9, linthalo@L1NTHALO_GENTOO, pid:1669]
36. xdg-desktop-portal [1.4.9, linthalo@L1NTHALO_GENTOO, pid:1789]
37. WirePlumber [1.4.9, linthalo@L1NTHALO_GENTOO, pid:19909]
49. WirePlumber [export] [1.4.9, linthalo@L1NTHALO_GENTOO, pid:19909]
50. wpctl [1.4.9, linthalo@L1NTHALO_GENTOO, pid:24190]
Audio
├─ Devices:
│
├─ Sinks:
│ * 34. Dummy Output [vol: 1.00]
│
├─ Sources:
│
├─ Filters:
│
└─ Streams:
Video
├─ Devices:
│
├─ Sinks:
│
├─ Sources:
│
├─ Filters:
│
└─ Streams:
Settings
└─ Default Configured Devices:
Code: Select all
Module #1
Module #2
Module #4
Module #6
Module #8
Module #10
Module #12
Module #14
Module #16
Module #17
Module #18
Module #20
Module #22
Module #536870912
Module #536870913
Module #536870914
Module #536870915
Code: Select all
Owner Module: 4294967295
Owner Module: 4294967295
Owner Module: 2
Owner Module: 2
Owner Module: 2
Owner Module: 2
Owner Module: 2
Owner Module: 2
Owner Module: 2
Now look at Sink #34 and Source #34, Owner Module: 4294967295. This is for Dummy Output and Monitor of Dummy Output, respectively.
Your pipewire output is showing syncing to dummy. Your pulseaudio output is showing mappings of the above. See the problem(s)?
Here's a simple(?) example of mine on a basic install:
Code: Select all
Module #0
Module #1
Module #2
Module #3
Module #4
Module #5
Module #6
Module #8
Module #9
Module #10
Module #11
Module #12
Module #13
Module #14
Module #15
Module #16
Module #17
Module #18
Module #19
Module #20
Module #21
Module #22
Module #23
Module #24
Module #25
Code: Select all
Owner Module: 6
Owner Module: 8
Owner Module: 6
Owner Module: 8
Owner Module: 8
Owner Module: 8
Owner Module: 18
Owner Module: 18
Owner Module: 12
Owner Module: 25
Owner Module: 12
Owner Module: 12
Owner Module: 6
Owner Module: 8
See the 1-1 mappings and no outliers on Owners vs Modules available?
Likewise, no sink is set established:
Code: Select all
$ wpctl status
PipeWire 'pipewire-0' [1.4.9, noone@amd300, cookie:1402655141]
└─ Clients:
33. xdg-desktop-portal [1.4.9, noone@amd300, pid:16349]
34. WirePlumber [1.4.9, noone@amd300, pid:16289]
42. WirePlumber [export] [1.4.9, noone@amd300, pid:16289]
43. wpctl [1.4.9, noone@amd300, pid:22556]
Audio
├─ Devices:
│
├─ Sinks:
│
├─ Sources:
│
├─ Filters:
│
└─ Streams:
Video
├─ Devices:
│
├─ Sinks:
│
├─ Sources:
│
├─ Filters:
│
└─ Streams:
Settings
└─ Default Configured Devices:
(I don't speak for/represent my current/past employers)
If it were me, I'd start with trying to find a default clean slate by removal of those configurations.
1. Might be good to backup your system if you haven't, just in case
2. find /etc ~ -iname "*.conf" -exec grep -il pulse "{}" \; 2>/dev/null, ran as your user, should reasonably find most related pulseaudio configuration files in your home directory and /etc. You may want to run it as well as root just on /etc. We're just looking for configuration files that are clearly specific pulseaudio and not something else referring to same or something else with the keyword 'pulse'.
3. Investigate the files produced looking for indicators of what you've shown us.
4. Use portage to completely purge pulseaudio and pipewire.
5. Re-eval any strays leftover from steps 2-3 and consider their removal, if and only if, they look like they have information related to your existing setup provided.
6. Remove ~/.config/pulse/ which generally contains internal database files.
I would also look into having neither running, while installed, and starting pulseaudio with a trace on open calls, e.g., to see what files it is loading, while ignoring the many shared library .so hits. That's only if we couldn't resolve purging back to a default setup from the aforementioned steps.
Would also consider a full review of https://wiki.gentoo.org/wiki/PipeWire before anything which may help you in your current state.
E.g., as mentioned from same:
1. Might be good to backup your system if you haven't, just in case
2. find /etc ~ -iname "*.conf" -exec grep -il pulse "{}" \; 2>/dev/null, ran as your user, should reasonably find most related pulseaudio configuration files in your home directory and /etc. You may want to run it as well as root just on /etc. We're just looking for configuration files that are clearly specific pulseaudio and not something else referring to same or something else with the keyword 'pulse'.
3. Investigate the files produced looking for indicators of what you've shown us.
4. Use portage to completely purge pulseaudio and pipewire.
5. Re-eval any strays leftover from steps 2-3 and consider their removal, if and only if, they look like they have information related to your existing setup provided.
6. Remove ~/.config/pulse/ which generally contains internal database files.
I would also look into having neither running, while installed, and starting pulseaudio with a trace on open calls, e.g., to see what files it is loading, while ignoring the many shared library .so hits. That's only if we couldn't resolve purging back to a default setup from the aforementioned steps.
Would also consider a full review of https://wiki.gentoo.org/wiki/PipeWire before anything which may help you in your current state.
E.g., as mentioned from same:
Dummy Output with PipeWire running
If the pipewire and wireplumber services are running and PipeWire is not detecting your audio input/output devices, only Dummy Output will show up as an output device. This may be because ACL is missing. Make sure the acl USE flag is not disabled in /etc/portage/make.conf and rerun emerge if a change was made.
(I don't speak for/represent my current/past employers)