From: Mathieu Bouffard <mbouffard@strangequarks.org>
To: alsa-devel@alsa-project.org
Subject: HDA Intel/ALC269 microphone problem
Date: Tue, 31 May 2011 21:16:10 -0400 [thread overview]
Message-ID: <4DE592DA.8070307@fedoraproject.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 856 bytes --]
Read a few bug reports (going back to 2009!) around where users couldn't
use their microphone with HDA Intel/ALC269. I had one set up JACK for 2
playback channels and 1 capture channel, make an .asoundrc to route
everything to pulse which is started with a configuration only using
module-jack-sink and module-jack-source, start it up and the microphone
and the whole setup worked. But that's quite a hassle for a workaround!
I had suspicions that it was the stereo mic causing problem and forcing
mono would work and it seems to be the case. I attached a patch, hoping
that the fix might be as simple as forcing mono at the ALSA level, but I
don't think it'll be that simple... Can someone more experienced see if
more is needed, and if not then commit it?
(orig file is from 3.0-rc1 source)
--
Mathieu Bouffard<mbouffard fedoraproject org>
[-- Attachment #2: realtek.patch --]
[-- Type: text/plain, Size: 1036 bytes --]
Changelog: this is probably not the only fix needed here, see the FIXME comment. I don't have the hardware
to test this.
Signed-off-by: Mathieu Bouffard <mbouffard@fedoraproject.org>
--- sound/pci/hda/patch_realtek.c 2011-05-29 20:43:36.000000000 -0400
+++ sound/pci/hda/fixed_patch_realtek.c 2011-05-31 20:48:43.621911836 -0400
@@ -14659,8 +14659,14 @@
static const struct hda_pcm_stream alc269_44k_pcm_analog_capture = {
.substreams = 1,
- .channels_min = 2,
- .channels_max = 2,
+ .channels_min = 1,
+ .channels_max = 1,
+ /* FIXME I read multiple bug reports where ALC269 users couldn't use their microphone. I had
+ * one set up JACK with two channels for output, and only one for input then route
+ * pulseaudio's sink/source to JACK as a test. It worked, it would seem as if this
+ * ALC269 does not support stereo capture? The above is probably not the only fix needed
+ * here, leaving it up to somebody more experienced.
+ */
.rates = SNDRV_PCM_RATE_44100, /* fixed rate */
/* NID is set in alc_build_pcms */
};
[-- Attachment #3: Type: text/plain, Size: 0 bytes --]
reply other threads:[~2011-06-01 1:16 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4DE592DA.8070307@fedoraproject.org \
--to=mbouffard@strangequarks.org \
--cc=alsa-devel@alsa-project.org \
--cc=mbouffard@fedoraproject.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