Hi Karsten, I've done all of that, and checked multiple times. I'll try again with your values, but I'm anticipating the same problem.
Thanks, Grant Hi Grant, > > the problem is you need to set up /etc/security/limits.conf to allow > you to create processes with realtime permission. Its easy: add this > line at the end of the file, log out and back in and you should be > fine. > > @audio - rtprio 99 > @audio - memlock unlimited > @audio - nice -19 > > ah, make sure you are part of 'audio' group too (which you probably > are if you already can use audio devices without rt-prio). > > Greetings, > > Karsten > grant centauri said : >* Hello. *>* *>* I'm not entirely new to Pure:Dyne, and I've been hacking around with linux for *>* over 2 years now so I'm generally able to solve problems on my own, with help *>* of internet discussion of course, but I can't seem to get this one. *>* *>* I have the same problem on another machine I've tried installing a realtime *>* kernel on as well. *>* *>* I followed the instructions for a full install of pure:dyne; fresh debian *>* install, updated repositories, updated apt, downloaded the realtime kernel *>* (2.6.29.3-rt14-pure-686 #1 SMP PREEMPT RT), booted into it and uninstalled the *>* standard kernel, and proceeded to install all of the pure:dyne standard *>* packages. *>* *>* Once that was done I thought I'd try to start up jack in realtime and play *>* around a bit to make sure things worked. However when I try to start jack I *>* get this error message (the same as on the other machine with a realtime *>* kernel, these are kernels I did NOT compile myself, but downloaded from *>* repositories): *>* *>* JACK compiled with System V SHM support. *>* cannot use real-time scheduling (FIFO at priority 10) [for thread -1212373328, *>* from thread -1212373328] (1: Operation not permitted) *>* cannot create engine *>* *>* If I run the same command as root, jack starts fine. So the realtime *>* capabilities seem to be there. I know the first answer will be "Edit your /etc *>* /security/limits.conf and add the @audio rtprio and so on..." I've done this, *>* and it doesn't help. I think it has something to do with memory, and not the *>* audio preemption. The only relevant thing I could find had something to do *>* with the realtime_lsm module, which I tried building for this kernel, but it *>* didn't work. So I'm really unsure of what to do here. When I run modprobe, I *>* don't get any results for a realtime module of any kind. But why wouldn't the *>* pure:dyne kernel be compiled correctly to support realtime? I just don't get *>* it. Perhaps its a simple permissions problem (something to do with /dev/shm?) *>* but I can't figure it out. If anyone has any insights or advice, please let me *>* know. I'd love to have realtime capabilities without using a liveCD. *>* *>* Thanks, *>* *>* Grant *>* *>* *
--- [email protected] irc.goto10.org #puredyne
