All of lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Hans de Bruin <jmdebruin@xmsnet.nl>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	David Henningsson <david.henningsson@canonical.com>
Subject: Re: 3.19-rc1 regression bisected No sound on Dell Latitude d430
Date: Sun, 11 Jan 2015 16:45:43 +0100	[thread overview]
Message-ID: <s5hy4p92ue0.wl-tiwai@suse.de> (raw)
In-Reply-To: <54B26ACE.90406@xmsnet.nl>

At Sun, 11 Jan 2015 13:21:34 +0100,
Hans de Bruin wrote:
> 
> This commit:
> 
> commit 3abb4f4d0e7aaad0d12004b5057f4486a688752b
> Author: David Henningsson <david.henningsson@canonical.com>
> Date:   Thu Oct 16 15:33:46 2014 +0200
> 
>      ALSA: hda - Use "Line Out" name instead of "PCM" when there are 
> other outputs
> 
>      In case there are speakers or headphones as well, anything that only
>      covers the line out should not be labelled "PCM". Let's name it
>      "Line Out" instead for clarity.
> 
>      Signed-off-by: David Henningsson <david.henningsson@canonical.com>
>      Signed-off-by: Takashi Iwai <tiwai@suse.de>
> 
> breaks the sound on my dell laptop.

What sound?  From the speaker, the headphone or the dock output?
Are you using PulseAudio?  What if you adjust/unmute the volume
(likely "Line Out") manually?

In anyway, please give alsa-info.sh output.  Run it with --no-upload
option and attach the output.


thanks,

Takashi

  reply	other threads:[~2015-01-11 15:45 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 [this message]
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

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=s5hy4p92ue0.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.