5 May
2004
5 May
'04
12:48 a.m.
Kai Vehmanen wrote:
Hello all,
this year's first stable Ecasound release is now out!
And while I'm at it, here are some recent interesting Eca-related
links and news items:
* http://4ms.org/influx9/
* http://www.agnula.org/documentation/dp_tutorials/no-x/
* http://emi.thevtek.com/
But now, back to the 2.3.3 release. CVS is tagged with 'v2_3_3' as usual,
and here are the details...:
1. Summary of changes
I'm having trouble compiling ecasound, but I can't compile 2.3.2 now
either, so I think there's something wrong with my system. I'm just
wondering if anyone else is having problems with this.
make fails like this:
PROCEDURE_TIMER::to_string() const':
kvu_procedure_timer.cpp:147: internal compiler error: Segmentation fault
Please submit a full bug report,
with preprocessed source if appropriate.
See <URL:http://gcc.gnu.org/bugs.html> for instructions.
make[2]: *** [kvu_procedure_timer.lo] Error 1
make[2]: Leaving directory
`/home/eric/audio_code/recent_releases/ecasound-2.3.3/kvutils'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory
`/home/eric/audio_code/recent_releases/ecasound-2.3.3'
make: *** [all] Error 2
System details below.
Thanks,
Eric Rz.
asus a7v8x-x
athlon XP 2800+ (2071.203 MHz)
1.5GB PC2700 RAM
12GB / /dev/hda2 (actually a 40G disk)
160GB /mnt/audio/ /dev/hdc1
2GB swap /dev/hda1
(onboard via8235 -- disabled)
ice1712 M-Audio Delta-66 w/omni i/o
ymfpci guillemot maxisound fortissimo -- midi only
debian testing (sarge)
2.6.5 (pre-empt on -- kernel.org sources compiled via make-kpkg)
drives tuned in kernel config
alsa-1.0.4rc2 drivers compiled in kernel tree
realtime-0.0.4 lsm (insmod'ed since make install screws things up)
alsa-1.0.4 (lib, envy24control, tools)
libsndfile-1.0.9 from tar.gz
libsamplerate-0.1.0 from tar.gz
jack-0.98.1
./configure --enable-capabilities --enable-optimize
--with-default-tmpdir=/dev/shm --disable-portaudio --disable-oss
ecasound-2.3.3
./configure --enable-pyecasound=c --disable-oss --disable-arts
--with-largefile
5 May
5 May
5:25 p.m.
On Tue, May 04, 2004 at 10:40:39PM -0400, Eric Dantan Rzewnicki wrote:
Kai Vehmanen wrote:
I'm having trouble compiling ecasound, but I can't compile 2.3.2 now
either, so I think there's something wrong with my system. I'm just
wondering if anyone else is having problems with this.
make fails like this:
PROCEDURE_TIMER::to_string() const':
kvu_procedure_timer.cpp:147: internal compiler error: Segmentation fault
Please submit a full bug report,
with preprocessed source if appropriate.
See <URL:http://gcc.gnu.org/bugs.html> for instructions.
make[2]: *** [kvu_procedure_timer.lo] Error 1
make[2]: Leaving directory
`/home/eric/audio_code/recent_releases/ecasound-2.3.3/kvutils'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory
`/home/eric/audio_code/recent_releases/ecasound-2.3.3'
make: *** [all] Error 2
System details below.
Thanks,
Eric Rz.
Just a note for the archives. This probably has nothing at all to do
with ecasound. My system is severly foobar. Shortly after I wrote that
it locked up completely resulting in widespread filesystem corruption.
Now when I boot it hangs at INIT.
I can get to a shell with alt-sysrq or passing init=/bin/bash at the
lilo prompt, but I haven't had time yet to fully survey the damage.
Anyway ... just wanted to say that the compile problem is most likely
not ecasound's fault in the least.
-Eric Rz. (/me thinking maybe it's time to try demudi)
6:09 p.m.
On Wed, 5 May 2004 15:17:13 -0400 someone called
Eric Dantan Rzewnicki wrote:
Just a note for the archives. This probably has nothing at all to do
with ecasound. My system is severly foobar. Shortly after I wrote that
it locked up completely resulting in widespread filesystem corruption.
Now when I boot it hangs at INIT.
I can get to a shell with alt-sysrq or passing init=/bin/bash at the
lilo prompt, but I haven't had time yet to fully survey the damage.
Anyway ... just wanted to say that the compile problem is most likely
not ecasound's fault in the least.
you hd isn't full, is it?
m
--
----> http://www.mprims.tk
6:35 p.m.
On Wed, May 05, 2004 at 09:56:14PM +0200, mik wrote:
On Wed, 5 May 2004 15:17:13 -0400 someone called
Eric Dantan Rzewnicki wrote:
No, probably not. I'll double check when I get home. But I think I had
only used about 50-60G or so of my 160G audio data drive and around 2-3G
of my 12G / partition on a separate drive.
I suspect such things as futex()'s, preemptive kernel, shared memory
problems, SCHED_FIFO processes getting out of hand, other such realtime
issues, (maybe) mozilla ... not sure really.
As Jack O'Quin pointed out to me recently I really should have been
running that realtime monitoring tool ... forget what it's called now.
Jack, can you send a link to that again? I fear my saved mail will not
be available when I get my box working again ...
-Eric Rz.
Just a note for the archives. This probably has
nothing at all to do
with ecasound. My system is severly foobar. Shortly after I wrote that
it locked up completely resulting in widespread filesystem corruption.
Now when I boot it hangs at INIT.
I can get to a shell with alt-sysrq or passing init=/bin/bash at the
lilo prompt, but I haven't had time yet to fully survey the damage.
Anyway ... just wanted to say that the compile problem is most likely
not ecasound's fault in the least.
you hd isn't full, is it? 
7:17 p.m.
New subject: [linux-audio-user] asoundrc question
I've got a card with 2 inputs, 8 outputs (echo gina 20). ALSA defaults
to using the first two outs for stereo playback. The problem is that one
of those outputs is physically damaged and unusable. Is there a way to
use asoundrc to tell ALSA to use outs 2 and 3 as the default outs
instead of 0 and 1?
7:42 p.m.
New subject: [linux-audio-user] asoundrc question
Is there a way to use asoundrc to tell ALSA to use
outs 2 and 3
as the default outs instead of 0 and 1?
There is indeed a way, Good Sir. You'll need a small rug and about five
minutes of your time.
Recipe:
=======
1) Kneel facing East.
2) Invoke the Name of Power: "Clemens Ladisch"
3) Think happy thoughts of Clemens frolicking in the Black Forest
4) Mentally ask about "asoundrc" and "ttable" syntax.
Your answer will come to you shortly. Lord Clemens seems to have mastered
this asoundrc devilry.
Even the Mad Steward of Gondor realised it was futile without Quality,
=MB=
--
A focus on Quality.
8:16 p.m.
New subject: [linux-audio-user] asoundrc question
Malcolm Baldridge wrote:
Add a few scantily clad beautiful young maidens and the answer will come
sooner... ;-)
Is there a way
to use asoundrc to tell ALSA to use outs 2 and 3
as the default outs instead of 0 and 1?
There is indeed a way, Good Sir. You'll need a small rug and about five
minutes of your time.
Recipe:
=======
1) Kneel facing East.
2) Invoke the Name of Power: "Clemens Ladisch"
3) Think happy thoughts of Clemens frolicking in the Black Forest 4) Mentally ask about "asoundrc" and
"ttable" syntax
Your answer will come to you shortly. Lord Clemens seems to have mastered
this asoundrc devilry.
Even the Mad Steward of Gondor realised it was futile without Quality,
=MB=
8:55 p.m.
New subject: [linux-audio-user] asoundrc question
On Wed, 2004-05-05 at 17:34, Malcolm Baldridge wrote:
There is indeed a way, Good Sir. You'll need a
small rug and about five
minutes of your time.
Recipe:
=======
1) Kneel facing East.
2) Invoke the Name of Power: "Clemens Ladisch"
3) Think happy thoughts of Clemens frolicking in the Black Forest
4) Mentally ask about "asoundrc" and "ttable" syntax.
Your answer will come to you shortly. Lord Clemens seems to have mastered
this asoundrc devilry.
Oh dear. I had a feeling I was going to need to dabble with Arcana and
Magick. Googling "Clemens Ladisch", "asoundrc", and
"ttable" syntax
turned up some very interesting grimoires to pore over. Thanks!
--Doug
How often I found where I should be going only by setting out for
somewhere else. -- R. Buckminster Fuller
6 May
6 May
12:22 a.m.
Eric Dantan Rzewnicki <rzewnickie(a)rfa.org> writes:
Jack, can you send a link to that again? I fear my
saved mail will not
be available when I get my box working again ...
http://www.joq.us/jack/rt_monitor.tgz
If that doesn't help, your system freeze is probably in the kernel.
Good luck,
--
joq
2:50 p.m.
New subject: [linux-audio-user] System freeze (was Re: [ecasound] ecasound 2.3.3 released)
On Wed, May 05, 2004 at 09:15:00PM -0500, Jack O'Quin wrote:
Eric Dantan Rzewnicki <rzewnickie(a)rfa.org>
writes:
Great. thanks.
I managed to get my system back (though I'm pretty sure it's not in good
order). My file system was a total mess. There were around 2000 items in
/lost+found. sed, tar, and vi (at least) were completely missing. man
was rsync. My dpkg/apt database was totally hosed. Much of what should
have been symlinks under /etc/alternatives/ was some sort of data file.
And so on, and so on ...
I found I had something called psed (perl implementation of sed) and
linked it to /bin/sed and floppy-disk-netted a copy of tar from another
box. With that and dselect I managed to reinstall most of the system and
get X and openbox working again. It was an interesting exercise, but I
think I'll need to reinstall anyway. It seems like many shared libraries
are missing or incorrect, i.e. something else has their name ...
When I left it around 1am last night I was trying to compile jack, but
running into issues with ld and libcap.
Anyway, when I have a reasonably clean system again I'll definitely be
running that rt_monitor. I would like to help get to the bottom of what
ever is causing these lockups, so any other advice for getting good
debug output or other troubleshooting tips are welcome.
Thanks,
Eric Rz.
Jack, can you send a link to that again? I fear
my saved mail will not
be available when I get my box working again ...
http://www.joq.us/jack/rt_monitor.tgz
If that doesn't help, your system freeze is probably in the kernel.
Good luck,
--
joq 
3:20 p.m.
New subject: [linux-audio-user] System freeze (was Re: [ecasound] ecasound 2.3.3 released)
On Thu, May 06, 2004 at 12:42:43PM -0400, Eric Dantan Rzewnicki wrote:
I managed to get my system back (though I'm pretty
sure it's not in good
order). My file system was a total mess. There were around 2000 items in
/lost+found. sed, tar, and vi (at least) were completely missing. man
was rsync. My dpkg/apt database was totally hosed. Much of what should
have been symlinks under /etc/alternatives/ was some sort of data file.
And so on, and so on ...
Eeeyuck. That sounds like what happened to me when a hardware
failure (bad RAM) totally hosed my ext2 filesystem a few years back.
The inodes were basically randomized.
Glad you got the important stuff back!
--
Paul Winkler
http://www.slinkp.com
3:48 p.m.
New subject: [linux-audio-user] System freeze (was Re: [ecasound] ecasound 2.3.3 released)
On Thu, May 06, 2004 at 01:13:30PM -0400, Paul Winkler wrote:
On Thu, May 06, 2004 at 12:42:43PM -0400, Eric Dantan
Rzewnicki wrote:
yuck is right. :-}
I wasn't too worried, my audio is all on a separate drive, that
fortunately didn't get scrambled at all as far as I can see.
I still need to make sure some of my ecasound eci python scripts I've
been working on are still ok. I think they are.
I really hope this isn't a hardware problem ...
-Eric Rz.
I managed to get my system back (though I'm
pretty sure it's not in good
order). My file system was a total mess. There were around 2000 items in
/lost+found. sed, tar, and vi (at least) were completely missing. man
was rsync. My dpkg/apt database was totally hosed. Much of what should
have been symlinks under /etc/alternatives/ was some sort of data file.
And so on, and so on ...
Eeeyuck. That sounds like what happened to me when a
hardware
failure (bad RAM) totally hosed my ext2 filesystem a few years back.
The inodes were basically randomized.
Glad you got the important stuff back!
4:15 p.m.
New subject: [linux-audio-user] System freeze (was Re: [ecasound] ecasound 2.3.3 released)
Eric Dantan Rzewnicki <rzewnickie(a)rfa.org> writes:
> Eeeyuck. That sounds like what happened to me
when a hardware
> failure (bad RAM) totally hosed my ext2 filesystem a few years back.
> The inodes were basically randomized.
> Glad you got the important stuff back!
I really hope this isn't a hardware problem ...
I agree with Paul, it sure sounds like either bad RAM or a bad disk
(or disk controller). Try running memtest86 (it's a boot option).
--
joq
5:28 p.m.
New subject: [linux-audio-user] System freeze (was Re: [ecasound] ecasound 2.3.3 released)
On Thu, May 06, 2004 at 01:07:56PM -0500, Jack O'Quin wrote:
Eric Dantan Rzewnicki <rzewnickie(a)rfa.org>
writes:
I agree with Paul, it sure sounds like either bad RAM or a bad disk
(or disk controller). Try running memtest86 (it's a boot option).
--
joq
:( ok ... I'll try that. thanks. -edrz
Eeeyuck.
That sounds like what happened to me when a hardware
failure (bad RAM) totally hosed my ext2 filesystem a few years back.
The inodes were basically randomized.
Glad you got the important stuff back!
I really hope this isn't a hardware
problem ...
7597
days inactive
7599
days old
linux-audio-user@lists.linuxaudio.org
13 comments
8 participants
participants (8)
-
Doug James -
Eric Dantan Rzewnicki -
Eric Dantan Rzewnicki -
Jack O'Quin -
Malcolm Baldridge -
Mark Knecht -
mik -
Paul Winkler