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

[Henk Jansen]

Ok, couldn't get the 2.6.10-2.1.ll.rhfc3.ccrma kernel to reccognize my
raid0 setup, but the 2.6.11-0.3.rdt.rhfc3.ccrma kernel does! Using this
kernel I end up with a normally running system that allows me to do
things as usual (mail, internet, ...). However, when I attempt starting
the jack server I obtain:

[root@jaki jans2]# jackstart -R -d alsa -d hw -r 44100
jackstart: cannot get realtime capabilities, current capabilities are:
           =ep cap_setpcap-ep
    probably running under a kernel with capabilities disabled,
    a suitable kernel would have printed something like "=eip"

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]#

Anyone a clue?

Thanks,

--Henk

BTW I have yet refrained from tuning the harddisk.

On Wed, 2005-06-22 at 11:12 -0700, Fernando Lopez-Lezcano wrote:
> On Wed, 2005-06-22 at 04:32, Henk Jansen wrote:
> > On Wed, 2005-06-22 at 11:45, Steve Harris wrote:
> > > Digging around in the recesses of my memory, that might be because you
> > > need an initrd (a thing that can load certain drivers that are needed
> > > before kenel boot finises. Look on the web for instruction about how to
> > > build one, you will nee the raid and md drivers in your initrd if there
> > > not already.
> > 
> > The planetccrma distribution comes with precompiled initrd-*'s and
> > vmlinuz-*. 
> 
> Hmmm, you should not need to "recompile" them. The initrd image used
> during boot is built at kernel install time using the information about
> peripherials that is part of /etc/modprobe.conf. So, it could be that at
> the time of the install the disk controller was not online and then its
> driver did not get added to the initrd image. You could rebuild the
> image by using mkinitrd ("man mkinitrd" for details). 
> 
> What is the raid device hanging from? Are the disks themselves and their
> controller recognized during the boot process? I take it that raid is
> recognized by the original Fedora kernel, right?
> 
> -- Fernando
> 
> > Are the source codes of the planetccrma kernels available so
> > that I can compile them myself?
> > 
> > Although I'm prepared to compile them myself, I still wonder though
> > whether it's necessary: I get the impression from postings in the
> > mailing list that software RAID is not a problem for the planetccrma
> > kernel... (anyway, it's not a problem for my default Fedora Core 3
> > kernel...).
> > 
> > --Henk
> > 
> > (Sorry Steve for the duplicate mailing.)
> > 
> > > 
> > > - Steve
> > > 
> > > On Wed, Jun 22, 2005 at 02:48:18 +0200, Henk Jansen wrote:
> > > > I've succesfully installed the PlanetCCRMA software for my Fedora 3
> > > > system. However, using the low latency kernel
> > > > (...-2.6.10-2.1.ll.rhfc3.ccrma.img) the booting process halted when it
> > > > had to startup my raid device (/dev/md0) with message:
> > > > 
> > > > """
> > > > Checking filesystems
> > > > fsck.ext3: Invalid argument while trying to open /dev/md0 [FAILED]
> > > > """
> > > > 
> > > > (...me ending up in rescue mode). How should I proceed in trying to get
> > > > the kernel working with my raid configuration? Anyone dealt with this
> > > > problem before? Thanks.
> 
> 
> _______________________________________________
> PlanetCCRMA mailing list
> PlanetCCRMA@ccrma.stanford.edu
> http://ccrma-mail.stanford.edu/mailman/listinfo/planetccrma