All of lore.kernel.org
 help / color / mirror / Atom feed
From: Uros Vampl <mobile.leecher@gmail.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@alsa-project.org
Subject: Re: No sound on Quanta KN1 with kernel 3.4
Date: Wed, 18 Apr 2012 19:33:35 +0200	[thread overview]
Message-ID: <20120418173335.GA27697@zverina> (raw)
In-Reply-To: <s5hlilt6lgo.wl%tiwai@suse.de>

On 18.04.12 18:41, Takashi Iwai wrote:
> Ah, does it affect both?
> What happens if you change the pin 0x10?  Does it affect the headphone
> or speaker output?

Pin 0x0f affects both. Pin 0x10 affects neither.

> Does the headphone output work with 3.4 kernel at all?

No. I always tested both speakers and headphones with each patch (and 
without patches). There was never any sound from either of the two.

> Also, just to be sure, try the patch below in addition to another.
> This will disable the COEF setup, and it wasn't applied to previous
> models.

This patch does the trick! First I tried it with the patch that deletes 
two lines from hda_codec.c, worked already, but there was no Speaker 
control. Then I instead tried with the patch that sets pin 0x0f. Sound 
works and I have a Speaker control. Interesting thing though, the 
Headphone control does nothing and the Speaker control affects both 
speakers and headphones. Maybe pin 0x10 is bogus too.

Also interesting, the Auto-Mute control does nothing. No matter what 
it's set to, when I plug in headphones the speakers go silent. It seems 
the machine has hardware auto-mute handling.

Thank you for your work, I now have sound again!

Regards,
Uroš
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel

  reply	other threads:[~2012-04-18 17:33 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-14 17:10 No sound on Quanta KN1 with kernel 3.4 Uros Vampl
2012-04-14 19:25 ` Takashi Iwai
     [not found]   ` <20120414205209.GA1041@zanic_kista>
2012-04-16 14:07     ` Takashi Iwai
2012-04-16 17:56       ` Uros Vampl
2012-04-16 19:25         ` Takashi Iwai
2012-04-18  8:05           ` Takashi Iwai
2012-04-18  9:55             ` Uros Vampl
2012-04-18 10:20               ` Uros Vampl
2012-04-18 10:27               ` Takashi Iwai
2012-04-18 10:32                 ` Takashi Iwai
2012-04-18 11:36                   ` Uros Vampl
2012-04-18 12:16                     ` Takashi Iwai
2012-04-18 16:25                       ` Uros Vampl
2012-04-18 16:41                         ` Takashi Iwai
2012-04-18 17:33                           ` Uros Vampl [this message]
2012-04-18 18:43                             ` Takashi Iwai
2012-04-18 19:25                               ` Takashi Iwai
2012-04-18 20:27                               ` Uros Vampl
2012-04-19  5:39                                 ` 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=20120418173335.GA27697@zverina \
    --to=mobile.leecher@gmail.com \
    --cc=alsa-devel@alsa-project.org \
    --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 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.