Posts by HiassofT

I just tested on a clean installation with the latest LE10 nightly build https://test.libreelec.tv/10.0/RPi/RPi4/…-5504109.img.gz, changed distroconfig.txt, config.txt and cmdline.txt as outlined in my post you linked to and it worked fine (running on PAL, 720x576).

I suggest you do the same - the SD card came preinstalled with kodi and you upgraded to LE10 it could be there's some crap on the installation that prevents kodi from starting (and upgrading eg from 9.2 to 10 isn't supported at all - it can work but often it doesn't).

Also make sure everything in cmdline.txt is on a single line and you don't omit the "e" on the video setting - you have to use eg

video=Composite-1:720x576@50ie

otherwise you just see the LibreELEC splash screen - kodi will start but you don't see it's splash or GUI.

so long,

Hias

Please test with the latest LE10 nightly build from here
https://test.libreelec.tv/10.0/RPi/RPi4/

ISTR 10.0.2 had some (composite) bugs that are fixed now.

Editing distroconfig.txt isn't ideal (as it will be replaced on updates) but should work - better keep a copy of it when you got it working.

I've thought about better solutions like having a separate distroconfig-composite.txt but while working on that composite configuration in RPi kernel/devicetree changed again and I decided to wait a bit until things had settled.

so long,

Hias

popcornmix rebased his changes, PR with update to current kodi master is here:

kodi: update to latest master by HiassofT · Pull Request #6859 · LibreELEC/LibreELEC.tv

This also includes rebased RPi colorspace/bpc patches. Runtime tested on RPi4

github.com

so long,

Hias

You haven't enabled debug logging so it's a bit hard to tell what really went wrong in your case but my guess is this is the long standing issue with kodi trying to create too many scaled-down thumbnails on the fily and thus exhausting (graphics) memory.

You could try running texturecache.py c, this will take a while and create thumbnails in a way that shouldn't trigger the issue - after that browsing should work fine.

Increasing CMA memory (that's the kind used for graphics) could remedy the issue a bit, too but probably won't help as much as creating all thumbnails upfront - add eg dtoverlay=cma,cma-512 to the end of /flash/config.txt

so long,

Hias

ISTR there were issues when tvheadend is running on the same device where video is being played back.

It could be that the memory bandwidth required for deinterlacing interferes with operation of the USB DVB hardware and/or drivers and/or tvheadend - might be too short buffers (in HW or driver) or something similar in tvheadend like increased latency resulting in dropped buffers/packets.

I don't think a definitive solution for that was found, other than moving tvheadend (with the DVB receiver) to a separate device.

so long,

Hias

Hmm, just checked the sample on my Linux laptop with VLC and mpv and there are blocking artifacts at around 15-17 seconds - so there seems at least to be an issue with the recording. Do you see other artifacts at different timestamps with LE?

so long,

Hias

Thanks a lot for the sample!

I'm a bit busy with my daytime job ATM but I'll have a look the next couple of days, not sure if I manage to check before next weekend though.

so long,

Hias

Can you share a short sample / recording that triggers the issue?

so long,

Hias

There were a lot of changes between 9.2 and 10 (completely new graphics stack on RPi, python 2->3 change etc) so it was a gamble if upgrading worked or not - hence our decision to not officially support it. LE10->11 should be a lot smoother (still there might be issues with addons, they have always been the main obstacles).

Migrating just your movies/music collection isn't too hard (search the forum, there have been detailed discussions about it).

Basically stop kodi (systemctl stop kodi), delete all MyVideos and MyMusic databases in .kodi/userdata/Database, copy the latest versions from your old installation there and also restore .kodi/userdata/sources.xml, then reboot (or start kodi again).

so long,

Hias

First of all you should have done a clean installation of LE10, upgrading from LE9.2 isn't supported.

Secondly, I'm the main RPi developer / maintainer so you can trust me that using the LE10 nightly builds will work fine - they contain several important bugfixes since LE10.0.2.

Thirdly, don't restore a backup from your LE9.2 or LE10 installation, they will pull in your banned addons (and probably other stuff that will cause issues) and you won't get support here.

so long,

Hias

Do a clean installation with the lastest LE10 nightly from here: https://test.libreelec.tv/10.0/RPi/RPi2/

You have tons of banned addons and wizards installed, don't install them again - you won't get any support on this forum if they are present.

If the issue persists then post new logs.

so long,

Hias

Check out https://rpilocator.com/ (or subscribe to their twitter feed to get stock updates).

Semaf (in Austria) currently has 2GB RPi4 in stock

Raspberry Pi 4 - 1.5GHz ARM Cortex A72 - 2GB LPDDR4 RAM

Raspberry Pi 4 is the first 28nm-based product The Raspberry Pi 4 has 1 5Ghz ARM Cortex A72 CPU, 2GB LPDDR RAM, 2x USB 3 0 Ports, a true Gigabit Ethernet an

electronics.semaf.at

so long,

Hias

4k H264 files are not supported on RPi - use H265/HEVC files for 4k.

so long,

Hias

Sorry, all I know about the sundek driver is that it exists and as it's closed-source binaries (i.e. not built for LE) it could be anything.

so long,

Hias

Quote from JoeAverage

so to prevent FS corruption you need to either

- shutdown the RPi (system will umount all mounted disks)

or

- in an terminal run "umount /var/media/*" or better "sysnc && sync && umount /var/media/*"

before unplugging the disk.

Or just use the "remove media" option from the context menu in the video files view.

so long,

Hias

Booting is handled by the bootloader in the RPi's EEPROM.

You can configure where to boot from (SD, USB, network) and then it'll search on these devices for a FAT partition (on SD/USB) containing firmware files (http://start.elf/fixup.dat).

So if you don't have a FAT partition on your 6TB the RPi won't boot from it - the bootloader will scan through the USB devices and spin it up though (to read the partition table).

cmdline.txt on the boot partition then determines which partitions LE should use for boot/flash (pointing back to the boot partition) and storage - by default these will be the ones from your LE installation (eg on SSD).

During bootup LE will then scan for all USB devices and mount all partitions (except boot/flash and storage, which are already mounted) in /var/media so you can access them - here your 6TB HDD will get mounted.

so long,

Hias

You could try using the official RPi imager tool to write RPiOS or LibreELEC to the SD card, IIRC it will do a verify pass after writing the image to SD card

Raspberry Pi OS – Raspberry Pi

From industries large and small, to the kitchen table tinkerer, to the classroom coder, we make computing accessible and affordable for everybody.

www.raspberrypi.com

Other disk imaging software might have a verify function, too, if yes use it to verify if the SD card is actually OK (SD card, card reader on your PC could all be faulty meaning you would be chasing a ghost searching for an issue on the RPi side).

so long,

Hias

Just run pastekodi again, sometimes the paste-site has hiccups (I've seen that lots of times myself).

Black screen can have lots of causes, just do a forum search and you'll find plenty of hints and/or answers.

so long,

Hias