63 63
balbes150

ARMBIAN for Amlogic S905 and S905X (ver 5.44 =<)

Recommended Posts

On 10/20/2018 at 11:40 AM, KY69 said:

Tanix TX3 mini 2GB RAM (S905W)

5.41.1 Ubuntu Xenial 3.14.29 icewm 20180406: everything working, boot from SD, system on HDD

 

A5X Max 4GB RAM (RK3328)

5.62 Ubuntu Bionic 4.4.143 desktop 20181014: rk3328-evb.dtb, boot from SD, system on HDD, just started testing, wifi and audio not working yet, ethernet okay.

 

Please, can you link the armbian img that you use?

I can't find 5.41.1 Ubuntu Xenial 3.14.29.

Thanks.

Share this post


Link to post
Share on other sites
2 hours ago, balbes150 said:

 

Learn how to use search, this issue has been discussed many times.

 

 

 

hi is me again i have search in THIS topic and finished setup pass information it showing "Reboot the system as soon as possible" im reboot and it showing again , i did is 10 TIME before im come here for help , im using the lastest ver with dtb meson-gxm-khadas-vim2 thanks !

does sdcard size matter cause i have 2 one is 2gb and 4gb i tried 2 of them !

Share this post


Link to post
Share on other sites
20 hours ago, BuiHuy said:

hi is me again i have search in THIS topic and finished setup pass information it showing "Reboot the system as soon as possible" im reboot and it showing again , i did is 10 TIME before im come here for help , im using the lastest ver with dtb meson-gxm-khadas-vim2 thanks !

does sdcard size matter cause i have 2 one is 2gb and 4gb i tried 2 of them !

I think 4gig is just a little too small, I would use at least 8 gig.

Share this post


Link to post
Share on other sites

Is the rtl8723bs combo wlan/bluethoot chip supported in the latest release (Armbian_5.67_Aml-s9xxx_Ubuntu_bionic_default_4.19.6_desktop_20181207)?

As for me only the wlan component is working on my Mnini M8S. It looks like the bluetooth hardware isn't recognised at all.

 

I'm thinking my problem could be related either to the chip's driver or my problem with dtb.img during installation. I've tried to install an alternative driver from https://github.com/lwfinger/rtl8723bs_bt, but it didn't make any difference.  As for the dtb.img; I couldn't use my android's dtb as it caused the installer to fail straight after the reboot. dtb is OK as md5sum is exactly the same as the one provided at the 150balbes' git repo.  The only way to successfully install the image was possible after hardcoding path to the dtb.img in uEnv.ini, also I had to use /boot/dtb/generic meson-gxbb-p200.dtb as my board is p200. Any other way of picking up dtb such as directly from android or placing any dtb.img in /boot failed (btw. is this expected behaviour or a bug?).

 

Looking through this thread, I noticed that ppl managed to get it going for earlier releases by compiling kernel, but I'm hopping this isn't needed any longer.

Anyone has an idea/tips how to go about troubleshooting this problem?

