Nick A

@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 

Delete the cache and output folder. Try again.

@dale
git clone https://github.com/NickAlilovic/build.git --branch v20251014

@dale Sure, I'll upload what have so far. Need help debugging it. 

@emor acid You could use the armbian build system to create patches https://docs.armbian.com/Developer-Guide_Build-Commands/#rewrite-uboot-patches. I like to use the git commands and make my own patches.
 
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 "x98h"
choose "edge"
rest is up to you.
 

 
Stop the build after the kernel patches are applied in the middle of the kernel build. Use "ctrl c" keys.
ctrl c
 
Patch your u-boot dts.
cd cache/sources/u-boot-worktree/u-boot/v2025.01
sudo pico dts/upstream/src/arm64/allwinner/sun50i-h618-x98h.dts
 
Delete this.
ethernet0 = &emac1; &emac1 { pinctrl-names = "default"; pinctrl-0 = <&rmii_pins>; phy-mode = "rmii"; phy-handle = <&rmii_phy>; phy-supply = <&reg_aldo1>; allwinner,rx-delay-ps = <3100>; allwinner,tx-delay-ps = <700>; status = "okay"; }; &mdio1 { rmii_phy: ethernet-phy@16 { compatible = "ethernet-phy-ieee802.3-c22"; reg = <16>; }; };  
Add this
ethernet0 = &emac0; ethernet1 = &emac1; &emac0 { compatible = "allwinner,sun50i-h616-emac"; pinctrl-names = "default"; pinctrl-0 = <&ext_rgmii_pins>; phy-mode = "rgmii"; phy-handle = <&ext_rgmii_phy>; phy-supply = <&reg_gmac_3v3>; phy-io-supply = <&reg_dldo1>; allwinner,rx-delay-ps = <3100>; allwinner,tx-delay-ps = <700>; status = "okay"; }; &mdio0 { ext_rgmii_phy: ethernet-phy@1 { /* rtl8211F compatible string for mdio and phy */ compatible = "ethernet-phy-id001c.c916"; reg = <1>; reset-assert-us = <20000>; reset-deassert-us = <100000>; reset-gpios = <&pio 8 16 GPIO_ACTIVE_LOW>; /* PI16 */ }; }; &emac1 { compatible = "allwinner,sunxi-gmac"; status = "disabled"; }; &mdio1 { rmii_phy: ethernet-phy@1 { compatible = "ethernet-phy-ieee802.3-c22"; reg = <1>; }; }; sudo git add dts/upstream/src/arm64/allwinner/sun50i-h618-x98h.dts
sudo git commit
 
This opens up an editor. First line is your Title. The rest is your description. Remember to save when you are done.
 
Title
Description
 
sudo git format-patch -1
 
Your new patch.
0001-Title.patch
 
Rename 0001-Title.patch to 172-Title.patch
Copy your patch into the build/patch/u-boot/u-boot-h616 directory.
 
 
 
Patch your kernel dts.
cd cache/sources/linux-kernel-worktree/6.12__sunxi64__arm64
sudo pico arch/arm64/boot/dts/allwinner/sun50i-h618-x98h.dts
Same changes as above. sudo git add arch/arm64/boot/dts/allwinner/sun50i-h618-x98h.dts
sudo git commit
 
Title
Description
 
sudo git format-patch -1
 
Rename 0001-Title.patch to 2002-Title.patch.
Copy your patch into the build/patch/kernel/archive/warpme-6.12 directory.
 

@emor acid could be your gpio settings for mmc0. Try the x98h image. If that doesn’t work you need to extract your android dts or use the one from the working Ubuntu.

There are probably 20 different CPUs that have cortex a53 (cpus from Allwinner, Rockchip and Amlogic).  TV box manufacturers all the time will use different CPUs in TV boxes that have the same external markings.  Which ever component is the cheapest at the time of manufacture is what gets used.  The only way to really be sure what you have is to look at the chip on the board (but even then there are cases where chip markings have been altered to make you think you have something else).  Welcome to the world of TV boxes (and why Armbian doesn't support them officially because they are a mess).