> I investigated a bit why i had no sound at startup, i found several
oddities
> in alsa launch process...
>
Good :-)
> In /etc/init.d/alsa script:
> 1) line 73, the awk scriplet filter every line snd-card-? and
sound-slot-?
> patterns from /etc/modules.conf
> alias snd-card-0 snd-card-ens1371
> alias sound-slot-0 snd-card-0
> As sound-slot-? lines are just oss-compatibility aliases, why not just
> filter
> on real alsa drivers (snd-card-? patterns) only ?
>
> 2)line 101:
> found)
> success;echo
> exit 1
> ;;
> If it is a success, it should be exit 0 rather
>
> in /etc/devfsd.conf, the following lines given in alsa/INSTALL have
> vanished:
> REGISTER sound/.* PERMISSIONS root.audio 660
> REGISTER snd/.* PERMISSIONS root.audio 660
>
This is not needed and is controlled by
- pam_console_apply_devfsd.so line in devfsd.conf together with
- /etc/security/console.perms, specifically
<sound>=/dev/dsp* /dev/audio* /dev/midi* \
/dev/mixer* /dev/sequencer \
/dev/sound/* /dev/snd/* /dev/beep \
^^^^^^^^^^^^^^^^^^^^^^^
> But the real error comes from a buggy launch sequence:
> When /etc/init.d/alsa script is invocated, alsa main module is already
> loaded, the script refuse to load oss compatibility layer (that is the
cause
> of missing /dev/dsp), and echoes "alsa already running". Now, where
could
> this damn module be loaded in launch sequence ?
I strongly suspect it comes from this line in /etc/devfsd.conf:
# ALSA stuff
LOOKUP snd MODLOAD ACTION snd
Another less likely candidate is in /etc/modules.devfs
alias /dev/sound sound-slot-0
...
# Soundcard
alias /dev/audio /dev/sound
alias /dev/mixer /dev/sound
alias /dev/dsp /dev/sound
alias /dev/dspW /dev/sound
alias /dev/midi /dev/sound
Could you remove them one-by-one and tell if it helps? It is good idea
to clean /lib/dev-state every time in between :-))
Still surprisingly enough I never had problem with ALSA even with these
lines. But I never had this nonsense in /etc/modules.conf; I always had
just
alias snd-card-0 snd-emu10k1
and sound worked just fine.
-andrej
