From: Stefan R. <st...@s5...> - 2010-08-26 12:27:53
|
Nils Philippsen wrote: > On Tue, 2010-08-24 at 17:43 -0300, Luis Pablo Gasparotto wrote: >> 02465276232: (ffado.cpp)[ 92] ffado_streaming_init: libffado 2.999.0-1881 built Aug 23 2010 02:19:42 >> 02470580344: Error (configrom.cpp)[ 150] initialize: Could not parse config rom of node 0 on port 0 >> 02475836333: Error (configrom.cpp)[ 150] initialize: Could not parse config rom of node 0 on port 0 >> firewire ERR: Error creating FFADO streaming device >> cannot load driver module firewire >> no message buffer overruns > > I'm not sure about these (then again, I don't know much about ffado > internals), but have you tried a current kernel with the juju firewire > stack so that you can compare against it? I find it strange that "ffado-test ListDevices" was able to identify the Alesis device (which means, it was able to parse its "config rom") whereas ffado-dbus-server and jackd -dfirewire were both unable to do that. Luis, I suggest you first re-run jackd -dfirewire, but now with -v3 or -v6 appended to the command line to increase the verbosity of libffado. The dear FFADO developers chose to hide a few rather essential failure messages in higher verbosity levels. :-/ PS, since you are operating this apparently on a 4-pin FireWire port, which does not provide bus power, I guess you are powering the audio device with a dedicated PSU as required, right? -- Stefan Richter -=====-==-=- =--- ==-=- http://arcgraph.de/sr/ |