From: Benjamin Pryor <programmer2514@gmail.com>
To: Andrew Udvare <audvare@gmail.com>, Takashi Iwai <tiwai@suse.com>,
Jaroslav Kysela <perex@perex.cz>
Cc: linux-sound@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ALSA: hda/realtek: Fix speaker dropouts on MSI GE66 Raider 11UE
Date: Sat, 24 Oct 2026 04:26:37 -0400 [thread overview]
Message-ID: <2bcdce5d-aa6c-4789-ab50-68dad16127b1@gmail.com> (raw)
In-Reply-To: <20260909193104.26508-1-audvare@gmail.com>
> Add a fixup that programs the amplifier's initialisation sequence at codec
> init, which turns silence detection off.
This fixup should apply to device ID 1462:1305 as well, since it uses
the exact same coefficients as 1462:12fb and suffers from the same
silence detection cutoffs.
See: https://github.com/thesofproject/sof/issues/10475#issuecomment-6380540623
Best,
Ben Pryor
---
diff -u alc269-old.c alc269.c
--- alc269-old.c 2026-10-24 04:14:40.174188675 -0400
+++ alc269.c 2026-10-24 04:14:28.725047392 -0400
@@ -7593,6 +7593,7 @@
SND_PCI_QUIRK(0x1458, 0x900e, "Gigabyte G5 KF5 (2023)", ALC2XX_FIXUP_HEADSET_MIC),
SND_PCI_QUIRK(0x1458, 0xfa53, "Gigabyte BXBT-2807", ALC283_FIXUP_HEADSET_MIC),
SND_PCI_QUIRK(0x1462, 0x12fb, "MSI GE66 Raider 11UE", ALC298_FIXUP_MSI_GE66_ALC1316_AMP),
+ SND_PCI_QUIRK(0x1462, 0x1305, "MSI GE76 Raider 11UG", ALC298_FIXUP_MSI_GE66_ALC1316_AMP),
SND_PCI_QUIRK(0x1462, 0xb120, "MSI Cubi MS-B120", ALC283_FIXUP_HEADSET_MIC),
SND_PCI_QUIRK(0x1462, 0xb171, "Cubi N 8GL (MS-B171)", ALC283_FIXUP_HEADSET_MIC),
SND_PCI_QUIRK(0x152d, 0x1082, "Quanta NL3", ALC269_FIXUP_LIFEBOOK),
---
next prev parent reply other threads:[~2026-10-24 8:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-09 19:31 Andrew Udvare
2026-09-10 15:55 ` Takashi Iwai
2026-10-24 8:26 ` Benjamin Pryor [this message]
2026-10-24 8:35 ` Takashi Iwai
2026-10-24 8:58 ` Benjamin Pryor
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=2bcdce5d-aa6c-4789-ab50-68dad16127b1@gmail.com \
--to=programmer2514@gmail.com \
--cc=audvare@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=perex@perex.cz \
--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®