Posts by chewitt

days not weeks

Python2, with a fixed configuration to suit Kodi (no PIP). Have a look for the EPG tools from edit4ever as they may bundle what you need.

Kodi requires Python v2 (v3 in the future with v19) so it's not user selectable, and the OS is read-only (appliance like) so does not support Python PIP unless you start creating your own add-ons with modules you require included in them. AFAIK everything else apart from socat is available though. You may be able to find add-on code for that if you don't mind self-building.

Contrast and brightness are adjusted on the TV using the remote control, not on the Raspberry Pi.

If you want to run banned repo's you're asking for help in the wrong forum. The door is that way ---->

Create /storage/.config/asound.conf and it will be used.

The autostart.sh script runs at the start of userspace boot before anything Kodi related is run. You can use it to script movement of files and folders to create a clean (or cleaner) runtime environment, e.g. moving /storage/.kodi to /storage/.kodi-old will give you a clean Kodi instance.

If the SoC chipset in your box is mentioned on this page Rockchip open source Document there is an active effort by Rockchip and the Linux community (of which LE is a part) to create mainline Linux kernel support for it and there is a possibility to run LE/Kodi images. Vendor and community efforts are focussed on current shipping and future Rockchip SoC's not the legacy stuff that shipped a few years ago, so if a SoC is not listed (and yours is not) we are not working on support and post #2 is the final answer.

The main problem with unreleased software is that it's not finished. We didn't even make an Alpha1 release yet.

disable lirc in LE settings?

I can see remains of an older OE install in the logs and there's some odd VAAPI errors so I'd SSH in and stop Kodi, rename /storage/.kodi out of the way and then wget a Kodi 18 development (milhouse) build .tar file to /storage/.update - then the box will update itself and restart with clean Kodi defaults. If it now works it's either a bug resolved in newer drivers (or Kodi) or bad config on the Krypton install. If you stick on Leia you can do some stop/move/restart to restore essential files (sources.xml, thumbs and DB's) before reinstalling add-ons.

Quote from shablamy

It should read gputemp

On AML devices the gputemp script is a symlink to cputemp and the cpu/gpu output is determined by how the script is called by Kodi.

PXE booting is niche but the code bits haven't been touched in years and require no maintenance so it's no issue to leave it in the codebase. Glad you got it working

I'd guess (and with no Kodi debug log guessing is all we can do) that the ISO RIP is using a native uncompressed codec/format that your older NUC device cannot hardware decode, and it doesn't have enough CPU grunt to cope with software decoding. Compress to H.264 which will be harware decoded and it shouldn't skip.

Well if you're running an official release the repo is embedded into the OS image and you cannot remove it so there's no need to add it, just browser add-ons by repo. If you're not running an official release it's up to whoever built the image to provide add-ons for it.

For official release it's in the LibreELEC repo not the Kodi repo.

It sounds like the install was successful (even if no video) so you can probably access the logfiles samba share to grab logs and see if there are any clues present. The red failed text is probably Xorg failing to start, which usually indicates a GPU driver issue.

Server issues are resolved. Add-ons should be available again.