Tony Kuneck wrote:
Hi all,
_First_ issue: In the current dev book svn-20060519, there is this section:

cat > /etc/udev/rules.d/15-alsa.rules << "EOF"
# Give the audio group ownership of sound devices
SUBSYSTEM=="sound",       GROUP="audio"

SUBSYSTEM=="snd",         GROUP="audio"

# ALSA Devices
# When a sound device is detected, restore the volume settings
KERNEL=="controlC[0-9]*", ACTION=="add", RUN+="/usr/sbin/alsactl restore %n"

KERNEL="hw[CD0-9]*",      NAME="snd/%k"
KERNEL="pcm[CD0-9cp]*",   NAME="snd/%k"
KERNEL="midiC[D0-9]*",    NAME="snd/%k"
KERNEL="timer",           NAME="snd/%k"

KERNEL="seq",             NAME="snd/%k"
EOF
chmod 644 /etc/udev/rules.d/15-alsa.rules

There should be double == for lines 8 thru 12, KERNEL==. In udev
language, a single = corresponds to a setting, and a double ==
corresponds to a matching, which is clearly what is to be done here.
I've attached a corrected 15-alsa.rules file

_Secondly_: /usr may not be mounted when udev deals with this action,
and so /usr/sbin/alsactl restore [0-9]* does not get called, (which is
the case I have now, I load the sound card module using
/etc/sysconfig/modules at which time /usr is not mounted). I'm
considering compiling a static version of alsactl (it only depends on
/usr/lib/asound.so.2, the other required libraries are in /lib) to put
into /sbin/ just so udev can call it at any time no matter when /usr
is mounted. But this does not seem to be the elegent solution.

Regards,


I've found it best to ignore the advice from the LFS/BLFS crowd who are (unusually) obsessed with getting udev to do everything :-) Not a criticism really, most times the guys give excellent advice.

I load the alsa modules with my modules script and then have my alsa bootscript run to reload the volumes. It works for any udev version too.

Eventually udev will stabilize, and then the right way might be to use it for this stuff, but not yet (IMNSHO).

R.

--
http://linuxfromscratch.org/mailman/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Reply via email to