Nick A

@qq20739111 The only change I can think of is the Thermal Governor is set to STEP_WISE by default. Without it the fan would run full speed all the time. Radxa had it set to CONFIG_THERMAL_DEFAULT_GOV_POWER_ALLOCATOR=y . I guess it would be safer to switch back to POWER_ALLOCATOR and figure another way to fix the fan issue. The 0.6.x images don't have these changes. Is this an image you compiled yourself? The CPU needs proper cooling you should install one of these. https://radxa.com/products/accessories/heatsink-6530b Extreme throttling introduced on A733 https://forum.radxa.com/t/extreme-throttling-introduced-on-a733/30688/4

@Sergioclr Try this build. If Ethernet works then we can borrow the dts settings.

@tiobily https://radxa.com/community Try these forums.

@Sergioclr Well that is the u-boot root directory. Where the main Makefile is located. I added my own root_key.pem in the patch. You don't have to generate one. The root_key.pem for Allwinner H616/618/313 devices is not a single, universal file, but rather an RSA private key file used for signing bootloader images (TOC0) in secure boot implementations. In many commercial H616-based TV boxes, Secure Boot is enabled by the manufacturer, but the efuses (which store the root key hash) are not permanently locked, allowing the use of custom keys openssl genrsa -out root_key.pem

@Sergioclr Search the forums for "PL2303HXA". I think it will work. After you compile your build, check build/cache/sources/u-boot-worktree/u-boot*; you should find root_key.pem there

@Sergioclr Those unpopulated pads in the top-left corner are likely the UART (Serial) debug port. Check the underside of the board—are the pads labeled GND, TX, and RX there? The most reliable way to boot Linux on this box is to use a USB-to-UART TTL adapter. Without one, we’re essentially working blind.

@Sergioclr are you sure the board has secure boot enabled? You should install a USB-to-UART TTL device.

@Sergioclr Try this one next. 159-add-x96-q-lpddr3-v1.3-defconfig.patch

@Sergioclr can you find a AXP chip on your board? It’s safer to boot images with the same AXP chip. I haven’t bricked any of my boxes. Don’t use armbian-config’s write to emmc until you have a stable image.

@Sergioclryou are only adding one line of code.. so whatever it is just add one. 162 would be 163.

@qq20739111 I'll add it soon. 6.18 might take awhile.

@HenricoLegal https://forum.armbian.com/topic/57960-sv6256p-wifi-now-working-on-linux-6x-armbian-tested/

@Sergioclr you can also try a newer branch https://github.com/NickAlilovic/build/tree/v20251014 https://github.com/NickAlilovic/build/tree/v20251014?tab=readme-ov-file#build-host-requirements

@Sergioclr Requirements for self hosted x86_64 / aarch64 machine at least 2GB of memory and ~35GB of disk space for VM, container or bare metal installation Armbian / Ubuntu Jammy 22.04.x for native building or any Docker capable Linux for containerised Windows 10/11 with WSL2 subsystem running Ubuntu Jammy 22.04.x Superuser rights (configured sudo or root access). Make sure your system is up-to-date! Outdated Docker binaries, for example, can cause trouble.

@Sergioclr the H313, H616, H618, and IK316 are essentially the same SoC family. To successfully boot an image, you must match the correct AXP chip (the Power Management IC) and the specific DRAM version used on your board. Essentially, any thread discussing the H616/H618 (excluding older H3/H5/H6 chips) will contain relevant information for these SoCs. PMIC Information: http://linux-sunxi.org/AXP_PMICs DRAM Types: 3: DDR3 4: DDR4 7: LPDDR3 8: LPDDR4 You can try flashing various boot images until one successfully initializes your hardware. (If your box is secure-boot enabled, you will need to add the secure-boot modifications posted above.) https://github.com/NickAlilovic/build/releases/tag/20250306 Alternatively, for a more precise approach: Extract your Device Tree (DTS). Identify the specific AXP chip located on your board. Connect a USB-to-UART TTL device to the RX, TX, and GND pins on your board to monitor the boot sequence. https://forum.armbian.com/topic/29794-how-to-install-armbian-in-h618/#findComment-232411 https://forum.armbian.com/topic/29794-how-to-install-armbian-in-h618/page/4/#findComment-187672 https://forum.armbian.com/topic/29794-how-to-install-armbian-in-h618/page/23/#findComment-218660 https://docs.radxa.com/en/rock5/rock5itx/radxa-os/serial?os=windows https://linux-sunxi.org/UART https://www.amazon.ca/IZOKEE-CP2102-Converter-Adapter-Downloader/dp/B07D6LLX19/ref=sr_1_2_mod_primary_new Decompile your Device Tree Blob (DTB😞 dtc -I dtb -O dts -o source.dts source.dtb For a visual reference of a board using these specific chips, check out this hardware breakdown. http://nskhuman.ru/allwinner/krugh618.php?np=3

@Ducdanh Nguyen probably a real H313 SOC. You know this! You were on the other thread.

@HenricoLegal can you find the wifi chip on your board?

@mrdeathjr Mainline Linux support for the A733 is still in its early stages. I currently have a Armbian build using a collection of patches sourced from the kernel mailing lists. However, I’m getting a lot of errors and haven't managed to boot to a login prompt. https://oftc.catirclogs.org/linux-sunxi/2026-03-23 13:07 <indy> hi all, is there any a733 upstreaming effort? 13:29 <apritzel> indy: effort is underway: pinctrl is WIP (patches have been on the list), and the clock patches have recently been posted 13:30 <apritzel> RTC and AXP are on the list as well, that would conclude the basic necessities to get a DT merged that wouldn't break in the future 15:25 <indy> apritzel_, is it targeted for 7.0? 15:29 <apritzel> indy: no, that's way too late, v7.0 is due to be released in like three weeks already. It's even too late now for v7.1. 15:30 <apritzel> and it's the usual bottleneck: reviews ... I hope I find some time soon to look at the clock patches With @alexc hard work porting the v1.4.8 BSP driver to kernel 6.18, I was able to create a working Armbian build for the Radxa A7Z. https://github.com/NickAlilovic/build/tree/Radxa-mainline-WIP

@thanh_tan This looks like an AI-generated adaptation of my Radxa Cubie A7Z Armbian build. The Orange Pi 4 Pro uses the same Allwinner A733, so the family config is shared, but Radxa's BSP isn't directly compatible with the Orange Pi 4 Pro without board-specific modifications. Looking at the repo, it's very early stage — The write_uboot_platform() function is just a stub that does nothing, and it's relying on whatever bootloader is already on the SD card. I wouldn't expect it to actually boot on real hardware in its current state.

@Octavio Cuatrochio I just noticed your link in the first post. The board in the link is a FAKE Allwinner H313. If your board does not have a small AXP### chip then it's not an Allwinner H313.

@alexc Thanks for all your hard work! I’ve put together an Armbian build using your kernel—you can check it out here: https://github.com/NickAlilovic/build/tree/Radxa-mainline-WIP

@Mohammad Adel AW869A and AIC8800 are the same WiFI chips. You should have WiFi working.

@Mohammad Adel I need to know the physical WiFi and Ethernet chip model number on your board. If you can take a high resolution picture or just tell me the model number. https://openwrt.org/toh/xunlong/orange_pi_zero_3 is the closest model. But you need to edit the device tree. (dts) and u-boot defconfig.

@Mohammad Adel can you find the wifi chip on the board? Also Ethernet.