~$ ls -l /lib/firmware/rtlwifi/rtl8723b*
-rw-rw-r-- 1 root root 31762 Dec  6 15:17 /lib/firmware/rtlwifi/rtl8723befw_36.bin
-rw-rw-r-- 1 root root 30746 Dec  6 15:17 /lib/firmware/rtlwifi/rtl8723befw.bin
-rw-rw-r-- 1 root root 20886 Dec  6 15:17 /lib/firmware/rtlwifi/rtl8723bs_ap_wowlan.bin
-rw-rw-r-- 1 root root  9120 Dec  6 15:17 /lib/firmware/rtlwifi/rtl8723bs_bt.bin
-rw-rw-r-- 1 root root 32108 Dec  6 15:17 /lib/firmware/rtlwifi/rtl8723bs_nic.bin
-rw-rw-r-- 1 root root 26398 Dec  6 15:17 /lib/firmware/rtlwifi/rtl8723bs_wowlan.bin
-rw-rw-r-- 1 root root 20886 Dec  6 15:17 /lib/firmware/rtlwifi/rtl8723bu_ap_wowlan.bin
-rw-rw-r-- 1 root root 32108 Dec  6 15:17 /lib/firmware/rtlwifi/rtl8723bu_nic.bin
-rw-rw-r-- 1 root root 26398 Dec  6 15:17 /lib/firmware/rtlwifi/rtl8723bu_wowlan.bin
~$ ls -l /lib/firmware/rtlbt/rtl8723b*
-rw-rw-r-- 1 root root    68 Dec  6 15:17 /lib/firmware/rtlbt/rtl8723b_config
-rw-rw-r-- 1 root root    59 Dec  6 15:17 /lib/firmware/rtlbt/rtl8723b_config_2Ant_S0
-rw-rw-r-- 1 root root 46236 Dec  6 15:17 /lib/firmware/rtlbt/rtl8723b_fw
-rw-rw-r-- 1 root root    75 Dec  6 15:17 /lib/firmware/rtlbt/rtl8723b_VQ0_config
-rw-rw-r-- 1 root root 46236 Dec  6 15:17 /lib/firmware/rtlbt/rtl8723b_VQ0_fw
dmesg |grep -i  rtl8723
[   11.866677] RTL8723BS: module init start
[   11.866684] RTL8723BS: rtl8723bs v4.3.5.5_12290.20140916_BTCOEX20140507-4E40
[   11.866686] RTL8723BS: rtl8723bs BT-Coex version = BTCOEX20140507-4E40
[   11.901275] RTL8723BS: rtw_ndev_init(wlan0)
[   11.903075] RTL8723BS: module init ret =0
[   41.537342] rtl8723bs: acquire FW from file:rtlwifi/rtl8723bs_nic.bin
[   44.909176] RTL8723BS: rtw_set_802_11_connect(wlan0)  fw_state = 0x00000008
[   53.105718] RTL8723BS: rtw_set_802_11_connect(wlan0)  fw_state = 0x00000008
[   61.697665] RTL8723BS: rtw_set_802_11_connect(wlan0)  fw_state = 0x00000008
[   70.641023] RTL8723BS: rtw_set_802_11_connect(wlan0)  fw_state = 0x00000008
[   86.997712] RTL8723BS: rtw_set_802_11_connect(wlan0)  fw_state = 0x00000008
[   96.489400] RTL8723BS: rtw_set_802_11_connect(wlan0)  fw_state = 0x00000008
[   97.048558] RTL8723BS: start auth
[   97.068551] RTL8723BS: auth success, start assoc
[   97.088588] RTL8723BS: rtw_cfg80211_indicate_connect(wlan0) BSS not found !!
[   97.088601] RTL8723BS: assoc success
[   98.385865] RTL8723BS: send eapol packet
[   98.397271] RTL8723BS: send eapol packet
[   98.397598] RTL8723BS: set pairwise key camid:4, addr:d0:65:ca:8d:b4:92, kid:                      0, type:AES
[   98.398611] RTL8723BS: set group key camid:5, addr:d0:65:ca:8d:b4:92, kid:1,                       type:AES
dmesg  |grep -i bluetooth
[  144.696817] Bluetooth: Core ver 2.22
[  144.696822] Bluetooth: Starting self testing
[  144.712600] Bluetooth: ECDH test passed in 15399 usecs
[  144.715301] Bluetooth: SMP test passed in 2588 usecs
[  144.715310] Bluetooth: Finished self testing
[  144.715388] Bluetooth: HCI device and connection manager initialized
[  144.715399] Bluetooth: HCI socket layer initialized
[  144.715404] Bluetooth: L2CAP socket layer initialized
[  144.715423] Bluetooth: SCO socket layer initialized

 

~$ lsmod
Module                  Size  Used by
bluetooth             544768  0
ecdh_generic           24576  1 bluetooth
zstd                   16384  4
zram                   24576  5
zsmalloc               24576  1 zram
nls_ascii              16384  1
r8723bs               581632  0
cfg80211              348160  1 r8723bs
rfkill                 28672  4 bluetooth,cfg80211
meson_rng              16384  0
rng_core               16384  1 meson_rng
meson_ir               16384  0
rc_core                49152  2 meson_ir
meson_gxbb_wdt         16384  0
pwm_meson              16384  1
ao_cec                 16384  0
scpi_hwmon             16384  0
sch_fq_codel           20480  6
ip_tables              28672  0
x_tables               36864  1 ip_tables
ipv6                  487424  28
crc_ccitt              16384  1 ipv6
~$ hcitool dev
Devices:

 

