mantouboji

Try to set the disabled status for the GPU node.
or temporarily disable this patch:
patch/kernel/archive/sunxi-6.12/series.conf#L472

Seems indeed broken for H61*
H6 is fine.

Hi. It's probably a bit late. On OrangePi Zero2 thereis i2c3 interface. Thus you must create your own DT overlay for i2c3 interface. See https://github.com/armbian/sunxi-DT-overlays/blob/master/sun50i-h6/sun50i-h6-i2c2.dts as an example. Let's say you create file sun50i-h6-i2c3.dts:
/dts-v1/; /plugin/; / { compatible = "allwinner,sun50i-h6"; fragment@0 { target-path = "/aliases"; __overlay__ { i2c3 = "/soc/i2c@5002c00"; }; }; fragment@1 { target = <&i2c3>; __overlay__ { pinctrl-names = "default"; pinctrl-0 = <&i2c3_ph_pins>; status = "okay"; }; }; };  
Compile this file into a binary device-tree overlay blob:
dtc -I dts -O dtb -o sun50i-h6-i2c3.dtbo sun50i-h6-i2c3.dts  
Set permmissions and copy compiled file into /boot/dtb/allwinner/overlay:
chmod +x ./sun50i-h6-i2c3.dtbo sudo cp ./sun50i-h6-i2c3.dtbo /boot/dtb/allwinner/overlay
Then use the following in your armbianEnv.txt:
overlay_prefix=sun50i-h6 overlay=i2c3  

Yes, it was fixed as part of https://github.com/armbian/build/pull/6040

FYI, I ported wifi driver to mainline (top two commits): https://github.com/jernejsk/linux-1/commits/h616-full
To say that code is convoluted is a big understatement.

Use:
 
 ./compile.sh CREATE_PATCHES="yes"
change sources when asked and a patch will be created / updated. Once done, copy that patch to the patck/kernel/sunxi64-edge/ folder and pay attention to the patch executing order. Hint - if you need that patch is executed last, add higher number or simply xx in front of the patch filename.
 
For adding an overlay, check this patch: https://github.com/armbian/build/blob/master/patch/kernel/archive/sunxi-5.15/general-sunxi-overlays.patch

As mentioned by @mantouboji 5.13 is working well for the moment with the relevant patches. Though we are missing, among others,  overlays and wifi.
Regarding overlays, I tried to compile w1-gpio-cl but I had issues with the headers on 5.13. Did anyone manage to compile anything with 5.13?
Regarding wifi, as this is new AW hw,  I expect that we need to port the driver from the ventor's legacy sdk. Is anyone familiar with the process? 

Successfully built & booted kernel 5.13.rc1 using mainline ATF, mainline uboot and this kernel source.
Ethernet & usb works, reboot does not. More tests in the next few days
Armbianmonitor

After some hack,  I use the SPI port on OPi One to connect with a MAX6675 board. 
 
The SPI port on One is SPI0,  so armbianEnv.txt should include these:
 
overlays=spi-spidev param_spidev_spi_bus=0 param_spidev_spi_cs=0  
the MAX6675 connects to OPi One as:
 
MAX6675                       One GPIO
------------------------------------------
VCC                                 PIN17
GND                                PIN20
SCK                                 PIN23
CS                                   PIN24
SO                                  PIN21
 
 
Then use the attachment program to read from MAX6675
readmax6675.c

After some hack,  I use the SPI port on OPi One to connect with a MAX6675 board. 
 
The SPI port on One is SPI0,  so armbianEnv.txt should include these:
 
overlays=spi-spidev param_spidev_spi_bus=0 param_spidev_spi_cs=0  
the MAX6675 connects to OPi One as:
 
MAX6675                       One GPIO
------------------------------------------
VCC                                 PIN17
GND                                PIN20
SCK                                 PIN23
CS                                   PIN24
SO                                  PIN21
 
 
Then use the attachment program to read from MAX6675
readmax6675.c

I use PA20,  PIN37. 
 
overlays=w1-gpio usbhost0
param_w1_pin=PA20

I use the OrangePi Zero.  But it is similar to other model.
 
It's very simple:
 
1) use the mainline 4.11.x kernel 
2) enable the uart1 and pps-gpio in /boot/armbianEnv.txt  like this :
  
