All Activity

Hey, @xiaobao80! Sadly not - but on the upside I was able to build and use the latest kernel. Also want to update and say that I did manage to use the NPU and the VPU successfully with Immich AI facial recognition and Jellyfin transcoding respectively.

I can't contribute much to this other than stating, it's the same on my Rock64 2GB v2.0 but I also cannot boot: Armbian_25.2.1_Rock64_bookworm_current_6.12.13_minimal.img.xz I then tried one from here https://archive.armbian.com/rock64/archive (site currently throws error: Internal error - code should not reach this point so I cannot tell which one specifically I used) but that one booted fine.

Hello everyone, I've already managed to identify and work with a few TV box models, but I'm currently facing difficulties with a model that uses the IK316 SoC. I've attached photos of the board and some of its components, as well as the DTS file I extracted from this model. Could anyone help me figure out how to proceed? I tried adapting the original DTB to work with an Armbian image, but I believe I'm making mistakes in this step. So far, I've accessed the device via UART using a TTL adapter. Using sudo, I was able to dump the Android image and then extract the DTB file using Python. Any guidance would be greatly appreciated! 01_dtbdump_,sun50iw9.dts

If a kernel package exists as artifact in oci cache it will be downloaded and used. Only if there is no artifact it will be built from scratch. After a new kernel version is released it may take a few days until oci catches up. However once locally built it will also be cached locally so it will be re-used if you start another build.

Hello @mvpwar Download image Unzip

@remlei Yes indeed, sometimes I ask to myself ( and to my friends @jock @ilmich ) who the hell give us so much entusiasm, patience ( and frustration) to deal AGAINST not the box itself, but against the lack of good documentation and support , but when finally a stuff is working after thousands of trials and errors, well then I go sleep like a child with it's christmas gift. This is the pagic called PASSION !!!

I assume thats the proper format because armbian-config is the one put that there so I never questioned about it. so far all of the NAND models seems to have USB OTG working but not all my eMCP boards, it always throw that error I posted earlier. also for some reason, in NAND models with jumpstart installed on NAND, overlay option on /boot/armbianEnv.txt for some reason do not work and have to resort editing the dtb file manually, all of it from led config to wifi stuff, also enabling the peripheral mode as well. I guess those overlay stuff only works when that u-boot bootscreen on emcp boards I had only have those overlay stuff working but not on the NAND models with jumpstart. After all those dtb shenanigans, I went ahead and install https://github.com/srepac/kvmd-armbian skipping all the way to step 3, a hour and 2 reboots later, yep its all working now. with 256GB USB flash drive mount on /var/lib/kvmd/msd and running that msd fix sh script to get that USB storage stuff working. sheesh, this box sure is really hell of a work. if I dont have extra time, id probably not doing this and just buy a cheap orange pi instead.

I am building a custom image for rpi4b and everything works great so far. I only want to customize the installed packets and configuration, but I do not need a custom kernel. Since building the kernel is what takes by a wide margin most of the image generation time, I was wondering if there's a way to build the image without building the kernel (using the one from the official builds). I have browsed the documentation and found no way, so maybe it is not supported and building the kernel is mandatory?

Finally someone has the question I wanted to ask right now.. Thank you for the solution you found. I will try it sir..

Makes sense, thanks for pointing that out. I had similar issues and I’ll check which package holds it on my setup and try replacing it. Hopefully that clears it up.. Thank you..

Further testing shows that Armbian 25.2.x through the current version all run the arecord -c 2 -r 192000 -f S32_LE test.wav without error, PROVIDED the 6.12.12 kernel is used. But, any kernel version after 6.12.12 fails. Now I've just got to find out what broke in 6.12.13 🙂

You can find this information on the Rock Pi S PoE Hat Wiki, but you need to write some GPIO values to enable the headphone jack. # echo 15 > /sys/class/gpio/export # echo out > /sys/class/gpio/gpio15/direction # echo 1 > /sys/class/gpio/gpio15/value To persist this across reboots you can create a `systemd-tmpfile` at `/etc/tmpfiles.d/enable-audio-jack.conf` with the following contents. w /sys/class/gpio/export - - - - 15 w /sys/class/gpio/gpio15/direction - - - - out w /sys/class/gpio/gpio15/value - - - - 1

