Skip to content
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

Closed
micha53 opened this issue Feb 15, 2021 · 8 comments
Closed

Kernel 5.10 Kodi has no screen output at rpi4b #4147

micha53 opened this issue Feb 15, 2021 · 8 comments

Comments

@micha53
Copy link

micha53 commented Feb 15, 2021

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

Feb 14 12:25:42 Medienserver tvheadend[699]: htsp: Got connection from 192.168.178.43
Feb 14 12:25:42 Medienserver tvheadend[699]: htsp: 192.168.178.43: Welcomed client software: Kodi Media Center (HTSPv34)
Feb 14 12:25:42 Medienserver tvheadend[699]: htsp: 192.168.178.43 [ Kodi Media Center ]: Identified as user 'micha'
Feb 14 12:25:42 Medienserver tvheadend[699]: htsp: 192.168.178.43 [ micha | Kodi Media Center ]: Privileges updated

so kodi seems to work, but without sudo it has no right to access the graphics output...?

@micha53 micha53 changed the title Kodi has no screen output at rpi4b Kernel 5.10 Kodi has no screen output at rpi4b Feb 15, 2021
@popcornmix
Copy link
Collaborator

Can you post link to ~/.kodi/temp/kodi.log (e.g. on pastebin type site). Also dmesg output.

@micha53
Copy link
Author

micha53 commented Feb 15, 2021

dmsg is from after downgrade to 5.4. The logs probably too, not sure.
dmesg.txt
kodi.log
kodi.old.log

@popcornmix
Copy link
Collaborator

Logs are only useful if they show the issue (i.e. on 5.10 kernel).

@micha53
Copy link
Author

micha53 commented Feb 15, 2021

I agree, but that is all I find, 'cause I turned back my system today to verify that the error came with 5.10.
But at least kodi.old.log is from 5.10.
I made the downgrade between 3:00 and 4:00 p.m.

@zito
Copy link

zito commented Feb 15, 2021

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:

root@pi4:/home/kodi/.kodi/temp# cat /etc/systemd/system/kodi.service
[Unit]
Description = Kodi Media Center
After = remote-fs.target network-online.target
Wants = network-online.target

[Service]
User = kodi
Group = kodi
Type = simple
ExecStart = /usr/bin/kodi-standalone
Restart = on-abort
RestartSec = 5

[Install]
WantedBy = multi-user.target

stopping the service takes long time. Starting again and trying to switch channels leads to distorted graphics
and the whole system hangs finally. I can see disk activity.
I cannot find anything usable in logs :-(

@zito
Copy link

zito commented Feb 16, 2021

I recorded a short sample of "safe" source channel and a sample of "problem" source channel.

Input #0, mpegts, from 'Udalosti v regionech.ts':
Duration: 00:00:05.23, start: 66887.062511, bitrate: 3468 kb/s
Program 1
Metadata:
service_name : CT 1 HD T2
service_provider: CESKA TELEVIZE
Stream #0:1[0x83e]: Video: hevc (Main) ([36][0][0][0] / 0x0024), yuv420p(tv, bt709), 1920x1080 [SAR 1:1 DAR 16:9], 50 fps, 50 tbr, 90k tbn, 50 tbc
Stream #0:20x848: Audio: aac_latm (LC) ([17][0][0][0] / 0x0011), 48000 Hz, stereo, fltp
Stream #0:30x849: Audio: aac_latm (LC) ([17][0][0][0] / 0x0011), 48000 Hz, stereo, fltp
Stream #0:40x84a: Audio: ac3 (AC-3 / 0x332D4341), 48000 Hz, stereo, fltp, 448 kb/s
Stream #0:50x84b: Audio: aac_latm (LC) ([17][0][0][0] / 0x0011), 48000 Hz, mono, fltp (visual impaired) (descriptions) (dependent)
Stream #0:60x852: Subtitle: dvb_teletext ([6][0][0][0] / 0x0006)
Stream #0:70x866: Subtitle: dvb_subtitle ([6][0][0][0] / 0x0006) (hearing impaired)
No Program
Stream #0:0[0x12]: Data: epg

Input #0, mpegts, from 'Slunce, seno, erotika.ts':
Duration: 00:00:15.03, start: 40957.720178, bitrate: 1934 kb/s
Program 1
Metadata:
service_name : Nova Cinema
service_provider: CDG
Stream #0:1[0xc94]: Video: hevc (Main) ([36][0][0][0] / 0x0024), yuv420p(tv), 960x540 [SAR 1:1 DAR 16:9], 50 fps, 50 tbr, 90k tbn, 50 tbc
Stream #0:20xc95: Audio: aac_latm (LC) ([17][0][0][0] / 0x0011), 48000 Hz, stereo, fltp
Stream #0:30xc9c: Subtitle: dvb_subtitle ([6][0][0][0] / 0x0006)
No Program
Stream #0:0[0x12]: Data: epg

A try to play "problem" sample causes kodi hang (with the fkms driver an the 5.10.11 kernel).

@micha53
Copy link
Author

micha53 commented Feb 17, 2021

issue update
today I made an installation of smb with the 5.4. kernel.
Starting kodi later kodi again does not appear at the screen, but sure it works. Somehow occasionally I started a TV program, and the TV screen appeared. Stopping TV again brought a black screen.
From a putty terminal I cold killall kodi, but not kodi.bin.v8. Even kill -9

pi@Medienserver:~ $ sudo killall kodi.bin_v8
pi@Medienserver:~ $ ps -A | grep kodi
2819 tty1 00:03:41 kodi.bin_v8
pi@Medienserver:~ $ ps -A | grep kodi
2819 tty1 00:03:43 kodi.bin_v8
pi@Medienserver:~ $ sudo kill -9 2819
pi@Medienserver:~ $ ps -A | grep kodi
2819 tty1 00:03:49 kodi.bin_v8

has only the result above.
Once started I can terminate kodi - blind - pressing "up" and twice "ret", like I would do it seeing the screen.
kodi.logs and dmesg are from the actual situation:
dmesg.txt
kodi.log
kodi_crashlog-20210217_202739.log

@micha53
Copy link
Author

micha53 commented Feb 23, 2021

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.

@micha53 micha53 closed this as completed Feb 23, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants