Posts by chewitt

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.

You need to follow a "backup > clean-install > manual restore" process to update the box. Clean install requires you to trigger recovery boot mode so the box reads new/updated bootscripts from the SD card; then it can find the new upstream device-tree (configured in uEnv.ini) and the boot files. Once Kodi is installed and running you can copy the backup to the box and do a manual restore of the essential bits (databases, thumbs, sources, add-on settings) and then restart Kodi. Then reinstall new Python3 versions of any add-ons you were using and you're done.

You cannot directly update - it will either refuse the update or if you force it, it will break boot (the box is not bricked, but you need to do the recovery process to get a working system again).

Or you stick with whatever image is on the box now .. if it all still works, nothing is forcing you to update.

99.999% of LE users have no idea that a local console exists (in debug mode) and thus have no need to access it, so we haven't wasted space in the image adding font-size-changing binaries that 0.001% of users or less will use.

Have you tried experimenting with fbcon=font: options in kernel boot params? https://www.kernel.org/doc/Documentation/fb/fbcon.txt

Quote from razvanelgsm

Hello! I have in hand Vontar X2 box with s905w2 and I manage connect serial wires and dump a boot log when i try to boot it from sdcard (armbian), I can provide this dumps and play more on this if you want to try.

I'd prefer to see output from the LE "box" image (not Armbian) since we normally use a newer kernel and I know what patches are being used with it - I don't track Armbian kernels. Please experiment with different SM1 device-trees and share logs.

https://test.libreelec.tv/11.0/Amlogic/box/ <= LE11 nightly images with K20

These images are using the upstream kernel codebase that isn't 100% feature comparable to the legacy vendor codebase, but it's still quite usable for most users (and the only option for S912 devices in the future anyways).

https://hub.docker.com/r/honeygain/honeygain should be usable via the Docker add-on

You don't configure the OS in LE to give bigger console text. You connect via SSH using an app and you set font size in the app. Or - you need to explain what you are trying to do - because it is not clear.

You might need to explain what "pb" is to get an answer.