Nick A

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

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

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

@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

Hi all,
Over the past few months working on the A7Z, I’ve successfully ported a number of BSP drivers to Linux 6.18.
The code is available here:
https://github.com/alexcaoys/allwinner-bsp/tree/linux-6.18.y
It’s currently tested on 6.18.19 and should, in theory, work with newer 6.18.y releases. I’ve tried to reuse as much upstream (mainline) drivers as possible, and have also upstreamed support for PCK600 and ET7304 used on the A7Z.
Hopefully this helps accelerate ongoing mainline efforts. Feedback, issues, and PRs are very welcome.
I may also look into creating branches for Linux 7.x in the future.

@billymore I got this from AI. It's not perfect. I haven't done this before. 

To convert a standard Armbian root filesystem (typically an ext4 partition) into the rootfs.cpio.lzma.uboot format required for RAM booting, you must package the file tree into a CPIO archive, compress it with LZMA, and then wrap it with a U-Boot header.
 
1. Extract the Armbian RootFS 
First, you need the actual files from your Armbian image. Mount the image to a temporary directory on your Linux PC:
mkdir -p /tmp/armbian_root
 
If you have your Armbian .img file ready, run this command to find the start sector of the root partition (usually the second partition):
fdisk -l armbian_image.img
 
Multiply that Start number by 512 to get the exact offset for the mount command.
sudo mount -o loop,offset=YOUR_OFFSET armbian_image.img /tmp/armbian_root
 
A standard Armbian rootfs doesn't have an init file in the root directory; it uses sbin/init (a symlink to systemd). A RAM disk requires an executable at /init. 
sudo ln -s sbin/init /tmp/armbian_root/init
 
2. Create the CPIO Archive
Pack the entire filesystem into a newc format CPIO archive. It is critical to perform this step as root to preserve file permissions. 
cd /tmp/armbian_root
sudo find . | sudo cpio -H newc -o > /tmp/rootfs.cpio
 
3. Compress with LZMA 
Compress the archive using the LZMA algorithm to minimize its size for RAM loading:
lzma -9 /tmp/rootfs.cpio                # This creates /tmp/rootfs.cpio.lzma
 
4. Add the U-Boot Header 
Use the mkimage tool (from the u-boot-tools package) to add the 64-byte legacy header that U-Boot uses to identify the ramdisk. 
mkimage -A  arm64 -O linux -T ramdisk -C lzma -n "Armbian Initramfs" -d /tmp/rootfs.cpio.lzma /tmp/rootfs.cpio.lzma.uboot
 
-A arm: Target architecture (use arm64 if applicable).
-T ramdisk: Identifies the image type as a RAM filesystem.
-C lzma: Specifies the compression used.
-d: Input data file. 
 
sunxi-fel -v uboot u-boot-sunxi-with-spl.bin \ write 0x40080000 Image \ write 0x4fa00000 dtbs/allwinner/sun50i-h313-tanix-tx1.dtb \ write 0x4fe00000 rootfs.cpio.lzma.uboot (Note: If you are using a raw Image instead of a uImage, use booti instead of bootm).

 
Once U-Boot initializes over the USB cable, it will drop to a prompt. You must run this to start the OS:
Armbian’s default kernel might not have a large enough ramdisk_size allocated in its config.
Update your bootargs to include a size limit (in KB). If your rootfs is 500MB:
setenv bootargs "console=ttyS0,115200 root=/dev/ram0 rw" booti 0x40080000 0x4fe00000 0x4fa00000 ramdisk_size=600000  

@billymore The "Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)" error indicates that the Linux kernel could not locate or mount the root file system during startup. . 
 
 This is commonly caused by a missing or corrupted initial RAM filesystem (initramfs), an incorrect root= boot parameter
 
write 0x4ff00000 rootfs.cpio.lzma.uboot

@marcosdsdba I would compile this on the box. Install kernel headers. Post the errors you are getting.
https://github.com/NickAlilovic/build/releases/download/20250306/linux-headers-edge-sunxi64_25.05.0-trunk_arm64__6.12.11-S62b2-Da873-P8a5c-C1abcH02eb-HK01ba-Vc222-B9bbb-R448a.deb

@sicxnull 
 

@Kevin su Excellent work! Porting the SV6256P driver all the way to kernel 6.12 is a huge achievement. Most users usually just give up and plug in a USB Wi-Fi adapter to avoid the headache of legacy drivers.

