14 Jul
2004
14 Jul
'04
10:28 p.m.
I've applied the realtime-lsm 0.1.1 patch but I stll get this. I'm
pretty sure I've followed the instructions properly.
$ jackstart -R -v -d alsa -d hw:0
jackstart: cannot get realtime capabilities, current capabilities are:
=ep cap_setpcap-e
probably running under a kernel with capabilities disabled,
a suitable kernel would have printed something like "=eip"
I've applied it to a 2.6.7 and 2.6.8.r1 kernel but I should think that
makes little difference. I'm getting really tired of chasing the 2.6
kernels to make them work as well as my 2.4.22. I gave up trying 6
months ago and it looks like nothing has improved. <sigh>
14 Jul
14 Jul
10:54 p.m.
I've applied it to a 2.6.7 and 2.6.8.r1 kernel but
I should think that
makes little difference. I'm getting really tired of chasing the 2.6
kernels to make them work as well as my 2.4.22. I gave up trying 6
months ago and it looks like nothing has improved. <sigh>
People, people...
Speaking as someone who's used and tinkered with Linux from the 1.x days,
never ever be fooled into thinking that "release" Linux kernels mean release
as in "high quality and/or bug-free" (as bug-free as can be realistically
expected at least).
I avoid new kernels until they make it through adolescence... .17 or .18.
Seriously. I could regale you with sordid tales of mid-stream VMM changes,
driver breakage, filesystem miseries (for ext3!!), etc. But just take my
word for it.
Unless you want to be on the BLEEDING edge (make sure you remember the
operative word there), just stick to the mature kernels. 2.4.26 is nice and
solid, and whatever flaws remain with it are really minor ones. I use for
everything from SMP web/MySQL servers, to
everything-including-the-kitchen-sink home network servers, to personal
development stations. It works, and it works well. There are mature and
well-tested low-latency patches which just work well. I use them on my
production servers and notice improvements in many aspects of their
performance, without compromises in uptime or robustness. (Many of these
servers crossed over a year of uptime recently.)
Let those who have an ample supply of band-aids and H2O2 mess around with
2.6. They're still getting their infrastructure issues sorted out.
=MB=
--
A focus on Quality.
15 Jul
15 Jul
9:43 a.m.
I understand this - however when the kernel developers are taking an interest
in the problems with audio/latency in the current kernel and are actively
asking for good bug reporting then in an effort to improve things it is
probably better if more people started testing the 2.6 branch.
Dave
On Thursday 15 July 2004 01:44, Malcolm Baldridge wrote:
People, people...
Speaking as someone who's used and tinkered with Linux from the 1.x days,
never ever be fooled into thinking that "release" Linux kernels mean
release as in "high quality and/or bug-free" (as bug-free as can be
realistically expected at least).
I avoid new kernels until they make it through adolescence... .17 or .18.
Seriously. I could regale you with sordid tales of mid-stream VMM changes,
driver breakage, filesystem miseries (for ext3!!), etc. But just take my
word for it.
Unless you want to be on the BLEEDING edge (make sure you remember the
operative word there), just stick to the mature kernels. 2.4.26 is nice
and solid, and whatever flaws remain with it are really minor ones. I use
for everything from SMP web/MySQL servers, to
everything-including-the-kitchen-sink home network servers, to personal
development stations. It works, and it works well. There are mature and
well-tested low-latency patches which just work well. I use them on my
production servers and notice improvements in many aspects of their
performance, without compromises in uptime or robustness. (Many of these
servers crossed over a year of uptime recently.)
Let those who have an ample supply of band-aids and H2O2 mess around with
2.6. They're still getting their infrastructure issues sorted out.
=MB=
14 Jul
14 Jul
11:45 p.m.
On Thu, Jul 15, 2004 at 10:18:39AM EST, Glenn McCord wrote:
I've applied the realtime-lsm 0.1.1 patch but I
stll get this. I'm
pretty sure I've followed the instructions properly.
$ jackstart -R -v -d alsa -d hw:0
jackstart: cannot get realtime capabilities, current capabilities are:
=ep cap_setpcap-e
probably running under a kernel with capabilities disabled,
a suitable kernel would have printed something like "=eip"
I am quite sure yu don't need to use jackstart. Jackd should work with no
problems. Jackstart is only for use with 2.4 kernels with capabilities enabled.
I've applied it to a 2.6.7 and 2.6.8.r1 kernel but
I should think that
makes little difference. I'm getting really tired of chasing the 2.6
kernels to make them work as well as my 2.4.22. I gave up trying 6
months ago and it looks like nothing has improved. <sigh>
I would personally stick with 2.4.26.
--
Luke Yelavich
http://www.audioslack.com
luke(a)audioslack.com
20 Jul
20 Jul
2:21 a.m.
Luke Yelavich <luke(a)audioslack.com> writes:
On Thu, Jul 15, 2004 at 10:18:39AM EST, Glenn McCord
wrote:
Right.
With current 2.6, libc and JACK versions, you'll also need the
LD_ASSUME_KERNEL workaround for useable results.
http://jackit.sourceforge.net/docs/faq.php#a53
I've applied the realtime-lsm 0.1.1 patch but
I stll get this. I'm
pretty sure I've followed the instructions properly.
$ jackstart -R -v -d alsa -d hw:0
jackstart: cannot get realtime capabilities, current capabilities are:
=ep cap_setpcap-e
probably running under a kernel with capabilities disabled,
a suitable kernel would have printed something like "=eip"
I am quite sure yu don't need to use jackstart. Jackd should work
with no problems. Jackstart is only for use with 2.4 kernels with
capabilities
enabled.
You *can* use `jackstart' with realtime-lsm on 2.6, but you need to
specify allcaps=1 for that to work. Otherwise, just use `jackd'.
--
joq
7409
days inactive
7415
days old
linux-audio-user@lists.linuxaudio.org
4 comments
5 participants
participants (5)
-
David M -
Glenn McCord -
Jack O'Quin -
Luke Yelavich -
Malcolm Baldridge