I’m a new-comer to Void Linux, and I am impressed with what I see over-all. XBPS is lightning fast compared to DPKG managers, and yet doesn’t skimp on the functionality. I decided to install Void w/out any desktop environment, primarily because I’m tired of all the bloat, and decided to just go with ROX-Filer and iceWM. I was even surprised that wifi worked with minimal assistance from me. Great work and many thanks for your effort!
Everything is working great on my System76 Galago laptop from 2015, with one exception: sound. After spending the last three days looking through forum posts both on Void and on StackExchange sites, I’m turning up blank. No matter what I do, I attempt to execute the following command:
# as root user aplay --file-type wav /usr/share/sounds/alsa/Front_Center.wav
and I get back the same results:
ALSA lib pcm_dmix.c:1099:(snd_pcm_dmix_open) unable to open slave aplay: main:828: audio open error: No such file or directory
ALSA appears to properly recognize the hardware provided by the laptop. It has two cards: card 0 contains five HDMI controls, while card 1 contains what appears to be your traditional sound card devices (PCM output, Mic input, et. al.).
alsamixer allows me to select between these two cards (default is 0) and make changes to the settings. These settings do persist between runs of
alsamixer, so I’m confident that it must be talking to hardware at some point.
Nonetheless, even with all controls set to maximum, I do not receive any audio.
After some digging around, I also discovered problems getting PulseAudio running. This may be related, but I cannot be sure:
# as root user cd /etc/sv/pulseaudio ./run
This results in the following diagnostic output:
W: [pulseaudio] main.c: Running in system mode, but --disallow-exit not set. W: [pulseaudio] main.c: Running in system mode, but --disallow-module-loading not set. N: [pulseaudio] main.c: Running in system mode, forcibly disabling SHM mode. N: [pulseaudio] main.c: Running in system mode, forcibly disabling exit idle time. W: [pulseaudio] main.c: OK, so you are running PA in system mode. Please make sure that you actually do want to do that. W: [pulseaudio] main.c: Please read http://www.freedesktop.org/wiki/Software/PulseAudio/Documentation/User/WhatIsWrongWithSystemWide/ for an explanation why system mode is usually a bad idea. W: [pulseaudio] main.c: Unable to contact D-Bus: org.freedesktop.DBus.Error.NoServer: Failed to connect to socket /run/dbus/system_bus_socket: Connection refused
I have confirmed the existence of the socket, and indeed, that dbus is running:
[root@fomalhaut pulseaudio]# ls -la /run/dbus total 0 drwxr-xr-x 2 dbus dbus 60 Apr 11 22:31 . drwxr-xr-x 18 root root 500 Apr 11 22:31 .. srwxrwxrwx 1 root root 0 Apr 11 22:31 system_bus_socket [root@fomalhaut pulseaudio]# ps awfux | grep dbus root 8051 0.0 0.0 10888 2328 pts/0 S+ 22:51 0:00 | | | \_ grep dbus kc5tja 7119 0.0 0.0 22692 248 ? S 22:23 0:00 dbus-launch --autolaunch 712ecc0bb918c563752fe17c5acc41a3 --binary-syntax --close-stderr kc5tja 7120 0.0 0.0 13352 176 ? Ss 22:23 0:00 /usr/bin/dbus-daemon --syslog-only --fork --print-pid 5 --print-address 7 --session
Permissions all look correct to me. Both root and my normal user are in the audio group.
alsamixer properly recognizes the hardware my laptop provides, and if I mute or unmute the mic input, I hear gentle clicks on the speakers, so I know something is talking to the hardware.
I genuinely believe that there are several issues afoot here, but I can’t even begin to know where to look next. If I can receive additional guidance on where to look next, I would be grateful indeed.
Thank you for your time.