Re: [PATCH] ALSA: hda/realtek: Add quirk for LG Gram 17ZD90R-EX79K

[Takashi Iwai <tiwai@suse.de>]

On Mon, 03 Aug 2026 09:02:10 +0200,
Takashi Iwai wrote:
> 
> On Thu, 30 Jul 2026 06:20:09 +0200,
> 빛나는황소 wrote:
> > 
> > From: Jabong Koo <safenine@gmail.com>
> > 
> > The internal speakers on the LG Gram 17ZD90R-EX79K remain silent,
> > while headphone output works normally.
> > 
> > The machine uses a Realtek ALC298 codec with PCI subsystem ID
> > 1854:048b. Existing LG Gram subsystem IDs 1854:0488, 1854:0489 and
> > 1854:048a use ALC298_FIXUP_SAMSUNG_AMP_V2_4_AMPS, but 1854:048b is
> > missing from the quirk table.
> > 
> > Add the matching quirk for subsystem ID 1854:048b.
> > 
> > Tested successfully on Ubuntu HWE kernels 6.17.0-41-generic and
> > 7.0.0-28-generic.
> > 
> > Signed-off-by: Jabong Koo <safenine@gmail.com>
> > ---
> >  sound/hda/codecs/realtek/alc269.c | 1 +
> >  1 file changed, 1 insertion(+)
> > 
> > diff --git a/sound/hda/codecs/realtek/alc269.c
> > b/sound/hda/codecs/realtek/alc269.c
> > --- a/sound/hda/codecs/realtek/alc269.c
> > +++ b/sound/hda/codecs/realtek/alc269.c
> > @@ -7752,6 +7752,7 @@ static const struct snd_pci_quirk alc269_fixup_tbl[] = {
> >  	SND_PCI_QUIRK(0x1854, 0x0488, "LG gram 16 (16Z90R)",
> > ALC298_FIXUP_SAMSUNG_AMP_V2_4_AMPS),
> >  	SND_PCI_QUIRK(0x1854, 0x0489, "LG gram 16 (16Z90R-A)",
> > ALC298_FIXUP_SAMSUNG_AMP_V2_4_AMPS),
> >  	SND_PCI_QUIRK(0x1854, 0x048a, "LG gram 17 (17ZD90R)",
> > ALC298_FIXUP_SAMSUNG_AMP_V2_4_AMPS),
> > +	SND_PCI_QUIRK(0x1854, 0x048b, "LG gram 17 (17ZD90R-EX79K)",
> > ALC298_FIXUP_SAMSUNG_AMP_V2_4_AMPS),
> >  	SND_PCI_QUIRK(0x1854, 0x05bf, "LG gram 17ZD90S",
> > ALC298_FIXUP_SAMSUNG_AMP_V2_4_AMPS),
> >  	SND_PCI_QUIRK(0x1854, 0x05c0, "LG gram 16Z90S",
> > ALC298_FIXUP_SAMSUNG_AMP_V2_4_AMPS),
> >  	SND_PCI_QUIRK(0x1854, 0x05c1, "LG gram 14Z90S",
> > ALC298_FIXUP_SAMSUNG_AMP_V2_4_AMPS),
> 
> The patch looks malformed (with wrong spaces), likely due to your
> mailer, so it can't be applied cleanly via git-am.
> Please fix your mailer setup, and resubmit the fix.

Never mind, I see that there was another fix submission by Aaron for
the very same device with the same quirk, and it was applied now.


thanks,

Takashi