All of lore.kernel.org
 help / color / mirror / Atom feed
From: kay-ws <a3.works@gmail.com>
To: alsa-devel@alsa-project.org
Subject: [BUG] ALC295 internal speaker silent on Panasonic Let's Note CF-SV8 (PCI subsys 10f7:8338)
Date: Fri, 1 May 2026 21:22:49 +0900	[thread overview]
Message-ID: <afSbGRSm0KSNnoBA@archlinux> (raw)

Hi,

Internal speaker is silent on a Panasonic Let's Note CF-SV8-2
(Realtek ALC295, PCI subsystem 10f7:8338), while the headphone jack
works correctly.

Hardware confirmed healthy:
  - Internal speaker plays sound under Windows 10
  - Panasonic BIOS HW self-test reports speaker OK

Linux side:
  - Kernel 7.0.2-2-cachyos (CachyOS / Arch)
  - ALSA 1.2.15.2, PipeWire 1.6.4

The driver picks no quirk fixup for this subsys:

  ALC295: picked fixup  for PCI SSID 10f7:8338   <- empty fixup name

PCM data reaches Pin 0x14 (Audio Output 0x02 has stream=1 during
playback, same as 0x03 which feeds the working headphone), Pin-ctls
is OUT, amp is unmuted, but no audio is produced through the
internal speaker.

Tried with no effect:
  - options snd_hda_intel model=thinkpad (fixup chain runs)
  - hda-verb 0x14 SET_EAPD_BTLENABLE 0x02
  - hda-verb 0x01 SET_GPIO_MASK/DIRECTION/DATA 0x03
  - WirePlumber profile output:analog-stereo (non-duplex)

Full alsa-info.sh dump:
  http://alsa-project.org/db/?f=546e2c9fc0e2261cb6d8a7c837f8c3f54f771064

Could a fixup entry for PCI SSID 10f7:8338 be added to the alc269
quirk table? I'm happy to test patches and try Realtek coef
sequences if suggested.

Thanks,
kay-ws

             reply	other threads:[~2026-05-04 11:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-01 12:22 kay-ws [this message]
2026-05-15  9:29 ` [BUG] ALC295 internal speaker silent on Panasonic Let's Note CF-SV8 (PCI subsys 10f7:8338) Kay

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=afSbGRSm0KSNnoBA@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.