[pulseaudio-discuss] How to launch pulseaudio on embedded system
Tanu Kaskinen
tanu.kaskinen at linux.intel.com
Tue Sep 2 03:35:16 PDT 2014
On Tue, 2014-09-02 at 11:24 +0200, DIEHCO R&D wrote:
> Le 02/09/2014 10:57, Tanu Kaskinen a écrit :
> >>>> (...)
> >>>> I: [pulseaudio] module-udev-detect.c: Found 0 cards.
> >>> The debug logs before this line should tell why there weren't any sound
> >>> cards found.
> >> module-udev-detect.so found. I don't see if there is problem in log below.
> > Ok, so according to udev there are no sound devices. What does "ls
> > -l /dev/snd" print?
> >
> root at eukrea-cpuimx25:~# ls -l /dev/snd
> crw-rw---- 1 root root 116, 0 Sep 2 09:13 controlC0
> crw-rw---- 1 root root 116, 24 Sep 2 09:13 pcmC0D0c
> crw-rw---- 1 root root 116, 16 Sep 2 09:13 pcmC0D0p
> crw-rw---- 1 root root 116, 1 Sep 2 09:13 seq
> crw-rw---- 1 root root 116, 33 Sep 2 09:13 timer
Hmm, pulseaudio probably can't use these devices, because they are
accessible only to root and pulseaudio runs under the "pulse" user, so
modifying the access rights is required, but I think the log indicates
that pulseaudio doesn't even try, because according to udev there are no
sound cards.
What does "udevadm info /dev/snd/controlC0" print?
> and see attached the "pulseaudio --system -vvvv &" and "pactl list
> cards" outputs with the lines:
> W: [pulseaudio] protocol-native.c: Denied access to client with invalid
> authorization data.
> Connection failure: Access denied
Add the user to the "pulse-access" group, or pass "auth-anonymous=true"
to module-native-protocol-unix in /etc/pulse/system.pa to allow any user
to access the server.
--
Tanu
More information about the pulseaudio-discuss
mailing list