alsa mute

[Timothy]

Thanks,

Seems it is fixed in modutils-2.4.26-16, but that just hasn't made the
developement tree yet.

Timothy

On Wed, 2004-05-05 at 14:00, Alexander Kirillov wrote:
> See:
> https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=119866
> https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=115932
> 
> Sasha
> 
> On Wed, 2004-05-05 at 13:09, Timothy wrote:
> > I have a laptop with a Sis chipset Si7012 and a desktop with an
> > Ensoniq.  The PCM slider is set to zero after each boot.  After saving
> > the settings I just put a "alsactl restore" entry in rc.local to restore
> > my settings.  Has (does) this need to be bugzilla'd?
> > 
> > Timothy
> > 
> > On Fri, 2004-04-30 at 17:44, Michael Schwendt wrote:
> > > On Fri, 30 Apr 2004 16:31:12 -0400, Alexander Kirillov wrote:
> > > 
> > > > On Fri, 2004-04-30 at 13:59, Alexander Kirillov wrote:
> > > > 
> > > > > /etc/asound.state is saved at shutdown, and running alsactl restore
> > > > > immediately after login  does restore the correct values for PCM and
> > > > > other controls. So the problem seems to be that modprobe didn't run
> > > > > alsactl restore at startup.  
> > > > > 
> > > > 
> > > > > Apr 30 16:15:47 Aristotle kernel: MC'97 1 converters and GPIO not ready (0xff00)
> > > 
> > > That is a modem detection message.
> > > 
> > > > Apr 30 16:15:47 Aristotle kernel: intel8x0_measure_ac97_clock: measured
> > > > 49596 usecs
> > > > Apr 30 16:15:47 Aristotle kernel: intel8x0: clocking to 48000
> > > 
> > > That configures your audio chipset to 48 kHz.
> > > 
> > > > Apr 30 16:15:47 Aristotle modprobe: FATAL: Error running install command
> > > > for sound_slot_1 
> > > 
> > > sound-slot-1 would be the second soundcard and OSS, sound-slot-0 the first.
> > > (/etc/modprobe.conf.dist handles the OSS stuff)
> > > 
> > > > Apr 30 16:18:28 Aristotle last message repeated 2 times
> > > > Apr 30 16:22:01 Aristotle modprobe: FATAL: Error running install command
> > > > for sound_slot_1 
> > > > 
> > > > Still can't understand why modprobe fails, though
> > > > 
> > > > 
> > > > OK, seems that these lines in sys log explain why:
> > > > 
> > > > 
> > > 
> > 
>