Arch Linux

nLEyETn

Member

Registered: 2008-10-01

Posts: 34

[SOLVED] JACK problem with locking down memory

I'm trying to run jack but it has a problem with locking memory down.  I get this message when jackd starts,

cannot lock down memory for RT thread (Cannot allocate memory)

Other than that, it seems to run alright with RT priority.  As far as I can tell, it looks like my /etc/security/limits.conf is fine.  It contains this in it:

*               -       rtprio          0
*               -       nice            0
@audio          -       rtprio          65
@audio          -       nice           -10
@audio          -       memlock         40000

Any ideas on what's causing it?

Last edited by nLEyETn (2008-10-21 03:55:25)

btartsa

Member

Registered: 2004-07-26

Posts: 222

Re: [SOLVED] JACK problem with locking down memory

Kernel, jack version and login manager please...oh and post up how you are starting jackd on the command line. (;

How much ram do you have?

nLEyETn

Member

Registered: 2008-10-01

Posts: 34

Re: [SOLVED] JACK problem with locking down memory

I'm using a custom compiled kernel 2.6.26.5  I kept all the options Arch uses, I just added LDM support to it.
JACK is 0.109.2 and is the official one from the repos.
I'm using a text login manager and just use startx to open up Xfce.
I have 2GB of RAM.

EDIT: Forgot to add the jackd startup command I'm using qjackctl to start it, but the command that shows up in messages is:

/usr/bin/jackd -R -dalsa -dhw:0 -r48000 -p512 -n4

Last edited by nLEyETn (2008-10-13 23:23:03)

nLEyETn

Member

Registered: 2008-10-01

Posts: 34

Re: [SOLVED] JACK problem with locking down memory

Bump.

And I thought I'd add I'm using the 2.6.27 kernel now, and it still has problems.

btartsa

Member

Registered: 2004-07-26

Posts: 222

Re: [SOLVED] JACK problem with locking down memory

Try installing slim-pam from aur and test it.

nLEyETn

Member

Registered: 2008-10-01

Posts: 34

Re: [SOLVED] JACK problem with locking down memory

Well, I fixed it by increasing the amount of allowed memory in /etc/security/limits.conf   It was set at 40000KB, and I tried bumping it up to 524288KB which let it work fine.  I then tried it at 1048576KB and that worked without any problems also.  I'm not sure why it needs that much memory but it seemed to do the trick so I'm happy with it now.