From: Borislav Petkov <bp@alien8.de>
To: Chris Vine <chris@cvine.freeserve.co.uk>
Cc: Takashi Iwai <tiwai@suse.de>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-sound@vger.kernel.org
Subject: Re: HDA Intel microphone regression in 3.1.0
Date: Wed, 2 Nov 2011 11:54:42 +0100 [thread overview]
Message-ID: <20111102105442.GA30355@gere.osrc.amd.com> (raw)
In-Reply-To: <20111102102554.1f443b9c@laptop.homenet>
(adding some more people to Cc)
On Wed, Nov 02, 2011 at 10:25:54AM +0000, Chris Vine wrote:
> My Lenovo S12 IdeaPad netbook uses a HDA Intel sound card with Realtek
> ALC269 chip. With the 3.1.0 kernel, all microphone input (both with the
> internal microphone and any external microphone) is permanently
> muted, although sound output works OK. Microphone input works correctly
> with the 3.0 and earlier kernels.
>
> The only obvious difference between the 3.0 and 3.1 kernels is that
> with kernel 3.0.7, 'dmesg | grep HDA' gives this:
>
> HDA Intel 0000:00:1b.0: PCI INT A -> GSI 22 (level, low) -> IRQ 22
> HDA Intel 0000:00:1b.0: setting latency timer to 64
> input: HDA Digital PCBeep as /devices/pci0000:00/0000:00:1b.0/input/input10
> input: HDA Intel Mic as /devices/pci0000:00/0000:00:1b.0/sound/card0/input11
> input: HDA Intel Headphone as /devices/pci0000:00/0000:00:1b.0/sound/card0/input12
>
> whereas with kernel 3.1.0 it just gives:
>
> input: HDA Digital PCBeep as /devices/pci0000:00/0000:00:1b.0/input/input9
> input: HDA Intel Mic as /devices/pci0000:00/0000:00:1b.0/sound/card0/input10
> input: HDA Intel Headphone as /devices/pci0000:00/0000:00:1b.0/sound/card0/input11
>
> lspci -v gives the following audio hardware information:
>
> 00:1b.0 Audio device: Intel Corporation N10/ICH 7 Family High Definition Audio Controller (rev 02)
> Subsystem: Lenovo Device 3be9
> Flags: bus master, fast devsel, latency 0, IRQ 22
> Memory at fc140000 (64-bit, non-prefetchable) [size=16K]
> Capabilities: [50] Power Management version 2
> Capabilities: [60] MSI: Enable- Count=1/1 Maskable- 64bit+
> Capabilities: [70] Express Root Complex Integrated Endpoint, MSI 00
> Capabilities: [100] Virtual Channel
> Capabilities: [130] Root Complex Link
> Kernel driver in use: snd_hda_intel
> Kernel modules: snd-hda-intel
>
> lsmod | egrep "snd|sound" gives:
>
> snd_seq_dummy 1023 0
> snd_seq_oss 23792 0
> snd_seq_midi_event 4408 1 snd_seq_oss
> snd_seq 39673 5 snd_seq_dummy,snd_seq_oss,snd_seq_midi_event
> snd_seq_device 4121 3 snd_seq_dummy,snd_seq_oss,snd_seq
> snd_pcm_oss 33087 0
> snd_mixer_oss 12647 1 snd_pcm_oss
> snd_hda_codec_realtek 205307 1
> snd_hda_intel 18347 2
> snd_hda_codec 64459 2 snd_hda_codec_realtek,snd_hda_intel
> snd_hwdep 4420 1 snd_hda_codec
> snd_pcm 57725 3 snd_pcm_oss,snd_hda_intel,snd_hda_codec
> snd_timer 14567 2 snd_seq,snd_pcm
> snd 40539 15 snd_seq_oss,snd_seq,snd_seq_device,snd_pcm_oss,snd_mixer_oss,snd_hda_codec_realtek,snd_hda_intel,snd_hda_codec,snd_hwdep,snd_pcm,snd_timer
> soundcore 4129 1 snd
> snd_page_alloc 5445 2 snd_hda_intel,snd_pcm
>
> Chris
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
--
Regards/Gruss,
Boris.
next prev parent reply other threads:[~2011-11-02 10:54 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-02 10:25 HDA Intel microphone regression in 3.1.0 Chris Vine
2011-11-02 10:54 ` Borislav Petkov [this message]
2011-11-02 11:09 ` Takashi Iwai
2011-11-02 17:07 ` Chris Vine
2011-11-02 18:54 ` Takashi Iwai
2011-11-02 20:25 ` Takashi Iwai
2011-11-03 9:39 ` Chris Vine
2011-11-03 9:59 ` Takashi Iwai
2011-11-03 11:46 ` Chris Vine
2011-11-02 23:32 ` Chris Vine
2011-11-03 8:26 ` Takashi Iwai
2011-11-02 12:40 ` Sergey S. Kostyliov
2011-11-02 17:08 ` Chris Vine
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=20111102105442.GA30355@gere.osrc.amd.com \
--to=bp@alien8.de \
--cc=chris@cvine.freeserve.co.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--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