[PlanetCCRMA] RT kernel, jack, freebob
Adam Swift
vikeul at omnitude.net
Tue Dec 9 17:53:22 PST 2008
Len,
Beware my own long post :P
Yes, I've had the firepod working a while now. Mine is actually a
firepod, not an FP10, but the only difference is a name change.
Something to do with a certain Apple product I think.
Based on your email, I'm fairly convinced that your problem is the
Ricoh firewire chipset. Apparently not all firewire chips are created
equal, which is of course silly seeing there is a specification. From
what I can tell, here is the developers order of preference:
TI (always works)
VIA (works with some and not others, this is what I have)
Ones that they/Presonus say don't work:
Ricoh (yours, unfortunately)
NEC (Presonus gear seems to have conflicts with these)
Firewire built into Creative Audigy cards
There is some addition hardware that is incompatible with listed here:
http://psfaq.presonus.com/index.php?action=artikel&cat=21&id=48&artlang=en
.
Every software problem I had and have seen with getting the firepod
working would have shown up in your logs- your logs get far enough
into the initialisation to suggest to me that it is not software. I
suggest you go to pc shops near you, ask to see a firewire card out of
its box, and read the manufacturer off the chip, if that's possible
with laptop cards. If it's TI, or less so VIA, buy! Make sure it is
not a USB/firewire combo card, and that it does not have firewire 800,
which has a much smaller socket. I found that TI cards were hard to
get here in Brisbane, Australia, but VIA worked for me. Australian
consumer rights guarantee a refund if it does not work in the
advertised use so I was able to get a refund easily when I bought an
NEC card by accident. Hopefully you can do the same.
Another thing to be wary of is the motherboard... I have an AsRock
P4i65G. There is an internal sound card which you see in the lspci
below but I don't use it. The previous motherboard was an ASUS. I hate
to say it, but every ASUS motherboard I have touched has had DSDT/ACPI
issues, which screws with the interrupts, which in turn screws with
firewire cards. Intel boards I know for sure are good about this and
other interrupt issues, because Intel was one of the main companies
who standardised ACPI and thus they follow it to the letter. But
anyway, try the firewire card first, because I know that Ricohs have
problems.
Good luck!
Adam
Here is a bunch of other spurious information that might help you:
Versions:
A "2008-03-31" spin of FC8. Applied most updates after installing
CCRMA, but I was careful not to install any things from the fedora
repositories that conflicted with the CCRMA ones- most noticeably
libraw1394, which broke my install before I figured it out.
kernel-rt-2.6.24.7-1.rt21.1.fc8.ccrma.i686 although I do think I was
using kernel-rt-2.6.24.7-1.rt3.2.fc8.ccrma.i686 before that.
jack-audio-connection-kit.i386 0.109.12-0.svn1135_942
libraw1394.i386 1.3.0-6.1.fc8.ccrma
ardour.i386 2.6.1-0.1.fc8.ccrma
ls -l /dev/raw1394
crw------- 1 mik rawfw 171, 0 2008-12-10 10:44 /dev/raw1394
Apparently I couldn't figure out how to set up the permissions
properly, so this hodge-podge is how it comes out when jack is running
with the firepod. This isn't your problem though, otherwise you'd have
permission denied errors. mik is the primary user on the machine.
I use qjackctrl to start jack before doing anything else, using these
settings:
Realtime on, priority 60 (which fits into my rtirq settings which I
have forgotten to retrieve), frames/period 512, sample rate 96k,
periods/buffer 3, interface hw:0.
Ardour is the primary application we use with it. It shows a latency
of 5.3ms which seems to be stable based on ~30min of test recording 8
channels, and a bunch of real work done after that.
Here is the important bits of lsmod:
Module Size Used by
dv1394 19128 0
raw1394 24408 4
i915 23552 2
snd_intel8x0 30108 3
snd_ac97_codec 92324 1 snd_intel8x0
ac97_bus 5888 1 snd_ac97_codec
snd_seq_dummy 6532 0
ohci1394 29744 3 dv1394
snd_seq_oss 29824 0
snd_seq_midi_event 9600 1 snd_seq_oss
snd_seq 45040 9 snd_seq_dummy,snd_seq_oss,snd_seq_midi_event
snd_seq_device 9740 3 snd_seq_dummy,snd_seq_oss,snd_seq
snd_pcm_oss 37120 0
snd_mixer_oss 16512 2 snd_pcm_oss
snd_pcm 63492 3 snd_intel8x0,snd_ac97_codec,snd_pcm_oss
snd_timer 20356 2 snd_seq,snd_pcm
snd 43780 15
snd_intel8x0,snd_ac97_codec,snd_seq_oss,snd_seq,snd_seq_device,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_timer
soundcore 9824 2 snd
snd_page_alloc 11016 2 snd_intel8x0,snd_pcm
uhci_hcd 23568 0
ohci_hcd 22532 0
ehci_hcd 31884 0
And here is the important bits of my lspci -vv:
01:02.0 FireWire (IEEE 1394): VIA Technologies, Inc. IEEE 1394 Host
Controller (rev 46) (prog-if 10 [OHCI])
Subsystem: VIA Technologies, Inc. IEEE 1394 Host Controller
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop-
ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium
>TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 32 (8000ns max), Cache Line Size: 32 bytes
Interrupt: pin A routed to IRQ 16
Region 0: Memory at ff0ff800 (32-bit, non-prefetchable) [size=2K]
Region 1: I/O ports at bc00 [size=128]
Capabilities: [50] Power Management version 2
Flags: PMEClk- DSI- D1- D2+ AuxCurrent=0mA
PME(D0-,D1-,D2+,D3hot+,D3cold+)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
Kernel driver in use: ohci1394
Kernel modules: ohci1394
00:00.0 Host bridge: Intel Corporation 82865G/PE/P DRAM
Controller/Host-Hub Interface (rev 02)
Subsystem: ASRock Incorporation Unknown device 2570
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast
>TAbort- <TAbort- <MAbort+ >SERR- <PERR- INTx-
Latency: 0
Region 0: Memory at fe800000 (32-bit, prefetchable) [size=4M]
Capabilities: [e4] Vendor Specific Information <?>
Kernel driver in use: agpgart-intel
00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev c2)
(prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR+ FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast
>TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0
Bus: primary=00, secondary=01, subordinate=01, sec-latency=32
I/O behind bridge: 0000b000-0000bfff
Memory behind bridge: ff000000-ff0fffff
Secondary status: 66MHz- FastB2B+ ParErr- DEVSEL=medium
>TAbort- <TAbort- <MAbort- <SERR- <PERR-
BridgeCtl: Parity- SERR+ NoISA+ VGA- MAbort- >Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
00:1f.5 Multimedia audio controller: Intel Corporation 82801EB/ER
(ICH5/ICH5R) AC'97 Audio Controller (rev 02)
Subsystem: ASRock Incorporation Unknown device 9761
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium
>TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0
Interrupt: pin B routed to IRQ 20
Region 0: I/O ports at d800 [size=256]
Region 1: I/O ports at d400 [size=64]
Region 2: Memory at ff27f800 (32-bit, non-prefetchable) [size=512]
Region 3: Memory at ff27f400 (32-bit, non-prefetchable) [size=256]
Capabilities: [50] Power Management version 2
Flags: PMEClk- DSI- D1- D2- AuxCurrent=375mA
PME(D0+,D1-,D2-,D3hot+,D3cold+)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
Kernel driver in use: Intel ICH
Kernel modules: snd-intel8x0
Len <lenb_99 at yahoo.com> wrote:
> 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
>
>
>
>
> _______________________________________________
> PlanetCCRMA mailing list
> PlanetCCRMA at ccrma.stanford.edu
> http://ccrma-mail.stanford.edu/mailman/listinfo/planetccrma
>
More information about the PlanetCCRMA
mailing list