Pipewire on openSUSE is not working -- no sound at all
Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Distribution: openSUSE, Raspbian, Slackware. Previous: MacOS, Red Hat, Coherent, Consensys SVR4.2, Tru64, Solaris
Posts: 2,818
Rep:
Pipewire on openSUSE is not working -- no sound at all
I've been trying to get sound on a fairly new Leap 15.6rc install (no updates as of earlier today other than some for Mesa and vlc which I declined) as well as an up-to-date Tumbleweed install to no avail. Both systems are using the ALC887 audio chip on the motherboard. The Leap system has sound but only when the motherboard audio is disabled and then the TU116 chip takes over (routing tinny sound to my monitor via HDMI -- not acceptable).
Audacious, for example, spits out error messages about the "snd_pcm_open" module not being found ("no such file or directory") when trying to use ALSA output. Sure enough... "lsmod | grep snd_pcm_open" doesn't show it's been loaded. "insmod" can't load it either.
I get a popup dialog stating: "Error opening output stream" if I try Pipewire or Pulseaudio output. On the CLI, I'm getting
Code:
$ audacious
ERROR ../src/pipewire/pipewire.cc:310 [init_core]: PipeWireOutput: unable to connect context
Clear as mud that message is.
I'm seeing a lot of references to systemctl being used to manage the pipewire software. Trouble is that I'm not seeing unit files for pipewire on either system.
What is missing in openSUSE's pipewire setup? A dependency of some sort? Frankly, I've run out if ideas.
TIA to anyone who can shed some light on what's going on (or not, as the case seems to be).
NOTE: This result was after going into the BIOS and re-enabling the onboard analog sound function (the desired situation, BTW). I have to turn this off if I don't want to go nuts with the
Code:
TU116 High Definition Audio Controller Digital Stereo (HDMI)
Built-in High Definition Analog Stereo
messages flashing repeatedly on whatever monitor the mouse happens to be positioned in.
Trying to configure sound via the panel's volume widget is a waste of time. The display twitches so fast you can never hope to make any changes.
For now, I'm disabling the HD audio device in the BIOS. I can easily re-enable ii if a promising solution is suggested.
I've started to attempt to use this as my music player in the event that System 1 will never work. All of my music files reside on this system anyway. System 1 is/was mounting that filesystem via NFS and that worked fine. (It's the means by which the RPi connected to the big stereo in the living room has been accessing music files for some years.)
In neither system is Audacious able to connect to an audio device. TBH, I've been trying various combinations of packages -- pipewire, jack, pulseaudio -- and nothing seems to get past an "unable to connect"-type error popup message.
It might be better to use pipewire-jack (wrapper for pipewire) instead...
Code:
sudo zypper in pipewire-jack
That's two different physical systems/boxes. I missed that inxi calls out "servers".
System 2 is using PulseAudio and Jack...
Code:
Server-1: JACK v: N/A status: off tools: jack_control
Server-2: PulseAudio v: 17.0 status: off with: pulseaudio-alsa
type: plugin tools: pacat,pactl,pamix,pamixer,pavucontrol
Quote:
It might be better to use pipewire-jack (wrapper for pipewire) instead...
Code:
sudo zypper in pipewire-jack
What I get:
Code:
$ sudo zypper install pipewire-jack
Refreshing service 'NVIDIA'.
Refreshing service 'openSUSE'.
Loading repository data...
Reading installed packages...
'pipewire-jack' is already installed.
No update candidate for 'pipewire-jack-1.0.5+git36.60deeb2-150600.1.2.x86_64'. The highest available version is already installed.
Resolving package dependencies...
Nothing to do.
NOTE: Sound is working on System 1 but it's using the TU116 card and routing all sound to my tinny monitor speakers via HDMI. If we want to explore solutions using the ALC887 card, please let me know as I'll need to tweak the BIOS, reboot, etc.
Last edited by rnturn; 05-21-2024 at 06:30 PM.
Reason: Added note about sound card.
Distribution: openSUSE, Raspbian, Slackware. Previous: MacOS, Red Hat, Coherent, Consensys SVR4.2, Tru64, Solaris
Posts: 2,818
Original Poster
Rep:
Quote:
Originally Posted by ferrari
Try using pavucontrol ('Configuration' tab) to set the desired card profile.
Well... that, at least, allowed the TU116 to be disabled and the built-in audio to be selected without a rapid-fire display of sound cards being displayed on the monitors. Still no actual sound output, though.
Pipewire is being used but... Jack-related utilities don't work -- at least jack_mixer doesn't so I can't confirm that there's even a connection to the system sound output like I could with jack+jack_mixer. Carla displays garbage (devices popping in and out of existence and connections to some device that don't even appear on the patch panel). Perhaps I read more into the claims about Pipewire providing all the functionality that Jack provided and it really doesn't. It's frustrating at best.
Q: How do I remove Pipewire completely as a fall-back and allow me to revert back to the Jack+Pulseaudio configuration that was successfully used in my 15.3 setup? Some may see Pipewire as the future but, IMHO, it sure seems as though it ain't ready for prime time yet. (Heck, Pulseaudio's intro was less of a hassle than Pipewire's.)
Sorry to vent but Pipewire's about to give me an ulcer.
Well... that, at least, allowed the TU116 to be disabled and the built-in audio to be selected without a rapid-fire display of sound cards being displayed on the monitors. Still no actual sound output, though.
Did you set the appropriate output levels, after selecting the desired profile?
Quote:
Pipewire is being used but... Jack-related utilities don't work -- at least jack_mixer doesn't so I can't confirm that there's even a connection to the system sound output like I could with jack+jack_mixer. Carla displays garbage (devices popping in and out of existence and connections to some device that don't even appear on the patch panel). Perhaps I read more into the claims about Pipewire providing all the functionality that Jack provided and it really doesn't. It's frustrating at best.
Yes, I can understand the frustration. For most desktop users, PipeWire works without them even being aware of what is operating under the hood. I doubt if PipeWire is the cause of the issue here. I know nothing about Carla, so can't offer any direct advice. A quick search shows numerous threads discussing issues with it, mostly around configuration.
Q: How do I remove Pipewire completely as a fall-back and allow me to revert back to the Jack+Pulseaudio configuration that was successfully used in my 15.3 setup? Some may Pipewire see as the future but, IMHO, it sure seems as though it ain't ready for prime time yet. (Heck, Pulseaudio's intro was less of a hassle than Pipewire's.)
Sorry to vent but Pipewire's about to give me an ulcer.
That is an incorrect assumption...this is an issue specific to your particular environment, and I suspect the the use of Carla.
You can reinstall PulseAudio with
Code:
sudo zypper in pulseaudio
Follow the prompts given (including the removal of wireplumber and pipewire-pulseaudio).
In addition to that, I have couple of scripts I use to see which outputs result in sound, one for when sound should be going out with the video to a display, the other for when going out the green pin jack to speakers. For the latter it's currently (and identical to the other except that omits this one's last 3 lines):
Those #^ lines are so when I save to disk I can readily use that space to indicate whether there was output and whether KMix was able to affect volume.
This I use to see most of what's installed that affects audio setup, and a bit extra:
Some day I hope to find out where the system hides whatever settings a DM uses to decide which device to use as default, as usually there are no less than about 6, and often more than twice that, even though most PCs have one physical analog output, and one (or two, or at most three) digital (HDMI and/or DisplayPort or both or two HDMI or two DisplayPort or two HDMI plus DisplayPort).
Distribution: openSUSE, Raspbian, Slackware. Previous: MacOS, Red Hat, Coherent, Consensys SVR4.2, Tru64, Solaris
Posts: 2,818
Original Poster
Rep:
Quote:
Originally Posted by ferrari
I know nothing about Carla, so can't offer any direct advice.
Never had any problems with it back in the Jack+Pulse days. I only launched it because jack_mixer doesn't work at all now and I had no simple means of seeing what was connected to what.
Follow the prompts given (including the removal of wireplumber and pipewire-pulseaudio).
You can remove PipeWire with
Code:
sudo zypper rm pipewire
Restart your desktop session once done.
Did that. Didn't help. In fact, I'm back to the blinking card messages again. [sigh] Playing audio using Audacious is now broken in that sound is interrupted frequently as though some gating effect has been introduced. No doubt related to the dueling sound card messages. I received an email from a user who solved what may be my problem by blacklisting the TU116 card. Sadly, that doesn't look promising.
How hard can it be to get Linux to see:
Code:
$ cat /proc/asound/cards
0 [PCH ]: HDA-Intel - HDA Intel PCH
HDA Intel PCH at 0xf7410000 irq 38
1 [NVidia ]: HDA-Intel - HDA NVidia
HDA NVidia at 0xf7080000 irq 17
2 [L313 ]: USB-Audio - Live Streamer CAM 313
Sunplus IT Co Live Streamer CAM 313 at usb-0000:00:14.0-2.2, high speed
and reliably allow the used of card 0 without the sound software getting confused by the existence of card 1.
I'm off to the ALSA project page to review the basics -- something's amiss.
Any hints on how to check/verify the lowest level of sound configuration?
Distribution: openSUSE, Raspbian, Slackware. Previous: MacOS, Red Hat, Coherent, Consensys SVR4.2, Tru64, Solaris
Posts: 2,818
Original Poster
Rep:
Quote:
Originally Posted by mrmazda
FWIW, when evaluating audio setup here, in addition to inxi -az, I run a script containing the following:
<snip>
Thanks... I'm knee-deep debugging a systemd problem at the moment. Soon I'll cut-n-paste your script and see what output I get.
Quote:
Some day I hope to find out where the system hides whatever settings a DM uses to decide which device to use as default, as usually there are no less than about 6, and often more than twice that, even though most PCs have one physical analog output, and one (or two, or at most three) digital (HDMI and/or DisplayPort or both or two HDMI or two DisplayPort or two HDMI plus DisplayPort).
That seems like something that would require getting a whole lot of separate development teams to agree upon a solution. I wouldn't hold my breath. I agree that desktop configuration is a mess. I've lost count of the number of times I've had something get corrupted and have had to reconfigure the desktop from scratch. Being to back it up and restore as need would be great.
UPDATE:
I ran msmazda'a scripts (with a little modification for the test sound file) and got the following in response (sorry but some of the output is quite long):
Code:
# alsactl info
./alsainfo: line 4: alsactl: command not found
# wpctl status
PipeWire 'pipewire-0' [1.0.5, rnturn@kadath.theturners.net, cookie:2684331307]
└─ Clients:
32. WirePlumber [1.0.5, rnturn@kadath.theturners.net, pid:2066]
40. WirePlumber [export] [1.0.5, rnturn@kadath.theturners.net, pid:2066]
45. xdg-desktop-portal [1.0.5, rnturn@kadath.theturners.net, pid:2233]
46. wpctl [1.0.5, rnturn@kadath.theturners.net, pid:4492]
Audio
├─ Devices:
│
├─ Sinks:
│
├─ Sources:
│
├─ Filters:
│
└─ Streams:
Video
├─ Devices:
│ 41. Live Streamer CAM 313 [v4l2]
│ 42. Live Streamer CAM 313 [v4l2]
│
├─ Sinks:
│
├─ Sources:
│ * 43. Live Streamer CAM 313 (V4L2)
│
├─ Filters:
│
└─ Streams:
Settings
└─ Default Configured Devices:
0. Audio/Sink alsa_output.pci-0000_00_1b.0.analog-stereo.99
# pw-cli list-objects Device
id 41, type PipeWire:Interface:Device/3
object.serial = "41"
factory.id = "14"
client.id = "40"
device.api = "v4l2"
device.description = "Live Streamer CAM 313"
device.name = "v4l2_device.pci-0000_00_14.0-usb-0_2.2_1.0"
media.class = "Video/Device"
id 42, type PipeWire:Interface:Device/3
object.serial = "42"
factory.id = "14"
client.id = "40"
device.api = "v4l2"
device.description = "Live Streamer CAM 313"
device.name = "v4l2_device.pci-0000_00_14.0-usb-0_2.2_1.0"
media.class = "Video/Device"
# pw-cli list-objects Node
id 29, type PipeWire:Interface:Node/3
object.serial = "29"
factory.id = "10"
priority.driver = "20000"
node.name = "Dummy-Driver"
id 30, type PipeWire:Interface:Node/3
object.serial = "30"
factory.id = "10"
priority.driver = "19000"
node.name = "Freewheel-Driver"
id 43, type PipeWire:Interface:Node/3
object.serial = "43"
object.path = "v4l2:/dev/video0"
factory.id = "10"
client.id = "40"
device.id = "41"
priority.session = "1000"
node.description = "Live Streamer CAM 313 (V4L2)"
node.name = "v4l2_input.pci-0000_00_14.0-usb-0_2.2_1.0"
node.nick = "Live Streamer CAM 313"
media.class = "Video/Source"
media.role = "Camera"
# aplay -lL
null
Discard all samples (playback) or generate zero samples (capture)
speexrate
Rate Converter Plugin Using Speex Resampler
jack
JACK Audio Connection Kit
pulse
PulseAudio Sound Server
upmix
Plugin for channel upmix (4,6,8)
default
Default ALSA Output (currently PulseAudio Sound Server)
sysdefault:CARD=PCH
HDA Intel PCH, ALC887-VD Analog
Default Audio Device
front:CARD=PCH,DEV=0
HDA Intel PCH, ALC887-VD Analog
Front output / input
surround21:CARD=PCH,DEV=0
HDA Intel PCH, ALC887-VD Analog
2.1 Surround output to Front and Subwoofer speakers
surround40:CARD=PCH,DEV=0
HDA Intel PCH, ALC887-VD Analog
4.0 Surround output to Front and Rear speakers
surround41:CARD=PCH,DEV=0
HDA Intel PCH, ALC887-VD Analog
4.1 Surround output to Front, Rear and Subwoofer speakers
surround50:CARD=PCH,DEV=0
HDA Intel PCH, ALC887-VD Analog
5.0 Surround output to Front, Center and Rear speakers
surround51:CARD=PCH,DEV=0
HDA Intel PCH, ALC887-VD Analog
5.1 Surround output to Front, Center, Rear and Subwoofer speakers
surround71:CARD=PCH,DEV=0
HDA Intel PCH, ALC887-VD Analog
7.1 Surround output to Front, Center, Side, Rear and Woofer speakers
hdmi:CARD=NVidia,DEV=0
HDA NVidia, ASUS VP278
HDMI Audio Output
hdmi:CARD=NVidia,DEV=1
HDA NVidia, ASUS VP278
HDMI Audio Output
hdmi:CARD=NVidia,DEV=2
HDA NVidia, HDMI 2
HDMI Audio Output
hdmi:CARD=NVidia,DEV=3
HDA NVidia, HDMI 3
HDMI Audio Output
**** List of PLAYBACK Hardware Devices ****
card 0: PCH [HDA Intel PCH], device 0: ALC887-VD Analog [ALC887-VD Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 1: NVidia [HDA NVidia], device 3: HDMI 0 [ASUS VP278]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 1: NVidia [HDA NVidia], device 7: HDMI 1 [ASUS VP278]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 1: NVidia [HDA NVidia], device 8: HDMI 2 [HDMI 2]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 1: NVidia [HDA NVidia], device 9: HDMI 3 [HDMI 3]
Subdevices: 1/1
Subdevice #0: subdevice #0
# systemctl -l --no-pager --global --user status pipewire.{service,socket} pipewire-pulse.{service,socket} wireplumber
● pipewire.service - PipeWire Multimedia Service
Loaded: loaded (/usr/lib/systemd/user/pipewire.service; enabled; preset: disabled)
Active: active (running) since Sun 2024-06-09 15:28:17 CDT; 4min 26s ago
TriggeredBy: ● pipewire.socket
Main PID: 2065 (pipewire)
Tasks: 3 (limit: 4915)
CPU: 26ms
CGroup: /user.slice/user-1000.slice/user@1000.service/session.slice/pipewire.service
└─2065 /usr/bin/pipewire
● pipewire.socket - PipeWire Multimedia System Sockets
Loaded: loaded (/usr/lib/systemd/user/pipewire.socket; enabled; preset: enabled)
Active: active (running) since Sun 2024-06-09 15:28:17 CDT; 4min 26s ago
Triggers: ● pipewire.service
Listen: /run/user/1000/pipewire-0 (Stream)
/run/user/1000/pipewire-0-manager (Stream)
CGroup: /user.slice/user-1000.slice/user@1000.service/app.slice/pipewire.socket
Unit pipewire-pulse.service could not be found.
Unit pipewire-pulse.socket could not be found.
● wireplumber.service - Multimedia Service Session Manager
Loaded: loaded (/usr/lib/systemd/user/wireplumber.service; enabled; preset: enabled)
Active: active (running) since Sun 2024-06-09 15:28:17 CDT; 4min 26s ago
Main PID: 2066 (wireplumber)
Tasks: 6 (limit: 4915)
CPU: 50ms
CGroup: /user.slice/user-1000.slice/user@1000.service/session.slice/wireplumber.service
└─2066 /usr/bin/wireplumber
The second script returned the following but with intermittent sound output. Previous runs of the script did result in some sound output to the HDMI port but that was when I'd disabled the onboard sound chop in the BIOS. With that enabled, the script produces either sound to the HDMI, distorted sound (again HDMI only), or no sound at all. Anyway... one run's output:
Code:
./soundtest
# aplay /home/rnturn/Data/share/sounds/GONG.WAV
Playing WAVE '/home/rnturn/Data/share/sounds/GONG.WAV' : Unsigned 8 bit, Rate 11025 Hz, Mono
#^
# aplay -D default /home/rnturn/Data/share/sounds/GONG.WAV && sleep 5
Playing WAVE '/home/rnturn/Data/share/sounds/GONG.WAV' : Unsigned 8 bit, Rate 11025 Hz, Mono
#^
# aplay -D hdmi /home/rnturn/Data/share/sounds/GONG.WAV
aplay: main:834: audio open error: No such file or directory
#^
# aplay -D hdmi:0,0 /home/rnturn/Data/share/sounds/GONG.WAV
aplay: main:834: audio open error: No such file or directory
#^
# aplay -D hdmi:0,1 /home/rnturn/Data/share/sounds/GONG.WAV
aplay: main:834: audio open error: No such file or directory
#^
# aplay -D hw:0,3 /home/rnturn/Data/share/sounds/GONG.WAV
aplay: main:834: audio open error: No such file or directory
#^
# aplay -D hw:0,7 /home/rnturn/Data/share/sounds/GONG.WAV
aplay: main:834: audio open error: No such file or directory
#^
# aplay -D plughw /home/rnturn/Data/share/sounds/GONG.WAV
Playing WAVE '/home/rnturn/Data/share/sounds/GONG.WAV' : Unsigned 8 bit, Rate 11025 Hz, Mono
#^
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
Pipewire on openSUSE is not working -- no sound at all
