All Activity

@MattWestB@Thiên Thư Lục In this directory I have put an experimental kernel with a kernel patch that should fix some USB3 issues. If may want to try and experiment if it works for you. It is based upon kernel 6.16. You only need to install the image and dtb packages, headers are only if you need to compile some thirdy party drivers.

Thanks. I have tried and compiled image, but when I boot with SD card nothing appears, and Serial interface seems that disconnects. I have tried both with "uboot" button pressed and not. These are, I think, the gpio you asked gpio_encrypt { compatible = "allwinner,gpio_encrypt"; gpio_number_sun = <0x05>; gpio1_value = <0x00>; gpio2_value = <0x01>; gpio3_value = <0x01>; gpio4_value = <0x01>; gpio5_value = <0x01>; gpio1_pin = <0x53 0x08 0x0d 0x01 0xffffffff 0xffffffff 0x00>; gpio2_pin = <0x53 0x08 0x09 0x01 0xffffffff 0xffffffff 0x00>; gpio3_pin = <0x53 0x08 0x01 0x01 0xffffffff 0xffffffff 0x00>; gpio4_pin = <0x53 0x07 0x06 0x01 0xffffffff 0xffffffff 0x00>; gpio5_pin = <0x53 0x07 0x07 0x01 0xffffffff 0xffffffff 0x00>; status = "okay"; linux,phandle = <0x17d>; phandle = <0x17d>; }; or these ones? boot_init_gpio { device_type = "boot_init_gpio"; status = "okay"; gpio0 = <0x53 0x08 0x0b 0x01 0xffffffff 0xffffffff 0x00>; gpio1 = <0x53 0x08 0x0c 0x01 0xffffffff 0xffffffff 0x01>; gpio2 = <0x53 0x08 0x0e 0x01 0xffffffff 0xffffffff 0x00>; };

So maybe it would be enough if the community version of U-Boot were updated to version v2025.07 and it would solve the reboot problem for this SBC, just like it happened for the Orange Pi Zero 3 where updating U-Boot to v2025.04 solved the problem of decoding RAM size on the SBC

Today it is EDGE v6.15 no v6.16.

Recommended to upgrade U-Boot to version v2025.07 This version has big changes for allwinner (sunxi) chips. This concerns the initialization of a non-standard size of RAM (1.5; 2.5 GB), downloads from eMMC.....

Yes, that's right. This is relevant to the issue under discussion.

While searching the internet for information about the reboot problem, I found this information but I don't know if it is helpful for us?

Is anyone using Linux kernel-edge on an Orange Pi Zero v1? Are they kernel versions 6.14 or 6.16? Does that also cause the reboot problem?

@Nick A I read the thread you shared. I think I understand it now, I’m about 30% done. I have the dram settings already. Thanks for your help! I’ll ask you again if I got some problem in the future.

data corruption can always happen when there is a power outage. Could be by chance that one device suffered while the other didn't. Best way to prevent is as guessed a small PSU which ideally tells the device 'there is an outtage, please shut down before I run out of battery". Having OS or data or microSD, eMMC or NVMe does not make a difference since the OS decides when and how often data is written. NVMe are even more fragile since they often come with an internal cache themselves that is emptied onto the actual flash asynchronously. Disabling write caches may lower chances for data corruption but for once can decrease performance a lot and for the other significantly decreases the lifetime of microSD cards.

I'm not sure what you're asking. I'm requesting information because I am seeing information stating that there is a working linux kernel that exists, but I don't know how to bridge that into a form where that kernel could be built or compiled into an image. Can what is on that github page be input into the build process? I've looked at what it takes to build Armbian from source and I understand the instructions when the board being built fits the categories in the instructions, but I'm not sure if that github kernel is useable or can be applied in that buidl process.

Hi everyone, Two Questions: 1) I have two Orange Pi 3 LTS boards at home. I installed AdGuard Home on one, serving as DHCP (I'll call it OP1), and on the other, I left a Docker with other apps (qbittorrent, omv6, samba, etc. - I'll call it OP2). Both are installed via SD card. But if there's a power outage, OP1 works normally again after, without any problems. But OP2, on the other hand, has experienced data corruption several times. Does anyone know why OP1 works fine and OP2 runs the risk of having to reinstall the system in such a case? 2) If I used a board with EMMC memory and unified all the systems on it, would the chances of this decrease, or is it unrelated? I see other people with same problem. Only using a UPS to prevent the OP2 problem? Thanks

@Randlin have you tried adding secure boot to @sicxnull build. If that doesn’t work you’ll need to play with the dram code. I don’t have time or a 1.5g board. https://github.com/sicXnull/armbian-build/tree/X96Q-TVBOX-LPDDR3

