> At Thu, 12 Aug 2010 23:06:22 +0200,
> Jiri Slaby wrote:
> >
> > On 08/12/2010 08:59 PM,
Valdis.Kletnieks@vt.edu wrote:
> > > On Wed, 11 Aug 2010 16:10:49 PDT,
akpm@linux-foundation.org said:
> > >> The mm-of-the-moment snapshot 2010-08-11-16-10 has been uploaded to
> > >>
> > >>
http://userweb.kernel.org/~akpm/mmotm/
> > >
> > > Something appears to be borked in the ALSA arena. There's no actual volume coming
> > > out of the system, and 'alsamixer' is insisting that the volume slider only goes from 0
> > > to 10% or so, no further. However, experimentation shows that the volume slider
> > > in 'xine' *does* affect the 'Amp-Out vals' lines, and alsamixer has *no* effect on
> > > what 'Amp-Out vals' lists.
> > >
> > > A diff of alsa-info.sh for the two kernels shows them being identical, so I'm only
> > > attaching one copy.
> > >
> > > It may be the weekend before I find time to do a bisection of this.
> >
> > Didn't you (like some other people) get into the state where pulseaudio
> > doesn't work? It chooses as an output a dummy driver automatically, then
> > you can change volume, play sound, but actually it all goes to /dev/null.
> >
> > It took me a while before I figured out that it's a "dummy" driver I
> > have in pulseaudio.
>
> Looks like there is a breakage regarding open/close due to fs/notify/*
> changes. I guess you can hear still sounds like:
>
> % aplay -Dplughw foo.wav
