keeping Jack from stopping

[oNNogitaar]

hmmokay, I opened Jack tried buffer 3 and 256 frames, then I pressed play.
Here is the outcome:

Code: Select all

18:24:02.151 Patchbay deactivated.
18:24:02.179 Statistics reset.
18:24:02.411 Startup script...
18:24:02.411 artsshell -q terminate
18:24:02.425 ALSA connection graph change.
sh: artsshell: not found
18:24:02.829 Startup script terminated with exit status=32512.
18:24:02.830 JACK is starting...
18:24:02.830 /usr/bin/jackd -dfirewire -dhw:0 -r44100 -p64 -n2
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    2690709
18:24:02.848 JACK was started with PID=5253.
no message buffer overruns
JACK compiled with System V SHM support.
loading driver ..
07693599738:  (ffado.cpp)[  92] ffado_streaming_init: libffado 2.999.0- built Dec  3 2010 14:10:13
18:24:03.035 ALSA connection change.
07694178399: Error (fireworks_session_block.cpp)[ 129] loadFromDevice: Flash read failed
jackd: src/fireworks/efc/efc_cmds_hardware.cpp:213: virtual bool FireWorks::EfcPolledValuesCmd::deserialize(Util::Cmd::IISDeserialize&): Assertion `nb_meters<100' failed.
18:24:03.692 JACK was stopped successfully.
18:24:03.693 Post-shutdown script...
18:24:03.693 killall jackd
18:24:03.694 JACK has crashed.
jackd: geen proces gevonden
18:24:04.106 Post-shutdown script terminated with exit status=256.
18:24:05.180 Could not connect to JACK server as client. - Overall operation failed. - Unable to connect to server. Please check the messages window for more info.
18:24:43.776 Startup script...
18:24:43.778 artsshell -q terminate
sh: artsshell: not found
18:24:44.183 Startup script terminated with exit status=32512.
18:24:44.184 JACK is starting...
18:24:44.184 /usr/bin/jackd -dfirewire -dhw:0 -r44100 -p256 -n3
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    2690709
18:24:44.196 JACK was started with PID=5275.
no message buffer overruns
JACK compiled with System V SHM support.
loading driver ..
07734980163:  (ffado.cpp)[  92] ffado_streaming_init: libffado 2.999.0- built Dec  3 2010 14:10:13
07735491584: Error (fireworks_session_block.cpp)[ 129] loadFromDevice: Flash read failed
jackd: src/fireworks/efc/efc_cmds_hardware.cpp:213: virtual bool FireWorks::EfcPolledValuesCmd::deserialize(Util::Cmd::IISDeserialize&): Assertion `nb_meters<100' failed.
18:24:44.912 JACK was stopped successfully.
18:24:44.913 Post-shutdown script...
18:24:44.913 killall jackd
18:24:44.914 JACK has crashed.
jackd: geen proces gevonden
18:24:45.324 Post-shutdown script terminated with exit status=256.
18:24:46.294 Could not connect to JACK server as client. - Overall operation failed. - Unable to connect to server. Please check the messages window for more info.

Jack stops...

[AutoStatic]

Found this: http://ubuntuforums.org/showthread.php?t=1382500

It is probably firmware related, you're either using a firmware version that is too old or too new. But the weird thing is that it has worked before and during our troubleshooting session it became clear you didn't perform any firmware updates. Is it possible to check what firmware is on the Echo? You will have to check this from Windows.

[oNNogitaar]

probably..., i can try that. Could you describe what I should do or is there a description online?
Thanks!
It is pretty funny(peculiar) yes...

[AutoStatic]

I'm afraid I really can't help you with obtaining the firmware version of the Echo. I don't own an Echo and my Windows knowledge is steadily degrading also.

[AutoStatic]

Could you try not using hw:0 as the designation for your FireWire card but (default) ?

[oNNogitaar]

In qjackctl, try

interface: (default)
instead of hw:0

Could you try not using hw:0 as the designation for your FireWire card but (default) ?

...sure, it it funny, I had already changed that

[oNNogitaar]

Code: Select all

