Posts by HiassofT

Remove the pvr.iptvsimple addon, it's causing the crash.

so long,

Hias

Read the wiki page, it's all explained in detail there. Also post the kodi_crash.log file from the FAILED kodi folder.

so long,

Hias

Most likely kodi is in safe mode and your previous .kodi folder was moved to .kodi.FAILED.

https://wiki.libreelec.tv/configuration/safe-mode

It might help if you connected a monitor and check what's displayed on screen - according to your logs you seem to be running with monitor unplugged or turned off.

so long,

Hias

See here: RE: LibreELEC-RPi2.arm-11.0-nightly-20220723-Boot loop after Kodi image - you have to remove and reinstall addons.

so long,

Hias

There's several crash logs in the URL, but a lot of them point to pvr.iptvsimple - remove and install it again as described above.

so long,

Hias

Please post kodi crash log using the crash upload function in LE settings (or "pastecrash" on the command line).

Most likely binary addons like pvr clients are causing this due to a recent change.

You need to remove the addons (eg rm -rf .kodi.FAILED/addons/pvr.hts), kodi's addon package cache (rm .kodi.FAILED/addons/packages/*) then reboot and install the addons again.

so long,

Hias

Check journal instead of dmesg, most likely you're seeing kodi crashing on startup which can happen if you have pvr or other binary addons installed - remove the addons and install them again.

Addons are currently being rebuilt, they should be available soon.

so long,

Hias

Quote from trent

Pi3 can hardware decode VC1 if you buy the key but LE 10 no longer supports these decoders.

That's not true, MPEG2 and VC1 decoder licenses still work on RPi2/3 with LE10.

so long,

Hias

Feb 02 date is normal, RPi doesn't have a real time clock so it will start up with that default date (date of systemd release, so other LE versions may have a different default date).

Your log still contains a lot of undervoltage errors - as I wrote in my previous post, use a proper power supply (I hightly recommend the official RPi power supply - others are a hit and miss).

Feb 02 15:29:48 LibreELEC kernel: Under-voltage detected! (0x00050005)

so long,

Hias

Use a proper power supply, the kernel reports undervoltage and then issues with the SD card appear.

so long,

Hias

Are you using a case, eg Argon One, or some other one which contains a HDMI adapter board? If yes, try without the case - those cases and bad HDMI cables are the most common issues for "no signal"

If this doesn't work add "drm.debug=0x04 ssh" to the end of cmdline.txt (immediately after "quiet", on the same line), boot the RPi, ssh in and run "pastekodi" and post the URL you got.

so long,

Hias

This sounds a bit like this issue: https://github.com/raspberrypi/firmware/issues/1647

Do you get a picture if you switch your TV to a different input and then back?

so long,

Hias

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