balbes150

This is from the old 3.14 kernel, it will not fit the new 4.19 kernel

q201 = 100 MB network, I have no samples with such equipment, I do not know what is the reason. Try the kernel version 4.20 (Next), if the wired network works there, can find the reason for the kernel 4.19.2

Update ver 20181130 kernel 4.4 Add new ver Linux Next 20181130 kernel 4.20 (compiled from the official git Linux Next) on MVR9 HDMI USB SD card wired network works add test DTB rk3328-t9-android.dtb (for lan 100M)

For Russian-speaking users can exchange information in their native language. http://forum.puppyrus.org/index.php?board=177.0

Update ver 5.67 20181128 Update kernel 4.19.2 Update ver Next 20181128 kernel 4.20

1. Why did you erase the firmware of the eMMC. kvim#store init 3 2. Carefully read the instructions for launching Armbian. You did not follow the important step of the instruction, did not add the correct dtb. reading dtb.img ** Unable to read file dtb.img **

Good news. New image with kernel 4.20 for Khadas EDGE, which is built using the official git Linux Next. It has HDMI, USB, SD and wired network. Thus, it is a full-fledged basic system. hmmm Added version "4.19.0-dev", it is built using the source code "ayufan". Video playback in it significantly slows down compared to the version collected from the official sources of Next Linux.

This model has s905y chip in which there is no support for wired network. I will not support such models.

Updated the images 20181124 on a revised version. Added two images DE on kernel based 3.10.108. On versions of Debian XFCE, surprisingly, video up to 720p is played not ideal, but quite watchable.

You can try this option steps. You'll add a new empty branch (add readme.md) to git build, I'll be able to clone it, add my changes to the new branch, and send a merge request. Between the existing system of images for models without built-in memory (eMMC) and TV boxes, there is a fundamental difference in the principle of starting the system. I wouldn't want to break the existing system. For TV boxes do not need u-boot, they can use the standard u-boot, it is safe for users and much easier. Therefore, I propose separate branches, so they do not interfere with each other.

Good news. 1. I checked the latest images on the s805. Systems with kernel 3.10 start up and run normally, as in previous images, even without a universal multi-boot update. In the image with the kernel 3.10.33 there is a small error, there was no script to enable the screen (/boot/hdmi.sh) and there is no service to run it. It is easy to fix it-copy the necessary files from the previous version and enable the service. For version 3.10.108 you need to replace uInitrd from version 5.44. 2. The image with the kernel 4.20 works on s805, it is necessary to replace the name of the dtb file in the "uEnv.ini" to " meson8b_ec100.dtb". With this dtb file I have a wired network and can manage the system via SSH. HDMI does not work yet, but can have a full-fledged server with control over the network or UART. Everything you need to build your version for s805 is now in the new GIT Build-Armbian. All questions on the Assembly, you can ask in this thread.

Ver 20181123 Added options in the kernel for Aufs and Docker

The specified options are available in the current kernel for s9xxx. https://github.com/150balbes/Build-Armbian/blob/master/config/kernel/linux-aml-s9xxx-default.config#L770

The new version of images of 5.67 20181123. Kernel 3.10.33 (dev) 3.10.108 (default) 4.20 (next) Pay attention. Changed the algorithm for specifying dtb. Now it corresponds to the General method. Be sure to update the universal multi-boot using the latest images (5.67). To select the desired dtb, edit the first line in the file "uEnv.ini". Specify your version of the file name from the image or you can copy your version of the file to the media and enter its name. You no longer need to copy and rename anything. I didn't test these images.

@Igor I decided to go back to the question of integrating the build options for TV boxes into the overall git. Alternatively, at the first stage, you can make an additional branch (for example, "tv-box") and put all the code from my git "Build-Armbian/master" into it (with minimal fixes author, etc.). I am ready to support a set of basic images (which I am currently releasing) for a number of models that I have in stock (Khadas VIM\VIM2\EDGE , MVR9 etc). If there are other options - I am ready to discuss them.

Once again, turn on the TV box with external media with LE and select the normal shutdown from the LE menu. LE itself set the correct value.

The new version 20181122 . Added support for Wi-Fi.

Activation multi-boot (run the script aml_autoscript from SD card) is done only once. After that, you no longer need to use aml_autoscript until a new universal multi-boot option is available. This means you need to burn the last image to the SD card, activate the multi-boot from the SD card once. After that, write the images to the USB drive and start the system from USB. You no longer need to run the aml_autoscript script to USB.

Use quality media. Most of these problems are usually associated with poor media. Use USB media, they are slower but much more stable.

Pay attention. Now all test images with the 4.1 x kernel will be placed in the same directory where the images with the current version are located, subdirectory (5.67/image_date/NEXT_4.(xx). For example, these images are now in 5/57/20181118/NEXT_4.20)

In new versions, the algorithm for specifying the required DTB has changed. Now, all the images for the s9xxx and s8xx will use a unified mechanism for specifying a DTB. You need to change the first line in the file " uEnv.ini", specifying the name of the dtb file. If you need to use your file (which is not part of the image), you need to copy it to the media and edit the "uEnv.ini", specifying the full path and file name where you copied it.

For Xiaomi https://forum.xda-developers.com/android-stick--console-computers/amlogic/xiaomi-mi-box-3-mdz-16-ab-boot-log-uart-t3702010

ver 5.67 20181118

Now checked the latest version on Ubuntu 5.67 x96 mini to dtb (meson-gxl-s905x-khadas-vim.dtb). The system starts, the monitor works without problems. The start of the graphical shell takes about 1-2 minutes, no WiFi and BT. The remote control from Khadas VIM works in MPV (adjusts the sound, can rewind the video, etc.). The standard remote control from x96 mini does not work. Shutdown works correctly. After switching off, just press the button on the remote control and the system starts again.

Package with headers on the site.