No HDMI sound output from alsa in server (no KMS)

[Dave Jones]

During ISO testing of the beta Ubuntu Server 22.10 for Raspberry Pi image, on a Raspberry Pi 4B and 3B, I noted that the HDMI "sound card" no longer appears in /proc/asound/cards; only the Headphones output (from the AUX socket on the board) appears.

I checked with the current linux-raspi in the release pocket (5.19.0-1001-raspi), and the new one in proposed (5.19.0-1002-raspi), and both exhibit the same issue.

On Kinetic:

$ cat /proc/asound/cards
 0 [Headphones ]: bcm2835_headpho - bcm2835 Headphones
                      bcm2835 Headphones

On Jammy:

$ cat /proc/asound/cards
 0 [b1 ]: bcm2835_hdmi - bcm2835 HDMI 1
                      bcm2835 HDMI 1
 1 [Headphones ]: bcm2835_headpho - bcm2835 Headphones
                      bcm2835 Headphones

[Dave Jones (waveform)]

It appears the bug also affects the Raspberry Pi 3B (not 2711 specific). Notably, on both platforms adding the KMS overlay causes an HDMI sound output to appear, though a different one from that seen on jammy (without the KMS overlay):

$ cat /proc/asound/cards
 0 [Headphones ]: bcm2835_headpho - bcm2835 Headphones
                      bcm2835 Headphones
 1 [vc4hdmi ]: vc4-hdmi - vc4-hdmi
                      vc4-hdmi

[Dave Jones (waveform)]

Updated description after confirming issue on arm64.

[Ubuntu QA Website (ubuntuqa)]

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
https://iso.qa.ubuntu.com/qatracker/reports/bugs/1991254

[Juerg Haefliger (juergh)]

A DT change broke the audio driver. Working on it.

[Brian Murray (brian-murray)]

Is this sorted out now?

[Juerg Haefliger (juergh)]

Is fixed in the 1003 kernel in kinetic-proposed. Don't know why this bug wasn't spammed...

[Launchpad Janitor (janitor)]

This bug was fixed in the package linux-raspi - 5.19.0-1004.10

---------------
linux-raspi (5.19.0-1004.10) kinetic; urgency=medium

  * kinetic/linux-raspi: 5.19.0-1004.10 -proposed tracker (LP: #1993133)

  * armhf kernel compiled with gcc-12 fails to boot on pi 3/2 (LP: #1993120)
    - [Packaging] raspi: Use gcc-11 for armhf
    - [Config] raspi: updateconfigs for gcc-11 for armhf

  [ Ubuntu: 5.19.0-21.21 ]

  * kinetic/linux: 5.19.0-21.21 -proposed tracker (LP: #1992639)
  * cannot change mount namespace (LP: #1991691)
    - SAUCE: apparmor: Fix getaatr mediation causing snap failures
  * Kernel regresses openjdk on riscv64 (LP: #1992484)
    - SAUCE: Revert "riscv: mmap with PROT_WRITE but no PROT_READ is invalid"

  [ Ubuntu: 5.19.0-20.20 ]

  * kinetic/linux: 5.19.0-20.20 -proposed tracker (LP: #1992408)
  * Packaging resync (LP: #1786013)
    - debian/dkms-versions -- update from kernel-versions (main/master)
  * Kinetic kernels 5.19.0-18/19-generic won't boot on Intel 11th/12th gen
    (LP: #1991704)
    - drm/i915: fix null pointer dereference
  * rcu_sched detected stalls on CPUs/tasks (LP: #1967130)
    - [Config] Disable VMAP_STACK on riscv64
  * Disable sv57 as the userspace is not ready (LP: #1991790)
    - SAUCE: riscv: mm: Force disable sv57
  * earlyconsole prints question marks on 5.19.0-1002-generic (LP: #1988984)
    - [Config] Set CONFIG_PWM_SIFIVE=m for riscv64
  * RCU stalls (LP: #1991951)
    - [Config] Harmonize RCU_CPU_STALL_TIMEOUT
  * backport dkms fixes to build modules correctly for hwe-5.19+ kernels with
    custom compiler (LP: #1991664)
    - [Packaging] use versioned gcc-12
    - [Packaging] Update configs with versioned compiler version
  * FTBFS on kinetic (LP: #1990964)
    - SAUCE: uapi: Fixup strace compile error
  * CVE-2022-40768
    - scsi: stex: Properly zero out the passthrough command structure
  * [22.10 FEAT] zKVM: Crypto Passthrough Hotplug - kernel part (LP: #1852741)
    - s390/vfio-ap: use new AP bus interface to search for queue devices
    - s390/vfio-ap: move probe and remove callbacks to vfio_ap_ops.c
    - s390/vfio-ap: manage link between queue struct and matrix mdev
    - s390/vfio-ap: introduce shadow APCB
    - s390/vfio-ap: refresh guest's APCB by filtering AP resources assigned to
      mdev
    - s390/vfio-ap: allow assignment of unavailable AP queues to mdev device
    - s390/vfio-ap: rename matrix_dev->lock mutex to matrix_dev->mdevs_lock
    - s390/vfio-ap: introduce new mutex to control access to the KVM pointer
    - s390/vfio-ap: use proper locking order when setting/clearing KVM pointer
    - s390/vfio-ap: prepare for dynamic update of guest's APCB on assign/unassign
    - s390/vfio-ap: prepare for dynamic update of guest's APCB on queue
      probe/remove
    - s390/vfio-ap: allow hot plug/unplug of AP devices when assigned/unassigned
    - s390/vfio-ap: hot plug/unplug of AP devices when probed/removed
    - s390/vfio-ap: reset queues after adapter/domain unassignment
    - s390/vfio-ap: implement in-use callback for vfio_ap driver
    - s390/vfio-ap: sysfs attribute to display the guest's matrix
    - s390/vfio-ap: handle config changed and scan complete notification...