[alsa-devel] [RFC][PATCH 00/13] bebob: a new driver for BridgeCo BeBoB based device

Daniel Wagner wagi at monom.org
Thu Dec 5 22:08:47 CET 2013

Hi Takashi,

On 12/01/2013 05:42 AM, Takashi Sakamoto wrote:
> Hi Daniel,
> Thanks for your testing.

No problem.

> At first, I describe our system to test. I use Ubuntu 13.10. You use
> Fedora 19.

Be aware I have a lot of own build libraries flying around (e.g.
libiec61883, libraw1394, ...)

> (Dec 01 2013 02:55), Daniel Wagner wrote:
>> I have tried this series (incl. the bug fix you recommend) on a FA-66.
>> While I see some output in alsa-info, pulseaudio didn't pick it up. I
>> also noted that some logs in the dmesg. I am not sure what is supposed
>> to work already or not.
>> Here are my logs
>> http://www.monom.org/misc/alsa-firewire/2013-11-30
> 1.pulseaudio
> PulseAudio can automatically load 'module-alsa-card' with
> 'module-udev-detect' (utilizing sysfs/dbus). But for snd-bebob, this
> mecanism doesn't work because PulseAudio cannot decide profiles for the
> card even if success to detect.
> For this problem, I have a need to commit some codes for PulseAudio but
> this may be my future work.
> Well, when I test with PulseAudio, I always directly load
> 'module-alsa-sink' or 'module-alsa-source' by these lines:
> $ pactl load-module module-alsa-sink device=hw:X,X
> $ pactl load-module module-alsa-source device=hw:X,X

I got the FA-66 now working (playback) with explicit loading of the

> 2.dmesg
> Hm. I want to know which asynchronous transaction is failed.
> [  446.796563] snd-bebob fw1.0: transaction failed: no ack
> [  446.838567] snd-bebob fw1.0: transaction failed: no ack

I was not able to reproduce this so far. Note that I a have crapy
firewire card. So that might just be the main reason why we
see these.

> Would you investigate which transactions cannot get 'no ack'?

I have uploaded some two logs. The first one is for the fa-66
(fw-fa66.txt) and the second one is for the Audio5 (fw-a5.txt).

There seems to be an issue with the Audio5, though I haven't
looked into it yet (quite busy, sorry) For that device I
even got a serial console to it) Maybe you see the problem
already from the log.



More information about the Alsa-devel mailing list