I just updated one of my Armbian installs, including the 6.12.22 kernel, and it's still working normally. $ uname -a Linux snapclient-master-bedroom 6.12.22-current-rockchip64 #1 SMP PREEMPT Mon Apr 7 08:08:37 UTC 2025 aarch64 GNU/Linux $ aplay -l **** List of PLAYBACK Hardware Devices **** card 0: analog [analog], device 0: ff320000.i2s-rk3308-hifi ff560000.codec-0 [ff320000.i2s-rk3308-hifi ff560000.codec-0] Subdevices: 1/1 Subdevice #0: subdevice #0 card 1: pcm5102a [pcm5102a], device 0: ff300000.i2s-pcm5102a-hifi pcm5102a-hifi-0 [ff300000.i2s-pcm5102a-hifi pcm5102a-hifi-0] Subdevices: 1/1 Subdevice #0: subdevice #0

Does 25.2.1/6.12.12 work?

Is there a fix for 6.12.22? uname -a Linux rp-satellite-xx 6.12.22-current-rockchip64 #1 SMP PREEMPT Mon Apr 7 08:08:37 UTC 2025 aarch64 GNU/Linux cat /sys/class/gpio/export cat: /sys/class/gpio/export: Permission denied ls /dev/snd/ seq timer aplay -l aplay: device_list:274: no soundcards found...

I think the only difference with x98h is the emmc gpio #. So it should boot but not off of emmc. Unless x98h has the correct value. I'm not sure if this will fix your problem because it's the kernel not detecting your dram. I don't know why. You can ask for help in this IRC channel. https://oftc.catirclogs.org/linux-sunxi/2025-05-18 You can find the dram config options here. I don't see TPR13 as an option so you can leave that out. https://elixir.bootlin.com/u-boot/v2025.07-rc2/source/arch/arm/mach-sunxi/Kconfig if DRAM_SUN50I_H616 config DRAM_SUNXI_DX_ODT hex "DRAM DX ODT parameter" help DX ODT value from vendor DRAM settings. config DRAM_SUNXI_DX_DRI hex "DRAM DX DRI parameter" help DX DRI value from vendor DRAM settings. config DRAM_SUNXI_CA_DRI hex "DRAM CA DRI parameter" help CA DRI value from vendor DRAM settings. config DRAM_SUNXI_ODT_EN hex "DRAM ODT EN parameter" default 0x1 help ODT EN value from vendor DRAM settings. config DRAM_SUNXI_TPR0 hex "DRAM TPR0 parameter" default 0x0 help TPR0 value from vendor DRAM settings. config DRAM_SUNXI_TPR2 hex "DRAM TPR2 parameter" default 0x0 help TPR2 value from vendor DRAM settings. config DRAM_SUNXI_TPR6 hex "DRAM TPR6 parameter" default 0x3300c080 help TPR6 value from vendor DRAM settings. config DRAM_SUNXI_TPR10 hex "DRAM TPR10 parameter" help TPR10 value from vendor DRAM settings. It tells which features should be configured, like write leveling, read calibration, etc. config DRAM_SUNXI_TPR11 hex "DRAM TPR11 parameter" default 0x0 help TPR11 value from vendor DRAM settings. config DRAM_SUNXI_TPR12 hex "DRAM TPR12 parameter" default 0x0 help TPR12 value from vendor DRAM settings.

I also have some oom issues when doing an aptitude upgrade in my opizero w/256 MiB ram. Guess even more on a 128MiB board like yours. Best to add a swap file to make sure upgrades go without issue. Grt,

It seems trying to update/upgrade got it into a partially updated state. It’s giving a /run/systemd is out of space error currently and says it cannot use/build with libc6 or something. Away from the PC and Pinecube at the moment. I will reflash my other SD card, set the memory values, and then copy all the outputs with verbosity 8 and early console enabled.

Little odd that it fails to load the fix up script there; In the old boot.cmd it checks if it can find the file and loads it if it can. Can you share a serial console log of the 21.x release that did work? Incl aembianmonitor -u output? Thx, Grt,

