Posts by chewitt

I use a Flirc case in a semi-open space (small cabinet, behind a speaker-cloth screen) and play all kinds of media. I've not seen issues with RPi4 and cooling since the early pre-production boards which were toasty warm (and before the first flirc case samples shipped). I see no problems with HDR content either (no DV, but you won't get that on Allwinner either). I run a deliberately simple setup .. default skin, Gb Ethernet to a switch and all content on a Synology box in the Network because USB drives and cables everywhere are a pain in the arse. I have cables and AVR that will do 4K@60 but the only content I can find is test media so I don't bother enabling support and leave things in the default up-to 4K@30 mode. I avoide CEC as I have too many test boards hooked up and it's not reliable and missing things I care about. I have a simple BT remote which is good. RPi4 is the least drama device I own - I think minor changes to your setup solve most of the issues.

I'll let others chime in with advice on Allwinner and RK devices.

You might have downloaded an LE image from the LE website, but you definitely didn't download a Raspbian image. LE boot config is in /flash which needs to be remounted read-write to edit (mount -o remount,rw /flash). I've moved to the Allwinner section of the forum.

LE technical direction is to drop X11 and switch to GBM .. the same "run on the framebuffer" approach that we've used on RPi images for the last decade and also use (via V4L2) on all other ARM SoC platforms. This works great with Intel and AMD GPUs and is in the early infancy of working with nVidia after they recently capitulated on doing their own thing (which nobody adopted) and gained mesa support. To be clear, nVidia are slowly moving in the right direction, but there is still lots of missing stuff (NVDEC) and no guarantee that nVidia GPUs will have good/full support under GBM anytime soon.

Our master development branch currently still supports GBM *and* X11 image types (and Wayland, which is used with Lakka) but since GBM is our main technical direction that's the only one we auto-build and publish for testing https://test.libreelec.tv/ .. but you can self-build an X11 image or hunt around in this forum to see if anyone's sharing them you can test. Currently you will need an X11 image to get the right drivers etc. to use the card.

Again, the built-in Intel GPU on the motherboard will outperform the nVidia card for LE use. If you want the nVidia card for some other OS and use-case (Gaming, etc.) that's fine, but for LE use the nVidia card is just going to cause problems for you. Don't put a $1000 card on the shelf, sell it and use the $$ for something more meaningful.

Merged. Next nightly should have it included.

Quote from Borygo77

Any help what's going on?

No boot and debug Kodi logs = no interest in blindly guessing at your problem.

Quote from abws

What is the build command for your odroid-c2 image ?

PROJECT=Amlogic DEVICE=AMLGX ARCH=arm UBOOT_SYSTEM=odroid-c2 make release

NB: Building aarch64 images should work, but we don't build aarch64 releases so there is no repo with aarch64 binary add-ons.

If you have integrated Intel graphics, use them. The GPU will perform better than the nVidia card.

See https://wiki.libreelec.tv/hardware/intel…ric#nvidia-gpus .. then perhaps see if a Generic X11 nightly (LE11) fares any better.

If this is an Amlogic S905 box, then LE has not released any images with Kodi 19 so you are not running LE. There are nightly images for LE11 available from several places, but these use Kodi 20 (development) code, not Kodi 19.

Explain what you are actually using and then we can provide better advice.

HDR is supported for some time (8/10/12-bit HEVC) using HDR/HDR10/HLG .. but not DV as this requires proprietary info, although ffmpeg is slowly reverse-engineering capabilities to at least not display DV content badly. HD audio is supported for some time too; Kodi/ffmpeg still has occasional issues with TrueHD content still but there have been fixes done recently and it's mostly broken media that has issues now. YMMV, but RPi4 is the lowest drama device that I run.

Nobody is testing anything in advance of it being published, but there is generally an attempt to test the changes before they are merged and then automatically built/published - the build/publish process is completedly automated.

Hello Heiner,

There is negligible mainline kernel support for S905X4 hardware at the current time. Amlogic started to upstream the basics but the quality of initial code submissions is poor and developers are slow to grasp the etiquette standards needed so progress is slow. Bring-up is still at the power-domains and pinctrl stages (some UART driver changes were recently posted too, which might help your cause) but there's some way to go before upstream kernels have a usable level of support. We also have to hope the upstreaming effort continues.

Khadas has VIM4 sources here https://github.com/khadas/u-boot/tree/khadas-vim4-r which might help with understanding the changes in the boot process on your board. I didn't spend long poking around, but I can see a lot more use of signed blobs and such. I'm also told OPTEE is now used for firmware loading (Amlogic ships and requires BL32) so there is clear intent to lock things down, and most of the Amlogic driver sources that I can see are subject to an Amlogic license (not a GPL license) requiring permission to disribute the code in source or binary format. That would be a challenge for a distro like LE. In fact, the more I read and poke around into what's needed for S4/SC2/T7 hardware support, the more I think Kodi support will be limited to Android or a few Linux using OEM manufacturers. It looks like Linux support will need NDAs which LE could never sign (as no legal entity) and would never sign (on principle).

Sorry.. not much help

HiassofT are RPi2/3 are still using patchram to load BT firmware? .. these days everything else (AWL/AML/RK) is driven from device-tree. If RPi did the same we wouldn't see that error, no?

You should be able to access LE settings under the "Add-ons" menu. Not all skins have the shortcut in the Kodi settings menu.

Nothing changed since my previous post.

LE does not support any form of wifi pre-configuration and LE10.x/LE11.x no longer formally support for RPi0 (or other 512MB devies) which is the only device where this Q comes up occasionally. As already suggested, use CEC to set things up; or borrow a USB keyboard from someone.

Add "ssh" to kernel boot params in extlinux.conf and the daemon is forced to start on boot. You probably need to also add something like this to force selection of HDMI instead an LVDS source (which is probably seen as active): video=HDMI-A-1:1920x1080M@60

cubalibre looks like some kind of DRM problem; the board doesn't see any valid modes on the HDMI connection - none are listed in modetest and the kodi.log shows DRM errors. See if adding "video=HDMI-A-1:1920x1080M@60" to params in cmdline.txt works?