From: Chris Pemberton <cjpembo@gmail.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@alsa-project.org
Subject: Re: possible snd_hda_intel jack-sensing issue with device 8086:1c20
Date: Thu, 13 Nov 2014 00:07:12 -0600 [thread overview]
Message-ID: <54644A90.3030507@gmail.com> (raw)
In-Reply-To: <s5hegt8rh2m.wl-tiwai@suse.de>
I opened up the machine and re-seated the connector to the motherboard.
The problem persists.
The motherboard has two adjacent ports for front panel audio; one marked
"HD" and the second "AC97". The single cable from the front audio jacks
has two connectors at the end; one marked "HD" and the other "AC97".
If I connect the cable end marked "AC97" to the port marked "AC97" and
set the BIOS for "AC97 front panel", should I expect everything to
work? I'd have HD audio at the rear ports and AC97 at the front? That
would be fine as I only expect to be using headphones at the front from
time to time.
Thanks
On 11/12/2014 01:52 AM, Takashi Iwai wrote:
> At Tue, 11 Nov 2014 12:34:41 -0600,
> Chris Pemberton wrote:
>> CentOS 7 x86_64
>> Asus P8Z68-V motherboard
>> Realtek ALC892
>> Gnome 3 desktop
>> nVidia GTX 770 with nVidia's driver
>>
>> With BIOS set to HD for both rear and front jacks, I experience the problems I reported here:
>>
>> https://bugs.freedesktop.org/show_bug.cgi?id=86158
>>
>> Basically, sound works, but the selected output keeps auto-magically flipping from Analog-Out to Headphones and back so fast you barely hear a click..
>>
>> Tried all sorts of snd_hda_intel module options and it didn't change.
>>
>> Finally changed BIOS to set front jacks to AC97 (left rear jacks as HD) and sound works great... but no jack sensing occurs at all...
>>
>> I can live without the jack sensing... but if anyone wants a stab at a fix, I'm game.
>>
>> I've got the HDA Analyzer downloaded and running if that helps.
>>
>> My device has id 8086:1c20
>>
>> Perhaps similar to this bug that was brought to my attention?
>>
>> https://git.kernel.org/cgit/linux/kernel/git/tiwai/sound.git/commit/sound/pci/hda?id=1565cc358585be40608b46f18f7ac431a1aae2bc
>>
>> Output of alsa-info.sh is here:
>>
>> http://www.alsa-project.org/db/?f=8cf116b0bc230524bcfa7285b2adb698078d4224
> Could you check the pin connection again? The symptom appears more like
> a hardware problem.
>
>
> Takashi
next prev parent reply other threads:[~2014-11-13 6:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-11 18:34 possible snd_hda_intel jack-sensing issue with device 8086:1c20 Chris Pemberton
2014-11-12 7:52 ` Takashi Iwai
2014-11-13 6:07 ` Chris Pemberton [this message]
2014-11-13 6:47 ` Chris Pemberton
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=54644A90.3030507@gmail.com \
--to=cjpembo@gmail.com \
--cc=alsa-devel@alsa-project.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