Hi @Nick A, I really need your help to understand the way to change the 171-add-x98h-defconfig.patch. Firstly, I extracted the DRAM parameters, but there are 15 of them: DRAM parameters, DRAM parameters 1, ... DRAM parameters E. Some of them have distinct parameters. The first of then (DRAM parameters) have the very identical parameters as yours, only differ in the same parameters, that isn't in patch file like TPR13, but I don't know if it matters. So I tried using the DRAM parameters 1, which is the most different, with clock 600 instead of 648 and almost all parameters different, but it works the same way with the same 2GB of RAM. I think this is strange, because with so many differences, I expected the image would not work. Do you have any tips for giving me? My extracted parameters: ./sunxi-fw info -v ./image4.img @ 0: wty: PhoenixSuite image file header v3.0, 45 images, 1859 MB wty:sys_config.fex : 34908 bytes @ +0x000000b800 wty:board.fex : 1024 bytes @ +0x0000014400 wty:config.fex : 53248 bytes @ +0x0000014800 wty:split_xxxx.fex : 512 bytes @ +0x0000021800 wty:sys_partition.fex : 5601 bytes @ +0x0000021c00 wty:sunxi.fex : 71680 bytes @ +0x0000023400 wty:boot0_nand.fex : 61440 bytes @ +0x0000034c00 wty:boot0_sdcard.fex : 61440 bytes @ +0x0000043c00 wty:u-boot.fex : 917504 bytes @ +0x0000052c00 wty:u-boot-crash.fex : 37 bytes @ +0x0000132c00 wty:toc1.fex : 8 bytes @ +0x0000133000 wty:toc0.fex : 8 bytes @ +0x0000133400 wty:fes1.fex : 40160 bytes @ +0x0000133800 wty:boot_package.fex : 1294336 bytes @ +0x000013d800 wty:usbtool.fex : 154624 bytes @ +0x0000279800 wty:usbtool_crash.fex : 621056 bytes @ +0x000029f400 wty:aultools.fex : 166515 bytes @ +0x0000337000 wty:aultls32.fex : 152069 bytes @ +0x000035fc00 wty:cardtool.fex : 73728 bytes @ +0x0000385000 wty:cardscript.fex : 1899 bytes @ +0x0000397000 wty:sunxi_gpt.fex : 8192 bytes @ +0x0000397800 wty:sunxi_mbr.fex : 65536 bytes @ +0x0000399800 wty:dlinfo.fex : 16384 bytes @ +0x00003a9800 wty:arisc.fex : 6 bytes @ +0x00003ad800 wty:vmlinux.fex : 12444168 bytes @ +0x00003adc00 wty:boot-resource.fex : 7490560 bytes @ +0x0000f8c000 wty:Vboot-resource.fex : 4 bytes @ +0x00016b0c00 wty:env.fex : 131072 bytes @ +0x00016b1000 wty:Venv.fex : 4 bytes @ +0x00016d1000 wty:boot.fex : 67108864 bytes @ +0x00016d1400 wty:Vboot.fex : 4 bytes @ +0x00056d1400 wty:vendor_boot.fex : 33554432 bytes @ +0x00056d1800 wty:Vvendor_boot.fex : 4 bytes @ +0x00076d1800 wty:super.fex : 1806382676 bytes @ +0x00076d1c00 wty:Vsuper.fex : 4 bytes @ +0x0073185400 wty:misc.fex : 16777216 bytes @ +0x0073185800 wty:Vmisc.fex : 4 bytes @ +0x0074185800 wty:vbmeta.fex : 8192 bytes @ +0x0074185c00 wty:Vvbmeta.fex : 4 bytes @ +0x0074187c00 wty:vbmeta_system.fex : 4096 bytes @ +0x0074188000 wty:Vvbmeta_system.fex : 4 bytes @ +0x0074189000 wty:vbmeta_vendor.fex : 4096 bytes @ +0x0074189400 wty:Vvbmeta_vendor.fex : 4 bytes @ +0x007418a400 wty:dtbo.fex : 2097152 bytes @ +0x007418a800 wty:Vdtbo.fex : 4 bytes @ +0x007438a800 @ 542: boot0: Allwinner boot0 size: 61440 bytes eGON checksum matches: 0x505a301a DRAM parameters: A64 H616 A133 DRAM clock : 648 648 648 DRAM type : 0x3 0x3 0x3 ZQ value : 0x3030303 - - ODT enabled : 0xe0e0e0e 0x1 - DX ODT : - 0x3030303 0x3030303 DX DRI : - 0xe0e0e0e 0xe0e0e0e CA DRI : - 0x1f12 0x1f12 PARA0 : - - 0x1 PARA1 : 0x1f12 0x30fb 0x30fb PARA2 : 0x1 0 0 MR0 : 0x30fb 0x840 0x840 MR1 : 0 0x4 0x4 MR2 : 0x840 0x8 0x8 MR3 : 0x4 0 0 TPR0 : 0x8 0xc0001002 0 TPR2 : 0 0 0xc0001002 TPR6 : 0 0x33808080 0x33808080 TPR10 : 0 0x2f1107 0x2f1107 TPR11 : 0 0xddddcccc 0xddddcccc TPR12 : 0xc0001002 0xeddc7665 0xeddc7665 TPR13 : 0 0x40 0x40 DRAM parameters 1: A64 H616 A133 DRAM clock : 600 600 600 DRAM type : 0x3 0x3 0x3 ZQ value : 0x3030303 - - ODT enabled : 0xe0e0e0e 0x1 - DX ODT : - 0x3030303 0x3030303 DX DRI : - 0xe0e0e0e 0xe0e0e0e CA DRI : - 0x1c1a 0x1c1a PARA0 : - - 0x1 PARA1 : 0x1c1a 0x30fb 0x30fb PARA2 : 0x1 0 0 MR0 : 0x30fb 0x840 0x840 MR1 : 0 0x4 0x4 MR2 : 0x840 0x8 0x8 MR3 : 0x4 0 0 TPR0 : 0x8 0xc000130a 0 TPR2 : 0 0 0xc000130a TPR6 : 0 0x33808080 0x33808080 TPR10 : 0 0x2f0006 0x2f0006 TPR11 : 0 0xddddcccc 0xddddcccc TPR12 : 0xc000130a 0xeddc6554 0xeddc6554 TPR13 : 0 0x40 0x40 DRAM parameters 2: A64 H616 A133 DRAM clock : 648 648 648 DRAM type : 0x3 0x3 0x3 ZQ value : 0x3030303 - - ODT enabled : 0xe0e0e0e 0x1 - DX ODT : - 0x3030303 0x3030303 DX DRI : - 0xe0e0e0e 0xe0e0e0e CA DRI : - 0x1c12 0x1c12 PARA0 : - - 0x1 PARA1 : 0x1c12 0x30fb 0x30fb PARA2 : 0x1 0 0 MR0 : 0x30fb 0x840 0x840 MR1 : 0 0x4 0x4 MR2 : 0x840 0x8 0x8 MR3 : 0x4 0 0 TPR0 : 0x8 0xc0000a05 0 TPR2 : 0 0 0xc0000a05 TPR6 : 0 0x33808080 0x33808080 TPR10 : 0 0x2f0006 0x2f0006 TPR11 : 0 0xddddcccc 0xddddcccc TPR12 : 0xc0000a05 0xeddc7564 0xeddc7564 TPR13 : 0 0x40 0x40 DRAM parameters 3: A64 H616 A133 DRAM clock : 648 648 648 DRAM type : 0x3 0x3 0x3 ZQ value : 0x3030303 - - ODT enabled : 0xe0e0e0e 0x1 - DX ODT : - 0x3030303 0x3030303 DX DRI : - 0xe0e0e0e 0xe0e0e0e CA DRI : - 0x1c12 0x1c12 PARA0 : - - 0x1 PARA1 : 0x1c12 0x30fb 0x30fb PARA2 : 0x1 0 0 MR0 : 0x30fb 0x840 0x840 MR1 : 0 0x4 0x4 MR2 : 0x840 0x8 0x8 MR3 : 0x4 0 0 TPR0 : 0x8 0xc0000a05 0 TPR2 : 0 0 0xc0000a05 TPR6 : 0 0x33808080 0x33808080 TPR10 : 0 0x2f0006 0x2f0006 TPR11 : 0 0xddddcccc 0xddddcccc TPR12 : 0xc0000a05 0xeddc7564 0xeddc7564 TPR13 : 0 0x40 0x40 DRAM parameters 4: A64 H616 A133 DRAM clock : 648 648 648 DRAM type : 0x3 0x3 0x3 ZQ value : 0x3030303 - - ODT enabled : 0xe0e0e0e 0x1 - DX ODT : - 0x3030303 0x3030303 DX DRI : - 0xe0e0e0e 0xe0e0e0e CA DRI : - 0x1c12 0x1c12 PARA0 : - - 0x1 PARA1 : 0x1c12 0x30fb 0x30fb PARA2 : 0x1 0 0 MR0 : 0x30fb 0x840 0x840 MR1 : 0 0x4 0x4 MR2 : 0x840 0x8 0x8 MR3 : 0x4 0 0 TPR0 : 0x8 0xc0000a05 0 TPR2 : 0 0 0xc0000a05 TPR6 : 0 0x33808080 0x33808080 TPR10 : 0 0x2f0006 0x2f0006 TPR11 : 0 0xddddcccc 0xddddcccc TPR12 : 0xc0000a05 0xeddc7564 0xeddc7564 TPR13 : 0 0x40 0x40 DRAM parameters 5: A64 H616 A133 DRAM clock : 648 648 648 DRAM type : 0x3 0x3 0x3 ZQ value : 0x3030303 - - ODT enabled : 0xe0e0e0e 0x1 - DX ODT : - 0x3030303 0x3030303 DX DRI : - 0xe0e0e0e 0xe0e0e0e CA DRI : - 0x1c12 0x1c12 PARA0 : - - 0x1 PARA1 : 0x1c12 0x30fb 0x30fb PARA2 : 0x1 0 0 MR0 : 0x30fb 0x840 0x840 MR1 : 0 0x4 0x4 MR2 : 0x840 0x8 0x8 MR3 : 0x4 0 0 TPR0 : 0x8 0xc0000a05 0 TPR2 : 0 0 0xc0000a05 TPR6 : 0 0x33808080 0x33808080 TPR10 : 0 0x2f0006 0x2f0006 TPR11 : 0 0xddddcccc 0xddddcccc TPR12 : 0xc0000a05 0xeddc7564 0xeddc7564 TPR13 : 0 0x40 0x40 DRAM parameters 6: A64 H616 A133 DRAM clock : 648 648 648 DRAM type : 0x3 0x3 0x3 ZQ value : 0x3030303 - - ODT enabled : 0xe0e0e0e 0x1 - DX ODT : - 0x3030303 0x3030303 DX DRI : - 0xe0e0e0e 0xe0e0e0e CA DRI : - 0x1c12 0x1c12 PARA0 : - - 0x1 PARA1 : 0x1c12 0x30fb 0x30fb PARA2 : 0x1 0 0 MR0 : 0x30fb 0x840 0x840 MR1 : 0 0x4 0x4 MR2 : 0x840 0x8 0x8 MR3 : 0x4 0 0 TPR0 : 0x8 0xc0000a05 0 TPR2 : 0 0 0xc0000a05 TPR6 : 0 0x33808080 0x33808080 TPR10 : 0 0x2f0006 0x2f0006 TPR11 : 0 0xddddcccc 0xddddcccc TPR12 : 0xc0000a05 0xeddc7564 0xeddc7564 TPR13 : 0 0x40 0x40 DRAM parameters 7: A64 H616 A133 DRAM clock : 648 648 648 DRAM type : 0x3 0x3 0x3 ZQ value : 0x3030303 - - ODT enabled : 0xe0e0e0e 0x1 - DX ODT : - 0x3030303 0x3030303 DX DRI : - 0xe0e0e0e 0xe0e0e0e CA DRI : - 0x1c12 0x1c12 PARA0 : - - 0x1 PARA1 : 0x1c12 0x30fb 0x30fb PARA2 : 0x1 0 0 MR0 : 0x30fb 0x840 0x840 MR1 : 0 0x4 0x4 MR2 : 0x840 0x8 0x8 MR3 : 0x4 0 0 TPR0 : 0x8 0xc0000a05 0 TPR2 : 0 0 0xc0000a05 TPR6 : 0 0x33808080 0x33808080 TPR10 : 0 0x2f0006 0x2f0006 TPR11 : 0 0xddddcccc 0xddddcccc TPR12 : 0xc0000a05 0xeddc7564 0xeddc7564 TPR13 : 0 0x40 0x40 DRAM parameters 8: A64 H616 A133 DRAM clock : 648 648 648 DRAM type : 0x3 0x3 0x3 ZQ value : 0x3030303 - - ODT enabled : 0xe0e0e0e 0x1 - DX ODT : - 0x3030303 0x3030303 DX DRI : - 0xe0e0e0e 0xe0e0e0e CA DRI : - 0x1c12 0x1c12 PARA0 : - - 0x1 PARA1 : 0x1c12 0x30fb 0x30fb PARA2 : 0x1 0 0 MR0 : 0x30fb 0x840 0x840 MR1 : 0 0x4 0x4 MR2 : 0x840 0x8 0x8 MR3 : 0x4 0 0 TPR0 : 0x8 0xc0000a05 0 TPR2 : 0 0 0xc0000a05 TPR6 : 0 0x33808080 0x33808080 TPR10 : 0 0x2f0006 0x2f0006 TPR11 : 0 0xddddcccc 0xddddcccc TPR12 : 0xc0000a05 0xeddc7564 0xeddc7564 TPR13 : 0 0x40 0x40 DRAM parameters 9: A64 H616 A133 DRAM clock : 648 648 648 DRAM type : 0x3 0x3 0x3 ZQ value : 0x3030303 - - ODT enabled : 0xe0e0e0e 0x1 - DX ODT : - 0x3030303 0x3030303 DX DRI : - 0xe0e0e0e 0xe0e0e0e CA DRI : - 0x1c12 0x1c12 PARA0 : - - 0x1 PARA1 : 0x1c12 0x30fb 0x30fb PARA2 : 0x1 0 0 MR0 : 0x30fb 0x840 0x840 MR1 : 0 0x4 0x4 MR2 : 0x840 0x8 0x8 MR3 : 0x4 0 0 TPR0 : 0x8 0xc0000a05 0 TPR2 : 0 0 0xc0000a05 TPR6 : 0 0x33808080 0x33808080 TPR10 : 0 0x2f0006 0x2f0006 TPR11 : 0 0xddddcccc 0xddddcccc TPR12 : 0xc0000a05 0xeddc7564 0xeddc7564 TPR13 : 0 0x40 0x40 DRAM parameters A: A64 H616 A133 DRAM clock : 648 648 648 DRAM type : 0x3 0x3 0x3 ZQ value : 0x3030303 - - ODT enabled : 0xe0e0e0e 0x1 - DX ODT : - 0x3030303 0x3030303 DX DRI : - 0xe0e0e0e 0xe0e0e0e CA DRI : - 0x1c12 0x1c12 PARA0 : - - 0x1 PARA1 : 0x1c12 0x30fb 0x30fb PARA2 : 0x1 0 0 MR0 : 0x30fb 0x840 0x840 MR1 : 0 0x4 0x4 MR2 : 0x840 0x8 0x8 MR3 : 0x4 0 0 TPR0 : 0x8 0xc0000a05 0 TPR2 : 0 0 0xc0000a05 TPR6 : 0 0x33808080 0x33808080 TPR10 : 0 0x2f0006 0x2f0006 TPR11 : 0 0xddddcccc 0xddddcccc TPR12 : 0xc0000a05 0xeddc7564 0xeddc7564 TPR13 : 0 0x40 0x40 DRAM parameters B: A64 H616 A133 DRAM clock : 648 648 648 DRAM type : 0x3 0x3 0x3 ZQ value : 0x3030303 - - ODT enabled : 0xe0e0e0e 0x1 - DX ODT : - 0x3030303 0x3030303 DX DRI : - 0xe0e0e0e 0xe0e0e0e CA DRI : - 0x1c12 0x1c12 PARA0 : - - 0x1 PARA1 : 0x1c12 0x30fb 0x30fb PARA2 : 0x1 0 0 MR0 : 0x30fb 0x840 0x840 MR1 : 0 0x4 0x4 MR2 : 0x840 0x8 0x8 MR3 : 0x4 0 0 TPR0 : 0x8 0xc0000a05 0 TPR2 : 0 0 0xc0000a05 TPR6 : 0 0x33808080 0x33808080 TPR10 : 0 0x2f0006 0x2f0006 TPR11 : 0 0xddddcccc 0xddddcccc TPR12 : 0xc0000a05 0xeddc7564 0xeddc7564 TPR13 : 0 0x40 0x40 DRAM parameters C: A64 H616 A133 DRAM clock : 648 648 648 DRAM type : 0x3 0x3 0x3 ZQ value : 0x3030303 - - ODT enabled : 0xe0e0e0e 0x1 - DX ODT : - 0x3030303 0x3030303 DX DRI : - 0xe0e0e0e 0xe0e0e0e CA DRI : - 0x1c12 0x1c12 PARA0 : - - 0x1 PARA1 : 0x1c12 0x30fb 0x30fb PARA2 : 0x1 0 0 MR0 : 0x30fb 0x840 0x840 MR1 : 0 0x4 0x4 MR2 : 0x840 0x8 0x8 MR3 : 0x4 0 0 TPR0 : 0x8 0xc0000a05 0 TPR2 : 0 0 0xc0000a05 TPR6 : 0 0x33808080 0x33808080 TPR10 : 0 0x2f0006 0x2f0006 TPR11 : 0 0xddddcccc 0xddddcccc TPR12 : 0xc0000a05 0xeddc7564 0xeddc7564 TPR13 : 0 0x40 0x40 DRAM parameters D: A64 H616 A133 DRAM clock : 648 648 648 DRAM type : 0x3 0x3 0x3 ZQ value : 0x3030303 - - ODT enabled : 0xe0e0e0e 0x1 - DX ODT : - 0x3030303 0x3030303 DX DRI : - 0xe0e0e0e 0xe0e0e0e CA DRI : - 0x1c12 0x1c12 PARA0 : - - 0x1 PARA1 : 0x1c12 0x30fb 0x30fb PARA2 : 0x1 0 0 MR0 : 0x30fb 0x840 0x840 MR1 : 0 0x4 0x4 MR2 : 0x840 0x8 0x8 MR3 : 0x4 0 0 TPR0 : 0x8 0xc0000a05 0 TPR2 : 0 0 0xc0000a05 TPR6 : 0 0x33808080 0x33808080 TPR10 : 0 0x2f0006 0x2f0006 TPR11 : 0 0xddddcccc 0xddddcccc TPR12 : 0xc0000a05 0xeddc7564 0xeddc7564 TPR13 : 0 0x40 0x40 DRAM parameters E: A64 H616 A133 DRAM clock : 648 648 648 DRAM type : 0x3 0x3 0x3 ZQ value : 0x3030303 - - ODT enabled : 0xe0e0e0e 0x1 - DX ODT : - 0x3030303 0x3030303 DX DRI : - 0xe0e0e0e 0xe0e0e0e CA DRI : - 0x1c12 0x1c12 PARA0 : - - 0x1 PARA1 : 0x1c12 0x30fb 0x30fb PARA2 : 0x1 0 0 MR0 : 0x30fb 0x840 0x840 MR1 : 0 0x4 0x4 MR2 : 0x840 0x8 0x8 MR3 : 0x4 0 0 TPR0 : 0x8 0xc0000a05 0 TPR2 : 0 0 0xc0000a05 TPR6 : 0 0x33808080 0x33808080 TPR10 : 0 0x2f0006 0x2f0006 TPR11 : 0 0xddddcccc 0xddddcccc TPR12 : 0xc0000a05 0xeddc7564 0xeddc7564 TPR13 : 0 0x40 0x40

