59 59
balbes150

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

Recommended Posts

Bonjour,

Excuse me for my poor English language; i'm french !

 

I just installed Armbian_5.37_S9xxx_Debian_stretch_3.14.29_server_20171226.img in dual-boot in my Mecool M8s-pro+ (4.xx) not boot.

 

But i have a problem, the owner and group of files and directory are "1023" (a user who does not exist)=>screen of /etc directory:

 

etc directory

 

When I add users in home directory (adduser command), the owner and the group of the users created are good (1001 and 1002) ; but after restarting, owner and group of users become "1023"=> like screen

 

home directory

 

I do not understand what it can come ; this is very annoying for ssh key connection.

 

If you can help me, thank you.

 

Merci d'avance pour votre aide.

Share this post


Link to post
Share on other sites

I have a mecool bb2  pro which is a powerful 8 core s912 box.    I'm using it for real-time FFMPEG transcoding and re-streaming and it's able to do this for HD with this number of core w/o GPU.    The problem I have is I need to make the wifi work on this box.   The install of Armbian is not finding the wifi hardware and installing drivers.   I tried the methods at the top of this post for wifi and none of them work on this box.     Maybe I need to build drivers for it myself?   Does anyone know the wifi chip used on the mecool bb2 pro  and/or if there is a way to detect and dump that info from Armbian command line tools?

 

Share this post


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

I have a mecool bb2  pro which is a powerful 8 core s912 box.    I'm using it for real-time FFMPEG transcoding and re-

Sorry, not familiar with mecool bb2 pro but as a general tip when debugging wifi problems, I found kernel 3.x Armbian builds supported wifi but the 4.x kernels did not work even though a module was loaded.
Having got the correct dtb file, I had a poke around in /sys/class/net/wlan0/device/modalias & uevent
I compared this to what android had and also made sure the files being used by android /lib/firmware/ and Armbian where correct.

 

Share this post


Link to post
Share on other sites

Hi! I can't boot the Armbian image in a Mecool Ki Pro, at least from USB. I tried changing in uEnv.ini the DTB to "dtb/meson-gxl-s905d-p230.dtb" and copying it as "dtb.img" in root of the BOOT partition without success, even I created my own aml_autoscript based in the original but haven't luck.

 

Here is my aml_autoscript after many modifications trying to get it work:

 

defenv

setenv env_addr 0x10400000
setenv kernel_addr 0x11000000
setenv initrd_addr 0x13000000

setenv bootargs 'root=LABEL=ROOTFS rootflags=data=writeback rw console=ttyAML0,115200n8 console=tty0 no_console_suspend consoleblank=0 fsck.fix=yes fsck.repair=yes net.ifnames=0'

setenv boot_start 'booti ${kernel_addr} ${initrd_addr} ${dtb_mem_addr}'

setenv sdload 'if fatload mmc 0 ${kernel_addr} zImage; \
then \
    if fatload mmc 0 ${initrd_addr} uInitrd; \
    then \
        if fatload mmc 0 ${env_addr} uEnv.ini; \
        then \
            env import -t ${env_addr} ${filesize}; \
        fi; \
        if fatload mmc 0 ${dtb_mem_addr} dtb.img; \
        then \
            #run boot_start; \
            setenv bootargs ${bootargs} sdload \
            booti ${kernel_addr} ${initrd_addr} ${dtb_mem_addr}; \
        else \
            store dtb read ${dtb_mem_addr}; \
            #run boot_start; \
            booti ${kernel_addr} ${initrd_addr} ${dtb_mem_addr}; \
        fi; \
    fi; \
fi;'

setenv usbload 'if fatload usb 0 ${kernel_addr} zImage; \
then \
    if fatload usb 0 ${initrd_addr} uInitrd; \
    then \
        if fatload usb 0 ${env_addr} uEnv.ini; \
        then \
            env import -t ${env_addr} ${filesize}; \
        fi; \
        if fatload usb 0 ${dtb_mem_addr} dtb.img; \
        then \
            #run boot_start; \
            setenv bootargs ${bootargs} usbload \
            booti ${kernel_addr} ${initrd_addr} ${dtb_mem_addr}; \
        else \
            store dtb read ${dtb_mem_addr}; \
            #run boot_start; \
            booti ${kernel_addr} ${initrd_addr} ${dtb_mem_addr}; \
        fi; \
    fi; \
fi;'

setenv bootcmd 'run sdload; run usbload; run storeboot;'
#setenv upgrade_step 2

saveenv
#run storeargs # desactivar si da problemas

run sdload
run usbload
run storeboot

#run bootcmd
#sleep 1
#reboot

PD: The image I have is "Armbian_5.60_Aml-s9xxx_Ubuntu_bionic_default_4.18.7_desktop_20180928.img"

Edited by Francisco Aarón

Share this post


Link to post
Share on other sites
10 hours ago, dbsharpe said:

Sorry, not familiar with mecool bb2 pro but as a general tip when debugging wifi problems, I found kernel 3.x Armbian builds supported wifi but the 4.x kernels did not work even though a module was loaded.
Having got the correct dtb file, I had a poke around in /sys/class/net/wlan0/device/modalias & uevent
I compared this to what android had and also made sure the files being used by android /lib/firmware/ and Armbian where correct.

 

Fwiw,  I had to use the 3.x kernel to get the mecool bb2 pro s912 to boot.   This build:  Armbian_5.44_S9xxx_Ubuntu_xenial_3.14.29_mate_20180515.img
But no wifi  KLM is loaded for the wireless hardware.   Maybe I need to try another dtb file in that build.

Share this post


Link to post
Share on other sites

hi all, same kind of problem for few days, trying to make wifi & bt to work on several boxes i have here : mini m8s (s905) , x96 mini (s905w), i have mecool and beelikn minimx too


No luck for the moment, i'm going to try to use the box for Domoticz usage (installed it and had the webpage working but i have trouble with armbian and internal box hw)


