From: Takashi Iwai <tiwai@suse.de>
To: Alex Riesen <raa.lkml@gmail.com>
Cc: alsa-devel@alsa-project.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: regression: from 3.8 to 3.9: headphones output no sound on Intel HDA, codec VIA VT1802
Date: Mon, 13 May 2013 17:26:04 +0200 [thread overview]
Message-ID: <s5h8v3irjeb.wl%tiwai@suse.de> (raw)
In-Reply-To: <CALxABCbP9hkNQ=xTEUMWb+6UhmVs2N-5kauYJe7d=j1z_RL+LA@mail.gmail.com>
At Sun, 12 May 2013 11:53:41 +0200,
Alex Riesen wrote:
>
> Hi,
>
> I just noticed (use the headphones rarely) that the headphones on this
> System76 Lemur Ultra (lemu4) stopped working. There is absolutely no
> output.
>
> I tried reverting all changes to patch_via.c since v3.8, and
> have the sound back, but there wasn't much to revert:
>
> Revert "ALSA: hda - Rearrange INPUT_PIN_ATTR_*"
> Revert "ALSA: hda - Use generic parser for VIA codec driver"
> Revert "ALSA: hda - Enable parsing the independent HP mode as default
> for VIA codecs"
> Revert "ALSA: hda/via - Fix wrong checks of power state bits"
> Revert "ALSA: hda - Fix phantom jacks on VT1708"
> Revert "ALSA: hda - detect jacks on VT1708 even when no streams are active"
> Revert "ALSA: hda - Use generic array for loopback list management"
>
> and one change (which I indeed suspect) is large: the use of generic parser.
>
> The problem is also present in 3.10-rc1. The output of alsa-info.sh attached,
> for 3.8.12 and 3.9.2 respectively.
It's strange that the pin 0x25 shows EAPD 0x00 and pin-control 0x00.
They should be 0x02 and 0xc0 constantly. Is it taken at the moment
the headphone is plugged, right? Please give alsa-info.sh outputs at
both the headphone plugged and unplugged.
Could you check whether changing them makes the headphone output
working? For example, get hda-verb program (see
Documentation/sound/alsa/HD-Audio.txt) and run it like
hda-verb /dev/snd/hwC0D0 0x25 SET_PIN_WID 0xc0
hda-verb /dev/snd/hwC0D0 0x25 SET_EAPD 0x02
thanks,
Takashi
next prev parent reply other threads:[~2013-05-13 15:26 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-12 9:53 regression: from 3.8 to 3.9: headphones output no sound on Intel HDA, codec VIA VT1802 Alex Riesen
2013-05-12 9:58 ` Fwd: " Alex Riesen
2013-05-13 15:26 ` Takashi Iwai [this message]
2013-05-13 15:53 ` Takashi Iwai
2013-05-13 18:24 ` Alex Riesen
2013-05-14 5:59 ` Takashi Iwai
2013-05-14 10:58 ` Takashi Iwai
2013-05-14 19:55 ` Alex Riesen
2013-05-15 5:20 ` Takashi Iwai
2013-05-15 20:17 ` Alex Riesen
2013-05-16 11:00 ` Takashi Iwai
2013-05-16 20:10 ` Alex Riesen
2013-05-17 6:04 ` Takashi Iwai
2013-05-18 20:29 ` Alex Riesen
2013-05-22 21:06 ` Alex Riesen
2013-05-23 16:34 ` Takashi Iwai
2013-05-23 18:38 ` Alex Riesen
2013-05-24 13:29 ` Takashi Iwai
2013-05-24 16:36 ` Alex Riesen
2013-05-24 17:22 ` Takashi Iwai
2013-05-24 21:32 ` Alex Riesen
2013-05-29 15:42 ` Takashi Iwai
2013-05-31 10:31 ` Alex Riesen
2013-05-31 13:05 ` Takashi Iwai
2013-05-31 15:32 ` Alex Riesen
2013-05-31 18:00 ` Takashi Iwai
2013-05-31 19:36 ` Alex Riesen
2013-06-03 10:05 ` Takashi Iwai
2013-06-03 18:49 ` Alex Riesen
2013-06-04 9:48 ` Takashi Iwai
2013-05-14 19:54 ` Alex Riesen
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=s5h8v3irjeb.wl%tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=linux-kernel@vger.kernel.org \
--cc=raa.lkml@gmail.com \
/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