17:12:13.147 Patchbay deactivated.
17:12:13.316 Statistics reset.
17:12:13.453 Startup script...
17:12:13.454 artsshell -q terminate
17:12:13.458 ALSA connection graph change.
sh: artsshell: not found
17:12:13.857 Startup script terminated with exit status=32512.
17:12:13.858 JACK is starting...
17:12:13.859 /usr/bin/jackd -dfirewire -dhw:0 -r44100 -p256 -n3
17:12:13.865 JACK was started with PID=6943.
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    2690709
no message buffer overruns
JACK compiled with System V SHM support.
loading driver ..
20830574033:  (ffado.cpp)[  92] ffado_streaming_init: libffado 2.999.0- built Dec  3 2010 14:10:13
17:12:14.065 ALSA connection change.
20831057484: Error (fireworks_session_block.cpp)[ 129] loadFromDevice: Flash read failed
jackd: src/fireworks/efc/efc_cmds_hardware.cpp:213: virtual bool FireWorks::EfcPolledValuesCmd::deserialize(Util::Cmd::IISDeserialize&): Assertion `nb_meters<100' failed.
17:12:14.549 JACK was stopped successfully.
17:12:14.550 Post-shutdown script...
17:12:14.550 killall jackd
17:12:14.551 JACK has crashed.
jackd: geen proces gevonden
17:12:14.961 Post-shutdown script terminated with exit status=256.
17:12:16.208 Could not connect to JACK server as client. - Overall operation failed. - Unable to connect to server. Please check the messages window for more info.

[AutoStatic]

And do you have any other options besides (default) or hw:0? Could you try those?

[oNNogitaar]

Could you try those?

Yes I do, I will try tomorrow. Can I read some about them somewhere?
Thanks Jeremy!

[oNNogitaar]

I did some homework and I learned:
-firmware is software by Echo
-it is somewhere on my card
-it has to do with Windows

I tried to join the Echo user forum, it seems to be dead. http://www.echoaudio.com/forum But it is being reanimated so I will get back there later...

I have some questions:
Why do I need Windows related software in the first place and (if not) why can I not (under Linux) just remove all Windows related software from the card and replace it with the one I need for Linux (I am not going back anyway, if it will not work under Linux I will ditch it in the end )
I still do have a Windows(xp) partition but there is almost nothing on it (the soundcard is not even installed there) so I do not know if I could still aproach the device from there.

http://ubuntuforums.org/showthread.php?t=1382500 this is very familiar indeed..

[AutoStatic]

Hi oNNogitaar,

What is the status at the moment? Sorry I didn't get back to you earlier
Which Linux distro are you using now? Still no joy? You can't update the firmware from Linux because probably Echo didn't give anyone the proper documentation to do so. And maybe no one's interested in writing such a firmware update tool for Linux so no one ever asked Echo for those docs. That's the way it is for Linux and big companies, if no one asks they won't take in account to write drivers or tools for Linux.

Best,

Jeremy

[oNNogitaar]

Hi Jeremy,
well it is not working. I am running avlinux4.2-liqx-lxde-i386-en and did this http://geekconnection.org/remastersys/forums/index.php?topic=516.0and thishttp://www.remastersys.com/forums/index%20...%20pic=1226.0 as adviced in a different topic.
It should work as stated herehttp://www.remastersys.com/forums/index.php?topic=1210.0but I have no succes yet. I also went to the Linuxusergroup as Pablo adviced but they do not know either... (no musicians there)
Concerning the firmware: I am not sure if I quite got your point...
When running Linux one uses the Windows firmware which is on the soundcard, is that right?
So I should hook up my device to a Windows PC and than what? http://www.echoaudio.com/forum is still down. I mailed Echo to ask for a firmware update tool for Linux. hope that helps...

[oNNogitaar]

...well, I have been doing my homework.
I updated my windows partition, and indeed everything went smoothly.
-hooked up the echo
-installed the driver
-opened the console
-updated the firmware to 5.5
and it is running fine under MS Windows XP sp3 ...

Under linux it is still a no go, Jack crashes within seconds (unable to read flash memory)

[Pablo]

Another interesting thread on a similar topic, in case it helps:

http://ardour.org/node/4216

[oNNogitaar]

thanks! i posted there