From: Kailang <kailang@realtek.com>
To: Evgeny Kapun <abacabadabacaba@gmail.com>, Takashi Iwai <tiwai@suse.de>
Cc: Linux Sound Mailing List <linux-sound@vger.kernel.org>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
Linux Regressions Mailing List <regressions@lists.linux.dev>,
Linux Stable Mailing List <stable@vger.kernel.org>
Subject: RE: [REGRESSION] Distorted sound on Acer Aspire A115-31 laptop
Date: Tue, 24 Dec 2024 02:54:45 +0000 [thread overview]
Message-ID: <58300a2a06e34f3e89bf7a097b3cd4ca@realtek.com> (raw)
In-Reply-To: <fc506097-9d04-442c-9efd-c9e7ce0f3ace@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 871 bytes --]
Please test attach patch.
> -----Original Message-----
> From: Evgeny Kapun <abacabadabacaba@gmail.com>
> Sent: Monday, December 23, 2024 9:29 PM
> To: Takashi Iwai <tiwai@suse.de>
> Cc: Linux Sound Mailing List <linux-sound@vger.kernel.org>; Kailang
> <kailang@realtek.com>; Linux Kernel Mailing List
> <linux-kernel@vger.kernel.org>; Linux Regressions Mailing List
> <regressions@lists.linux.dev>; Linux Stable Mailing List
> <stable@vger.kernel.org>
> Subject: Re: [REGRESSION] Distorted sound on Acer Aspire A115-31 laptop
>
>
> External mail.
>
>
>
> >> Or do you need alsa-info with a new kernel, but with the offending
> >> commit reverted?
> > Yes, that'll be the best for eliminating other possible artifacts.
>
> Here are two alsa-info outputs for the same kernel version, except that one has
> the problematic commit reverted.
[-- Attachment #2: 0000-acer-a115.patch --]
[-- Type: application/octet-stream, Size: 904 bytes --]
diff --git a/sound/pci/hda/patch_realtek.c b/sound/pci/hda/patch_realtek.c
index 61ba5dc35b8b..2934799b6e07 100644
--- a/sound/pci/hda/patch_realtek.c
+++ b/sound/pci/hda/patch_realtek.c
@@ -10158,6 +10158,7 @@ static const struct hda_quirk alc269_fixup_tbl[] = {
SND_PCI_QUIRK(0x1025, 0x1308, "Acer Aspire Z24-890", ALC286_FIXUP_ACER_AIO_HEADSET_MIC),
SND_PCI_QUIRK(0x1025, 0x132a, "Acer TravelMate B114-21", ALC233_FIXUP_ACER_HEADSET_MIC),
SND_PCI_QUIRK(0x1025, 0x1330, "Acer TravelMate X514-51T", ALC255_FIXUP_ACER_HEADSET_MIC),
+ SND_PCI_QUIRK(0x1025, 0x1360, "Acer Aspire A115", ALC255_FIXUP_ACER_MIC_NO_PRESENCE),
SND_PCI_QUIRK(0x1025, 0x141f, "Acer Spin SP513-54N", ALC255_FIXUP_ACER_MIC_NO_PRESENCE),
SND_PCI_QUIRK(0x1025, 0x142b, "Acer Swift SF314-42", ALC255_FIXUP_ACER_MIC_NO_PRESENCE),
SND_PCI_QUIRK(0x1025, 0x1430, "Acer TravelMate B311R-31", ALC256_FIXUP_ACER_MIC_NO_PRESENCE),
next prev parent reply other threads:[~2024-12-24 2:54 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-15 13:06 [REGRESSION] Distorted sound on Acer Aspire A115-31 laptop Evgeny Kapun
2024-12-16 2:07 ` Kailang
2024-12-18 20:33 ` Evgeny Kapun
2024-12-19 2:05 ` Kailang
2024-12-22 7:26 ` Evgeny Kapun
2024-12-19 3:19 ` Kailang
2024-12-16 9:35 ` Kailang
2024-12-19 16:38 ` Takashi Iwai
2024-12-22 7:37 ` Evgeny Kapun
2024-12-22 8:27 ` Takashi Iwai
2024-12-23 13:29 ` Evgeny Kapun
2024-12-24 2:54 ` Kailang [this message]
2025-01-11 15:00 ` Evgeny Kapun
2025-01-16 14:26 ` Takashi Iwai
2025-01-17 7:48 ` Kailang
2025-01-17 10:06 ` Takashi Iwai
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=58300a2a06e34f3e89bf7a097b3cd4ca@realtek.com \
--to=kailang@realtek.com \
--cc=abacabadabacaba@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=regressions@lists.linux.dev \
--cc=stable@vger.kernel.org \
--cc=tiwai@suse.de \
/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