For the Orange Pi Zero v1, it might be recommended to upgrade U-Boot to version v2025.4. I remember having similar problems with the Orange Pi Zero 3, and after the U-Boot update, the reboot works correctly and doesn't shut down the computer.

I see that the reported problem was raised in another topic:

There is certainly nothing planned. In general most of the open source community has moved away from working on amlogic based devices as the support from amlogic if lacking (and given the arm cpu space where all arm cpu vendors don't really support main line linux very much, amlogic is significantly even less supportive). So these days around armbian in particular most developers choose to invest there volunteer time in Rockchip cpus (and more recently some in allwinner cpus). But this is open source and community driven. So anyone is welcome to pitch in and do the heavy lifting to support it if they want. That is how most boards get support, is that someone with an interest volunteers to do the work.

Okay that detects 1.5gb at spl, but then detects 2gb at uboot, just like the first patch I tried. Maybe something to do with me currently using the U-Boot DTB from X96-q, a 2gb device? I did try a different config for a different tv box as well (transpeed), but that had the same result. U-Boot SPL 2025.01-armbian-2025.01-S6d41-P37d4-H8869-V004f-Bb703-R448a-dirty (Aug 13 2025 - 17:14:56 +0000) DRAM base address is defined as 0x40000000 DRAM has 15 b/raw, 10 b/col, 4 B/width, 2 #rank and 8 #bank DRAM top address must be less than 0x80000000 DRAM top address must be less than 0x60000000 DRAM: 1536 MiB Trying to boot from MMC1 NOTICE: BL31: v2.10.14(debug):armbian NOTICE: BL31: Built : 15:34:29, Aug 13 2025 NOTICE: BL31: Detected Allwinner H616 SoC (1823) NOTICE: BL31: Found U-Boot DTB at 0x4a0b2520, model: hechuang,x96-q LPDDR3 INFO: ARM GICv2 driver initialized INFO: Configuring SPC Controller INFO: PMIC: Probing AXP305 on RSB ERROR: RSB: set run-time address: 0x10003 INFO: Could not init RSB: -65539 INFO: BL31: Platform setup done INFO: BL31: Initializing runtime services INFO: BL31: cortex_a53: CPU workaround for erratum 855873 was applied INFO: BL31: cortex_a53: CPU workaround for erratum 1530924 was applied INFO: PSCI: Suspend is unavailable INFO: BL31: Preparing for EL3 exit to normal world INFO: Entry point address = 0x4a000000 INFO: SPSR = 0x3c9 INFO: Changed devicetree. ns16550_serial serial@5000000: pinctrl_select_state_full: uclass_get_device_by_phandle_id: err=-19 U-Boot 2025.01-armbian-2025.01-S6d41-P37d4-H8869-V004f-Bb703-R448a-dirty (Aug 13 2025 - 17:14:56 +0000) Allwinner Technology CPU: Allwinner H616 (SUN50I) Model: hechuang,x96-q LPDDR3 DRAM: 2 GiB (effective 0 Bytes)

Thanks for putting all this together — it’s a fantastic resource for anyone still trying to get the most out of these cheap RK3318 boxes. Fully agree on avoiding them for anything critical, but for tinkering and learning, this thread is gold.

Yep, I’ve been testing the 1.5GB version with Armbian. Images are still rough—some issues with AdGuard Home not starting properly after reboot, and a few quirks with networking. Promising board though, especially for the price.

Check if AdGuard is binding to the correct IP after reboot. You can verify this in the AdGuardHome.yaml file—make sure bind_host is set to 0.0.0.0 or your static IP. Also confirm the service is listening with sudo netstat -tulnp | grep 3000 and check logs with journalctl -u AdGuardHome.

Another phenomenon is also observed on the Orange Pi Zero v1. Issuing the reboot command causes the computer to not restart, requiring the power supply to be turned off and on again.

@RandlinTry removing 110,111,113 patches in my uboot. Then add https://github.com/armbian/build/blob/main/patch/u-boot/v2025-sunxi/0009-sunxi-h616-dram-support-1.5GB-RAM-size.patch

So I copied the patches from Minimyth2 to your Armbian and it built, however it is now detecting 2gb ram lol.... Will try to see if I can find a way to hardcode 1.5gb

The Mesa 25.2 release introduces support for AFBC compressed YUV textures in the Panfrost driver for ARM Mali GPUs, enabling more efficient memory bandwidth and power usage in video playback and real-time texture processing. View the full article

“This DRAM setup is currently not supported. resetting “ You need to extract your boot0 and use sunxi-fw to read your dram settings. sunxi-fw info -v boot0.bin Go back one page.