mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Valdis.Kletnieks@vt.edu
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Wu Fengguang <fengguang.wu@intel.com>,
	linux-kernel@vger.kernel.org, alsa-devel@alsa-project.org
Subject: Re: mmotm 2010-08-11 - audio volume issues
Date: Thu, 12 Aug 2010 21:37:33 +0200	[thread overview]
Message-ID: <s5htymztyf6.wl%tiwai@suse.de> (raw)
In-Reply-To: <5043.1281639572@localhost>

At Thu, 12 Aug 2010 14:59:32 -0400,
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.

Hm, there shouldn't be a change regarding the volume control.
There can be an issue about PCM stream, e.g. in commit 
    eb541337b7a43822fce7d0c9d967ee149b2d9a96
    ALSA: hda - Make converter setups sticky

To be sure, could you try to revert it?  If it doesn't help but still
you get strange volume behavior, please get alsa-info.sh output at
different volume levels for comparison.


thanks,

Takashi

  reply	other threads:[~2010-08-12 19:37 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-11 23:10 mmotm 2010-08-11-16-10 uploaded akpm
2010-08-12 16:18 ` mmotm 2010-08-11 - RCU whinge during very early boot Valdis.Kletnieks
2010-08-16 17:23   ` Paul E. McKenney
2010-10-05 10:05   ` Zdenek Kabelac
2010-10-06 23:04     ` Paul E. McKenney
2010-10-06 23:18       ` Ben Greear
2010-10-18 12:26       ` Zdenek Kabelac
2010-11-07 18:46         ` Paul E. McKenney
2010-08-12 16:36 ` [PATCH] mmc: fix for CONFIG_PM disabled Randy Dunlap
2010-08-18  9:10   ` Uwe Kleine-König
2010-08-12 16:37 ` mmotm 2010-08-11 - lockdep whinges at e1000e driver ifconfig up Valdis.Kletnieks
2010-08-12 18:59 ` mmotm 2010-08-11 - audio volume issues Valdis.Kletnieks
2010-08-12 19:37   ` Takashi Iwai [this message]
2010-08-12 21:06   ` Jiri Slaby
2010-08-12 21:11     ` Takashi Iwai
2010-08-13  2:13       ` Valdis.Kletnieks

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=s5htymztyf6.wl%tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=Valdis.Kletnieks@vt.edu \
    --cc=akpm@linux-foundation.org \
    --cc=alsa-devel@alsa-project.org \
    --cc=fengguang.wu@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®