From: Kay <a3.works@gmail.com>
To: alsa-devel@alsa-project.org
Subject: Re: [BUG] ALC295 internal speaker silent on Panasonic Let's Note CF-SV8 (PCI subsys 10f7:8338)
Date: Fri, 15 May 2026 18:29:02 +0900 [thread overview]
Message-ID: <agbmDHkCiyheGiiQ@archlinux> (raw)
In-Reply-To: <afSbGRSm0KSNnoBA@archlinux>
Closing the loop on this bug report for the list archive.
The root cause turned out to lie entirely outside the ALSA driver. The
codec layer (snd_hda_codec_realtek) was correct all along; no kernel
fixup or patch is needed for this hardware. The actual issue was a
combination of (1) an older BIOS that left the ALC295 codec in a state
that could not drive the internal speaker amplifier at all, and (2) a
userspace ACP path config that unconditionally mutes the speaker mixer
control on every path activation.
(1) BIOS
-------
Panasonic shipped a BIOS update for this model (V2.00L30, dated
2025-06-19) via Windows Update. After applying it, the ALC295 codec
initializes correctly. The "Speaker Playback Switch" then behaves as a
normal Pin 0x14 Amp-Out mute bit, and toggling it on lets audio flow
through the internal speaker as expected.
For others hitting the same symptom on Panasonic Let's Note CF-SV8: a
BIOS update via Windows Update resolved the codec-side issue here, with
no kernel changes required. Older BIOS versions appear to leave the
codec in a state from which the internal speaker cannot be unmuted at
all, even with manual hda-verb writes to Pin 0x14.
(2) Persistence (PipeWire / ACP path config)
-------------------------------------------
After the BIOS fix, the speaker could be unmuted with
`amixer sset Speaker on`, but the "Speaker Playback Switch" was reset
to off on every wireplumber restart and on every boot, leaving the
speaker silent again until manually unmuted.
The cause is in the ACP path config file
/usr/share/alsa-card-profile/mixer/paths/analog-output-speaker.conf,
specifically:
[Element Speaker]
required-any = any
switch = off
volume = merge
The "switch = off" directive instructs ACP to "always set this control
to off" whenever this path is activated. This config assumes a
classical HD-Audio layout where Master is the master attenuator/mute
and Speaker is a path-selection hint that should be left off. On
ALC295, however, "Speaker" is the per-pin (Pin 0x14) Amp-Out mute bit
of the internal speaker, and Master alone does not gate it. The
unconditional "switch = off" therefore mutes the internal speaker on
every path activation.
Workaround: drop a copy of analog-output-speaker.conf into
/etc/alsa-card-profile/mixer/paths/ and change the [Element Speaker]
directive to "switch = ignore":
[Element Speaker]
required-any = any
- switch = off
+ switch = ignore
volume = merge
PipeWire's ACP picks up the /etc/ copy in preference to the one under
/usr/share/. After this change, ACP no longer touches the Speaker mixer
control on path activation, the speaker stays unmuted across
wireplumber restarts, warm reboots, and cold boots (including a full
battery-out power cycle), and no other userspace component
(alsa-restore.service, autostart scripts, custom systemd units) is
needed to keep it that way.
Thanks to the list -- lore archives of similar codec quirks were
useful while triaging this.
--
kay-ws
prev parent reply other threads:[~2026-05-15 9:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-01 12:22 [BUG] ALC295 internal speaker silent on Panasonic Let's Note CF-SV8 (PCI subsys 10f7:8338) kay-ws
2026-05-15 9:29 ` Kay [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=agbmDHkCiyheGiiQ@archlinux \
--to=a3.works@gmail.com \
--cc=alsa-devel@alsa-project.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.