balbes150

There are no compatibility problems between Libreelec and Armbian in principle (these are friendly systems that help each other develop). You may have confused it with the launch of corelec. Yes, there is a big problem from this launch on the AML s9xx platform. After that, you need to completely restore the regular Android firmware and re-activate the universal multi-boot. This should also work on Wetek (s812). No, it's not two systems together. This is an option to run both of these systems on S8xx (if multi-boot is enabled). As part of image LE is files to activate the multi-boot. But for Wetek (if I'm not confused), additional steps are needed (and perhaps add file). Details on how to activate multi-boot on Wetek is on the forum LE in the topic about s812 (there you can also take the necessary file). Test Image LE for s8xx (s805 s802 s812) dir *-s8xx https://yadi.sk/d/8vNYuuxynz1L0w

Good news. Thanks to the work done by Martin and the developers of Libreelec (Chewitt etc). An early alpha version of Libreelec with a 5.6 core is now available.This version is intended for General evaluation of the system's ability to run on s805\s802\s812. This version uses a new DTB configuration mechanism that is common with the latest Armbian versions for all RK+AW+AML platforms. You need to edit the file to configure it (uEnv.txt). If you want to test this system, I can give you a link to the images (provided that there is a report on the results of the launch). If multi-loading is already enabled on your device, the system should start automatically after setting up DTB.

Sound requires several elements (kernel , scripts, settings, etc.). All these elements are present only in the latest images. If you update only the kernel (without adding other necessary elements) in older versions, the sound will not work. Yes, I know, this only shows up on some AML chips. Compiling the kernel with a direct reference to files is a bad practice, it may be suitable for personal use, but it is not suitable for mass use. May need to correct the IDs to correctly identify the desired firmware (or rename firmware them).

According to the log, errors occurred during installation. I don't know exactly what scripts are used in this core, so I don't know how to fix them properly. Try not updating the kernel (freeze it). Or try deleting the old kernel (For example, via synaptic or dpkg) before installing the new kernel.

If you don't use the direct name /dev/mmcblk anywhere, you can ignore it.

I don't use this kernel, I don't know what changed there.

It looks like the 5.4.32 core can't install correctly. Try moving all files from /boot to another location before updating. The system may not be able to overwrite them.

Show the contents of /boot after the update (without changing anything)

remove this link, it forces you to use dtb from kernel 5.4.32 show the content armbianEnv.txt

Show the contents of the /boot directory with eMMC And show the full UART log at system startup.

Are you trying to launch with eMMC ? Which files were copied to and where (please write more details). What is your device model ?

The core starts. You need to wait about 10 minutes. This kernel is slowly unpacking Initrd.

For testing, I'm looking for volunteers who have an Odroid C1 (s805)

Look in the directory /lib/modules what the name of the directory with modules is there and you can simply copy the necessary files to the media in the /boot partition without any "chroot". Alternatively, mount the image that you installed (or started) your system from. And just copy the /boot partition (its contents) from the image. After that, you can start the system with eMMC and perform the rest of the settings without losing the current ROOTFS file system.

KODI from network repositories will not work properly. This package is not optimized for H6. Therefore, the load on the processor will be maximum and, accordingly, the temperature will also be high.

1. Have you tried other versions of the images ? 2. Have you tried to replace u-boot ? 3. Have you tried to use other DTB ?

Where did you get KODI ? Installed from network repositories as a deb package ?

Please contact the administration to move this topic to the TV box section. I would like to (as far as possible) continue this direction (native Armbian build directly on ARM devices). For skeptics. Recently, I completely moved the LivreELEC build to the ARM platform (i.e. the entire process of creating LE images and Addons now takes place on ARM rk3399\s922x devices). My dream is (perhaps) to try to transfer the ArmbianTV build completely to the ARM platform and get rid of the x86 dependency.

It is better to place this information in the mailing list, where all developers will see it faster. http://lists.infradead.org/mailman/listinfo/linux-amlogic

I didn't check this port.

I don't have such hardware, I have no idea what's wrong with the parameters there.

Sorry, I didn't understand the question, what version of images are we talking about ?

Tnx

Depending on the speed of the carrier, the initial start may take up to 10 minutes.

These are test versions that are constantly changing, so don't expect them to be stable and work correctly.