public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: David Henningsson <david.henningsson@canonical.com>
Cc: Hans de Bruin <jmdebruin@xmsnet.nl>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: 3.19-rc1 regression bisected No sound on Dell Latitude d430
Date: Mon, 12 Jan 2015 12:55:42 +0100	[thread overview]
Message-ID: <s5h8uh89ps1.wl-tiwai@suse.de> (raw)
In-Reply-To: <54B3A90D.7080104@canonical.com>

At Mon, 12 Jan 2015 11:59:25 +0100,
David Henningsson wrote:
> 
> 
> 
> On 2015-01-11 22:44, Hans de Bruin wrote:
> > running 3.19-rc1 alsamixer show these options:
> >
> > Master
> > PCM
> > Line Out
> > Mic Boost
> > Auto Mute mode
> >
> > Line out now controls the vole of the speaker (this 'new' channel had
> > volume 0 so did not hear anything). Changing PCM has no effect.
> 
> So, now that you have adjusted "Line Out" you have sound again, correct?
> 
> Then this might be easiest resolved by just adding a "Line Out" section 
> to /usr/share/alsa/init/default that intializes Line Out to something 
> else than zero. We probably should do that anyway.
> 
> Takashi, do you agree? If so I'll write a patch for it.

Yes, that would be good.

Though, "Line Out" should have been initialized to 0dB as a vmaster
slave by the driver itself (of course only before alsactl saves the
state).


Takashi

      reply	other threads:[~2015-01-12 11:55 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-11 12:21 3.19-rc1 regression bisected No sound on Dell Latitude d430 Hans de Bruin
2015-01-11 15:45 ` Takashi Iwai
2015-01-11 21:44   ` Hans de Bruin
2015-01-12  6:52     ` Takashi Iwai
2015-01-12 18:13       ` Hans de Bruin
2015-01-12 10:59     ` David Henningsson
2015-01-12 11:55       ` Takashi Iwai [this message]

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=s5h8uh89ps1.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=david.henningsson@canonical.com \
    --cc=jmdebruin@xmsnet.nl \
    --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