@marcosdsdba the only driver that works is from kernel 4.4. Unless someone figures out a way to port this to a modern kernel, your only option is to use a usb wifi adapter.

@marcosdsdba 
 

Glade to see you back @sicxnull. Thanks for the shoutout! Tried my best while you were gone. I don’t own one of these boxes. But I guess it doesn’t matter which one I get because theirs so many variations of the same box.

@伍翠波  Framebuffer console should work now. 
https://github.com/NickAlilovic/build/releases/tag/Radxa-a7a-v0.4

@伍翠波  Framebuffer console should work now. 
https://github.com/NickAlilovic/build/releases/tag/Radxa-a7a-v0.4

@Jeeva Kandasamy depends on which branch you are looking at? V20250306 hasn’t changed much.
https://github.com/NickAlilovic/build/commits/v20250306/

@Malay delete patch/u-boot/u-boot-aw/99-dump-dram-controller-regs.patch. Using your compiler it causes a fatal error. The compiler I'm using it creates a warning. You don't need it anyways, it's for ram debug messages. I removed it from my repository,   

@Shubham Singh 
To check if KVM is compiled into the kernel, use the following command: 
grep CONFIG_KVM /boot/config-$(uname -r)
 
CONFIG_KVM=y
CONFIG_KVM_MMIO=y
CONFIG_KVM_VFIO=y
CONFIG_KVM_GENERIC_DIRTYLOG_READ_PROTECT=y
CONFIG_KVM_XFER_TO_GUEST_WORK=y
 
A7A: Harware Virtualization
https://forum.radxa.com/t/a7a-harware-virtualization/29745
 

@dale I had the same problem last night. Should be fixed now. Clone or update the repository. You will need to install Docker.
 
https://github.com/NickAlilovic/build/commit/025e4487f87233bfb823c7d51162d877b2a9fd6f
 
https://github.com/armbian/build/issues/8572

@Jeeva Kandasamy depends on which branch you are looking at? V20250306 hasn’t changed much.
https://github.com/NickAlilovic/build/commits/v20250306/

@qwerty keyboard here are some links that will help you.

Find your Dram settings 
https://forum.armbian.com/topic/29794-how-to-install-armbian-in-h618/#findComment-218660
 
Find boot.bin and extract dts.
https://forum.armbian.com/topic/29794-how-to-install-armbian-in-h618/#findComment-187672
 
Uboot defconfig. I have two x96q builds with ddr3.
https://github.com/NickAlilovic/build/blob/v20250306/patch/u-boot/u-boot-h616/151-add-x96-q-ddr3-defconfig.patch
Or
https://github.com/NickAlilovic/build/blob/v20250306/patch/u-boot/u-boot-h616/163-add-x96-q-ddr3-v5.1-defconfig.patch
 
You can edit the patch and enter the new values. 
 
If you need to add a new line in the defconfig patch. At the bottom of the patch add your newline and put a "+" infront of it. Also, for x96q ddr3 increase @@ -0,0 +1,37 @@ to @@ -0,0 +1,38 @@ or for x96q ddr3 v5.1 @@ -0,0 +1,39 @@ to @@ -0,0 +1,40 @@.
 
Download and compile my build:
git clone https://github.com/NickAlilovic/build.git --branch v20250306
cd build
./compile.sh
choose "Do not change kernel configuration"
choose "Show CSC/WIP/EOS/TVB"
choose "I understand and agree"
choose "X96Q DDR3” or “X96Q DDR3 v5.1”
choose "edge"
rest is up to you.

@qwerty keyboard H313/H616/H618 are pretty much the same. A133 and A64 are different SOC’s.
 
You don’t need the dts for the dram settings.

After wanting to use Debian 13 (Trixie) @Nick A suggested trying to build it myself, and this was my first experience building an Armbian image. I encountered some obstacles, but I got through them.
 
I saw that the model was mentioned branch v20251014. I tried building it (Mate Desktop), which as build smoother than (v20250306) before. I tried booting it with this box (Transpeed 8K618-T)  and and found that the wifi was not visible. I followed the troubleshooting methods in the previous thread solved it. I have installed additional IR remote and OpenVFD. Now everything is smooth and happy.
 
The only thing left is the video acceleration, but that would be difficult because it is beyond my ability.

Finally, thank you, @Nick A

@Jeeva Kandasamy it’s on this page. Build Host Requirements.  https://github.com/armbian/build

@Jeeva Kandasamy correct