No HDMI audio under 5.19.0-35 & -37 (regression from -32)

Status changed to 'Confirmed' because the bug affects multiple users.

HDMI video does not work for me on this kernel. 5.19.0-31 works fine.

I'm running ubuntu DISTRIB_RELEASE=22.10 on and HP Fury 16 G9 laptop with 12th Gen Intel(R) Core(TM) i9-12950HX.

It also causes the fan to come on. Logging in is very slugging. 5.19.0.31 is very responsive and does not force the fan on under casual use.

Looking through the growing list of duplicates, everyone has an AMD GPU so this is almost certainly an issue in that driver. The list of cards affected so far:

* RX570 (mine)
* RX6700 XT (from LP: #2009275)
* RX580 (from LP: #2009276)
* RX6600 (from LP: #2009542)

I'm happy to post any additional logs / traces that would help debug this and/or test patched kernels (worth looking at the duplicates for additional logs too).

Hello.

Same here, with a readeon HD7700 and Ubuntu 22.04.2

With kernel -35 there is no hdmi audio output, but after -32 restore everything is fine.

Hi Timo, this also affects jammy -- should I add that to the targeting, or is that to be handled separately?

@Matthias, Dave, Andy, Would you please help me to bisect it?
i would appreciate a lot.

here's test kernel.
https://drive.google.com/drive/folders/1Hyejgp0r_Dq2gsovXqxB2BNTE8uPEd6g?usp=share_link

* please disable the SecureBoot in bios and run these to install.
  # sudo dpkg -i *.deb

@kobako the 5.19.9000-34-generic kernel provided in comment 10 is "bad" (no HDMI audio present, same dmesg lines as seen in the -35 kernel)

@Dave, thanks
here's another test kernel for bisect
https://drive.google.com/drive/folders/1yRA9fYQg98yEAIeyRg6cQYGboroDEHgb?usp=share_link

@kobako the 5.19.9001-34-generic kernel provided in comment 12 is also "bad" (same symptoms, same dmesg lines as seen in the -35 kernel)

@Dave, appreciate,
I would like to check from first patch in amd driver first. thanks
https://drive.google.com/drive/folders/1bWeHxyBYhukZLic8CmRowDfr0zSjGs-N?usp=share_link

@kobako the 5.19.9002-34-generic kernel in comment 14 is also "bad"

@Dave, thanks your effort.
here's another kernel, reverted this patch.
Would you please also dump the lspci -nvvvv, thanks
~~~
fdcc4c22b7ab) ALSA: hda/hdmi - enable runtime pm for more AMD display audio
~~~
https://drive.google.com/drive/folders/1Ky7Xw6Yt8HVU0YLDbFRJX0ROuJ9O0iVU?usp=share_link

@kobako the 5.15.9003-68-generic kernel in comment 16 is "good"; HDMI audio detected and working happily. I'm attaching the requested lspci output.

Errr, let me try that again from root so it's actually got the caps output!

This bug affects also Ubuntu 22.04.2 LTS
# uname -a
Linux xxxx 5.19.0-35-generic #36~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Fri Feb 17 15:17:25 UTC 2 x86_64 x86_64 x86_64 GNU/Linux

@bpl indeed -- I asked Timo if the targeting should be adjusted in comment 9 as I wasn't sure if the kernel team wanted to track this separately over in the hwe package, but given this bug was moved from that package this one I may as well just add jammy to the affected set.

R9 290 here, HDMI audio output disappeared after updating to 5.19.0-35, loaded 5.19.0-32 and it's working again.

This does not affect the jammy kernel (5.15), so adding that is misleading. When it's fixed in kinetic, hwe-5.19 in jammy will get the fix automatically.

Still experiencing this with 5.19.0-37-generic. Any ETA on when the fix will make it in?

@Timo ah I see, sorry for the noise!

+202303131023,
1. latest vanilla kernel,
https://drive.google.com/drive/folders/1fyu43ZWyzL51YHgwRVJeP9K4AnNEPEUv?usp=share_link

2. latest vanilla reverted the suspicious
https://drive.google.com/drive/folders/1YHW7qHXqNQNHZfYHDLLFdPL1-wPezDJ4?usp=share_link
~~~
Revert "ALSA: hda/hdmi - enable runtime pm for more AMD display audio"
This reverts commit fdcc4c22b7ab20e90b97f8bc6225d876b72b8f16.
~~~

3. 5.19.0-35 reverted the suspicious
https://drive.google.com/drive/folders/1MOVbujtJmRpCyqA4nZ7hSToTScscbJ7-?usp=share_link

@koba I've tried each of the kernels in comment 25 and I'm afraid it rather refutes the theory that fdcc4c22b is the culprit:

The latest vanilla kernel (#1) is "good"; HDMI audio works happily. That suggests (although not conclusively) that fdcc4c22b isn't the culprit as it presumably includes that commit.

The latest vanilla kernel with fdcc4c22b reverted (#2) is also "good"; HDMI audio works, although I did note dmesg had an awful lot of preempt errors reported in it (which did not appear with the vanilla kernel above).

Finally, just to put the nail in the coffin of fdcc4c22b being the faulty commit, the 5.19.0-35 kernel with fdcc4c22b reverted (#3) is "bad"; exhibits the original failure with HDMI audio being unavailable.

To go further wiyh the last remarks, fdcc4c22b commit (https://github.com/torvalds/linux/commit/fdcc4c22b7ab20e90b97f8bc6225d876b72b8f16 is just the addition of a new device hw caps (PCI_DEVICE(0x1002, 0xab30). I doubt it can be the culprit.

I don't understand how the bisect did identify it as the source of the problem. Except if there was some kind of error when patching the ubuntu kernel package to mimic it.

By the way I am also impacted with:
> Baffin HDMI/DP Audio [Radeon RX 550 640SP / RX 560/560X] [1002:AAE0]
(lshw -numeric -class multimedia)
so device 0x1002,0xaae0

Hello, I tried all the kernels in this post and I experience the same behaviour as Dave :

5.19.0-31 OK
5.19.0-32 OK
5.19.0-35 bad

5.19.9000-34 (tk) bad
5.19.9001-34 (tk1) bad
5.19.9002-34 (tk2) bad
5.15.9003-68 (tk3) OK

tk_generic_202303131019 = latest vanilla OK
tk_genRevertfdcc4c22b7ab_202303131037 OK
tk_20230313113 (5.19.0-35 rev fdcc4c22b) bad

I am experiencing this problem with DisplayPort audio output on a RX580.
I am attaching the output of "sudo lspci -nvvvvl" as spci-sf.out

This is also a problem for me on jammy with -35 / AMD Radeon pro wx 3200 series. When I rolled back to -32 it worked.

@duxeu To fill in a bit of background here, the AMD folks were emailed in the background and are of the same opinion.

Personally, I'm not sure the bisect *did* identify that as the commit, but unfortunately bisection isn't an entirely straight-forward process when dealing with packages that have a ton of Ubuntu-specific patches on top of them (as the kernel naturally does).

@kobako Are there any further test kernels to try?

In the meantime I'll stick the currently affected list of cards at the top so new people coming to the bug can easily check against the list (though I have a feeling, looking at the list, it could be summarised as "pretty much all AMD GPUs").

@dave, I will have a amdgpu and am going to reproduce on my side

Also RX560, only to complete the list.

I have an AMD/ATI R9 270 and I am also affected. Attached is my full output from "lspci -vvvv"

$ uname -a
Linux dell-xps-8700 5.19.0-35-generic #36~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Fri Feb 17 15:17:25 UTC 2 x86_64 x86_64 x86_64 GNU/Linux

I'm also affected with an iGPU on my amd cpu.

I attached my 'lspci -vvvv'. I'm currently using the working '-32' kernel.

I would like to report that with -32 kernel sound works fine and -35 does not in a more complex configuration. AMD RX 560 is bypassed into a virtual machine using IOMMU. A display port connection is used.

I'm attaching 'sudo lspci -nvvv' for -32 and -35 kernels invoked from the virtual machine.

This is the difference between them:

diff --git a/lspci.32.iommu b/lspci.35.iommu
index e7f7560..058c719 100644
--- a/lspci.32.iommu
+++ b/lspci.35.iommu
@@ -34,9 +34,9 @@
        Capabilities: [48] Vendor Specific Information: Len=08 <?>
        Capabilities: [50] Power Management version 3
                Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
- Status: D3 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME-
+ Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME-
        Capabilities: [a0] MSI: Enable+ Count=1/1 Maskable- 64bit+
- Address: 00000000fee09000 Data: 0024
+ Address: 0000000000000000 Data: 0000
        Kernel driver in use: snd_hda_intel
        Kernel modules: snd_hda_intel

+202303220231
@Dave and affected guys,
test kernel is based on 5.19.0-37.
I could get the hdmi/audio card against wx3200
~~~
01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Lexa XT [Radeon PRO WX 3200] (rev 10) (prog-if 00 [VGA controller])
 Subsystem: Dell Lexa XT [Radeon PRO WX 3200]
---
Linux u-Vostro-3888 5.19.9000-37-generic #38~22.04.1 SMP PREEMPT_DYNAMIC Tue Mar 21 18:06:56 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
 0 [PCH ]: HDA-Intel - HDA Intel PCH
                      HDA Intel PCH at 0xe2320000 irq 137
 1 [HDMI ]: HDA-Intel - HDA ATI HDMI
                      HDA ATI HDMI at 0xe2260000 irq 134
~~~
would you please help to verify this test kernel?thanks
https://drive.google.com/drive/folders/1B9PHrnKgaaM5qkfyS8Cyj40cRIIxcUnw?usp=share_link

the caused commit I found is
~~~
21f5c9a0ed2d - ALSA: memalloc: Don't fall back for SG-buffer with IOMMU
~~~

Applied the fixes patches,
~~~
9d8e536d36e7) ALSA: memalloc: Try dma_alloc_noncontiguous() at first
dd164fbfdc20) ALSA: memalloc: Drop special handling of GFP for CONTINUOUS allocation
a5ed0c547d50) ALSA: vx: Drop superfluous GFP setup
63bfc84672bb) ALSA: pdaudiocf: Drop superfluous GFP setup
97557ec97a24) ASoC: Intel: sst: Switch to standard device pages
~~~

uname -r 5.19.9000-37-generic, RX560
refresh rate set to 30Hz, it works (default setting after first boot).
Further test has shown that the volume is significantly lower, compared with "...32".

But if I set the refresh rate to 60HZ, it seems the speech will also speed up, not understandable anymore.
lspci output attached.

@Richard,
Thanks for feedback.
I can't bootup with -32 on my machine due to nvme issue,
so does the audio behave normally against -32 on your side (speech
wouldn't speed up)?

Checked against 6.2-generic, the speed up issue still persists.

@Koba,
Two issues with 37 on my system :
Set refresh rate to 60 Hz, audio will be like chirps
Set refresh rate to 30 Hz, audio will be OK, but the volume will be significantly lower (TV former volume value set to 10-12 (e.g.: youtube), now the TV must be set to 50.).
I did check the volume setting = 100% of Ubuntu.

@Richard,

How about against -32?
Do you also observe these two issues with -32

@Koba,
with 32 :
refresh rate 30, 60Hz, audio did work with "normal" volume settings.

But I remember me, that the first 22.04 Kernel, last year, had a similar issue with the 60Hz settings on my system, audio didn`t work (only 30Hz audio did work).

If you know the link of the first Kernel of 22.04 (April 2022), I would install it again on my system, and would give you more detailed results of the former issue.

@Koba,
I am sorry,
Kernel 37 and 30Hz works perfectly (audio volume OK).

@Richard, thanks for confirming.
So the remaining issue is the audio speed up when refresh rate is changed from 30 to 60

@Korba,
currently I do not have the Kernel 32 on my system, to be sure that 60Hz did also work, perhaps it would help to install the first 22.04 Kernel, the second and 32.
But to find there : https://kernel.ubuntu.com/~kernel-ppa/mainline/
the right kernel it would be a problem for me.
Therefore if you know, the respective links, please add in your comment.

@Richard,
here's hwe-5.19.0-32, please have a try.
Ref. https://drive.google.com/drive/folders/1LMj-LGy1FPkfkki063LgpIrXVVO94vfa?usp=share_link

I tried on my side and boot-up successfully.
switched from 30 to 60hz, observed the audio speed up issue too.

Against 5.19-18, also observed the audio speed up issue.
~~~
Linux u-Vostro-3888 5.19.0-18-generic #18~22.04.2 SMP PREEMPT_DYNAMIC Wed Mar 22 04:45:19 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
 0 [PCH ]: HDA-Intel - HDA Intel PCH
                      HDA Intel PCH at 0xe2320000 irq 137
 1 [HDMI ]: HDA-Intel - HDA ATI HDMI
                      HDA ATI HDMI at 0xe2260000 irq 134
~~~

I would like to create another one bug to track the issue "audio speed up".

@Korba,
thank you for the link.
I agree, with hwe-5.19.0-32 and 60Hz, I have also the audio speed up issue.

I must confess, now I am a bit confused. But I was "sure" that after the first 22.04 Kernel, one of the following Kernels had not this "speed up issue".

Thank you also for fixing the bug.

@Koba I can confirm the 5.19.9000-37-generic kernel from comment 36 fixes the issue for me as well, congratulations!

I agree the 60Hz audio issue ought to be a separate report, but until that appears a quick side note to this one: my refresh rate is 60Hz and I have no issues with my audio but I wonder if that's also related to resolution. Specifically I'm on an old 1080p monitor so the lowest refresh rate I can drop to is 50Hz (and the highest ~72Hz), and neither seems to have any particularly noticeable effect on the audio output. I wonder if those having audio issues are running at a higher resolution, presumably 4K?

@Dave Jones, Koba,
I can confirm the following (RX560) :
5.19.9000-37-generic, Resolution 3840x2180, refresh rate 60Hz, audio speed up issue
5.19.9000-37-generic, Resolution 1920x1080, refresh rate 60Hz, no audio speed up issue
5.19.9000-37-generic, Resolution 3840x2180, refresh rate 30Hz, no audio speed up issue

5.19.0-21-generic, Resolution 3840x2180, refresh rate 60Hz, audio speed up issue
5.19.0-21-generic, Resolution 1920x1080, refresh rate 60Hz, no audio speed up issue
5.19.0-21-generic, Resolution 3840x2180, refresh rate 30Hz, no audio speed up issue

5.15.0-67-generic, Resolution 3840x2180, refresh rate max 30Hz, to set 60Hz is not possible
5.19.0-67-generic, Resolution 1920x1080, refresh rate 60Hz, no audio speed up issue
5.19.0-67-generic, Resolution 3840x2180, refresh rate 30HZ, no audio speed up issue

With 5.19.9000-37-generic my HDMI sound is back!

With 5.19.9000-37-generic, the audio is back on my RX580 DisplayPort too.

No audio problem with 60Hz refresh rate, but my screen resolution is 2560*1440. The audio speedup issue should be a separate bug report, anyway.

SRUed for Kinetic,
https://lists.ubuntu.com/archives/kernel-team/2023-March/138043.html

@Richard, would you please help to open another bug for tracking the audio speed up issue? thanks

@Koba,
yes of course I can do. I did this duplicated Bug report :
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009815

I can do the bug report, with the attached files as given in 20009815

I will refer to this "bug comment", done by you.
I would give examples also written in comment 48.
I would boot the modified Kernel 37.

@Korba,
added bug report : https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2012830

@Richard, thanks

No audio.

$ lspci -vvvv
00:1f.3 Audio device: Intel Corporation 100 Series/C230 Series Chipset Family HD Audio Controller (rev 31)
        Subsystem: ASUSTeK Computer Inc. 100 Series/C230 Series Chipset Family HD Audio Controller
        Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
        Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
        Latency: 32, Cache Line Size: 64 bytes
        Interrupt: pin A routed to IRQ 140
        Region 0: Memory at f7420000 (64-bit, non-prefetchable) [size=16K]
        Region 4: Memory at f7400000 (64-bit, non-prefetchable) [size=64K]
        Capabilities: <access denied>
        Kernel driver in use: snd_hda_intel
        Kernel modules: snd_hda_intel

01:00.0 Audio device: Creative Labs Sound Core3D [Sound Blaster Recon3D / Z-Series] (rev 01)
        Subsystem: Creative Labs SB1570 SB Audigy Fx
        Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
        Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort+ >SERR- <PERR- INTx-
        Latency: 0, Cache Line Size: 64 bytes
        Interrupt: pin A routed to IRQ 16
        Region 0: Memory at f7304000 (64-bit, non-prefetchable) [size=16K]
        Region 2: Memory at f7300000 (64-bit, non-prefetchable) [size=16K]
        Capabilities: <access denied>
        Kernel driver in use: snd_hda_intel
        Kernel modules: snd_hda_intel

$ uname -a
Linux 5.19.0-38-generic #39~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Fri Mar 17 21:16:15 UTC 2 x86_64 x86_64 x86_64 GNU/Linux

@Ivanto, would you please try the test kernel from #45?

@koba

kernel 5.19.0-32: works
subsequent: no

@Ivanto,
thanks

I had previously rolled back my kernel and was fine for a while, after first noticing this on March 6. Another kernel update rolled out (I'm now on 5.19.0-38) and it's broken again.

Ryzen 7 3700x + Radeon 5700 XT with Ubuntu 22.04.

I also have that bug. KDE Neon, Kernel 5.19.0-38-generic. And the last time I tried rolling back on KDE Neon, I had to reinstall OS.

I have RX 590 btw.

Like everyone else, I've had this for a while...

AMD Radeon™ RX 6600 XT

but it seems
5.19.0-32
isn't available

As a workaround until the fix lands (and is subsequently back-ported to the jammy HWE kernel), Koba's test-kernel in comment 36 works nicely. However, please note that the test kernel is not signed and will require that you disable secure boot to try it (if it's enabled on your machine), which may or may not fit your circumstances. If you require secure boot to be enabled I'm afraid you'll need to wait a bit longer.

If you don't require secure boot, then:

* disable secure boot
* grab all files from the link in comment 36 to a clean directory
* sudo dpkg -i *.deb (from that directory)
* (you likely don't actually need *all* of the packages, but rather than sorting out which you do / don't need it's easier to simply install the lot)
* sudo reboot

@Aaron, take a look, comment 36, bug fixed.
And to install via "sudo dpkg -i *.deb"
Automatically update must be switched of, refer to comment 60.

Still same problem with kernel 5.19.0.40--generic like with kernel 5.19.0.38
only with 5.19.0-32-generic is working properly hdmi sound with Radeon X570.

Micro-Star International Co., Ltd. MS-7B79
Radeon RX 570 Series
Ubuntu 22.04.2 LTS

@Siggitron, i checked 5.19-40 is released on March 31 so the next version may have the solution.

@koba you mean that in 5.19-49 this issue is resolved? It's a really annoying bug which is present well through few kernel updates already.

@Nolt, sorry, it's typo. (i mean 5.19-40)

@SiggiTron can confirm, I also still have the same bug. 5.19.0-40 on KDE Neon with RX590 and still no audio. It really sucks at this point - more than a month with shitty audio from 11 years old motherboard.

The "problem" is inside of kernel-modules. Probably there is some conflict between the snd modules (snd-hda-intel?) and hardware. This is a historical problem of all linux distributions that has been repeating cyclically for many years.

I'm having the same problem with a Toshiba laptop using an A8-4500 APU (HD 7640G integrated graphics). Still booting 5.19.0-32 so my HDMI audio works. Like others have said, 5.19.0-40 (Ubuntu 22.04) didn't fix it. Hopefully the next one will have the fix!

This bug is awaiting verification that the linux/5.19.0-41.42 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-kinetic' to 'verification-done-kinetic'. If the problem still exists, change the tag 'verification-needed-kinetic' to 'verification-failed-kinetic'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

Hi Guys, would you please enable proposed and install the target kernel(5.19.0-41.42) to verify? thanks a lot

Hello!

Same for me, kernel 5.19.0-40 no audio
Ubuntu Jammy 22.04 LTS

Enable proposed
There is no kernel 5.19.0-41.42

Same issue on RX 470

lspci -vvvv
01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] (rev cf) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Radeon RX 470
 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
 Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
 Latency: 0, Cache Line Size: 64 bytes
 Interrupt: pin A routed to IRQ 36
 Region 0: Memory at e0000000 (64-bit, prefetchable) [size=256M]
 Region 2: Memory at f0000000 (64-bit, prefetchable) [size=2M]
 Region 4: I/O ports at e000 [size=256]
 Region 5: Memory at f7e00000 (32-bit, non-prefetchable) [size=256K]
 Expansion ROM at 000c0000 [disabled] [size=128K]
 Capabilities: <access denied>
 Kernel driver in use: amdgpu
 Kernel modules: amdgpu

00:1b.0 Audio device: Intel Corporation 9 Series Chipset Family HD Audio Controller
 Subsystem: Micro-Star International Co., Ltd. [MSI] 9 Series Chipset Family HD Audio Controller
 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
 Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
 Latency: 0, Cache Line Size: 64 bytes
 Interrupt: pin A routed to IRQ 44
 Region 0: Memory at f7f10000 (64-bit, non-prefetchable) [size=16K]
 Capabilities: <access denied>
 Kernel driver in use: snd_hda_intel
 Kernel modules: snd_hda_intel

Linux rafal-MS-7917 5.19.0-40-generic #41~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Fri Mar 31 16:00:14 UTC 2 x86_64 x86_64 x86_64 GNU/Linux

I've tried both Displayport and HDMI. No luck.

@Ubuntu Kernel Bot, I can not find any logic in your statement : "If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed." (Beneath, a bug can be solved or not, but to close a bug, what is this ?)

And also 8 duplicated bug reports will be closed ?

After closing the bug reports, which strategy you have, to solve the bug ? Do you expect that Ubuntu user shall write again a bug-report with the given Issue ?

I agree with Ivanto (comment 75):

"Ubuntu Jammy 22.04 LTS
Enable proposed
There is no kernel 5.19.0-41.42"

Yea I also confirm, no Kernel 5.19.0-41.42 in proposed...

@Ubuntu Kernel Bot, bug solved by Korba, Kernel 5.19.9000-37-generic, confirmed by :
#37, #47, 49#, #60 and also german user can agree :

please refer to : https://forum.ubuntuusers.de/topic/kein-sound-ueber-hdmi-8/, comment :
12. April 2023 14:11

Since 2023-03-21, I use the named kernel, I did stop all Canonical updates to behave my system.

And Ubuntu Kernel Bot has decided to remove the bug fix, if no additional user confirm the bug is fixed ??????????????????????????????????

I wait for the next kernel update, with the fixed issue by Korba !!!!!!!!!!!

I enabled proposed archive and installed "linux-image-5.19.0-42-generic" package. My system failed to boot. Looks like there was some error starting X server. Attaching part of the boot log.

Falled back to the older kernel "linux-image-5.19.0-31-generic" and I was able to boot and get my audio to work over HDMI.

@Richard, don't worry about the comment from bot. the fix wouldn't be pull out.
if bot closes the issue, i will open it again until the fix is landed on your hands.

I didn't also find 5.19-42 on jammy and think it's landed on kinetic first.
finding the machine and will install kinetic to verify.
please wait a moment. thanks

Verified on kinetic with 5.19.0-42-generic, the issue is fixed.

With kernel 5.19.0-40-generic: No HDMI audio output device
$ cat /proc/asound/cards
 0 [PCH ]: HDA-Intel - HDA Intel PCH
                      HDA Intel PCH at 0x200ffe310000 irq 77

With kernel 5.19.0-42-generic: Sound output device shows "HDMI/DisplayPort3 - Ellesmere H"
$ cat /proc/asound/cards
 0 [PCH ]: HDA-Intel - HDA Intel PCH
                      HDA Intel PCH at 0x200ffe310000 irq 77
 1 [HDMI ]: HDA-Intel - HDA ATI HDMI
                      HDA ATI HDMI at 0x9e840000 irq 78

Kernel: 5.19.0-42-generic
Graphic: RX 580

So, when will it roll for Jammy?

For those using the lowlatency kernel, the last kernel that works with HDMI audio is "5.19.0-1017-lowlatency".

Come on! When will it roll out for Jammy? I have been waiting for this fix for months now. F Ubuntu just can't work without breaking the most annoying things.

Problem still exists for me after updating to

Linux dell-xps-8700 5.19.0-41-generic #42~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Tue Apr 18 17:40:00 UTC 2 x86_64 x86_64 x86_64 GNU/Linux

(Ubuntu 22.04.2 LTS)

Yes... problem still exists with 5.19.0-41. Known fix is in 5.19.0-42, which has been landed in non-LTS. Sharing sentiment about landing it in 22.04.x as that's the *current long term support version*. Crucial when.

It is obvious, Ubuntu is not a friend of logic any more (@Korba, nothing against you).
Therefore, I did search for alternatives, and I have found it.
Try it : https://spirallinux.github.io/
There you will find pre configured Debian-Desktops (I prefer Gnome, e.g pre installed.: Synaptic, Firefox, Thunderbird, LibreOffice ...).
And it is faster (minimum twice) then Ubuntu (what else, without snap).
Neither problems with HDMI audio, nor with UHD resolution.
Nice to meet you, Ubuntu, but it is time to go, bye bye.

But I am using KDE Neon and I have to still rely on f Ubuntu, not f up.

Btw, 5.19.0-41 is also broken for me.

@Richard, as my understanding, because there's a release cycle, it wouldn't be so quick to arrive the users. Im very sorry and please wait more days.

@Wiktor, after discussing, the fix is landed on 5.19-42 if youre using jammy, please wait more time for the target kernel arrived. thanks.

This bug is awaiting verification that the linux-nvidia-5.19/5.19.0-1010.10 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

@Wiktor, Richard, i saw the kernel(5.19-42) hsa been in the proposed queue.
Would you please enable the proposed and help to verify it? thanks

~~~
$ sudo apt install linux-image-5.19.0-
 linux-image-5.19.0-37-generic linux-image-5.19.0-30-generic linux-image-5.19.0-42-generic
~~~

@Korba, I have to repeat me, I did work for Avionic, Automotive Industry, but if someone would voice this statement :
"If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed."
The caller would be dropped !

I'm getting increasingly frustrated by this bug. I've been patiently monitoring this bug since it began, with no audio on my media and games server and having to learn how to revert to previous kernels (which was actually fun) just to get audio.

I am a developer myself and understand the problems with point release distro's. But for something as crucial as having sound over HDMI, I find it crazy that so many users are waiting for nearly 2 months on 22.04 LTS now (almost a month after the fix was released to mainline).

I'm getting very close to formatting the entire hard drive and replacing Ubuntu with a rolling release arch distro.

sudo apt install --install-recommends linux-generic-hwe-22.04 linux-headers-generic-hwe-22.04 linux-image-generic-hwe-22.04 linux-firmware

5.19.0-41-generic #42~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC - no hdmi sound - (regural update)

5.19.0-42-generic #43~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC - hdmi sound works! - (kernel from proposed update)

For me, it's really f, on my "Jammy" (KDE Neon).

5.19.0-42 - no boot

And because of really stupid decision to, by default hide Grub and disable os prober, it basically broke my system. (For whatever reason shortcut for grub is also not working.) I had to unplug SATA drive, boot from live, replug the drive, mount with bind, chroot, change the grub setting, update-grub, and reboot with the grub boot menu, and guess what 5.19.0-42 still unbootable. Systemd gets stuck in random moments.

I also tried 5.19.0-42 recovery and it might have worked, but I am not sure, because it refused to work with my normal keyboard and only accepted my custom keyboard that has only arrows, ESC, and enter. That was enough to get me out of the recovery menu but not through the login screen. It's f anyway.

Thx @koba for trying, but again no HDMI audio for me. At least you are someone who wants to fix it, thx.

------------------------------------------------------
Now rant about Ubuntu.

I am getting very frustrated. Whenever my GPU kicks in my onboard audio sound like 1000 daemons eating the souls of innocent in the abyss. Ubuntu, wth? I get that bugs happen, but this has been fixed a month ago and this kind of situation is what makes Linux shit in the eyes of newbies. Breaking HDMI audio would be unacceptable on Windows or MAC.

"And because of the really stupid decision to, by default hide Grub and disable os prober, it basically broke my system."

I had the same problem when I tried to unroll and back then I just reinstalled OS, because that was faster. Now I used that OS for months and I didn't want to set it up again.

Ok, so I think I can at least unroll now back to 5.19.0-32.

Edit: Damnit, 5.19.0-32 breaks the same way as -42. This must be some configuration issue. I am not gonna debug this further.

Wiktor, if you're not able to boot with -42, then make an issue for that, but it doesn't mean HDMI audio doesn't work under that version. The verification-done-jammy tag has been added as of comment #95.

Matt, but the problem is not that I can't boot with - 42. I can't boot with ANYTHING except for the latest one from the normal queue, so the bug is not fixed because it didn't roll out.

An issue with your own system *not booting across multiple kernel versions* is a completely separate issue from "the bug", which is a working system but broken HDMI audio. Nolt already verified -42 for jammy above which means that it does run for them and there's audio.

Curious why status still says "Invalid", though.

After upgrading to kernel 5.19.0-42 hdmi sound work. A (very) little issue: in Preference Panel-Audio-Output, not work the audio "test"!
Processor: AMD® Ryzen 5 3600 6-core processor × 12
Graphic: AMD® Radeon rx 580 series
OS Name: Ubuntu 22.04.2 LTS 64-bit
GNOME version: 42.5
Graphic System: Wayland

Matt, yes I agree with you, but it didn't roll out yet, did it? So fix IS verified but it's not fixed. I wrote what I wrote because Koba asked me to help with verification. I tried but I can't and I am still mad at f Ubuntu because I still doesn't have audio.

@Wiktor,
Because the target kernel was landed on jammy,it would fix the issue.
Jammy have a rolling 5.19 kernel channel and you could update it.
As I known, the fix was landed on kinetic first after some progresses,it
would arrive jammy too.
I understand it's not a quick process but you will get it on jammy.
Can't boot issue, please file another bug,thanks

My problems remain After upgrading to pre-proposed kernel 5.19.0-42 : Youtube , mouse, key input still often paused for some time( 10 seconds or more).
Youtube, there are 30 seconds buffer, still paused for more than 10 seconds very often.
Mouse might disappear for more than 10 seconds very often.

Good news are that 2 warnings (hdaudio hdaudioC1D0: no AFG or MFG node found , snd_hda_intel 0000:01:00.1: no codecs initializedd) disappeared after upgrade to 5.19.0.42.

When -42 start up, 4 warnings still appeared:
[1.043489]blacklist: Problem blacklisting hash (-13)
[1.043489]blacklist: Problem blacklisting hash (-13)
[1.043489]blacklist: Problem blacklisting hash (-13)
[1.043489]blacklist: Problem blacklisting hash (-13)

hdaudio hdaudioC1D0: no AFG or MFG node found ( 5.15.0-70, 5.19.0-40, 5.19.0-41 has this warning)
snd_hda_intel 0000:01:00.1: no codecs initializedd ( 5.15.0-70, 5.19.0-40, 5.19.0-41 has this warning)

Version below 5.15.0-70 works fine and without any warning.

I had the same problems (Youtube , mouse, key input frozing )with 5.19.0.32 as well,

[1.043489]blacklist: Problem blacklisting hash (-13)
[1.043489]blacklist: Problem blacklisting hash (-13)
[1.043489]blacklist: Problem blacklisting hash (-13)
[1.043489]blacklist: Problem blacklisting hash (-13)

but without the following warinings:
hdaudio hdaudioC1D0: no AFG or MFG node found （5.19.0.32 does not have this warning)
snd_hda_intel 0000:01:00.1: no codecs initialized （5.19.0.32 does not have this warning)

@Yubo,
Would you please file another bug and upload the dmesg, lspci and cpuinfo

FYI I got the -42 update today via Software Update on one machine, so I assume it rolled out, but not another running the same exact setup (22.04.2). Not just waiting to be notified at interval, but actually running it to check.

Edit: Further, the machine that did get it, I later caved and updated to 22.10 as a means to get to 23.04 because it wasn't offering a direct upgrade path, which took it back to -41 under Kinetic. >:/ FFS.

i had enabled "Pre-released updates (jammy-proposed)"
from Software & Updates - Developer Options,
and the option for HDMI sound appeared again, the HDMI sound works fine.
On AMD RX-590 and
Kernel : Linux 5.19.0-42-generic (x86_64)
Version : #43~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Fri Apr 21 16:51:08 UTC 2
Thanks for the fix

I installed on a new secondary partition, next to Ubuntu 22.04 LTS, also Ubuntu 22.10.

Audio, updated to kernel 5.19.0-42-generic, on Creative Z-Series card is now detected again

:~$ sudo lshw -c multimedia
  *-multimedia
        description: Audio device
        product: Sound Core3D [Sound Blaster Recon3D / Z-Series]
        Vendor: Creative Labs

Enable proposed (from Ubuntu 22.04 LTS Jammy) it works properly.

Thanks for the correction.

Bit of an odd one here in that I can now select HDMI output again, but not actually getting anything coming through.

This was working a long time ago before this issue, was broken by the kernel bug, and now still doesn't work despite the HDMI option being available again.

Any tips or advice?

@ianp999,
With 5.19-32, does it work well?

@koba

Sorry, I did not try with that version. Based on comments above, I switched the config of software updater to use pre-released updates and ended up with

5.19.0-42-generic #43~22.04.1-Ubuntu

This gave me the option to select HDMI audio in my sound settings again (it was previously missing).

I can see that there is audio "flowing" (for want of a better word) because when I play sound, for example a youtube video, then I can see the meters registering the peaks and troughs.

However, I don't hear any sound either through monitor speakers or through a DAC connected to an optical output, which previously worked in an older kernel version.

It's probably something specific to me and something I've done in the process of trying to resolve the issue when I first encountered it, but given that all of the config looks good, I'm out of ideas.

Could you please switch back to 32 and check if you could hear the music?
Thanks

To the above, I use PulseEffects and PulseAdio Volume Control to manage my audio signal flow, and know that there are many factors between in/out. Some may have been changed or reset with updates in regard to blocklist, enablement, etc. I will assume you're familiar with all this unless saying otherwise. Backing koba.

Are there any plans to migrate ubuntu to pipewire and wireplumber by default for audio?

ivanto: It looks that PipeWire has indeed replaced PulseAudio in 22.10+, though as far as I can tell this here is a kernel issue specific to AMD cards per OP. Appreciate any info on how this affects things.

@koba - I am not sure how to downgrade. I know that the kernel you are asking about is not in my /boot folder so I could not load it from the grub menu, however, I'm not sure where to get it from.

Sometimes removing ~/.pulse can solve a lot of issues with audio. The pulse tends to break occasionally. Also, flatpak version of PulseEffects is way more stable if you use that.

@Iain Potter, refer to comment #45 and the description to install comment #64.

Did -42 come out on Jammy?

@Wiktor,
it still in Jammy-proposed queue, would you like to enable proposed?

@koba, ok, thx, but as I wrote above: I can't boot any kernel other than the released one and I don't have the time to debug this.

So, it *hasn't* rolled? Curious how one of my 22.04.2 setups got -42 (comment #106) when neither have proposed enabled.

After new installation of 22.04.02 and automatically update , got -41, installed after all 5.19.9000-37-generic (see above, bug fixed version)
Yesterday : sudo apt update, sudo apt upgrade, didn`t got -42, proposed disabled.

@Matt, it can be an additional bug on your system, that the proposed enabled/disabled check-box does not work properly, but I don`t know how to verify the status of proposed via command line (perhaps an environment entry ?).

@Richard, the machine in question is very clean as it's a seldom used entertainment setup, has never had proposed turned on, and I don't remember seeing anything else experimental in the list like I do when I turn it on now. Just a curiosity anyway, not a concern.

This bug was fixed in the package linux - 5.19.0-42.43

---------------
linux (5.19.0-42.43) kinetic; urgency=medium

  * kinetic/linux: 5.19.0-42.43 -proposed tracker (LP: #2016503)

  * selftest: fib_tests: Always cleanup before exit (LP: #2015956)
    - selftest: fib_tests: Always cleanup before exit

  * Debian autoreconstruct Fix restoration of execute permissions (LP: #2015498)
    - [Debian] autoreconstruct - fix restoration of execute permissions

  * Kinetic update: upstream stable patchset 2023-04-10 (LP: #2015812)
    - drm/etnaviv: don't truncate physical page address
    - wifi: rtl8xxxu: gen2: Turn on the rate control
    - drm/edid: Fix minimum bpc supported with DSC1.2 for HDMI sink
    - clk: mxl: Switch from direct readl/writel based IO to regmap based IO
    - clk: mxl: Remove redundant spinlocks
    - clk: mxl: Add option to override gate clks
    - clk: mxl: Fix a clk entry by adding relevant flags
    - powerpc: dts: t208x: Mark MAC1 and MAC2 as 10G
    - clk: mxl: syscon_node_to_regmap() returns error pointers
    - random: always mix cycle counter in add_latent_entropy()
    - KVM: x86: Fail emulation during EMULTYPE_SKIP on any exception
    - KVM: SVM: Skip WRMSR fastpath on VM-Exit if next RIP isn't valid
    - can: kvaser_usb: hydra: help gcc-13 to figure out cmd_len
    - powerpc: dts: t208x: Disable 10G on MAC1 and MAC2
    - powerpc/vmlinux.lds: Ensure STRICT_ALIGN_SIZE is at least page aligned
    - powerpc/64s/radix: Fix RWX mapping with relocated kernel
    - uaccess: Add speculation barrier to copy_from_user()
    - wifi: mwifiex: Add missing compatible string for SD8787
    - audit: update the mailing list in MAINTAINERS
    - ext4: Fix function prototype mismatch for ext4_feat_ktype
    - Revert "net/sched: taprio: make qdisc_leaf() see the per-netdev-queue pfifo
      child qdiscs"
    - bpf: add missing header file include
    - wifi: ath11k: fix warning in dma_free_coherent() of memory chunks while
      recovery
    - sched/psi: Stop relying on timer_pending() for poll_work rescheduling
    - docs: perf: Fix PMU instance name of hisi-pcie-pmu
    - randstruct: disable Clang 15 support
    - ionic: refactor use of ionic_rx_fill()
    - Fix XFRM-I support for nested ESP tunnels
    - arm64: dts: rockchip: drop unused LED mode property from rk3328-roc-cc
    - ARM: dts: rockchip: add power-domains property to dp node on rk3288
    - HID: elecom: add support for TrackBall 056E:011C
    - ACPI: NFIT: fix a potential deadlock during NFIT teardown
    - btrfs: send: limit number of clones and allocated memory size
    - ASoC: rt715-sdca: fix clock stop prepare timeout issue
    - IB/hfi1: Assign npages earlier
    - neigh: make sure used and confirmed times are valid
    - HID: core: Fix deadloop in hid_apply_multiplier.
    - x86/cpu: Add Lunar Lake M
    - bpf: bpf_fib_lookup should not return neigh in NUD_FAILED state
    - net: Remove WARN_ON_ONCE(sk->sk_forward_alloc) from sk_stream_kill_queues().
    - vc_screen: don't clobber return value in vcs_read
    - scripts/tags.sh: fix incompatibility with PCRE2
    - usb: dwc3: pci: add support for the Intel Meteor Lake-M
    - USB: serial: option: add suppo...

This bug is awaiting verification that the linux-gcp/5.19.0-1024.26 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-kinetic' to 'verification-done-kinetic'. If the problem still exists, change the tag 'verification-needed-kinetic' to 'verification-failed-kinetic'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

The bot is going wild again and -0.42 still didn't roll out for Jammy. Wtf? This bug has existed for almost 3 months and the fix was committed almost a month ago, yet it's still broken on the "stable" release.

I hope a worst case scenario will be present, nobody did verify linux-gcp/5.19.0-1024.26 kernel and the working bug fix will be removed, all dependent bug-reports will be closed.

What then ? Another flood of bug-reports ? Again the same bug fix, and again user have to test a proposed version : "If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed." ?

I think, Ubuntu Kernel bot has to reflect its software verification procedure, especially the way to test a bug fix with unstable SW (e.g.: #96 "5.19.0-42 - no boot").

@Richard: Yeah #96 was wiktor again, and he's stated he can't boot *lots* of versions everyone else can. Something's got to be up with his setup.

Would someone with authority please add verification-done-kinetic back to this a *third time* so we can get -42 and have audio? Why is the bot even talking about -1024 in this thread? And why does jammy still say invalid?

Post #108 ??

@Matt, my setup is a pretty clean install of KDE Neon, so I think I am not the only one affected by this issue while not having the ability to boot different kernels than mainstream. I don't have time to fix this, so all I have left is to bother Ubuntu to push the fix.

bug report 2009032 reflects 5.19.0-35
bug report 2009275 reflects 5.19.0-35
bug report 2009276 reflects 5.19.0-35
bug report 2009287 reflects 5.19.0-35
bug report 2009542 reflects 5.19.0-35
bug report 2009542 reflects 5.19.0-35
bug report 2009815 reflects 5.19.0-35
bug report 2011334 reflects 5.19.0-35
bug report 2012141 reflects 5.19.0-35
Ubuntu Kernel Bot reflects :
This bug is awaiting verification that the linux/5.19.0-41.42 kernel ... (5.19.0-35)
This bug is awaiting verification that the linux-nvidia-5.19/5.19.0-1010.10 kernel ...
This bug is awaiting verification that the linux-gcp/5.19.0-1024.26 kernel ...

Ubuntu Kernel Bot, how many verification threads we have to expect ?

@Ubuntu Kernel bot :
"ISO 9001:2015 specifies requirements for a quality management system when an organization:

a) needs to demonstrate its ability to consistently provide products and services that meet customer and applicable statutory and regulatory requirements, and

b) aims to enhance customer satisfaction through the effective application of the system, including processes for improvement of the system and the assurance of conformity to customer and applicable statutory and regulatory requirements.

All the requirements of ISO 9001:2015 are generic and are intended to be applicable to any organization, regardless of its type or size, or the products and services it provides."

@Ubuntu Kernel bot, take a look.

Wow, you are really pissed off about that bot. I just want my audio to finally work after months of Ubuntu being stupid. I haven't used my GPU for anything for the last few months.

This bug is awaiting verification that the linux-allwinner/5.19.0-1012.12 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-kinetic' to 'verification-done-kinetic'. If the problem still exists, change the tag 'verification-needed-kinetic' to 'verification-failed-kinetic'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

@Koba, does 5.19.0-1012.12 even include the fix?

I think the fix must be applied on "allwinner" kernel, 5.29-1012

I just got the kernel update this morning:

ryan@dell-xps-8700 [~]$ uname -a
Linux dell-xps-8700 5.19.0-42-generic #43~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Fri Apr 21 16:51:08 UTC 2 x86_64 x86_64 x86_64 GNU/Linux

I now have HDMI audio working again. A great big Thank You to all the developers and testers who worked toward getting this fix in. Wish it would have been resolved sooner, but I realize it's free software, so I take what i can get :)

I've just run the software updater, downloaded the latest kernel updates etc and after a restart, HDMI is now back and fully functional again.

Happy days are here again :)

Thank you to all concerned, very much appreciated.

Big huggies,

M

@Koba, I also confirm via update, upgrade I got -42, and it works as expected.
I must confess, I was a bit afraid, that the audio speed up issue I will get again with -42, but there is no bug. Only if I start with Kinetic installation, the audio speed up issue will be present.
Thank you.

I also confirm. -42 rolled out and it's working. Thx @Koba and everyone else involved.

It feels like fucking Xmas again. All demons in my audio output are gone.

@Koba, from my side of view, https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2012830
does not depend on the kernel.

-42 works fine on my machine.
Thank you.

@Richard, that's important information, thanks.
it may be caused other packages and may be caused by pulseaudio/pipewire(im not familiar with audio pieces)

Got the update but the new kernel wasn't showing up in grub. This fixed it: https://elementaryos.stackexchange.com/questions/28013/new-kernel-boot-option-not-showing-up-in-grub

Finally I can hear again! :)

@Koba, please refer to bug report https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2012830, its still assigned to you.

This bug is awaiting verification that the linux-aws/5.19.0-1027.28 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-kinetic' to 'verification-done-kinetic'. If the problem still exists, change the tag 'verification-needed-kinetic' to 'verification-failed-kinetic'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

KDEneon provided 5.19.0-42 this morning and the audio devices reappeared. HOWEVER, system startup sound and Accessibility notifications (like Lock Key toggle sound) do not produce audio.

Rebooting back to the 5.15.0 series restored normal audio feedback.

@oshunluvr, please check whether its the same issue as described here :
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2012830.
The described issue does not depend on the kernel. "Audio speed up, it sounds like chirps"

Updated to 5.19.0-43, still no sound. Reverting to -38 works, -40, -41, -42 and -43 all have no sound through HDMI.
Also, from my end:
- HDMI device is showing in GUI sound settings for both -38 and -43.
- "lspci" prints the same result.
- "cat /proc/asound/cards" prints the same for both -38 and -43 (no HDMI devices, but for -38 sound works)
- "pacmd list-cards" prints the same thing for both -38 and -43
- Connecting to an LG TV and using 4K 120Hz if that helps (tried to lower the resolution and refresh rate, same result, -38 has sound but -43 doesn't)

Additional information, obviously there is something wrong. SW will be modified without test purpose, UHD + AMD GPU is not verifiable by Canonical. But why the modification of the SW without possibilities to verify the modification ???
Please confirm to ISO9001 !

@zzq4343, are you using jammy or kinetic?

This bug is awaiting verification that the linux-azure/5.19.0-1028.31 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-kinetic' to 'verification-done-kinetic'. If the problem still exists, change the tag 'verification-needed-kinetic' to 'verification-failed-kinetic'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

I'm coming back to this topic just to add what worked for me.

I had to disable Wayland in order to get audio up and running through HDMI again, following the instructions at

https://linuxconfig.org/how-to-enable-disable-wayland-on-ubuntu-22-04-desktop

I'm not sure why this helped, but at the moment I'm just happy that I have HDMI audio back!

Hope this helps someone else.

@ivanto, trying 5.15.0-83 now

ah, actually I was fiddling around with kernel installers and ended up with 6.2.0-33-generic
now I have to figure out how to put 22.04 back on the regular kernels.

@Joseph,
please try
#5.15
sudo apt install linux-image-generic
#6.2
sudo apt install linux-image-generic-hwe-22.04

joseph@joseph-desktop:~$ sudo apt install linux-image-generic

linux-image-generic est déjà la version la plus récente (5.15.0.84.81).
0 mis à jour, 0 nouvellement installés, 0 à enlever et 0 non mis à jour.

joseph@joseph-desktop:~$ uname -a
Linux joseph-desktop 6.2.0-33-generic #33~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Thu Sep 7 10:33:52 UTC 2 x86_64 x86_64 x86_64 GNU/Linux

I uninstalled linux-image-generic-hwe-22.04 but I'm still stuck on 6.2.0-33-generic, I'll try again

Ok I managed to get back onto 5.15.x,
still no sound options available other than "Sortie fictive" (Fake output). - my OS is in French language.

5.15.0-84-generic #93-Ubuntu SMP Tue Sep 5 17:16:10 UTC 2023

DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=22.04
DISTRIB_CODENAME=jammy
DISTRIB_DESCRIPTION="Ubuntu 22.04.3 LTS"

12:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Navi 21 HDMI Audio [Radeon RX 6800/6800 XT / 6900 XT]
 Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Navi 21 HDMI Audio [Radeon RX 6800/6800 XT / 6900 XT]
 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
 Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
 Latency: 0, Cache Line Size: 64 bytes
 Interrupt: pin B routed to IRQ 85
 IOMMU group: 12
 Region 0: Memory at fcb20000 (32-bit, non-prefetchable) [size=16K]
 Capabilities: <access denied>
 Kernel driver in use: snd_hda_intel
 Kernel modules: snd_hda_intel

30:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Renoir Radeon High Definition Audio Controller
 Subsystem: Micro-Star International Co., Ltd. [MSI] Renoir Radeon High Definition Audio Controller
 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
 Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
 Latency: 0, Cache Line Size: 64 bytes
 Interrupt: pin B routed to IRQ 87
 IOMMU group: 16
 Region 0: Memory at fc900000 (32-bit, non-prefetchable) [size=16K]
 Capabilities: <access denied>
 Kernel driver in use: snd_hda_intel
 Kernel modules: snd_hda_intel

Meanwhile, I've tried 3rd party made in china asmedia asm1083 pcix soundcard, it crashes the system after 5 seconds of playing sound. as soon as sound started, crash. Removed the soundcard, no more crashing. This happened with 6.2 kernel, I tried many kernels.

Now I'm on 5.15.0-84-generic (assembled this new computer for my daughter) and with the Rx series video cards (I have 3 of them, 6500xt, 6700xt, 6800xt, no sound when used with the MSI b550 chipset motherboard.

On an older AM3 motherboard that my son has there is sound but I'm not sure if it's the AC97 chipset or the hdmi doing the sound on that computer which is working, haven't checked that.

This MSI B550 running AMD Ryzen 5500 has no sound.

I've ordered a sound blaster audigy card now, hopefully better luck than the knockoff card that claimed to be linux ready.

so I tried a 6500xt radeon, 6700xt, 6800xt, they all didn't like the asmedia asm1083 pcix soundcard. I think the soundcard drivers for the asmedia pcix card I tested out are bad or the card it'self is defective, kernel failure and reboot after 5 seconds of sound.

I purchased and installed this card because the MSI B550 chipset motherboard with any of the video cards I tried has no sound.

I noticed some people reporting better luck with some kernels above. the 5.15.0-84-generic kernel I just tested made no difference in my situation.

Disabling/reenabling Wayland didn't help for my setup. I have seen other reports elsewhere about issues with sound for those using motherboards containing the B550 chipset. The success reported above was encouraging. Knock on wood the soundblaster audigy pcix card I ordered will arrive soon and I'll test that with this chipset.