after successful install i got stuck in a boot loop. no matter what dtb is configured.
but thanks anyway. i appreciate your work!
Write in detail, all the steps that you did.
Has anyone got the new images working on a u9?. I tried the meson-gxm-q200.dtb and it goes from the Minix logo to just screen noise.
You should check all DTBS for your group (gxm).
FDT /rk3328-box-trn9.dtb
APPEND boot=UUID=0409-3836 disk=UUID=ad8750dd-cd77-41ea-bc60-fc0cefb36c32 quiet console=tty0 bluetooth
These are clearly not my images. I use a different logic. Show the exact name of the LE image and where you download it from.
Will the new version work on beelink gt1 ultimate 3gb ddr4 / 32gb emmc? (Leia-18/kernel_4.x/20190114)
and if yes, which dtb i have to use?
Should work on s912, what dtb to use - you need to check in practice, I do not have such a model.
If this isn't realistic with this SOC then perhaps I should indeed go for RK3328 or a different alternative.
Passive cooling really have any hardware (all Rk3399 rk3328 etc). The main thing is to perform it correctly. Metal body can help with this. But it should be borne in mind that under certain conditions (maximum load on the system and high ambient temperature) passive cooling can not cope with heat dissipation. By the way, even in this metal case, the engineers made a mistake - there is an air outlet on the sides of the body, but there are no holes for air supply to the body. It as in a task for school students about the pool where there are two pipes - on one water flows into the pool, and on another follows. In this case, made only one " pipe "to flow, but there is no" pipe " to enter the air into the body. Therefore, the side holes will only work if you put the case vertically sideways (from the bottom of the entry hole, from the top to the exit). I had to make holes for the air inlet on the rear side , and the output to make the top cover in the area of the radiator. Then passive cooling will work better directly from the radiator. This is more efficient than transferring heat from the radiator to the body and only then to the environment.
Tried again, started your build, started emmc backup in le settings, waited for 50 min. nothing happened no backup file in /storage/backup and no reboot.
What firmware do you currently have in eMMC ? Which dtb is specified in the file " extlinux.conf"? Can you connect to MVR9 via SSH ?
Did not know GUI Libreelec Setting had this feature
This mode is still only in my images. If the LE developer community decides to adopt this add-on, then it will be in all LE images.
PD: Offtopic - Do you know where can i find more info about how eMMC works? i mean, i tried to mount eMMC on /mnt from the sd LE install but only see the first partition. And i know there are 6 more partitions (how this filesystem works?) how should i mount the rootfs partition (i guess is the 7)
If you have a regular Android firmware, there is no partition table and you need to use a direct reference to "/dev/system" "/dev/data" for mounting, etc.
After click on backup I waited for at least 5 minutes but there was no shot down.
I strongly recommend that you run a full backup of the entire eMMC. It will not be fast (about 20-30 minutes), but you will be able to return the exact state in the eMMC, which will be at the time of creation of the copy.
Will there be newer versions for the S812 processor.
I hope that there will be. It takes time to fix the errors that I have when building new images for S812.
I think, that need create a new subject for models s812\805. Because this topic was discussed in the version for the S9xxx. Infa about s8xxx confuses them (it is absolutely different versions).
The new version of the images for the S9xxx 20190114. Pay attention. The names of the images have now changed to refer to the whole group for which these images are suitable S905 (S905 S905X S905D S905W) S912 (S912). All previous images were also universal, but apparently many users were confused by the use of a specific model name (Khadas_VIM\VIM2). So I changed the name of the images to universal. The principle of use has not changed. To select the desired dtb, edit the file "uEnv.ini "(or " extlinux.conf" for those who switched to using the new u-boot-2018).
The choice of model depends on what video you want to watch and on what TV. For example, if you have a FullHD TV (not 4K) and you're going to watch options up to 1080p inclusive, and you don't plan to change TV in the next 1-2 years, If you plan to use only LE optimal rk3328 (ARMv8). IMHO I would not begin to spend now money for the outdated model ARMv7 (armhf) rk3288 and similar.
The use of RK3399 is justified if you want maximum performance on Linux (when running other systems in addition to LE), or if you want the maximum performance of graphics subsystem (T860). Note, for full use RK3399 (to use all its power and performance) need a very good cooling system. A sealed plastic case is a bad decision no matter what radiator you install there. Try it yourself, wear a sealed coat and in the summer heat to go running in it on the street. Buy RK3399 and use its features, only 20-30% is not reasonable.
I looked at my image of Khadas EDGE rk3399. It turns out it already has a dtb for rock960. To run on Rock960 just edit the file " extlinux.conf" (change the name of the dtb used). Also in the composition there are a few more DTB. For those who want to try running this version on RK3399-you can take turns trying all these files.
Sorry, can you explain how does this work?
I have a nanopc-t4 with rk3399 soc.
Installed dtb file from rockpro64 and now i can use wireless, bluetooth and can see emmc as mmcblk1 but not able to mount mmcblk1p1 (previously i installed armbian inside emmc and it's suposed to have an ext4 filesystem).
are you saying is there a kodi addon able to do the emmc installation?
Did I understand correctly that you were able to run the LE image for EDGE on your T4 model ?
You want to install LE in the eMMC ? To do this, the GUI Libreelec Settings has a special menu for installation in eMMC, to create and restore a full backup.
downloaded LibreELEC-RK3328.aarch64-9.1-devel-20190110144513-79c10ab-box-trn9.img
This image is for all rk3328. What model are you trying to run it on ?
I also tried your latest le build on my mvr9 box. I see Emmc in le settings but when I select full backup and reboot nothing happens. Same with install to emmc.
After you run to create a copy, you need to wait for the system to shut down. After that, you run the LE again from the SD card and select "install to emmc" . The system will install and shut down. Pull out the SD card and turn on the power. If everything went correctly, start LE from eMMC.
Sorry but i cant find any information about the installation from libreelec on the internal emmc of my ROCK960.
I have installed and booted the image from the sd card at the moment.
If you want, you can try to check how the installation will work on your model in eMMC. All my images are universal, just add your dtb to dir /dtb (it can be copied from the current LE image you are using now) to the SD card and edit the file "/extlinux/extlinux.conf" (specify in it which dtb to use). After that, try running LE from a prepared SD card, if everything works, you can run the EMMC installation from KODI. There is a special menu Libreelec Settings. Before installing to eMMC, I strongly recommend that you run a full backup of the entire eMMC. It will not be fast (about 20-30 minutes), but you will be able to return the exact state in the eMMC, which will be at the time of creation of the copy.
The new version Libreelec (20190108) on the basis of the kernel of 4.19 works with HW at S912.
It's not all ready yet, but it's working. Tested on VIM2 Basic (everything works except BT), WiFi\BT does not work On VIM2 Pro\Max. On Tronsmart Vega S96 with DTB VIM2 works from remote but not working wired network (and of course WiFi\BT), with native dtb Vega S96 wired network works , but no remote control (I hope soon finished dtb for Vega S96, something was wired network and remote control). All models rotate video up to 4K inclusive, KODI interface has small glitches, but works without brakes. So that can be considered these images sustainable alpha. By the way, ran on all TV boxes with a simple USB flash drive.
i coping file boot.ini in storage boot libreelec
i edit name dtb wetek play 2 in file uEnv.ini ( dtb_name=/dtb/meson-gxbb-wetek-play2.dtb )
Check that the file name is correct and its presence. The log shows that the DTB file is not loaded.
reading /dtb/meson-gxbb-wetek-play2.dtb
** Unable to read file /dtb/meson-gxbb-wetek-play2.dtb
Ver 20181228 (kernel 4.19)
Ver Khadas_KVIM tested
S905 - Tronsmart Vega S95 Telos (dtb gxbb_wetek_play2)
S905X Khadas VIM1 (dtb gxl_s905x_khadas_vim)
S905W x96mini (dtb s905w_tanix_t3)
Ver Khadas_KVIM2 tested
s912 Khadas VIM2 (dtb gxm_khadas_vim2)
On the S912 version, the interface is not fully ready yet, there are no labels, but video playback works.
Additional information. To use your remote control, you can place the settings file in the directory "/storage/.config/rc_keymaps/" named "remote-ir.conf." By default, the image has several files for several TV box models (by default, the settings file for Khadas VIM\VIM2 is used).
For those who want that, would file for his model immediately included in the composition of the images, you need to give me your version of the configuration file with the model name of the TV box.
from 8.2.3 LibreELEC release. But I think dtb is not the problem. I think the problem is that the newer "boot configuration" files don't work on my box. If I try to boot any LibreELEC release lower than 9, it boots. But 9 release and ARMbian that uses the same "boot system", don't boot.
If you are running an older version of the 3.14 kernel and the newer version is not running, it means that either you are not following the instructions to run the newer versions correctly, or the newer versions of the DTB are not suitable for your model.
After read some topic I think that my version of LibreELEC (8.2) can't use Netflix I need to do an upgrade. What file I need to download and where I need to put it?
Where run LE (SD, USB, eMMC) ?
(maybe try arm build first)
For Netflix - only arm (not aarch64).
The new version 20181224_LIMA. This image is universal for s905 and S905X models. To select the desired dtb you need to edit the file " uEnv.ini". Please note that for the correct operation of LE when installing in eMMC, it is necessary to update the universal multi-download using the files included in the new image. Another change. Menu items are now "Install to eMMC" and "Backup eMMC" "Restore eMMC" to full backup in a separate partition (Libreelec settings \ eMMC). Running this image has been tested on several s905x and S905 (p201) models. Those who will test this image on s905 (not X) models are requested to write the results, indicating the exact model and version of the DTB file used.
My question is asking if we can directly obtain an LE .image running in eMMC with all the new configuration settings and add-ons that a user has spent time with. This is better than getting a fresh stock LE image and then restoring all your settings/add-ons to it separately- backing up the updated .img directly from eMMC is a one step process.
You want when installed in eMMC, at the same time to move the settings that are made while the system is running from external media ?
Is there a solution to my p282 board problem or should I just return the boxes for a refund?
Have you tried all the dtb for the "gxl" series (s905x s905d s905w etc) ?
I wish I could say the same!..
..my problem with tx3mini 2/16 is that on all 4.xx-Versions I got no sound because my monitor has no speakers, so sound just delivered over hdmi is absolutely useless for me. I mostly use on these s905w boxes(got 3 of em) av-port with a 3.5mm to cinch cable connected to old '80s analogue stereo Amps and huge PA-speakers(2x15"+ 18" subs..) , also a usb-soundcard(which works with all armbian or 3.xx-LE-Versions perfect but also needs one of the precious two usb-ports, which I block on LE-Box with mini-keyboard and HDD for Music & Videos already) isn't recognized on the newer 4.xx LE-builds I tested. It seems if there is no solution to get the av-out working, I have to stay on 3.xx Kernel on the LE box, because neither a new Amp nor a new TV/Monitor are an option..
The core in Armbian is the same as in LE, the only difference is in the configuration. Therefore, chewitt can easily add the necessary support for USB audio devices (enough to make a diff config Armbian and LE). 
Important information.
New images and update 20181217 for kernel 3.14 with the current time are the latest. I stopped producing images for LE S9xxx using kernel 3.14. I'm freezing a branch in my GIT soon, which is used to build version s9xxx with kernel 3.14.
For all future versions, I plan to use the new kernel. "4.xx"
