Kodi fails to start

[oradke]

Kodi fails to start

[oradke]

Adding
display_auto_detect=1
too config.txt did the trick. Now Kodi works!

[Joulinar]

Found something similar on Kodi forum https://forum.kodi.tv/showthread.php?tid=371581

[MichaIng]

Strange error. I never heard that Kodi requires any config file, aside of the ones it auto-generates in the user's home dir. Do you as well get this segmentation fault from the Kodi forum?

dmesg -l 0,1,2,3

And do you have a crash log as well, either in your home dir, or in its .kodi sub directory somewhere.

[oradke]

Here's the log:
kodi.log

after trying

sudo apt install pipewire pipewire-pulse
sudo apt install pipewire-audio-client-libraries
sudo apt install gstreamer1.0-pipewire libspa-0.2-bluetooth libspa-0.2-jack

the error disappeared from journalctl, but Kodi still won't start.

[MichaIng]

I had such a feeling that those two errors were unrelated. pw for PipeWire makes sense, which is the new default audio stack on RPi OS. But I think we would have seen a lot more reports if it would not also just work with ALSA.

This will be the major issue:

error <general>: CDRMUtils::OpenDrm - no drm devices found: (No such file or directory)

KMS/DRM is not enabled. This does not exist, right?

ls -l /dev/dri

This should have been enabled automatically on Kodi installation. Can you check whether the overlay was added:

grep vc4-kms-v3d /boot/config.txt

If this does not give a result, can you run this command and check again:

/boot/dietpi/func/dietpi-set_hardware rpi-opengl vc4-kms-v3d 512

And in case the overlay was now added, reboot and retry.

Did you add the TFT via dietpi-config after Kodi installation? And/or set another resolution there? All these options make use of the legacy graphics stack, while Kodi requires the new one (KMS). Also changing the resolution to one other option than the KMS one(s), will disable it. We need to switch all this to the new graphics stack anyway, now more then before since the RPi 5 compatible firmware packages removed vast parts of the legacy stack. Until then, better follow the official docs to setup the display: https://www.raspberrypi.com/documentation/accessories/display.html
In case the resolution is wrong, you can remove the two framebuffer_width/framebuffer_height settings from /boot/dietpi.txt or set them to the correct values.

[oradke]

Thanks for the reply! Let me go through all the items:

• /dev/dri does NOT exist
• the grep command returns NOTHING, so overlay way NOT added!
• command ran fine, afterwards grep found the overlay
• after reboot, screen was dark, but Kodi log had no errors
• I remember this happened after the very first install. I had actually used dietpi-config. Perhaps that threw KODI off
• dietpi.txt does not have framebuffer settings
• I edited boot.txt and the screen changed, but Kodi still crashes with
  critical <general>: CApplication::CreateGUI - unable to init windowing system
  Have attached
  kodi.log
  new log file.

[MichaIng]

Right, that is the way to enable LCD support with KMS 👍. Alternatively one could add a specific overlay in some cases, but the auto-detection usually just works.

Okay, I'll mark this as closed then. Will work on GPU stack migration for all RPis in our code.