balbes150

What is your exact Ubuntu or Debian system ?

Monitor output (HDMI) not working ? Reaction to keystrokes (for example, the Capslock key changes the state of the indicator) on a conventional keyboard connected via USB is (After starting Armbian and prompted to log) ? I see that runs u-boot assembled in Armbian from SD card. If you press and hold (do not release during u-boot) the space bar or enter key before turning on the power and after starting u-boot, is there a reaction ?

New image 5.77 kernel old 3.10 and test 5.0 (HDMI not work)

RK models use a different principle of running from external media. There is no multi-boot activation mode. That is, when you connect the SD card with the correct u-boot on the SD card, Armbian should start automatically. If you do not, then either the u-boot in your firmware is specifically blocked from running other systems, or the u-boot on the SD card does not fit your model. In this thread there are links and description to another variant of u-boot, see previous posts in this thread. If writing another version of u-boot to the SD card does not help, you will have to use the method of maskrom (contact closure on the Board to lock the regular u-boot in eMMC). The details are in the thread about the Z28 model on this forum.

CE can not work with universal multi-boot, so it breaks down the work of all other systems. To build a system with kernel 4, you can roll back to the previous commits in Build-Armbian and get a system with kernel 4 when you run the build.

Did I understand correctly that you are trying to run Armbian with Сoreelec installed in eMMC ?

Try the dtb file for trn9 (mvr9) it has 1000 network.

This is a guaranteed working model with 1000 wired network and DDR4. https://www.amazon.fr/TICTID-Touchpad-Bluetooth-Quad-Core-Cortex-A53/dp/B07GH12CRZ/ref=sr_1_6?__mk_fr_FR=ÅMÅŽÕÑ&keywords=TICTID&qid=1552449517&s=gateway&sr=8-6

Build your DTB option with your hardware included.

Perhaps the answer is in this quote. New Rock64 Revision 3 features include support for Power over Ethernet, a Real Time Clock, support for high-speed microSD cards, and improved PI2 GPIO compatibility.

In Android u-boot, some providers block the ability to stop startup. It would be interesting to see the UART log when trying to run Armbian from SD card. I am interested in whether the u-boot from eMMC is interrupted and control is transferred to u-boot from SD card or not.

Judging by the log, the system starts, but there is a problem with the quality of data reading from the SD card (maybe problems with the card or card reader on the TV box). Try to write an image on a USB flash drive and also to configure dtb. If multi-boot is activated, you can use any media SD card and USB flash drives. On TV boxes usually only two variants of wired network 100 and 1000 are used. Therefore, a wired network must work with one of the DTBS.

bootcmd=run storeboot This shows that multiboot is not enabled.

ls mmc 0:0 ls mmc 0:1 ext4ls mmc 1:0 ext4ls mmc 1:1 ext2ls mmc 1:0 ext2ls mmc 1:1 fatls mmc 1:0 fatls mmc 1:1

The script works with any media.

It should be. u-boot-2018 does not support USB Burn Tool (I warned all about this). Also, u-boot-2018 can not run external systems from USB media, you need to use only the SD card. You should only write u-boot-2018 to eMMC when you know exactly what you need it for. For other cases, you need to use the installation with the preservation of the standard u-boot-2015 (use the installation script install.sh). To make USB Burn Tool work you need to erase u-boot-2018 in eMMC. For example to run the command "dd if=/dev/zero of=/dev/mmcblkX bs=1M count=4M" (Replace X with the number of your eMMC).

1. Show the printenv output. 2. Judging by the log u-boot you have not activated multiload, so there are no attempts to run the script s805_autoscript. 3. What you copied from the firmware is not a DTB file. And you can't use it directly.

Show the output of the command help and command ls mmc 1:0 ls mmc 1:1

IMHO. The problem with the video may be from overheating.

Are you sure you are using dtb q201 ? Judging by this infa, you use dtb from Khadas VIM2. [ 11.798739] brcmfmac mmc2:0001:1: Direct firmware load for brcm/brcmfmac43455-sdio.khadas,vim2.txt failed with error -2

I checked the launch on the Tronsmart Vega S95 Telos (s905). Everything works. BT, wired network and sound. After adding these files to the directory "/lib/firmware/brcm" , Wifi began to work. https://yadi.sk/d/si381PghmHbRsQ On Khadas VIM1 (s905x) with the correct dtb (use default to image) also all works. BT Wi-Fi wired network audio. Checked x96mini (s905w) 2\16. Used dtb p281 from the image. Everything starts normally and works with USB flash drives. Works wired network and sound. BT and WiFi chip ssw6051 will not work (the manufacturer has not provided the driver and disappeared).

New image LE and Armbian 5.77 kernel 4.4 and next (5.1.0-rc1) 20190321

I feel like in normal mini PC mode, RK3399 is faster than s912. IMHO the Real price for normal RK3399 will be around 90-130. If you have the ability, and you are not only a regular user, but also carries out the development (you version of the kernel or u-boot, etc.), I would recommend the option Khadas EDGE-V. This device can be ordered immediately with a good cooling system (radiator+ fan) and the case. In addition, EDGE-V has a number of important features that do not have TV boxes and that significantly help in the development and any experiments with the device.

RK3399 is significantly more powerful than RK3328. In normal mini PC mode it shows very good results (I rate it as a real replacement for a regular PC with i3-i5). XFCE desktop works without problems at 4K resolution (4096*2016). Even without the inclusion of HW he easily copes with full screen video at a resolution desktop 1080. In addition to it there is a media script that includes HW and then any video at the resolution of the desktop 4K works without problems on the entire screen. But it is important to understand - for the implementation of all the power is necessary TO have a good cooling (to alter the body and add a fan). Only then can all these results be obtained. By the way, Libreelec also works fine on rk3399 and shows very good results (for N6 I added the correct DTB to the Lebreelec images works WiFi, BT, remote control and wired network).

If you have a task to add support for the remote control in Libreelec, see these patches. They add support for the MX10, MVR9, Magicsee N6 max remotes. https://github.com/150balbes/LibreELEC.tv/blob/Amlogic-Leia-4.x/projects/Rockchip/patches/linux/rockchip-4.4/linux-9000-box-trn9-rc-24k-dts.patch#L147 https://github.com/150balbes/LibreELEC.tv/blob/Amlogic-Leia-4.x/projects/Rockchip/patches/linux/rockchip-4.4/mvr9_ir_remote.patch https://github.com/150balbes/LibreELEC.tv/tree/Amlogic-Leia-4.x/projects/Rockchip/patches/linux/rockchip-4.4 p.s. By the way, Armbian runs normally and works on Magicsee N6 max (rk3399),