i bought them long time ago, not very sure if each of them support wifi (i think so ) and Bluetooth (not sure, at least x96mini doesn't)


Armbian worked well (i found the correct dtb fil for each box)

 

 

so i parsed alors of pages from this forum, and tried few things for wifi , i'm on the mini m8s classic box and hope some advices :

 

 

i think the mini m8s s905 box has 8723bs


so i tried "modprobe 8723bs"

 

i tried first  : 5.64 image but after few reading i got the point i needed to go to a 3.14 kernel and now sd card has it :

took from
mali6/5.41.1_KODI-17.6 image

Linux amlogic 3.14.29 #24 SMP PREEMPT Fri Apr 6 18:56:07 MSK 2018 aarch64 GNU/Linux

 

after a reboot :

 

root@amlogic:~# lsmod
Module                  Size  Used by
aml_nftl_dev           95108  0

root@amlogic:~# modprobe 8723bs

root@amlogic:~# lsmod
Module                  Size  Used by
8723bs               1321264  0
cfg80211              415017  1 8723bs
aml_nftl_dev           95108  0

 

Spoiler

 

[   20.013633] aml_audio_i2s_mute_flag: flag=0
[   20.013655] aml_audio_set_spdif_mute: flag=0
[   20.013667] aml_snd_card: aml_m8_set_spk: aml_m8_spk_enabled=0
[   21.110814] input: lircd-uinput as /devices/virtual/input/input3
[   21.384074] libphy: stmmac-0:08 - Link is Up - 100/Full
[   23.029943] meson_uart c81004c0.serial: ttyS0 use xtal(8M) 24000000 change 115200 to 115200
[   23.030331] meson_uart c81004c0.serial: ttyS0 use xtal(8M) 24000000 change 115200 to 115200
[   23.055156] meson_uart c81004c0.serial: ttyS0 use xtal(8M) 24000000 change 115200 to 115200
[   23.055530] meson_uart c81004c0.serial: ttyS0 use xtal(8M) 24000000 change 115200 to 115200
[   46.137792] nf_conntrack: automatic helper assignment is deprecated and it will be removed soon. Use the iptables CT target to attach helpers instead.
[  200.932568] cfg80211: Calling CRDA to update world regulatory domain
[  201.069037] RTL871X: module init start
[  201.069051] RTL871X: rtl8723bs v4.3.16_13854.20150410_BTCOEX20150119-5844
[  201.069055] RTL871X: rtl8723bs BT-Coex version = BTCOEX20150119-5844
[  201.069058] ######platform_wifi_power_on:
[  201.069079] aml_wifi wifi.32: [extern_wifi_set_enable] WIFI  Disable! 240
[  201.102972] cfg80211: World regulatory domain updated:
[  201.102989] cfg80211:  DFS Master region: unset
[  201.102994] cfg80211:   (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
[  201.102999] cfg80211:   (2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A, 2000 mBm)
[  201.103003] cfg80211:   (2457000 KHz - 2482000 KHz @ 20000 KHz), (N/A, 2000 mBm)
[  201.103008] cfg80211:   (2474000 KHz - 2494000 KHz @ 20000 KHz), (N/A, 2000 mBm)
[  201.103012] cfg80211:   (5170000 KHz - 5250000 KHz @ 80000 KHz), (N/A, 2000 mBm)
[  201.103016] cfg80211:   (5250000 KHz - 5330000 KHz @ 80000 KHz), (N/A, 2000 mBm)
[  201.103020] cfg80211:   (5490000 KHz - 5730000 KHz @ 160000 KHz), (N/A, 2000 mBm)
[  201.103024] cfg80211:   (5735000 KHz - 5835000 KHz @ 80000 KHz), (N/A, 2000 mBm)
[  201.103028] cfg80211:   (57240000 KHz - 63720000 KHz @ 2160000 KHz), (N/A, 0 mBm)
[  201.573756] aml_wifi wifi.32: [extern_wifi_set_enable] WIFI  Enable! 240
[  202.089687] [aml_sd_emmc_irq] sdio: resp_timeout,vstat:0xa3ff2800,virqc:3fff
[  202.089713] [aml_host_bus_fsm_show] sdio: err: wait for irq service, bus_fsm:0x8
[  202.089759] aml_sd_emmc_data_thread 2639 sdio: cmd:8
[  202.091790] aml_sd_emmc d0070000.sdio: card claims to support voltages below defined range
[  202.109793] sdio: new high speed SDIO card at address 0001
[  202.109817] sdio: clock 50000000, 4-bit-bus-width

[  202.110252] [sdio_reinit] finish
[  202.110407] RTL871X: module init ret=0

 

 


root@amlogic:~# iwconfig
eth0      no wireless extensions.

ip6tnl0   no wireless extensions.

sit0      no wireless extensions.

lo        no wireless extensions.

tunl0     no wireless extensions.

 

any ideas?
thanks alot!
(will try bluetooth afterward)

Edited by ster

Share this post


Link to post
Share on other sites
17 hours ago, ster said:

hi all, same kind of problem for few days, trying to make wifi & bt to work on several boxes i have here : mini m8s (s905) , x96 mini (s905w), i have mecool and beelikn minimx too


No luck for the moment, i'm going to try to use the box for Domoticz usage (installed it and had the webpage working but i have trouble with armbian and internal box hw)


i bought them long time ago, not very sure if each of them support wifi (i think so ) and Bluetooth (not sure, at least x96mini doesn't)


Armbian worked well (i found the correct dtb fil for each box)

 

 

so i parsed alors of pages from this forum, and tried few things for wifi , i'm on the mini m8s classic box and hope some advices :

 

 

i think the mini m8s s905 box has 8723bs


so i tried "modprobe 8723bs"

 

i tried first  : 5.64 image but after few reading i got the point i needed to go to a 3.14 kernel and now sd card has it :

took from
mali6/5.41.1_KODI-17.6 image

Linux amlogic 3.14.29 #24 SMP PREEMPT Fri Apr 6 18:56:07 MSK 2018 aarch64 GNU/Linux

 

after a reboot :

 

root@amlogic:~# lsmod
Module                  Size  Used by
aml_nftl_dev           95108  0

root@amlogic:~# modprobe 8723bs

root@amlogic:~# lsmod
Module                  Size  Used by
8723bs               1321264  0
cfg80211              415017  1 8723bs
aml_nftl_dev           95108  0

 

  Reveal hidden contents

 

[   20.013633] aml_audio_i2s_mute_flag: flag=0
[   20.013655] aml_audio_set_spdif_mute: flag=0
[   20.013667] aml_snd_card: aml_m8_set_spk: aml_m8_spk_enabled=0
[   21.110814] input: lircd-uinput as /devices/virtual/input/input3
[   21.384074] libphy: stmmac-0:08 - Link is Up - 100/Full
[   23.029943] meson_uart c81004c0.serial: ttyS0 use xtal(8M) 24000000 change 115200 to 115200
[   23.030331] meson_uart c81004c0.serial: ttyS0 use xtal(8M) 24000000 change 115200 to 115200
[   23.055156] meson_uart c81004c0.serial: ttyS0 use xtal(8M) 24000000 change 115200 to 115200
[   23.055530] meson_uart c81004c0.serial: ttyS0 use xtal(8M) 24000000 change 115200 to 115200
[   46.137792] nf_conntrack: automatic helper assignment is deprecated and it will be removed soon. Use the iptables CT target to attach helpers instead.
[  200.932568] cfg80211: Calling CRDA to update world regulatory domain
[  201.069037] RTL871X: module init start
[  201.069051] RTL871X: rtl8723bs v4.3.16_13854.20150410_BTCOEX20150119-5844
[  201.069055] RTL871X: rtl8723bs BT-Coex version = BTCOEX20150119-5844
[  201.069058] ######platform_wifi_power_on:
[  201.069079] aml_wifi wifi.32: [extern_wifi_set_enable] WIFI  Disable! 240
[  201.102972] cfg80211: World regulatory domain updated:
[  201.102989] cfg80211:  DFS Master region: unset
[  201.102994] cfg80211:   (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
[  201.102999] cfg80211:   (2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A, 2000 mBm)
[  201.103003] cfg80211:   (2457000 KHz - 2482000 KHz @ 20000 KHz), (N/A, 2000 mBm)
[  201.103008] cfg80211:   (2474000 KHz - 2494000 KHz @ 20000 KHz), (N/A, 2000 mBm)
[  201.103012] cfg80211:   (5170000 KHz - 5250000 KHz @ 80000 KHz), (N/A, 2000 mBm)
[  201.103016] cfg80211:   (5250000 KHz - 5330000 KHz @ 80000 KHz), (N/A, 2000 mBm)
[  201.103020] cfg80211:   (5490000 KHz - 5730000 KHz @ 160000 KHz), (N/A, 2000 mBm)
[  201.103024] cfg80211:   (5735000 KHz - 5835000 KHz @ 80000 KHz), (N/A, 2000 mBm)
[  201.103028] cfg80211:   (57240000 KHz - 63720000 KHz @ 2160000 KHz), (N/A, 0 mBm)
[  201.573756] aml_wifi wifi.32: [extern_wifi_set_enable] WIFI  Enable! 240
[  202.089687] [aml_sd_emmc_irq] sdio: resp_timeout,vstat:0xa3ff2800,virqc:3fff
[  202.089713] [aml_host_bus_fsm_show] sdio: err: wait for irq service, bus_fsm:0x8
[  202.089759] aml_sd_emmc_data_thread 2639 sdio: cmd:8
[  202.091790] aml_sd_emmc d0070000.sdio: card claims to support voltages below defined range
[  202.109793] sdio: new high speed SDIO card at address 0001
[  202.109817] sdio: clock 50000000, 4-bit-bus-width

[  202.110252] [sdio_reinit] finish
[  202.110407] RTL871X: module init ret=0

 

 


root@amlogic:~# iwconfig
eth0      no wireless extensions.

ip6tnl0   no wireless extensions.

sit0      no wireless extensions.

lo        no wireless extensions.

tunl0     no wireless extensions.

 

any ideas?
thanks alot!
(will try bluetooth afterward)

I seem to remember that I had the same problem, both with the Mini M8S and a Mini MXIII (which is virtually identical), I downloaded the 8723as driver module from github, compiled and installed it and got WiFi working but never BT, until I hooked on a cheap usb-bt adapter.

Share this post


Link to post
Share on other sites

I still can't boot Armbian in a Mecool Ki Pro. I have been using an Arch Linux image that I found on a website but it came with few things installed, and after installing more applications and configuring things now it randomly freeze. I only wanted compile applications for using in LibreElec.

Share this post


Link to post
Share on other sites

Answering to myself : everything work now..

 

I changed boxes (i have several mini m8s) , and one is working (modprobe 8723bs display now a wlan0 in ifconfig)

 

difference is that one box is bigger than the other, both have the same design, name and chipset serial (S905)

 

be careful so

IMG_0627.jpg

Share this post


Link to post
Share on other sites
Just now, ster said:

Answering to myself : everything work now..

 

I changed boxes (i have several mini m8s) , and one is working (modprobe 8723bs display now a wlan0 in ifconfig)

 

difference is that one box is bigger than the other, both have the same design, name and chipset serial (S905)

 

be careful so

IMG_0627.jpg

They just might have different wlan chip...

Share this post


Link to post
Share on other sites
11 hours ago, Francisco Aarón said:

I still can't boot Armbian in a Mecool Ki Pro. I have been using an Arch Linux image that I found on a website but it came with few things installed, and after installing more applications and configuring things now it randomly freeze. I only wanted compile applications for using in LibreElec.

If you run ArchLinux, so Armbian can start. They use close kernels (the kernel in ArchLinux is added from Armbian).

 

 

Share this post


Link to post
Share on other sites

The BT dongle had no spesifiic name, just a cheap one from the "Clas Ohlson" store here in Norway, but it worked right of of the box. WiFi worked with the built-in and the AS8723 driver module from Github.

Share this post


Link to post
Share on other sites
On 11/12/2018 at 1:48 PM, dbsharpe said:

Sorry, not familiar with mecool bb2 pro but as a general tip when debugging wifi problems, I found kernel 3.x Armbian builds supported wifi but the 4.x kernels did not work even though a module was loaded.
Having got the correct dtb file, I had a poke around in /sys/class/net/wlan0/device/modalias & uevent
I compared this to what android had and also made sure the files being used by android /lib/firmware/ and Armbian where correct.

 

So how does one know or figure out the correct dtb file to copy up to /boot/dtb.img  ?    Is it purely trial and error?
I'm using this build:  Armbian_5.44_S9xxx_Ubuntu_xenial_3.14.29_mate_20180515.img.   I've modprobe xyz  about everything i could find under /lib/modules/3.14.29/kernel/drivers/amlogic/wifi but no wlan0 i/f will show up.  Some of these KLMs will load and show with lsmod, but no wifi.    I'm motivated to make a donation armbian.com to get the wifi working on this box.   It's the only 8 core box I know for under $100 so this is a great platform to support.

Share this post


Link to post
Share on other sites

I can't get any of the images in 5.67 to boot on Mini M8S or Mini MXIII (S905 cpu), they seem to work fine on my MXQPro+ (S905w cpu), even video plays smoot in fullscreen/full HD.

Har anyone tried this images on a S905 cpu?

Share this post


Link to post
Share on other sites
22 minutes ago, briand123 said:

So how does one know or figure out the correct dtb file to copy up to /boot/dtb.img  ?    Is it purely trial and error?
I'm using this build:  Armbian_5.44_S9xxx_Ubuntu_xenial_3.14.29_mate_20180515.img.   I've modprobe xyz  about everything i could find under /lib/modules/3.14.29/kernel/drivers/amlogic/wifi but no wlan0 i/f will show up.  Some of these KLMs will load and show with lsmod, but no wifi.    I'm motivated to make a donation armbian.com to get the wifi working on this box.   It's the only 8 core box I know for under $100 so this is a great platform to support. 

Kernel 3.14 is no longer developing (not supported), so you will have to try to add the necessary support for WiFi in this version of the kernel or contact the manufacturer (seller) of your equipment.

 

21 minutes ago, Reddwarf said:

Har anyone tried this images on a S905 cpu?

S905 = gxbb

Check all available DTB of this group.

Share this post


Link to post
Share on other sites
Just now, balbes150 said:

S905 = gxbb

Check all available DTB of this group.

I have tried all the gxbb dtb's on previous versions and the only one that works with those mentioned boxes is the p200 dtb.

Share this post


Link to post
Share on other sites
Just now, venioni said:

Can anyone tell me if these Armbian arm img can working on my mi tv box 3 international version ? I have try many of these rom and not worked.

Which dtb did you use? If the box runs Android you can install the CPUZ app and find the board model, it will help you fint the correct dtb to use...

Share this post


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

Which dtb did you use? If the box runs Android you can install the CPUZ app and find the board model, it will help you fint the correct dtb to use...

II have tried all dtb and none working, my tv box model is Mi box 3 mdz 16-ab with S905 SoC with quad-core Cortex-A53 CPU .

Share this post


Link to post
Share on other sites
Just now, venioni said:

II have tried all dtb and none working, my tv box model is Mi box 3 mdz 16-ab with S905 SoC with quad-core Cortex-A53 CPU .

Yeah, but if you run cpu-z you should get a board number, ie. my Mini M8S has board number p200, my MXQPro+ has board number 281, and that is what you are looking for.

 

Share this post


Link to post
Share on other sites
53 minutes ago, Reddwarf said:

Yeah, but if you run cpu-z you should get a board number, ie. my Mini M8S has board number p200, my MXQPro+ has board number 281, and that is what you are looking for.

 

I runned CPU-Z and dont showing nothing about board number.

IMG_20181118_203251.jpg

IMG_20181118_203259.jpg

IMG_20181118_203307.jpg

Share this post


Link to post
Share on other sites
10 hours ago, venioni said:

I runned CPU-Z and dont showing nothing about board number.

IMG_20181118_203251.jpg

IMG_20181118_203259.jpg

IMG_20181118_203307.jpg

No you'r right, it should have been under Device, board but it only says "once". But balbes150 has linked to a very useful thread :)

Share this post


Link to post
Share on other sites
17 hours ago, venioni said:

I runned CPU-Z and dont showing nothing about board number.

 

 

Don't know if it will be more help but you can also get the hardware info from android adb shell getprop | grep -i build.product  or grep -i build.product /system/build.prop
Also grep for
ro.build.flavor
ro.product.name
ro.product.device
ro.product.board
ro.build.product
board.platform

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
59 59