balbes150

If you are using My armbian image, you need to use other steps (commands) to install your kernel (according to the rules used by the s905_autoscript system startup script). 1. The correct name and location of the kernel file (/boot/zImage) 2. The Initrd file must be processed by mkinitrd.

Have you tried changing the default resolution from 1080 to 720 ?

I think it's solved. Try to compare the packages with a working version of Jessi or Ubuntu, maybe you'll find what packages are missing in the new version.

I checked the remote on the latest version of Mate 3.14.29 (20180205). It works. Perhaps Debian changed\no used to do packages.

A corrected version kernel 3.14.29 of the images with mali-6 20180205. Fixed KODI in HW mode.

In images with kernel 4.9.40 is no support for s905. These images can only run on s905X and S912 (s912 KODI does not work). To work remote need to verify the composition of packages and kernel configuration (I hope to test it next week).

Image update 20180204 kernel 3.14.29 and 4.9.40. Added version of the images with mali-6 (Ubuntu Mate and Debian XFCE). In these images uses a new library libMali r6p3. These images are in the directory mali-6 on the website. In the directory mali-5 are all old images 20180203 (server and desktop variants). Added to the website version of the images with the kernel 4.9.40 a working version of KODI. Pay attention to the images 20180204 c kernel 4.9.40 Mate and XFCE desktops contain a version of KODI 17.3, which can work on models with S905X. Important. The image with the kernel 4.9.40 to run KODI, you need to log on desktop (which would have been on MATE or XFCE) and from it (via the menu) to launch KODI. Only in this mode will work the sound in KODI. When you exit KODI the screen will remain blank (black), for the appearance of the desktop you need to switch to another console with CTRL+ALT+F1 and go back to your desktop CTRL+ALT+F7.

A little surprise to Chinese New Year holiday. Image update 20180203.

Gathered from the latest commit image stretch 4.9.40. Recorded on the USB flash drive, added the dtb (kvim2_multios.dtb). Has launched on the VIM2 Max. Connected only to a wired network, a USB flash drive with the system and USB power. Joined VIM2 via SSH from the PC and performed the initial configuration. After a reboot everything works. Try to run this image. Maybe when you build something made not so. https://yadi.sk/d/5zSm31vQ3S3ijn

There are General guidelines, they are suitable for all versions Armbian for TV boxes (S8xxx and S9xxx).

update

Here was discussed a similar question (to increase the memory by turning off the redundant memory). http://forum.khadas.com/

1. Try to pick the correct dtb file. It depends on the work wired network. 2. What did you change in the file "armbian.txt" ? 3. H3 has nothing to do with the TV boxes with S905X.

This issue has already been discussed, it is possible but would require a large amount of manual operations (installing all the required packages, configure them, etc.).

On the Internet there are instructions on how to configure BT. You can try different options to find the cause. May need to try different dtb.

Strange WiFi chip. I haven't found information about it freely available. For cooling fans. Then should be enough for this radiator.

Try to replace the directory /lib/firmware (copy it from the old version to the new one).

Wait for the nearest update GIT. It will be added a new version with the kernel 4.9.40 for the VIM2. I will write the steps that you will need to perform to build such an option.

Try to record on USB image LE. Add correct dtb (to try all that apply). Connect USB media to TV box and check how the system's going to start. To activate the multi-boot is NOT necessary (it is already activated). To execute the commands in the UART is NOT needed (everything has to start automatically). By the way, it is possible that your friend recorded in a TV box is not the correct u-boot and it's not gxbb_p201. Need to try other options gxbb*.

What kernel chooses when building image ? Which version of the image ? What dtb are using to run ?

I understand that this TV box may not start with any systems, including those with Android ?

The startup script works correctly and the kernel starts, but no data correct dtb to the kernel. The reason is not the correct dtb file. Pick the right option dtb file.

You need a version q201_2g Judging by the log , you don't have a file dtb.img in the root of the first partition (FAT). Add in the root the correct dtb (it means to copy from /dtb to the root of the file, and rename it to "dtb.img").