24 Mar
2007
24 Mar
'07
7:18 p.m.
I'm following the directions on the wiki for the RT kernel at:
http://proaudio.tuxfamily.org/wiki/index.php?title=Realtime_%28RT%29_Kernel
and I'm at the point of modprobe'ing the realtime module in the
instructions which say:
-----------------
load realtime-lsm
# modprobe commoncap
# modprobe realtime gid=18
-----------------
But, I receive this error:
FATAL: Error inserting realtime
(/lib/modules/2.6.16-rt29-tglx4/extra/realtime.ko): Invalid module format--
when modprobe'ing the "realtime" module.
Why is this? The kernel and the module were compiled with the same tools.
Michel Dominique in the gentoo audio forum suggested to
# make mrproper"
# make oldconfig; make
# remove /lib/modules/2.6.16-rt-tglx4
# make modules_install
reinstall the kernel and reinstall realtime-lsm
but that didn't change anything.
===
Maybe some hints:
I find that if I rmmod commoncap and then modprobe realtime it works,
realtime loads with no error. However, when I then modprobe commoncap
(with "realtime" already in) I receive the same error as I do above:
FATAL: Error inserting commoncap
(/lib/modules/2.6.16-rt29-tglx4/kernel/security/commoncap.ko): Invalid
module format
I don't know if order is an issue for the loading of these two modules,
but I don't know what the problem is.
With the realtime module loaded and no commoncap, audio plays but is
very very slow.
Any one have any ideas on this?
--
brad fuller
http://www.Sonaural.com/
+1 (408) 799-6124
25 Mar
25 Mar
4:01 p.m.
On 3/25/07, Brad Fuller <brad(a)sonaural.com> wrote:
I'm following the directions on the wiki for the
RT kernel at:
http://proaudio.tuxfamily.org/wiki/index.php?title=Realtime_%28RT%29_Kernel
and I'm at the point of modprobe'ing the realtime module in the
instructions which say:
-----------------
load realtime-lsm
# modprobe commoncap
# modprobe realtime gid=18
-----------------
But, I receive this error:
FATAL: Error inserting realtime
(/lib/modules/2.6.16-rt29-tglx4/extra/realtime.ko): Invalid module format--
when modprobe'ing the "realtime" module.
Why is this? The kernel and the module were compiled with the same tools.
Hi Brad,
You may have not seen it but on the wiki you pointed to, in the part
called "Activate and test RT" the realtime-lsm module is marked as
deprecated. if you go a little further in the document you will find a
section called "RLIMITS" (right after the realtime-lsm one).
The currently recommended method to get realtime to work is to use the
rlimits method with PAM, which you should normally have on your
system. It will make things a lot easier for you.
The tutorial might be taking some shortcuts (depending on your
configuration). If after following the tutorial's info it still
doesn't work, try the following :
- check that your user is part of the audio group
- from a terminal, type in the following command :
grep "pam_limits.so" /etc/pam.d/{gdm,kdm,xdm,login} 2> /dev/null
you should see lines like this :
/etc/pam.d/login:session required pam_limits.so
In this example, the file named /etc/pam.d/login contains the modules
used by pam when you authenticate with the login program. The line
that appeared (normally) on your screen states that the pam_limits.so
module will be used. That's the one you want.
Please give us some feedback on how it went and ask again if it didn't work.
Cheers,
__________________
Marc-Olivier Barre,
Markinoko.
4:59 p.m.
Marc-Olivier Barre wrote:
On 3/25/07, Brad Fuller <brad(a)sonaural.com>
wrote:
CRAP! I simply didn't see that! Thanks for the reply and thanks for
pointing this out!
I'm following the directions on the wiki for
the RT kernel at:
http://proaudio.tuxfamily.org/wiki/index.php?title=Realtime_%28RT%29_Kernel
and I'm at the point of modprobe'ing the realtime module in the
instructions which say:
-----------------
load realtime-lsm
# modprobe commoncap
# modprobe realtime gid=18
-----------------
But, I receive this error:
FATAL: Error inserting realtime
(/lib/modules/2.6.16-rt29-tglx4/extra/realtime.ko): Invalid module
format--
when modprobe'ing the "realtime" module.
Why is this? The kernel and the module were compiled with the same
tools.
Hi Brad,
You may have not seen it but on the wiki you pointed to, in the part
called "Activate and test RT" the realtime-lsm module is marked as
deprecated. if you go a little further in the document you will
find a
section called "RLIMITS" (right after the realtime-lsm one).
The currently recommended method to get realtime to work is to use the
rlimits method with PAM, which you should normally have on your
system. It will make things a lot easier for you.
The tutorial might be taking some shortcuts (depending on your
configuration). If after following the tutorial's info it still
doesn't work, try the following :
- check that your user is part of the audio group
- from a terminal, type in the following command :
grep "pam_limits.so" /etc/pam.d/{gdm,kdm,xdm,login} 2> /dev/null
Aha,
well. I have it none.
How would this get added?
you should see lines like this :
/etc/pam.d/login:session required pam_limits.so
In this example, the file named /etc/pam.d/login contains the modules
used by pam when you authenticate with the login program. The line
that appeared (normally) on your screen states that the pam_limits.so
module will be used. That's the one you want.
Please give us some feedback on how it went and ask again if it didn't
work.
Cheers,
__________________
Marc-Olivier Barre,
Markinoko.
--
brad fuller
http://www.Sonaural.com/
+1 (408) 799-6124
5:34 p.m.
On Sun, Mar 25, 2007 at 11:45:05AM -0700, Brad Fuller wrote:
Add the line
session required pam_limits.so
to the appropriate file, where appropriate means what you are using; so
when using gdm, add it to /etc/pam.d/gtk. After logging out and logging
in again, it should work.
Burkhard
- check that your user is part of the audio group
- from a terminal, type in the following command :
grep "pam_limits.so" /etc/pam.d/{gdm,kdm,xdm,login} 2> /dev/null
Aha,
well. I have it none.
How would this get added?
5:59 p.m.
Brad Fuller wrote:
Marc-Olivier Barre wrote:
well... I just went ahead and added the line:
session required pam_limits.so
in /etc/pam.d/xdm, login and gdm
Which didn't seem to make a difference to my other problem.
Note that booting produces no errors. My audio device driver loads fine
and initializes. Everything seems fine, except
1. Audio plays back very slowly. Video files play at various speeds
(fast then slow then fast, etc.)
2. Running qjackctl I receive the warning that real-time scheduling is
not permed and then I continuously receive delay errors:
----
12:30:12.271 Startup script...
12:30:12.272 artsshell -q terminate
12:30:12.595 Startup script terminated with exit status=256.
12:30:12.602 JACK is starting...
12:30:12.602 /usr/bin/jackd -R -p256 -dalsa -dhw:0 -r44100 -p1024 -n2 -m
12:30:12.610 JACK was started with PID=6349 (0x18cd).
jackd 0.101.1
Copyright 2001-2005 Paul Davis and others.
jackd comes with ABSOLUTELY NO WARRANTY
This is free software, and you are welcome to redistribute it
under certain conditions; see the file COPYING for details
JACK compiled with System V SHM support.
loading driver ..
apparent rate = 44100
creating alsa driver ... hw:0|hw:0|1024|2|44100|0|0|nomon|swmeter|-|32bit
control device hw:0
configuring for 44100Hz, period = 1024 frames, buffer = 2 periods
nperiods = 2 for capture
nperiods = 2 for playback
cannot use real-time scheduling (FIFO at priority 20) [for thread
-1229620336, from thread -1229620336] (1: Operation not permitted)
cannot use real-time scheduling (FIFO at priority 10) [for thread
-1238013040, from thread -1238013040] (1: Operation not permitted)
12:30:14.628 Server configuration saved to "/home/bfuller/.jackdrc".
12:30:14.630 Statistics reset.
12:30:14.805 Client activated.
12:30:14.817 Audio connection change.
12:30:14.825 Audio connection graph change.
cannot use real-time scheduling (FIFO at priority 9) [for thread
-1232647280, from thread -1232647280] (1: Operation not permitted)
12:30:20.362 XRUN callback (1).
delay of 104670.000 usecs exceeds estimated spare time of 21713.000;
restart ...
delay of 96148.000 usecs exceeds estimated spare time of 21713.000;
restart ...
delay of 104496.000 usecs exceeds estimated spare time of 21713.000;
restart ...
----
========================
I then went into alsamixer and noticed that
"Multi Track Internal Clock"
was set wrong. I changed it to 44.1k and now audio plays at a reasonable level.
Which, makes me think that I need to be able to change this on the fly.
Other audio files and video files do not play correctly because it is stuck on 44.1k.
I can't seem to change "Multi Track Rate Locking" and "Multi Track Rate
Reset".
==================================
After setting "Multi Track Internal Clock" jackd worked better but still no
real-time.
----
loading driver ..
apparent rate = 44100
creating alsa driver ... hw:0|hw:0|1024|2|44100|0|0|nomon|swmeter|-|32bit
control device hw:0
configuring for 44100Hz, period = 1024 frames, buffer = 2 periods
nperiods = 2 for capture
nperiods = 2 for playback
cannot use real-time scheduling (FIFO at priority 20) [for thread -1228780656, from thread
-1228780656] (1: Operation not permitted)
cannot use real-time scheduling (FIFO at priority 10) [for thread -1237173360, from thread
-1237173360] (1: Operation not permitted)
12:55:07.717 Server configuration saved to "/home/bfuller/.jackdrc".
12:55:07.720 Statistics reset.
12:55:07.723 Client activated.
12:55:07.727 Audio connection change.
12:55:07.734 Audio connection graph change.
subgraph starting at qjackctl-6564 timed out (subgraph_wait_fd=15, status = 0, state =
Triggered)
**** alsa_pcm: xrun of at least 1.605 msecs
cannot use real-time scheduling (FIFO at priority 9) [for thread -1232909424, from thread
-1232909424] (1: Operation not permitted)
12:55:07.806 XRUN callback (1).
----
Any help on: pointers on getting real-time to work AND for applications to set the clock
of the audio device is much appreciated!
On 3/25/07, Brad Fuller <brad(a)sonaural.com>
wrote:
CRAP! I simply didn't see that! Thanks for the reply and thanks for
pointing this out!
I'm following the directions on the wiki for
the RT kernel at:
http://proaudio.tuxfamily.org/wiki/index.php?title=Realtime_%28RT%29_Kernel
and I'm at the point of modprobe'ing the realtime module in the
instructions which say:
-----------------
load realtime-lsm
# modprobe commoncap
# modprobe realtime gid=18
-----------------
But, I receive this error:
FATAL: Error inserting realtime
(/lib/modules/2.6.16-rt29-tglx4/extra/realtime.ko): Invalid module
format--
when modprobe'ing the "realtime" module.
Why is this? The kernel and the module were compiled with the same
tools.
Hi Brad,
You may have not seen it but on the wiki you pointed to, in the part
called "Activate and test RT" the realtime-lsm module is marked as
deprecated. if you go a little further in the document you
will find a
section called "RLIMITS" (right after the realtime-lsm one).
The currently recommended method to get realtime to work is to use the
rlimits method with PAM, which you should normally have on your
system. It will make things a lot easier for you.
The tutorial might be taking some shortcuts (depending on your
configuration). If after following the tutorial's info it still
doesn't work, try the following :
- check that your user is part of the audio group
- from a terminal, type in the following command :
grep "pam_limits.so" /etc/pam.d/{gdm,kdm,xdm,login} 2> /dev/null
Aha,
well. I have it none.
How would this get added?
6:21 p.m.
On 3/25/07, Brad Fuller <brad(a)sonaural.com> wrote:
Brad Fuller wrote:
Good. Did you check what the /var/log/auth.log file says after you've
logged in ? there could be some hints there.
Marc-Olivier Barre wrote:
well... I just went ahead and added the line:
session required pam_limits.so
in /etc/pam.d/xdm, login and gdm
On 3/25/07, Brad Fuller <brad(a)sonaural.com>
wrote:
CRAP! I simply didn't see that! Thanks for the reply and thanks for
pointing this out!
I'm following the directions on the wiki for
the RT kernel at:
http://proaudio.tuxfamily.org/wiki/index.php?title=Realtime_%28RT%29_Kernel
and I'm at the point of modprobe'ing the realtime module in the
instructions which say:
-----------------
load realtime-lsm
# modprobe commoncap
# modprobe realtime gid=18
-----------------
But, I receive this error:
FATAL: Error inserting realtime
(/lib/modules/2.6.16-rt29-tglx4/extra/realtime.ko): Invalid module
format--
when modprobe'ing the "realtime" module.
Why is this? The kernel and the module were compiled with the same
tools.
Hi Brad,
You may have not seen it but on the wiki you pointed to, in the part
called "Activate and test RT" the realtime-lsm module is marked as
deprecated. if you go a little further in the document you
will find a
section called "RLIMITS" (right after the realtime-lsm one).
The currently recommended method to get realtime to work is to use the
rlimits method with PAM, which you should normally have on your
system. It will make things a lot easier for you.
The tutorial might be taking some shortcuts (depending on your
configuration). If after following the tutorial's info it still
doesn't work, try the following :
- check that your user is part of the audio group
- from a terminal, type in the following command :
grep "pam_limits.so" /etc/pam.d/{gdm,kdm,xdm,login} 2> /dev/null
Aha,
well. I have it none.
How would this get added? Which didn't seem to make a difference to my other
problem.
Note that booting produces no errors. My audio device driver loads fine
and initializes. Everything seems fine, except
1. Audio plays back very slowly. Video files play at various speeds
(fast then slow then fast, etc.)
That video thing is weird, though I'm not sure it's realtime related
2. Running qjackctl I receive the warning that
real-time scheduling is
not permed and then I continuously receive delay errors:
Try running ulimit -l in a terminal to see if you get the same value
you've set in the /etc/security/limits.conf ( "-l" gives the memlock
parameter). If not, then the limits.conf file is not being taken into
account at login time.
Any help on: pointers on getting real-time to work AND
for applications to set the clock
of the audio device is much appreciated!
Before starting jack, you need to set the sample rate to what you
want. if you can do it with alsamixer, it means that it can be saved
and reloaded at boot time using alsactl. I supposed there is an init
script in gentoo that does it automatically at boot time (have a look
in /etc/init.d or /etc/rc.d/init.d, there should be a script called
"alsa" something)
__________________
Marc-Olivier Barre,
Markinoko.
6:33 p.m.
Marc-Olivier Barre wrote:
Hmm... no /var/log/auth.log file. This security stuff is new to me. Can
you tell me where I can force
pam (I assume that's who's writing the log) to write this log? I'll google.
I don't either, I think it is clock related. The video is following the
audio and the video player can't set the audio device clock. Thus, I
think it's related to setting the audio device's clock.
Yep, it's the same. That's good.
Right, that's why it worked when I set it to 44.1k (which was my
default)
well... I just went ahead and added the line:
session required pam_limits.so
in /etc/pam.d/xdm, login and gdm
Good. Did you check what the /var/log/auth.log file says after you've
logged in ? there could be some hints there. Which didn't seem to make a difference to my
other problem.
Note that booting produces no errors. My audio device driver loads fine
and initializes. Everything seems fine, except
1. Audio plays back very slowly. Video files play at various speeds
(fast then slow then fast, etc.)
That video thing is weird, though I'm not sure it's realtime related 2. Running qjackctl I receive the warning that
real-time scheduling is
not permed and then I continuously receive delay errors:
Try running ulimit -l in a terminal to see if you get the same value
you've set in the /etc/security/limits.conf ( "-l" gives the memlock
parameter). If not, then the limits.conf file is not being taken into
account at login time. Any help on: pointers on getting real-time to
work AND for
applications to set the clock
of the audio device is much appreciated!
Before starting jack, you need to set the sample rate to what you
want. if you can do it with alsamixer, it means that it can
be saved
and reloaded at boot time using alsactl.
Yeah... I've done that. But, still I would like to be able to have
external apps set the clock, right?
I supposed there is an init
script in gentoo that does it automatically at boot time (have a look
in /etc/init.d or /etc/rc.d/init.d, there should be a script called
"alsa" something)
yeah, it's /etc/init.d/alsasound in gentoo.
I appreciate your input, thanks!
brad
6:39 p.m.
On 3/25/07, Brad Fuller <brad(a)sonaural.com> wrote:
Yeah... I've done that. But, still I would like to
be able to have
external apps set the clock, right?
It can't work if JACK is running anyway because all clients are
required to support the server sample rate.
WRT realtime, last i heard was that Gentoo does not supply a new
enough version of PAM (0.80 or higher is required)
Lee
8:01 p.m.
Lee Revell wrote:
On 3/25/07, Brad Fuller <brad(a)sonaural.com>
wrote:
That I know.
Yeah... I've done that. But, still I would
like to be able to have
external apps set the clock, right?
It can't work if JACK is running anyway because all clients are
required to support the server sample rate.
WRT realtime, last i heard was that Gentoo does not supply a new
enough version of PAM (0.80 or higher is required)
that I don't know.
Bummer...
# equery which pam
/usr/portage/local/layman/pro-audio/sys-libs/pam/pam-0.78-r6.ebuild
Thanks... back to realtime-lsm
--
brad fuller
http://www.Sonaural.com/
+1 (408) 799-6124
8:55 p.m.
On So, 2007-03-25 at 14:59 -0700, Brad Fuller wrote:
Lee Revell wrote:
Hi,
pam-0.78-r6 should work. I use this version and jack runs with rt-prio.
Check your /etc/security/limits.conf for the right entries
# REALTIME support for audio group users
@audio - rtprio 100
@audio - nice -10
@audio - memlock 250000
You can also find up to date ebuilds for rt-kernels and audio software
in the pro-audio overlay. There you can set the use of realtime-lsm by
setting a USE variable but I'd suggest to go with pam. More information
can be found in the wiki:
http://proaudio.tuxfamily.org/wiki/index.php?title=Main_Page
Good luck
Martin
On 3/25/07, Brad Fuller <brad(a)sonaural.com>
wrote:
That I know.
Yeah... I've done that. But, still I would
like to be able to have
external apps set the clock, right?
It can't work if JACK is running anyway because all clients are
required to support the server sample rate.
WRT realtime, last i heard was that Gentoo does not supply a new
enough version of PAM (0.80 or higher is required)
that I don't know.
Bummer...
# equery which pam
/usr/portage/local/layman/pro-audio/sys-libs/pam/pam-0.78-r6.ebuild
Thanks... back to realtime-lsm
9:54 p.m.
Martin Wohlleben wrote:
On So, 2007-03-25 at 14:59 -0700, Brad Fuller wrote:
Well... it's good to know that version should work. I made sure I had
it. The entries are the same.
Lee Revell wrote:
Hi,
pam-0.78-r6 should work. I use this version and jack runs with rt-prio.
Check your /etc/security/limits.conf for the right entries
On 3/25/07, Brad Fuller <brad(a)sonaural.com>
wrote:
That I know.
Yeah... I've done that. But, still I would
like to be able to have
external apps set the clock, right?
It can't work if JACK is running anyway because all clients are
required to support the server sample rate.
WRT realtime, last i heard was that Gentoo does
not supply a new
enough version of PAM (0.80 or higher is required)
that I don't know. Bummer...
# equery which pam
/usr/portage/local/layman/pro-audio/sys-libs/pam/pam-0.78-r6.ebuild
Thanks... back to realtime-lsm
# REALTIME support for audio group users
@audio - rtprio 100
@audio - nice -10
@audio - memlock 250000
You can also find up to date ebuilds for rt-kernels and audio software
in the pro-audio overlay. There you can set the use of realtime-lsm by
setting a USE variable but I'd suggest to go with pam. More information
can be found in the wiki:
http://proaudio.tuxfamily.org/wiki/index.php?title=Main_Page
That's what I'm referring to, as I mentioned in my first msg:
I'm following the directions on the wiki for the RT kernel at:
http://proaudio.tuxfamily.org/wiki/index.php?title=Realtime_%28RT%29_Kernel
ulimit -l replies
# ulimit -l
250000
So, as Marc-Olivier mentioned, at least that is being read. But, is
there anything else that I can check?
With my latest kernel compile and with the change to the alsamixer to
44.1k (as I mentioned before) running qjackctl
does not say that it can't run realtime, but the "RT" symbol is not
lighted ("Realtime" IS checked in the setup)
Here's a log:
jackd 0.101.1
Copyright 2001-2005 Paul Davis and others.
jackd comes with ABSOLUTELY NO WARRANTY
This is free software, and you are welcome to redistribute it
under certain conditions; see the file COPYING for details
JACK compiled with System V SHM support.
loading driver ..
apparent rate = 44100
creating alsa driver ... hw:0|hw:0|1024|2|44100|0|0|nomon|swmeter|-|32bit
control device hw:0
configuring for 44100Hz, period = 1024 frames, buffer = 2 periods
nperiods = 2 for capture
nperiods = 2 for playback
16:43:28.923 Server configuration saved to "/home/bfuller/.jackdrc".
16:43:28.923 Statistics reset.
16:43:29.758 Client activated.
16:43:29.774 Audio connection change.
16:43:29.785 Audio connection graph change.
So, I'm getting there, but I'm not certain that I'm really running jack
in realtime mode.
11:03 p.m.
Brad Fuller wrote:
Martin Wohlleben wrote:
Gosh... so sorry people! I totally forgot that I could look
in the
status of qjackctl and it does say that I'm running
in Realtime mode.
Cool... sorry for the noise (I hope it'll, at least, help others later)
--
brad fuller
http://www.Sonaural.com/
+1 (408) 799-6124
On So, 2007-03-25 at 14:59 -0700, Brad Fuller
wrote:
Well... it's good to know that version should work. I made sure I had
it. The entries are the same.
Lee Revell wrote:
Hi,
pam-0.78-r6 should work. I use this version and jack runs with rt-prio.
Check your /etc/security/limits.conf for the right entries
On 3/25/07, Brad Fuller <brad(a)sonaural.com>
wrote:
> Yeah... I've done that. But, still I would like to be able to have
> external apps set the clock, right?
>
It can't work if JACK is running anyway because all clients are
required to support the server sample rate.
That I know.
WRT realtime, last i heard was that Gentoo does
not supply a new
enough version of PAM (0.80 or higher is required)
that I don't know. Bummer...
# equery which pam
/usr/portage/local/layman/pro-audio/sys-libs/pam/pam-0.78-r6.ebuild
Thanks... back to realtime-lsm
# REALTIME support for audio group users
@audio - rtprio 100
@audio - nice -10
@audio - memlock 250000
You can also find up to date ebuilds for rt-kernels and audio software
in the pro-audio overlay. There you can set the use of realtime-lsm by
setting a USE variable but I'd suggest to go with pam. More information
can be found in the wiki:
http://proaudio.tuxfamily.org/wiki/index.php?title=Main_Page
That's what I'm referring to, as I mentioned in my first msg:
I'm following the directions on the wiki for the RT kernel at:
http://proaudio.tuxfamily.org/wiki/index.php?title=Realtime_%28RT%29_Kernel
ulimit -l replies
# ulimit -l
250000
So, as Marc-Olivier mentioned, at least that is being read. But, is
there anything else that I can check?
With my latest kernel compile and with the change to the alsamixer to
44.1k (as I mentioned before) running qjackctl
does not say that it can't run realtime, but the "RT" symbol is not
lighted ("Realtime" IS checked in the setup)
Here's a log:
jackd 0.101.1
Copyright 2001-2005 Paul Davis and others.
jackd comes with ABSOLUTELY NO WARRANTY
This is free software, and you are welcome to redistribute it
under certain conditions; see the file COPYING for details
JACK compiled with System V SHM support.
loading driver ..
apparent rate = 44100
creating alsa driver ... hw:0|hw:0|1024|2|44100|0|0|nomon|swmeter|-|32bit
control device hw:0
configuring for 44100Hz, period = 1024 frames, buffer = 2 periods
nperiods = 2 for capture
nperiods = 2 for playback
16:43:28.923 Server configuration saved to "/home/bfuller/.jackdrc".
16:43:28.923 Statistics reset.
16:43:29.758 Client activated.
16:43:29.774 Audio connection change.
16:43:29.785 Audio connection graph change.
So, I'm getting there, but I'm not certain that I'm really running
jack in realtime mode.
26 Mar
26 Mar
1:50 p.m.
On 3/25/07, Martin Wohlleben <martin.wohlleben(a)gmx.de> wrote:
pam-0.78-r6 should work. I use this version and jack
runs with rt-prio.
Check your /etc/security/limits.conf for the right entries
# REALTIME support for audio group users
@audio - rtprio 100
@audio - nice -10
@audio - memlock 250000
Great... another distro patching old PAM versions rather than
upgrading... why?!?
Lee
4:48 p.m.
Lee Revell wrote:
On 3/25/07, Martin Wohlleben
<martin.wohlleben(a)gmx.de> wrote:
Perceived level of risk?
pam-0.78-r6 should work. I use this version and
jack runs with rt-prio.
Check your /etc/security/limits.conf for the right entries
# REALTIME support for audio group users
@audio - rtprio 100
@audio - nice -10
@audio - memlock 250000
Great... another distro patching old PAM versions rather than
upgrading... why?!? 
5:13 p.m.
On Mo, 26.03.07 19:48 rob <rob(a)curates-egg.org> wrote:
Lee Revell wrote:
tom@SiRiUS ~ $ equery which pam
/home/tom/cvs/proaudio/trunk/overlays/proaudio/sys-libs/pam/pam-0.99.7.1-r1.ebuild
Though 0.78-r6 is marked as stable here, whereas 0.99 is marked as
~arch (testing/unstable). Gentoo stable likes keeping old stuff, because
of stability reasons I'd guess - like debian, or redhat, or whatever
other distro providing stable and testing branches.
But if you want the newer one, just emerge it. You just have to unmask
it.
Also no idea why you are using a 2.6.16 kernel - 2.6.20-rt8 is superb,
at least on my uniproc machine here.
Cheers
On 3/25/07, Martin Wohlleben
<martin.wohlleben(a)gmx.de> wrote:
Perceived level of risk? pam-0.78-r6 should work. I use this version and
jack runs with
rt-prio. Check your /etc/security/limits.conf for the right entries
# REALTIME support for audio group users
@audio - rtprio 100
@audio - nice -10
@audio - memlock 250000
Great... another distro patching old PAM versions rather than
upgrading... why?!?
5:33 p.m.
Thomas Kuther wrote:
On Mo, 26.03.07 19:48 rob <rob(a)curates-egg.org>
wrote:
well.. I was just following the directions - I haven't done a realtime
kernel on gentoo and am using/trying the proaudio overlay.
Lee Revell wrote:
tom@SiRiUS ~ $ equery which pam
/home/tom/cvs/proaudio/trunk/overlays/proaudio/sys-libs/pam/pam-0.99.7.1-r1.ebuild
Though 0.78-r6 is marked as stable here, whereas 0.99 is marked as
~arch (testing/unstable). Gentoo stable likes keeping old stuff, because
of stability reasons I'd guess - like debian, or redhat, or whatever
other distro providing stable and testing branches.
But if you want the newer one, just emerge it. You just have to unmask
it.
Also no idea why you are using a 2.6.16 kernel - 2.6.20-rt8 is superb,
at least on my uniproc machine here.
On 3/25/07, Martin Wohlleben
<martin.wohlleben(a)gmx.de> wrote:
Perceived level of risk?
pam-0.78-r6 should work. I use this version and
jack runs with
rt-prio. Check your /etc/security/limits.conf for the right entries
# REALTIME support for audio group users
@audio - rtprio 100
@audio - nice -10
@audio - memlock 250000
Great... another distro patching old PAM versions rather than
upgrading... why?!?
6:09 p.m.
On Mo, 26.03.07 12:29 Brad Fuller <brad(a)sonaural.com> wrote:
Thomas Kuther wrote:
Yeah well, the howto uses 2.6.16 as example kernel, as 2.6.16 was the
current stable kernel when I wrote it.
But hmm, Frieder still marked 2.6.16-rt29 as the stable rt-sources in
the overlay - not sure why exactly, maybe perceived level of risk -
anyways in case of PAM and the kernel, I personally recommend using
latest ~ masked pam and =rt-sources-2.6.20-r8 :)
Regards,
Tom
On Mo, 26.03.07 19:48 rob
<rob(a)curates-egg.org> wrote:
well.. I was just following the directions - I haven't done a
realtime kernel on gentoo and am using/trying the proaudio overlay. Lee Revell wrote:
tom@SiRiUS ~ $ equery which pam
/home/tom/cvs/proaudio/trunk/overlays/proaudio/sys-libs/pam/pam-0.99.7.1-r1.ebuild
Though 0.78-r6 is marked as stable here, whereas 0.99 is marked as
~arch (testing/unstable). Gentoo stable likes keeping old stuff,
because of stability reasons I'd guess - like debian, or redhat, or
whatever other distro providing stable and testing branches.
But if you want the newer one, just emerge it. You just have to
unmask it.
Also no idea why you are using a 2.6.16 kernel - 2.6.20-rt8 is
superb, at least on my uniproc machine here.
On 3/25/07, Martin Wohlleben
<martin.wohlleben(a)gmx.de> wrote:
> pam-0.78-r6 should work. I use this version and jack runs with
> rt-prio. Check your /etc/security/limits.conf for the right
> entries
>
> # REALTIME support for audio group users
> @audio - rtprio 100
> @audio - nice -10
> @audio - memlock 250000
>
Great... another distro patching old PAM versions rather than
upgrading... why?!?
Perceived level of risk?
6:54 p.m.
Thomas Kuther wrote:
On Mo, 26.03.07 12:29 Brad Fuller
<brad(a)sonaural.com> wrote:
Right, I was using 2.6.16-rt29 and it's working with the pam 0.78. I'll
try the newest kernel.
--
brad fuller
http://www.Sonaural.com/
+1 (408) 799-6124
Thomas Kuther wrote:
Yeah well, the howto uses 2.6.16 as example kernel, as 2.6.16 was the
current stable kernel when I wrote it.
But hmm, Frieder still marked 2.6.16-rt29 as the stable rt-sources in
the overlay - not sure why exactly, maybe perceived level of risk -
anyways in case of PAM and the kernel, I personally recommend using
latest ~ masked pam and =rt-sources-2.6.20-r8 :)
On Mo, 26.03.07 19:48 rob
<rob(a)curates-egg.org> wrote:
well.. I was just following the directions - I haven't done a
realtime kernel on gentoo and am using/trying the proaudio overlay.
Lee Revell wrote:
> On 3/25/07, Martin Wohlleben <martin.wohlleben(a)gmx.de> wrote:
>
>
>> pam-0.78-r6 should work. I use this version and jack runs with
>> rt-prio. Check your /etc/security/limits.conf for the right
>> entries
>>
>> # REALTIME support for audio group users
>> @audio - rtprio 100
>> @audio - nice -10
>> @audio - memlock 250000
>>
>>
> Great... another distro patching old PAM versions rather than
> upgrading... why?!?
>
>
Perceived level of risk?
tom@SiRiUS ~ $ equery which pam
/home/tom/cvs/proaudio/trunk/overlays/proaudio/sys-libs/pam/pam-0.99.7.1-r1.ebuild
Though 0.78-r6 is marked as stable here, whereas 0.99 is marked as
~arch (testing/unstable). Gentoo stable likes keeping old stuff,
because of stability reasons I'd guess - like debian, or redhat, or
whatever other distro providing stable and testing branches.
But if you want the newer one, just emerge it. You just have to
unmask it.
Also no idea why you are using a 2.6.16 kernel - 2.6.20-rt8 is
superb, at least on my uniproc machine here.
6384
days inactive
6386
days old
linux-audio-user@lists.linuxaudio.org
19 comments
8 participants
participants (8)
-
Brad Fuller -
Burkhard Ritter -
Jack O'Quin -
Lee Revell -
Marc-Olivier Barre -
Martin Wohlleben -
rob -
Thomas Kuther