Posts by HiassofT

Thanks for testing! Yes, the fix will be in 10.0.3 - feel free to use the testbuild until then.

so long,

Hias

Yes, just copy it to the update SMB share (or /storage/.update/ folder via scp) and reboot.

so long,

Hias

Can you please test this build: https://www.horus.com/~hias/tmp/libr…759-4d9d4e2.tar

It contains a fix that might help with your seeking issue (it's the same fix that was included in nightlies a few days ago and seems to have helped ghtester).

so long,

Hias

Thanks a lot for testing!

so long,

Hias

Can you please test this LE10 build: https://www.horus.com/~hias/tmp/libr…759-4d9d4e2.tar

It contains an ffmpeg fix that should help with your files (I could verify that on LE master, but can't test on LE10 right now).

so long,

Hias

Here's a LE10 build with the RTC fix: https://www.horus.com/~hias/tmp/libr…759-4d9d4e2.tar

Could you please test that as well?

so long & thanks,

Hias

Thanks for testing and reporting back, good to hear it's working!

I've created a PR for LE master https://github.com/LibreELEC/LibreELEC.tv/pull/6334 and will create a PR for LE 10 too in the next days.

Pretoriano I've thought about the linux USB issue reports, too, but not 100% sure if they are really related. Could also be some of the other USB bugs (eg missing quirk or firmware issue of your USB device/adapter).

so long,

Hias

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 here RE: TV/AVR turns back on right after turning them off

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

Quote from niels

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

Quote

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.

Quote

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