From: Benji F. <fr...@so...> - 2007-07-25 22:09:35
|
On 7/25/07, Pieter Palmers <pi...@jo...> wrote: > Remove everything you have compiled and installed from source, and > reinstall the ubuntu provided system packages. Then upgrade libfreebob > to the debug version using the package available here: > > http://subversion.ffado.org/index.fcgi/attachment/wiki/DevelopmentReleases/libfreebob0_1.0.3-dbg-1_i386.deb > > This will install a libfreebob version with verbose debugging enabled. > > Capture & post the output of jack started with the freebob backend. I reverted everything back to the stock Kubuntu packages, and then replaced libfreebob with the one in the link you provided (thanks!). Before installing debug version: -rw-r--r-- 1 root root 360K 2006-11-28 09:23 libfreebob.so.0.1.0 After installing debug version: -rw-r--r-- 1 root root 393K 2007-05-10 05:53 libfreebob.so.0.1.0 Initially, I got the same output as before: ------------------------------------------------------------ $ jackd -d freebob jackd 0.102.20 Copyright 2001-2005 Paul Davis and others. jackd comes with ABSOLUTELY NO WARRANTY This is free software, and you are welcome to redistribute it under certain conditions; see the file COPYING for details JACK compiled with System V SHM support. loading driver .. Freebob using Firewire port 0, node -1 Root node has no children! Root node has no children! FreeBoB ERR: FREEBOB: Error creating virtual device cannot load driver module freebob no message buffer overruns ------------------------------------------------------------ After following a few dead ends, I ran out of alternative ideas, and rebooted the machine. Then, on the first attempt, I got this: ------------------------------------------------------------ $ jackd -d freebob jackd 0.102.20 Copyright 2001-2005 Paul Davis and others. jackd comes with ABSOLUTELY NO WARRANTY This is free software, and you are welcome to redistribute it under certain conditions; see the file COPYING for details JACK compiled with System V SHM support. loading driver .. Freebob using Firewire port 0, node -1 FREEBOB MSG: freebob_streaming.c:100 (freebob_streaming_init): FreeBoB Streaming Device Init FREEBOB MSG: freebob_streaming.c:101 (freebob_streaming_init): Using FreeBoB lib version libfreebob 1.0.3 FREEBOB MSG: freebob_streaming.c:102 (freebob_streaming_init): Device information: FREEBOB MSG: freebob_streaming.c:104 (freebob_streaming_init): Device options: FREEBOB MSG: freebob_streaming.c:106 (freebob_streaming_init): Port : 0 FREEBOB MSG: freebob_streaming.c:107 (freebob_streaming_init): Device Node Id : -1 FREEBOB MSG: freebob_streaming.c:108 (freebob_streaming_init): Samplerate : 48000 FREEBOB MSG: freebob_streaming.c:109 (freebob_streaming_init): Period Size : 1024 FREEBOB MSG: freebob_streaming.c:110 (freebob_streaming_init): Nb Buffers : 3 FREEBOB MSG: freebob_streaming.c:111 (freebob_streaming_init): Directions : 0 DEBUG freebob_streaming.c:168 (freebob_streaming_init): port = 0, devices_on_bus = 0 Root node has no children! Root node has no children! FreeBoB ERR: FREEBOB: Error creating virtual device cannot load driver module freebob Segmentation fault (core dumped) ------------------------------------------------------------ All subsequent attempts produced the same non-verbose output as before (even after unplugging the Ozonic, unloading all ieee1394-related modules, reloading them, and plugging the Ozonic back in, with or without using gscanbus to force a bus reset). The segfault also happens only the first time. This seems rather odd to me. Is this indicative of a deeper problem with my firewire configuration? Regardless of what is causing the lack of verbose output on subsequent jackd startups, it looks to me as if FreeBoB is either (A) not seeing the Ozonic at all or (B) not recognizing the Ozonic as a BeBoB device. Any suggestions on how to narrow it down to A or B? If possible, I'd like to work with a version of FreeBoB built from a local source tree, so I can more easily make slight changes (and drop in extra debug messages) in an attempt to get a better idea of what's going on here. Is the "debug version" in the .deb just the standard 1.0.3 release built with --enable-debug, or is there more to it? Thanks again for your time, |) |)enji |