From: David Henningsson <david.henningsson@canonical.com>
To: alsa-devel@alsa-project.org
Subject: Re: ALC269 mixer nodes
Date: Tue, 03 Aug 2010 08:49:05 +0200 [thread overview]
Message-ID: <4C57BBE1.7040703@canonical.com> (raw)
In-Reply-To: <s5h7hk9nk6c.wl%tiwai@suse.de>
2010-08-02 16:50, Takashi Iwai skrev:
> At Mon, 02 Aug 2010 16:30:57 +0200,
> David Henningsson wrote:
>>
>> Here's yet another ALC269 which I'm unsure of how to fix the right way.
>> There is no way to enable the microphone, and I think the trouble has to
>> do with that the auto parser does not check whether the node is a mixer
>> or a selector. It might be that the "alc269" vs "alc269vb" detection is
>> wrong as well (btw, what does vb stand for?).
>>
>> I unfortunately do not have the full alsa-info output, but the
>> codec-proc is here:
>> http://launchpadlibrarian.net/49076615/Card0.Codecs.codec.2.txt
>> and PCI IDs:
>> http://launchpadlibrarian.net/49076618/PciMultimedia.txt
>
> Are you sure that it's the result with the very latest driver?
The codec-proc might not have been generated with the very latest
driver, but when I run it through hda-emu (with a just-pulled
sound-2.6.git as hda-dir), I get errors as:
send: NID=0x23, VERB=0x701(set_connect_sel), PARM=0x1
invalid connect select for node 0x23
...which makes me believe the error is still there. The error above
comes from patch_realtek.c:14366, btw.
--
David Henningsson, Canonical Ltd.
http://launchpad.net/~diwic
next prev parent reply other threads:[~2010-08-03 6:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-02 14:30 ALC269 mixer nodes David Henningsson
2010-08-02 14:50 ` Takashi Iwai
2010-08-03 6:49 ` David Henningsson [this message]
2010-08-03 7:18 ` Takashi Iwai
2010-08-03 7:22 ` 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=4C57BBE1.7040703@canonical.com \
--to=david.henningsson@canonical.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 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.