public inbox for linux-sound@vger.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Theodoros Orfanidis <teoulas@gmail.com>
Cc: m.krycki@gmail.com, alsa-devel@alsa-project.org,
	linux-sound@vger.kernel.org
Subject: Re: [BUG] ALSA: hda/realtek: SSID 1458:a194 is shared by different Gigabyte ALC897 front-panel layouts
Date: Tue, 07 Apr 2026 14:28:11 +0200	[thread overview]
Message-ID: <87qzorlztw.wl-tiwai@suse.de> (raw)
In-Reply-To: <20260407120350.42282-1-teoulas@gmail.com>

On Tue, 07 Apr 2026 14:03:48 +0200,
Theodoros Orfanidis wrote:
> 
> On Mon, 06 Apr 2026, Marcin Krycki wrote:
> > [BUG] ALSA: hda/realtek: SSID 1458:a194 is shared by different
> > Gigabyte ALC897 front-panel layouts
> 
> Same issue here. After a recent kernel update from 6.19.10 to 6.19.11
> (Arch Linux), I realized my mic port had become another headphone out.
> 
> Pin 0x19 (the physical Front Mic jack) is re-tasked as a second
> headphone output, and the microphone input disappears from the
> available sources in the system.
> 
> Prior to this patch (tested on kernel 6.19.10), auto-config correctly
> identified the separate pins:
>   inputs: Rear Mic=0x18, Front Mic=0x19
>   hp_outs=1 (0x1b)
> 
> With this patch applied:
>   inputs: Mic=0x18
>   hp_outs=2 (0x1b, 0x19)
>   Front Mic (0x19) is missing from inputs.
> 
> Manually re-tasking Pin 0x19 back to'Microphone' via hdajackretask
> restores the expected behavior.
> 
> Hardware: Gigabyte B660I AORUS PRO DDR4 (rev. 1.x)
> PCI SSID: 1458:a194
> Codec: Realtek ALC897

OK, I'm going to revert the commit.  The fix patch looks dubious and
needs to be revisited.


thanks,

Takashi

  reply	other threads:[~2026-04-07 12:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAEfRphPU_ABuVFzaHhspxgp2WAqi7kKNGo4yOOt0zeVFPSj8+Q@mail.gmail.com>
2026-04-07 12:03 ` [BUG] ALSA: hda/realtek: SSID 1458:a194 is shared by different Gigabyte ALC897 front-panel layouts Theodoros Orfanidis
2026-04-07 12:28   ` Takashi Iwai [this message]
2026-04-06  9:49 Marcin Krycki

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=87qzorlztw.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=linux-sound@vger.kernel.org \
    --cc=m.krycki@gmail.com \
    --cc=teoulas@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