>>> On Wed, 28 Nov 2001 15:17:12 -0800, Jeremy Brown <mee@xxxxxxx> said:
[ ... ]
mee> 3. Run one of the cute GUI mixers, like gmix or kmix, and turn up the
mee> levels again. I have no idea why this is necessary, but it is on my
mee> machines.
>> This should not be necessary if 'alsactl restore' is part of the ALSA
>> startup script of your distribution.
mee> It works when I use alsa without devfs, but does not work when I
mee> use alsa with devfs. /dev/sound/dsp and friends are not created
mee> until I run gmix or kmix. [ ... ]
Ahhhhhhhhhh, that's because they are OSS mixers, and they trigger (via
MODLOAD it hink) the loading of the three ALSA/OSS ompatibility modules.
But 'alsactl' and 'xamixer' (as well as 'amixer' [command line] or
'alsamixer' [curses]) all use the native ALSA devices; and the simulated
OSS devices are just wrappers around them (so if you restore the
settings of the ALSA devices with 'alsactl' the OSS device settings are
reset too).
BTW, I just load explicitly in my local boot script the relevant
modules:
modprobe snd-card-emu10k1
modprobe snd-mixer-oss
modprobe snd-pcm-oss
modprobe snd-seq-oss
This most definitely creates all the relevant entries from the
beginning.
|