freebob / jack won't start since upgrading to 2.1~pre2
Hi,
totally new here, I've installed 2.0 last week and started to use it with jack and freebob (for my firewire M-Audio). It worked great but I missed my VSTs so I've upgraded to 2.1~pre2 as I wanted to try the VST/VSti How-to.
Now Freebob can't start anymore unless I reboot with the previous kernel, I've tried to re-install it with Synaptics but no luck.
I have the following messages when I click on start in JackControl :
23:03:32.274 Patchbay deactivated.
23:03:32.354 Statistics reset.
JACK tmpdir identified as [/dev/shm]
23:03:32.517 MIDI connection graph change.
23:03:32.630 MIDI connection change.
23:03:37.394 Startup script...
23:03:37.395 artsshell -q terminate
JACK tmpdir identified as [/dev/shm]
can't create mcop directory
Creating link /home/facochere/.kde/socket-64studio.
23:03:38.132 Startup script terminated with exit status=256.
23:03:38.132 JACK is starting...
23:03:38.132 /usr/bin/jackd -R -dfreebob -r44100 -p128 -n3 -D
23:03:38.135 JACK was started with PID=4535 (0x11b7).
jackd 0.103.0
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
Ieee1394Service::initialize: Could not get 1394 handle: No such file or directory
Is ieee1394 and raw1394 driver loaded?
[31mFatal (devicemanager.cpp)[68] initialize: Could not initialize Ieee1349Service object
[0m[31mFatal (freebob.cpp)[69] freebob_new_handle: Could not initialize device manager
FreeBoB ERR: FREEBOB: Error creating virtual device
[0mcannot load driver module freebob
23:03:38.355 JACK was stopped successfully.
23:03:38.355 Post-shutdown script...
23:03:38.355 killall jackd
jackd: aucun processus tué
23:03:38.578 Post-shutdown script terminated with exit status=256.
23:03:40.154 Could not connect to JACK server as client. Please check the messages window for more info.
JACK tmpdir identified as [/dev/shm]
Thanks in advance

It's configuration bug
Thanks for your answer, I'll
I've tried suggestions from