Nick A

@Piotr si guess this problem doesn’t exist with miniarch. I’ll have to update my build to 6.16 kernel with warpme patches. I’m busy right now so it might take awhile.

@ARx8 try miniarch. https://github.com/warpme/miniarch/releases/tag/f3b14fbae071 I think this box is having the same issue as yours?

Connect using 5037

@buzz89In oranges zero2 dts it has a 3.3v regulator defined as reg_dcdce. There’s only 5v defined in the vontar dts. You can add this to your dts reg_dcdce: dcdce { regulator-always-on; regulator-min-microvolt = <3300000>; regulator-max-microvolt = <3300000>; regulator-name = "vcc-eth-mmc"; }; https://linux.googlesource.com/linux/kernel/git/bpf/bpf/+/refs/tags/v6.9-rc2/arch/arm64/boot/dts/allwinner/sun50i-h616-orangepi-zero2.dts you can borrow code off these boards as well https://linux-sunxi.org/index.php?search=RTL8211F&title=Special%3ASearch&go=Go if you can extract your android dts for more clues.

@ARx8X98h has a similar AIC8800D wifi chip. You could probably use the wifi section from x98h dts. I have never had problems with my sdcard. Maybe it’s a bad solder joint?

RTL8211F Is an external gigabit chip. Maybe this post will help.

@ARx8 try using the x98h image.

@Piotr s im using the same warpme patches so it’s odd that it doesn’t boot. To show more information on your console screen change your loglevel to 7 in armbianEnv.txt. The file is located at the root directory of your sdcard.

@Piotr sTry this image https://github.com/NickAlilovic/build/releases/download/20250306/Armbian-unofficial_25.05.0-trunk_X96q-lpddr3_bookworm_edge_6.12.11_xfce_desktop.img.xz to fix Ethernet you need to edit this file https://github.com/NickAlilovic/build/blob/v20250306/patch/u-boot/u-boot-h616/159-add-x96-q-lpddr3-v1.3-defconfig.patch. Change 16 to 0. Then compile a new image. +&mdio1 { + rmii_phy: ethernet-phy@0 { + compatible = "ethernet-phy-ieee802.3-c22"; + reg = <0>; + }; +}; more information can be found here

@buzz89

Wifi chip model?

@zink try these images https://github.com/NickAlilovic/build/releases/tag/20250306

Try this image https://github.com/NickAlilovic/build/releases/download/20250306/Armbian-unofficial_25.05.0-trunk_X98h_bookworm_edge_6.12.11_xfce_desktop.img.xz

@mdidis do non secure boot images show any output. The one posted is an android uboot output.

@dale there’s a new patch to fix boards without external 32k clock. I haven’t tested it yet. https://github.com/warpme/minimyth2/commit/728a14a73924e349fe88fb4def7e5f50a79aed5c

@mdidisDid you compile with the secure boot patch? Because it sounds like that’s your issue. If secure boot is not enabled you won’t get any output from your serial interface. post your dts. I’ll tell you the correct gpio for wifi and emmc.

@Ducdanh Nguyen hard to tell. I don’t see any markings for uart. It’s not going to be easy to debug your board.

@Randlin have you tried adding secure boot to @sicxnull build. If that doesn’t work you’ll need to play with the dram code. I don’t have time or a 1.5g board. https://github.com/sicXnull/armbian-build/tree/X96Q-TVBOX-LPDDR3

@RandlinTry removing 110,111,113 patches in my uboot. Then add https://github.com/armbian/build/blob/main/patch/u-boot/v2025-sunxi/0009-sunxi-h616-dram-support-1.5GB-RAM-size.patch

“This DRAM setup is currently not supported. resetting “ You need to extract your boot0 and use sunxi-fw to read your dram settings. sunxi-fw info -v boot0.bin Go back one page.

https://github.com/NickAlilovic/build/releases/ [01.296]secure enable bit: 1 I see this in your android log so I believe you have to enable secure boot. If the images don’t boot. These are the steps to enable secure boot for tanix_tx6s_axp313. (Link below) [01.303]PMU: AXP1530 You have a axp313a so transpeed, x98h and tanix might work for you. [359]DRAM Type =3 (3:DDR3,4:DDR4,7:LPDDR3,8:LPDDR4) Transpeed, x98h and tanix use ddr3 If emmc or wifi do not work. You can use your android dts to find the gpio numbers. You might also need to take a picture of your wifi chip.

@mdidis try the transpeed or x98h image. You might need to enable secure boot.

@jdie both of those are android logs

Orange pi zero 3 with 1.5g had the same problem too.. I think they used the 1.5g hardcoded patch to fix it. You might have to remove the newer ram size detection patch. I haven’t updated warpme patches in awhile so I’m hoping this bug has been fixed.