Posts by HiassofT

I finally had a time to look at it:

Kodi seems to consume an insanely amount of (graphics) memory when browsing pictures, especially in wall mode with 4x3 thumbnails on screen.

RPi4 showed about 1GB memory usage and RPi3B+ with 256MB CMA quickly crashed because it ran out of memory.

I'm not exactly sure why kodi is doing that, maximum texture size on RPi0-3 is 2048x2048 (i.e. roughly 8MB at full HD, max 16MB for 2048x2048 at 32bit) and it looks a bit like it may be not loading the scaled-down thumbnails but allocating full textures for every picture.

Anyways, bumping CMA to 512MB looks like a good workaround for now until this is solved in kodi.

Another workaround would be to use list mode in pictures, that only shows one single picture and seems to use a lot less memory (check CmaFree in /proc/meminfo on RPi2/3 - on RPi4 graphics memory is allocated from heap so check with top there).

so long,

Hias

Please test with our latest LE10 and LE11 nightly builds from here:
https://test.libreelec.tv/

I recently removed all my testbuilds as they are heavily outdated now and no one should be using them as all my changes are in LE nightlies.

so long,

Hias

Full log with debug info would be nice. You could save it to a file "pastecrash -c > my.crash.log" and upload it somewhere (google drive, dropbox etc).

If it's too much hassle then non-debug log is OK, too.

so long,

Hias

I don't see any SMB errors in the log (failing to open a directory is usually caused by wrong permissions on the SMB server).

The crash happens in the video driver and I suspect this is caused by the previous CMA ("graphics memory") exhaustion - probably kodi got a NULL texture back, didn't check for that and later tried to display it (or something similar to that).

Unfortunately finding out the exact cause will be very tricky as building kodi with debug symbols is no longer possible (that needs way too much memory to be usable on RPi3). Also not sure why the CMA memory exhaustion occurred - either kodi tried to allocated too many textures etc or there's a memory leak somewhere...

Bedford please try increasing CMA to 512MB and if you get a crash with that, too, please post another crashlog.

so long,

Hias

Pletse post the crash log (using "pastecrash" or the crash log file uploader in LE settings). The log you uploaded only contains kodi log after it was restarted.

so long,

Hias

Might be worth opening a separate thread for the limited/full range issue.

I can't really help with that as I'm not really familiar with RK. As mandated by the HDMI standard all CTA (aka "TV") modes like 1920x1080p60 are output with limited range - some video drivers allow to override that but I have no idea if that's the case with RK.

so long,

Hias

You have to copy the edid.bin to /storage/.config/firmware/edid (eg using scp/WinSCP) - it's important that the file is placed both there and in the edid.cpio.

Note: the directory isn't present by default, you have to create it manually

mkdir -p /storage/.config/firmware/edid/

then scp the file in there and run the create-edid-cpio script

so long,

Hias

If you copied the edid.cpio from x86 or created it on RK using the guide you will get that error as the guide is faulty and only works (by chance) on x86_64.

On RK (and all other ARM devices running 32bit userspace) /lib/ is a symlink to /usr/lib and the cpio will trash that , creating a /lib directory - containing only the firmware file but no /lib/ld.so is gone and init can't be run - hence the error you got.

On x86_64 64-bit userspae is used so the trashed /lib symlink doesn't matter as it's using the /lib64 symlink.

The solution is to create the cpio with /usr/lib/firmware (the real directory), this will work both on x86_64 and arm - or just use the script I mentioned, which creates a correct edid.cpio file

so long,

Hias

The guide is wrong and only works on x86_64 - the firmware files need to be put in /usr/lib/firmware, not /lib/firmware.

But you can save yourself a lot of hassle and simply use the create-edid-cpio script in LE10/11 - it creates a /flash/edid.cpio with the contents from /storage/.config/firmware/edid

So you just need to put your edid in the .config/firmware/edid directory, run the script and adjust kernel command line.

so long,

Hias

The legacy display-related programs and config options are obsolete since LE10 switched to the standard linux graphics stack.

Don't use tvservice, vcgencmd display_power etc anymore, at best they won't do anything, at worst they might crash your RPi or mess up display output.

so long,

Hias

Ah, and testing with the latest LE11 nightly build (on a separate SD card) would also be interesting.

so long,

Hias

You could try increasing cma size further to 448 or 512 (the latter is used on RPi4 by default, but it could be problematic with only 1GB RAM).

It might also be worth to try a full clean installation on a separate SD card (without any further addons, skins etc) - it could also be related to some addon or setting you changed.

We'll need a full pastecrash log to give further advice (non-debug log might already help and cut size down, but debug log would be preferred of course).

so long,

Hias

Do you have an advancedsettings.xml file and have changed imageres , fanartres or other settings? If yes, remove your advancedsettings.xml file and test again.

so long,

Hias

Please try with stock config.txt (i.e gpu_mem=76 and no cma dtoverlay) - the log indicates you are running out of CMA memory, so 394 isn't enough.

Please post another log with stock settings if it fails.

so long,

Hias

It's a bit more involved:

in LE10 you need to change CONFIG_SND_SOC_TLV320AIC3X in projects/RPi/devices/RPi4/linux/linux.aarch64.conf to 'm', in LE10 you need to set CONFIG_SND_SOC_TLV320AIC3X_I2C to m

But the soundcard also needs a soundcard driver (dacberry400.ko) in addition to the device tree overlay.

The source code for the driver is in the src directory, but as the provided Makefile is a bit of a mess you'd need to adapt it before you can add a separate driver package for it to LE and include it in the LE build (see packages/linux-drivers/ for various out-of-tree driver packages).

Certainly doable, but a bit of a PITA.

As you payed good money to the manufacturer I'd prod him a bit more to get the sound card driver included in the official RPi kernel - or try to get a refund and buy a card with better support.

so long,

Hias

Keep gpu_mem at 76, setting it higher only wastes memory.

You could try reducing cma to 384 (as you did), but the problem seems to be that kodi is caching too many pictures and if they are large it runs out of memory at some point...

so long,

Hias

Just contact the manufacturer and ask them to PR the driver in the official RPi kernel source https://github.com/raspberrypi/linux then we can enable it when it's been added.

We won't be adding any out-of-tree drivers as they've been causing a lot of pain in the past (they need constant maintenance and tend to break on every other kernel update - and we do lots of them on a regular basis).

so long,

Hias

Thanks for reporting back!

The current LE10 nightly should be safe to use, we've been rather conservative and careful when updating the LE10 branch. But OFC we can't be 100% sure that something slipped through or will slip through in the future so always do it at your own risk.

I'm not sure if (auto-)updating LE10 nightly works as we've recently restructured the directory layout on the test server.

If in doubt just stick to the current nightly build, manually update it if you want or just update to the next official release when it's out (should be soon-ish, we're just waiting for Kodi 19.5 release).

so long,

Hias