Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Rene Dohmen <acidjunk@gmail.com>
Cc: alsa-devel@alsa-project.org
Subject: Re: no front speaker sound with ALC262
Date: Fri, 29 Feb 2008 17:57:15 +0100	[thread overview]
Message-ID: <s5hprufpuok.wl%tiwai@suse.de> (raw)
In-Reply-To: <01CED47B-533E-4913-BED5-4DD6E9E86414@gmail.com>

At Fri, 29 Feb 2008 17:24:03 +0100,
Rene Dohmen wrote:
> 
> No I still don't know where the speakers are conencted.
> I asked the support engineers at tangent to send me a detailed  
> blockdiagram of their sound solution and ik think i'll receive that  
> sooner or later.
> 
> So, for now, I just tried passing the EAPD option to all NIDS in the  
> codec#0 file.
> 
> I attached the code#0 file while working with very low volume
> 
> When I run
> sudo hda-verb/hda-verb /dev/snd/hwC0D0  0x03 SET_EAPD 0x02
> or
> sudo hda-verb/hda-verb /dev/snd/hwC0D0  0x02 SET_EAPD 0x02

Doh, I actually misunderstood that your codec were ALC268 but it's
ALC262.  EAPD command can be issued only on widgets that support.
ALC262 has no EAPD pin caps at all. so it doesn't work like that.

Instead, ALC262 (and other Realtek codecs) has a special sequence with
coefficients to the vendor-defined widget.  Yes, it's a black magic.

Try the following sequence:

	0x20 SET_COEF_INDEX 0x07
	0x20 SET_PROC_COEF 0x3060

0x3060 can be different numbers like 0x3070 or 0x3050.
If you set a different number, reset the coef index again (i.e. always
call as a pair).


Takashi

  parent reply	other threads:[~2008-02-29 16:57 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-23  0:45 no front speaker sound with ALC262 Rene Dohmen
2008-02-23  2:28 ` Matthew R. Hurne
2008-02-23  2:29   ` Matthew R. Hurne
2008-02-25 12:49     ` Rene Dohmen
2008-02-26 12:10       ` Takashi Iwai
2008-02-26 12:21         ` Rene Dohmen
2008-02-26 23:19           ` Rene Dohmen
2008-02-27 10:42             ` Takashi Iwai
2008-02-27 18:16               ` Rene Dohmen
2008-02-28 11:14                 ` Takashi Iwai
2008-02-28 11:20                   ` Takashi Iwai
     [not found]                     ` <01CED47B-533E-4913-BED5-4DD6E9E86414@gmail.com>
2008-02-29 16:57                       ` Takashi Iwai [this message]
2008-03-04 13:37                         ` Rene Dohmen
2008-03-04 13:54                           ` Takashi Iwai
2008-03-14 20:54                           ` Matthew R Hurne
2008-02-26 16:59         ` Matthew R. Hurne
2008-03-17 17:07         ` Matthew R Hurne
2008-03-17 18:35           ` Tobin Davis
2008-03-17 19:04             ` Matthew R Hurne
     [not found]               ` <1205781169.27317.165.camel@razman.gruemaster.com>
     [not found]                 ` <47DECB8E.7060007@versatile.com>
     [not found]                   ` <1205792180.27317.188.camel@razman.gruemaster.com>
2008-03-18 13:11                     ` Matthew R Hurne
2008-03-18 13:24                       ` Takashi Iwai
2008-03-21 20:14                         ` Tobin Davis
2008-03-22 17:59                         ` Rene Dohmen
2008-03-22 19:09                           ` Tobin Davis
2008-03-25 10:40                             ` Rene Dohmen
2008-03-28 18:28                               ` Tobin Davis
     [not found]                                 ` <69D07E29-4C67-45C7-B980-BBF6B553C070@gmail.com>
     [not found]                                   ` <1206970216.756.648.camel@razman>
2008-04-15 10:02                                     ` Rene Dohmen
2008-04-15 13:31                                       ` Tobin Davis
2008-04-28 20:57                               ` Tobin Davis

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=s5hprufpuok.wl%tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=acidjunk@gmail.com \
    --cc=alsa-devel@alsa-project.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