From: Takashi Iwai <tiwai@suse.de>
To: Yu-Hsiang Tseng <asas1asas200@gmail.com>
Cc: linux-sound@vger.kernel.org, tiwai@suse.com, perex@perex.cz,
linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH] ALSA: hda/realtek: Fix silent speaker on Higole F9B
Date: Mon, 28 Sep 2026 13:37:57 +0200 [thread overview]
Message-ID: <87se2t61yi.wl-tiwai@suse.de> (raw)
In-Reply-To: <20260923141344.1543158-1-asas1asas200@gmail.com>
On Wed, 23 Sep 2026 16:13:44 +0200,
Yu-Hsiang Tseng wrote:
>
> The Higole F9B is an Alder Lake-N mini PC with a 7" touchscreen and an
> ALC269VC codec (subsystem ID 0x10ec111e). Its DMI strings are all
> "Default string", so the SSID is the only way to identify it.
>
> The internal speaker is silent out of the box. The generic parser
> assigns DAC 0x03 to the speaker pin 0x14 and DAC 0x02 to the headphone
> pin 0x15, but the speaker only reproduces what DAC 0x02 plays, whatever
> its connection selection says. Checked one path at a time, only the
> gain of DAC 0x02 and the mute of pin 0x14 change what comes out of the
> speaker. User space only knows the path it was told the speaker uses,
> so selecting the speaker turns the path that actually reaches it all
> the way down.
>
> Route both 0x14 and 0x15 through mixer 0x0c (DAC 0x02), which is what
> ALC290_FIXUP_MONO_SPEAKERS already does. Tested on the device: the
> speaker plays.
>
> Cc: <stable@vger.kernel.org>
> Assisted-by: LLM
> Signed-off-by: Yu-Hsiang Tseng <asas1asas200@gmail.com>
> ---
> The quirk line and this changelog were drafted with an LLM (Claude Code);
> the path-by-path analysis and the test were done by hand on the device.
Applied now. Thanks.
Takashi
prev parent reply other threads:[~2026-09-28 11:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-23 14:13 Yu-Hsiang Tseng
2026-09-28 11:37 ` Takashi Iwai [this message]
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=87se2t61yi.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=asas1asas200@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=perex@perex.cz \
--cc=stable@vger.kernel.org \
--cc=tiwai@suse.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
all inboxes | Powered by JetHome®