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

[balbes150]

53 minutes ago, phicommN1 said:

4.  aml-s9xxx

arm-64

 

 

[phicommN1]

2 hours ago, balbes150 said:

arm-64

 

 

I really thank you for your help, it done!

[l33chy]

Hi everyone!

First of all, I just stumbled upon Armbian and balbes Images. Incredible work! I got my "MX pro 4k" to boot the buster image using the generic meson_gxbb-p201.dtb 

Ethernet is working fine, however wifi is not (RTL8189etv chipset). I can imagine that the DTB doesn't contain the proper entries for this chipset. I've tried all gxbb DTBs but none of them load the Realtek module.

Has anyone got wifi to work and/or is anyone willing to share some info how I could make this work?

Would decompiling the p201 DTB and updating it with info from a DTB with rtl support, then compile again, work?

 

Any hints would be much appreciated!

Thanks,

l33chy 

[amirdelta]

hi

after installing new version (20.05.1)

As i usually use telnet to access the device,

 I have a long long annoying delay in responses sent from server via SSH and SFTP .

Does anybody else encountered same issue in tests ?

I have s905x-p212 2G board- installed to Emmc

 

ps : I've  had enabled RDP in config before but i'm not sure about the Interference.

[dbsharpe]

50 minutes ago, amirdelta said:

hi

after installing new version (20.05.1)

As i usually use telnet to access the device,

 I have a long long annoying delay in responses sent from server via SSH and SFTP .

 

Have a look at https://forum.armbian.com/topic/12162-single-armbian-image-for-rk-aml-aw/page/10/?tab=comments#comment-96403

So that will be selinux=0 at the end of the APPEND= line in /boot/uEnv.txt

It's only a work around but it would be nice to get a fix.

[zanfi]

On 3/8/2020 at 12:26 PM, gounthar said:

Has anyone tested any AllWinner H616 based box?
I have one, and will give it a try.

Hi gounthar, some hope for armbian on a H616 soc?

[Beppe]

On 4/6/2020 at 11:59 AM, balbes150 said:

 

Use images from this link.

https://yadi.sk/d/V29-iMTUiq043Q

Hi @balbes150,

unfortunately i can't boot...

I have writed Armbian_20.05.0_Rk3328-tv_buster_current_5.6.0-rc4_20200312.img to my SD

Then writed u-boot-rk3328-mvr9.img

But nothing...
Tried also with USB method, but nothing... I don't know what to do

 

Beppe.

[balbes150]

5 minutes ago, Beppe said:

unfortunately i can't boot...

I have writed Armbian_20.05.0_Rk3328-tv_buster_current_5.6.0-rc4_20200312.img to my SD

Then writed u-boot-rk3328-mvr9.img

But nothing...
Tried also with USB method, but nothing... I don't know what to do

If you use an image labeled 3328 in the name, you don't need to write u-boot. Only to complete the configuration of the DTB (rk3328-box.dtb).

 only need to add u-boot for the arm-64 version of the image

[Seb_Lz]

On 4/7/2020 at 2:54 PM, Seb_Lz said:

 

I have a similar issue, also with beelink GT1 2Gb ram (S912): with Armbian_20.05.0_Arm-64_bionic_current_5.6.0-rc6_20200331.img, eth0 and wlan0 eventually started to work using dtb q200 (was NOT the case with previous RC6 img, was previously running an old 4.20 kernel img) BUT today I had a small power failure and on reboot, I started to loose eth0 support again, with following error in kern.log:

Apr  7 14:32:56 localhost kernel: [   11.076849] meson8b-dwmac c9410000.ethernet eth0: no phy at addr -1
Apr  7 14:32:56 localhost kernel: [   11.076859] meson8b-dwmac c9410000.ethernet eth0: stmmac_open: Cannot attach to PHY (error: -19)

 

NB: directly after installing rc6_20200331, I did an apt update + apt upgrade and all went fine (I did not upgrade the kernel), so in my case the problem with eth0 does not seem to be related to upgrading some packages.

Since this error started to appear just after a power failure, could this be linked to some corrupted file ? Any idea how I could restore  them ?

 

