[LAU] firewire newbie in trouble

[Atte André Jensen]

Hi

I went ahead and got myself a edirol fa-66. Having no experience with 
firewire I have no idea why it doesn't work. The problem is that jack 
(qjackctl) seems to start up fine, but dies after a few seconds. My jack 
settings are IMO conservative: buffer size of 256.

Here's what's printed in "messages":
19:39:10.306 Patchbay activated.
19:39:10.354 Statistics reset.
19:39:10.364 Startup script...
19:39:10.365 artsshell -q terminate
19:39:10.403 ALSA connection graph change.
19:39:10.787 Startup script terminated with exit status=256.
19:39:10.788 JACK is starting...
19:39:10.788 /usr/bin/jackd -R -P80 -m -dfreebob -dhw:0 -r48000 -p128 -n3 -D
19:39:10.790 JACK was started with PID=10604.
jackd 0.109.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 ..
Freebob using Firewire port 0, node -1
19:39:10.989 MIDI active patchbay scan...
19:39:10.992 ALSA connection change.
19:39:11.192 MIDI active patchbay scan...
19:39:11.715 ALSA connection graph change.
libiec61883 warning: iec61883_cmp_create_p2p_output: Failed to set the 
oPCR[0] plug for node 0.
LibFreeBoB ERR: Could not do CMP for connection 0
FreeBoB ERR: Could not start streaming threads
DRIVER NT: could not start driver
cannot start driver
19:39:11.793 MIDI active patchbay scan...
19:39:11.795 ALSA connection change.
19:39:31.721 Could not connect to JACK server as client. - Overall 
operation failed. - Server communication error. Please check the 
messages window for more info.
jackd watchdog: timeout - killing jackd
could not attach as JACK client (server has exited)
19:39:31.918 ALSA connection graph change.
19:39:31.919 JACK was stopped successfully.
19:39:31.919 Post-shutdown script...
19:39:31.920 killall jackd
19:39:31.920 JACK has crashed.
jackd: no process killed
19:39:32.335 Post-shutdown script terminated with exit status=256.
20:27:22.325 MIDI active patchbay scan...
20:27:22.327 ALSA connection change.
20:27:22.528 MIDI active patchbay scan...

What I did + info about my system (ubuntu 8.04):
atte at vestbjerg:~$ uname -r
2.6.24-21-rt

atte at vestbjerg:~$ lsmod | grep 1394
dv1394                 20664  0
raw1394                29400  0
ohci1394               34096  1 dv1394
ieee1394               95544  4 dv1394,raw1394,sbp2,ohci1394

atte at vestbjerg:~$ grep disk /etc/udev/rules.d/40-permissions.rules
ATTRS{removable}!="1",			GROUP="disk"
KERNEL=="raw1394",			GROUP="disk"
ATTRS{type}=="0",			GROUP="disk"

atte at vestbjerg:~$ grep disk /etc/group
disk:x:6:atte

This is what dmesg says when plugging the fa-66 in:
[ 3824.579054] ieee1394: Node changed: 0-01:1023 -> 0-00:1023
[ 3824.579064] ieee1394: Node suspended: ID:BUS[0-00:1023] 
GUID[0040ab0000c37a87]
[ 3830.249545] ieee1394: Error parsing configrom for node 0-00:1023
[ 3830.249623] ieee1394: Node changed: 0-00:1023 -> 0-01:1023
[ 3831.383625] doh, someone wants to mess with state set
[ 3831.453179] ieee1394: Node resumed: ID:BUS[0-00:1023] 
GUID[0040ab0000c37a87]

Besides this, I'm not sure what to look for. Any help appreciated!

-- 
Atte

http://atte.dk    http://modlys.dk