Posts by chewitt

You may want to experiment with the RPi removed from the case. We see lots of random weird bug reprots from Argon One users caused by bad connectors and such. And yes it might have worked fine in the past, but.. that's not always a relevant observation.

laurent734 LE probably needs to use ConnMan with the built-in DNS proxy to avoid DNS leaks at source; but we deliberately don't use the DNS proxy because it means Kodi GUI (correctly) shows 127.0.0.1 as the system DNS server and then we drown in annoyiing user support posts that point fingers at "networking is broken, it shows 127.0.0.1 not my real DNS server" posts from users. The workaround is to force traffic using iptables (read a few posts above).

Quote from b1k3rdude

So one question that came out of this, what version of linux is LE actually based on..?

LE is based on the priciples from https://www.linuxfromscratch.org/ which means it's effectively hand-built and not derived from any other Linux distro.

OpenELEC Testbuilds for RaspberryPi Part 3 (Kodi 14.0)

OpenELEC Testbuilds for RaspberryPi Part 3 (Kodi 14.0)

Posts are from 2014 so no idea if it still works

Start by sharing a full debug log and not the micro-snippet that you think is useful .. we want to see more.

Milhouse builds used to have an animated boot splash, although I think those stopped before we switched to the upstream DRM based video pipeline so whatever method was used might not be supported now. I checked and he appears to have deleted (or made private) all his old LE repos so I can't easily point you to the method used though, but there was one (helpful, I know).

I'll summarise:

You aren't using our normal (supported) boot mechanism

You want to add kernel modules we have avoided adding to the distro for years

You are the first person to ever mention ventoy in this forum (that I recall)

You opened a non-bug ticket in a bug tracker

The last point means the ticket will be auto-closed when I get back to my normal laptop (unless someone else beats me to it). The rest just means it would be super low priority to add support.

You are welcome (and encouraged) to self-build your own LE images with the extra modules that you need.

5GHz is capable of being faster than 2.4GHz but requires a better signal to sustain the same data rates (esp. on an RPi which has a relatively rubbish antenna to start with and might have USB3 enabled too) so often you might find a "slower" 2.4GHz connection will achieve better throughput and reliability .. until you add a bunch of other 2.4GHz devices to the network. TL/DR: If you want a reliable connection, run a cable to the RPi, or build a proper WiFi network with multiple base-stations, each with Ethernet backhaul to the main switch/router.

It's possible to fiddle with cache settings in Kodi, but while these can smooth minor peaks/toughs in bandwidth, they will never solve a lack of bandwidth or instability in the connection; which sounds more like the root cause.

The errors in the screenshot are all about device-mapper drivers being missing. I've zero knowledge of ventoy or how it tries to boot things but perhaps something changed on their side. The errors about missing files will be correct because we don't have support for DM baked into our Linux kernels. Support will be present in most conventional distros, but it's nothing new for LE (and OE before) .. we've never had support.

4K requires hardware decoding which isn’t going to work on an N2 due to current issues with the upstream decoding drivers. You’ll need to use CE on the Amlogic vendor/legacy kernel. I can’t say whether that’s laggy or not as I don’t use or track CE (and not that I find RPi4 slow either).

It runs K20b1 and widevine will work the same on C2 as an RPi or any other LE device. No harm in writing a spare SD card to experiment.

Matched DTB for "s4_ap201_4g"

I was expecting S905W2 to be similar to S905X2 (G12A) but actually this is an S4 device so there is no usable support in the upstream kernel at this time. Some patches have started to dribble in but LE will not be supporting them anytime soon. I believe CE have been working on S4 with their vendor-kernel based fork - best to look there.

8-bit HDR works reasonably well on S912 boards; we don't have proper 10-bit output yet (don't hold breath for it). The vendor kernel is more feature complete, but then you won't get the latest Kodi version (do you need it is the question).

You write the image to an SD card (same as an RPi) insert the card to the board (same as an RPi) flip the switch on the front to the right so it ignores petitboot (which does not support extlinux booting) then power on the board. There is nothing to set and it should boot straight into Kodi.

NB: You will probably want to turn hardware decoding off on the N2 (same as all G12A/B and SM1 devices). H264 works well but HEVC isn't so good and anything 10-bit wedges the board.This does limit the board to 1080p, but it works well. If you want 4K support you will need to run a vendor kernel image like CE.

LE11 nightlies support a wide range of Odroid boards using the upstream kernel, which runs better on a C2 than an N2 due to the current limbo state of the hardware decoder. You might want to run CE on the N2 and (as there is no other option these days) LE on the C2.

https://test.libreelec.tv

It was merged to the master branch so is in current LE11 nightlies. It wasn't backported to LE10.

Kodi has no support for "tonemapping" (converting HDR content to SDR and vice versa) so does your 'old' NUC support HDR? If no, there is nothing to do. If yes, when HDR content is detected the display pipeline will configure itself to use the best-matching output.