[fedora-arm] Sound over HDMI fails in Fedora 24 Mate Spin on Odroid-Xu4

[Stewart Samuels]

Hello,

I do not seem to be able to get sound via my HDMI TV connection to the Odroid-Xu4. Pulseaudio is running however. What drivers are required for this and how do I check to see if they are a) installed; b) loaded. Lsmod shows now snd modules running but I suspect this is because HDMI is being used.

Thanks for any help.

Stewart

[Stewart Samuels]

Ok. Performing a "jounalctl -xb" reveals the following for the hdmi probe.


[***@myodroid exynos]# journalctl -xb
-- Logs begin at Thu 2016-02-11 11:28:00 EST, end at Sat 2016-08-13
22:01:01 EDT. --
Feb 11 11:28:02 myodroid systemd-journald[180]: Runtime journal
(/run/log/journal/) is 8.0M, max 98.9M, 90.9M free.
-- Subject: Disk space used by the journal
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Runtime journal (/run/log/journal/) is currently using 8.0M.
-- Maximum allowed usage is set to 98.9M.
-- Leaving at least 148.3M free (of currently available 981.0M of disk
space).
-- Enforced usage limit is thus 98.9M, of which 90.9M are still available.
--
-- The limits controlling how much disk space is used by the journal may
-- be configured with SystemMaxUse=, SystemKeepFree=, SystemMaxFileSize=,
-- RuntimeMaxUse=, RuntimeKeepFree=, RuntimeMaxFileSize= settings in
-- /etc/systemd/journald.conf. See journald.conf(5) for details.
Feb 11 11:28:02 myodroid kernel: Booting Linux on physical CPU 0x100
Feb 11 11:28:02 myodroid kernel: Linux version 4.6.5-300.fc24.armv7hl
(***@arm04-builder03.arm.fedoraproject.org) (gcc version 6.1.1
20160621 (Red Hat
Feb 11 11:28:02 myodroid kernel: CPU: ARMv7 Processor [410fc073]
revision 3 (ARMv7), cr=10c5387d
Feb 11 11:28:02 myodroid kernel: CPU: div instructions available:
patching division code
Feb 11 11:28:02 myodroid kernel: CPU: PIPT / VIPT nonaliasing data
cache, VIPT aliasing instruction cache
Feb 11 11:28:02 myodroid kernel: Machine model: Hardkernel Odroid XU4
Feb 11 11:28:02 myodroid kernel: efi: Getting EFI parameters from FDT:
Feb 11 11:28:02 myodroid kernel: efi: UEFI not found.
Feb 11 11:28:02 myodroid kernel: cma: Reserved 64 MiB at 0xba800000
Feb 11 11:28:02 myodroid kernel: Memory policy: Data cache writealloc
Feb 11 11:28:02 myodroid kernel: Samsung CPU ID: 0xe5422001
Feb 11 11:28:02 myodroid kernel: On node 0 totalpages: 514560
Feb 11 11:28:02 myodroid kernel: free_area_init_node: node 0, pgdat
c0edc900, node_mem_map eee24000
Feb 11 11:28:02 myodroid kernel: Normal zone: 1728 pages used for memmap
Feb 11 11:28:02 myodroid kernel: Normal zone: 0 pages reserved
Feb 11 11:28:02 myodroid kernel: Normal zone: 192512 pages, LIFO batch:31
Feb 11 11:28:02 myodroid kernel: HighMem zone: 322048 pages, LIFO batch:31
Feb 11 11:28:02 myodroid kernel: Running under secure firmware.
Feb 11 11:28:02 myodroid kernel: percpu: Embedded 13 pages/cpu @eed8a000
s24332 r8192 d20724 u53248
Feb 11 11:28:02 myodroid kernel: pcpu-alloc: s24332 r8192 d20724 u53248
alloc=13*4096
Feb 11 11:28:02 myodroid kernel: pcpu-alloc: [0] 0 [0] 1 [0] 2 [0] 3 [0]
4 [0] 5 [0] 6 [0] 7
Feb 11 11:28:02 myodroid kernel: Built 1 zonelists in Zone order,
mobility grouping on. Total pages: 512832
Feb 11 11:28:02 myodroid kernel: Kernel command line: ro
root=UUID=4d70d307-a61d-4cda-9535-8a8849c262c2 cma=64M LANG=en_US.UTF-8
Feb 11 11:28:02 myodroid kernel: PID hash table entries: 4096 (order: 2,
16384 bytes)
...skipping...
Feb 11 11:28:11 myodroid kernel: [drm:hdmi_probe [exynosdrm]] *ERROR*
failed to get regulators
Feb 11 11:28:11 myodroid kernel: [drm:hdmi_probe [exynosdrm]] *ERROR*
hdmi_resources_init failed
Feb 11 11:28:11 myodroid kernel: exynos-hdmi 14530000.hdmi: Failed to
get supply 'vdd': -517
Feb 11 11:28:11 myodroid kernel: [drm:hdmi_probe [exynosdrm]] *ERROR*
failed to get regulators
Feb 11 11:28:11 myodroid kernel: [drm:hdmi_probe [exynosdrm]] *ERROR*
hdmi_resources_init failed
Feb 11 11:28:11 myodroid kernel: exynos-rot 11c00000.rotator: The exynos
rotator is probed successfully
Feb 11 11:28:11*myodroid kernel: exynos-drm-gsc 13e00000.video-scaler:
failed to get system register.*
Feb 11 11:28:11 myodroid kernel: exynos-drm-gsc 13e00000.video-scaler:
drm gsc registered successfully.
Feb 11 11:28:11 *myodroid kernel: exynos-drm-gsc 13e10000.video-scaler:
failed to get system register.*
Feb 11 11:28:11 myodroid kernel: exynos-drm-gsc 13e10000.video-scaler:
drm gsc registered successfully.
Feb 11 11:28:11 myodroid kernel: exynos-drm-ipp exynos-drm-ipp: drm ipp
registered successfully.
Feb 11 11:28:11 myodroid kernel: exynos-hdmi 14530000.hdmi: Failed to
get supply 'vdd': -517
Feb 11 11:28:11 myodroid kernel: [drm:hdmi_probe [exynosdrm]] *ERROR*
failed to get regulators
Feb 11 11:28:11 myodroid kernel: [drm:hdmi_probe [exynosdrm]] *ERROR*
hdmi_resources_init failed
Feb 11 11:28:11 myodroid kernel: s5m-rtc s2mps14-rtc: rtc core:
registered s5m-rtc as rtc0
Feb 11 11:28:11 myodroid kernel: exynos-hdmi 14530000.hdmi: Failed to
get supply 'vdd': -517
Feb 11 11:28:11 myodroid kernel: [drm:hdmi_probe [exynosdrm]] *ERROR*
failed to get regulators
Feb 11 11:28:11 myodroid kernel: [drm:hdmi_probe [exynosdrm]] *ERROR*
hdmi_resources_init failed
Feb 11 11:28:11 myodroid kernel: *vdd_ldo9: ramp_delay not se*t
Feb 11 11:28:11 myodroid kernel: *vdd_ldo13: ramp_delay not set*
Feb 11 11:28:11 myodroid kernel: *vdd_ldo15: ramp_delay not set*
Feb 11 11:28:11 myodroid kernel: *vdd_sd: ramp_delay not set*
Feb 11 11:28:11 myodroid kernel: [drm] Exynos DRM: using 14450000.mixer
device for DMA mapping operations
Feb 11 11:28:11 myodroid kernel: exynos-drm exynos-drm: bound
14450000.mixer (ops mixer_component_ops [exynosdrm])
Feb 11 11:28:11 myodroid kernel: exynos-drm exynos-drm: bound
14530000.hdmi (ops hdmi_component_ops [exynosdrm])
Feb 11 11:28:11 myodroid kernel: exynos-drm exynos-drm: bound
exynos-drm-vidi (ops vidi_component_ops [exynosdrm])
Feb 11 11:28:11 myodroid kernel: [drm] Supports vblank timestamp caching
Rev 2 (21.10.2013).
Feb 11 11:28:11 myodroid kernel: [drm] No driver support for vblank
timestamp query.
Feb

[Stewart Samuels]

I have now got past the failures listed in my previous posting by using
the following "append" line in /boot/extlinux/extlinux.conf.


append rd.driver.pre="exynosdrm ehci-exynos,ohci-exynosro"
root=UUID=4d70d307-a61d-4cda- 9535-8a8849c262c2 cma=64M LANG=en_US.UTF-8


However, journalctl -xb shows the system is now failing with the
following messages:

Feb 11 11:28:02 myodroid systemd-modules-load[178]: Failed to find
module 'snd_bcm2835'
Feb 11 11:28:02 myodroid systemd[1]: Starting Setup Virtual Console...
Feb 11 11:28:02 myodroid systemd[1]: Starting dracut cmdline hook...
Feb 11 11:28:03 myodroid dracut-cmdline[189]: dracut-24 (Twenty Four)
dracut-044-20.fc24
Feb 11 11:28:03 myodroid dracut-cmdline[189]: Using kernel command line
parameters: rd.driver.pre="exynosdrm ehci-exynos,ohci-exynosro"
root=UUID=4d70d307-a
Feb 11 11:28:03 myodroid systemd[1]: Started Journal Service.
Feb 11 11:28:03 myodroid audit[1]: SERVICE_START pid=1 uid=0
auid=4294967295 ses=4294967295 subj=kernel msg='unit=systemd-journald
comm="systemd" exe="/usr/
Feb 11 11:28:03 myodroid systemd[1]: systemd-modules-load.service: Main
process exited, code=exited, status=1/FAILURE
Feb 11 11:28:03 myodroid systemd[1]: Failed to start Load Kernel Modules.
---------------------------------------------------------------------------------------------------------

So, where do I find the snd_bcm2835 module? Is there an rpm for it?
Will I have to rebuild the kernel?

Stewart

[Peter Robinson]

I have now got past the failures listed in my previous posting by using the
following "append" line in /boot/extlinux/extlinux.conf.
append rd.driver.pre="exynosdrm ehci-exynos,ohci-exynosro"
root=UUID=4d70d307-a61d-4cda- 9535-8a8849c262c2 cma=64M LANG=en_US.UTF-8
However, journalctl -xb shows the system is now failing with the following
Feb 11 11:28:02 myodroid systemd-modules-load[178]: Failed to find module
'snd_bcm2835'
Feb 11 11:28:02 myodroid systemd[1]: Starting Setup Virtual Console...
Feb 11 11:28:02 myodroid systemd[1]: Starting dracut cmdline hook...
Feb 11 11:28:03 myodroid dracut-cmdline[189]: dracut-24 (Twenty Four)
dracut-044-20.fc24
Feb 11 11:28:03 myodroid dracut-cmdline[189]: Using kernel command line
parameters: rd.driver.pre="exynosdrm ehci-exynos,ohci-exynosro"
root=UUID=4d70d307-a
Feb 11 11:28:03 myodroid systemd[1]: Started Journal Service.
Feb 11 11:28:03 myodroid audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295
ses=4294967295 subj=kernel msg='unit=systemd-journald comm="systemd"
exe="/usr/
Feb 11 11:28:03 myodroid systemd[1]: systemd-modules-load.service: Main
process exited, code=exited, status=1/FAILURE
Feb 11 11:28:03 myodroid systemd[1]: Failed to start Load Kernel Modules.
---------------------------------------------------------------------------------------------------------
So, where do I find the snd_bcm2835 module? Is there an rpm for it? Will I
have to rebuild the kernel?

Why would you want the sounds driver for the raspberry pi?

[Stewart Samuels]

Hi Peter,

I don't want the sound driver for the Raspberry PI. The "snd_bcm2835"
module is what Fedora 24 is trying to load (and fails) on my Odroid-Xu4
(as shown in my "journalctl -xb" snippet that I posted). What module
should it be loading, if any, to use sound of hdmi to my TV? I get no
sound what so ever.

Stewart

[Peter Robinson]

Post by Stewart Samuels
Hi Peter,
I don't want the sound driver for the Raspberry PI. The "snd_bcm2835"
module is what Fedora 24 is trying to load (and fails) on my Odroid-Xu4 (as
shown in my "journalctl -xb" snippet that I posted). What module should it
be loading, if any, to use sound of hdmi to my TV? I get no sound what so
ever.

TBH no idea, have you tried googling it? Looking at the device tree
there doesn't appear to be any audio bits for the XU4 as yet, there is
for the XU3 and XU3 Lite, but I'm not directly aware of the
differences between the 3 models, eg the XU4 could have a different
codec chip or something.

Peter

[Stewart Samuels]

Hello Peter,

After researching this for a bit, what I found is that the XU4 is
suppose to be 100% software compatible with the XU3. Does that suggest
you should be able to use the audio bits for the XU3 with the XU4? Are
these audio bits software or hardware?

Stewart

[Peter Robinson]

Post by Stewart Samuels
Hello Peter,
After researching this for a bit, what I found is that the XU4 is suppose to
be 100% software compatible with the XU3. Does that suggest you should be
able to use the audio bits for the XU3 with the XU4? Are these audio bits
software or hardware?

Hardware, there will be a codec chip, and probably something around
the hdmi and how it's all wired together.