balbes150

One great options is to help make it. I am pretty sure that all current maintainers have a big pile of hardware and very little time. More load is almost impossible to add ... I talked with @balbes150 about this problem long time ago. He is having boxes, I am having boards. Have it or have a free access to them. This is still the same. We as a community, not just he and I, wants to see project develop further. We (those few people who stands out with their work) can't produce more and more. It doesn't go that way ... it's more, more, more ... and once nothing more  That is bad for all. The one wants to work but he can't and community lost one of the prime contributors.

If you or someone else wants to see this and that board/hardware supported, become its maintainer. It's a long term micro job and we can arrange samples or other random boards from our (over)stock and donations cuts for compensation/motivation.
 
Making board officially supported means answering to its problems over longer period of time. Someone has to take that prime responsibility and someone has to serve as a backup. IMO current maintainers could jump on backup roles at best.

Hi, everyone can get the info now, it's public, sorry if I'm infringing on Armbian's copyright or something by rehosting the files, but I compiled the kernel + built the image myself...
 
https://projects.milankragujevic.com/amlogic/s805/2018-10-28/
 
Included is the .config file I used. 

Version 20181113.
Expanded the list of modules for wifi.

Both addresses are correct. But each is used for its task (function).
 
1. It is very bad advice - to destroy regular u-boot on TV box. You run the risk of getting a brick that will have to be restored. If the user is lucky and has the necessary firmware files for recovery, cable, software and skills for this, he will be able to recover.
2. Since when are scripts not part of Armbian ?
 
I really want to look at the source code (build environment) "pure vanilla Armbian" for TV boxes.

Version 20181113.
Expanded the list of modules for wifi.

Version 20181113.
Expanded the list of modules for wifi.

I got my EDGE this weekend. And in the coming days plans to start assembling and testing Armbian for Khadas EDGE.
 
By the way, according to Robert, this model plays well videos up to 4K on Ubuntu from Youtube.
https://forum.freaktab.com/forum/tv-player-support/rockchip-based-tv-players/rk3399-devices/733786-edge-rk3399-by-khadas-for-those-that-like-to-tinker?p=750851#post750851

Update Ver 20181112

I got my EDGE this weekend. And in the coming days plans to start assembling and testing Armbian for Khadas EDGE.
 
By the way, according to Robert, this model plays well videos up to 4K on Ubuntu from Youtube.
https://forum.freaktab.com/forum/tv-player-support/rockchip-based-tv-players/rk3399-devices/733786-edge-rk3399-by-khadas-for-those-that-like-to-tinker?p=750851#post750851

Update Ver 20181112

Information in this topic is very outdated see this topic.
 
 
 
 
 
 
The start system in Coreelec is not compatible with LibreELECE  Armbian  etc. If you run coreelec on your TV box, you will no longer be able to run LE and Armbian normally until the full recovery of the standard firmware via the USB Burn Tool and the new activation of the universal multi-boot, which is used in all new systems.
 
 
The new version 5.55 of images. In this version, images with a single DE (XFCE) and a server in composition are as close as possible to the official versions. Version with a Mate and Icewm will probably be later and the gathering will be from another branch GIT (specially adapted for this DE). Since now all the images will be collected using the main kernel "4.1 x", have a common structure for the entire line of s9xxx and differ significantly in steps when configuring the system, I open a separate topic for this direction.
 
 
https://yadi.sk/d/pHxaRAs-tZiei
 
https://mega.nz/#F!j9QSDQSQ!6WpasOlbZYIInfw6yo4phQ
 
The primary steps to capture an image, activate multi-boot, and select a dtb file are common with the previous images.
 
 
Please note that starting with the version number version 20180928.
Major change. A new algorithm for the use of the dtb. Starting with this version, you no longer need to copy the dtb files and rename it to "dtb.img." In order to specify which dtb file to use, you need to edit the file 'uEnv.ini" (specify the desired file name for use dtb). This is a plain text file and can be easily edited. This change will make it easy to update the kernel from the "deb" file in the future. The new algorithm is now used in the eMMC system installation script.
 
Be sure to activate multi-boot using the new image. If multiboot previously activated is required to repeat activation using files in a new image.
 
Pay attention. To use the system with
u-boot-2015 (regular firmware Android), you need to edit the file "uEnv.ini"
 
When using
u-boot-2018, you need to edit the file "/extlinux/extlinux.conf"
 
 
For those who doubt or do not know what u-boot is used, you can specify the desired name in both files at the same time.
 
 
To change the used MAC address.
 
1 options
You can add the required parameter to the startup files (uEnv.ini and extlinux.conf). To do this, at the end of the line with the launch parameters, you need to add a parameter specifying the desired MAC address.
For example,
mac=xx:xx:xx:xx:xx 
or
ethaddr=xx:xx:xx:xx:xx
 
 
 
Old info multiboot
 
https://sourceforge.net/p/amlogic-s9xxx/code/ci/master/tree/
 
add info
 
