Kodi 19 no sound over hdmi using fkms

Open
#4,634 24 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
c, linux

Research direction

Start with the config.txt overlays and the Kodi Settings > System > Audio > Audio output device path, comparing linux-raspberrypi4 5.10.63-18 with 5.10.73-3 under the reported RPi4 setup. Investigate why HDMI is no longer enumerated with fkms, then verify that HDMI becomes selectable and audio works with the HDMI extractor and DVI monitor.

Written by the indexing model from the issue text.

Description

Describe the bug
With the latest linux-raspberrypi kernel on RPi4 aarch64 and kodi-rpi I cannot select hdmi as audio output device anymore.

To reproduce
With config.txt as follows:
dtoverlay=vc4-fkms-v3d,cma-512
dtoverlay=rpivid-v4l2
dtoverlay=
dtparam=audio=on
From kodi, go to Settings > System > Audio > Audio output device.

Expected behaviour
hdmi selectable as an audio output device.

Actual behaviour
there's only headphone option.

System

  • RPi4
  • Arch ARM (aarch64)
  • linux-firmware 20210919.d526e04-1
  • linux-raspberrypi4 5.10.73-3

Additional context
Since kms heavily depends on the monitor's hdmi capabilties and I'm using an hdmi audio extractor in combination with a DVI monitor I have to use fkms. This worked fine until linux-raspberrypi4 5.10.63-18. After upgrading a few days ago hmdi sound was not available anymore. When I downgrade the current linux-raspberrypi4 5.10.73-2 kernel to linux-raspberrypi4 5.10.63-18 I have sound over hdmi back again. See also https://archlinuxarm.org/forum/viewtopic.php?f=65&t=15598 for more details.

Dominant language
C
Stars
13.2k
Forks
5.5k
Avg merge
2d 21h
Merged PRs (30d)
21

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from raspberrypi/linux

All issues in raspberrypi/linux

Similar issues

More C issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.