From: Tobin Davis <tdavis@dsl-only.net>
To: Matthew R Hurne <matt.hurne@versatile.com>, Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@alsa-project.org
Subject: Re: no front speaker sound with ALC262
Date: Fri, 21 Mar 2008 13:14:01 -0700 [thread overview]
Message-ID: <1206130441.4863.133.camel@razman.gruemaster.com> (raw)
In-Reply-To: <s5hd4psw4fj.wl%tiwai@suse.de>
Everything is set in motion for me to get an eval unit. I should see it
in about a week. As soon as it comes in, I'll hit the ground running,
and see what I can figure out.
Tobin
On Tue, 2008-03-18 at 14:24 +0100, Takashi Iwai wrote:
> At Tue, 18 Mar 2008 09:11:47 -0400,
> Matthew R Hurne wrote:
> >
> > Tobin Davis wrote:
> > > Ok, it looks like it may be a couple of weeks out, but they are more
> > > than happy to get me a unit. Their sales staff has been bugging for
> > > Linux support for 6 months apparently.
> > >
> > > In the mean time, if you can get me that output, I can at least start
> > > making a dent on this. From the photo, it looks like you have a speaker
> > > jack (green) , line-in (blue), and mic (pink), plus speakers and mic
> > > built in? I'll review the online documents again to be sure.
> > >
> > > Tobin
> >
> > We put some pressure on Tangent to get Linux audio working, and the tech. support guys I spoke with were clearly clueless. :-(
> >
> > I have attached the relevant output from dmesg, and a new alsa-info.sh output.
>
> In your case, the driver cannot work as is because the hardware tells
> that you have no speaker output. It's a bug of BIOS.
>
> As mentioned in the earlier mail, then you'll have to figure out which
> pin corresponds to the speaker output actually manually by trial and
> error. This requires some least knowledge of HD-audio codec. See
> HD-audio documentation available on intel or other web sites.
>
> Regarding the words you listed: the HD-audio codec contains small
> components (called widgets) that are connected with each other. Each
> widget has a unique number id (NID) and has a different role, such as
> DAC/ADC, mixer, selector, pin (the actual I/O), etc. Each widget can
> get/set certain commands, called verbs. You can see the widgets on
> your codec in the codec#* proc file output in alsa-info.sh output.
>
>
> Takashi
--
Tobin Davis
BOFH excuse #64:
CPU needs recalibration
next prev parent reply other threads:[~2008-03-21 20:14 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
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 [this message]
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=1206130441.4863.133.camel@razman.gruemaster.com \
--to=tdavis@dsl-only.net \
--cc=alsa-devel@alsa-project.org \
--cc=matt.hurne@versatile.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox