Posts by HiassofT

  • RPI4 on Libreelec 9.1.502 thumbnail/pictures problems

    I could reproduce the crash with the testfiles on a RPi4 with total_mem=1024 in config.txt Problem is that kodi is running out of memory.

    Keep in mind that (GPU) memory allocation on RPi4 is rather different to RPi3:

    On RPi4 the gpu_mem is needed for video decoding and the memory needed by the 3D graphics chip is allocated from system memory. The latter can be quite big (check for CmaTotal and CmaFree in /proc/meminfo), with a HD monitor I see about 35MB being used, with a 4k display about 90MB.

    It's planned to make memory allocation more dynamic, but that's not finished yet so for now the RPi4 needs more memory than the RPi3.

    1GB RAM and 4k output on the RPi4 isn't an ideal combination - for 4k output a 2GB RPi4 is recommended.

    so long,

    Hias

  • Why complete logs?

    The reason is quite simple: more often than not the actual error is way before what users think the errors is. eg. video playback may crash if some setup at the very beginning (audio devices, video driver setup etc) went wrong. If users then just post the snipped where eg video playback crashed it's completely useless as it doesn't contain the important information for developers - the context.

    Don't worry too much about "private" stuff, passwords etc are usually automatically redacted in kodi logs so no one will know about them. And knowing that your NAS is at 192.168.1.123 won't give anyone access to it either.

    If you are worried that your log shows "playing XXX_hardcore_porn_from_torrent_site.mkv" then, well, rename that file to something harmless before.

    Anyways, if in doubt do a clean installation (which doesn't contain any possible private info), play files from local harddrives with harmless names, and don't install tons of addons. Then you have nothing to worry about and both you and devs know that it's not one of the odd addons or config settings that's causing your problems.

    TL;DR Most important thing to know is that cut down or redacted logs will be simply ignored by devs - so if you want support post full logs. Cutting down or redacting logs is wasted time, no one will look at them.

    so long,

    Hias

  • log2ram support

    /var (and thus /var/log) are already in RAM so log2ram won't provide any benefit. Also note that by default the systemd journal is only kept in RAM (without being written to /var/log/journal) unless you add "debugging" to the kernel command line - which enables permanent journal logging to /storage.

    Kodi's log (/storage/.kodi/temp/kodi.log) will always be written to SD card (though that's not too many writes, unless you enable debug logging in kodi).

    so long,

    Hias

  • Hyperion hypercon problem no green and white lights

    Arduino sketch is on github ledstream.pde

    Depending on which Arduino (clone) you use you may need to modify the source (see comments at the beginning) and some of the smaller/cheaper boards require you to solder in the 0.1" connectors yourself.

    Just make sure you get an Arduino with Atmega 32u4 (this is the one with USB built-in, the older/other Arduinos with separate USB/serial chip won't work well as communication will be too slow).

    In hypercon / hyperion.config.json set the type to "adalight" and port to "/dev/ttyACM0"

    For other details about arduino stuff and the Adalight / ledstream sketch just search the net, there are tons of infos out there.

    so long,

    Hias

  • Hyperion hypercon problem no green and white lights

    I'm not using a level-shifter myself, I use a "Adalight" / Arduino to connect the LED strip. The Arduino outputs 5V signals so there's no problem to drive the WS2801 (which require a minimum of 4V for logic high input signals).

    The 74HCT00 circuit on the hyperion wiki Supported hardware | Hyperion - Forum looks fine, if you build it yourself don't forget to connect +5V from the RPi to pin 14 and GND to pin 7 of the 74HCT00 - that small detail is missing in the schematic (buit their PCB looks OK).

    so long,

    Hias

  • RPi4. USB-ports does not turn-off power after shutdown.

    Yes, this is the default behaviour in current RPi4 bootloader firmware. You can change that by editing the bootloader config settings.

    On LibreELEC 9.2 Beta 2 (9.1.502) first run the following command to get the default config:

    Code
    LibreELEC:~ # rpi-eeprom-config --out /tmp/config /lib/firmware/raspberrypi/bootloader/critical/pieeprom-2019-09-10.bin

    Then edit the /tmp/config file and change POWER_OFF_ON_HALT to 1 and WAKE_ON_GPIO to 0.

    eg run

    Code
    LibreELEC:~ # nano /tmp/config

    the config should then look like this:

    Code
    BOOT_UART=0
WAKE_ON_GPIO=0
POWER_OFF_ON_HALT=1
FREEZE_VERSION=0

    Then create a bootloader firmware file with the changed config and install it

    Code
    LibreELEC:~ # rpi-eeprom-config /lib/firmware/raspberrypi/bootloader/critical/pieeprom-2019-09-10.bin --config /tmp/config --out /tmp/pieeprom
LibreELEC:~ # rpi-eeprom-update -d -f /tmp/pieeprom

    Now reboot to update the bootloader eeprom.

    You can check if the update was successful by running vcgencmd bootloader_version (it should report Sep 10 2019) and vcgencmd bootloader_config (it should print the config from above).

    Note: you only have to do this once, subsequent bootloader updates (via the LE settings addon) will keep config in the bootloader eeprom intact.

    so long,

    Hias

  • Radio Remote Control not working with 9.1.501

    Sorry, can't really comment on RF remotes, maybe someone else has a recommendation.

    If you have an IR receiver on your RPi configure your Harmony to the Microsoft Media Center profile - this will work out of the box with LibreELEC.

    CEC may be another option.

    I'm mainly using an IR remote on my RPi, sometimes just CEC for basic navigation and if I need to enter lots of text I have a Logitech K400.

    so long,

    Hias