[pulseaudio-discuss] pulseaudio 0.9.8 still unhappy with ALSA (for different reasons?)
Lennart Poettering
lennart at poettering.net
Sun Nov 25 09:51:55 PST 2007
On Fri, 23.11.07 00:00, Nix (nix at esperi.org.uk) wrote:
> The error from ALSA has changed but is still, well... an error:
>
> nix at hades 90 /home/nix% /usr/bin/pulseaudio -vv --daemonize=no
> pulseaudio: modules/module-alsa-sink.c:177: mmap_write: Assertion `(areas[0].step >> 3) == u->frame_size' failed.
> Aborted
Hmm. This doesn*t look good. What kind of device is this? This is
really a strange error.
> I get some syslog output at the same time:
>
> main.c: PolicyKit grants us acquire-high-priority privilige.
> main.c: We're in the group 'realtime', allowing real-time and high-priority scheduling.
> core-util.c: Successfully gained nice level -11.
> main.c: setrlimit(RLIMIT_NICE, (31, 31)) failed: Operation not permitted
> main.c: setrlimit(RLIMIT_RTPRIO, (9, 9)) failed: Operation not permitted
> main.c: Page size is 4096 bytes
> main.c: Dude, your kernel stinks! The chef's recommendation today is Linux with high-resolution timers enabled!
> module-alsa-sink.c: Successfully opened device hw:0.
> module-alsa-sink.c: Successfully enabled mmap() mode.
> alsa-util.c: Successfully attached to mixer 'hw:0'
> alsa-util.c: Using mixer control "Master".
> sink.c: Created sink 0 "alsa_output.hw_0" with sample spec "s16le 2ch 44100Hz"
> source.c: Created source 0 "alsa_output.hw_0.monitor" with sample spec "s16le 2ch 44100Hz"
> module-alsa-sink.c: Using 4 fragments of size 4408 bytes.
> alsa-util.c: All 2 channels can be mapped to mixer channels. Using hardware volume control.
>
> (The EPERM errors are my fault, I think: a PAM config bug, perhaps,
> although it's not obvious. The hires timer thing remains undiagnosed so
> far.)
The hrtimer warning just tells you to get a better kernel with
hrtimers enabled. That's all. PA works fine without them, but it's
recommended to have them.
> Using plughw:0 fails for other reasons, visible only if alsa-lib is
> compiled without --disable-debug and pulseaudio is started with --enable-daemonize=no:
>
> ALSA lib control.c:909:(snd_ctl_open_noupdate) Invalid CTL plughw:0
> ALSA lib control.c:909:(snd_ctl_open_noupdate) Invalid CTL plughw:0
>
> So I suspect plughw:0 simply doesn't exist, or something (whatever it
> is).
This is not an error. PA tries to find a suitable mixer device for
your PCM. First it tries "plughw:0" and then it falls back to
"hw:0". ALSA likes to be quite verbose on this. It shouldn't
be. Complain to ALSA.
> When it boots successfully (using a hardwired OSS), I get some rather
> strange log messages:
>
> Nov 22 22:47:51 hades err: pulseaudio[6242]: socket-server.c: socket(PF_INET6): Address family not supported by protocol
> Nov 22 22:47:51 hades err: pulseaudio[6242]: socket-server.c: socket(PF_INET6): Address family not supported by protocol
> Nov 22 22:47:51 hades err: pulseaudio[6242]: socket-server.c: socket(PF_INET6): Address family not supported by protocol
> Nov 22 22:47:51 hades err: pulseaudio[6242]: socket-server.c:
> socket(PF_INET6): Address family not supported by protocol
A kernel without IPV6? So we are living in the early nineties now?
> Nov 22 22:47:51 hades err: pulseaudio[6242]: socket-server.c: bind(): Address already in use
> Nov 22 22:47:51 hades err: pulseaudio[6242]: module.c: Failed to load module "module-native-protocol-tcp" (argument: "auth-anonymous=1"): initialization failed.
> Nov 22 22:47:51 hades err: pulseaudio[6242]: module-gconf.c: pa_module_load() failed
> Nov 22 22:47:51 hades err: pulseaudio[6242]: socket-server.c: socket(PF_INET6): Address family not supported by protocol
> Nov 22 22:47:51 hades err: pulseaudio[6242]: socket-server.c: bind(): Address already in use
> Nov 22 22:47:51 hades err: pulseaudio[6242]: module.c: Failed to load module "module-esound-protocol-tcp" (argument: "auth-anonymous=1"): initialization failed.
> Nov 22 22:47:51 hades err: pulseaudio[6242]: module-gconf.c: pa_module_load() failed
> Nov 22 22:47:51 hades err: pulseaudio[6242]: module.c: Module "module-zeroconf-publish" should be loaded once at most. Refusing to load.
> Nov 22 22:47:51 hades err: pulseaudio[6242]: module-gconf.c: pa_module_load() failed
>
> It's almost as if it's reading the config file twice or something.
Is it possible that you activated the network modules in GConf via
paprefs and are loading them at the same time from the config file?
The comments in default.pa explicitly warn you about this.
Lennart
--
Lennart Poettering Red Hat, Inc.
lennart [at] poettering [dot] net ICQ# 11060553
http://0pointer.net/lennart/ GnuPG 0x1A015CC4
More information about the pulseaudio-discuss
mailing list