-
-
Notifications
You must be signed in to change notification settings - Fork 492
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Kodi fails to start #6828
Comments
Found something similar on Kodi forum https://forum.kodi.tv/showthread.php?tid=371581 |
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 |
Here's the log: after trying
the error disappeared from journalctl, but Kodi still won't start. |
I had such a feeling that those two errors were unrelated. This will be the major issue:
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 |
Thanks for the reply! Let me go through all the items:
|
Adding |
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. |
Creating a bug report/issue
Required Information
G_DIETPI_VERSION_SUB=25
G_DIETPI_VERSION_RC=1
G_GITBRANCH='master'
G_GITOWNER='MichaIng'
Additional Information (if applicable)
yes
Steps to reproduce
Expected behaviour
Actual behaviour
Extra details
The text was updated successfully, but these errors were encountered: