presonus firebox + freebob problems

cteampride · 2010-01-10 05:44:11

everyone is probably thinking "whats new?" at this point... yes i have read many many frustrated posts on freebob/ffado and the new firewire driver stack (http://bbs.archlinux.org/viewtopic.php?pid=680851)

I have installed all dependencies for freebob. I compiled jackd after i installed freebob. all seemed to go smoothly.

I even get the blue sync light on my firebox when i run

jackd -d freebob

- but here's the catch: even if i have a good sync, so it seems, and i connect my firebox correctly within qjackctl, it fails to produce any sound output to the computer, nothing, nada, not even the headphone out on the box works (and it does output sound through the headphone jack when the firebox is not synced... furthermore it works fine in windows. def not the box).

Under the "connections tab" in qjackctl i see the firebox is up and running and synced, all 6 captures are visable. I can connect these with the system as expected... but a quick listen to the headphones or upon opening ardour is is aparent that something has gone horribly wrong.

furthermore since i get a blue sync light when i run jackd -d freebob i would think that running qjackctl first with freebob selected as the driver would work fine, sync the firebox, ect... but NO. qjackclt outputs this error:

17:35:47.277 Startup script...
17:35:47.277 artsshell -q terminate
sh: artsshell: command not found
17:35:47.681 Startup script terminated with exit status=32512.
17:35:47.681 JACK is starting...
17:35:47.681 /usr/bin/jackd -R -P70 -dfreebob -dhw:0 -r44100 -p32 -n8 -D
17:35:47.683 JACK was started with PID=1977.
jackd 0.116.2
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 ..
can't load "/usr/lib/jack/jack_freebob.so": libiec61883.so.0: failed to map segment from shared object: Resource temporarily unavailable
cannot load driver module freebob
17:35:47.920 JACK was stopped successfully.
17:35:47.921 Post-shutdown script...
17:35:47.921 killall jackd
jackd: no process found
17:35:48.340 Post-shutdown script terminated with exit status=256.
17:35:49.872 Could not connect to JACK server as client. - Overall operation failed. - Unable to connect to server. Please check the messages window for more info.

i belive this strange behavior is caused by the new 1394 stack implimented recently...

modprobe raw1394

returns fatal error...doesnt exist... so the new stack containing firewire_core and firewire_ohci may be to blame. My question: should i remove these and get the old stuff back (ieee1394, ohci1394, raw1394)? and how do i go about doing this?
Or does this have to do with the error i get pertaining to libiec61883?

since i am a relative noob to linux, and a total noob to arch i was wondering if anyone can chime in on this, or if its more of just a wait and pray for better drivers deal...

CedricR · 2010-01-12 16:20:18

I am in the same situation, I cannot launch raw1394 module to use this one with ffado.

cteampride · 2010-01-12 23:48:43

I think the only solution for now lies here:

Old drivers installed as fallback if the new ones are insufficient
To provide a seemless migration from the old to the new drivers, it is possible to build and install the new and the old drivers together. However, care needs to be taken to keep in control which drivers are loaded. I.e. create proper blacklist entries in /etc/modprobe.conf as explained below to avoid auto-loading of the wrong drivers. Also, you need to upgrade your userland to libraw1394 v2 if you want to switch to the new drivers (or freely between old and new drivers).
If you are having trouble with the new drivers, do not hesitate to get in touch via the Mailinglists.
Note, don't use the new drivers in Linux kernel versions older than 2.6.27.5. They are too buggy.

from: http://ieee1394.wiki.kernel.org/index.p … _Migration

looks like we need to rebuild the kernel with the old and new mods, or possibly revert to an outdated one . Yeah there is no way for me to switch between them with modprobe... and hours or fiddling with jackd and freebob yeilded no result. Only a blue light to show for it.

during this transition period i think both the old and new stack should be included in the instillation, but i guess that would go against the arch way of keeping it simple.... would have avoided many headaches.

but in other news: got crossover and steam working well together (tf2 ftww!!!)

*edit
I suppose we could build the old modules (i guess not in the kernel but in the userspace, is that terminology correct?)

http://bbs.archlinux.org/viewtopic.php? … 15#p687215
has details.

looks like we need pacman -S kernel26-headers
but idk where to go from there

cheers

Last edited by cteampride (2010-01-13 01:10:45)

Intrepid · 2010-01-19 05:29:03

Ah yes. I'm sorry I posted on some other topic. I would also be interested in figuring this out, but unfortunately I don't know exactly the name of the drivers I need. I think in that same article you posted, the answer lies in one of these lines:

How to suppress auto-loading
To avoid confusion, it is recommended that either the old or the new driver stack is built, but not both together. It is nevertheless possible to build and install both stacks together. If you chose to do so, you may want to add lines like:
# blacklist firewire-ohci
# blacklist firewire-sbp2
# blacklist firewire-net

blacklist ohci1394
blacklist sbp2
blacklist eth1394
blacklist dv1394
blacklist raw1394
blacklist video1394

to /etc/modprobe.d/file_of_your_choice or /etc/modprobe.conf to suppress auto-loading of one of the stacks.
Extremely old modutils which do not support the blacklist keyword can be instructed by configuration entries like "install module /bin/true" to suppress loading of a particular module.

So those module names are involved in the firewire process. The question is, which one should be loaded? I will experiment with that myself to see if I can somehow get the old firewire drivers.

Intrepid · 2010-01-20 05:20:33

Alright. So I'm sort of confused. It seems to be improved over before as far as errors, BUT it still doesn't work. I compiled the latest git kernel with the old firewire stack included. Seems like it has nothing to do with it. The errors change, but I'm still getting errors. How frustrating! I'm going to revert to mainline and hope some dev comes up with a true fix. As far as I know, it worked in kernel 2.6.31-r6 so maybe that's the answer for now.

Here's the most prominent error:

Error (configrom.cpp)[ 150] initialize: Could not parse config rom of node 0 on port 0

Last edited by Intrepid (2010-01-20 05:34:55)

cteampride · 2010-01-20 23:30:09

very unfortunate. I will continue to look into a (more elegant) fix.

Arch Linux

#1 2010-01-10 05:44:11

presonus firebox + freebob problems

#2 2010-01-12 16:20:18

Re: presonus firebox + freebob problems

#3 2010-01-12 23:48:43

Re: presonus firebox + freebob problems

#4 2010-01-19 05:29:03

Re: presonus firebox + freebob problems

#5 2010-01-20 05:20:33

Re: presonus firebox + freebob problems

#6 2010-01-20 23:30:09

Re: presonus firebox + freebob problems

Board footer