balbes150

New version 5.77 (20190318). Updated kernel to 5.0.2. Fixed a bug with the overflow log.

use commit https://github.com/150balbes/Build-Armbian/commit/2ec509ae341cdd8508a2ca245ee861dafa276f54 to all New image 5.77

Someone left image version 5.67 from 20181203 ?

Have you tried the latest version of the image with the kernel 5 ?

IMHO the branch "next" should use the primary sources, branch NEXT Linux with minimal patches. The "dev" branch can use any kernel sources, any patches for the kernel and dtb. In this case, you will know exactly in what state the support for specific processors in the main core is and work on patches to be sent to the main core. After all, the main task is to get full support in the main kernel by default (without additional patches in Armbian itself, except for the patch to build DEB packages).

If the system does not start automatically in DE. There are only two reasons - bad media (Sd card, card reader, badly recorded image, etc.) or wrong DTB.

This package is built for AMD (x86_64) and cannot be used on the ARM platform .

What do you mean can't install ? Write in detail what you do and what messages you receive from the system. https://docs.armbian.com/

Take the dtb and make the necessary changes.

Your firmware does not have a compatible kernel version.

The new versions have changed the algorithm of using dtb and the system startup script itself.

Update image 5.76 kernel 3.10

New image 5.76 kernel 4.4 and next (5.0.0) 20190307

Copy the dtb, kernel and modules (and possibly startup scripts) to the desired image and use.

Alpine Linux for S9xxx https://forum.khadas.com/t/alpine-linux-for-amlogic-s9xxx/3040

Now RPI strongly loses in all respects to s9xxx and rk33xx TV boxes. The only place where the use of RPI is justified, systems that use a variety of external sensors and actuators, of which a large number are produced and there are ready-made systems for their use. LE did not use patches, but a ready-made closed binary module (driver), which was taken from the finished Android firmware. This binary module was built exclusively for one version of the 3.14 kernel and cannot work with any other versions of the kernel. The manufacturer of the chip does not give anyone the source code from this driver, so no one will spend their time disassembling the binary code and studying it to write a new driver for the kernel 4\5. If you want, you can do the job yourself.

New images 5.76 201903306. The files are in the same location as the previous version. Slightly updated kernel.

With the installation process on S805 with the new images a lot is unclear, so I disabled the script. You can (at your own risk) do the installation yourself, but there is no guarantee that it will work.

Do I understand correctly that after running the system Armbian you are running the SATA port and you can work with disks connected to it ?

fix

The new version of the image with the kernel 5.76 5-rc8. Please note that the image files have replaced the previous versions of the files on the site. The new kernel adds support for BT on VIM2 (S912), but the BT audio output does not work yet (the sound stutters, you need to change the settings and perhaps the firmware file). Also fixed DTB files for Vega S95 (s905). Tested on Tronsmart Vega S95 Telos. The system starts normally and works with external media (wired network, sound, BT).

No, images from this theme will not work. You have a model with rk32xx , it is not aarch64. See the topic about rk32xx.

kernel 4

If you have NAND, you will not be able to install new versions with kernel 4 and 5 in NAND. These kernels only work with eMMC.

Show the whole output when you run the script "/root/install.sh".