19 Jun
2006
19 Jun
'06
4:51 p.m.
Konichiwa!!
This has been bothering me for some time. I cannot, for the life of me,
run the muse sequencer with full real time (RT) capabilities.
I use Slackware 10.2 and a 2.6.15.6 kernel that has RT capabilities
compiled in.
I start qjackctl which, in turn, starts the jack daemon (jackd) with
RT enabled, which is indicated in qjackctl GUI (letters RT showing!!).
But, then when I fire up muse I get this:
Trying RTC timer...
got timer = 14
showMarker 0
tickValues(0x41d3a21) not found(1)
tickValues(0x41d3a21) not found(1)
3set realtime scheduler: Operation not permitted
watchdog process 22391 _NOT_ running SCHED_FIFO
JACK ERROR: cannot lock down memory for RT thread (Cannot allocate memory)
JACK ERROR: cannot use real-time scheduling (FIFO at priority 9) [for
thread -1284142160, from thread -1284142160] (1: Operation not
permitted)
error set_schedparam 2:: Operation not permitted
set realtime scheduler: Operation not permitted
midi thread 22391 _NOT_ running SCHED_FIFO
JACK thread not running SCHED_FIFO, try to set...
set realtime scheduler: Operation not permitted
JACK still not running FIFO !?!
======reliable RT operation not possible!!======
I tried setting the permissions on the /dev/rtc device so that
regular users can have access, it didn't help. What could be the
issue here, I probably misconfigured or am missing something.
Please help.
Hiram
--
http://www.egoboobits.net/HiramAbiff
19 Jun
19 Jun
5 p.m.
On Mon, 2006-06-19 at 20:51 +0200, Hiram Abiff wrote:
This has been bothering me for some time. I cannot,
for the life of
me, run the muse sequencer with full real time (RT) capabilities.
I use Slackware 10.2 and a 2.6.15.6 kernel that has RT capabilities
compiled in.
I don't know what you mean by "RT capabilities". Are you using the
realtime LSM module? What options are you loading it with? Is your
user in the audio group?
Lee
5:59 p.m.
On 6/19/06, Hiram Abiff <domain.admin(a)online.ie> wrote:
Konichiwa!!
This has been bothering me for some time. I cannot, for the life of me,
run the muse sequencer with full real time (RT) capabilities.
I use Slackware 10.2 and a 2.6.15.6 kernel that has RT capabilities
compiled in.
I start qjackctl which, in turn, starts the jack daemon (jackd) with
RT enabled, which is indicated in qjackctl GUI (letters RT showing!!).
But, then when I fire up muse I get this:
Trying RTC timer...
got timer = 14
showMarker 0
tickValues(0x41d3a21) not found(1)
tickValues(0x41d3a21) not found(1)
3set realtime scheduler: Operation not permitted
watchdog process 22391 _NOT_ running SCHED_FIFO
JACK ERROR: cannot lock down memory for RT thread (Cannot allocate memory)
JACK ERROR: cannot use real-time scheduling (FIFO at priority 9) [for
thread -1284142160, from thread -1284142160] (1: Operation not
permitted)
error set_schedparam 2:: Operation not permitted
set realtime scheduler: Operation not permitted
midi thread 22391 _NOT_ running SCHED_FIFO
JACK thread not running SCHED_FIFO, try to set...
set realtime scheduler: Operation not permitted
JACK still not running FIFO !?!
======reliable RT operation not possible!!======
I tried setting the permissions on the /dev/rtc device so that
regular users can have access, it didn't help. What could be the
issue here, I probably misconfigured or am missing something.
Please help.
Hiram
Hiram,
There are a few things to discover:
1) Are you running Jack as root or a user?
- First, try running Jack as root and see if these problems go away.
2) Assuming you run as root without problems then the issue here is
probably one of permissions. However it is not /dev/rtc that needs to
be changed. Infact, nothing in /dev should be changed for this to
work. You either need to install the realtime-lsm package, create a
realtime group, add yourself to that group, and then load the realtime
module telling it to grant realtime permissions to that group. For
this to work you need a kernel with Linux Capabilities enabled in the
security section of the .config file.
Alternatively there is a PAM based solution to this that is newer but
I haven't used it.
Hope this helps,
Mark
21 Jun
21 Jun
6:31 p.m.
Quoting Mark Knecht <markknecht(a)gmail.com>om>:
Hiram,
There are a few things to discover:
1) Are you running Jack as root or a user?
- First, try running Jack as root and see if these problems go away.
Gruß Dich, Mark
I tried running it as root, works great.
2) Assuming you run as root without problems then the
issue here is
probably one of permissions. However it is not /dev/rtc that needs to
be changed. Infact, nothing in /dev should be changed for this to
work. You either need to install the realtime-lsm package, create a
realtime group, add yourself to that group, and then load the realtime
module telling it to grant realtime permissions to that group. For
this to work you need a kernel with Linux Capabilities enabled in the
security section of the .config file.
I recompiled my kernel with the required module, I created a realtime
group, added my user to it and loaded the module. lsmod reports
it's loaded. However, I still get the same error messages when running
muse. :(
I also noticed that when running qsampler with ALSA output, not JACK,
I get this in the messages window:
22:30:07.751 Channel 0 Some channel settings could not be set. Sorry.
Thread: WARNING, can't assign realtime scheduling to thread!: Operation
not permitted
Thread: WARNING, can't mlockall() memory!: Cannot allocate memory
Alternatively there is a PAM based solution to this that is newer but
I haven't used it.
Hope this helps,
Mark
It does.
Hiram.
--
http://www.egoboobits.net/HiramAbiff
6:46 p.m.
On Wed, 2006-06-21 at 22:30 +0200, Hiram Abiff wrote:
Quoting Mark Knecht <markknecht(a)gmail.com>om>:
How did you load the realtime module? You have to do "modprobe realtime
gid=$FOO" where $FOO is the number of your realtime group.
Also, you must log out and log back in for changes in group membership
to take effect.
Lee
Hiram,
There are a few things to discover:
1) Are you running Jack as root or a user?
- First, try running Jack as root and see if these problems go away.
Gruß Dich, Mark
I tried running it as root, works great.
2) Assuming you run as root without problems then
the issue here is
probably one of permissions. However it is not /dev/rtc that needs to
be changed. Infact, nothing in /dev should be changed for this to
work. You either need to install the realtime-lsm package, create a
realtime group, add yourself to that group, and then load the realtime
module telling it to grant realtime permissions to that group. For
this to work you need a kernel with Linux Capabilities enabled in the
security section of the .config file.
I recompiled my kernel with the required module, I created a realtime
group, added my user to it and loaded the module. lsmod reports
it's loaded. However, I still get the same error messages when running
muse. :(
I also noticed that when running qsampler with ALSA output, not JACK,
I get this in the messages window:
22:30:07.751 Channel 0 Some channel settings could not be set. Sorry.
Thread: WARNING, can't assign realtime scheduling to thread!: Operation
not permitted
Thread: WARNING, can't mlockall() memory!: Cannot allocate memory
Alternatively there is a PAM based solution to this that is newer but
I haven't used it.
Hope this helps,
Mark
It does.
Hiram.
7:34 p.m.
On 6/21/06, Hiram Abiff <domain.admin(a)online.ie> wrote:
Quoting Mark Knecht <markknecht(a)gmail.com>om>:
<SNIP>
Hiram,
There are a few things to discover:
1) Are you running Jack as root or a user?
- First, try running Jack as root and see if these problems go away.
Gruß Dich, Mark
I tried running it as root, works great.
I recompiled my kernel with the required module, I created a realtime
group, added my user to it and loaded the module. lsmod reports
it's loaded. However, I still get the same error messages when running
muse. :(
It may be the way you are loading the realtime module. Here's how I do
it at boot time on my Gentoo box in /etc/modules.autoload/kernel-2.6:
realtime gid=600 any=1
and here is how I set up my group:
mark@lightning ~ $ cat /etc/group | grep realtime
realtime:x:600:mark
mark@lightning ~ $
Nothing more than that and I work fine.
lightning ~ # modinfo realtime
filename: /lib/modules/2.6.17-rt1/extra/realtime.ko
license: GPL
description: Realtime Capabilities Security Module
vermagic: 2.6.17-rt1 preempt mod_unload gcc-3.4
license: GPL
description: Standard Linux Common Capabilities Security Module
depends:
vermagic: 2.6.17-rt1 preempt mod_unload gcc-3.4
parm: any: grant realtime privileges to any process. (int)
parm: gid: the group ID with access to realtime privileges. (int)
parm: mlock: enable memory locking privileges. (int)
lightning ~ #
Hope this helps,
Mark
And here is houw I
23 Jun
23 Jun
6:58 p.m.
Mark Knecht escribió:
On 6/21/06, Hiram Abiff <domain.admin(a)online.ie>
wrote:
With ubuntu and 2.6.17-rt1 I load it in this way
realtime gid=29 wich is the audio group
Saludos.
--Carlos.
Quoting Mark Knecht
<markknecht(a)gmail.com>om>:
<SNIP>
Hiram,
There are a few things to discover:
1) Are you running Jack as root or a user?
- First, try running Jack as root and see if these problems go away.
Gruß Dich, Mark
I tried running it as root, works great.
I recompiled my kernel with the required module, I created a realtime
group, added my user to it and loaded the module. lsmod reports
it's loaded. However, I still get the same error messages when running
muse. :(
It may be the way you are loading the realtime module. Here's how I do
it at boot time on my Gentoo box in /etc/modules.autoload/kernel-2.6:
realtime gid=600 any=1
and here is how I set up my group:
mark@lightning ~ $ cat /etc/group | grep realtime
realtime:x:600:mark
mark@lightning ~ $
Nothing more than that and I work fine.
lightning ~ # modinfo realtime
filename: /lib/modules/2.6.17-rt1/extra/realtime.ko
license: GPL
description: Realtime Capabilities Security Module
vermagic: 2.6.17-rt1 preempt mod_unload gcc-3.4
license: GPL
description: Standard Linux Common Capabilities Security Module
depends:
vermagic: 2.6.17-rt1 preempt mod_unload gcc-3.4
parm: any: grant realtime privileges to any process. (int)
parm: gid: the group ID with access to realtime privileges.
(int)
parm: mlock: enable memory locking privileges. (int)
lightning ~ #
Hope this helps,
Mark
And here is houw I
25 Jun
25 Jun
11:23 a.m.
Quoting Carlos Pino <pinojazz(a)gmail.com>om>:
Mark Knecht escribió:
Hi!
Thanx for the help everyone, I load the modprobe with the following
parameters and it works:
modprobe realtime gid=500 any=1 mlock=1
--
http://www.egoboobits.net/HiramAbiff
On 6/21/06, Hiram Abiff
<domain.admin(a)online.ie> wrote:
With ubuntu and 2.6.17-rt1 I load it in this way
realtime gid=29 wich is the audio group
Saludos.
--Carlos.
Quoting Mark Knecht
<markknecht(a)gmail.com>om>:
<SNIP>
Hiram,
There are a few things to discover:
1) Are you running Jack as root or a user?
- First, try running Jack as root and see if these problems go away.
Gruß Dich, Mark
I tried running it as root, works great.
I recompiled my kernel with the required module, I created a realtime
group, added my user to it and loaded the module. lsmod reports
it's loaded. However, I still get the same error messages when running
muse. :(
It may be the way you are loading the realtime module. Here's how I do
it at boot time on my Gentoo box in /etc/modules.autoload/kernel-2.6:
realtime gid=600 any=1
and here is how I set up my group:
mark@lightning ~ $ cat /etc/group | grep realtime
realtime:x:600:mark
mark@lightning ~ $
Nothing more than that and I work fine.
lightning ~ # modinfo realtime
filename: /lib/modules/2.6.17-rt1/extra/realtime.ko
license: GPL
description: Realtime Capabilities Security Module
vermagic: 2.6.17-rt1 preempt mod_unload gcc-3.4
license: GPL
description: Standard Linux Common Capabilities Security Module
depends:
vermagic: 2.6.17-rt1 preempt mod_unload gcc-3.4
parm: any: grant realtime privileges to any process. (int)
parm: gid: the group ID with access to realtime privileges. (int)
parm: mlock: enable memory locking privileges. (int)
lightning ~ #
Hope this helps,
Mark
And here is houw I
20 Jun
20 Jun
11:05 p.m.
New subject: [linux-audio-user] Re: RT and Jack problems
As far as I know MusE authors admit to it being rather unstable, so this
might be the reason.
I know setting the muse exectutable 'setuid' works, however I would
recommend simply using seq24 for MIDI and Ardour for Audio (MIDI support
for Ardour is coming up).
Carlo
11:08 p.m.
New subject: [linux-audio-user] Re: RT and Jack problems
On Wed, 2006-06-21 at 03:03 +0200, Carlo Capocasa wrote:
As far as I know MusE authors admit to it being rather
unstable, so this
might be the reason.
I know setting the muse exectutable 'setuid' works, however I would
recommend simply using seq24 for MIDI and Ardour for Audio (MIDI support
for Ardour is coming up).
No, the reason is that his setup does not support non-root realtime.
Just use the realtime LSM.
Lee
6801
days inactive
6807
days old
linux-audio-user@lists.linuxaudio.org
10 comments
5 participants
participants (5)
-
Carlo Capocasa -
Carlos Pino -
Hiram Abiff -
Lee Revell -
Mark Knecht