Ticket #304 (closed defect: invalid)

Opened 4 years ago

Last modified 4 years ago

loading both module-alsa-{sink,source} fails

Reported by: zdeqb Owned by: lennart
Milestone: Component: module-alsa-*
Keywords: Cc:

Description

If I try to load both module-alsa-sink and module-alsa-source, whichever one is latter in the default2.pa file fails with a 'device or resource busy' message

But, If I comment one of the modules, the other will load without problems.

I don't know if this is an alsa, or pulseaudio bug, but I thought I'd try my luck here first...

I ran pulseaudio with: pulseaudio -nF .pulse/default2.pa

default2.pa contains the following:

#!/usr/bin/pulseaudio -nF

load-module module-alsa-sink
load-module module-alsa-source

load-module module-native-protocol-tcp auth-anonymous=1 port=4777
#load-module module-zeroconf-publish

This is on a thinkpad 760el (w/ snd-es1688) running debian unstable/testing, with pulseaudo 0.9.10.

pulseaudio output:

[zdeqb@favonius:~]$ pulseaudio -nF .pulse/default2.pa -vv
I: main.c: Called SUID root and real-time/high-priority scheduling was requested in the configuration. However, we lack the necessary priviliges:
I: main.c: We are not in group 'pulse-rt' and PolicyKit refuse to grant us priviliges. Dropping SUID again.
I: main.c: For enabling real-time scheduling please acquire the appropriate PolicyKit priviliges, or become a member of 'pulse-rt', 
or increase the RLIMIT_NICE/RLIMIT_RTPRIO resource limits for this user.
I: main.c: Note that real-time/high-priority scheduling is NOT normally required. If you experience crackling or other sound anomali
es, consider one or more of the above solutions.
I: main.c: High-priority scheduling enabled in configuration but now allowed by policy. Disabling forcibly.
W: main.c: setrlimit(RLIMIT_NICE, (31, 31)) failed: Operation not permitted
W: main.c: setrlimit(RLIMIT_RTPRIO, (9, 9)) failed: Operation not permitted
I: main.c: This is PulseAudio 0.9.10
I: main.c: Page size is 4096 bytes
I: main.c: Dude, your kernel stinks! The chef's recommendation today is Linux with high-resolution timers enabled!
W: alsa-util.c: Device default doesn't support 44100 Hz, changed to 44191 Hz.
I: module-alsa-sink.c: Successfully opened device default.
I: module-alsa-sink.c: Successfully enabled mmap() mode.
I: alsa-util.c: Successfully attached to mixer 'default'
I: alsa-util.c: Using mixer control "Master".
I: sink.c: Created sink 0 "alsa_output.default" with sample spec "s16le 2ch 44100Hz"
I: source.c: Created source 0 "alsa_output.default.monitor" with sample spec "s16le 2ch 44100Hz"
I: module-alsa-sink.c: Using 4 fragments of size 4408 bytes.
I: alsa-util.c: All 2 channels can be mapped to mixer channels. Using hardware volume control.
D: module-alsa-sink.c: Thread starting up
D: rtpoll.c: Acquired POSIX realtime signal SIGRTMIN+29
I: module-alsa-sink.c: Starting playback.
I: module.c: Loaded "module-alsa-sink" (index: #0; argument: "").
E: alsa-util.c: Error opening PCM device default: Device or resource busy
E: module.c: Failed to load  module "module-alsa-source" (argument: ""): initialization failed.
E: main.c: Module load failed.
E: main.c: Failed to initialize daemon.
I: module.c: Unloading "module-alsa-sink" (index: #0).
D: module-alsa-sink.c: Thread shutting down
I: sink.c: Freeing sink 0 "alsa_output.default"
I: source.c: Freeing source 0 "alsa_output.default.monitor"
I: module.c: Unloaded "module-alsa-sink" (index: #0).
I: main.c: Daemon terminated.

Change History

  Changed 4 years ago by lennart

Hmm, maybe your device only suports simplex audio? i.e. only either recording or playback is supported, not both at the same time?

in reply to: ↑ 1comment   Changed 4 years ago by zdeqb

  • status changed from new to closed
  • resolution set to invalid

That never occured to me...

Google also says it supports only simplex audio... I guess I ought to get a newer computer...

Anyway, thanks, and I guess this ticket can be closed... :-)

Note: See TracTickets for help on using tickets.