Linux Sound subsystem development
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Gilberto Ferreira <gilberto.nunes32@gmail.com>
Cc: linux-sound@vger.kernel.org
Subject: Re: No HDMI audio with Linux Kernel 7 rc1 or rc2...
Date: Mon, 02 Mar 2026 17:21:43 +0100	[thread overview]
Message-ID: <87qzq2kxrc.wl-tiwai@suse.de> (raw)
In-Reply-To: <CAOKSTBs1VNBdjRZe3M2v-nC+pLZZ0-KQtRUZUj6ACqb4Xe7LDg@mail.gmail.com>

On Mon, 02 Mar 2026 15:30:31 +0100,
Gilberto Ferreira wrote:
> 
> Hi there.
> 
> This is my first post here.
> I have compiled both RC1 and RC2 for kernel 7 and after booting with
> it, no HDMI sound at all.
> This my laptop:
> 
> Operating System: Kubuntu 26.04
> KDE Plasma Version: 6.6.1
> KDE Frameworks Version: 6.23.0
> Qt Version: 6.10.2
> Kernel Version: 6.19.5 (64-bit)
> Graphics Platform: X11
> Processors: 12 × AMD Ryzen 5 5625U with Radeon Graphics
> Memory: 64 GiB of RAM (47.0 GiB usable)
> Graphics Processor: AMD Radeon Graphics
> Manufacturer: Positivo Bahia - VAIO
> Product Name: VJFE69F11X-B0411H
> 
> With kernel 6.19, even the RC's works perfectly fine.
> This is how I compiled the kernel:
> 
> git clone from Linus github
> cd linux
> make mrproper
> cp /boot/config-$(uname -r) .config
> fakeroot make -j$(nproc) deb-pkg
> 
> 
> Hope this can be fixed soon.

Could you give a bit more details?  How it "doesn't work"?
Is the device completely gone?  Or the playback breaks and doesn't
proceed or error?  Or does it output only silence?

You can check /proc/asound/cards and aplay -l output whether you can
see the sound devices at least from both working and broken kernels.

And, if they look different, compare the kernel logs (dmesg ouput)
between them to figure out any relevant differences.

And, beware that HDMI problems are often about the graphics drivers,
not the sound drivers.


Takashi

  reply	other threads:[~2026-03-02 16:21 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 [this message]
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
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=87qzq2kxrc.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