Share this post


Link to post
Share on other sites
On 12/17/2018 at 11:14 AM, bog lee said:

Is the rtl8723bs combo wlan/bluethoot chip supported in the latest release (Armbian_5.67_Aml-s9xxx_Ubuntu_bionic_default_4.19.6_desktop_20181207)?

 

On 12/17/2018 at 11:14 AM, bog lee said:

I'm thinking my problem could be related either to the chip's driver or my problem with dtb.img during installation. I've tried to install an alternative driver from https://github.com/lwfinger/rtl8723bs_bt, but it didn't make any difference.  As for the dtb.img; I couldn't use my android's dtb as it caused the installer to fail straight after the reboot. dtb is OK as md5sum is exactly the same as the one provided at the 150balbes' git repo.  The only way to successfully install the image was possible after hardcoding path to the dtb.img in uEnv.ini, also I had to use /boot/dtb/generic meson-gxbb-p200.dtb as my board is p200. Any other way of picking up dtb such as directly from android or placing any dtb.img in /boot failed (btw. is this expected behaviour or a bug?).

 

 

 

2 hours ago, Greenhatguy said:

I've recently got Armbian running from the SD card using these methods, but my device (MXQ PRO, S905X) does not boot into Android when the SD card is not present.  It waits at the Amlogic logo and does nothing.  I've tried booting into recovery mode (toothpick method, bootable SD card) but nothing works.  Any ideas?

On such a meager description of what image you use and what steps did - only psychics will be able to understand what could be the problem.

Share this post


Link to post
Share on other sites

thanks balbes for make my device alive but i have a little issue , i installed lastest ubuntu version kerner 3.14.29 it booted , but look like screen is zoom in , i see only my desktop without taskbar i try to change resolution to 720p it boot to login screen after that nothing show up ! please help me 

THANK YOU FOR GREAD WORK !

which version recommended on my x96mini and DEB file THANK

IMAG0002.jpg

Share this post


Link to post
Share on other sites

Wifi working well open application a bit slow ( my sdcard class 4 8gb ) chrome work but extreme slow look like 12fps when play video (cpu not full load) for who dont know im using dtb 281 .

IMAG0011.jpg

IMAG0010.jpg

IMAG0009.jpg

IMAG0006.jpg

IMAG0004.jpg

IMAG0005.jpg

IMAG0003.jpg

Share this post


Link to post
Share on other sites
3 hours ago, BuiHuy said:

which version recommended on my x96mini and DEB file THANK

I am using on X96mini (2\16) version 5.67 with DTB from khadas-vim. All the details are in the relevant subject.

Share this post


Link to post
Share on other sites
2 hours ago, talraash said:

@BuiHuy disable gpu acceleration in chrome settings. an 480p in browser max(in some case 720p)

thanks but unfortunate i got 1080p ! It is possible to overclock this cpu cause in the box it show 2Ghz of cpu clock speed , but in ubuntu is 1,2Ghz and Go full load when i scrolling but not smooth

Share this post


Link to post
Share on other sites
On 12/22/2018 at 6:12 PM, BuiHuy said:

thanks but unfortunate i got 1080p ! It is possible to overclock this cpu cause in the box it show 2Ghz of cpu clock speed , but in ubuntu is 1,2Ghz and Go full load when i scrolling but not smooth

You soc maximum 1.2GHz by amlogic blob... 

Share this post


Link to post
Share on other sites

On WeTek Hub (1GB RAM) I'm getting the following error on any image from yadi.sk:
 

Quote

E:footer is wrong

E:signature verification failed
Instalation aborted

 

I tried with 2 sd cards. I properly set the uEnv.ini and then run the aml_autoscript.zip in updates section :S

