Alexander E. Patrakov wrote:
> DJ Lucas wrote:
>
>> I have 4 or 5 SBLive! cards (all identical)...lets see
>> what happens. Never had more than 2 in a single PC before. :-)
>
>
> For me to remove the FIXME, it would be sufficient to post
> /etc/asound.state after setting different volumes on two identical cards
> and "alsactl store".
>
Success! Unfortunately, not all the cards were identical, but two of
them were. I have another, but I'd have to drop an important box to get
to it, and it's not necessary anyway. Test case was three SBLive! cards
(EMU10K1 chipset). One is a CT10000(I can't read it exactly, haven't
removed it from the machine) and two CT3830s (Identical). I sent
asound.state to my home dir on belgarath, but the test case works as
expected...cold boot to make certain that nothing residual or anything
of that nature.
For recap, here are the contents of the alsa helper:
[EMAIL PROTECTED] ~]# cat /etc/dev.d/snd/alsa.dev
#!/bin/sh -e
DEV_BASENAME="${DEVNAME##*/}"
x=0
while [ $x -lt 20 ]
do
sleep 1
if [ -f /usr/sbin/alsactl ]; then
case "$DEV_BASENAME" in
controlC[0-7])
N="${DEV_BASENAME#controlC}"
alsactl restore $N
;;
esac
exit 0
else
if [ $x -eq 20 ]; then
exit 1
fi
fi
done &
[EMAIL PROTECTED] ~]#
Next issue with this is the sample soundfont loading. I would think it
could be reasonably assumed that machines requiring soundfonts to be
loaded would have some horsepower and that timing is not an issue....but
assumptions are bad! We can leave well enough alone, or add a second
specific handler for individual devices. Alex, am I correct in my
assumption that the alsa.dev script will run before any device specific
scripts, but the device scripts will run in order? I still don't have
access to my soundfonts...or sfxload for that matter, but it should be
easy enough to find.
-- DJ Lucas
--
http://linuxfromscratch.org/mailman/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
