From: Takashi Iwai <tiwai@suse.de>
To: Gilberto Ferreira <gilberto.nunes32@gmail.com>
Cc: Takashi Iwai <tiwai@suse.de>, linux-sound@vger.kernel.org
Subject: Re: No HDMI audio with Linux Kernel 7 rc1 or rc2...
Date: Mon, 09 Mar 2026 15:09:35 +0100 [thread overview]
Message-ID: <87jyvlm6w0.wl-tiwai@suse.de> (raw)
In-Reply-To: <CAOKSTBuUnS=stepHySGVYH4GbQytEQL45cLj4eV8u0KAsquF5w@mail.gmail.com>
On Mon, 09 Mar 2026 15:02:17 +0100,
Gilberto Ferreira wrote:
>
> Linux kernel 7 RC3 is out and still no HDMI sound.
>
At best, please try git bisect. Or if it can't work for you, ask your
distro people who can help.
And, I'm afraid that it's not the sound subsystem but the DRM graphics
driver that actually broke. In that case, you're reporting to a wrong
list, and further ping wouldn't help.
(And for figuring it out, you'd need the bisection, so going back to
square...)
thanks,
Takashi
> ---
>
> Gilberto Nunes Ferreira
>
>
>
>
>
> ---
>
>
> Gilberto Nunes Ferreira
> +55 (47) 99676-7530 - Whatsapp / Telegram
>
>
>
>
>
>
> Em qui., 5 de mar. de 2026 às 10:06, Takashi Iwai <tiwai@suse.de> escreveu:
> >
> > On Thu, 05 Mar 2026 13:54:45 +0100,
> > Gilberto Ferreira wrote:
> > >
> > > Hi there...
> > >
> > > I just installed ArchLinux, because I thought that perhaps
> > > Ubuntu/Debian was the culprit.
> > > So, I went ahead and installed linux-mainline from AUR.
> > > But I get this same result.
> >
> > Then please try to git bisect. That's likely the most straightforward
> > way to figure out the culprit.
> >
> >
> > thanks,
> >
> > Takashi
> >
> > >
> > >
> > > ---
> > >
> > >
> > > Gilberto Nunes Ferreira
> > > +55 (47) 99676-7530 - Whatsapp / Telegram
> > >
> > >
> > >
> > >
> > > ---
> > >
> > >
> > > Gilberto Nunes Ferreira
> > > +55 (47) 99676-7530 - Whatsapp / Telegram
> > >
> > >
> > >
> > >
> > >
> > >
> > > Em ter., 3 de mar. de 2026 às 09:17, Gilberto Ferreira
> > > <gilberto.nunes32@gmail.com> escreveu:
> > > >
> > > > Well... I really don't know what happened.
> > > > Probably my fault, as usual.
> > > > I do this:
> > > > git clone https://github.com/torvalds/linux.git
> > > > cd linux
> > > > git checkout cb9b6f9d2be6bda1b0117b147df40f982ce06888
> > > > make mrproper
> > > > cp /boot/config-$(uname -r) .config
> > > > fakeroot make -j$(nproc) deb-pkg
> > > >
> > > > But after that, the result was
> > > > linux-image-6.19.0-rc1+_6.19.0~rc1-00011-gcb9b6f9d2be6-1_amd64.deb!
> > > > I don't get it.
> > > >
> > > > git log shows me this:
> > > >
> > > > commit cb9b6f9d2be6bda1b0117b147df40f982ce06888 (HEAD)
> > > > Author: Vivian Wang <wangruikang@iscas.ac.cn>
> > > > Date: Thu Jan 29 09:56:09 2026 +0800
> > > >
> > > > ALSA: hda/intel: Make MSI address limit based on the device DMA limit
> > > >
> > > > So, basically, I give up!
> > > > When this issue gets fixed, I will try kernel 7.0 again.
> > > >
> > > > Sorry to bother.
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > ---
> > > >
> > > >
> > > > Gilberto Nunes Ferreira
> > > > +55 (47) 99676-7530 - Whatsapp / Telegram
> > > >
> > > >
> > > > Em ter., 3 de mar. de 2026 às 07:48, Takashi Iwai <tiwai@suse.de> escreveu:
> > > > >
> > > > > On Tue, 03 Mar 2026 11:27:24 +0100,
> > > > > Gilberto Ferreira wrote:
> > > > > >
> > > > > > Sorry... I am not an expert on this stuff.
> > > > > > I just like to compile the kernel...
> > > > > >
> > > > > > >> You need to *compare* between two kernel logs. You can strip the time
> > > > > > >> prefix, and check which lines appear and which disappear in the new
> > > > > > >> kernel log.
> > > > > > How can I do that?
> > > > > > Via journalctl -xe -p3? journalctl -r -b?
> > > > >
> > > > > You can run "dmesg > dmesg.log" on the running kernel. And you can
> > > > > get two outputs. You can strip the time prefix from there by some
> > > > > script for easier comparison.
> > > > >
> > > > > > >> And, have you tested the revert?
> > > > > > I don't know how to do that.
> > > > > >
> > > > > > If you can point me to some doc, it would be nice.
> > > > >
> > > > > Have you ever built a kernel by yourself? If yes, it should be just a
> > > > > git revert of the suggested commit and rebuild / retest.
> > > > > If not, which (distro) kernel are you using? Usually you can ask
> > > > > distro people to build a test kernel.
> > > > >
> > > > > In general, please be more specific about your system and
> > > > > configuration.
> > > > >
> > > > >
> > > > > Takashi
next prev parent reply other threads:[~2026-03-09 14:09 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-02 14:30 No HDMI audio with Linux Kernel 7 rc1 or rc2 Gilberto Ferreira
2026-03-02 16:21 ` Takashi Iwai
2026-03-02 16:56 ` Gilberto Ferreira
2026-03-02 17:04 ` Takashi Iwai
2026-03-02 17:20 ` Gilberto Ferreira
2026-03-02 17:37 ` Gilberto Ferreira
2026-03-02 18:28 ` Gilberto Ferreira
2026-03-03 6:35 ` Takashi Iwai
2026-03-03 10:27 ` Gilberto Ferreira
2026-03-03 10:48 ` Takashi Iwai
2026-03-03 12:17 ` Gilberto Ferreira
2026-03-05 12:54 ` Gilberto Ferreira
2026-03-05 13:06 ` Takashi Iwai
2026-03-09 14:02 ` Gilberto Ferreira
2026-03-09 14:09 ` Takashi Iwai [this message]
2026-03-09 14:14 ` Gilberto Ferreira
2026-03-09 14:15 ` Gilberto Ferreira
2026-03-09 14:24 ` Takashi Iwai
2026-03-09 14:25 ` Gilberto Ferreira
2026-03-10 12:32 ` Gilberto Ferreira
2026-03-12 13:24 ` Thorsten Leemhuis
2026-03-12 13:35 ` Gilberto Ferreira
2026-03-23 13:03 ` Gilberto Ferreira
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=87jyvlm6w0.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=gilberto.nunes32@gmail.com \
--cc=linux-sound@vger.kernel.org \
/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