The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: "Adam J. Richter" <adam@yggdrasil.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: "Adam J. Richter" <adam@yggdrasil.com>,
	pshou@realtek.com.tw, matt.jared@intel.com, andy.kopp@intel.com,
	dan.d.kogan@intel.com, linux-kernel@vger.kernel.org
Subject: Re: intel-hda sound too quiet in linux-2.6.25-rc6
Date: Wed, 19 Mar 2008 01:11:46 -0700	[thread overview]
Message-ID: <20080319081146.GA11524@freya.yggdrasil.com> (raw)
In-Reply-To: <s5hwso0nxra.wl%tiwai@suse.de>

Hi Takashi,

	Thank you for your quick response.  Your suggested alsa
commands seem to have worked.  Here is a more detailed response in
case the information contained below might be helpful.


On Tue, Mar 18, 2008 at 11:15:53AM +0100, Takashi Iwai wrote:
[...] 
> This is likely a missing volume setting.  With the upgrade to 2.6.25,
> you may have a different mixer representation and the udev or init
> script didn't restore the old mixer setting properly (typicall missing
> -F option to alsactl).  Also note that aumix doesn't cover all volume
> controls since it's an OSS app.

	I would think that these new volume controls should be made to
default to whatever setting leaves the volume unmodified (usually
"100%"), to minimize disruption and to preserve support for pure OSS
systems.  I would be interested to know if there is some consideration
that outweighs this.

> Anyway, there is too little hardware information here.  Please show
> the output of alsa-info.sh:
> 	http://hg.alsa-project.org/alsa/raw-file/tip/alsa-info.sh  

	I ran this script, and it only showed me the dialog program
getting a segmentation fault (probably my fault), but perhaps the
following information will be helpful:

% lspci -s 14.2
00:14.2 Audio device: ATI Technologies Inc SBx00 Azalia
% lspci -n -s 14.2
00:14.2 0403: 1002:4383

	Vendor 0x1002, product 0x4383 in sound/pci/hda/hda_intel.c has
a pci_device_id entry with AZX_DRIVER_ATI in the extra data field.

	Also, Jeff Garzik's posting about having a similar problem
with a chip described by lspci as "Audio device: Intel Corporation
82801G (ICH7 Family) High Definition Audio Controller (rev 01)"
appears to correspond to PCI vendor 0x8086, PCI device ID 0x27d8,
which has AZX_DRIVER_ICH.


> In most cases, running the following commands solves the mixer issue:
> 
> 	% amixer set Master unmute 80%
> 	% amixer set Front unmute 100%
> 	% amixer set Headphone unmute 100%

	Thank you.  These commands give me approximately the old
volume levels.  In particular, the middle command seems to be the one
that effected the volume that I could hear.

	I hope the little bit of information about the PCI IDs that I
was able to provide above will be helpful.  Thanks again for your
quick response.

Adam J. Richter

  reply	other threads:[~2008-03-19 19:38 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-18  6:23 intel-hda sound too quiet in linux-2.6.25-rc6 Adam J. Richter
2008-03-18  7:41 ` Adam J. Richter
2008-03-18 10:50   ` Takashi Iwai
2008-03-18  7:54 ` Jeff Garzik
2008-03-18 10:52   ` Takashi Iwai
2008-03-18 10:15 ` Takashi Iwai
2008-03-19  8:11   ` Adam J. Richter [this message]
2008-03-19 14:42     ` Takashi Iwai

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=20080319081146.GA11524@freya.yggdrasil.com \
    --to=adam@yggdrasil.com \
    --cc=andy.kopp@intel.com \
    --cc=dan.d.kogan@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matt.jared@intel.com \
    --cc=pshou@realtek.com.tw \
    --cc=tiwai@suse.de \
    /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