| Re: [proaudio] jackd refuses realtime - it used to work? |
[ Thread Index |
Date Index
| More lists.tuxfamily.org/proaudio Archives
]
On Friday 16 February 2007 12:06, Dominique Michel wrote:
> Le Fri, 16 Feb 2007 00:58:29 +0100,
> Johan Ekenberg <johan@xxxxxxxxxxx> a écrit :
> > Using 2.6.19-rt15, realtime-lsm and jack 0.102.20, I did a lot of audio
> > programming a few months back. Now I'm trying to continue where I left
> > off, but jackd refuses to run with -R.
> >
> > "required capabilities not available"?
> > realtime-lsm is loaded, it's the same kernel and jackd as before. I'm in
> > the audio-group as always.
> >
> > When running as root, it also stops after "waiting for signals":
> > ===
> > root@duo:/home/johan# jackd -v -R -d alsa
> > < the same as above until: >
> > running with uid=0 and euid=0, will not try to use capabilites
> > < again as above until: >
> > 8107 waiting for signals
> > ==> <again the ~5 second delay>
> > jackd watchdog: timeout - killing jackd
> > Aborted
> > ===
> >
> > Yes, audio using ALSA still works normally. The hardware has not changed.
> > The system is configured according to
> > http://proaudio.tuxfamily.org/wiki/index.php?title=Realtime_%28RT%29_Kern
> >el
> >
> > I never actively tried to use PAM/RLIMITS, but I see
> > that /etc/security/limits.conf has: # REALTIME support for audio group
> > users @audio - rtprio 100
> > @audio - nice -10
> > @audio - memlock 250000
> >
> > Could this be causing a conflict with realtime-lsm? I tried rmmod
> > realtime and jackd -R but no improvement.
> With 2.6.19 kernel, the realtime-lsm name is realcap. So you have to change
> it in /etc/modules.autoload.d/kernel-2.6:
>
> realcap gid=18
Well, no. This is only true if you use the realtime-module from the kernel. I
emerged realtime-lsm from portage, and then it's still called realtime. And
yes, I also tried the realcap-version from the kernel. I also tried a number
of older kernels from 2.6.16 - 2.6.18 both with the portage realtime-lsm and
the module from the kernel, but the problem described above persists.
The problem here is something else, not related to the exact version of the
kernel or realtime-module.
Please note that it does NOT work when running as root, so it also has nothing
to do with misconfiguration of gid för realtime/realcap etc.
I'm still stuck. Stracing just shows jackd starting a few threads,
say "waiting for signals", polling /dev/snd/pcmC0D0[pc] for a few seconds and
then giving up with a few hundred XRUNs.
Please audio gurus, help!
/Johan