[PlanetCCRMA] RT kernel, jack, freebob

Len lenb_99 at yahoo.com
Tue Dec 9 11:03:27 PST 2008


I'm having problems getting a Presonus Firepod (FP-10) to work on FC8.  I read in an earlier thread that someone (Adam Swift) was running this box successfully using the Planet CCRMA RT kernel.  Not sure if it was FC8.

I installed Fedora 8 on a HP Pavilion laptop (Core 2 duo CPU).  Everything went fine, installed Planet CCRMA Core and Apps, was able to run Jack and Hydrogen using the on-board (HDA Intel) sound card.  

I was running 
kernel-rt-2.6.24.7-1.rt3.2.fc8.ccrma.i686 
and 
jack-audio-connection-kit-0.116.0-0.svn3154.1.fc8.ccrma.i386

Since that was working fine, I plugged in the Firepod, selected the freebob drivers in Qjackctl Setup and fired up jack.  There were errors, but I don't have a copy of the output.  They seemed to be related to the libraw1394 drivers from Fedora, and I read in the PlanetCCRMA archives that it was necessary to force the CCRMA libraw1394 driver to install, so I did that.  Still no luck.

Here is an example of the errors I'm getting now (I guess I must have let the package updater upgrade jack to 0.116.1 in the interim):

12:37:20.923 /usr/bin/jackd -R -P89 -dfreebob -dhw:0 -r48000 -p128 -n3 -D
12:37:20.926 JACK was started with PID=3129.
jackd 0.116.1
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 ..
SSE2 detected
Freebob using Firewire port 0, node -1
12:37:22.745 ALSA connection graph change.
libiec61883 warning: Established connection on channel 0.
You may need to manually set the channel on the receiving node.
libiec61883 warning: Established connection on channel 1.
You may need to manually set the channel on the transmitting node.
12:37:22.928 ALSA connection change.
12:37:23.149 Server configuration saved to "/home/chwbk/.jackdrc".
12:37:23.150 Statistics reset.
12:37:23.757 Client activated.
12:37:23.762 JACK connection change.
12:37:23.769 JACK connection graph change.
SSE2 detected
12:37:26.780 ALSA connection graph change.
12:37:26.781 Shutdown notification.
12:37:26.788 JACK is stopping...
LibFreeBoB ERR: watchdog: timeout
12:37:26.789 JACK is being forced...
cannot continue execution of the processing graph (Broken pipe)
zombified - calling shutdown handler
12:37:26.791 JACK has crashed.
12:37:26.989 JACK was stopped successfully.
12:37:26.989 Post-shutdown script...
12:37:26.989 killall jackd
jackd: no process killed
12:37:27.446 Post-shutdown script terminated with exit status=256.


Then I tried enabling the testing repo and installing 
kernel-rt-2.6.24.7-1.rt21.1.fc8.ccrma.i686
and
jack-audio-connection-kit-1.9.1-0.svn3142.1.fc8.ccrma.i386  (jackdmp?)


Now I get this error from jack:
13:01:13.895 /usr/bin/jackd -R -P89 -dfreebob -dhw:0 -r48000 -p256 -n3 -D
13:01:13.906 JACK was started with PID=3148.
jackdmp 1.9.1
Copyright 2001-2005 Paul Davis and others.
Copyright 2004-2008 Grame.
jackdmp 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 server starting in realtime mode with priority 89
Freebob using Firewire port 0, node -1
libiec61883 warning: Established connection on channel 0.
You may need to manually set the channel on the receiving node.
libiec61883 warning: Established connection on channel 1.
You may need to manually set the channel on the transmitting node.
13:01:16.690 Server configuration saved to "/home/chwbk/.jackdrc".
13:01:16.691 Statistics reset.
13:01:16.696 Client activated.
13:01:16.704 JACK connection change.
13:01:19.746 Shutdown notification.
13:01:19.753 JACK is stopping...
LibFreeBoB ERR: watchdog: timeout
13:01:19.754 JACK is being forced...
Cannot read socket fd = 18 err = Success
JackSocketClientChannel read fail
13:01:19.760 JACK has crashed.
13:01:19.955 JACK was stopped successfully.
13:01:19.956 Post-shutdown script...
13:01:19.956 killall jackd
jackd: no process killed
13:01:20.586 Post-shutdown script terminated with exit status=256.


The whole firewire thing is kind of new for me.  I've been successful configuring a desktop system using a PCI-based breakout box (Echo Layla 24/96).

Is it necessary to do anything with modules.conf (or modprobe.conf), or does firewire not use it?

I'm also wondering if something else is messing with the same IRQ resource as the 1394 device.  I took a look at the output of lspci, but not sure how to interpret it (guess I should have used lspci -v or something).  These are just resources that appear to be on the same IRQ (09?) as the 1394:

09:09.0 FireWire (IEEE 1394): Ricoh Co Ltd R5C832 IEEE 1394 Controller (rev 05)
09:09.1 SD Host controller: Ricoh Co Ltd R5C822 SD/SDIO/MMC/MS/MSPro Host Adapter (rev 22)
09:09.2 System peripheral: Ricoh Co Ltd R5C843 MMC Host Controller (rev 12)
09:09.3 System peripheral: Ricoh Co Ltd R5C592 Memory Stick Bus Host Adapter (rev 12)
09:09.4 System peripheral: Ricoh Co Ltd xD-Picture Card Controller (rev ff)

These are the modules that are loaded (just 1394-related).  I can post the output of lsmod for all modules, but it's a long list.

$ sudo /sbin/lsmod | grep 1394
dv1394                 19128  0 
raw1394                24408  0 
ohci1394               29744  1 dv1394

Sorry for the long post.  Any help or advice would be greatly appreciated.  I guess I could try the stock Fedora kernel, but the RT kernel seemed to be working so well with the onboard sound - it doesn't appear to be a kernel issue.

Thanks!
Len


      



More information about the PlanetCCRMA mailing list