Soundcard configuration lost following a reboot

Michael Schwendt fedora at wir-sind-cool.org
Sat Sep 4 12:48:43 UTC 2004


On Thu, 2 Sep 2004 10:20:20 -0400, Allen Winter wrote:

> > whether kudzu detected your soundcard as NEW 
> I don't believe it did because it would have asked me to configure it, right?

But it did set up /etc/modprobe.conf for you, because now you've got
the alsactl entries in there.
 
> > and what you have got in /etc/modprobe.conf currently.
> # cat /etc/modprobe.conf
> alias eth0 natsemi
> alias snd-card-0 snd-ali5451
> install snd-ali5451 /sbin/modprobe --ignore-install snd-ali5451 && /usr/sbin/alsactl restore >/dev/null 2>&1 || :
> remove snd-ali5451 { /usr/sbin/alsactl store >/dev/null 2>&1 || : ; }; /sbin/modprobe -r --ignore-remove snd-ali5451
> alias usb-controller ohci-hcd
> install ipv6 /bin/true
> alias sound_slot_1 off
> 
> And.. sound config does not seem to survive a reboot.  I need to re-run system-config-soundcard
> on each reboot.

That has different reasons and indicates that you still did not set/save
all your audio mixers, because the entries in /etc/modprobe.conf restore
ALSA mixers upon loading the modules. ALSA (the Advanced Linux Sound
Architecture) in Fedora Core 2 comes with two audio drivers, native ALSA
and OSS emulation. Depending on what audio devices files your applications
use, you may need to set different mixers. /dev/dsp and /dev/mixer are
OSS, /dev/snd/* are ALSA. system-config-soundcard justs sets the mixers
for the test sound to be played on /dev/dsp (OSS), so whatever you try
after a reboot, it seems to use OSS and the OSS mixer has not been set
up correctly. Naturally, setting ALSA mixers should get the OSS mixers
in sync, but that doesn't seem to work everywhere and with every audio
driver.

-- 
Fedora Core release 1 (Yarrow) - Linux 2.4.22-1.2199.nptl
loadavg: 0.42 0.28 0.19





More information about the users mailing list