LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Matej Laitl <strohel@gmail.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel <alsa-devel@alsa-project.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [ALSA] HDA: no sound in headphone-out caused by commit f889fa91ad47e (2.6.25-rc1 regression)
Date: Tue, 12 Feb 2008 19:24:35 +0100 [thread overview]
Message-ID: <200802121924.35232.strohel@gmail.com> (raw)
In-Reply-To: <s5hmyq6t7u5.wl%tiwai@suse.de>
Takashi Iwai wrote:
> Matej Laitl wrote:
> > Yes, this "slightly better" patch applied on top of your first patch
> > against hda_codec.c did the trick, but with some side-effects:
> > * the "Speaker" switch now mutes/unmutes speakers
> > * muting/unmuting "Front" channel now has zero effect (in 2.6.24 it had
> > the same effect as the "Speaker" switch now has)
> > * changing volume on "Front" channel now affects volume in headphones
> > (was not so in 2.6.24)
>
> This is what your BIOS sets up. The main output is connected to the
> docking station. That's why "Front" (a silly name for ALC262; it
> should read "Line Out", maybe will be renamed in later versions)
> switch doesn't work.
> OTOH, all outputs (speaker, headphone and line-outs) use the same DAC,
> and this is controlled via line-out volume, i.e. "Front" volume.
I was actually wrong when saying the "Front" channel did not influence HP-out
in 2.6.24 - it did, so no regressions here.
> > So there are now 3 vol controls that affect both speakers and headphones:
> > * Master (which appeared somewhere between 2.6.24 and .25-rc1), when set
> > to zero, the sound is still audible in speakers and headphones
>
> This must be the behavior of the codec chip... Did "Front" volume 0
> mute in the earlier version? If not, it actually doesn't mute with
> the lowest volume. Use the master switch to mute.
>
> Anyway, attach the alsa-info.sh output at the moment Master volume is
> zero.
No, setting Master and/or Front channel to 0% did not mute audio in any
version I used.
I'm now listening to music with Master=0% and Front=0%, the sound is at well
audible volume. Pastebin for this configuraion is here:
http://pastebin.ca/901459
However I don't consider it a problem, it's mutable by PCM and HP/Speaker
switches. Funny thing is that resulting volume of those 3 setting is equal:
* Master=0, Front=0
* Master=100%, Front=0
* Master=0, Front=100%
But when both set to let's say 50, changing one of these audibly affects
resulting volume.
> > * PCM, working as expected (0 volume = no sound)
> > * Front (0 volume = still audible sound)
> >
> > So it is usable now (and those Speaker and Headphones on/off switches
> > make sense), but kinda suboptimal. (is it my BIOS who is to blame?)
>
> Yep. For the perfect solution, you'd need to create a static "patch"
> for this particular model instead of auto-configuration. Then you can
> adjust everything as you like.
Would it be easy to do this in a robust way? If not, it's not worth it.
On a side note, I experience increased noise when not playing anything during
2.6.24 -> .25-rc1 upgrade, but this is probably completly unrelated to
today's problem.
Anyways, thanks for your effort and patches, Takashi.
Matej Laitl
next prev parent reply other threads:[~2008-02-12 18:24 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-11 20:58 Matej Laitl
2008-02-12 10:13 ` Takashi Iwai
2008-02-12 10:50 ` Matej Laitl
2008-02-12 11:02 ` Takashi Iwai
2008-02-12 11:34 ` Takashi Iwai
2008-02-12 12:06 ` Matej Laitl
2008-02-12 14:02 ` Takashi Iwai
2008-02-12 14:13 ` Takashi Iwai
2008-02-12 15:27 ` Matej Laitl
2008-02-12 17:14 ` Takashi Iwai
2008-02-12 18:24 ` Matej Laitl [this message]
2008-02-12 22:57 ` Matej Laitl
2008-02-13 10:59 ` Takashi Iwai
2008-02-13 12:05 ` Matej Laitl
2008-02-13 13:06 ` Takashi Iwai
2008-02-13 15:00 ` Matej Laitl
2008-02-13 15:25 ` Takashi Iwai
2008-02-13 11:01 ` Takashi Iwai
2008-02-12 11:36 ` Matej Laitl
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=200802121924.35232.strohel@gmail.com \
--to=strohel@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tiwai@suse.de \
--subject='Re: [ALSA] HDA: no sound in headphone-out caused by commit f889fa91ad47e (2.6.25-rc1 regression)' \
/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
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).