Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Delcypher <delcypher@gmail.com>
Cc: alsa-devel@alsa-project.org,
	Po-Hsu Lin <po-hsu.lin@canonical.com>,
	David Henningsson <david.henningsson@canonical.com>
Subject: Re: Regression Intel Corporation Haswell-ULT HD Audio	Controller
Date: Mon, 05 May 2014 10:02:14 +0200	[thread overview]
Message-ID: <s5h1tw8irg9.wl%tiwai@suse.de> (raw)
In-Reply-To: <CANNJ_zh6HXT-pdkOV9XpDor3J1aFVbi3zbHLyDnpgisu7DdMdA@mail.gmail.com>

At Sat, 3 May 2014 12:57:55 +0100,
Delcypher wrote:
> 
> Hi,
> 
> I was told to report my bug here because the ALSA bug tracker is no
> longer active.
> 
> I'm having an issue with " Intel Corporation Haswell-ULT HD Audio
> Controller" card which is inside the Dell XPS13 9333 developer edition
> [1].
> 
> I've tried two different distributions
> 
> * Arch Linux (kernel 3.14)
> Output of alsa-utlils-alsa-info.sh [2]
> 
> * Ubuntu 14.04 LTS (kernel 3.13)
> Output of alsa-utlils-alsa-info.sh [3]
> 
> The card behaves correctly under Ubuntu but under Arch Linux I've
> observed the following issues.
> 
> - The microphone does not work correctly. In alsamixer I select
> "Internal Mic" as my capture device but when I do
> 
> $ arecord -d 5 test.wav
> $ aplay test.wav
> 
> test.wav contains silence.
> 
> I've also tried enabling/disabling "CAPTURE" on the Capture channel at
> the same time - I don't really understand why this channel is here
> (seems a little bizarre) but enabling/disabling "CAPTURE" on this
> channel doesn't seem to make any difference anyway. Under Ubuntu the
> "arecord... aplay" command works correctly.
> 
> - There probably isn't a way to reproduce this but when I first
> installed Arch Linux the sound card was put in a state where the
> headphone jack would not work at all. Sound would continue playing out
> of the speakers when the headphone jack was inserted and no sound
> would come out of the headphones. I did notice that if the headphone
> jack was only partially inserted I would get some sound sent to one of
> the headphones.
> 
> My intuition is that the card is probably being incorrectly
> initialised because if you take a look at the output of
> alsa-utils-alsa-info.sh and diff them. Two very big differences I
> noticed were that
> 
> - The card name (from lscpi) is "Intel Corporation Haswell-ULT HD
> Audio Controller" under Ubuntu but under Arch Linux it is "Intel
> Corporation Device 0a0c"
> - The card codec is "Realtek ALC668" under Ubuntu but is "Realtek
> ALC3661" under Arch Linux.
> 
> One interesting I did notice is that under Arch Linux it is possible
> to use the microphone from the Audacity program by selecting "HDA
> Intel PCH: ALC3661Analog (hw0:0) Internal mic:0" as the input (this is
> not the default). Unfortunately I know of no way to make other
> applications use this.
> 
> Any thoughts on how to fix this?
> 
> [1] http://www.dell.com/uk/business/p/xps-13-linux/pd
> [2] https://gist.github.com/delcypher/11367224
> [3] https://gist.github.com/delcypher/11367302

The "Capture Switch" is off, according to alsa-info.sh output.
Try to turn it on.
   % amixer -c0 set Capture cap

If this doesn't help, it must be a quirk added in 3.14 kernel:
  commit f47e5dc464251f661da9495fcbf003a0d22c1360
  ALSA: hda - Add a headset quirk for Dell XPS 13
    
I added relevant people in Cc.

Meanwhile, you can try to pass model=nofixup to snd-hda-intel module
for avoiding the added fixup above.


thanks,

Takashi

  parent reply	other threads:[~2014-05-05  8:02 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-03 11:57 Regression Intel Corporation Haswell-ULT HD Audio Controller Delcypher
2014-05-04  3:09 ` Raymond Yau
2014-05-04 11:45   ` Delcypher
2014-05-05  8:02 ` Takashi Iwai [this message]
2014-05-05  8:46   ` Delcypher
2014-05-05  8:56     ` Fwd: " Delcypher
2014-05-05  9:02     ` 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=s5h1tw8irg9.wl%tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=david.henningsson@canonical.com \
    --cc=delcypher@gmail.com \
    --cc=po-hsu.lin@canonical.com \
    /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