lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHk-=wjj9DvOZtmTkoLtyfHmy5mNKy6q_96d9=4FUEDXre=cww@mail.gmail.com>
Date: Tue, 29 Jul 2025 21:21:20 -0700
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: Takashi Iwai <tiwai@...e.de>
Cc: Mark Brown <broonie@...nel.org>, Liam Girdwood <lgirdwood@...il.com>, 
	Linux Sound Mailing List <linux-sound@...r.kernel.org>, 
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [GIT PULL] sound updates for 6.17-rc1

On Fri, 25 Jul 2025 at 06:44, Takashi Iwai <tiwai@...e.de> wrote:
>
> This includes lots of file shuffling due to HD-audio code
> reorganization and many trivial changes, but otherwise there shouldn't
> be much surprise from the functionality POV.

Hmm. I suspect I have been bitten by this on my laptop. I no longer have sound.

I also suspect that it's purely because "make oldconfig" doesn't work,
and probably turned off my old Intel HDA settings. Or something.

Renaming config parameters is *bad*. I've harped on the Kconfig phase
of the kernel build probably being our nastiest point, and a real pain
point to people getting involved with development simply because
building your own kernel can be so daunting with hundreds of fairly
esoteric questions.

And it looks like this pull has basically made it all worse, by making
previous answers to those esoteric questions null and void.

Now, it could be something else - like a real actual bug in the code -
but it does smell a bit like just silly Kconfig noise.

My laptop seems to think I have headphones attached, and there is no
sound. I think it's some generic HDA setup (the kernel messages do say
"autoconfig for Generic").

This is my bog-standard Intel laptop from many years ago (Dell xps13).
I am seeing snd_hda_intel and hda_codec_hdmi, but it *used* to pick
out ALC3271 and apparently that just magically went away

I think that's realtek, but when I enable it, I get this mess of
"which realtek", which I have no idea because the ALC3271 that the
kernel used to print out is not mentioned.

This was _singularly_ unhelpful. If the answer is "just enable
everything because you can't know which codec you have", then why have
the question in the first place?

This whole "ask people questions that they cannot know the answer to"
is a disease. And then the questions then randomly change, that's
*worse*.

             Linus

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