Seite 1 von 1

FFADO, Jack und Motu 828

Verfasst: Mo Jul 19, 2010 9:24 am
von dorschner
Hallo liebe Leute,
wer kann mir bitte helfen ich verzweifle. Bitte schreibt einfach,dass ein Anfänger verstehen kann!
Ich bin neu auf der Linuxgemeinde, bisher hatte ich immer Mac. Jetzt ist die Zeit für mich gekommen umzusteigen.
Ich habe Ubuntu Studio installiert und bin begeistert was alles und wie gut es Funktioniert.
Nur: ich habe die Firewire Soundkarte Motu828, erstes Modell. Meine FirewirePCI ist gut erkannt worden, ich habe auch nach langem Probieren und nur mit vorherigem Starten des ffad-dbus-server, ffado-mixer starten können und er erkennt die Motu828 auch. Wenn ich aber Jack-Control starte findet er immer den Treiber nicht. Fehlermeldung (ohne gestartetem ffad-dbus-server):
10:13:05.186 Steckfeld deaktiviert.
10:13:05.232 Statistik zurückgesetzt.
10:13:05.246 Schaubild der ALSA-Verbindungen geändert.
10:13:06.162 ALSA active patchbay scan...
10:13:06.163 ALSA-Verbindung geändert.
10:13:06.401 ALSA active patchbay scan...
10:13:09.416 Startup script...
10:13:09.416 artsshell -q terminate
sh: artsshell: not found
10:13:09.818 Startup script terminated mit Rückgabewert = 32512.
10:13:09.818 JACK startet...
10:13:09.818 /usr/bin/jackd -v -P1 -p512 -dfirewire -r44100 -p1024 -n3 -i8 -o8
10:13:09.820 JACK wurde mit PID = 1961 gestartet.
jackd 0.118.0
Copyright 2001-2009 Paul Davis, Stephane Letz, Jack O'Quinn, Torben Hohn 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
Memory locking is unlimited - this is dangerous. You should probably alter the line:
@audio - memlock unlimited
in your /etc/limits.conf to read:
@audio - memlock 3042720
getting driver descriptor from /usr/lib/jack/jack_firewire.so
no message buffer overruns
getting driver descriptor from /usr/lib/jack/jack_oss.so
getting driver descriptor from /usr/lib/jack/jack_alsa.so
getting driver descriptor from /usr/lib/jack/jack_dummy.so
getting driver descriptor from /usr/lib/jack/jack_net.so
JACK compiled with System V SHM support.
server `default' registered
registered builtin port type 32 bit float mono audio
registered builtin port type 8 bit raw midi
clock source = system clock via clock_gettime
loading driver ..
start poll on 3 fd's
new client: firewire_pcm, id = 1 type 1 @ 0x1c1d8e0 fd = -1
SSE2 detected
new buffer size 1024
libffado 2.0.0 built Mar 31 2010 16:21:44
firewire MSG: Streaming thread running with Realtime scheduling, priority 1
firewire MSG: Registering audio capture port C0_dev0_cap_Analog1
firewire MSG: Registering audio capture port C1_dev0_cap_Analog2
registered port system:capture_1, offset = 4096
registered port system:capture_2, offset = 8192
firewire MSG: Registering audio capture port C2_dev0_cap_Analog3
firewire MSG: Registering audio capture port C3_dev0_cap_Analog4
registered port system:capture_3, offset = 12288
firewire MSG: Registering audio capture port C4_dev0_cap_Analog5
registered port system:capture_4, offset = 16384
firewire MSG: Registering audio capture port C5_dev0_cap_Analog6
registered port system:capture_5, offset = 20480
firewire MSG: Registering audio capture port C6_dev0_cap_Analog7
registered port system:capture_6, offset = 24576
firewire MSG: Registering audio capture port C7_dev0_cap_Analog8
registered port system:capture_7, offset = 28672
firewire MSG: Registering audio capture port C8_dev0_cap_SPDIF1
registered port system:capture_8, offset = 32768
firewire MSG: Registering audio capture port C9_dev0_cap_SPDIF2
registered port system:capture_9, offset = 36864
firewire MSG: Registering midi capture port C10_dev0_cap_MIDI0
registered port system:capture_10, offset = 40960
registered port firewire_pcm:C10_dev0_cap_MIDI0, offset = 4096
firewire MSG: Registering audio playback port P0_dev0_pbk_Analog1
firewire MSG: Registering audio playback port P1_dev0_pbk_Analog2
registered port system:playback_1, offset = 0
firewire MSG: Registering audio playback port P2_dev0_pbk_Analog3
registered port system:playback_2, offset = 0
firewire MSG: Registering audio playback port P3_dev0_pbk_Analog4
registered port system:playback_3, offset = 0
firewire MSG: Registering audio playback port P4_dev0_pbk_Analog5
registered port system:playback_4, offset = 0
firewire MSG: Registering audio playback port P5_dev0_pbk_Analog6
registered port system:playback_5, offset = 0
firewire MSG: Registering audio playback port P6_dev0_pbk_Analog7
registered port system:playback_6, offset = 0
firewire MSG: Registering audio playback port P7_dev0_pbk_Analog8
registered port system:playback_7, offset = 0
firewire MSG: Registering audio playback port P8_dev0_pbk_SPDIF1
firewire MSG: Registering audio playback port P9_dev0_pbk_SPDIF2
firewire MSG: Registering midi playback port P10_dev0_pbk_MIDI0
registered port system:playback_8, offset = 0
registered port system:playback_9, offset = 0
registered port system:playback_10, offset = 0
registered port firewire_pcm:P10_dev0_pbk_MIDI0, offset = 0
++ jack_sort_graph
++ jack_rechain_graph():
+++ client is now firewire_pcm active ? 1
client firewire_pcm: internal client, execution_order=0.
-- jack_rechain_graph()
-- jack_sort_graph
firewire ERR: Could not start streaming threads: -1
DRIVER NT: could not start driver
cannot start driver
starting server engine shutdown
stopping driver
server thread back from poll
unloading driver
no message buffer overruns
freeing shared port segments
stopping server thread
stopping watchdog thread
last xrun delay: 0.000 usecs
max delay reported by backend: 0.000 usecs
freeing engine shared memory
max usecs: 0.000, engine deleted
cleaning up shared memory
cleaning up files
unregistering server `default'
10:13:10.335 JACK wurde angehalten erfolgreich.
10:13:10.335 Post-shutdown script...
10:13:10.335 killall jackd
jackd: no process found
10:13:10.744 Post-shutdown script terminated mit Rückgabewert = 256.
10:13:12.091 Keine Verbindungsaufnahme als Client zum JACK-Server möglich. - Overall operation failed. - Verbindungsaufnahme zum Server gescheitert. Bitte sehen Sie im Meldungsfenster nach weiteren Informationen.
Fehlermeldung (mit gestartetem ffad-dbus-server):
10:19:53.084 Steckfeld deaktiviert.
10:19:53.135 Statistik zurückgesetzt.
10:19:53.151 Schaubild der ALSA-Verbindungen geändert.
10:19:53.712 ALSA active patchbay scan...
10:19:53.713 ALSA-Verbindung geändert.
10:19:53.942 ALSA active patchbay scan...
10:19:58.235 Startup script...
10:19:58.235 artsshell -q terminate
sh: artsshell: not found
10:19:58.637 Startup script terminated mit Rückgabewert = 32512.
10:19:58.637 JACK startet...
10:19:58.637 /usr/bin/jackd -v -P1 -p512 -dfirewire -r44100 -p1024 -n3 -i8 -o8
10:19:58.639 JACK wurde mit PID = 2140 gestartet.
jackd 0.118.0
Copyright 2001-2009 Paul Davis, Stephane Letz, Jack O'Quinn, Torben Hohn 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
Memory locking is unlimited - this is dangerous. You should probably alter the line:
@audio - memlock unlimited
in your /etc/limits.conf to read:
@audio - memlock 3042720
getting driver descriptor from /usr/lib/jack/jack_firewire.so
no message buffer overruns
getting driver descriptor from /usr/lib/jack/jack_oss.so
getting driver descriptor from /usr/lib/jack/jack_alsa.so
getting driver descriptor from /usr/lib/jack/jack_dummy.so
getting driver descriptor from /usr/lib/jack/jack_net.so
JACK compiled with System V SHM support.
server `default' registered
loading driver ..
registered builtin port type 32 bit float mono audio
registered builtin port type 8 bit raw midi
clock source = system clock via clock_gettime
start poll on 3 fd's
SSE2 detected
new client: firewire_pcm, id = 1 type 1 @ 0x27f18e0 fd = -1
new buffer size 1024
libffado 2.0.0 built Mar 31 2010 16:21:44
firewire MSG: Streaming thread running with Realtime scheduling, priority 1
firewire MSG: Registering audio capture port C0_dev0_cap_Analog1
firewire MSG: Registering audio capture port C1_dev0_cap_Analog2
firewire MSG: Registering audio capture port C2_dev0_cap_Analog3
firewire MSG: Registering audio capture port C3_dev0_cap_Analog4
firewire MSG: Registering audio capture port C4_dev0_cap_Analog5
firewire MSG: Registering audio capture port C5_dev0_cap_Analog6
firewire MSG: Registering audio capture port C6_dev0_cap_Analog7
firewire MSG: Registering audio capture port C7_dev0_cap_Analog8
firewire MSG: Registering audio capture port C8_dev0_cap_SPDIF1
firewire MSG: Registering audio capture port C9_dev0_cap_SPDIF2
firewire MSG: Registering midi capture port C10_dev0_cap_MIDI0
firewire MSG: Registering audio playback port P0_dev0_pbk_Analog1
firewire MSG: Registering audio playback port P1_dev0_pbk_Analog2
firewire MSG: Registering audio playback port P2_dev0_pbk_Analog3
firewire MSG: Registering audio playback port P3_dev0_pbk_Analog4
firewire MSG: Registering audio playback port P4_dev0_pbk_Analog5
firewire MSG: Registering audio playback port P5_dev0_pbk_Analog6
firewire MSG: Registering audio playback port P6_dev0_pbk_Analog7
firewire MSG: Registering audio playback port P7_dev0_pbk_Analog8
firewire MSG: Registering audio playback port P8_dev0_pbk_SPDIF1
firewire MSG: Registering audio playback port P9_dev0_pbk_SPDIF2
firewire MSG: Registering midi playback port P10_dev0_pbk_MIDI0
registered port system:capture_1, offset = 4096
registered port system:capture_2, offset = 8192
registered port system:capture_3, offset = 12288
registered port system:capture_4, offset = 16384
registered port system:capture_5, offset = 20480
registered port system:capture_6, offset = 24576
registered port system:capture_7, offset = 28672
registered port system:capture_8, offset = 32768
registered port system:capture_9, offset = 36864
registered port system:capture_10, offset = 40960
registered port firewire_pcm:C10_dev0_cap_MIDI0, offset = 4096
registered port system:playback_1, offset = 0
registered port system:playback_2, offset = 0
registered port system:playback_3, offset = 0
registered port system:playback_4, offset = 0
registered port system:playback_5, offset = 0
registered port system:playback_6, offset = 0
registered port system:playback_7, offset = 0
registered port system:playback_8, offset = 0
registered port system:playback_9, offset = 0
registered port system:playback_10, offset = 0
registered port firewire_pcm:P10_dev0_pbk_MIDI0, offset = 0
++ jack_sort_graph
++ jack_rechain_graph():
+++ client is now firewire_pcm active ? 1
client firewire_pcm: internal client, execution_order=0.
-- jack_rechain_graph()
-- jack_sort_graph
firewire ERR: Could not start streaming threads: -1
DRIVER NT: could not start driver
cannot start driver
starting server engine shutdown
stopping driver
server thread back from poll
unloading driver
no message buffer overruns
freeing shared port segments
stopping server thread
stopping watchdog thread
last xrun delay: 0.000 usecs
max delay reported by backend: 0.000 usecs
freeing engine shared memory
max usecs: 0.000, engine deleted
cleaning up shared memory
cleaning up files
unregistering server `default'
10:19:59.020 JACK wurde angehalten erfolgreich.
10:19:59.020 Post-shutdown script...
10:19:59.021 killall jackd
jackd: no process found
10:19:59.429 Post-shutdown script terminated mit Rückgabewert = 256.
10:20:00.946 Keine Verbindungsaufnahme als Client zum JACK-Server möglich. - Overall operation failed. - Verbindungsaufnahme zum Server gescheitert. Bitte sehen Sie im Meldungsfenster nach weiteren Informationen.
Herzlichst und Danke Dorschner

Re: FFADO, Jack und Motu 828

Verfasst: Mo Jul 19, 2010 9:54 am
von khz
handelt sich es um diese sc?

Re: FFADO, Jack und Motu 828

Verfasst: Mo Jul 19, 2010 1:12 pm
von dorschner
Nein, meine ist noch älter als die mkI.
dorschner

Re: FFADO, Jack und Motu 828

Verfasst: Mo Jul 19, 2010 5:25 pm
von Mitsch
Hä?
"mkI" heißt doch "erstes Modell" - älter geht nicht.

* lasse mich aber gerne eines besseren belehren *

Coole Sache, was Du mit dem MOTU 828 versuchst - Kenne einen Kollegen mit diesem Interface und ich habe mich schon immer gefragt, ob man das Teil mit Linux benutzen könnte. Leider habe ich in Sachen Firewire-Interface und Linux keinerlei Erfahrung. Nach wie vor sind die PCI-Interfaces von RME (zumindest) meine erste Wahl... :)

Grüße!