[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: unable to start qjackctl and ardour



Chris, 

thank you very much for your answer. The situation is the following. As
a normal user I want to use qjackctl in order to start jack. Then I get
the followin message:

cannot lock down memory for jackd (Operation not permitted)
loading driver ..
apparent rate = 48000
creating alsa driver ... hw:0|hw:0|1024|2|48000|0|0|nomon|swmeter|-|
32bit
control device hw:0
configuring for 48000Hz, period = 1024 frames, buffer = 2 periods
Couldn't open hw:0 for 32bit samples trying 24bit instead
Couldn't open hw:0 for 24bit samples trying 16bit instead
Couldn't open hw:0 for 32bit samples trying 24bit instead
Couldn't open hw:0 for 24bit samples trying 16bit instead
JACK: unable to mlock() port buffers: Operation not permitted
jack_create_thread: error 1 setting scheduler parameters after thread
creation: Operation not permitted
cannot start watchdog thread
cannot load driver module alsa
09:57:47.539 JACK was stopped successfully.
09:57:49.523 Could not connect to JACK server as client.

Only when I run the command as root I can start jack. 

As you suggested, the problem has to do with realtime privileges. It
seems that the answer of John O'Hagan provides the solution, which
requires a kernel recompilation.

Regards,

Marcelo



On Mon, 2006-10-16 at 01:03 -0400, Chris Metzler wrote:
> On Sun, 15 Oct 2006 21:36:19 -0200
> Marcelo Chiapparini wrote:
> >
> > Dear list,
> > 
> > I am running sarge. And I want to use ardour. I have installed ardour
> > and qjackctl. But the only way to run both, qjackctl to start the jack
> > deamon, and ardour, is as root. I am unable to star both programs as a
> > normal user. How can I fix this?
> 
> Could you elaborate?  What do you mean by "unable to start"?  How do
> you try to start them, and what error messages do you get when you try?
> 
> As an aside, have you read the related documentation for jackd?  If so,
> do your problems relate to realtime privileges?
> 
> -c
> 
> 
-- 
Marcelo Chiapparini
chiappa@oi.com.br



Reply to: