[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <227130559.2YHlkDm1H6@segfault.sh0n.net>
Date: Fri, 08 Mar 2013 15:13 -0500
From: Shawn Starr <shawn.starr@...ers.com>
To: linux-kernel@...r.kernel.org
Subject: Re: [Linux 3.8/3.9-rc1][alsa][hda] Problem with automute on HDA CX20561 (Hermosa) - Persistent even after power off
On Friday, March 08, 2013 03:06:12 PM Shawn Starr wrote:
> Hello folks,
>
> All of a sudden, it worked fine in Linux kernel 3.8, I believe after booting
> Linux kernel 3.9 (which has ALSA HDA changes). I can no longer hear audio
> from speakers on laptop. If I plug in headphones audio works.
>
> [ 18.434846] hda_codec: CX20561 (Hermosa): BIOS auto-probing.
> [ 18.434932] ALSA sound/pci/hda/hda_auto_parser.c:306 autoconfig:
> line_outs=1 (0x1a/0x0/0x0/0x0/0x0) type:speaker [ 18.434934] ALSA
> sound/pci/hda/hda_auto_parser.c:310 speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) [
> 18.434936] ALSA sound/pci/hda/hda_auto_parser.c:314 hp_outs=2
> (0x19/0x16/0x0/0x0/0x0) [ 18.434937] ALSA
> sound/pci/hda/hda_auto_parser.c:315 mono: mono_out=0x0 [ 18.434939] ALSA
> sound/pci/hda/hda_auto_parser.c:318 dig-out=0x1c/0x0 [ 18.434940] ALSA
> sound/pci/hda/hda_auto_parser.c:319 inputs:
> [ 18.434942] ALSA sound/pci/hda/hda_auto_parser.c:323 Mic=0x18
> [ 18.434944] ALSA sound/pci/hda/hda_auto_parser.c:323 Internal Mic=0x1d
> [ 18.434945] ALSA sound/pci/hda/hda_auto_parser.c:323 Dock Mic=0x17
> [ 18.435835] ALSA sound/pci/hda/patch_conexant.c:4587 hda_codec: Enable
> sync_write for stable communication [ 18.443473] input: HDA Intel Dock Mic
> as /devices/pci0000:00/0000:00:1b.0/sound/card0/input9 [ 18.443563] input:
> HDA Intel Mic as /devices/pci0000:00/0000:00:1b.0/sound/card0/input10 [
> 18.443614] input: HDA Intel Headphone as
> /devices/pci0000:00/0000:00:1b.0/sound/card0/input11 [ 18.443674] input:
> HDA Intel Dock Headphone as
> /devices/pci0000:00/0000:00:1b.0/sound/card0/input12
>
> I did a hard power off, even booted into a Windows OS to see the windows
> kernel driver might reset the autio ports and it didn't fix this even, did
> the kernel driver reprogram the hardware badly somewhere? How can I fix
> this?
>
> Thanks,
> Shawn
Sorry for the noise, this is fixed, I found the cause.
Thanks,
Shawn
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists