1 hour ago, balbes150 said:

Try to set configuration file /boot/hdmi.sh  or /boot/amlogics905x_init.sh  value instead "mode=720p"   to  "mode=1080i59Hz"

not working(((

7 hours ago, balbes150 said:

You need to compare what is written in the normal dtb and put it in the new to check.

sorry but your meson8m2_n200_2gb.dtb hasnt any led infos. i search google for android and other m8s dtb/dts but also no led infos inside this files .  i found only this info about led config

https://lists.freebsd.org/pipermail/freebsd-arm/2015-February/010126.html

there is a info about gpio ao 13 , how i write this to the dts ( is red right or blue ?) or maybe complet wrong. Maybe LED dont control by GPIO only by power state ?

 

        red_led_gpio = "GPIOAO_13";
        blue_led_gpio = <0x13>;  (or 0xc8100024 )

You have the source code from the regular dtb (used in firmware) ?

2 hours ago, balbes150 said:

You have the source code from the regular dtb (used in firmware) ?

no i do not have  extract the dtb from the android that is on the box

Uploaded the new version of the initialization script monitor (hdmi.sh) with support of resolution 1080. To use simply replace the script in the image to a new version. Please try in both modes (720 and 1080). For use on older images you need to rename amlogics905x_init.sh or change the call line in /etc/rc.local .

 

https://yadi.sk/d/L-F3RlhX3JYtif

18 hours ago, balbes150 said:

Uploaded the new version of the initialization script monitor (hdmi.sh) with support of resolution 1080. To use simply replace the script in the image to a new version. Please try in both modes (720 and 1080). For use on older images you need to rename amlogics905x_init.sh or change the call line in /etc/rc.local .

 

https://yadi.sk/d/L-F3RlhX3JYtif

Does not work(((  "Armbian_5.27_S812_Ubuntu_xenial_3.10.99_server_20170526"

armbian31099.log

 

 

And "Armbian_5.24_Vegas812_Ubuntu_xenial_3.10.99_desktop_20170113" works !

_armbian31099.log

 

 

What dtb are used ?

meson8m2_n200_m8s_plus.dtb

1 hour ago, wzor said:

Armbian_5.24_Vegas812_Ubuntu_xenial_3.10.99_desktop_20170113

What dtb are used ?

yes. no problem!

The name of the dtb file that you would use in 20170113 ?

 

In the image 20170526 have you tried all the dtb files that are in the directory /dtb ?

meson8m2_n200_m8s_plus.log

meson8m2_n200C_2G.log

meson8m2_n200_m8s.log

meson8m2_n200_2G.dtb.log

Spoiler

Какой dtb файл (имя) используется в версии 20170113 ?

 

Spoiler

 имя meson8m2_n200_m8s_plus переименовыл в dts.img.

 

All files means - all the files including meson8_k200.

meson8_k200b_2G_emmc_sdhc.log

Try this version of the dtb file with 20170526.

 

https://yadi.sk/d/5Yujtmen3Ja535

No load(((

 

meson8m2_n200_2G_M8SPlus.log

 

The problem is not dtb files. The problem in the kernel.

Try this file. The reason is not in the kernel. The reason for the dtb. Need to choose the parameters.

https://yadi.sk/d/dnGiOmKV3Ja6pi

(((

 

meson8m2_n200_2G_MXIIIPlus.log

update dtb meson8m2_n200_m8s_plus

https://yadi.sk/d/qm-o7QH03JWPEg

Does not work

 

meson8m2_n200_m8s_plus(1).log

Spoiler

Перезалил файл, пробуй. На сегодня - всё, вариантов пока нет.

 

Spoiler

Заработал но на полоску вверху экрана! Разрешение меня 720 и 1080, полоска только уже становится.

 

 

meson8m2_n200_m8s_plus(2).log

Spoiler

Если знаком с утилитой dtc , распакуй этот dtb и пробуй сравить параеметры из meson8m2_n200_2G и постепенно подбирать, а потом упаковать.

 

Spoiler

распаковал но что там менять, и главное на что((((

Почему в январском образе прекрасно работало с моим дтб? Только с сетью проблемы и сервис хостнаме не подгружались.

 

PS.

Решил с разрешением, заменил hdmi.sh на старый vegas805_init.sh и все заработало!!!!

СПАСИБО ЗА ВАШЕ ВНИМАНИЕ И ПОМОЩЬ!!!!!!

 

Осталось несколько ошибок.

1. Failed to start Hostname service.

2. Failed to start Network Manager Wain online

 

и что за ошибка "

[   50.294613@0] CONFIG-ERROR) dhd_conf_set_mimo_bw_cap: mimo_bw_cap setting failed -23

 

"

 

 

1 hour ago, wzor said:

1. Failed to start Hostname service.

If linux-vegas812-default.config is the kernel config for this board/SoC, then it's missing CONFIG_NAMESPACES (and all namespaces inside the submenu) and some CONFIG_CGROUP_* options which may prevent some services from starting.

15 hours ago, zador.blood.stained said:

then it's missing CONFIG_NAMESPACES (and all namespaces inside the submenu)

Adding this option to the config, causes a build error in the kernel.

I normally compiled.

Show the config.

 

 

Found why I gave the error (used the experimental source in which a lot changed).

Edited May 28, 20179 yr by balbes150