13 Jul
2008
13 Jul
'08
5:41 p.m.
On Monday 07 July 2008 23:31:30 Giuseppe Zompatori wrote:
2008/7/7 Emanuel Rumpf <xbran(a)web.de>de>:
I thought, it would probably help some of you, if
I uploaded
my rt-config for a 2.6.25.8 realtime kernel (debian system).
<snip>
tar xfj patch-2.6.25.8-rt7.bz2
zcat ../config.gz > ./.config
</snip>
You can use those compressed files directly/in-line by using the z/bz
prefixed version of cat, i.e.:
bzcat ../patch-2.6.25.8-rt7.bz2 | patch -p1
Did all that, worked like a charm: 1. realtime apparently cannot be set to be modularized
as in previous
versions. WIll NOT accept:
CONFIG_SECURITY_CAPABILITIES=m
CONFIG_REALTIME_CAPABILITIES=m
but insists on CONG_SECURITY_CAPABILITIES=y
realtime-lsm may no longer be valid for 2.6.25 kernels--debian has no prepared
modules beyond 2.6.23.
I have not objection to rlimits but cannot find this. How does one install/use
this?
2. My old nvidia driver will not compile. I can check
back on their site for
an upgrade but this is for an older mx400 card!
Debian's legacy 96xx did build up and install after a fashion. Have not tried
it yet.. In the past, I got half the frame rate using debian's versions. I did
not install the debian nvidia libglx.so at this point and I guard nvidia's on
every xorg upgrade. May not work with the debian driver, however.
Without rlimits, I will not use 2.6.25 kernel anyway.
13 Jul
13 Jul
6:43 p.m.
New subject: debian realtime kernel config 2.6.25.8.rt7
2008/7/13 David Baron <d_baron(a)012.net.il>il>:
realtime-lsm may no longer be valid for 2.6.25
kernels--debian has no prepared
modules beyond 2.6.23.
I have not objection to rlimits but cannot find this. How does one install/use
this?
there's no reason to use realtime-lsm anymore
Without rlimits, I will not use 2.6.25 kernel anyway.
rlimits functionality is default in 2.6.25 kernel.
I think it's activated with the CONFIG_SECURITY_CAPABILITIES=y option (?)
also don't forget to add this to /etc/security/limits.conf :
@audio - rtprio 78
@audio - memlock 400000
@audio - nice -10
6:58 p.m.
New subject: debian realtime kernel config 2.6.25.8.rt7
things to do additionally
------------------------------------------------------------------------------
enable realtime clock
----------------------
for the realtime clock to work, you've got to load these modules:
modprobe rtc_core
modprobe rtc_cmos
you should then have a device
/dev/rtc0
then change the max-user-frequency of rtc (default is only 64):
echo 2048 > /sys/class/rtc/rtc0/max_user_freq
test:
cat /sys/class/rtc/rtc0/max_user_freq
and maybe of hpet as well (?)
echo 2048 > /proc/sys/dev/hpet/max-user-freq
(Is hpet emulated by rtc ?)
------------------------------------------------------------------------------
set realtime priorities
-----------------------
install scheduling tools (/usr/bin/chrt)
apt-get install schedutils
or
apt-get install schedtool
install,setup and run the rtirq script by Rui Nuno Capela
download:
wget http://www.rncbc.org/jack/rtirq-20071012.tar.gz
14 Jul
14 Jul
3:26 a.m.
New subject: debian realtime kernel config 2.6.25.8.rt7
On Sunday 13 July 2008 23:58:19 Emanuel Rumpf wrote:
things to do additionally
---------------------------------------------------------------------------
---
enable realtime clock
----------------------
for the realtime clock to work, you've got to load these modules:
modprobe rtc_core
modprobe rtc_cmos
rebuilding the kernel to get rtc_cmos right now. There are others in that
group and my MB has a via chipset so I hope this is OK. The standard IDE
driver was not.
you should then have a device
/dev/rtc0
then change the max-user-frequency of rtc (default is only 64):
echo 2048 > /sys/class/rtc/rtc0/max_user_freq
test:
cat /sys/class/rtc/rtc0/max_user_freq
It would not let me create these
directories but may after the module is
available.
and maybe of hpet as well (?)
echo 2048 > /proc/sys/dev/hpet/max-user-freq
(Is hpet emulated by rtc ?)
2:06 p.m.
New subject: debian realtime kernel config 2.6.25.8.rt7
On Sunday 13 July 2008 23:58:19 Emanuel Rumpf wrote:
things to do additionally
---------------------------------------------------------------------------
---
enable realtime clock
----------------------
for the realtime clock to work, you've got to load these modules:
modprobe rtc_core
modprobe rtc_cmos
you should then have a device
/dev/rtc0
I have /dev/rtc from previous
then change the max-user-frequency of rtc (default is only 64):
echo 2048 > /sys/class/rtc/rtc0/max_user_freq
I have this set to 1024 (kernel hz?) in /etc/sysctl.conf.
test:
cat /sys/class/rtc/rtc0/max_user_freq
and maybe of hpet as well (?)
echo 2048 > /proc/sys/dev/hpet/max-user-freq
(Is hpet emulated by rtc ?)
There are hpet source files in the kernel sources and
among them an
hpet/emulate.rtc.h. No particular hpet.ko was built, however.
There is a /usr/src/linux-2.6.25.8/Documentation/hpet.txt which says that this
is a REPLACEMENT for the rtc stuff and the first two of its 32 timers will
stand in for the rtc. So it would seem one or the other.
---------------------------------------------------------------------------
---
set realtime priorities
-----------------------
install scheduling tools (/usr/bin/chrt)
apt-get install schedutils
This one threatened to remove some stuff
or
apt-get install schedtool
This one was clean.
install,setup and run the rtirq script by Rui Nuno Capela
download:
wget http://www.rncbc.org/jack/rtirq-20071012.tar.gz
Got it, copied the files to
places and my startup stuff to run it.
So will give everything a try out. The kernel runs fine. Debian's nvidia built
and works OK. One caveat is that hal kicks out all the dma and 32-bit disk
accesses but they can be immediately set back so I put that in my startup
stuff as well.
3:20 p.m.
New subject: debian realtime kernel config 2.6.25.8.rt7
2008/7/14 David Baron <d_baron(a)012.net.il>il>:
that's the old interface
it's incompatible, deactivate it. look at my config!
( zcat config.gz | grep -i rtc )
see src/Documentation/rtc.txt for more info
# CONFIG_RTC is not set
# CONFIG_GEN_RTC is not set
# CONFIG_HPET_RTC_IRQ is not set
1024 is ok too.
for the new interface however, there doesn't seem to be a sysctl
option anymore/yet and one has to set it manually.
you should
then have a device
/dev/rtc0
I have /dev/rtc from previous
then change the max-user-frequency of rtc (default is only 64):
echo 2048 > /sys/class/rtc/rtc0/max_user_freq
I have this set to 1024 (kernel hz?) in /etc/sysctl.conf.
One caveat is that hal kicks out all the dma and
32-bit disk
accesses but they can be immediately set back so I put that in my startup
stuff as well.
how do you set it up?
can/should that be done with any drive?
any conditions?
6:09 p.m.
New subject: debian realtime kernel config 2.6.25.8.rt7
On Monday 14 July 2008 20:20:41 Emanuel Rumpf wrote:
1024 is ok too.
for the new interface however, there doesn't seem to be a sysctl
option anymore/yet and one has to set it manually.
Most everything seems to do sysctl. One can set it manually to see how it
works out. If it is OK, it gets put in the sysctl so one need not manually set
it again.
hdparm
2008/7/14 David Baron <d_baron(a)012.net.il>il>:
that's the old interface
it's incompatible, deactivate it. look at my config!
( zcat config.gz | grep -i rtc )
see src/Documentation/rtc.txt for more info
# CONFIG_RTC is not set
# CONFIG_GEN_RTC is not set
# CONFIG_HPET_RTC_IRQ is not set
It is not compatible with what?
Here is ~$ lsmod | grep rtc
snd_rtctimer 3616 0
rtc_cmos 10848 0
rtc_core 19632 1 rtc_cmos
rtc_lib 3200 1 rtc_core
rtc 14620 1 snd_rtctimer
The "old" rtc is used by snd_rtctimer so that needs also to be replaced if
CONFIG_RTC will not be used. You may want the HPET in place of all of this?
you
should then have a device
/dev/rtc0
I have /dev/rtc from previous then
change the max-user-frequency of rtc (default is only 64):
echo 2048 > /sys/class/rtc/rtc0/max_user_freq
I have this set to 1024 (kernel hz?) in /etc/sysctl.conf. One caveat is
that hal kicks out all the dma and 32-bit disk
accesses but they can be immediately set back so I put that in my startup
stuff as well.
how do you set it up? can/should that be done with any drive?
That
gets done up front, hal bawks for some reason when starting. So for now,
I hdparm again.
any conditions?
I do not know why.
15 Jul
15 Jul
1:13 p.m.
New subject: debian realtime kernel config 2.6.25.8.rt7
2008/7/14 David Baron <d_baron(a)012.net.il>il>:
On Monday 14 July 2008 20:20:41 Emanuel Rumpf wrote:
with the
new rtc (at least it's not recommended to use both (see below)
2008/7/14 David Baron
<d_baron(a)012.net.il>il>:
that's the old interface
it's incompatible, deactivate it. look at my config!
( zcat config.gz | grep -i rtc )
see src/Documentation/rtc.txt for more info
# CONFIG_RTC is not set
# CONFIG_GEN_RTC is not set
# CONFIG_HPET_RTC_IRQ is not set
It is not compatible with what? you
should then have a device
/dev/rtc0
I have /dev/rtc from previous Here is ~$ lsmod | grep rtc
snd_rtctimer 3616 0
rtc_cmos 10848 0
rtc_core 19632 1 rtc_cmos
rtc_lib 3200 1 rtc_core
rtc 14620 1 snd_rtctimer
The "old" rtc is used by snd_rtctimer so that needs also to be replaced if
CONFIG_RTC will not be used. You may want the HPET in place of all of this?
hm..
when I was selecting the new rtc-driver in menuconf, I got a warning,
it would be incompatible with the old rtc.
Also it doesn't sound convincing to me, to run two different
rtc-drivers at the same time.
I don't have snd_rtctimer, only snd_timer.
in
linux/sound/core/rtctimer.c
I find:
#if defined(CONFIG_RTC) || defined(CONFIG_RTC_MODULE)
so you might be right, that the snd_rtctimer
still requires the old rtc.
# lsmod | grep -i rtc
rtc_cmos 11680 0
rtc_core 21584 1 rtc_cmos
rtc_lib 4096 1 rtc_core
20 Jul
20 Jul
12:44 p.m.
New subject: debian realtime kernel config 2.6.25.8.rt7
On Monday 14 July 2008 20:20:41 Emanuel Rumpf wrote:
2008/7/14 David Baron <d_baron(a)012.net.il>il>:
that's the old interface
it's incompatible, deactivate it. look at my config!
( zcat config.gz | grep -i rtc )
see src/Documentation/rtc.txt for more info
# CONFIG_RTC is not set
# CONFIG_GEN_RTC is not set
# CONFIG_HPET_RTC_IRQ is not set
1024 is ok too.
for the new interface however, there doesn't seem to be a sysctl
option anymore/yet and one has to set it manually.
I rebuilt the kernel with the hpet stuff enabled. Make menuconfig offers no
place to get rid of CONFIG_RTC, even though hpet should be taking care of it.
Anyway, all the same results.
you
should then have a device
/dev/rtc0
I have /dev/rtc from previous then
change the max-user-frequency of rtc (default is only 64):
echo 2048 > /sys/class/rtc/rtc0/max_user_freq
I have this set to 1024 (kernel hz?) in /etc/sysctl.conf.
21 Jul
21 Jul
2:18 p.m.
New subject: debian realtime kernel config 2.6.25.8.rt7
2008/7/20 David Baron <d_baron(a)012.net.il>il>:
I rebuilt the kernel with the hpet stuff enabled. Make menuconfig offers no
place to get rid of CONFIG_RTC, even though hpet should be taking care of it.
I deactivated these:
Menu -> DeviceDrivers -> CharacterDevices -> EnhancedRealtimeClockSupport
Menu -> DeviceDrivers -> CharacterDevices -> Generic /dev/rtc emulation
but enabled:
Menu -> DeviceDrivers -> Real Time Clock
22 Jul
22 Jul
2:40 a.m.
New subject: debian realtime kernel config 2.6.25.8.rt7
On Monday 21 July 2008 19:18:10 Emanuel Rumpf wrote:
2008/7/20 David Baron <d_baron(a)012.net.il>il>:
OK, but that "enhanced realtime clock support is menued as "new". The rtc.c
does hpet refences. Snd-rcttimer will not be built this way.
The question is will muse run without snd-rtc-timer. The 1.0 beta did come
up in the midi-only mode but it kicks at ladspa descripters before one can do
anything. I do not remember which one of these programs wanted the snd-
rtctimer. Rosegarden is one of the few kde3 apps that will not run under kde4!
muse 0.8 will start up without rtc, snd-rtctimer loaded. It will not play midi
to a midi out device if jack is running but I think this is a problem with
current jack since qsynth had the same problem.
I rebuilt the kernel with the hpet stuff enabled.
Make menuconfig offers
no place to get rid of CONFIG_RTC, even though hpet should be taking care
of it.
I deactivated these:
Menu -> DeviceDrivers -> CharacterDevices -> EnhancedRealtimeClockSupport
Menu -> DeviceDrivers -> CharacterDevices -> Generic /dev/rtc emulation
but enabled:
Menu -> DeviceDrivers -> Real Time Clock
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user(a)lists.linuxaudio.org
http://lists.linuxaudio.org/mailman/listinfo/linux-audio-user 
6:11 a.m.
New subject: debian realtime kernel config 2.6.25.8.rt7
Am Tuesday 22 July 2008 schrieb David Baron:
Rosegarden is one of the few kde3 apps that will not
run under kde4!
Sorry, but I can't confirm this: I have a fresh openSUSE 11.0 install, with
kernel-rt 2.6.25.5 and CONFIG_HZ=1000, and both rosegarden(1.7.1-svn) and
muse(0.9) run happily under KDE 4.0.4, even in parallel and jack transport
synced (if I use the muse transport buttons, rosegarden crashes, but that's
a different issue I didn't care to look at yet). Three modules with rtc in
their name are loaded: rtc_lib, rtc_core and rtc_cmos.
muse 0.8 will start up without rtc, snd-rtctimer loaded. It will not play midi
to a midi out device if jack is running but I think this is a problem with
current jack since qsynth had the same problem.
Can't confirm either: using latest jack svn here (0.112.0), muse plays MIDI
to it's internal softsynths (I tried DeicsOnce) as well as to external
hardware gear (tried Korg Wavestation via the Delta 1010LT MIDI output).
12:49 p.m.
New subject: debian realtime kernel config 2.6.25.8.rt7
2008/7/22 David Baron <d_baron(a)012.net.il>il>:
OK, but that "enhanced realtime clock support is
menued as "new". The rtc.c
does hpet refences.
Snd-rcttimer will not be built this way.
That's what I said. I don't have it.
But which/what is using/requiring snd-rtctimer btw?
The question is will muse run without snd-rtc-timer.
yes
but create a link:
ln -s /dev/rtc0 /dev/rtc
for the new rtc-device, so that muse can find it.
2008/7/22 David Baron <d_baron(a)012.net.il>il>:
Something else I just noticed in the kernel
builds:Section mismatches! 24 in
image and 9 in the modules.
maybe the build is not clean
have you run
make-kpkg clean
??
I have sometimes had problems
that "make clean" could not remove.
Starting with fresh sources
and a known working config
helped in most cases.
1:19 p.m.
New subject: debian realtime kernel config 2.6.25.8.rt7
On Tuesday 22 July 2008 17:49:28 Emanuel Rumpf wrote:
2008/7/22 David Baron <d_baron(a)012.net.il>il>:
Actually, without that link, I get:
Trying RTC timer...
fatal error: open /dev/rtc failed: No such file or directory
Trying ALSA timer...
got timer = 20
starting with default template
showMarker 0
3set realtime scheduler: Operation not permitted
With the symlink I get.
Trying RTC timer...
got timer = 20
starting with default template
showMarker 0
3set realtime scheduler: Operation not permitted
So nothing is really different. How do I get the realtime scheduler? The
rlimits is for the audio group to have that!
Also get
watchdog process 7192 _NOT_ running SCHED_FIFO
OK, but that "enhanced realtime clock
support is menued as "new". The
rtc.c does hpet refences.
Snd-rcttimer will not be built this way.
That's what I said. I don't have it.
But which/what is using/requiring snd-rtctimer btw?
The question is will muse run without
snd-rtc-timer.
yes
but create a link:
ln -s /dev/rtc0 /dev/rtc
for the new rtc-device, so that muse can find it.
2008/7/22 David Baron <d_baron(a)012.net.il>il>:
I can try that when I have time to let that go on again!
Something else I just noticed in the kernel
builds:Section mismatches! 24
in image and 9 in the modules.
maybe the build is not clean
have you run
make-kpkg clean
??
I have sometimes had problems
that "make clean" could not remove.
Starting with fresh sources
and a known working config
helped in most cases.
2:54 p.m.
New subject: debian realtime kernel config 2.6.25.8.rt7
2008/7/22 David Baron <d_baron(a)012.net.il>il>:
On Tuesday 22 July 2008 17:49:28 Emanuel Rumpf wrote:
Nothing different?
In the first output it uses alsa-timer
In the second rtc-timer
I would call that different at least :-)
but create a link:
ln -s /dev/rtc0 /dev/rtc
for the new rtc-device, so that muse can find it.
Actually, without that link, I get:
Trying RTC timer...
fatal error: open /dev/rtc failed: No such file or directory
Trying ALSA timer...
got timer = 20
With the symlink I get.
Trying RTC timer...
got timer = 20
So nothing is really different. How do I get the realtime scheduler?
If you have
"PREEMPT RT" in output of
uname -v
you allready have it.
The rlimits is for the audio group to have that!
?
If you can run jackd as user in realtime-mode rlimit (we use PAM now)
should already be set right.
Also get
watchdog process 7192 _NOT_ running SCHED_FIFO
where? don't know what this is.
3:05 p.m.
New subject: debian realtime kernel config 2.6.25.8.rt7
On Tuesday 22 July 2008 19:54:03 Emanuel Rumpf wrote:
It does. That's how we built this kernel
It does start. So why does muse kick?
Message follows the others here.
2008/7/22 David Baron <d_baron(a)012.net.il>il>:
What is the practical difference. How would I get udev to place this symlink
since /dev is generated.
On Tuesday 22 July 2008 17:49:28 Emanuel Rumpf
wrote:
Nothing different?
In the first output it uses alsa-timer
In the second rtc-timer
I would call that different at least :-) but create a link:
ln -s /dev/rtc0 /dev/rtc
for the new rtc-device, so that muse can find it.
Actually, without that link, I get:
Trying RTC timer...
fatal error: open /dev/rtc failed: No such file or directory
Trying ALSA timer...
got timer = 20
With the symlink I get.
Trying RTC timer...
got timer = 20
So nothing is really different. How do I get the realtime scheduler?
If you have "PREEMPT RT" in output of
uname -v
you allready have it. The rlimits is for the audio group to have that!
?
If you can run jackd as user in realtime-mode rlimit (we use PAM now)
should already be set right. Also get
watchdog process 7192 _NOT_ running SCHED_FIFO
where? don't know what this is.
14 Jul
14 Jul
3:28 a.m.
New subject: debian realtime kernel config 2.6.25.8.rt7
On Sunday 13 July 2008 23:43:34 Emanuel Rumpf wrote:
2008/7/13 David Baron <d_baron(a)012.net.il>il>:
These are already there:
# audio facilities:
@audio - rtprio 95
@audio - memlock 512000
@audio - nice -19
better or worse?
realtime-lsm may no longer be valid for 2.6.25
kernels--debian has no
prepared modules beyond 2.6.23.
I have not objection to rlimits but cannot find this. How does one
install/use this?
there's no reason to use realtime-lsm anymore
Without rlimits, I will not use 2.6.25 kernel
anyway.
rlimits functionality is default in 2.6.25 kernel.
I think it's activated with the CONFIG_SECURITY_CAPABILITIES=y option (?)
also don't forget to add this to /etc/security/limits.conf :
@audio - rtprio 78
@audio - memlock 400000
@audio - nice -10
12:23 p.m.
New subject: debian realtime kernel config 2.6.25.8.rt7
also don't
forget to add this to /etc/security/limits.conf :
@audio - rtprio 78
@audio - memlock 400000
@audio - nice -10
These are already there:
# audio facilities:
@audio - rtprio 95
@audio - memlock 512000
@audio - nice -19
better or worse?
5970
days inactive
5979
days old
linux-audio-user@lists.linuxaudio.org
17 comments
3 participants
participants (3)
-
David Baron -
Edgar Aichinger -
Emanuel Rumpf