30 Sep
2005
30 Sep
'05
9:01 p.m.
I used to have jack working fine on my system, but lately strange things
have been happening. Right now when I try:
jackd -v -d alsa
I get,
too many servers already active
I've also tried different variations on this (-R, etc), and using
qjackctl. I can't find any other jack processes ("ps aux | grep jack"
shows nothing). I get the same thing right after rebooting. Alsa seems
to be working (aplay, etc). Can anyone give some advice?
thanks.
30 Sep
30 Sep
9:15 p.m.
Ken Schutte wrote:
I used to have jack working fine on my system, but
lately strange things
have been happening. Right now when I try:
jackd -v -d alsa
I get,
too many servers already active
I've also tried different variations on this (-R, etc), and using
qjackctl. I can't find any other jack processes ("ps aux | grep jack"
shows nothing). I get the same thing right after rebooting. Alsa seems
to be working (aplay, etc). Can anyone give some advice?
I had a similar problem before - I think it happened after my machine
had been powered off without shutting down (not my fault!)
I solved the problem by deleting a pair of temporary jack files
somewhere, and then rebooting.
I think they are jack buffer files. Try to do a 'locate fifo'.
I'll have a look for them in the morning and post back.
Michael
9:38 p.m.
Michael T D Nelson wrote:
Ken Schutte wrote:
I did find two files that I tried deleting:
~/.qt/.qjackctlrc.lock
/var/lock/subsys/alsasound
Initialy I was getting the same error, but after rebooting now it works!
Thanks!
Well, I shouldn't say it's now working... now I'm getting:
required capabilities not available
capabilities: = cap_ipc_lock,cap_sys_nice,cap_sys_resource+e
within the qjackctl messages on start.
But, I guess this is unrelated, so I'll have to look into this now...
thanks again.
I used to have jack working fine on my system,
but lately strange
things have been happening. Right now when I try:
jackd -v -d alsa
I get,
too many servers already active
I had a similar problem before - I think it happened after my machine
had been powered off without shutting down (not my fault!)
I solved the problem by deleting a pair of temporary jack files
somewhere, and then rebooting.
I think they are jack buffer files. Try to do a 'locate fifo'.
I'll have a look for them in the morning and post back.
Michael 
10:49 p.m.
> I think they are jack buffer files. Try to do a
'locate fifo'.
typically in /tmp/jack-* or /dev/shm/jack/tmp or some similar location.
I did find two files that I tried deleting:
~/.qt/.qjackctlrc.lock
/var/lock/subsys/alsasound
neither one is related.
Initialy I was getting the same error, but after
rebooting now it works!
Thanks!
Well, I shouldn't say it's now working... now I'm getting:
required capabilities not available
capabilities: = cap_ipc_lock,cap_sys_nice,cap_sys_resource+e
within the qjackctl messages on start.
But, I guess this is unrelated, so I'll have to look into this now...
it is unrelated. what kernel version are you running and what jack
startup command are you using?
--p
11:48 p.m.
Paul Davis wrote:
Okay. I guess somehow on more reboot did it then...
2.6.10-2.1.ll.rhfc3.ccrma
jackd version 0.99.36
I've been trying a bunch of ways to start jack from command line and
qjackctl. If I simply do "jackstart -d alsa", I get:
jackstart: cannot get realtime capabilities, current capabilities are:
=ep cap_setpcap-ep
probably running under a kernel with capabilities disabled,
a suitable kernel would have printed something like "=eip"
back from read, ret = 1 errno == Success
jackstart: could not give capabilities: Operation not permitted
jackd 0.99.36
Copyright 2001-2003 Paul Davis 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
JACK compiled with System V SHM support.
loading driver ..
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
nperiods = 2 for capture
nperiods = 2 for playback
I've been trying some different input and output devices in qjackctl,
but nothing seems to work. Things used to work with all the defaults,
and I'm not sure what I changed, so I'm not sure what happened...
I did find two files that I tried deleting:
~/.qt/.qjackctlrc.lock
/var/lock/subsys/alsasound
neither one is related.
Initialy I was getting the same error, but after
rebooting now it works!
Thanks!
Well, I shouldn't say it's now working... now I'm getting:
required capabilities not available
capabilities: = cap_ipc_lock,cap_sys_nice,cap_sys_resource+e
within the qjackctl messages on start.
But, I guess this is unrelated, so I'll have to look into this now...
it is unrelated. what kernel version are you running and what jack
startup command are you using?
1 Oct
1 Oct
10:22 a.m.
it is
unrelated. what kernel version are you running and what jack
startup command are you using?
2.6.10-2.1.ll.rhfc3.ccrma
jackd version 0.99.36
I've been trying a bunch of ways to start jack from command line and
qjackctl. If I simply do "jackstart -d alsa", I get: 
10:32 a.m.
On Sat, 01 Oct 2005 08:23:27 -0400
Paul Davis <paul(a)linuxaudiosystems.com> wrote:
i don't know how to make it more obvious that jackstart is not intended
for use with 2.6 series kernel. maybe jackstart should try to detect the
kernel version and exit if it is not 2.4 or lower.
if you want to use JACK with the -R (realtime) flag on a 2.6 kernel then
you either need an absolutely totally up to the minute kernel and user
space utilities (bash, pam, glibc etc), or you need the realtime-lsm
module.
Maybe simply by making the error message more verbose:
--- jackstart.c.orig 2005-10-01 14:29:23.000000000 +0200
+++ jackstart.c 2005-10-01 14:31:24.000000000 +0200
@@ -228,6 +228,8 @@
fprintf (stderr, " %s\n", cap_to_text(cap,
&size));
fprintf (stderr, " probably running under a kernel with
capabilities disabled,\n");
fprintf (stderr, " a suitable kernel would have printed something
like \"=eip\"\n\n");
+ fprintf (stderr, " jackstart is intended to be used with 2.4.x
kernels only.\n");
+ fprintf (stderr, " if you run a 2.6.x (or higher) kernel, please
see the FAQ on jackit.sf.net for more infos on how to run jackd with realtime
scheduling.\n");
}
/* check the executable, owner, permissions, md5 checksum */
Flo
--
Palimm Palimm!
http://tapas.affenbande.org
it is unrelated. what kernel version are you running
and what jack
startup command are you using?
2.6.10-2.1.ll.rhfc3.ccrma
jackd version 0.99.36
I've been trying a bunch of ways to start jack from command line and
qjackctl. If I simply do "jackstart -d alsa", I get:
6987
days inactive
6988
days old
linux-audio-user@lists.linuxaudio.org
6 comments
4 participants
participants (4)
-
Florian Schmidt -
Ken Schutte -
Michael T D Nelson -
Paul Davis