| Re: [proaudio] jackd refuses realtime - it used to work? |
[ Thread Index |
Date Index
| More lists.tuxfamily.org/proaudio Archives
]
- To: proaudio@xxxxxxxxxxxxxxxxxxx
- Subject: Re: [proaudio] jackd refuses realtime - it used to work?
- From: Dominique Michel <dominique.michel@xxxxxxxxxxxx>
- Date: Fri, 16 Feb 2007 12:06:24 +0100
- Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwBAMAAAClLOS0AAAAJFBMVEXy8ubtkoXo7+b1+fbN cGKCeWDtamweFA8eMkmKPkPtvcWRoqyV0Pn7AAACbElEQVQ4jXXTMWvbQBQA4MOlizsdXEXp KAi09mKcLZ0EJxONDRJVkikg9AtqTm63gtHDmVJs1GsnC0JiaTMJGN2f67uzznJb+gZj9PFO 7717IqdtvCAmem4bxMLp/2BEyEBF1+U/0H8uhI6rv+BVLNrY/gH9T0L8yAxk2yMY3YuZxDCn TY/gpBByyTGktIcZOIvFjPNJmqYJDwrx3cIoBrE0zzG4FF8tfBAwM+DonKCYWjgROZ6Upjcm 5Qje58JAmlKKGfIAjzaDUuogZBY2Bjg14eDbywMIqZvwqgqFBcVFB0seYONLb00ZZlh4p0F6 FHNoUMyKAzxowJSQTyj+XloYs3MN3GeMpzyYSTMshLM00ODpWlPp4SDbqs4cViDcGAgmlK/a PsaOg7DvIQ3wzANMqB/iQW/XTkoTLO6XhSeHUoQKe+NLjyY/Ldx7CW2D4WTYhZ3V0GP64RpP Q/E66IUWMLj3+nDn4w2ejMACyXFeHZy6ETcZehc49bv1GQ/0bazNuzm97mDkhnoie9i30WYM w/YCnYT7Fx308s98n0IT//Jod1+aOzdzYXLVbftol+PC+REG3u+0AxdEtuSMB6G+DLGwMH4E vXGmJn8VCLM9LhmrOAMQYt5Wi/DFgIC52iFkUzMpDVmjAaDZRGC+JGwDqzJ/G5fUUcWZAaE7 YfvPLYtIU1Wb4A2IeS7uDMgcIFutiCr766qGfKHyuxvTIERKXVNSN27lDgCuBuojlpxIyJV6 ritS1uWWuHF2Ww7qcIKbqEFVNbmtmm3vGSCHbVXjikrY3SpVxwQWw2aIjwG+ueXTJDmHeK6a HfwGyU5ZSlGeSRQAAAAASUVORK5CYII=
Le Fri, 16 Feb 2007 00:58:29 +0100,
Johan Ekenberg <johan@xxxxxxxxxxx> a écrit :
> Hi!
>
> 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_Kernel
>
> 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.
>
> /Johan Ekenberg - Sweden
Hej Johan !
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
If you are using older kernel too, you can have 2 lines, one for realtime, the
other for realcap. It will work, you will only get an error message for the non
existing one with the kernel you are booting.
I have not changed anything in /etc/modules.d/realtime. It is still
options realtime gid=18
and it seem to work. It look like I can remove that line anyway as I am
using /etc/modules.autoload.d/kernel-2.6 for that.
PAM-rlimits and realcap (or realtime) will not conflict because PAM-rlimits
will take control over the realcap module. So it make no sens to use both and
is better to configure and use only one of them.
Ciao,
Dominique