0

ALSA woke us up to write new data to the device, but there was actually nothing

Hello
Im using the DAC+ on my raspberry pi 2 with arch linux.
uname -a
Linux rapi3 4.1.6-2-ARCH #1 SMP PREEMPT Sat Aug 22 12:18:37 MDT 2015 armv7l GNU/Linux



tail /boot/config.txt
dtoverlay=hifiberry-dacplus



within my journal control I see:
journalctl _PID=292 -b
Aug 28 12:40:22 rapi3 pulseaudio[292]: [pulseaudio] server-lookup.c: Unable to contact D-Bus: org.freedesktop.DBus.Error.NotSupported: Unable to autolaunch a dbus-daemon without a $DISPLAY for X11
Aug 28 12:40:22 rapi3 pulseaudio[292]: [pulseaudio] main.c: Unable to contact D-Bus: org.freedesktop.DBus.Error.NotSupported: Unable to autolaunch a dbus-daemon without a $DISPLAY for X11
Aug 28 12:40:23 rapi3 pulseaudio[292]: [alsa-sink-HiFiBerry DAC+ HiFi pcm512x-hifi-0] alsa-sink.c: ALSA woke us up to write new data to the device, but there was actually nothing to write!
Aug 28 12:40:23 rapi3 pulseaudio[292]: [alsa-sink-HiFiBerry DAC+ HiFi pcm512x-hifi-0] alsa-sink.c: Most likely this is a bug in the ALSA driver 'snd_soc_hifiberry_dacplus'. Please report this issue to the ALSA developers.
Aug 28 12:40:23 rapi3 pulseaudio[292]: [alsa-sink-HiFiBerry DAC+ HiFi pcm512x-hifi-0] alsa-sink.c: We were woken up with POLLOUT set -- however a subsequent snd_pcm_avail() returned 0 or another value < min_avail.



In the end the hifiberry is working, however I think I should not see this message.

Cheers

3 comments

Please sign in to leave a comment.