Closed lx7741 closed 2 years ago
My x96maxplus 4+64 has also been used for a year. But some 2+16 devices can't. I asked flippy to adjust it according to the normal security partition.
@ophub Do you got the issue that sometimes the X96 max plus (4+64) stop working because of Kernel panic as below?
There was a kernel like this a month ago, just upgrade to the latest kernel.
armbian-update
The final result is out. I downloaded the original Android 2/16 firmware from the Internet today, and started armbian with a U disk. 2GB of RAM is back, and also 2GB when writing to emmc. It can be seen that the correct Android original system is very important, and there will be many problems if you flash the wrong original firmware! finish the flower
@luoluo888 have you got success with 5.15? As I understand, here are steps you already used, right?
63:X96 Max+ 100Mb:s905x3:meson-sm1-sei610.dtb:u-boot-x96maxplus.bin:NA:NA:4C@2100Mhz,2GB+16GB,100M Nic
Thank you.
The final result is out. I downloaded the original Android 2/16 firmware from the Internet today, and started armbian with a U disk. 2GB of RAM is back, and also 2GB when writing to emmc. It can be seen that the correct Android original system is very important, and there will be many problems if you flash the wrong original firmware! finish the flower
@luoluo888 have you got success with 5.15? As I understand, here are steps you already used, right?
- Restore original Android
- Change the dtb file in uEnv.txt to use
- Use the following option to install armbian to eMMC:
63:X96 Max+ 100Mb:s905x3:meson-sm1-sei610.dtb:u-boot-x96maxplus.bin:NA:NA:4C@2100Mhz,2GB+16GB,100M Nic
Thank you.
BM838_141 V1.0 21022 2+16+W1
BM838_141 V1.0 21022 2+16+W1
so you got success with both 5.4 & 5.15 kernel, right?
BM838_141 V1.0 21022 2+16+W1
so you got success with both 5.4 & 5.15 kernel, right?
5.4 is right. 5.15 has not been tested yet。First, you should be able to enter the system from SD / USB, and then brush armbian install into EMMC. If you can't access the system, you can try install-to-emmc.sh
5.4 is right. 5.15 has not been tested yet。First, you should be able to enter the system from SD / USB, and then brush armbian install into EMMC. If you can't access the system, you can try install-to-emmc.sh
I also got success with 5.4. Now, I'm trying with 5.15 but not success when boot from eMMC. If you have time, please try 5.15. Thank you.
Ok, no problem
@ophub @luoluo888 Sometimes, I got the following error once reboot 5.4 from eMMC and unable to boot again.
Once I got this error, I must restore Android TV stock firmware and install Armbian 5.4 from USB again.
5.4 is right. 5.15 has not been tested yet。First, you should be able to enter the system from SD / USB, and then brush armbian install into EMMC. If you can't access the system, you can try install-to-emmc.sh
I also got success with 5.4. Now, I'm trying with 5.15 but not success when boot from eMMC. If you have time, please try 5.15. Thank you.
Hi. I've tried various methods these days. Version 5.15 only brushes meson-sm1-x96-air-100.dtb and u-boot-x96maxplus.bin, black screen cannot be started. If you brush meson-sm1-x96-air-100,dtb,u-boot-x96maxplus.bin and /usr/lib/u-boot/x96maxplus-u-boot bin.sd.bin, can be started, but the wired network card has no driver
Hi. I've tried various methods these days. Version 5.15 only brushes meson-sm1-x96-air-100.dtb and u-boot-x96maxplus.bin, black screen cannot be started. If you brush meson-sm1-x96-air-100,dtb,u-boot-x96maxplus.bin and /usr/lib/u-boot/x96maxplus-u-boot bin.sd.bin, can be started, but the wired network card has no driver
@ophub @luoluo888 Have you tried to test the stability of this box with 5.4? I tried to test by add the reboot command to the crontab to reboot the armbian every 5 mintues and after 5-10times, it is unable to start again. Then must unplug the power and plug the power again to make it work.
I tested the flow above with 2 X96 max + box (2+16G, 100Mb).
Hi. I've tried various methods these days. Version 5.15 only brushes meson-sm1-x96-air-100.dtb and u-boot-x96maxplus.bin, black screen cannot be started. If you brush meson-sm1-x96-air-100,dtb,u-boot-x96maxplus.bin and /usr/lib/u-boot/x96maxplus-u-boot bin.sd.bin, can be started, but the wired network card has no driver
@ophub @luoluo888 Have you tried to test the stability of this box with 5.4? I tried to test by add the reboot command to the crontab to reboot the armbian every 5 mintues and after 5-10times, it is unable to start again. Then must unplug the power and plug the power again to make it work.
I tested the flow above with 2 X96 max + box (2+16G, 100Mb).
I tested it, and 5.4 does have this problem. I changed the DTB in /boot/uenv.txt to meson-sm1-sei610.dtb。 Add /usr /sbin/reboot to crontab
I tested it, and 5.4 does have this problem. I changed the DTB in /boot/uenv.txt to meson-sm1-sei610.dtb。 Add /usr /sbin/reboot to crontab
It seems this issue related to the reboot command in armbian only. I've tested the reboot by several cycles of unplug the power and plug the power again and it still boot well.
@lx7741 @dinhchinh82 @luoluo888
https://github.com/ophub/amlogic-s9xxx-armbian/commit/fdbbec5d484f903dd7ab99660a51a565be6d1995
59:X96 Air 1Gb:s905x3:meson-sm1-x96-air-gbit.dtb:u-boot-x96maxplus.bin:NA:NA:4C@2100Mhz,2GB Mem,1Gb Nic,Wifi
60:X96 Air 100Mb:s905x3:meson-sm1-x96-air.dtb:u-boot-x96maxplus.bin:NA:NA:4C@2100Mhz,2GB Mem,100M Nic,Wifi
我看了下上游f大的内核源码,现在这2个dtb改名了,我更正了下,你方便的时候测试下。
@lx7741 @dinhchinh82 @luoluo888
59:X96 Air 1Gb:s905x3:meson-sm1-x96-air-gbit.dtb:u-boot-x96maxplus.bin:NA:NA:4C@2100Mhz,2GB Mem,1Gb Nic,Wifi 60:X96 Air 100Mb:s905x3:meson-sm1-x96-air.dtb:u-boot-x96maxplus.bin:NA:NA:4C@2100Mhz,2GB Mem,100M Nic,Wifi
我看了下上游f大的内核源码,现在这2个dtb改名了,我更正了下,你方便的时候测试下。
好的,没问题
我使用x96 air的dtb-100可以跑起来,但是一直报rtl871x错误。 使用x96 max+刷入emmc无法启动。