Changing release back to Armbian_community_24.11.0-trunk.273 (just happened to have it from last time I tested a while back) seems to have posted into the kernel. I'll try an update && upgrade but I'm sure it will break again like before. Here's the armbianmonitor -u if it helps in any way: https://paste.armbian.com/zutopexulu Here's the u-boot from that version if it helps. I did modify the armbianenv values with: verbosity=8 earlycon=on fdt_addr_r=0x41000000 kernel_addr_r=0x41080000 ramdisk_addr_r=0x42080000 U-Boot SPL 2024.01-armbian-2024.01-S866c-Pb2fe-H0429-Vc98b-Bda0a-R448a (Oct 10 2024 - 02:38:10 +0000) DRAM: 128 MiB Trying to boot from MMC1 ns16550_serial serial@1c28800: pinctrl_select_state_full: uclass_get_device_by_phandle_id: err=-19 U-Boot 2024.01-armbian-2024.01-S866c-Pb2fe-H0429-Vc98b-Bda0a-R448a (Oct 10 2024 - 02:38:10 +0000) Allwinner Technology CPU: Allwinner V3s (SUN8I 1681) Model: PineCube IP Camera DRAM: 128 MiB Core: 47 devices, 20 uclasses, devicetree: separate WDT: Not starting watchdog@1c20ca0 MMC: mmc@1c0f000: 0, mmc@1c10000: 1 Loading Environment from FAT... Unable to use mmc 0:1... In: serial@1c28800 Out: serial@1c28800 Err: serial@1c28800 Autoboot in 1 seconds, press <Space> to stop switch to partitions #0, OK mmc0 is current device Scanning mmc 0:1... Found U-Boot script /boot/boot.scr 4107 bytes read in 2 ms (2 MiB/s) ## Executing script at 41900000 U-boot loaded from SD Boot script loaded from mmc 288 bytes read in 2 ms (140.6 KiB/s) 10752455 bytes read in 446 ms (23 MiB/s) 8994176 bytes read in 374 ms (22.9 MiB/s) Found mainline kernel configuration 18875 bytes read in 5 ms (3.6 MiB/s) Working FDT set to 41000000 Failed to load '/boot/dtb/overlay/sun8i-v3s-fixup.scr' Kernel image @ 0x41080000 [ 0x000000 - 0x893d80 ] ## Loading init Ramdisk from Legacy Image at 42080000 ... Image Name: uInitrd Image Type: ARM Linux RAMDisk Image (gzip compressed) Data Size: 10752391 Bytes = 10.3 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 41000000 Booting using the fdt blob at 0x41000000 Working FDT set to 41000000 Loading Ramdisk to 423be000, end 42dff187 ... OK Loading Device Tree to 42351000, end 423bdfff ... OK Working FDT set to 42351000 Starting kernel ...