overlays=uart1 pps-gpio param_pps_pin=PA7  
3) edit /etc/default/gpsd  to use ttyS1 as gps device
# Devices gpsd should collect to at boot time. # They need to be read/writeable, either by user gpsd or the group dialout. DEVICES="/dev/ttyS1" # Other options you want to pass to gpsd GPSD_OPTIONS="-G -n "  
4) If you use ntpd,  edit /etc/ntpd.conf like this:
# GPS Serial data reference server 127.127.28.0 minpoll 4 maxpoll 4 prefer fudge 127.127.28.0 time1 0.135 refid GPS server 127.127.22.0 maxpoll 4 # ATOM(PPS) fudge 127.127.22.0 flag3 1 # enable PPS API  
5) Or if you prefer crony rather than ntp, install chrony instead of ntp, edit /etc/chrony/chrony.conf , add this to end of it:
refclock SHM 0 refid GPS precision 1e-1 offset 0.134 delay 0.2 noselect refclock PPS /dev/pps0 lock GPS 6) connect GPS module to UART1 
    GPS      Zero
---------------------
   TXD        UART1_RX PIN10
   RXD        UART1_TX  PIN8
  PPS          IO-1  PIN12
 
7)  use ntpq -p  or chrony sources. to check it.
 

I use the OrangePi Zero.  But it is similar to other model.
 
It's very simple:
 
1) use the mainline 4.11.x kernel 
2) enable the uart1 and pps-gpio in /boot/armbianEnv.txt  like this :
  
overlays=uart1 pps-gpio param_pps_pin=PA7  
3) edit /etc/default/gpsd  to use ttyS1 as gps device
# Devices gpsd should collect to at boot time. # They need to be read/writeable, either by user gpsd or the group dialout. DEVICES="/dev/ttyS1" # Other options you want to pass to gpsd GPSD_OPTIONS="-G -n "  
4) If you use ntpd,  edit /etc/ntpd.conf like this:
# GPS Serial data reference server 127.127.28.0 minpoll 4 maxpoll 4 prefer fudge 127.127.28.0 time1 0.135 refid GPS server 127.127.22.0 maxpoll 4 # ATOM(PPS) fudge 127.127.22.0 flag3 1 # enable PPS API  
5) Or if you prefer crony rather than ntp, install chrony instead of ntp, edit /etc/chrony/chrony.conf , add this to end of it:
refclock SHM 0 refid GPS precision 1e-1 offset 0.134 delay 0.2 noselect refclock PPS /dev/pps0 lock GPS 6) connect GPS module to UART1 
    GPS      Zero
---------------------
   TXD        UART1_RX PIN10
   RXD        UART1_TX  PIN8
  PPS          IO-1  PIN12
 
7)  use ntpq -p  or chrony sources. to check it.
 

I use the OrangePi Zero.  But it is similar to other model.
 
It's very simple:
 
1) use the mainline 4.11.x kernel 
2) enable the uart1 and pps-gpio in /boot/armbianEnv.txt  like this :
  
overlays=uart1 pps-gpio param_pps_pin=PA7  
3) edit /etc/default/gpsd  to use ttyS1 as gps device
# Devices gpsd should collect to at boot time. # They need to be read/writeable, either by user gpsd or the group dialout. DEVICES="/dev/ttyS1" # Other options you want to pass to gpsd GPSD_OPTIONS="-G -n "  
4) If you use ntpd,  edit /etc/ntpd.conf like this:
# GPS Serial data reference server 127.127.28.0 minpoll 4 maxpoll 4 prefer fudge 127.127.28.0 time1 0.135 refid GPS server 127.127.22.0 maxpoll 4 # ATOM(PPS) fudge 127.127.22.0 flag3 1 # enable PPS API  
5) Or if you prefer crony rather than ntp, install chrony instead of ntp, edit /etc/chrony/chrony.conf , add this to end of it:
refclock SHM 0 refid GPS precision 1e-1 offset 0.134 delay 0.2 noselect refclock PPS /dev/pps0 lock GPS 6) connect GPS module to UART1 
    GPS      Zero
---------------------
   TXD        UART1_RX PIN10
   RXD        UART1_TX  PIN8
  PPS          IO-1  PIN12
 
7)  use ntpq -p  or chrony sources. to check it.