Re: [Jack-Devel] Jack on arm hf

On 05/06/2013 05:25 PM, [hidden] wrote:
> Hi Robin and all,
> 
> hmm, that last commit is from two months ago. I'm quite sure I'm using that patch already. I'm using a self-compiled version of jackd2 1.9.10  on a special distribution made for these sticks called Picuntu with no window manager.

The most common error: you're using a self-compiled jackd and libjack
but there are some files remaining from distribution's jack packages.
check /usr/lib/armhf-linux-gnu/jack/ vs /usr/lib/jack/ for example.

> I just tried again with the built in hdmi interface after unsuccessful attempts with a usb interface:
> 
> When I try to connect SuperCollider or just the jack_simple_client I get similar errors like this:
> 
> "Cannot lock down 68157440 byte memory area (Cannot allocate memory)
> Cannot lock down 2048917504 byte memory area (Cannot allocate memory)

That one smells like some 32/64 bit or endianess issue. Though hard to
say. Can you provide a backtrace?  -- It might also just be missing RT
privileges and/or related to you not starting jackd manually but let
supercollider start a temporary jack server...

NB. On a similar system (802mkII) I had issues with bus powered USB
devices where jackd would crash randomly or even stranger things
happened. -- It turned out that the USB bus could not provide enough
power for the audio device.

I run jack2 on both armel as well as armhf platforms - custom versions
(no dbus) debian packages: http://gareus.org/deb/pool/main/j/jackd2/
might be they work for you, too.

> Cannot lock down 25165824 byte memory area (Cannot allocate memory)
> You cannot set callbacks on an active client
> no physical playback ports
> axel@picuntu:$ Unknown error..

OK. this is a different issue than previous jack2/ARM issues (which
crashed with bus error due to memory alignment, packed structs).

Can you post the complete log from jack startup? or best a gdb backtrace
of the crash.

robin

1367855112.3186_0.ltw:2,Sa <5187D001.1020808 at gareus dot org>