Easiest way to debug such things is with a serial console. Remove "quiet" from cmdline.txt and add "systemd.debug_shell ignore_loglevel" - for initramfs debugging adding "debugging" and "progress" may also help.
I'm not using a USB/SSD here and rarely do updates on SD card, most of the time I netboot my dev systems and update the boot partition with a simple script using the files in the tar
so long,
Hias
The last two lines are normal (and harmless) and you can safely ignore them, the first one (10min invalid argument) is odd though and should not be there.
Not sure where that should come from, 10 minutes sounds like a ridiculously long timeout. Did you add some systemd services and set it there?
so long,
Hias
Can you give this build a try?
https://www.horus.com/~hias/tmp/libreelec/LibreELEC-RPi4.arm-11.0-devel-20220327210704-a78ef86.tar
I noticed RPi kernels didn't have CONFIG_RTC_HCTOSYS enabled, since kernel 5.10 that should also work with RTC drivers built as a module and thus system time should be automagically set after module load if it's not been set up yet - so the (broken) udev rule should no longer be needed.
Would be great if you could give that a try, I don't have any RTCs for RPi4 here.
BTW: source code is here: https://github.com/HiassofT/LibreELEC.tv/tree/le11-test
so long,
Hias
Thanks, ir-keytable -r output looks OK.
Please try running "ir-keytable -p all -t", push some buttons on the remote and post the output.
Also run "ir-ctl -r", push a single button for a very short time (quarter or max half a second) and post the full output you got - the ir-ctl output in your first post looks rather odd.
BTW: are you sure the batteries in the remote are OK?
so long,
Hias
did you stop kodi and eventlircd before? What's the output of ir-keytable -r?
so long,
Hias
NeB the file also plays fine here on RPi4 - both on LE10.0.2 and nightly and both on my HD monitor and 4k TV.
Note that this is a 10bit video so RPi4 may now output it in 10 or 12bit, depending on the capabilities of your TV.
Check your TV's settings, try a different HDMI cable (bandwidth could now be 50% higher than before) and post a debug "pastekodi" log if the issue persists.
so long,
Hias
See https://wiki.libreelec.tv/configuration/…troubleshooting
Especially the output of ir-keytable -t (with kodi and eventlircd stopped) would be useful. Also make sure you are not running lircd (i.e. you don't have a lircd.conf file in .config).
Also post the output of ir-keytable -r
so long,
Hias
Can you please post some detailed log where kodi didn't like the addon version? We've been using that scheme for ages and haven't seen any issues so far.
so long,
Hias
The .1/.3/... at the end is nothing you need to worry about, it's simply the PKG_REV added to the original addon version - see eg here https://github.com/LibreELEC/Libr…o/package.mk#L7
Most of the time PKG_REV will be .1, sometimes when we need to roll out new versions of the addons (eg when important underlying dependencies have changed) we increment PKG_REV so kodi sees it as a new addon version.
so long,
Hias
thanks, but why is the procedure distinct for rpi3 and rpi4 ? is it risky to upgrade on rpi3 ?
No, it's exactly the same. If you run LE 9.2 it's strongly advised you make a complete clean install of LE 10, as mentioned in the release note (see first post)
LibreELEC (Matrix) 10.0.2 - LibreELEC
Users of LibreELEC 10 Beta or RC1 get an automatic update to the final version. LibreELEC 9.2 setups will not be automatically updated, you will need to manually update.
So unless you are already running an image with Kodi 19 inside, a clean install is preferred. We apologize for the inconvenience, but we expect a much higher than normal support effort with in-place upgrades so it’s sensible advice.
so long,
Hias
Thanks for the info, this seems to be a widevine issue - see eg here https://github.com/xbmc/inputstream.adaptive/issues/877 - reverting back to older widevine version seems to help in this case
so long,
Hias
busfahrer303 thanks for the info! Can you please do a test with this build:
https://www.horus.com/~hias/tmp/libreelec/LibreELEC-RPi4.arm-10.0-devel-20220319153448-7f96b91.tar
I've added a bit of additional debug logging which will show if and when scrambling is used. Please reproduce the issue and post a log from that build.
BTW: I strongly recommend setting kodi gui resolution to 1920x1080 60Hz, not 3840x2160 30Hz. Kodi will keep using GUI resolution as a fallback when none of the whitelist entries match and 30Hz is a very bad choice eg for 50/60fps video playback.
so long,
Hias
Just tested your sample and got the same "no signal" issue here. Not quite sure what's going wrong, I've informed RPi devs about it.
so long,
Hias
I'm still puzzled about your first log. Did you also have no picture after TV power off/on at 3840x2160 30Hz? Does it also happen at 1920x1080 (60 and 30 Hz)?
so long,
Hias
Try a different, HDMI Premium certified ,HDMI cable. RPi4 will now output 10/12bit video which means you'll see issues like that with cables that don't meet the specs.
See also here: RE: RPi Deinterlacer testbuild
so long,
Hias
busfahrer303 I just checked your log again and you don't seem to be using 4kp50/60 output - log shows kodi GUI runs in 4kp30 and the 720p video playback switches to 4kp25 - so scratch my comments about scrambling.
INFO <general>: GUI format 1920x1080, Display 3840x2160 @ 30.000000 Hz
INFO <general>: Display resolution ADJUST : 3840x2160 @ 25.000000 Hz (29)BTW: I highly recommend configuring your display settings and whitelist as described in the wiki: https://wiki.libreelec.tv/configuration/4k-hdr
so long,
Hias