Nick A

@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 You also need to ensure your CPU supports virtualization. Check with: egrep -c '(vmx|svm)' /proc/cpuinfo 0 A return value greater than 0 indicates virtualization support is present. CPU doesn't support virtualization. Check the official Radxa image. Using these commands. I doubt it works. I'm using the same kernel config and Board support package.

@djoness you need to Disable Armbian kernel/firmware upgrades using the armbian-config tool. System -> Updates -> UPD002 - Disable Armbian firmware upgrades -> Disable Armbian kernel/firmware upgrades X96Q has many different variations of the same box. Read the bottom of this thread. https://github.com/warpme/miniarch/issues/102 If you want a well supported box get a Transpeed 8K618-t.

An apt error related to ntpdate typically indicates a time synchronization issue, as apt relies on accurate system time for validating package release files. https://www.google.com/search?sca_esv=55588fd05011d482&rlz=1CDGOYI_enCA922CA922&hl=en-US&sxsrf=AE3TifMjcn14YNfEQNUHV48vtdb2hNOADw:1763573317647&q=How+to+fix+apt+error+around+ntpdate&sa=X&ved=2ahUKEwiLzojJ3v6QAxUbEFkFHatLG24Q1QJ6BAgQEAE&biw=390&bih=665&dpr=3

@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.

@djonessIf you can find the source code for this image that would help. MiniArch-20231112-6.6.2-board-h313.x96_q-SD-Image.img Have you tried miniarch latest images?

@djoness My build uses the miniarch patches. https://github.com/NickAlilovic/build/releases/tag/20250306 Here's a direct link to X96q ddr3 server image. https://github.com/NickAlilovic/build/releases/download/20250306/Armbian-unofficial_25.05.0-trunk_X96q-ddr3_bookworm_edge_6.12.11_server.img.xz

@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.

@blackc Exact the original U-boot DRAM settings from your boot.bin or an update. https://forum.armbian.com/topic/29794-how-to-install-armbian-in-h618/page/23/#findComment-218660 If you are still having issues ask the sunxi guys on IRC. https://oftc.catirclogs.org/linux-sunxi/2025-11-14

Fixed the automatic first boot configuration on Bookwarm. Now you can boot the desktop image without a usb serial device.

You need to set this to y or m in your kernel config. https://github.com/NickAlilovic/build/blob/v20250306/config/kernel/linux-sunxi64-edge.config#L5745 https://www.kernelconfig.io/config_usb_acm

@eli It's compiled in the kernel https://github.com/NickAlilovic/build/blob/Radxa-A7A/config/kernel/linux-sun60i-legacy.config#L1659-L1672

For those with a Radxa Cubie A7A, I made a custom Armbian Build using the BSP kernel. https://github.com/NickAlilovic/build/releases/tag/Radxa-a7a-v0.2 https://github.com/NickAlilovic/build/tree/Radxa-A7A Now supports automatic first boot configuration by default. No need for a usb serial device to boot into a desktop image. First boot takes awhile to load. If you are using a server image you need a usb serial device/ssh to interact with the console. There is no Framebuffer console support in the BSP kernel. If you want to edit the automatic first boot configuration read the documentation. https://docs.armbian.com/User-Guide_Autoconfig/ Username: radxa password: radxa

@emor acid The build system downloads the original uboot and kernel sources. Then it applies the patches on top. Whatever you edited will be erased. The only way around this is to create a patch with your changes. You could use dtc to compile your dts file into a binary dtb. Then copy it into your sdcard.

@Farhan Ishraq Have you tried the images in the link @Sadiq Ahmed posted? Download BalenaEtcher software. Write one of the bigtreetech cb1 images onto a SDcard. Put it in your box and boot.

@Gilliard Gabriel Rodrigues Mark was using my Transpeed image. https://github.com/NickAlilovic/build/releases/tag/20250306

@ayoub-hs I don't own one of these boxes. I got the patches from warpme's miniarch/minimyth2. Supporting the x96q is a real PITA. https://github.com/warpme/miniarch/issues/102 Comparing the uboot DTS for both x96q lpddr3 and x96q lpddr3 v1.3. I don't see much difference other than wifi. Maybe you'll find something I missed. u-boot: https://github.com/NickAlilovic/build/blob/v20250306/patch/u-boot/u-boot-h616/159-add-x96-q-lpddr3-v1.3-defconfig.patch https://github.com/NickAlilovic/build/blob/v20250306/patch/u-boot/u-boot-h616/150-add-x96-q-lpddr3-defconfig.patch Kernel: https://github.com/NickAlilovic/build/blob/v20250306/patch/kernel/archive/warpme-6.12/0648-arm64-dts-allwinner-h313-add-x96q-lpddr3-TVbox.patch https://github.com/warpme/minimyth2/tree/master/script/bootloaders https://github.com/warpme/minimyth2/tree/master/script/bootloaders/u-boot-aw/files

