Linux Sound subsystem development
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Paul Menzel <pmenzel@molgen.mpg.de>
Cc: Takashi Iwai <tiwai@suse.de>, Jaroslav Kysela <perex@perex.cz>,
	Takashi Iwai <tiwai@suse.com>,
	linux-sound@vger.kernel.org, regressions@lists.linux.dev
Subject: Re: Quiet crackling noise at boot and after stopping music
Date: Wed, 06 Aug 2025 10:46:24 +0200	[thread overview]
Message-ID: <87sei4rg67.wl-tiwai@suse.de> (raw)
In-Reply-To: <d542d223-fc6e-4be7-b581-8a390ce2f6be@molgen.mpg.de>

On Wed, 06 Aug 2025 10:34:57 +0200,
Paul Menzel wrote:
> 
> Dear Takashi,
> 
> 
> Thank you so much for your instant reply with the solution.
> 
> 
> Am 06.08.25 um 10:20 schrieb Takashi Iwai:
> > On Wed, 06 Aug 2025 10:15:08 +0200, Paul Menzel wrote:
> 
> >> I believe the Realtek refactoring caused a regression on my Intel Kaby
> >> Lake laptop Dell XPS 13 9360. There is quiet crackling noise during
> >> boot, when GDM is started, and also after playing music is
> >> stopped. It’s reproducible with 6.16.0-04055-g14bed9bc81ba, that
> >> contains the sound subsystem pull request.
> >> 
> >> 177bf8620cf4 Merge tag 'sound-6.17-rc1' of
> >> git://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound
> >> 
> >> I uploaded the run of alsa-info [1]. I try to verify with plain 6.16 later.
> > 
> > It's likely because of the missing CONFIG_SND_HDA_CODEC_* selections.
> > Please set CONFIG_SND_HDA_CODEC_ALC269=m and
> 
> Indeed, I didn’t select this.
> 
> > CONFIG_SND_HDA_CODEC_HDMI_INTEL=m if not done yet.
> 
> I had selected this.
> 
> > Those were already set to default=y in the later PR for avoiding such
> > a pitfall.
> 
> I remember I tried to check which to select, and I ran `alsa-info` to
> find the codecs, but only found:
> 
>     Codec: Realtek ALC3246
> 
> As this didn’t match to any of the offerings, I didn’t select
> it. May I suggest to extend the Kconfig help texts with notes how to
> determine the correct module?

There are quite lots of different codec names, so we can't put all
them, unfortunately...

> Also, would the driver be able to detect, if no codec modules are
> selected and log a warning?

It still "works" with the generic HD-audio codec, as you already
noticed.


Takashi

  reply	other threads:[~2025-08-06  8:46 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-06  8:15 Quiet crackling noise at boot and after stopping music Paul Menzel
2025-08-06  8:20 ` Takashi Iwai
2025-08-06  8:34   ` Paul Menzel
2025-08-06  8:46     ` Takashi Iwai [this message]
2025-08-06 13:57       ` Paul Menzel
2025-08-06 14:42         ` Takashi Iwai
2025-08-06 16:12           ` Paul Menzel
2025-08-06 18:58             ` Takashi Iwai
2025-08-06 17:00           ` Hans de Goede
2025-08-06 18:58             ` 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=87sei4rg67.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=linux-sound@vger.kernel.org \
    --cc=perex@perex.cz \
    --cc=pmenzel@molgen.mpg.de \
    --cc=regressions@lists.linux.dev \
    --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