[SOLVED] alsa-*-1.1.9 upgrade, pulse device configuration limited

Hello everyone;

Hope you all having a nice weekend, I would appreciate any help in solving my issue.

I am on current with multilib installed, system was last updated on May 16/2019. I use slackpkg to update:

slackpkg update; slackpkg upgrade-all slackpkg install multilib

I have the following audio devices in my box:

root@yafa:~# lspci | grep -i audio 00:1b.0 Audio device: Intel Corporation C600/X79 series chipset High Definition Audio Controller (rev 05) 05:00.1 Audio device: NVIDIA Corporation GF110 High Definition Audio Controller (rev a1) 09:04.0 Multimedia audio controller: Creative Labs EMU10k1X [SB Live! Value/OEM Series]

I use the Sound Blaster card as my primary device, with 4 speakers and a subwoofer connection. To achieve that I change its profile to "Analog Surround 4.1 Output" see pictures

With the latest alsa update, I have not been able to change the setting on this device using pavucontrol gui! When I try to change the setting the device disappears from the application list! The following is left in /var/log/syslog:

May 18 11:59:23 yafa pulseaudio[1937]: [pulseaudio] socket-server.c: bind(): Address already in use May 18 11:59:23 yafa pulseaudio[1937]: [pulseaudio] module.c: Failed to load module "module-esound-protocol-unix" (argument: ""): initialization failed. May 18 11:59:24 yafa pulseaudio[1937]: [pulseaudio] bluez5-util.c: GetManagedObjects() failed: org.freedesktop.DBus.Error.ServiceUnknown: The name org.bluez was not provided by any .service files May 18 12:02:09 yafa pulseaudio[1937]: [alsa-sink-emu10k1x] alsa-sink.c: snd_pcm_writei: Device or resource busy May 18 12:02:09 yafa pulseaudio[1937]: [pulseaudio] protocol-native.c: protocol error, kicking client

BTW there is no bluetooth device in this system.
tried:
*) removed and then reinstalled pulseaudio-12.2-x86_64-1
*) deleted $HOME/.config/pulse/ and /root/.config/pulse/
both actions did not help. So I reverted to earlier alsa*

Again I appreciate any help and thank you.

Wael H.

It seems I can not include the pictures! They show pavucontrol gui configuration PAGE and output devices where user sets volume for individual speaker

Wael H.

Hello everyone;

There is this thread, so I have rebuilt pulseaudio package version 12.2 by using slackware source slack script replacing source tar ball from its git source here. The result I was
able to set ALL device configuration without the device disappearing from pulseaudio device list. That was great, but ...

I have three audio devices:

root@yafa:~# lspci | grep -i audio 00:1b.0 Audio device: Intel Corporation C600/X79 series chipset High Definition Audio Controller (rev 05) 05:00.1 Audio device: NVIDIA Corporation GF110 High Definition Audio Controller (rev a1) 09:04.0 Multimedia audio controller: Creative Labs EMU10k1X [SB Live! Value/OEM Series]

I did NOT test NVIDIA HDA device!
Changing the volume for Intel (onboard audio) was okay, worked normally.
However changing the volume for Sound Blaster Live on any control broke the sound for few seconds and produced logged messages in /var/syslog file:

May 19 14:35:41 yafa pulseaudio[1483]: [pulseaudio] pid.c: Daemon already running. May 19 14:35:41 yafa pulseaudio[1440]: [alsa-sink-emu10k1x] alsa-sink.c: snd_pcm_mmap_commit: Device or resource busy, trying to restart PCM May 19 14:39:16 yafa pulseaudio[1440]: [alsa-sink-emu10k1x] alsa-sink.c: snd_pcm_mmap_commit: Device or resource busy, trying to restart PCM May 19 14:40:20 yafa last message repeated 3 times May 19 14:41:29 yafa last message repeated 13 times May 19 14:41:38 yafa last message repeated 149 times May 19 14:42:06 yafa chrome[1635]: [1635:1635:0519/144206.673632:ERROR:browser_dm_token_storage_linux.cc(101)] Error: /etc/machine-id contains 0 characters (32 were expected). May 19 14:44:19 yafa pulseaudio[1440]: [alsa-sink-emu10k1x] alsa-sink.c: snd_pcm_mmap_commit: Device or resource busy, trying to restart PCM May 19 14:44:19 yafa last message repeated 3 times

It maybe wrong to mark this as solved, I gave up!

Wael H.

If you don't use the Intel sound chip onboard your nvidia card, the easy solution is to blacklist it. If you do use it, then I suspect it will be necessary to omit any specific ALSA calls such as with an "`/.asoundrc" file. Simply renaming that file should put PA back in control. It doesn't "play nice with others".