[graysky]

I built the latest Kodi from git/master on Arch ARM for RPi4.  I am finding two things that I cannot explain. WhenI start my kodi.service shown below, systemd is busy/delays the start up by precisely 2.0 minutes but only the first time kodi is loaded. Subsequent stop and start calls via systemctl work fine.

The second thing I cannot explain are the following errors that are displayed briefly before as the Kodi splash screen and as well to dmesg:

Code:

vc4_hdmi fef05700.hdmi: ASoC: can't open interface fef05700.hdmi: -19
vc4_hdmi fef05700.hdmi: ASoC: can't open interface fef05700.hdmi: -19
vc4_hdmi fef05700.hdmi: ASoC: can't open interface fef05700.hdmi: -19
vc4_hdmi fef05700.hdmi: ASoC: can't open interface fef05700.hdmi: -19

I have functionality when Kodi does finally load, but I am seeking to understand more about:
1) The delay (seems like a time out as it is consistently 2.0 minutes).
2) Is the vc4_hdmi f2f05700.hdmi: ASoC: can't open interface fef05700.hdmi: -19 error related or something else I need to fix.

dmesg: https://gist.github.com/graysky2/f336f9e...f885a779a1
kodi.log: https://gist.github.com/graysky2/9e61fd5...6ac32bbdd1

kodi.service:

Code:

[Unit]
Description=Kodi standalone (GBM)
After=systemd-user-sessions.service network.target network-online.target sound.target upower.service mysqld.service
Wants=network-online.target polkit.service upower.service
[email protected]
[Service]
User=kodi
Group=kodi
SupplementaryGroups=input
PAMName=login
TTYPath=/dev/tty1
Environment=WINDOWING=gbm
ExecStart=/usr/bin/kodi-standalone
Restart=on-abort
StandardInput=tty
StandardOutput=journal
[Install]
Alias=display-manager.service

[popcornmix]

"[   20.578975] vc4_hdmi fef05700.hdmi: ASoC: can't open interface fef05700.hdmi: -19" occurs on a working LE build so isn't a problem.
I did see a explanation on a github pr/issue and I think some system debug files are created twice with the same name for hdmi0/hdmi1 provoking a harmless message.

[graysky]

Thanks for the reply.  I also asked on to the RPi forums to make sure it's not a firmware or kernel bug before opening an issue.  One of the developers independently confirmed it.  I think the systemd delay is it's own issue and unrelated to the output I see when kodi finally does launch.