3 Apr
2007
3 Apr
'07
7:20 p.m.
well.. I was just following the directions - I
haven't done a
realtime kernel on gentoo and am using/trying the proaudio overlay.
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 :)
Right, I was using 2.6.16-rt29 and it's working with the pam 0.78.
I'll try the newest kernel.
Ok.. I've finally got some time and am now on
the newest kernel:
bfuller@ives ~ $ uname -a
Linux ives 2.6.20-rt8 #2 PREEMPT Thu Mar 29 21:32:54 PDT 2007 i686
Intel(R) Pentium(R) 4 CPU 1700MHz GenuineIntel GNU/Linux
but, I get clicks and jumps when playing anything. I don't get clicks
and jumps with standard kernels. What could I look at? dmesg didn't seem
to have anything of relevance to this. Should it?
tia,
brad
--
brad fuller
http://www.Sonaural.com/
+1 (408) 799-6124
3 Apr
3 Apr
7:31 p.m.
On 4/3/07, Brad Fuller <brad(a)sonaural.com> wrote:
Did you set the priorities of your soundcard IRQ and jackd correctly?
Lee
well.. I was
just following the directions - I haven't done a
realtime kernel on gentoo and am using/trying the proaudio overlay.
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 :)
Right, I was using 2.6.16-rt29 and it's working with the pam 0.78.
I'll try the newest kernel.
Ok.. I've finally got some time and am now on
the newest kernel:
bfuller@ives ~ $ uname -a
Linux ives 2.6.20-rt8 #2 PREEMPT Thu Mar 29 21:32:54 PDT 2007 i686
Intel(R) Pentium(R) 4 CPU 1700MHz GenuineIntel GNU/Linux
but, I get clicks and jumps when playing anything. I don't get clicks
and jumps with standard kernels. What could I look at? dmesg didn't seem
to have anything of relevance to this. Should it?
8:30 p.m.
Lee Revell wrote:
On 4/3/07, Brad Fuller <brad(a)sonaural.com>
wrote:
Did you set the priorities of your soundcard IRQ and jackd correctly?
I don't
know how to set the soundcard IRQ prioirity. jackd priority is
set to 0, but luckily that isn't the problem. I tracked it down to the
xine engine in amarok. It doesn't work well, but it has always worked
great in other kernels.
well.. I
was just following the directions - I haven't done a
realtime kernel on gentoo and am using/trying the proaudio overlay.
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 :)
Right, I was using 2.6.16-rt29 and it's working with the pam 0.78.
I'll try the newest kernel.
Ok.. I've finally got some time and am now on
the newest kernel:
bfuller@ives ~ $ uname -a
Linux ives 2.6.20-rt8 #2 PREEMPT Thu Mar 29 21:32:54 PDT 2007 i686
Intel(R) Pentium(R) 4 CPU 1700MHz GenuineIntel GNU/Linux
but, I get clicks and jumps when playing anything. I don't get clicks
and jumps with standard kernels. What could I look at? dmesg didn't seem
to have anything of relevance to this. Should it? 
8:50 p.m.
g'day Brad.
emerge rtirq. that'll take care of the irq prio. in qjackctl set your prioity
to -1 off your rt clock (rtc). to check what that is, use:
ps -Leo rtprio,cmd,pid
my rtc is set to 80, so i set the priority in qjackctl to 79 and it's
magnificent.
g.
9:12 p.m.
Geoff Beasley wrote:
g'day Brad.
emerge rtirq. that'll take care of the irq prio.
already emerge'd that.
in qjackctl set your prioity
to -1 off your rt clock (rtc). to check what that is, use:
ps -Leo rtprio,cmd,pid
My card is on IRQ10 which is priority 85, I assume that's good.
I don't see rtc or "clock" in the list. I do see: - jackd -R -P79
-p128 -dalsa 1329
- jackd -R -P79 -p128 -dalsa 1329
- jackd -R -P79 -p128 -dalsa 1329
89 jackd -R -P79 -p128 -dalsa 1329
79 jackd -R -P79 -p128 -dalsa 1329
78 qjackctl 12061
my rtc is set to 80, so i set the priority in qjackctl
to 79 and it's
magnificent.
9:19 p.m.
On Wednesday 04 April 2007 09:12:29 Brad Fuller wrote:
My card is on IRQ10 which is priority 85, I assume
that's good.
that's fine>
I don't see rtc or "clock" in the list.
I do see: - jackd -R -P79
different mobo's have different rtc chips etc. that's ok.
-p128 -dalsa 1329
- jackd -R -P79 -p128 -dalsa 1329
- jackd -R -P79 -p128 -dalsa 1329
89 jackd -R -P79 -p128 -dalsa 1329
79 jackd -R -P79 -p128 -dalsa 1329
78 qjackctl 12061
you're already running jack properly. the higher of the two schedfifo threads
is the watchdog which is -1 from the rtc which is normally 90. there is a
diff of 10 between the jack thread and the jack watchdog thread. on my
machine if i go to 80 in qjackctl i get lock-ups and freezes. should be fine.
are you till having trouble ? did you enable the tickless timer and hpet
under processor type and features ?
g.
9:29 p.m.
On Wednesday 04 April 2007 09:23:50 Brad Fuller wrote:
what is that, and in what app are you referring to?
sorry,
cd /usr/src/linux
make menuconfig
in the kernel under processor type and features. this is where all of the
important things relating to your kernel and hardware is situated. make sure
you enable high resolution timer support,tickless timers, subarchitecture
type is pc, hpet timers premption is set to real time and timer frequency is
set to 1000hz.
g.
9:52 p.m.
Geoff Beasley wrote:
On Wednesday 04 April 2007 09:23:50 Brad Fuller
wrote:
Right, these are all set except for: hpet (my cpu is too old), but I'll
set it anyway and "Tickless System." Is this what you are referring to
when you speak of "tickless timers"?
brad
what is that, and in what app are you referring
to?
sorry,
cd /usr/src/linux
make menuconfig
in the kernel under processor type and features. this is where all of the
important things relating to your kernel and hardware is situated. make sure
you enable high resolution timer support,tickless timers, subarchitecture
type is pc, hpet timers premption is set to real time and timer frequency is
set to 1000hz.
9:59 p.m.
On Wednesday 04 April 2007 09:52:16 Brad Fuller wrote:
Right, these are all set except for: hpet (my cpu is
too old), but I'll
set it anyway and "Tickless System." Is this what you are referring to
when you speak of "tickless timers"?
yup. it'll help. what are the exact symptoms ? you should be having no
problem at all...
g.
10:55 p.m.
Geoff Beasley wrote:
On Wednesday 04 April 2007 09:52:16 Brad Fuller
wrote:
my only problems now are outside of jack, - i think jack works ok. Using
the xine engine in amarok produces lots of clicks. Moving to the Helix
engine works much better.
Audacity, w/o jack, clicks too with any typing, net, window movement...
the usual.
I'm also concerned with the playback rate. Some apps playback too slow
(amarok and snd, neither with jack) while audacity plays back at the
right sample rate (with or w/o jack).
Right, these are all set except for: hpet (my cpu
is too old), but I'll
set it anyway and "Tickless System." Is this what you are referring to
when you speak of "tickless timers"?
yup. it'll help. what are the exact symptoms ? you should be having no
problem at all...
11:16 p.m.
On 4/3/07, Brad Fuller <brad(a)sonaural.com> wrote:
Geoff Beasley wrote:
Did you make sure that the soundcard IRQ is higher prio than all other
IRQs and that Audacity has realtime mode enabled (actually I have no
idea whether it has such a thing but it should)
On Wednesday 04 April 2007 09:52:16 Brad Fuller
wrote:
my only problems now are outside of jack, - i think jack works ok. Using
the xine engine in amarok produces lots of clicks. Moving to the Helix
engine works much better.
Audacity, w/o jack, clicks too with any typing, net, window movement...
the usual.
Right, these are all set except for: hpet (my cpu
is too old), but I'll
set it anyway and "Tickless System." Is this what you are referring to
when you speak of "tickless timers"?
yup. it'll help. what are the exact symptoms ? you should be having no
problem at all...
I'm also concerned with the playback rate. Some
apps playback too slow
(amarok and snd, neither with jack) while audacity plays back at the
right sample rate (with or w/o jack).
Probably your hardware only supports 48Khz but these apps use a hw
device which disables software resampling. Audacity would work as it
uses OSS compatibility layer which resamples in kernel space.
Lee
4 Apr
4 Apr
3:21 a.m.
Lee Revell wrote:
ahh... (I'm using a Delta66 in this PC and it goes up to 96kHz)
On 4/3/07, Brad Fuller <brad(a)sonaural.com>
wrote:
I'll check.
Geoff Beasley wrote:
having no
Did you make sure that the soundcard IRQ is higher prio than all other
IRQs and that Audacity has realtime mode enabled (actually I have no
idea whether it has such a thing but it should) On Wednesday 04 April 2007 09:52:16 Brad Fuller
wrote:
> Right, these are all set except for: hpet (my cpu is too old), but
I'll
> set it anyway and "Tickless
System." Is this what you are
referring to
when you
speak of "tickless timers"?
yup. it'll help. what are the exact symptoms ? you should be problem at all...
my only problems now are outside of jack, - i think jack works ok. Using
the xine engine in amarok produces lots of clicks. Moving to the Helix
engine works much better.
Audacity, w/o jack, clicks too with any typing, net, window movement...
the usual.
I'm also concerned with the playback rate.
Some apps playback too slow
(amarok and snd, neither with jack) while audacity plays back at the
right sample rate (with or w/o jack).
Probably your hardware only supports 48Khz but these apps use a hw
device which disables software resampling. Audacity would work as it
uses OSS compatibility layer which resamples in kernel space.
12:44 a.m.
If you get libxine from svn... it now has jack supported as a backend....
It works reasonably well except that wma files just don't want to play
properly.
Hopefully they will make a release sometime soon.
On Wed, 4 Apr 2007 10:55:28 am Brad Fuller wrote:
Geoff Beasley wrote:
--
<n3tg0d> has /usr/bin/emacs been put into /etc/shells yet? :P
On Wednesday 04 April 2007 09:52:16 Brad Fuller
wrote:
my only problems now are outside of jack, - i think jack works ok. Using
the xine engine in amarok produces lots of clicks. Moving to the Helix
engine works much better.
Audacity, w/o jack, clicks too with any typing, net, window movement...
the usual.
I'm also concerned with the playback rate. Some apps playback too slow
(amarok and snd, neither with jack) while audacity plays back at the
right sample rate (with or w/o jack).
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user(a)lists.linuxaudio.org
http://lists.linuxaudio.org/mailman/listinfo.cgi/linux-audio-user Right, these are all set except for: hpet (my cpu
is too old), but I'll
set it anyway and "Tickless System." Is this what you are referring to
when you speak of "tickless timers"?
yup. it'll help. what are the exact symptoms ? you should be having no
problem at all...
3 Apr
3 Apr
9:20 p.m.
Geoff Beasley wrote:
g'day Brad.
emerge rtirq. that'll take care of the irq prio. in qjackctl set your prioity
to -1 off your rt clock (rtc). to check what that is, use:
ps -Leo rtprio,cmd,pid
my rtc is set to 80, so i set the priority in qjackctl to 79 and it's
magnificent.
but:
# cat /proc/interrupts
CPU0
0: 4821170 XT-PIC-XT timer
1: 10 XT-PIC-XT i8042
2: 0 XT-PIC-XT cascade
5: 3 XT-PIC-XT ohci1394
6: 5 XT-PIC-XT floppy
7: 0 XT-PIC-XT parport0
8: 2 XT-PIC-XT rtc
9: 63360 XT-PIC-XT acpi, uhci_hcd:usb2
10: 177569 XT-PIC-XT ICE1712
11: 107572 XT-PIC-XT uhci_hcd:usb1, eth1
12: 112 XT-PIC-XT i8042
14: 51509 XT-PIC-XT ide0
15: 36626 XT-PIC-XT ide1
My rtc is IRQ 8 and according to the other list, [IRQ8] is set to
priority 90. Who would set that?
4 Apr
4 Apr
5:53 a.m.
Brad Fuller escribe:
>well.. I was just following the directions - I
haven't done a
>realtime kernel on gentoo and am using/trying the proaudio overlay.
It's "preemptive kernel" and "realtime" which are different
stuff. AFAIK you can try going realtime without a preemptive kernel
(this is, a kernel without Ingo Molnar patches).
Going preemptive: Download a vanilla kernel sources, version according
to latest available Ingo Molnar patches. Apply patches, recompile,
install, reboot.
[1]This article explains nicely what preemption is all about.
1. http://lwn.net/Articles/146861/
If running a debianized distro things are far easier, simply download
a [2]Musix kernel or a [3]64 Studio kernel (I'm right now running
Debian sid with a Musix 2.6.20 kernel and everything's smooth).
2. http://linux.ilmainen.net/musix/
3. http://archive.64studio.com/64studio/testing/pool/main/l/linux-2.6/
Talking about realtime, the newest the kernel the better although
other things break.
Going realtime is a matter of running a fairly recent version of
libpam-modules (higher than 0.79 I think), making sure the user is a
member of the audio group, putting this stanza into
/etc/security/limits.conf and relogging.
# limit realtime and memory locking access to users in the group audio
# there is no way to say "allow locking all memory", 4G should be enough
#
* - rt_priority 0
* - nice 0
#
@audio - rtprio 99
@audio - memlock 250000
@audio - nice -10
You should then be able to run jackd realtime.
: [ ~ ] $; jackd -R -d alsa
Also it should be useful enabling the high resolution timer in your
/etc/sysctl.conf as this:
dev.rtc.max-user-freq=1024
And then sysctl -p as root.
Hope I haven't mistaked anything and info is useful.
Cordially, Ismael
--
Ismael Valladolid Torres m. +34679156321
La media hostia j. ivalladt(a)gmail.com
http://lamediahostia.blogspot.com/
6235
days inactive
6236
days old
linux-audio-user@lists.linuxaudio.org
17 comments
5 participants
participants (5)
-
Brad Fuller -
danni -
Geoff Beasley -
Ismael Valladolid Torres -
Lee Revell