29 Apr
2010
29 Apr
'10
6:27 p.m.
Does anyone out there have an opinion on linux kernel
2.6.31-rt vs. 2.6.33-rt for audio?
Thanks,
Gabriel
29 Apr
29 Apr
7:16 p.m.
On Thu, Apr 29, 2010 at 11:27:07AM -0500, Gabriel M. Beddingfield wrote:
Does anyone out there have an opinion on linux kernel 2.6.31-rt vs.
2.6.33-rt for audio?
i am in the process of updating.
had some problems with udev not creating device nodes for my HD
partitions.
i think i solved them. (didnt reboot yet)
make sure the deprecated sysfs interface is off.
CONFIG_SYSFS_DEPRECATED_V2
according to blackpenguin the symptoms match.
i also had a lockup when hal was started.
dunno... 2.6.31-rt (which i am running now) was a little bit less painless.
--
torben Hohn
8:11 p.m.
torbenh wrote:
On Thu, Apr 29, 2010 at 11:27:07AM -0500, Gabriel M.
Beddingfield wrote:
Do you build it for Debian or Ubuntu? When I tried to build it for Hardy
(64 Studio) the same way as I build my current kernel uname -r
2.6.31.12-rt20, it failed.
http://lists.64studio.com/pipermail/64studio-users/2010-April/004359.html
Does anyone out there have an opinion on linux
kernel 2.6.31-rt vs.
2.6.33-rt for audio?
i am in the process of updating.
had some problems with udev not creating device nodes for my HD
partitions.
i think i solved them. (didnt reboot yet)
make sure the deprecated sysfs interface is off.
CONFIG_SYSFS_DEPRECATED_V2
according to blackpenguin the symptoms match.
i also had a lockup when hal was started.
dunno... 2.6.31-rt (which i am running now) was a little bit less painless.
8:32 p.m.
Ralf Mardorf wrote:
torbenh wrote:
Perhaps my issue is solved.
http://lkml.indiana.edu/hypermail/linux/kernel/0607.2/0107.html
On Thu, Apr 29, 2010 at 11:27:07AM -0500, Gabriel
M. Beddingfield wrote:
Do you build it for Debian or Ubuntu? When I tried to build it for
Hardy (64 Studio) the same way as I build my current kernel uname -r
2.6.31.12-rt20, it failed.
http://lists.64studio.com/pipermail/64studio-users/2010-April/004359.html Does anyone out there have an opinion on linux
kernel 2.6.31-rt vs.
2.6.33-rt for audio?
i am in the process of updating.
had some problems with udev not creating device nodes for my HD
partitions.
i think i solved them. (didnt reboot yet)
make sure the deprecated sysfs interface is off.
CONFIG_SYSFS_DEPRECATED_V2
according to blackpenguin the symptoms match.
i also had a lockup when hal was started.
dunno... 2.6.31-rt (which i am running now) was a little bit less
painless.
8:40 p.m.
On Thu, Apr 29, 2010 at 08:11:31PM +0200, Ralf Mardorf wrote:
torbenh wrote:
debian. dunno. still seems to be wrong.
i am running it now, but i needed to mknod the HD device nodes.
--
torben Hohn
On Thu, Apr 29, 2010 at 11:27:07AM -0500, Gabriel
M. Beddingfield wrote:
Do you build it for Debian or Ubuntu? When I tried to build it for
Hardy (64 Studio) the same way as I build my current kernel uname -r
2.6.31.12-rt20, it failed.
http://lists.64studio.com/pipermail/64studio-users/2010-April/004359.html Does anyone out there have an opinion on linux
kernel 2.6.31-rt vs.
2.6.33-rt for audio?
i am in the process of updating.
had some problems with udev not creating device nodes for my HD
partitions.
i think i solved them. (didnt reboot yet)
make sure the deprecated sysfs interface is off.
CONFIG_SYSFS_DEPRECATED_V2
according to blackpenguin the symptoms match.
i also had a lockup when hal was started.
dunno... 2.6.31-rt (which i am running now) was a little bit less painless.
8:47 p.m.
torbenh wrote:
On Thu, Apr 29, 2010 at 08:11:31PM +0200, Ralf Mardorf
wrote:
Do you build the kernel using make-kpkg? To be honest, for Hardy I never
used "--append-to-version=-1", but I did this for Karmic and there it
worked for 2.6.31.12-rt21-1. However that be, modifying
debian/ruleset/misc/version_vars.mk
-UTS_RELEASE_VERSION=$(shell if [ -f include/linux/version.h ]; then \
- grep 'define UTS_RELEASE' include/linux/version.h | \
+UTS_RELEASE_VERSION=$(shell if [ -f include/linux/utsrelease.h ]; then \
+ grep 'define UTS_RELEASE' include/linux/utsrelease.h | \
might solve the problem?!
Ralf
torbenh wrote:
debian. dunno. still seems to be wrong.
i am running it now, but i needed to mknod the HD device nodes. On Thu, Apr 29, 2010 at 11:27:07AM -0500, Gabriel
M. Beddingfield wrote:
Do you build it for Debian or Ubuntu? When I tried to build it for
Hardy (64 Studio) the same way as I build my current kernel uname -r
2.6.31.12-rt20, it failed.
http://lists.64studio.com/pipermail/64studio-users/2010-April/004359.html
Does anyone out there have an opinion on linux
kernel 2.6.31-rt vs.
2.6.33-rt for audio?
i am in the process of updating.
had some problems with udev not creating device nodes for my HD
partitions.
i think i solved them. (didnt reboot yet)
make sure the deprecated sysfs interface is off.
CONFIG_SYSFS_DEPRECATED_V2
according to blackpenguin the symptoms match.
i also had a lockup when hal was started.
dunno... 2.6.31-rt (which i am running now) was a little bit less painless.
8:51 p.m.
On Thu, 29 Apr 2010, torbenh wrote:
On Thu, Apr 29, 2010 at 11:27:07AM -0500, Gabriel M.
Beddingfield wrote:
IDE, SCSI, or both?
Does anyone out there have an opinion on linux kernel 2.6.31-rt vs.
2.6.33-rt for audio?
i am in the process of updating.
had some problems with udev not creating device nodes for my HD
partitions. i think i solved them. (didnt reboot yet)
make sure the deprecated sysfs interface is off.
CONFIG_SYSFS_DEPRECATED_V2
Thanks for the tip.
FWIW, I built 2.6.33.2-rt13 by tweaking the current
Debian/experimental build system. So far it's been working
fine for me on two different Ubuntu-based, 32-bit, x86
systems.
Things I've noticed:
* The fan seems to run less often (good, it was
running too often before).
* 'cat /proc/cpuinfo' doesn't show the actual current
clock speed without loading in some other modules.
I haven't put it through its paces on RT audio, yet.
-gabriel
8:57 p.m.
Gabriel M. Beddingfield wrote:
On Thu, 29 Apr 2010, torbenh wrote:
For .31-rt I never noticed that the fan ever was audible for my adm64.
spinymouse-sudo@64studio:~$ uname -a
Linux 64studio 2.6.31.12-rt20 #1 SMP PREEMPT RT Sun Feb 7 13:55:55 CET
2010 x86_64 GNU/Linux
spinymouse-sudo@64studio:~$ hwinfo --cpu | grep Model
Model: 15.107.2 "AMD Athlon(tm) X2 Dual Core Processor BE-2350"
On Thu, Apr 29, 2010 at 11:27:07AM -0500, Gabriel
M. Beddingfield wrote:
IDE, SCSI, or both?
Does anyone out there have an opinion on linux kernel 2.6.31-rt vs.
2.6.33-rt for audio?
i am in the process of updating.
had some problems with udev not creating device nodes for my HD
partitions. i think i solved them. (didnt reboot yet)
make sure the deprecated sysfs interface is off.
CONFIG_SYSFS_DEPRECATED_V2
Thanks for the tip.
FWIW, I built 2.6.33.2-rt13 by tweaking the current
Debian/experimental build system. So far it's been working fine for
me on two different Ubuntu-based, 32-bit, x86 systems.
Things I've noticed:
* The fan seems to run less often (good, it was
running too often before).
* 'cat /proc/cpuinfo' doesn't show the actual current
clock speed without loading in some other modules.
I haven't put it through its paces on RT audio, yet.
-gabriel
9:08 p.m.
Gabriel M. Beddingfield wrote:
On Thu, 29 Apr 2010, Ralf Mardorf wrote:
Aha, a laptop. Ok, "not audible" is overstated, but of course a tower,
as I'm using, might have an advantage regarding to heat. I keep my
fingers crossed that less activity for you fan, won't shutdown your
laptop, when doing audio work.
Good luck!
Ralf
For .31-rt I never noticed that the fan ever was
audible for my adm64.
I do (.31-rt). Core Duo processor, in a laptop, with a weak battery
(i.e. power supply often adding heat to power computer and charge
battery).
-gabriel
9:16 p.m.
On Thu, 29 Apr 2010, Ralf Mardorf wrote:
using, might have an advantage regarding to heat. I
keep my fingers crossed
that less activity for you fan, won't shutdown your laptop, when doing audio
work.
Well, I've used it for several kernel builds with -j2.
Gets hot, but hasn't overheated... so I think I'm good.
:-)
-gabriel
9:23 p.m.
Gabriel M. Beddingfield wrote:
On Thu, 29 Apr 2010, Ralf Mardorf wrote:
This is a good test :), when I do build a kernel the CPU is working to
capacity for around 1 hour, when set to MAKEFLAGS="CONCURRENCY-LEVEL=2",
quasi -j2. I guess your mileage won't vary too much, so several kernel
builds should be harder than audio work.
using, might have an advantage regarding to heat.
I keep my fingers
crossed that less activity for you fan, won't shutdown your laptop,
when doing audio work.
Well, I've used it for several kernel builds with -j2. Gets hot, but
hasn't overheated... so I think I'm good. :-)
-gabriel
9:41 p.m.
On Thu, Apr 29, 2010 at 09:23:37PM +0200, Ralf Mardorf wrote:
Gabriel M. Beddingfield wrote:
1 hour ... with both cores ?
thats why i dont use these weird kernel buildsystems.
i build a kernel in 10minutes on one core.
simply because i turn the stuff i dont need off...
but this time i missed some important option and it took pretty long to
get the new kernel working...
for the record:
this was the solution.
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/571164
On Thu, 29 Apr 2010, Ralf Mardorf wrote:
This is a good test :), when I do build a kernel the CPU is working
to capacity for around 1 hour, when set to
MAKEFLAGS="CONCURRENCY-LEVEL=2", quasi -j2. I guess your mileage
won't vary too much, so several kernel builds should be harder than
audio work. using, might have an advantage regarding to heat.
I keep my
fingers crossed that less activity for you fan, won't shutdown
your laptop, when doing audio work.
Well, I've used it for several kernel builds with -j2. Gets hot,
but hasn't overheated... so I think I'm good. :-)
-gabriel _______________________________________________
Linux-audio-dev mailing list
Linux-audio-dev(a)lists.linuxaudio.org
http://lists.linuxaudio.org/listinfo/linux-audio-dev
--
torben Hohn
9:52 p.m.
--- On Thu, 4/29/10, torbenh <torbenh(a)gmx.de> wrote:
From: torbenh <torbenh(a)gmx.de>
Subject: Re: [LAD] Kernel Opinions: .31-rt or .33-rt?
To: linux-audio-dev(a)lists.linuxaudio.org
Date: Thursday, April 29, 2010, 3:41 PM
On Thu, Apr 29, 2010 at 09:23:37PM
+0200, Ralf Mardorf wrote:
CPU is working
I tried 2.6.33.x-rty with a config from 2.6.32. Did the usual make-kpkg thing with the env
variable CONCURRENCY_LEVEL=2 set prior to make-kpkg (dual core system). It built fine in a
reasonable time (my kernel config is home-made, a lot of stuff is not checked in).
But when booting, I got a kernel panic (first time in years!). So back to vanilla 2.6.32
which works great for me even for RT (see xruns only when unstable apps are sometimes
crashing - I use jack2 by the way).
J.
Gabriel M. Beddingfield wrote:
>
>
>On Thu, 29 Apr 2010, Ralf Mardorf wrote:
>
>>using, might have an advantage regarding to
heat. I keep my
>>fingers crossed that less activity for
you
fan, won't shutdown
>>your laptop, when doing audio work.
>
>Well, I've used it for several kernel builds with
-j2. Gets hot,
but
hasn't overheated... so I think I'm good. :-)
-gabriel
This is a good test :), when I do build a kernel the to capacity for around 1 hour, when set to
MAKEFLAGS="CONCURRENCY-LEVEL=2", quasi -j2. I guess
your mileage
won't vary too much, so several kernel builds
should
be harder than
audio work.
1 hour ... with both cores ?
thats why i dont use these weird kernel buildsystems.
i build a kernel in 10minutes on one core.
simply because i turn the stuff i dont need off...
but this time i missed some important option and it took
pretty long to
get the new kernel working...
for the record:
this was the solution.
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/571164
10:05 p.m.
James Warden wrote:
--- On Thu, 4/29/10, torbenh <torbenh(a)gmx.de>
wrote:
Some days ago I saw my first kernel panic ever and this happened because
the hardware for the computer from a friend needs to be repaired. After
I repaired his hardware there wasn't the kernel panic any more.
Regarding to Torben's and your experiences it won't make any sense to
build .33-rt.
Anyway, I'll try to do it tomorrow.
Ralf
From: torbenh <torbenh(a)gmx.de>
Subject: Re: [LAD] Kernel Opinions: .31-rt or .33-rt?
To: linux-audio-dev(a)lists.linuxaudio.org
Date: Thursday, April 29, 2010, 3:41 PM
On Thu, Apr 29, 2010 at 09:23:37PM
+0200, Ralf Mardorf wrote:
CPU is working
I tried 2.6.33.x-rty with a config from 2.6.32. Did the usual make-kpkg thing with the
env variable CONCURRENCY_LEVEL=2 set prior to make-kpkg (dual core system). It built fine
in a reasonable time (my kernel config is home-made, a lot of stuff is not checked in).
But when booting, I got a kernel panic (first time in years!). So back to vanilla 2.6.32
which works great for me even for RT (see xruns only when unstable apps are sometimes
crashing - I use jack2 by the way).
J.
Gabriel M. Beddingfield wrote:
> On Thu, 29 Apr 2010, Ralf Mardorf wrote:
>
>
>> using, might have an advantage regarding to
>>
heat. I keep my
>> fingers crossed that less activity for
you
>>
fan, won't shutdown
>> your laptop, when doing audio work.
>>
> Well, I've used it for several kernel builds with
>
-j2. Gets hot,
but
hasn't overheated... so I think I'm good. :-)
-gabriel
This is a good test :), when I do build a kernel the
to capacity for around 1 hour, when set to
MAKEFLAGS="CONCURRENCY-LEVEL=2", quasi -j2. I guess
your mileage
won't vary too much, so several kernel builds
should
be harder than
audio work.
1 hour ... with both cores ?
thats why i dont use these weird kernel buildsystems.
i build a kernel in 10minutes on one core.
simply because i turn the stuff i dont need off...
but this time i missed some important option and it took
pretty long to
get the new kernel working...
for the record:
this was the solution.
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/571164
9:53 p.m.
This is a good
test :), when I do build a kernel the CPU is working
to capacity for around 1 hour, when set to
MAKEFLAGS="CONCURRENCY-LEVEL=2", quasi -j2. I guess your mileage
won't vary too much, so several kernel builds should be harder than
audio work.
1 hour ... with both cores ?
thats why i dont use these weird kernel buildsystems.
i build a kernel in 10minutes on one core.
simply because i turn the stuff i dont need off...
but this time i missed some important option and it took pretty long to
get the new kernel working...
for the record:
this was the solution.
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/571164
9:22 p.m.
On Thu, Apr 29, 2010 at 01:51:20PM -0500, Gabriel M. Beddingfield wrote:
On Thu, 29 Apr 2010, torbenh wrote:
hmm... that wasnt it.
dunno... i dont like the debian build system
it builds everything.
i tried it once, waited 30 minutes, and the kernel it built didnt work.
i just built a proper bzImage using my config from gentoo,
and it worked.
i dont think i will bother with this again.
although this kernel is a bit bitchy :)
rebooting like 3 times in order to install a kernel.
On Thu, Apr 29, 2010 at 11:27:07AM -0500, Gabriel
M. Beddingfield wrote:
IDE, SCSI, or both?
Does anyone out there have an opinion on linux kernel 2.6.31-rt vs.
2.6.33-rt for audio?
i am in the process of updating.
had some problems with udev not creating device nodes for my HD
partitions. i think i solved them. (didnt reboot yet)
make sure the deprecated sysfs interface is off.
CONFIG_SYSFS_DEPRECATED_V2
Thanks for the tip.
FWIW, I built 2.6.33.2-rt13 by tweaking the current
Debian/experimental build system. So far it's been working fine for
me on two different Ubuntu-based, 32-bit, x86 systems.
Things I've noticed:
* The fan seems to run less often (good, it was
running too often before).
* 'cat /proc/cpuinfo' doesn't show the actual current
clock speed without loading in some other modules.
I haven't put it through its paces on RT audio, yet.
-gabriel
--
torben Hohn
9:45 p.m.
On Thu, 29 Apr 2010, torbenh wrote:
dunno... i dont like the debian build system
it builds everything.
Eh, I've warmed up to it. It has its good and bad points.
You can trim out all the arch's you don't want
(debian/config/defines, IIRC) and re-build for just a single
arch:
$ fakeroot make -f ./debian/rules.gen binary-arch_i386_none_686 -j2
-gabriel
9:58 p.m.
Gabriel M. Beddingfield wrote:
On Thu, 29 Apr 2010, torbenh wrote:
spinymouse-sudo@64studio:~$ ls /usr/src/kernel/linux-2.6.33.2-rt13/arch -a
. alpha avr32 cris .gitignore ia64 m32r m68knommu
mips parisc s390 sh um x86_64
.. arm blackfin frv h8300 Kconfig m68k microblaze
mn10300 powerpc score sparc x86 xtensa
I only do need amd64 == x86_64. What option do I need to add?
Ralf
dunno... i dont like the debian build system
it builds everything.
Eh, I've warmed up to it. It has its good and bad points.
You can trim out all the arch's you don't want (debian/config/defines,
IIRC) and re-build for just a single arch:
$ fakeroot make -f ./debian/rules.gen binary-arch_i386_none_686 -j2
-gabriel
9:22 p.m.
On Thu, Apr 29, 2010 at 01:51:20PM -0500, Gabriel M. Beddingfield wrote:
On Thu, 29 Apr 2010, torbenh wrote:
sata == both (or something :)
--
torben Hohn
On Thu, Apr 29, 2010 at 11:27:07AM -0500, Gabriel
M. Beddingfield wrote:
IDE, SCSI, or both?
Does anyone out there have an opinion on linux kernel 2.6.31-rt vs.
2.6.33-rt for audio?
i am in the process of updating.
had some problems with udev not creating device nodes for my HD
partitions.
9:27 p.m.
torbenh wrote:
On Thu, Apr 29, 2010 at 01:51:20PM -0500, Gabriel M.
Beddingfield wrote:
On Noobish: You use the module that call had devices sda too?
On Thu, 29 Apr 2010, torbenh wrote:
sata == both (or something :)
On Thu, Apr 29, 2010 at 11:27:07AM -0500, Gabriel
M. Beddingfield wrote:
IDE, SCSI, or both?
Does anyone out there have an opinion on linux
kernel 2.6.31-rt vs.
2.6.33-rt for audio?
i am in the process of updating.
had some problems with udev not creating device nodes for my HD
partitions.
5114
days inactive
5114
days old
linux-audio-dev@lists.linuxaudio.org
20 comments
4 participants
participants (4)
-
Gabriel M. Beddingfield -
James Warden -
Ralf Mardorf -
torbenh