[PlanetCCRMA] PlanetCCRMA and RAID: which way to go?

[Fernando Lopez-Lezcano]

On Mon, 2005-06-27 at 11:55, Henk Jansen wrote:
> > > (read on about soundcard ...)
> > > 
> > > > 
> > > > > back from read, ret = 1 errno == Success
> > > > > jackstart: could not give capabilities: Operation not permitted
> > > > > jackd 0.99.36
> > > > > Copyright 2001-2003 Paul Davis and others.
> > > > > jackd comes with ABSOLUTELY NO WARRANTY
> > > > > This is free software, and you are welcome to redistribute it
> > > > > under certain conditions; see the file COPYING for details
> > > > > 
> > > > > JACK compiled with System V SHM support.
> > > > > loading driver ..
> > > > > apparent rate = 44100
> > > > > creating alsa driver ... hw|hw|1024|2|44100|0|0|nomon|swmeter|-|32bit
> > > > > configuring for 44100Hz, period = 1024 frames, buffer = 2 periods
> > > > > Couldn't open hw for 32bit samples trying 24bit instead
> > > > > Couldn't open hw for 24bit samples trying 16bit instead
> > > > > nperiods = 2 for capture
> > > > > Couldn't open hw for 32bit samples trying 24bit instead
> > > > > Couldn't open hw for 24bit samples trying 16bit instead
> > > > > nperiods = 2 for playback
> > > > > jackd watchdog: timeout - killing jackd
> > > > > Aborted
> > > > > [root@jaki jans2]#
> > > > 
> > > > Hmmm, looks like jack is hanging (and its watchdog process is killing
> > > > it)... what soundcard do you have installed?
> > > 
> > > My soundcard: C-Media Electronics Inc CM738
> > > Driver:       snd-cmipci
> > 
> > I'd try to see what happens if you start jack with more periods, for
> > example 3 (option "-n" - perhaps you will also need to reduce the length
> > of the buffer, for example "-p 512 -n 3"). 
> 
> (I'm not running as root anymore)
> 
> [jans2@jaki jans2]$ /usr/bin/jackd -R -d alsa  -r48000 -p512 -n3
> **** alsa_pcm: xrun of at least 0.025 msecs
> **** alsa_pcm: xrun of at least 0.024 msecs
> **** alsa_pcm: xrun of at least 0.037 msecs
> .... <etcetera>

So it definitely has to do with the soundcard and what it can (or can't)
do, I guess. Try more periods to see if that makes a difference.

> However, when I try starting rosegarden in another console, I get:
> 
> [jans2@jaki jans2]$ rosegarden
> kbuildsycoca running...
> PluginFactory::instance(dssi): creating new DSSIPluginFactory
> [/home/jans2/.dssi] [/usr/local/lib/dssi] [/usr/lib/dssi]
> PluginFactory::instance(ladspa): creating new LADSPAPluginFactory
> [/usr/lib/ladspa]
> Rosegarden 4-1.0 - AlsaDriver - alsa-lib version 1.0.8
> 
> JackDriver::initialiseAudio - JACK server not running
> ALSA lib seq_hw.c:451:(snd_seq_hw_open) open /dev/snd/seq failed: No
> such file or directory

Load the sequencer module by hand or enable the alsasound startup script
so that it is loaded on boot ("/sbin/chkconfig alsasound on")

> *** glibc detected *** double free or corruption (!prev): 0x080ccc78 ***

Hmmmm, bug in rosegarden?

> Profiler : id = querying plugins - elapsed = 890ms CPU,  1.019586000R
> real
> [jans2@jaki jans2]$
> 
> ... indicating that (apparently) the JACK server is stil not running.
> Trying to restart the jack server gives me:
> 
> [jans2@jaki jans2]$ /usr/bin/jackd -R -d alsa  -r48000 -p512 -n3
> jackd 0.99.36
> Copyright 2001-2003 Paul Davis and others.
> jackd comes with ABSOLUTELY NO WARRANTY
> This is free software, and you are welcome to redistribute it
> under certain conditions; see the file COPYING for details
> 
> JACK compiled with System V SHM support.
> too many servers already active
> [jans2@jaki jans2]$
> 
> Yet:
> 
> [jans2@jaki jans2]$ ps aux | grep jack
> jans2     8573  0.0  0.0  3720  652 pts/5    S+   20:54   0:00 grep jack
> [jans2@jaki jans2]$
> 
> ...no jackd to be found --- confusing, isn't it?

Yep. 
Maybe a previous jack was killed in a way in which it could not do any
cleanup and left stuff in the temporary directory used to store pipes
and all that. 

In fc3 that should be /var/lib/jack/tmp/ (should be mounted in tmpfs),
make sure that directory is empty and that there are no instances of
jack running. 

-- Fernando