From: Takashi Iwai <tiwai@suse.de>
To: Uros Vampl <mobile.leecher@gmail.com>
Cc: alsa-devel@alsa-project.org
Subject: Re: No sound on Quanta KN1 with kernel 3.4
Date: Wed, 18 Apr 2012 18:41:59 +0200 [thread overview]
Message-ID: <s5hlilt6lgo.wl%tiwai@suse.de> (raw)
In-Reply-To: <20120418162527.GA27483@zverina>
At Wed, 18 Apr 2012 18:25:27 +0200,
Uros Vampl wrote:
>
> On 18.04.12 14:16, Takashi Iwai wrote:
> > Yes, but it alone doesn't help for analysis because it's already an
> > abstracted mixer element. We need to figure out which pin corresponds
> > to the speaker output. It must be either 0x0f or 0x11.
> >
> > BTW, any reason to set the "Speaker" volume so low? It's almost
> > inaudible. Raise this volume.
>
> No reason. I tried again with all volume sliders to the max, still no
> sound.
>
> > If raising volume doesn't change, and if you can still run the older
> > kernel, try to change the pin control via hda-verb like:
> > # hda-verb /dev/snd/hwC0D0 0x0f SET_PIN_WID 0x00
> > and check whether the speaker still works. If 0x0f doesn't change,
> > try 0x11,
> > # hda-verb /dev/snd/hwC0D0 0x11 SET_PIN_WID 0x00
> >
> > If the pin 0x0f actually changes the speaker output, use the patch
> > below instead of the previous one.
>
> By older kernel, you mean 3.3? If I do
> # hda-verb /dev/snd/hwC0D0 0x0f SET_PIN_WID 0x00
> on 3.3, sound disappears. On both speakers and headphones. Doing
> # hda-verb /dev/snd/hwC0D0 0x0f SET_PIN_WID 0x40
> turns sound back on. That means we have our pin, right?
Ah, does it affect both?
What happens if you change the pin 0x10? Does it affect the headphone
or speaker output?
> Well, I tried the new patch which sets 0x0f as the speaker pin, no
> sound. Attached is alsa-info with this patch.
>
> > > Also, there's only one capture control now.
> >
> > This is correct. When there are only internal and external mics,
> > the driver enables the auto-mic switching mode.
> >
> > > Shouldn't I be able to
> > > choose whether to capture from internal or external mic?
> >
> > Just plugging the mic jack should switch to the external mic
> > automatically just like the headphone/speaker switch.
>
> Ah interesting, that's good info to have.
>
> So what now? Neither of the patches work. Does the fact that pin 0x0f
> controls both speakers and headphones on kernel 3.3 provide a clue?
Does the headphone output work with 3.4 kernel at all?
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.
Takashi
---
diff --git a/sound/pci/hda/patch_realtek.c b/sound/pci/hda/patch_realtek.c
index 2508f81..15cdc21 100644
--- a/sound/pci/hda/patch_realtek.c
+++ b/sound/pci/hda/patch_realtek.c
@@ -789,6 +789,7 @@ static void alc_auto_init_amp(struct hda_codec *codec, int type)
case ALC_INIT_DEFAULT:
switch (codec->vendor_id) {
case 0x10ec0260:
+#if 0
snd_hda_codec_write(codec, 0x1a, 0,
AC_VERB_SET_COEF_INDEX, 7);
tmp = snd_hda_codec_read(codec, 0x1a, 0,
@@ -798,6 +799,7 @@ static void alc_auto_init_amp(struct hda_codec *codec, int type)
snd_hda_codec_write(codec, 0x1a, 0,
AC_VERB_SET_PROC_COEF,
tmp | 0x2010);
+#endif
break;
case 0x10ec0262:
case 0x10ec0880:
next prev parent reply other threads:[~2012-04-18 16:42 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 [this message]
2012-04-18 17:33 ` Uros Vampl
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=s5hlilt6lgo.wl%tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=mobile.leecher@gmail.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 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.