-
Notifications
You must be signed in to change notification settings - Fork 44
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 freeze/crash on boot with 4k TV #912
Comments
Note that there may be issues with hdmi audio: raspberrypi/linux#4543 |
Thanks that finally someone has tested 4k resolution, I can not due to lack of hardware. I have already considered several times to switch from fkms to kms in new built images, but have not done it because of other small problems, which you also partly mentioned here. For example, because VNC doesn't work anymore. This is a long known problem, for this I used the solution of lrusak and integrated the VNC server directly in Kodi (his version is not really usable), but only in the version 20. I use meanwhile therefore also already some weeks the kms driver The animated Kodi start doesn't work either, because this still requires the old dispmanx functionality. An alternative solution with ffplay or the like is unfortunately not usable. Another solution might work, but I haven't got around to testing it yet. The black screen and the audio dropout when switching to video background (in my opinion a pretty useless function anyway) is probably due to the fact that the screen mode has to be switched, and that just takes some time |
It used to work until a few months ago on the 4k TV with fkms, then an update broke it. It may just be a problem with the Kodi config file, I'll try to reset it. Update: no change with a new Kodi profile. The video background is optional, but it's smoother with fkms because there isn't that screen mode change. |
This is probably due to the firmware, which also broke the PI:HDMI audio device at kms We'll just have to live with that (for a while?), since everything happens in the kernel (opensource) and no longer via the firmware (closedsource) as with fkms. Progress report: |
When booting Xbian with rpi4b connected to a 4k TV, Kodi crashes (the screens stays stuck on the Matrix style background).
After reading "4K Playback on rpi4" (http://forum.xbian.org/thread-4133-post-37278.html#pid37278),
I tried changing
dtoverlay=vc4-fkms-v3d,cma-384
to
dtoverlay=vc4-kms-v3d,cma-384
in /boot/config.txt
and it works.
(I also had to change the audio output to S/PDIF in Kodi to have sound since that's what's being used here for now).
A few drawbacks:
I also tried with and without the staging firmware, but it made no difference. I'll report any problem I notice.
Despite the drawbacks, I suggest using kms by default for the rpi4, unless an option can be added to xbian-config to enable it (with a notice about 4k screen compatibility).
By the way, kms is needed for a 4k TV even if we use Kodi in 1920x1080.
The text was updated successfully, but these errors were encountered: