-
Notifications
You must be signed in to change notification settings - Fork 5.1k
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
Kernel 5.10 Kodi has no screen output at rpi4b #4147
Comments
Can you post link to ~/.kodi/temp/kodi.log (e.g. on pastebin type site). Also dmesg output. |
dmsg is from after downgrade to 5.4. The logs probably too, not sure. |
Logs are only useful if they show the issue (i.e. on 5.10 kernel). |
I agree, but that is all I find, 'cause I turned back my system today to verify that the error came with 5.10. |
I can confirm problems too with kodi playback of some TV streams with vc4-fkms-v3d. Downgrade back to 5.4.83 solves the problem. I run kodi standalone as service:
stopping the service takes long time. Starting again and trying to switch channels leads to distorted graphics |
I recorded a short sample of "safe" source channel and a sample of "problem" source channel.
A try to play "problem" sample causes kodi hang (with the fkms driver an the 5.10.11 kernel). |
issue update
has only the result above. |
I set up my system fresh from scratch and since I have done this, I cannot reproduce the error I described above. My new set up system works well - concerning this issue - and nobody else reported the same behavior, so I'll close this issue. |
starting kodi as normal user at rpi4 only a black screen appears instead of the kodi start screen.
starting kodi with command sudo kodi the normal screen appears.
After downgrading to kernel 5.4.50 everything works again, kodi starts with his normal screen.
System
rpi4b, Raspbian OS buster, error came with kernel 5.10.xx update
no kodi crashlog appears in this context, but in syslog I can see
so kodi seems to work, but without sudo it has no right to access the graphics output...?
The text was updated successfully, but these errors were encountered: