12 Mar
2007
12 Mar
'07
11:36 a.m.
On 3/12/07, Atte André Jensen <atte.jensen(a)gmail.com> wrote:
Hi
I had realtime working just fine (debian/etch, 2.6.18-rt8), but now it
doesn't. And i can't figure out why...
When I start qjackctl I get this in messages:
cannot use real-time scheduling (FIFO at priority 10) [for thread
-1210070368, from thread -1210070368] (1: Operation not permitted)
atte@ajstrup:~$ grep -v '#' /etc/security/limits.conf
@audio - rtprio 99
@audio - memlock 500000
@audio - nice -10
atte@ajstrup:~$ grep atte /etc/group
dialout:x:20:atte,emil,britt
cdrom:x:24:atte,emil,britt
floppy:x:25:atte,emil,britt
audio:x:29:atte,emil,britt
video:x:44:atte,emil,britt
plugdev:x:46:atte,emil,britt
atte:x:1000:
atte@ajstrup:~$ sudo apt-get install libpam0g
Reading package lists... Done
Building dependency tree... Done
libpam0g is already the newest version.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Hi,
Hehehe, I had the same one this week-end. What happened for me is that
I used to run jackd only after login in with gdm. this week end I
tried launching it by login on a console (thus with the "login"
program) and I couldn't get realtime to work (with the same message).
check your configuration in /etc/pam.d : gdm, login and kdm should
include a line with something like :
session required /lib/security/pam_limits.so
Before this week, only /etc/pam.d/gdm had this line on my setup.
One last piece of advice : when modifying /etc/pam.d/login, be sure to
leave one console open, while testing your ability to login on
another. if you make a Big Mistake (TM) and logout, you won't be able
to login again (via login only of course, gdm/kdm/xdm should work).
Cheer,
__________________
Marc-Olivier Barre,
Markinoko.