Posts by chewitt

Yes, it's broken for a while now (and nobody understands Qt properly to fix it). Please use Etcher to create USB/SD cards.

U-boot also allows the entire boot process to be encrypted/signed and protected; but this requires support for those things in Silicon which increases costs, so you almost never see it with cheap TV box devices.

It looks like "quiet" is missing from boot params (so you see the earlycon boot content).

RPi4 can boot via u-boot, but it's not needed and we don't use it with LE images for RPi devices. And if the user needs to ask Q's at the current level the likelihood of them building a custom image that implements u-boot support for RPi in LE is rather unlikely IMHO.

liberi That isn't going to work on an RPi4 which doesn't use Grub2 (or any other normal bootloader).

Take a backup of the .kodi folder and contents from the RPiOS install, store it somewhere safe. Once you installed LE via PINN or NOOBS for some level of multi-boot support you can copy the backup file over and manually restore content by stopping Kodi, moving files to the right places, restarting Kodi again.

NB: It is not possible to install LE into a partition. It is not possible to use an NTFS drive as the /storage partition. You can use the NTFS drive as a separate media drive that's shared between several OS without issues, but /storage needs Unix filesystem permissions support.

I know nothing about RK hardware

Older devices may also need the "Use Legacy Security" option enabled.

It means I won't be publishing more LE10 images, as I moved my codebase forwards onto the master branch (K20 pre-alpha). See:

amlogic: bump to Linux 5.15.y and other misc. changes by chewitt · Pull Request #5920 · LibreELEC/LibreELEC.tv

This bumps Amlogic (GX) to Linux 5.15.y with the following notable changes: Switch bootloader/install to use Makefiles in amlogic-boot-fip sources Move…

github.com

For the crackling audio, see if reducing volume on the mixer to ~80% helps. It seems to be a common remedy to similar reports on a large variety of cards (not specifically Amlogic). Thanks for sharing the mixer settings, I will validate and add to our soundconfig script.

Index of /testing/

As long as the binaries are in the $PATH it doesn't matter whether they were embedded into the image or packaged as an add-on.

https://chewitt.libreelec.tv/testing/ has some experimental K19 and K20 images for C2. There are bugs, but H264/1080p works well enough and if you avoid fiddling with Kodi audio settings you shouldn't trip the main unresolved audio bug too often. The C2 image boots and runs Kodi 19 at least. I don't plan on maintaining the Matrix images as I've moved the codebase to (pre-Alpha) Nexus now. NB: You cannot update with these images as the boot process is completely different to older releases, so you must clean install.

It's probably easiest to make a new SD cards and start over. The default 32MB /storage partition should be resized to 100% on first boot. For some unknown reason that didn't happen and unless you are familiar with Linux CLI commands and have another Linux VM around to mount the card and fix the partitions with, it's not something that's simple to resolve (cannot be done from the booted card). As a rule, the 2% of LE users who know how to solve that stuff just fix it instead of asking Qs in forums, so I assume you're iin the other 98%.

Quote from JAXXX

MeCool BB2 Pro S912

Use the box image and experiment with the MeCool KIII Pro dtb, it's probably identical specs.

The main challenge with u-boot on Meson8 boards is that half the stuff you think you know hasn't been implemented yet on the prehistoric version of u-boot that's being used .. it's an archeological exercise

LE's KERNEL file contains an initramfs so we don't use a separate initrd file, and we avoid the entire topic of coexistence with other distros by simply not supporting it. As a rule it's not a big requirement on ARM devices among our userbase so we avoid the heartache.

wrxtasy released images for C1 for a while and I can see active installs in our stats server, so there is prior-art in his GitHub repo. There is also ongoing effort from dtech to adapt his LE 9.2.x image.

There is also a slow-burning effort to run mainline kernels on Meson8 boards. The amlogic-mx branch in my LE repo builds images but we did not figure out the u-boot bootscripts needed yet, so we are interested in what you figure out. Keep sharing infos.

Current K20 images from my webshare have no hardware decode (which is why H264/HEVC and seeking etc. work great). All 1080p media will probably work fine on GXM and newer boxes due to better CPUs but GXBB/GXL struggle a bit unless the bitrates are low. I'm attempting to use the same ffmpeg sources as Raspberry Pi due to the huge time/effort that the Pi devs have put into ffmpeg/v4l2_m2m, but the current sources have become a bit too Pi flavoured and we didn't figure out how to add quirks for Amlogic yet. There is also no progress with "the noise" on GXBB/GXL/GXM boxes so beware of Kodi audio setting changes, as that's an easy way to trip them (if making changes, keep the TV or AVR volume super low, and if you trip it, toggling settings will fix it).

The purple line needs something in the HDMI/DRM code to be poked, a register is off somewhere on not being set. I've no idea how to do that so can't really investigate - I've flagged it to the upstream maintainers though.

NB: I have no real plans to maintain K19 images going forwards so 10.0.x files will probably be deleted in the next week. I'll fork the branch on my GitHub LE repo in case anyone needs to build from them.

1. The kernel expects to find SYSTEM in the same partition as the KERNEL (or kernel.img) file. I'm not aware of a way to pass SYSTEM as a param but since I can't think of any reason to put it anywhere other than the boot partition I'm not sure it would be needed.

2. "printenv" will show the u-boot environment via UART cable on a working board. If no UART you'll need to dive into the ancient Hardkernel sources. I wouldn't attempt to mess around with the default boot flow that's present in existing C1 images. It works, and the code behind it is crappy so by fiddling with it (from experience) you will only break something, and fixes bring new exiting bugs to play with.

3. I'm not really sure what the question is. Leave the boot flow alone.

If not, you know your next move