Posts by HiassofT

  • LibreElec slow booting or not booting at all

    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).

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

    so long,

    Hias

  • HDMI stops boot (matrix)

    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

  • Crash after scrolling many (larger) pictures

    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

  • Crash after scrolling many (larger) pictures

    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

  • custom edid and RK3399

    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

  • custom edid and RK3399

    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

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

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

    so long,

    Hias

  • custom edid and RK3399

    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

  • custom edid and RK3399

    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

  • vcgencmd display_power broken?

    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