Single Armbian image for RK + AML + AW (aarch64 ARMv8)


Recommended Posts

19 hours ago, gilberto said:

I tried all the dtbs but the wifi does not work the device does not appear with the command ifconfig the hardware configuration is just below. Thank you all for your help! Right now I'm downloading the last img 5/20 to try.

 

 

Your dmesg implies your built in wifi might be RTL8723BS but I couldnt tell you about kernel / dts support for it.
Have a look at this post https://forum.armbian.com/topic/2419-armbian-for-amlogic-s905-and-s905x-ver-544/?do=findComment&comment=65706 (which you probably know anyway how to probe) and my other posts about hardware.
You've not said what box/hardware you have - it may be covered by one of the other forums topics.

Link to post
Share on other sites
Donate and support the project!

19 hours ago, gilberto said:

I tried all the dtbs but the wifi does not work the device does not appear with the command ifconfig the hardware configuration is just below.

0.000000] Linux version 5.1.0-aml-s905

 

old kernel

Link to post
Share on other sites

The new version 20.05.5 (20200522).

All images are build entirely on the ARM platform (rk3399 + NVMe). After fixing bugs, the process of building the first image (including downloading sources, building all packages, building the kernel, u-boot, and so on) took less than 50 minutes.  :)

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

 

Your dmesg implies your built in wifi might be RTL8723BS but I couldnt tell you about kernel / dts support for it.
Have a look at this post https://forum.armbian.com/topic/2419-armbian-for-amlogic-s905-and-s905x-ver-544/?do=findComment&comment=65706 (which you probably know anyway how to probe) and my other posts about hardware.
You've not said what box/hardware you have - it may be covered by one of the other forums topics.

Following instructions from you and balbes150, I changed the version of the image to kernel 5.6, as for the model of my box, how can I have details. The only thing written behind it is Model TX3 Mini -H.

 

Linux aml 5.5.0-rc6-aml-s9xxx #rc1.037 SMP PREEMPT Wed Feb 5 15:59:04 MSK 2020 aarch64 GNU/Linux this is my kernel

I try modprobe r8723bs 


oot@aml:/home/fenixix# lsmod
Module                  Size  Used by
r8723bs               581632  0
cfg80211              417792  1 r8723bs
fuse                  131072  3
bnep                   32768  2
zram                   36864  2
nls_ascii              16384  1
joydev                 28672  0
hci_uart              143360  0
ir_nec_decoder         20480  0
btqca                  20480  1 hci_uart
meson_vdec             86016  0
btrtl                  24576  1 hci_uart
lima                   45056  0
btbcm                  16384  1 hci_uart
v4l2_mem2mem           40960  1 meson_vdec
rc_khadas              16384  0
gpu_sched              28672  1 lima
btintel                32768  1 hci_uart
videobuf2_dma_contig    24576  1 meson_vdec
crct10dif_ce           16384  1
videobuf2_memops       20480  1 videobuf2_dma_contig
meson_ir               16384  0
videobuf2_v4l2         36864  2 meson_vdec,v4l2_mem2mem
bluetooth             598016  13 btrtl,btqca,btintel,hci_uart,btbcm,bnep
rc_core                61440  4 rc_khadas,ir_nec_decoder,meson_ir
videobuf2_common       61440  3 meson_vdec,videobuf2_v4l2,v4l2_mem2mem
videodev              233472  4 meson_vdec,videobuf2_v4l2,videobuf2_common,v4l2_mem2mem
ao_cec                 20480  0
ecdh_generic           16384  1 bluetooth
ecc                    32768  1 ecdh_generic
rfkill                 36864  5 bluetooth,cfg80211
mc                     61440  4 videodev,videobuf2_v4l2,videobuf2_common,v4l2_mem2mem
meson_rng              16384  0
dw_hdmi_cec            16384  0
ip_tables              28672  0
x_tables               40960  1 ip_tables
ipv6                  585728  48
nf_defrag_ipv6         24576  1 ipv6
gpio_keys_polled       16384  0
adc_keys               16384  0
root@aml:/home/fenixix# uname -a
Linux aml 5.5.0-rc6-aml-s9xxx #rc1.037 SMP PREEMPT Wed Feb 5 15:59:04 MSK 2020 aarch64 GNU/Linux
root@aml:/home/fenixix# 
 

the result is

root@aml:/home/fenixix# ifconfig 
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.0.13  netmask 255.255.255.0  broadcast 192.168.0.255
        inet6 2804:14c:87c0:c3ca:99dd:aeb8:80fe:936a  prefixlen 64  scopeid 0x0<global>
        inet6 2804:14c:87c0:c3ca:215:18ff:fe01:8131  prefixlen 64  scopeid 0x0<global>
        inet6 fe80::215:18ff:fe01:8131  prefixlen 64  scopeid 0x20<link>
        ether 00:15:18:01:81:31  txqueuelen 1000  (Ethernet)
        RX packets 18935  bytes 17030091 (16.2 MiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 9778  bytes 1469003 (1.4 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
        device interrupt 23  

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 1000  (Local Loopback)
        RX packets 6  bytes 234 (234.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 6  bytes 234 (234.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

root@aml:/home/fenixix# 
 

 

it seems to be a problem with the firmware the module loads but I see this message with dmesg

 

[  594.344364] cfg80211: Loading compiled-in X.509 certificates for regulatory database
[  594.382245] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
[  594.385982] platform regulatory.0: Direct firmware load for regulatory.db failed with error -2
[  594.391731] cfg80211: failed to load regulatory.db
[  594.426432] r8723bs: module is from the staging directory, the quality is unknown, you have been warned.
[  594.443870] RTL8723BS: module init start
[  594.443910] RTL8723BS: rtl8723bs v4.3.5.5_12290.20140916_BTCOEX20140507-4E40
[  594.449220] RTL8723BS: rtl8723bs BT-Coex version = BTCOEX20140507-4E40
[  594.455843] RTL8723BS: module init ret =0
root@aml:/home/fenixix# 
 

I have with armbianmonitor -u

http://ix.io/2n0i

 

 

I believe that other people will have the same problem with their boxes. How can I be sure the model of my box only has the sticker that I said behind it. I have a project and I will have several models being tested. I compiled the 7.7 kernel and it was the same. Guys do you have any idea ..

 

Thanks for responding and I want to help as much as possible on the s905 cards

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

Following instructions from you and balbes150, I changed the version of the image to kernel 5.6, as for the model of my box, how can I have details. The only thing written behind it is Model TX3 Mini -H.

 

 

TV boxes can be anything inside despite being identical so you have to dig around.
If I was in your position, I would boot into android to determine what wifi chip you have and what firmware file it uses - see this post plus whats in /sys/class/net/.

The type of AMLogic hardware 'details' can be determined from this post which give you an starting point for the dtb file that is required.

Wifi & BT are not guaranteed to work as per the developer/forum thread originator. Hardware can be supported one day and then the next release a bug creeps into the kernel or dts.
You also need to try every dtb file.

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

The new version 20.05.5 (20200522).

All images are build entirely on the ARM platform (rk3399 + NVMe). After fixing bugs, the process of building the first image (including downloading sources, building all packages, building the kernel, u-boot, and so on) took less than 50 minutes.  :)

Really impressive. Thank you for the excellent work you're doing.

 

I've migrated recently from Armbian to Manjaro ARM (some credit for balbes150 again) on my Khadas Vim2 Pro like (dtb) machines : Dealdig-Boxd6/Beelink GT1 Ultimate. Everything works great there too (eth, wlan even in AP mode, bluetooth) and OpenGL ES with Panfrost (but unfortunnaly not yet on XFCE4 with its default compositor nor with picom either).

 

 

 

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

 

TV boxes can be anything inside despite being identical so you have to dig around.
If I was in your position, I would boot into android to determine what wifi chip you have and what firmware file it uses - see this post plus whats in /sys/class/net/.

The type of AMLogic hardware 'details' can be determined from this post which give you an starting point for the dtb file that is required.

Wifi & BT are not guaranteed to work as per the developer/forum thread originator. Hardware can be supported one day and then the next release a bug creeps into the kernel or dts.
You also need to try every dtb file.

The first thing I will try and in the 5.7 kernel, test all dtbs I already installed Android and I will access the / sys / class / net / and discover the modules used by the kernel on android. I'm installing an app on android called King root to access the shell and discover this information. For me to be root and discover this. Thank you very much for all your help. I will try to be active on the channel to help everyone as well .... I will soon pass on my discoveries about this BOX .... If you have suggestions I will follow ...

Link to post
Share on other sites

A clean test build of the Focal-server image on the Ugoos X2 TV box (s905x2). The build system (Armbian Bionic desktop) is started from the SD card. I cloned GIT, started the build, and the system automatically got all the necessary packages (dependencies), installed them, and started the build (downloading sources, building the kernel, and so on). The entire process from the start of the build to the output of the finished image took exactly 201 minutes. The total amount of space used on the SD card (together with the finished image) it was about 11 GB. This means that 16 GB of storage will be enough to build the server version (perhaps 16 GB will be enough for the desktop version). I consider this a good result for a minimal device with 4 cores and the slowest media (SD card). :)

It would be interesting to compare the results of the build process on different TV boxes (chips) with different media.

Link to post
Share on other sites

Checked the test build on AM6 (s922). When starting the system and building from the SD card, the clean build of the Focal-server version took 101 minutes. Installed the same system from the SD card to eMMC. Launched a clean build of the Bionic-desktop version for s812 (running, downloading all sources, full kernel build, u-boot, all packages, etc.). build Time is 73 minutes. This shows how media parameters affect the overall build time.

Link to post
Share on other sites
On 5/24/2020 at 11:16 AM, balbes150 said:

A question for those who use the header package for the kernel. Previously reported errors with this package (due to the build on x86). I'm wondering if there are any header errors after transferring the build to the ARM platform ?

deb files with the new kernel collected on the ARM platform

 

https://yadi.sk/d/4swKv82e0Cd29A

Hi,

Even though the old sources packages also work fine for me, now i can compile rtl8812au driver with the parts that use floating point.  Is now the kernel compiled without mgeneral-regs-only?

Thank you,

Link to post
Share on other sites
On 5/24/2020 at 11:16 AM, balbes150 said:

A question for those who use the header package for the kernel. Previously reported errors with this package (due to the build on x86). I'm wondering if there are any header errors after transferring the build to the ARM platform ?

deb files with the new kernel collected on the ARM platform

 

https://yadi.sk/d/4swKv82e0Cd29A

No problem here :

❯ dpkg -i linux-image-current-arm-64_20.05.5_arm64.deb linux-headers-current-arm-64_20.05.5_arm64.deb
(Reading database ... 74883 files and directories currently installed.)
Preparing to unpack linux-image-current-arm-64_20.05.5_arm64.deb ...
Unpacking linux-image-current-arm-64 (20.05.5) over (20.05.4) ...
Preparing to unpack linux-headers-current-arm-64_20.05.5_arm64.deb ...
Unpacking linux-headers-current-arm-64 (20.05.5) over (20.05.4) ...
Setting up linux-image-current-arm-64 (20.05.5) ...
update-initramfs: Generating /boot/initrd.img-5.7.0-rc6-arm-64
W: Couldn't identify type of root file system for fsck hook
update-initramfs: Converting to u-boot format
Setting up linux-headers-current-arm-64 (20.05.5) ...
Compiling headers - please wait ...

Link to post
Share on other sites

Hello world!

 

I wanted to ask if there is a possibility of updating my current Armbian build 20.05.4 to a new one 20.05.5? I run it on S905 with balbes150's build. apt upgrade fetches the newest versions of packages, but armbian-config still shows the old version. Updating the kernel to the newest one (with 20.05.5 headers) also does not affect the version.

 

I did some digging and it appears that 20.05.4 shows up in a couple of files, including armbian-release (which advises not to modify the file).

 

Did I miss something or is the clean installation the only option?

 

Thanks!

Link to post
Share on other sites
On 5/22/2020 at 3:24 PM, dbsharpe said:

 

TV boxes can be anything inside despite being identical so you have to dig around.
If I was in your position, I would boot into android to determine what wifi chip you have and what firmware file it uses - see this post plus whats in /sys/class/net/.

The type of AMLogic hardware 'details' can be determined from this post which give you an starting point for the dtb file that is required.

Wifi & BT are not guaranteed to work as per the developer/forum thread originator. Hardware can be supported one day and then the next release a bug creeps into the kernel or dts.
You also need to try every dtb file.

 

To find out the information about the BOX, I am posting images of Android with the information, discover the module:  which is the ssv6051 but the error with the command sudo modprobe ssv6051

As I am testing with the new images of Balbes150 I believe that many will have this problem with this wifi.  

 

The images below are from android and show amlogic box. I tried to load the module ssv6051 but it shows error says that the module does not exist. 

the kernel and 5.6 any suggestions?

boxs905.jpegboxs905-modulos.jpeg

Link to post
Share on other sites
17 minutes ago, gilberto said:

 

To find out the information about the BOX, I am posting images of Android with the information, discover the module:  which is the ssv6051 but the error with the command sudo modprobe ssv6051

As I am testing with the new images of Balbes150 I believe that many will have this problem with this wifi.  

 

The images below are from android and show amlogic box. I tried to load the module ssv6051 but it shows error says that the module does not exist. 

the kernel and 5.6 any suggestions?

boxs905.jpegboxs905-modulos.jpeg

I tried this commands

 

root@aml:/lib/modules/5.5.0-rc6-aml-s9xxx/kernel/net# cd wireless/
root@aml:/lib/modules/5.5.0-rc6-aml-s9xxx/kernel/net/wireless# ls
cfg80211.ko             lib80211_crypt_tkip.ko  lib80211.ko
lib80211_crypt_ccmp.ko  lib80211_crypt_wep.ko
root@aml:/lib/modules/5.5.0-rc6-aml-s9xxx/kernel/net/wireless# modprobe ssv6051
modprobe: FATAL: Module ssv6051 not found in directory /lib/modules/5.5.0-rc6-aml-s9xxx
root@aml:/lib/modules/5.5.0-rc6-aml-s9xxx/kernel/net/wireless# 
 

Link to post
Share on other sites
On 5/23/2020 at 11:31 AM, balbes150 said:

It would be interesting to compare the results of the build process on different TV boxes (chips) with different media.

I pulled you latest Build-Armbian tree yesterday to attempt a native build on some of my hardware.  I got the following error:

 

...

  DTC     arch/arm/dts/rk3399-rockpro64.dtb
  SHIPPED dts/dt.dtb
  FDTGREP dts/dt-spl.dtb
  CAT     u-boot-dtb.bin
Image Type:   Rockchip RK33 (SD/MMC) boot image
Data Size:    73728 bytes
warning: TCG doesn't support requested feature: CPUID.01H:ECX.vmx [bit 5]
/lib64/ld-linux-x86-64.so.2: No such file or directory
warning: TCG doesn't support requested feature: CPUID.01H:ECX.vmx [bit 5]
/lib64/ld-linux-x86-64.so.2: No such file or directory
[ error ] ERROR in function compile_uboot [ compilation.sh:227 ]
[ error ] U-boot file not found [ uboot.img ]
[ o.k. ] Process terminated 

(I was attempting the following build:  Full OS Image, arm-64, bionic, server, standard).

Should your Build-Armbian github repo be working for native builds?

I haven't tried to debug this error yet, just wanted to check with you if you felt this should work given what you have checked into your github repository.

Link to post
Share on other sites
33 minutes ago, SteeMan said:

(I was attempting the following build:  Full OS Image, arm-64, bionic, server, standard).

Should your Build-Armbian github repo be working for native builds?

I haven't tried to debug this error yet, just wanted to check with you if you felt this should work given what you have checked into your github repository.

What system do you run the build on ? And write in detail, all the steps that you do.

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

/lib64/ld-linux-x86-64.so.2: No such file or director

Judging from this line, you didn't use the latest Armbian Bionic image. Only they have all the pre-settings for the correct operation of the build system.

Link to post
Share on other sites
10 minutes ago, balbes150 said:

Judging from this line, you didn't use the latest Armbian Bionic image. Only they have all the pre-settings for the correct operation of the build system.

So I need a new install of a current image, and I can't use an environment that has been upgraded?  Correct?  I will try that when I have a chance.  Thanks

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

 

So I need a new install of a current image, and I can't use an environment that has been upgraded?  Correct?  I will try that when I have a chance.  Thanks

You can use the current system, but you need to manually add two directories\files to work with qemu (you can take them from the last finished image), see the log, it will indicate what is missing. The rest should work and install automatically.

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

 

One suggestion is to forget about this WiFi chip and use a USB chip.

 

 

 

Mr. Balbes 150 or do you think you can try to compile this code in the kernel? libreelec people use this driver, would it be cool to put it in your images? I'll try to compile !!! What kernel header should I use I didn't find s9xx. the code below looks promising to me

 

http://kszaq.libreelec.tv/sources/ssv6xxx-1041e7d.tar.gz

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

If you want to try it, it's your right. I won't waste any more time answering you.

 

I am sorry you are right, I just wanted to help I discovered this in my research.

 

The company making the SV6051P wifi chip went bankrupt.
So you won't get any new Android OS with that driver or old ones where the driver didn't exist.
Linux kernel developers also said they won't update the driver for newer kernels and mainline it because it's in a terrible state and it must go extinct.
It's a very bad idea to buy such no-name devices, now later on you sit with problems.

Link to post
Share on other sites
On 5/20/2020 at 6:25 AM, amirul said:

Runs OK on rk3399 Magicsee N6 Max, without the additional dd u-boot step

 

Can you tell us which DTB are you using ? Tried /dtb/rockchip/rk3399-rock-pi-4.dtb and it boots but it cannot detect SD card so it cannot mount the rootfs :( 

 

Or you boot with USB pendrive ?

 

TIA

Link to post
Share on other sites

Hi, I want to install hass.io in my old amlogic Tv-Box and transform it in my server. It is a mini m8s with s905 chipset, 2 GB Ram and 8 GB Rom (not mini m8s II) 

https://androidpc.es/review-mini-m8s/

 

First I need install Linux, but I am not sure which. .img and dtb files I have to use.  Someone could help me?. 

Thanks a lot in avance. 

Link to post
Share on other sites
5 hours ago, Juanjo said:

 

Can you tell us which DTB are you using ? Tried /dtb/rockchip/rk3399-rock-pi-4.dtb and it boots but it cannot detect SD card so it cannot mount the rootfs :( 

 

Or you boot with USB pendrive ?

 

TIA

The dtb I used is a variant to run 1.7 and 2.02 GHz. I am booting bionic desktop fine from sdcard but focal seems to have the rootfs problem

rk3399-rock-pi-4-2-5.7.dtb

Link to post
Share on other sites
Guest
This topic is now closed to further replies.