@leXia "no matter which image I use, it always boots into Android". Maybe it's not booting into FEL mode or it's not reading your SDcard. To enter FEL mode, power off the TV box, insert your SDcard, press and hold a hidden button (often inside the AV port, reachable with a toothpick) while connecting the power cable, release the button after a few seconds. If that doesn't work try another SDcard. Usually, if you box detects uboot and stops you'll just get a black screen. Without UART communication I can't really help. If it boots the kernel then you can check your SDcard for log files.

@Jeeva Kandasamy it’s on this page https://github.com/NickAlilovic/build/tree/v20250306

@snow https://linux-sunxi.org/FEL/USBBoot I haven’t tried this before.

@snow download balena etcher and flash the image onto a sdcard. This will boot armbian off the sdcard. Unless you use armbian-config and write to emmc you will be fine.

@Jeeva Kandasamy I haven't had that error before. Maybe your host is out of date. Have you tried "sudo apt update && sudo apt upgrade"?

@Jeeva Kandasamy correct

@Jeeva Kandasamy I would freeze your kernel updates using armbian-config. I’m using a custom kernel so it will break your system. I made google search and found this. https://github.com/MichaIng/DietPi/issues/4600

@MeJune A523/T527 support still needs a lot of work. There is no HDMI support yet. So you will need to install a usb serial device to your uart to interact with your box. You can find details at the botton of the site you posted https://linux-sunxi.org/X96QPro%2B. You could try warpme minimyth2 or miniarch. He has the latest support for these boxes. I don't own a X96q pro+ so I can't help you.

@Unrealchex The base-files error is a known issue. You'll need to run the ./compile command a second time and it should continue where it left off. Here's a post that show's you how to create patches. https://forum.armbian.com/topic/29794-how-to-install-armbian-in-h618/#findComment-227058 You want to edit u-boot and kernel dts. Remove the x96q code and add the wifi code from x98h. The x96h U-boot and kernel code might be different double check it. remove (Existing x96q wifi code.) reg_vcc_wifi: reg_vcc_wifi { compatible = "regulator-fixed"; regulator-name = "vcc-wifi"; regulator-min-microvolt = <3300000>; regulator-max-microvolt = <3300000>; gpio = <&pio 6 18 GPIO_ACTIVE_HIGH>; /* PG18 WL_REG_ON */ regulator-always-on; enable-active-high; status = "okay"; }; wifi_pwrseq: wifi_pwrseq { compatible = "mmc-pwrseq-simple"; clocks = <&rtc CLK_OSC32K_FANOUT>; clock-names = "ext_clock"; pinctrl-names = "default"; pinctrl-0 = <&x32clk_fanout_pin>; /* PG10 with MUX3 set */ }; &mmc1 { vmmc-supply = <&reg_dldo1>; vqmmc-supply = <&reg_vcc_wifi>; mmc-pwrseq = <&wifi_pwrseq>; bus-width = <4>; non-removable; status = "okay"; wlan: wifi@1 { reg = <1>; interrupt-parent = <&pio>; interrupts = <6 15 IRQ_TYPE_EDGE_RISING>; /* PG15 WL_HOSTWAKE*/ interrupt-names = "host-wake"; local-mac-address = [dc 44 6d c0 ff 02]; }; }; Add (code borrowed from x98h) reg_vcc3v3: vcc3v3 { /* discrete 3.3V regulator */ compatible = "regulator-fixed"; regulator-name = "vcc-3v3"; regulator-min-microvolt = <3300000>; regulator-max-microvolt = <3300000>; regulator-always-on; }; reg_3v3_wifi: vcc3v3-wifi { compatible = "regulator-fixed"; regulator-name = "vcc-3v3-wifi"; regulator-min-microvolt = <3300000>; regulator-max-microvolt = <3300000>; regulator-always-on; }; }; &mmc1 { vmmc-supply = <&reg_vcc3v3>; bus-width = <4>; non-removable; max-frequency = <35000000>; status = "okay"; wlan: wifi@1 { reg = <1>; }; }; You don't need to create a patch for build/config/boards. Edit the file x96q-lpddr3.csc and add this to the bottom of display_alert "$BOARD" "Using ${BOOT_FDT_FILE} for ${BRANCH}" "info" display_alert "Applying wifi firmware" pushd "$SDCARD/lib/firmware" ln -s "aic8800/SDIO/aic8800D80" "aic8800_sdio" # use armbian-firmware cp -R $SRC/packages/blobs/sunxi/h618/armbian-audio-config $SDCARD/usr/lib/armbian cp -R $SRC/packages/blobs/sunxi/h618/armbian-audio-config $SDCARD/lib/armbian popd