Small update on my research to make the image work with Beelink GT1:
After trying a few things, I eventually decided to start again from scratch with Armbian_20.05.1_Arm-64_bionic_current_5.6.0-rc7_20200404.img.xz. After installing, same problem on clean install. I then tried to go back to 20200331 version, which was previously working. To my surprise, and despite using the exact same image (clean format using balenaEtcher), it was also not working anymore ! I thought about an hardware problem, but rebooting on android emmc system prove me wrong as ethernet was there working fine. I then flashed back the SD to 20200404 and used Q201 dtb file. The eth0 interface is recognized but there are still errors in kern.log and the interface is still faulty (can't get an IP from DHCP nor connect to it when set statically):

root@hassio:~# dmesg -T --level=err,warn
[Wed Apr  8 17:02:39 2020] KASLR disabled due to lack of seed
[Wed Apr  8 17:02:41 2020] OCFS2 User DLM kernel interface loaded
[Wed Apr  8 17:02:42 2020] meson8b-dwmac c9410000.ethernet: IRQ eth_wake_irq not found
[Wed Apr  8 17:02:42 2020] meson8b-dwmac c9410000.ethernet: IRQ eth_lpi not found
[Wed Apr  8 17:02:42 2020] meson8b-dwmac c9410000.ethernet: PTP uses main clock
[Wed Apr  8 17:02:42 2020] dwc3 c9000000.dwc3: Failed to get clk 'ref': -2
[Wed Apr  8 17:02:43 2020] phy phy-d0078080.phy.3: unsupported PHY mode 5
[Wed Apr  8 17:02:43 2020] hub 2-0:1.0: config failed, hub doesn't have any ports! (err -19)
[Wed Apr  8 17:02:43 2020] mmc2: queuing unknown CIS tuple 0x80 (2 bytes)
[Wed Apr  8 17:02:43 2020] mmc2: queuing unknown CIS tuple 0x80 (3 bytes)
[Wed Apr  8 17:02:43 2020] mmc2: queuing unknown CIS tuple 0x80 (3 bytes)
[Wed Apr  8 17:02:43 2020] mmc2: queuing unknown CIS tuple 0x80 (7 bytes)
[Wed Apr  8 17:02:47 2020] gx-sound-card sound: ASoC: no DMI vendor name!
[Wed Apr  8 17:02:47 2020] panfrost d00c0000.gpu: d00c0000.gpu supply mali not found, using dummy regulator
[Wed Apr  8 17:02:47 2020] panfrost d00c0000.gpu: GPU Fault 0x00000088 (UNKNOWN) at 0x000000fcffbfffc0
[Wed Apr  8 17:02:48 2020] meson_vdec: module is from the staging directory, the quality is unknown, you have been warned.
[Wed Apr  8 17:02:48 2020] hci_uart_bcm serial0-0: serial0-0 supply vbat not found, using dummy regulator
[Wed Apr  8 17:02:48 2020] hci_uart_bcm serial0-0: serial0-0 supply vddio not found, using dummy regulator
[Wed Apr  8 17:02:48 2020] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio for chip BCM4345/6
[Wed Apr  8 17:02:48 2020] brcmfmac mmc2:0001:1: Direct firmware load for brcm/brcmfmac43455-sdio.amlogic,q201.txt failed with error -2
[Wed Apr  8 17:02:48 2020] bluetooth hci1: Direct firmware load for brcm/BCM4345C0.hcd failed with error -2
[Wed Apr  8 17:02:49 2020] meson8b-dwmac c9410000.ethernet eth0: PTP not supported by HW
[Wed Apr  8 17:02:49 2020] ext4 filesystem being mounted at /var/log supports timestamps until 2038 (0x7fffffff)
[Wed Apr  8 17:02:50 2020] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio for chip BCM4345/6
[Wed Apr  8 17:02:50 2020] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM4345/6 wl0: Feb 27 2018 03:15:32 version 7.45.154 (r684107 CY) FWID 01-4fbe0b04
[Wed Apr  8 17:03:09 2020] process 'docker/tmp/qemu-check033460557/check' started with executable stack
[Wed Apr  8 17:03:12 2020] overlayfs: NFS export requires "index=on", falling back to nfs_export=off.

I've extracted the dtb file from the working Android system and from the 20200404 img and converted them to dts file. I tried to adapt some values in the ethernet@c9410000 {...} part to mimic what is in the android part, but this didn't help (in some cases, it created more errors). I'm really confused how as how to make progress on this, any kind of help would be very welcome (dts files in attachments).

 

android-q201.dts meson-gxm-q201.dts

[amirdelta]

6 hours ago, dbsharpe said:

Have a look at https://forum.armbian.com/topic/12162-single-armbian-image-for-rk-aml-aw/page/10/?tab=comments#comment-96403

So that will be selinux=0 at the end of the APPEND= line in /boot/uEnv.txt

It's only a work around but it would be nice to get a fix.

Thanks man

it's now better, but not fully gone.

I thought I'm the first encountering such a problem.

I'm not lazy :-)  

[Turgus]

Thanks @balbes150 for the good work!

I just turned another x96mini 2/16 into mini-desktop with Armbian_20.05.1_Arm-64_bionic_current_5.6.2_desktop_20200408.img.xz
Everything works as expected (on this board revision 4.0 even with wifi & bt) from eMMC so far. While configuring I had also sound via hdmi on testvideo, but now it works remote with hdmi-dummy-monitor and additional (passive) cooling.

On Armbian_20.05.1_Arm-64_bionic_current_5.6.0-rc7_desktop_20200404.img.xz I had an error "some parts of the hardware might not work like expected"(something similar was shown), but before searching deeper I placed 200408 on the card, which worked directly(after changing dtb in uEnv.txt)..

 

 

 

Btw. On this strange eachlink H6mini / flowfon f1 box I still couldn't boot anything useful, no matter which LE/armbian/usb/sd/u-boot/append/dtb combination I tried and uart gives just garbage, but I will keep on trying occasionally..

[amirul]

Armbian_20.05.1_Arm-64_bionic_current_5.6.0-rc7_desktop_20200404, zImage & uInitrd from 20200324

 

Armbian_20.05.1_Arm-64_bionic_current_5.6.2_desktop_20200408

 

Magicsee N6 Max RK3399. The level of gray has gone missing. Anyone else seeing this?

[Gausus]

X96 Max Plus s905x3 4G  DTB fix for network and sound.

 

https://drive.google.com/file/d/1jWnRu-GdOL72__X-ea8oI2VRW_x1ENTM/view?usp=sharing

 

Tested on Armbian 20.05.01 20200408.

 

Based on meson-sm1-sei610-ethfix.dtb (network ok no sound) and meson-sm1-sei610-2.dtb (sound hdmi ok no network) found on this forum.

 

If you want to editing DTB you have to convert it to DTS .

 

dtc -I dtb -O dts x.dtb -o x.dts

EDIT  (i use kate)

CONVERT (BACK) dts to dtb

dtc -I dts -O dtb test.dts -o test.dtb

 

Ignore warnings when converting.

 

If some DTB working on network and other working on sound you can copy past to fix.

A lot off trying and failing.

[amirul]

There's linux-image-current-arm-64 thats upgradable. Putting it on hold until the color/gray issue is settled.

[ilsalgo]

Hi everyone, in my box (Beelink Mx II mini S905) wifi e Bluetooth don't work. 

Any idea to fix they? 

[psxsnake]

I have strange things when i try tu install a package

it happens even with sudo apt update

 

 

chris@arm-64:~/klipper/scripts$ ./install-debian.sh

###### Running apt-get update...
Get:1 http://ports.ubuntu.com focal InRelease [265 kB]
Get:3 http://ports.ubuntu.com focal-security InRelease [97.9 kB]               
Get:4 http://ports.ubuntu.com focal-updates InRelease [89.1 kB]                
Get:5 http://ports.ubuntu.com focal-backports InRelease [89.2 kB]              
Get:2 https://apt.armbian.com focal InRelease [18.2 kB]                        
Reading package lists... Done                    
E: Release file for http://ports.ubuntu.com/dists/focal/InRelease is not valid yet (invalid for another 14d 3h 8min 43s). Updates for this repository will not be applied.
E: Release file for http://ports.ubuntu.com/dists/focal-security/InRelease is not valid yet (invalid for another 7d 20h 47min 44s). Updates for this repository will not be applied.
E: Release file for http://ports.ubuntu.com/dists/focal-updates/InRelease is not valid yet (invalid for another 7d 20h 47min 46s). Updates for this repository will not be applied.
E: Release file for http://ports.ubuntu.com/dists/focal-backports/InRelease is not valid yet (invalid for another 7d 20h 47min 59s). Updates for this repository will not be applied.
E: Release file for http://apt.armbian.com/dists/focal/InRelease is not valid yet (invalid for another 13d 2h 35min 25s). Updates for this repository will not be applied.

[SteeMan]

2 hours ago, psxsnake said:

I have strange things when i try tu install a package

it happens even with sudo apt update

E: Release file for http://ports.ubuntu.com/dists/focal/InRelease is not valid yet (invalid for another 14d 3h 8min 43s). Updates for this repository will not be applied.
 

Is your system clock correct? 

[psxsnake]

3 hours ago, SteeMan said:

Is your system clock correct? 

Right... is wrong but i don't have ntp installed so cannot change.. theres another way?

 

found  

date -s "09 APR 2020 21:36"

[agtconf]

Hi.

 

When I try to upgrade my amlogic S912 tvbox with ubuntu bionic 20.05.0 to 20.05.1, the .dtb my tvbox use is gxm-vim-khadas2

 

If I reboot the machine it gets stuck on amlogic boot screen, I've tried to change the .dtb for the one's in the image Armbian_20.05.1_Arm-64_bionic_current_5.6.2_20200408.img.xz but it hasn't work.

 

I've burned the image Armbian_20.05.1_Arm-64_bionic_current_5.6.2_20200408.img on a sd card, I've changed the dtb on uEnv.txt but it hasn't boot it was stuck on amlogic boot screen. When i read the sd card the uEnv.txt was restored to original with no changes.

 

I've restored with a backup  and upgraded all packages except "linux-image-current-arm-64/bionic 20.05.1 arm64 [upgradable from: 20.05.0]" and it works.

 

 

conf@arm-64:~$ sudo apt list --upgradable
Listing... Done
linux-image-current-arm-64/bionic 20.05.1 arm64 [upgradable from: 20.05.0]
N: There are 2 additional versions. Please use the '-a' switch to see them.
conf@arm-64:~$ sudo apt list -a --upgradable
Listing... Done
linux-image-current-arm-64/bionic 20.05.1 arm64 [upgradable from: 20.05.0]
linux-image-current-arm-64/bionic,now 20.05.0 arm64 [installed,upgradable to: 20.05.1]
linux-image-current-arm-64/bionic 19.11.5 arm64

 

Any idea?

 

 

 

[Binbin Qian]

Hi there, I have a S905M device, I installed Armbian_20.05.1_Arm-64_bionic_current_5.6.0-rc7_20200404.img to eMMC with install-aml-s905.sh and it works well, but it can't boot from u-disk any more, even holding the reset button when booting, is it possible to boot from u-disk? This image looks like a server version, but why is it so big, 5.24GB? Thanks in advance.

[gusnau]

20 hours ago, Gausus said:

X96 Max Plus s905x3 4G  DTB fix for network and sound.

 

https://drive.google.com/file/d/1jWnRu-GdOL72__X-ea8oI2VRW_x1ENTM/view?usp=sharing

 

Tested on Armbian 20.05.01 20200408.

 

Based on meson-sm1-sei610-ethfix.dtb (network ok no sound) and meson-sm1-sei610-2.dtb (sound hdmi ok no network) found on this forum.

 

Thanks, ethernet confirmed working, but only on 100Mbps. Do you have any idea to make it working on 1Gbps?

[Ricardo JL Rufino]

On 3/7/2020 at 5:48 PM, rossbcan said:

whoohoo!! solved: No Wifi Tanix TX92

 

I did all the heavy lifting on this. Please incorporate changes in build (if you want), including the firmware

    patch from https://www.spinics.net/lists/linux-wireless/msg190482.html
    to patch/kernel/aml-s9xxx-current/qca9377_hw1.1.patch
    on target:
        hint: https://github.com/erstrom/linux-ath/issues/9
        cd /tmp; git clone -b bd-sdmac https://github.com/erstrom/ath10k-firmware.git
        mkdir /lib/firmware/ath10k; cp -rf ath10k-firmware/QCA9887/ /lib/firmware/ath10k
        cp /lib/firmware/ath10k/QCA9377/hw1.0/firmware-5.bin_WLAN.TF.1.0-00267-1 /lib/firmware/ath10k/QCA9377/hw1.0/firmware-5.bin
        cp /lib/firmware/ath10k/QCA9377/hw1.0/untested/firmware-sdio-5.bin_WLAN.TF.1.1.1-00061-QCATFSWPZ-1 /lib/firmware/ath10k/QCA9377/hw1.0/firmware-sdio-5.bin

 

Regards;

Bill

qca9377_hw1.1.patch 1.71 kB · 27 downloads

 

WiFi Working !! thanks

My Board: Tx8 - S905W 2GB

Using DTB: dtb_meson-gxl-s905w-p281.dtb

Image: Armbian_20.05.0_Arm-64_bionic_current_5.6.0-rc6_desktop_20200403.img.xz

No patch required, only copy files:

 

cd /tmp; 
git clone --depth=1 https://github.com/erstrom/ath10k-firmware
mkdir /lib/firmware/ath10k; cp -rf ath10k-firmware/QCA9377/ /lib/firmware/ath10k
cd /lib/firmware/ath10k/QCA9377/hw1.0/
cp firmware-5.bin_WLAN.TF.1.0-00267-1 firmware-5.bin
cp untested/firmware-sdio-5.bin_WLAN.TF.1.1.1-00061-QCATFSWPZ-1 firmware-sdio-5.bin

 

[ilsalgo]

19 minutes ago, Ricardo JL Rufino said:

 

WiFi Working !! thanks

My Board: Tx8 - S905W 2GB

Using DTB: dtb_meson-gxl-s905w-p281.dtb

Image: Armbian_20.05.0_Arm-64_bionic_current_5.6.0-rc6_desktop_20200403.img.xz

No patch required, only copy files:

 

cd /tmp; 
git clone --depth=1 https://github.com/erstrom/ath10k-firmware
mkdir /lib/firmware/ath10k; cp -rf ath10k-firmware/QCA9377/ /lib/firmware/ath10k
cd /lib/firmware/ath10k/QCA9377/hw1.0/
cp firmware-5.bin_WLAN.TF.1.0-00267-1 firmware-5.bin
cp untested/firmware-sdio-5.bin_WLAN.TF.1.1.1-00061-QCATFSWPZ-1 firmware-sdio-5.bin

 

Incredibile! This also work for me!! Thanks you so much. 

Only Bluetooth don't work. 

[SteeMan]

On 3/7/2020 at 3:48 PM, rossbcan said:

whoohoo!! solved: No Wifi Tanix TX92

 

I did all the heavy lifting on this. Please incorporate changes in build (if you want), including the firmware

    patch from https://www.spinics.net/lists/linux-wireless/msg190482.html
    to patch/kernel/aml-s9xxx-current/qca9377_hw1.1.patch
    on target:
        hint: https://github.com/erstrom/linux-ath/issues/9
        cd /tmp; git clone -b bd-sdmac https://github.com/erstrom/ath10k-firmware.git
        mkdir /lib/firmware/ath10k; cp -rf ath10k-firmware/QCA9887/ /lib/firmware/ath10k
        cp /lib/firmware/ath10k/QCA9377/hw1.0/firmware-5.bin_WLAN.TF.1.0-00267-1 /lib/firmware/ath10k/QCA9377/hw1.0/firmware-5.bin
        cp /lib/firmware/ath10k/QCA9377/hw1.0/untested/firmware-sdio-5.bin_WLAN.TF.1.1.1-00061-QCATFSWPZ-1 /lib/firmware/ath10k/QCA9377/hw1.0/firmware-sdio-5.bin

 

Regards;

Bill

qca9377_hw1.1.patch 1.71 kB · 29 downloads

First off, I want to say thank you for contributing.  We need all the help around here that we can get.

 

However, a patch like this is a example of the problems that Armbian faces (and probably to even a greater extent that the Armbian for TV boxes fork faces). 

 

There are probably hundreds of different android TV boxes being manufactured.  Each with a lot of inexpensive components - wifi chips, bluetooth, ethernet, etc.  In an ideal world each manufacturer would support their products and incorporate their drivers into the mainline kernel.  But this isn't an ideal world, and many of these chips have no support by the manufacturer (probably no source code, rarely any bug fixes, security updates are unlikely).  That kind of works in the android world as the kernel version is fixed and there isn't an expectation of updates or long term support. 

 

But here in the Armbian world, end users expect that there will be long term support and security and bug fix updates.  But that becomes very difficult if the upstream chip builders don't support their products.  It isn't sustainable for the limited Armbian developers to spend all their time tracking down and then maintaining hundreds of patches for all these different drivers over a period of years.  Therefore you will see in Armbian a desire to put effort into areas where the upstream code can be integrated into the mainline kernel (hopefully by the original manufacturer), so that patches only need to be maintained for a couple of kernel release cycles as the code get integrated into mainline. 

 

So while I know nothing about the wifi chip that your supplied patch supports, it there isn't an effort by someone upstream to be integrating that into the mainline kernel, it probably doesn't make sense for it to be incorporated here.  The long term maintenance costs aren't worth the effort. While there certainly are exceptions, that is how I see the reality of being of the current Armbian environment.  The project is not able to support the wide variety of components that exist in all the different SBC's and TV boxes being produced today or over the last 5 years, so the effort goes to where there is the most support from upstream suppliers.

[imrannaqvi83]

Hi Everyone,

I have Sunvell Q Plus Allwinner H6 soc with 4GB/32GB, i am trying to install armbian (Armbian_20.05.0_Arm-64_buster_current_5.6.0-rc6_20200403.img.xz) from sd-card.

One quirk about this device is that reset button doesnot work, its rooted and so i can go to shell and type su, reboot recovery to go to recovery but that is not much helpfull to me, or i don't know if it is useful.

 

What i did so far.

 

1. written Armbian_20.05.0_Arm-64_buster_current_5.6.0-rc6_20200403.img.xz to sdcard in windows 10 using Win32diskImager.
2. From sd-card, removed .aw from all 4 allwinnder files with replaced existing files.
3. updated uEnv.txt to use
   • FDT=/dtb/allwinner/sun50i-h6-tanix-tx6.dtb
   • APPEND=root=LABEL=ROOTFS rootflags=data=writeback rw console=ttyS0,115200 console=tty0 no_console_suspend consoleblank=0 fsck.fix=yes fsck.repair=yes net.ifnames=0
4. Did not knew what is the procedure is to writing uboot files so just copied (u-boot-allwinner-h6-tanix-tx6.img) to sd-card as u-boot.ext

But device is not booting from sd-card.

Please let me know if you need some other information, i am not sure about step 4 but i don't know what to do next.

[balbes150]

53 minutes ago, imrannaqvi83 said:

1. Did not knew what is the procedure is to writing uboot files so just copied (u-boot-allwinner-h6-tanix-tx6.img) to sd-card as u-boot.ext

 

Not copy, but write , just as you write an image.

[imrannaqvi83]

5 hours ago, balbes150 said:

Not copy, but write , just as you write an image.

 Hi @balbes150

Thanks for your quick reply, but sorry for my ignorance I did not understood that. I am on Windows 10 and using Win32DiskImager. After writing main armbian image there are two partitions on sd card. One is boot partitiin which is fat32 and other not visible in Windows.

Writting uboot image will overwrite contents of boot partition.

Is it suppose to be or I need some other program which will not overwrite boot partition? This is just my assumption, I did not tried. Will try that asap.

[balbes150]

8 hours ago, imrannaqvi83 said:

Writting uboot image will overwrite contents of boot partition.

Carefully read the first message of the topic from this place onwards.

***********************************************

Rules for using the new u-boot option.

[legogris]

On 4/4/2020 at 8:19 PM, balbes150 said:

All sources with documents are regularly updated in my GIT (Build-Armbian).

Awesome, thanks, I somehow missed that despite searching around! Maybe you want to put that in the top post :)

(For anyone else: https://github.com/150balbes/Build-Armbian)

[imrannaqvi83]

2 hours ago, balbes150 said:

Carefully read the first message of the topic from this place onwards.

***********************************************

Rules for using the new u-boot option.

Thanks @balbes150

After writing u-boot to boot partition, i tried few dtbs and able to boot from only /dtb/allwinner/sun50i-h6-pine-h64-model-b.dtb but initial setup drops to shell with error "alert lable:rootfs doesnot exist"

I am not sure if i am using the correct versions of files, but only this combination boots at all.

 

 

armbian-image: Armbian_20.05.0_Arm-64_buster_current_5.6.0-rc6_20200403.img
u-boot:u-boot-allwinner-h6-tanix-tx6.img

 

 

 

uEnv.txt:

----------

LINUX=/zImage
INITRD=/uInitrd

# aw h6
FDT=/dtb/allwinner/sun50i-h6-pine-h64-model-b.dtb
APPEND=root=LABEL=ROOTFS rootflags=data=writeback rw console=ttyS0,115200 console=tty0 no_console_suspend consoleblank=0 fsck.fix=yes fsck.repair=yes net.ifnames=0