https://medium.com/@vysmol/how-to-install-ubuntu-on-s905w-and-simular-tv-boxes-ru-eng-7aca3e1011a5
 
 
Install Armbian to eMMC.
1. Be sure to activate multi-boot using the new image. If multiboot previously activated is required to repeat activation using files in a new image.
2. Run Armbian from external media, run "ddbr" and create full backup eMMC.
3.  install Armbian on eMMC execute script “/root/install.sh”.
 
Please note, this is a test installation, which was tested only on a few models. Possible errors (Armbian will not boot) when you are working on unverified models which used non-standard distribution of partitions in the eMMC. Therefore, be sure to back up the "ddbr" utility before running the scripts.
 
 

Information in this topic is very outdated see this topic.
 
 
 
 
 
 
The start system in Coreelec is not compatible with LibreELECE  Armbian  etc. If you run coreelec on your TV box, you will no longer be able to run LE and Armbian normally until the full recovery of the standard firmware via the USB Burn Tool and the new activation of the universal multi-boot, which is used in all new systems.
 
 
The new version 5.55 of images. In this version, images with a single DE (XFCE) and a server in composition are as close as possible to the official versions. Version with a Mate and Icewm will probably be later and the gathering will be from another branch GIT (specially adapted for this DE). Since now all the images will be collected using the main kernel "4.1 x", have a common structure for the entire line of s9xxx and differ significantly in steps when configuring the system, I open a separate topic for this direction.
 
 
https://yadi.sk/d/pHxaRAs-tZiei
 
https://mega.nz/#F!j9QSDQSQ!6WpasOlbZYIInfw6yo4phQ
 
The primary steps to capture an image, activate multi-boot, and select a dtb file are common with the previous images.
 
 
Please note that starting with the version number version 20180928.
Major change. A new algorithm for the use of the dtb. Starting with this version, you no longer need to copy the dtb files and rename it to "dtb.img." In order to specify which dtb file to use, you need to edit the file 'uEnv.ini" (specify the desired file name for use dtb). This is a plain text file and can be easily edited. This change will make it easy to update the kernel from the "deb" file in the future. The new algorithm is now used in the eMMC system installation script.
 
Be sure to activate multi-boot using the new image. If multiboot previously activated is required to repeat activation using files in a new image.
 
Pay attention. To use the system with
u-boot-2015 (regular firmware Android), you need to edit the file "uEnv.ini"
 
When using
u-boot-2018, you need to edit the file "/extlinux/extlinux.conf"
 
 
For those who doubt or do not know what u-boot is used, you can specify the desired name in both files at the same time.
 
 
To change the used MAC address.
 
1 options
You can add the required parameter to the startup files (uEnv.ini and extlinux.conf). To do this, at the end of the line with the launch parameters, you need to add a parameter specifying the desired MAC address.
For example,
mac=xx:xx:xx:xx:xx 
or
ethaddr=xx:xx:xx:xx:xx
 
 
 
Old info multiboot
 
https://sourceforge.net/p/amlogic-s9xxx/code/ci/master/tree/
 
add info
 
https://medium.com/@vysmol/how-to-install-ubuntu-on-s905w-and-simular-tv-boxes-ru-eng-7aca3e1011a5
 
 
Install Armbian to eMMC.
1. Be sure to activate multi-boot using the new image. If multiboot previously activated is required to repeat activation using files in a new image.
2. Run Armbian from external media, run "ddbr" and create full backup eMMC.
3.  install Armbian on eMMC execute script “/root/install.sh”.
 
Please note, this is a test installation, which was tested only on a few models. Possible errors (Armbian will not boot) when you are working on unverified models which used non-standard distribution of partitions in the eMMC. Therefore, be sure to back up the "ddbr" utility before running the scripts.
 
 

It is possible, but it will take time. Packages with HW used from Assembly ayufan, they need to modify and assemble with the new settings. I expect in the next version (to get one with Debian feature set) is not included by default, these packets from ayufan. For those who want to use them, you will need to perform a set of steps to install and configure them yourself.
 
I'll see what I can do. I do not give any guarantees (I do not have such equipment).
 
Did you check if any mmcblk0\1\2 appeared ?
 
You need to try the tools to extract the firmware file. Maybe then you can get the dtb.
 
 

Ver 5.64 (20181019)
 
For those who want to work on HW support on their own, there are two components on the site.
https://github.com/superna9999/meson_gx_mali_450
 
1. Module "mali.ko"
2. Archive with libMali.
The working version of xf86-video-armsoc is missing. I have a package (for Xenial) that gathered Numbqq (dev with Khadas), but the system does not accelerate and it needs to be corrected.
https://github.com/numbqq/xf86-video-armsoc_s905x/tree/master/xenial/arm64

Ver 5.64 (20181019)
 
For those who want to work on HW support on their own, there are two components on the site.
https://github.com/superna9999/meson_gx_mali_450
 
1. Module "mali.ko"
2. Archive with libMali.
The working version of xf86-video-armsoc is missing. I have a package (for Xenial) that gathered Numbqq (dev with Khadas), but the system does not accelerate and it needs to be corrected.
https://github.com/numbqq/xf86-video-armsoc_s905x/tree/master/xenial/arm64

New version 20181018 of the image with kernel 4.19 and fixed MPV config.

Add to the parameter string (in the file "uEnv.ini") parameter " mac=00:ac:3f:75:c0:ff"

In previous images, a strange error was found, so I updated the images to version 20181014.
Checked on MVR9, everything works. Added additional image with Ubuntu Bionic and built-in MPV with HW support. The video plays in full screen. For those who need to play full screen video from Youtube, I recommend To install SMPlayer and Smtube packages, configure Smplayer (in additional options to use MPV with options "--vo=gpu --gpu-context=drm --hwdec=rkmpp" )  and you will get Youtube video in full screen in Smtube.

Write in PM, I will explain in Russian.

In previous images, a strange error was found, so I updated the images to version 20181014.
Checked on MVR9, everything works. Added additional image with Ubuntu Bionic and built-in MPV with HW support. The video plays in full screen. For those who need to play full screen video from Youtube, I recommend To install SMPlayer and Smtube packages, configure Smplayer (in additional options to use MPV with options "--vo=gpu --gpu-context=drm --hwdec=rkmpp" )  and you will get Youtube video in full screen in Smtube.

New version 5.62 (20181012). It fixed shutdown\reboot on S912.
 
 
I do not understand the question, specify what you mean.
 
You can find some useful information in this discussion.
 
 
 
... and other developers have started working on similar projects ... 

What's the "new version"?
 
The version of the image ? The medium from which the system starts ? 1Gb of RAM is not enough for full-fledged work of graphic DE.
 
Odroid uses its kernel version for S905 (not X), it is not compatible with S905X\S912.
 
 

Depending on what tasks the device will be used for, you can use different combinations. For example, if you and your loved ones will use the device to watch videos more often , it is better to install LE in eMMC and run Linux from external media as required. By the way, the latest versions of Libreelec for Amlogic and RK3328 can be installed in parallel with the regular Android in the TV box (eMMC) and can use Libreelec and regular Android. With a strong desire (and certain skills), you can install multiple systems in eMMC together (Android+Libreelec+Linux, etc.).
 

https://forum.khadas.com/t/armbian-kodi-ubuntu-debian-for-sd-usb-emmc/825/258?u=balbes150
 
1. Clearly, in fact you have nothing to answer. You, the topic title, remember ?
2. I don't know what developers and what you're told, but a lot of users have been using Armbian+KODI with HW for a long time. And for those who need maximum possible, use a bunch Armbian+Librelec.
 I just stick to the discussion of the "Armbian+KODI" bundle, which exists (if I'm not confused) only for the Amlogic S905X. There is another option of Armbian+c2play image with HW full screen video playback for s912 assembled by pro777. And for reference, in the near future (I hope to find time for this) comes out Armbian+KODI for rk3328-tv.  Armbian+MPV version with full screen video for rk3328-tv is now available.
3. This question is directly related to this topic, as it directly affects the time of appearance of the version of Armbian+KODI with HW on the kernel 4.x for a number of promising platforms (Amlogic and Rockchip. And it depends on the feasibility of investing money.
 
1. I do not have a" favorite " chip, I try to choose the ones that are optimal for my tasks.
2. You are "a little" late with the advice to use "vanilla" Armbian. I have been developing Armbian for TV boxes and other devices for several years. And oddly enough, these works are in demand among many users. And among these works there is a variant of Armbian+KODI.
 
hhhhm .... either you do not understand these issues, or deliberately misleading ... start by reading the topics in the about TV boxes section. Perhaps then, you will discover the real situation with the launch of Armbian on TV boxes. And learn to read carefully :
 
p.s.
Judging by what you write, I see no reason to waste time answering.

Did I understand correctly that in order for RPI to work, you have to keep an additional device (NAS or server that provides a network resource to host the RPI working system) turned on ?
 
If you install LE or Linux on eMMC (you can use different systems, not only Armbian), you will have all USB ports and SD card slot free. But be careful when choosing, it is better not to rush and ask questions to real users with the proposed equipment. What versions of images and with what kernel they work, what features of iron can occur.
 
On S905X in Armbian (with the mainline kernel) can be enabled support for two levels of HW (which are needed for full-screen video playback in KODI or other programs built with this feature).
https://github.com/superna9999/meson_gx_mali_450/tree/DX910-SW-99002-r7p0-00rel1_meson_gx
 
1. Can you provide links to real images for H3 with Armbian + KODI where there is full HW support ?
2. Perhaps you are not aware already released versions of images of the LE with the kernel 4.18 and HW  for S905X.
3. Do you have a good idea of the difference between mali400p2 and mali450p5\T820\T860 ?
Recommend to study.
Yes, this is only the initial stage and will need time until everything goes into the finished product. But to recommend obviously outdated, incorrectly.
 
 
 
Summary is wrong. Let me tell you a secret, to use KODI with full HW in Armbian does not require many complex steps.  For those who are not in a hurry-it is enough not to wait much and soon there will be a ready solution.
 
To give that kind of money for a very weak iron in our time ....
 

If you did not violate the instructions and before installing the system in eMMC created a full backup (using the utility "ddbr"). You could easily go back to the old version.
I draw everyone's attention, before any experiments, be sure to create a backup.