Bug 111492

Summary: HDMI audio is unavailable with amdgpu on R9 270
Product: DRI Reporter: Marti Raudsepp <marti>
Component: DRM/AMDgpuAssignee: Default DRI bug account <dri-devel>
Status: RESOLVED MOVED QA Contact:
Severity: not set    
Priority: not set    
Version: unspecified   
Hardware: x86-64 (AMD64)   
OS: Linux (All)   
Whiteboard:
i915 platform: i915 features:

Description Marti Raudsepp 2019-08-26 20:03:25 UTC
Video card: ASUS Radeon R9 270
Kernel: 5.2.9-arch1-1-ARCH

I recently had some issues with the "radeon" driver and discovered that the "amdgpu" driver now has support for Southern Islands (SI) GPUs using the amdgpu.si_support=1 boot flag.

Graphics stuff works great with amdgpu so far, however, all HDMI audio outputs are marked as "(unplugged) (unavailable)" in the pavuctl utility.

Someone else's screenshot with similar issue: https://i.imgur.com/67HYPG3.png
Initially this issue seemed related to bug 107835, but Alex Deucher said that's not the case.

alsa-info.sh debug dump uploaded to: http://alsa-project.org/db/?f=bd09f9bd5cdadc129852d2f4487aec9f22d9b915



There is nothing in kernel logs to indicate issues. Grepping for relevant keywords in dmesg gives this:

[    0.145413] Kernel command line: initrd=\initramfs-linux.img root=UUID=93067a3f-2c68-4e1a-9f3a-96cdc0221771 rw acpi_enforce_resources=lax iommu=pt radeon.si_support=0 amdgpu.si_support=1 amdgpu.dc=1 radeon.audio=1
...
[    3.910423] input: HDA ATI HDMI HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:03.1/0000:09:00.1/sound/card0/input4
[    3.910454] input: HDA ATI HDMI HDMI/DP,pcm=7 as /devices/pci0000:00/0000:00:03.1/0000:09:00.1/sound/card0/input5
[    3.910480] input: HDA ATI HDMI HDMI/DP,pcm=8 as /devices/pci0000:00/0000:00:03.1/0000:09:00.1/sound/card0/input6
[    3.910513] input: HDA ATI HDMI HDMI/DP,pcm=9 as /devices/pci0000:00/0000:00:03.1/0000:09:00.1/sound/card0/input7
[    3.910547] input: HDA ATI HDMI HDMI/DP,pcm=10 as /devices/pci0000:00/0000:00:03.1/0000:09:00.1/sound/card0/input8
[    3.910579] input: HDA ATI HDMI HDMI/DP,pcm=11 as /devices/pci0000:00/0000:00:03.1/0000:09:00.1/sound/card0/input9
...
[    4.110170] [drm] amdgpu kernel modesetting enabled.
[    4.110310] amdgpu 0000:09:00.0: remove_conflicting_pci_framebuffers: bar 0: 0xe0000000 -> 0xefffffff
[    4.110312] amdgpu 0000:09:00.0: remove_conflicting_pci_framebuffers: bar 2: 0xfcf00000 -> 0xfcf3ffff
[    4.110313] amdgpu 0000:09:00.0: vgaarb: deactivate vga console
[    4.110485] amdgpu 0000:09:00.0: kfd not supported on this ASIC
[    4.120150] amdgpu 0000:09:00.0: No more image in the PCI ROM
[    4.121491] amdgpu 0000:09:00.0: VRAM: 2048M 0x000000F400000000 - 0x000000F47FFFFFFF (2048M used)
[    4.121492] amdgpu 0000:09:00.0: GART: 1024M 0x000000FF00000000 - 0x000000FF3FFFFFFF
[    4.121557] [drm] amdgpu: 2048M of VRAM memory ready
[    4.121560] [drm] amdgpu: 3072M of GTT memory ready.
[    4.123745] amdgpu 0000:09:00.0: PCIE GART of 1024M enabled (table at 0x000000F400300000).
[    4.124929] [drm] amdgpu: dpm initialized
[    4.125034] [drm] AMDGPU Display Connectors
[    4.502455] fbcon: amdgpudrmfb (fb0) is primary device
[    4.779046] amdgpu 0000:09:00.0: fb0: amdgpudrmfb frame buffer device
[    5.237526] [drm] Initialized amdgpu 3.32.0 20150101 for 0000:09:00.0 on minor 0
Comment 1 Marti Raudsepp 2019-08-26 20:33:23 UTC
Oh and I'm using HDMI output for video, which works fine.
Unplugging and re-plugging the HDMI cable does not help.
Comment 2 Alex Deucher 2019-08-27 18:34:36 UTC
For display audio on SI, your best bet is to use radeon.  The SI support in amdgpu is experimental.
Comment 3 Martin Peres 2019-11-19 09:50:39 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/drm/amd/issues/895.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.