You need to add the module config to the kernel configuration file and compile a new image. Edit the kernel configuration file manually. CONFIG_WLAN_VENDOR_MEDIATEK=y CONFIG_MT7601U=m Im very busy with work so I can’t do this for you right now.

Good to hear that something was found at least! Should the last build already have it incorporated because I still needed to modify the fdt/kernel/ramdisk variables in the armbianenv in order to get the process started? But it looks like turning it to verbosity=8 and earlycon=on didn't provide any additional details sadly. U-Boot SPL 2024.01-armbian-2024.01-S866c-P7738-Ha5c2-V1f00-Bb703-R448a (Mar 16 2025 - 04:03:33 +0000) DRAM: 128 MiB Trying to boot from MMC1 ns16550_serial serial@1c28800: pinctrl_select_state_full: uclass_get_device_by_phandle_id: err=-19 U-Boot 2024.01-armbian-2024.01-S866c-P7738-Ha5c2-V1f00-Bb703-R448a (Mar 16 2025 - 04:03:33 +0000) Allwinner Technology CPU: Allwinner V3s (SUN8I 1681) Model: PineCube IP Camera DRAM: 128 MiB Core: 47 devices, 20 uclasses, devicetree: separate WDT: Not starting watchdog@1c20ca0 MMC: mmc@1c0f000: 0, mmc@1c10000: 1 Loading Environment from FAT... Unable to use mmc 0:1... In: serial@1c28800 Out: serial@1c28800 Err: serial@1c28800 Autoboot in 1 seconds, press <Space> to stop switch to partitions #0, OK mmc0 is current device Scanning mmc 0:1... Found U-Boot script /boot/boot.scr 5475 bytes read in 3 ms (1.7 MiB/s) ## Executing script at 41900000 U-boot loaded from SD 241 bytes read in 2 ms (117.2 KiB/s) Load fdt: /boot/dtb/sun8i-s3-pinecube.dtb 12284163 bytes read in 509 ms (23 MiB/s) 11014744 bytes read in 458 ms (22.9 MiB/s) Found mainline kernel configuration 19691 bytes read in 6 ms (3.1 MiB/s) Working FDT set to 41000000 Kernel image @ 0x41080000 [ 0x000000 - 0xa81258 ] ## Loading init Ramdisk from Legacy Image at 42080000 ... Image Name: uInitrd Image Type: ARM Linux RAMDisk Image (gzip compressed) Data Size: 12284099 Bytes = 11.7 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 41000000 Booting using the fdt blob at 0x41000000 Working FDT set to 41000000 Loading Ramdisk to 42248000, end 42dff0c3 ... OK Loading Device Tree to 421da000, end 42247fff ... OK Working FDT set to 421da000 Starting kernel ...

Is it possible to use usb-wifi on an 8812au chip? I tried installing the driver, but it doesn't work: klipper@transpeed-8k618-t:~$ sudo dkms status [sudo] password for klipper: rtl8812au/5.13.6-23, 6.12.11-edge-sunxi64, aarch64: installed klipper@transpeed-8k618-t:~$ sudo modprobe --force 8812au modprobe: ERROR: could not insert '8812au': Exec format error I also have a Mediatek mt7601u from the recommended list, but it doesn't work either. I used to flash the file Armbian-unofficial_25.05.0-trunk_Transpeed-8k618-t_bookworm_edge_6.12.11_server.img.xz (20250306 Latest)

I'm building a multi-zone music streaming setup built around an SBCs running Snapcast/MPD and this MA12070P board (AliExpress link). From the pinout diagrams it looks like the board is the same as the Merus Audio Amp Hat just with a built in USB-C PD supply (why I want to use this board). If it's a clone then it looks like support is in Raspberry Pi OS, but I want to use the Radxa Zero 3W since I can get it at a similar price point with better specs. This is my first embedded project since ~2019 so a bit out of my depth when it comes to device tree overlays. How would I write a DTO to enable audio output to this device?