|
From: Mentoj D. <men...@gm...> - 2014-07-10 20:43:45
|
hey there, this morning i tried to start with another firewire-wire (lol). but no change. but the new one is 5 m long and never actually worked ;-) so i need to get another proper one... can take some time. but right now i tried it again with the old (short) one. and jack startet for about 2 seconds and then stoped again (in this time, the status LED turns also blue, which normally is a good sign. but then red again what is bad). here is the output: 22:03:52.170 Patchbay deactivated. 22:03:52.178 Statistics reset. 22:03:52.182 ALSA connection change. connect(2) call to /dev/shm/jack-1000/default/jack_0 failed (err=No such file or directory) attempt to connect to server failed 22:03:52.191 ALSA connection graph change. 22:03:54.545 JACK is starting... 22:03:54.546 /usr/bin/jackd -r -t2000 -dfirewire -r44100 -p1024 -n3 connect(2) call to /dev/shm/jack-1000/default/jack_0 failed (err=No such file or directory) attempt to connect to server failed jackd 0.124.1 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 22:03:54.596 JACK was started with PID=2991. JACK compiled with System V SHM support. loading driver .. 1405022634589222: (ffado.cpp)[ 92] ffado_streaming_init: libffado 2.1.9999-2468 built Dec 25 2013 14:40:10 22:03:56.615 JACK connection change. 22:03:56.616 Server configuration saved to "/home/av/.jackdrc". 22:03:56.617 Statistics reset. 22:03:56.617 Client activated. 22:03:56.617 Post-startup script... 22:03:56.618 /usr/bin/start_jackutils.sh 22:03:56.619 Buffer size change (1024). alsa_in: no process found alsa_out: no process found zita-a2j: no process found zita-j2a: no process found pulseaudio: no process found 22:03:59.021 Post-startup script terminated successfully. 22:03:59.022 JACK connection change. Alsa Loopback daemon started successfully firewire ERR: Could not start streaming threads: -1 DRIVER NT: could not start driver cannot start driver 22:04:02.609 JACK connection graph change. 22:04:02.625 JACK connection change. no message buffer overruns 22:04:02.802 Shutdown notification. 22:04:02.802 Client deactivated. 22:04:02.803 JACK is being forced... cannot read server event (Success) cannot continue execution of the processing graph (Bad file descriptor) graph error - calling shutdown handler cannot read server event (Success) cannot continue execution of the processing graph (Broken pipe) graph error - calling shutdown handler cannot read server event (Success) cannot continue execution of the processing graph (Bad file descriptor) graph error - calling shutdown handler Killing conflicting processes... Alsa Loopback daemon is shutting down 22:04:03.003 JACK was stopped successfully. 22:04:03.003 Post-shutdown script... 22:04:03.003 /usr/bin/stop_jackutils.sh jackd: no process found 22:04:05.409 Post-shutdown script terminated with exit status=256. i can reproduce this at this moment. always with the same output. does that make any sense? Gesendet: Donnerstag, 10. Juli 2014 um 01:23 Uhr Von: "Jonathan Woithe" <jw...@ju...> An: "Mentoj Dija" <men...@gm...> Cc: ffa...@li..., jw...@ju... Betreff: Re: [FFADO-user] me and my firepod need help! Hi Mentoj On Thu, Jul 10, 2014 at 12:11:32AM +0200, Mentoj Dija wrote: > well, that was to fast. now it doesn'n work again. with both distros... :-( :-( I thought it slightly odd that the issue was fixed simply by the passage of time. :-) > so back to start... > > i'm using a firewire-expressCard. i'm trying to start jack with qJackCTL. > not as root! Great - thanks for confirming this. > dmesg returns a lot. i think this is the interesting part: > > [ 139.426187] firewire_core 0000:05:00.0: parent port inconsistency for node 0: parent_count=1 > [ 139.426196] firewire_core 0000:05:00.0: topology build failed > : > [ 139.429935] firewire_core 0000:05:00.0: PHY ID mismatch in self ID: 1 != 2 > [ 139.429938] firewire_core 0000:05:00.0: topology build failed > : > [ 142.933747] firewire_ohci 0000:05:00.0: isochronous cycle inconsistent > : > [ 279.719450] firewire_ohci 0000:05:00.0: bad self ID 0/4 (9627f807 != ~00000000) > : > [ 281.781805] firewire_ohci 0000:05:00.0: no self IDs > : > [ 603.472617] firewire_core 0000:05:00.0: created device fw0: GUID 00000000000000c8, S400 > [ 604.722330] firewire_ohci 0000:05:00.0: bad self ID 0/4 (9927f807 != ~00000000) > [ 604.723027] firewire_ohci 0000:05:00.0: bad self ID 0/4 (9927f807 != ~00000000) > : > [ 604.724623] firewire_core 0000:05:00.0: PHY ID mismatch in self ID: 1 != 3 > [ 604.724637] firewire_core 0000:05:00.0: topology build failed These messages seem to confirm my suspicions that there is some sort of hardware problem at play here. Evidently it's intermittant since you were able to get things working briefly. It explains, for instance, why your "ListDevices" test reported yesterday did not include your audio interface. Stefan would be the best person to decode the above messages and suggest possible causes. To me it appears that the bus is completely failing to configure itself, possibly because data is being corrupted on the bus. I can think of the following potential causes, roughly in order of decreasing probability: 1) A bad firewire cable (or a cable that's too long) 2) A bad firewire socket either on the expresscard or the audio interface itself 3) A fault in the audio interface 4) A faulty expresscard 5) An obscure problem in the firewire kernel driver which is getting tripped by your specific card Since the reported errors are all associated with data flow on the bus I think we can discount a faulty expresscard interface. The above messages from the kernel indicate that there is an issue which lies very close to the bus hardware, which is several layers below FFADO. The components involved when a firewire audio interface is used are encountered in the following order. FFADO - libraw1394 - [firewire_core] - [firewire_ohci] - expresscard hardware - firewire bus - audio interface The messages you're receiving are coming from the two kernel modules (listed inside []) which are reporting problems which could originate from any of the three components on the bottom line. The result is that the expresscard is unable to communicate with the audio interface and as a result, anything above that can not know about the interface's existence. Therefore, our current focus needs to be the identification of the cause of these messages in your setup. Cause 1 is easiest to test: just try a different cable. Obviously things get more complicated as you move down the list. FYI the firewire specification says that 5m cables are the maximum permissible length. Manufacturers tend to play it safe and offer 4.5m as a maximum length. In my experience, cables this long only work if they are high quality cables. Furthermore, if devices are daisychanged such that the bus length approaches 4-5m you can also hit problems. The best approach is to use the best quality shortest cables you can get away with. > [ 665.846994] thinkpad_acpi: EC reports that Thermal Table has changed For what it's worth I don't think this has anything to do with the firewire stuff. Regards jonathan |