Share this post


Link to post
Share on other sites
On 12/24/2018 at 1:49 PM, mocsadek68 said:

Hello everybody. 
I have got an Mecool M8S Pro + (S905X 2Gb 16Gb) machine. I try to install Armbian_5.37_S9xxx_Debian_stretch_3.14.29_xfce_20171226.img, but after the install, the system doesn't operate. The next picture can be seen:

 

https://drive.google.com/file/d/1PPU8q5kft2Io_8StWjMVFIwLYSn9rAbz/view?usp=sharing

 

Thank you for help!

I have the same Box and did try many .dtb files and images.

The only one i got to work was the 3.14 Kernel Images with the lepotato2g dtb. Try Armbian_5.44_S9xxx_Debian_stretch_3.14.29_xfce_20180601.

The newer Version from 20180729 has a different dtb file for the lepotato which didn't work for me. (Or take the new image but the dtb file from the old one)

As mentioned, did try 4.9 and 4.19 Images but no luck to get it working with different dtb files... Maybe someone can give me a tip :)

 

I have decompiled some dtb files back to dts (and the original android) to have a look at the differences, but with the newer kernels the "format" inside did change completly... 

 

Anyone having this Box, and got it to work, please get in touch with me :) (maybe with all the dtb file testing i did make a mistake^^)

Thanks

Share this post


Link to post
Share on other sites
23 hours ago, petatester said:

On WeTek Hub (1GB RAM) I'm getting the following error on any image from yadi.sk:

Maybe Wetek Hub needs to use the same multi-boot approach that works for Week Play 2. You need to add a special file " boot.ini", I remember sending it to the user Wetek Play2.

Share this post


Link to post
Share on other sites
1 hour ago, balbes150 said:

Maybe Wetek Hub needs to use the same multi-boot approach that works for Week Play 2. You need to add a special file " boot.ini", I remember sending it to the user Wetek Play2.

Interesting, i tried using multiboot from LibElec & company but when Wetek shows the "Press power button to boot from sdcard" and you press it, nothing happens, loads Android as usual. Maybe the Android version is too up to date and needs a downgrade?

Share this post


Link to post
Share on other sites
15 hours ago, petatester said:

Interesting, i tried using multiboot from LibElec & company but when Wetek shows the "Press power button to boot from sdcard" and you press it, nothing happens, loads Android as usual. Maybe the Android version is too up to date and needs a downgrade? 

Try to ask the user about the start. Please note that the LE option, which is specifically designed for Wetek, does not have a universal multi-boot and will not work correctly with Armbian.

 

https://forum.libreelec.tv/thread/12330-test-libreelec-images-with-kodi-18-for-s9xxx/?postID=106454#post106454

Share this post


Link to post
Share on other sites
On 6/7/2017 at 8:40 AM, balbes150 said:

1. After the first command, you need to wait 1-2 minutes and check the network connections Manager the advent of Wi-Fi. If your desired network appears, you need to open the file /etc/modules and add on a new line the name of the module wifi_dummy. After that, reboot the system, if you did everything correctly, you should automatically see the wifi network at startup.

2. If the first module (wifi_dummy) network did not work. You need to run the second command "sudo modprobe dhd" . Notice all the letters exactly as written. Capitalization is important in LINUX. dhd is not equal DHD. Other actions with the dhd module are the same as in the first point.

 

The wifi_dummy trick does not work anymore with recent version of armbian (I am using 5.71) what is the new trick @balbes150 thank you in advance for your help

Share this post


Link to post
Share on other sites
1 hour ago, David Markey said:

I have bricked my s905x box, I installed onto the in built memory and now it kernel oops. It was working for a long time. How can I force to boot off SD card again?

Write in detail what you did, what settings you used, what image was used, what is happening now.

Share this post


Link to post
Share on other sites

It's a while since I set this box up.. it just decided not to boot recently.. I believe i used some script supplied by armbian or yourself to install onto the internal storage. I think it was 5.34

 

I've tried to solder the serial headers but I cannot I started to make a mess.

 

Here is the boot sequence: 

I c

 

 

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
63 63