~> cat /sys/class/graphics/fb0/virtual_size
1024,768

I've created a script that fix that with recompiling initramfs, adding necessary /lib/firmware/edid/1920x1080.bin file directly into it.

Feel free to use, suggestions are welcome.

P.S.
Please add tags A20-OLinuXino-LIME2 and T2-OLinuXino-LIME2

fix_hdmi_resolution.sh

The 1st image was adding extension 'u-boot-menu'; build ended in success, but have not tested it on HW. I saw in extlinux.conf that there was no 'FDT' line (with  sun8i-h3-nanopi-neo.dtb), which I did ad myself in own extlinux testting/semi-automatic .conf generation, but as BOARD=nanopineo, the U-Boot can know a default to be loaded, or nothing at all as the DT in the U-Boot is likely good enough or almost the same as th eone from kernel, but maybe I test/challenge that later.

The 2nd image build was just 'u-boot-menu' replaced by 'grub-with-dtb':

cd /local/s0/armbuild/
sudo btrfs subvolume create nanopineo
sudo chown 1000:1000 nanopineo
cd nanopineo
git clone https://github.com/armbian/build
cd build
./compile.sh \
BOARD=nanopineo \
RELEASE=trixie \
BRANCH=edge \
BUILD_DESKTOP=no \
BUILD_MINIMAL=yes \
NETWORKING_STACK=systemd-networkd \
FIXED_IMAGE_SIZE=2G \
IMAGE_PARTITION_TABLE=gpt \
BOOTPART_REQUIRED=yes \
BOOTSIZE=256 \
BOOTFS_TYPE=fat \
ROOTFS_TYPE=btrfs \
BTRFS_COMPRESSION=zstd \
COMPRESS_OUTPUTIMAGE=sha \
EXTRAWIFI=no \
KERNEL_CONFIGURE=no \
KERNEL_BTF=no \
KERNEL_GIT=shallow \
ENABLE_EXTENSIONS=watchdog,net-systemd-networkd,uboot-btrfs,grub-with-dtb

It then fails with:

[🔨]   E: Unable to locate package grub-efi-armhf-bin
[🔨]   E: Unable to locate package grub-efi-armhf
 

The issue here is that the Debian package must be: grub-efi-arm

Also I now remember an issue from years ago when I made a non-EFI system UEFI bootable, must have been RPi thing or so, but also did it several times for x86. AFAIR if only grub-efi-arm and grub-efi-arm-bin, you get into trouble later on, can be years later when dist-upgrading in-place. So I just do 'apt install grub-efi' which then works fine as is pulls in also some dependencies. Not 'efibootmgr', that is just recommended, and I add that manually as most systems allow storing boot URL's in SPI-flash or so, certainly the KVM ones where machine is using EDK2 UEFI, which I use extensively.

So it seems to me that this is an architecture naming or aliasing issue, like we have amd64 vs. x86-64 vs. x86_64 and arm64 vs. aarch64

If just 'grub-efi' that also works for riscv I guess, so avoiding this naming/aliasing issue and also better future proof. It might be that dependencies are not supported in image building, I don't know enough about that to judge. I have also not looked in detail at size impact, but it is relative I would say. There is plenty of other issues that claim more space or can reduce way more. There were more issues, but I solved those via trial-error, no show-stoppers.

Although topic tag NanoPi-NEO, this is more like an Armbian Build issue, but for me it is about my 5 NanoPi-NEO's that are still great (and still overkill for their 4x Cortex-A7), but they are still Debian 32-bit ARMv7, not like unsupported RPi0/1 single-core ARMv6 (arm11* or older). A reason for wanting EFI bootloader is that upgrading/testing can by done in a KVM running on RPi4 (fast USB3-SSD) or ROCK3A (fast PCI-Ev3x2 NVMe) while using (differential) btrfs send|receive, which is way faster than on SD-cards en real HW. The other option is via U-Boot (QEMU -enable-kvm option), is supported for 64-bit in Armbian by BOARD=qemu-uboot-arm64, not for 32-bit.

https://github.com/NickAlilovic/build/tree/Radxa-A7A

https://github.com/NickAlilovic/build/releases

To build your own image:

git clone https://github.com/NickAlilovic/build.git --branch Radxa-A7A

./compile.sh

"do not change the kernel configuration"

"show csc/wip/eos/tvb"

"I understand and agree"

"radxa-cubie-a7a" or "radxa-cubie-a7z"

rest is up to you...

Should you choose to run Armbian, ensure the CPU has adequate cooling by installing the Radxa Heatsink.
https://radxa.com/products/accessories/heatsink-6530b
https://radxa.com/products/accessories/heatsink-6540b

Armbian_23.5.2_Nanopineo_bookworm_current_6.1.30

And then I froze these packages to keep the working firmware and kernel:

armbian-firmware/bookworm,bookworm 24.2.1 all [upgradable from: 23.05.1--1-SAfece-B6ae3]
linux-dtb-current-sunxi/bookworm 24.2.1 armhf [upgradable from: 23.05.1--6.1.30-Sa343-D8bc9-P73a0-C162eHfe66-HK01ba-V014b-B9c18]
linux-image-current-sunxi/bookworm 24.2.1 armhf [upgradable from: 23.05.1--6.1.30-Sa343-D8bc9-P73a0-C162eHfe66-HK01ba-V014b-B9c18]
linux-u-boot-nanopineo-current/bookworm 24.2.1 armhf [upgradable from: 23.05.1--2022.04-Se4b6-P6b27-H0429-Ve2df-B91a8]

I know there are newer official builds from when it was still supported, but I can't find them available for download anymore.  Do you know if there's an archive somewhere that would have it?  Thanks.

https://www.cnx-software.com/2023/07/03/orange-pi-zero-3-allwinner-h618-sbc-ships-with-up-to-4gb-ram/

https://liliputing.com/orange-pi-zero-3-is-a-cheap-tiny-single-board-pc-with-up-to-4gb-ram-gigabit-ethernet-and-allwinner-h618/

http://www.orangepi.org/html/hardWare/computerAndMicrocontrollers/details/Orange-Pi-Zero-3.html

even the linux images is very 'fresh' as in that they are just released *yesterday* 😄

https://www.cnx-software.com/2025/07/07/allwinner-a527-t527-and-a733-datasheets-user-manuals-and-linux-sdk-released/

http://www.orangepi.org/html/hardWare/computerAndMicrocontrollers/details/Orange-Pi-4-Pro.html

Another Allwinner board dropped

figuring out the wifi chip is always hard, seem to be

https://www.taobao.com/list/item/931793873067.htm

https://pine64.sfo3.cdn.digitaloceanspaces.com/doc/datasheet/oz64/AIC8800DC Datasheet v1.0.pdf

as usual, it is uncertain if drivers and firmware is after all available.

Ethernet according to CNX seemed to be YT8531CA 
Ethernet seemed to be same as that in OrangePi Zero 3

https://www.cnx-software.com/2023/07/03/orange-pi-zero-3-allwinner-h618-sbc-ships-with-up-to-4gb-ram/

WiFi is 'more critical' these days, if it is closed sourced and no firmware, then it is good as just a door stop.

Then that thare are other stuff the figure out especially the :

- DRAM controller,

- and various DRAM timing and configuration aspects

- many other low level specific stuff to even have u-boot to boot it up to the linux prompt.

- then the other devices e.g. uart etc. 

- then HDMI

- then gpu acceleration (or at least display video, not playing media yet)

- then media 

- and finally NPU, don't seemed documented yet

- many more known or unknown unknowns, audio etc

Logs:

Hi Armbian and sunxi developers,

I would like to share an industrial-grade diagnostic report and a 100% verified solution regarding a severe, reproducible boot deadlock on Allwinner H2+/H3 platforms (specifically tested on Banana Pi P2 Zero) utilizing onboard eMMC.

=== 1. SYMPTOM ===
During rigorous power-cycling stress tests (hard power-off during random kernel init/write phases), the system randomly bricks on subsequent boots, showing a "dropping to shell" (initramfs / BusyBox prompt) or failing completely during the U-Boot phase with a non-existent MMC device error. 

A severe "vicious cycle" (degrading cycle count) was observed: initially, the failure occurred around the 11th cycle. After optimization, it pushed to the 78th/93rd cycle, but eventually dropped down to a catastrophic failure after just 12 cycles, locking the eMMC in an unbootable state.

=== 2. ROOT CAUSE ANALYSES ===
We discovered a multi-layered hardware/software deadlock (a conceptual deadlock between the eMMC firmware and the Linux kernel/U-Boot drivers):

A) eMMC Internal State Hang: Sudden power loss during write operations forces the eMMC controller's FTL (Flash Translation Layer) into an internal Power Loss Recovery routine upon next boot. It flags this state in its internal NVRAM.
B) Aggressive Host Initialization: While the eMMC controller is busy performing its background recovery, the U-Boot and Linux Kernel drivers immediately flood the MMC bus with high-frequency initialization sequences and commands (e.g., trying to shift to high-speed modes like HS200 or DDR at 1.8V).
C) Runtime Power Management Interruption: The eMMC controller, overwhelmed by background recovery and high-speed host commands, responds with a timeout. The `sunxi-mmc` driver interprets this timeout as a fatal hardware failure and immediately triggers Runtime PM, disabling the MMC clock (CLK) to save power. 
D) The Deadlock: Disabling the CLK freezes the eMMC internal microcontroller mid-flight. Without a host clock, the eMMC cannot finish its internal Power Loss Recovery. The corrupt state remains burned into the NVRAM flag. Subsequent cold resets wake up the eMMC with the exact same corrupt flag, trapping the board in an permanent boot hivel.

=== 3. VERIFIED SOLUTION (320+ Cycles Success) ===
To break this deadlock, we had to apply a 5-step cross-layer configuration (U-Boot, Device Tree, and Filesystem). After applying these fixes, the device successfully passed a brutal 5-hour stress test, completing 320 consecutive aggressive power-cycles without a single warm-boot or failure.

Here is the exact production-ready recipe:

1) Limit eMMC Frequency & Disable High-Speed Modes (DTB)
Prevent the kernel from driving the chip into unstable timing states during the sensitive boot phase. Limit the bus to a stable, industrial 52 MHz clock.
In the device tree, target the exact eMMC controller node (mmc@1c1f000 for mmc2 on BPi-P2Z):
&mmc2 {
    max-frequency = <52000000>;
    /delete-property/ mmc-hs200-1_8v;
    /delete-property/ mmc-ddr-1_8v;
};

2) Disable MMC Runtime Power Management & Enforce Continuous Clock (DTB)
Force the host to maintain a constant clock signal on the MMC bus, allowing the eMMC microcontroller to finish its internal recovery routines even if a timeout occurs.
&mmc2 {
    non-removable;
    keep-power-in-suspend;
    no-mmc-runtime-pm;
    status = "okay";
};

3) Enforce U-Boot Level eMMC Bus Reset and Nagging Clean-up (boot.cmd / boot.scr)
Clear the internal state-machine of the eMMC controller *before* U-Boot attempts to read large kernel files from the ext4 root partition.
Add these exact lines to the very beginning of your /boot/boot.cmd before compiling it to boot.scr:
# Force MMC2 bus reset and NVRAM buffer flush
mmc dev 2
mmc rescan
# Provide a 2-second silent window for the eMMC FTL to safely finish house-keeping
sleep 2

4) Register-Level Hardware Watchdog Activation in U-Boot (boot.cmd / boot.scr)
Ensure a hardware-level warm-boot safety net in case the eMMC hangs during early bootloader stages before the kernel can initialize its own watchdog.
Add this at the top of /boot/boot.cmd:
# Enable Allwinner H3 belső Watchdog (16-second threshold)
mw.l 0x01c20c90 0x00000000
mw.l 0x01c20c94 0x00000b03

5) Mitigate Write Stress on Filesystem (/etc/fstab)
Reduce the probability of power-loss catching the eMMC during a critical metadata/journal write phase.
Modify the root partition mount options in /etc/fstab:
UUID=your-uuid-here  /  ext4  defaults,noatime,nodiratime,commit=60,barrier=0  0  1

=== CONCLUSION ===
By combining a U-Boot level `mmc rescan` + `sleep 2` (which clears the FTL buffers) with the Device Tree `no-mmc-runtime-pm` (which guarantees uninterrupted host clock), we permanently fixed this elusive hardware/software race condition. 

I highly recommend incorporating these MMC stability flags into the standard Armbian dts targets for Allwinner boards deployed in mission-critical or unstable power environments.

Best regards,
mihint
 

armbianarm_errors.txt

is there currently support for NVMe storage in Armbian trunk?

I tried to flash the latest build, added nvme ssd storage - but it is not seen in the system.

What to check?

RADXA Cubie A5E 1GB RAM Armbian CLI stuck while uboot via sdcard

seems to be an issue with the uboot which hangs very early. 

With original debian image from radxa the board is b ooting and running. But i intend to use the armbian version with newer debian and kernel.

What can i do?

Regards Rolf

I am experiencing a persistent boot issue with my Orange Pi Win Plus running Armbian, used as a headless server.

The Problem: Whenever the board suffers a power loss (unplugged) or I issue a system reboot, it fails to start automatically. The power LED stays on, but the system/network never comes up. To get it to boot, I have to go through a frustrating manual routine: manually holding/pressing the power button, sometimes plugging/unplugging the HDMI cable, and repeating this process a couple of times before it finally kicks in.

What I have already checked/ruled out:

Power supply is NOT the issue: I have tested multiple different power adapters and tried powering the board through both the standard DC jack and the micro-USB port — the behavior remains identical.

I am running a clean Armbian setup, but the board refuses to perform a clean automated cold start or reboot on its own.

System Info & Configuration:

Plaintext

# PLEASE DO NOT EDIT THIS FILE
BOARD=orangepiwin
BOARD_NAME="Orange Pi Win"
BOARDFAMILY=sun50iw1
BUILD_REPOSITORY_URL=https://github.com/armbian/build
BUILD_REPOSITORY_COMMIT=fd4ebfd1e
LINUXFAMILY=sunxi64
ARCH=arm64
BOOT_SOC=
IMAGE_TYPE=nightly
BOARD_TYPE=csc
INITRD_ARCH=arm64
KERNEL_IMAGE_TYPE=Image
KERNEL_TARGET=current,edge,legacy
KERNEL_TEST_TARGET=current
FORCE_BOOTSCRIPT_UPDATE=
FORCE_UBOOT_UPDATE=
OVERLAY_DIR="/boot/dtb/allwinner/overlay"
VENDOR="Armbian"
VENDORCOLOR="247;16;0"
VENDORDOCS="https://docs.armbian.com"
VENDORURL="https://www.armbian.com/"
VENDORSUPPORT="https://forum.armbian.com"
VENDORBUGS="https://www.armbian.com/bugs"
BOOTSCRIPT_FORCE_UPDATE="no"
BOOTSCRIPT_DST="boot.cmd"
VERSION=26.11.0-trunk.25
REVISION=26.11.0-trunk.25
BRANCH=current
Linux orangepiwin 6.18.46-current-sunxi64 #1 SMP PREEMPT Sun Aug 23 12:27:10 UTC 2026 aarch64 GNU/Linux
verbosity=1
bootlogo=false
console=both
disp_mode=1920x1080p60
overlay_prefix=sun50i-a64
rootdev=UUID=5aab4b22-0cdc-4f77-a4c4-f79a401b64df
rootfstype=ext4
overlays=
hdmi_blank=off
edid=false
disp_disable=1
usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u

Has anyone encountered this behavior on the Allwinner A64 platform? Is there a known workaround, device tree patch, or PMU/u-boot configuration to force this board to reliably boot up automatically after power restoration without requiring physical button presses or HDMI tricks?

Any advice would be greatly appreciated. Thanks in advance!

6.18.43 armbian debian build. It booted fine from SD and I then flashed the boot rom to the eeprom so I could boot from USB (sudo flashcp /usr/lib/linux-u-boot-current-orangepizero3/u-boot-sunxi-with-spl.bin /dev/mtd0)

I was able to boot from USB0 fine but not from the USB ports USB1 and 2 on the 13 pin header.

With the help of google and some ai I found that if I run the following my sd card is recognised when plugged into usb1

fdt addr bbf107b0

fdt set /soc/usb@5310000 status "okay"

bind /soc/usb@5310000 ehci_generic

usb reset

usb storage



That produced:



Bus usb@5310000: 2 USB Device(s) found

1 Storage Device(s) found

Kingston DataTraveler 3.0

57.7 GB

The uboot seems to be missing the commands for the other usb ports.

fdt addr ${fdtcontroladdr}

Working FDT set to bbf107b0

=> fdt set /soc/usb@5310000 status okay

=> fdt print /soc/usb@5310000

usb@5310000 {

compatible = "allwinner,sun50i-h616-ehci", "generic-ehci";

reg = <0x05310000 0x00000100>;

interrupts = <0x00000000 0x0000001e 0x00000004>;

clocks = <0x00000002 0x0000006a 0x00000002 0x0000006e 0x00000002 0x00000064>;

resets = <0x00000002 0x0000002c 0x00000002 0x00000030>;

phys = <0x0000001e 0x00000002>;

phy-names = "usb";

status = "okay";

phandle = <0x00000054>;

};

=> fdt set /soc/usb@5310400 status okay

=> fdt set /soc/usb@5311000 status okay

=> fdt set /soc/usb@5311400 status okay

=> bind /soc/usb@5310000 ehci_generic

=> bind /soc/usb@5310400 ohci_generic

=> bind /soc/usb@5311000 ehci_generic

=> bind /soc/usb@5311400 ohci_generic

=> usb reset

resetting USB...

USB EHCI 1.00

USB OHCI 1.0

USB EHCI 1.00

USB OHCI 1.0

USB EHCI 1.00

USB OHCI 1.0

Bus usb@5200000: 1 USB Device(s) found

Bus usb@5200400: 1 USB Device(s) found

Bus usb@5310000: 2 USB Device(s) found

Bus usb@5310400: 1 USB Device(s) found

Bus usb@5311000: 1 USB Device(s) found

Bus usb@5311400: 1 USB Device(s) found

scanning usb for storage devices... 1 Storage Device(s) found

=>

does anyone have any advice on how i can update the image file code to support the additional usb ports. Ive tried looking at how to rebuild the u-boot-sunxi-with-spl.bin but could do with some guidance as ive not done this before.

Many thanks

Trev

Dug into it a bit over serial console:

The default boot_targets is fel nvme0 mmc_auto usb0 pxe dhcp — NVMe is checked before the SD/eMMC. Radxa hit the same issue on the RK3588 boards and fixed it upstream (radxa/u-boot#25, "give SD higher boot priority than NVME"). Would be great to see the same fix applied here.

I tried working around it manually (setenv boot_targets 'mmc0 mmc1 nvme0 usb0 pxe dhcp'), which does work for that boot — SD is picked up correctly when present. But saveenv fails with "Unable to use mmc 0:1... Failed (1)", so the change doesn't survive a reboot. Looks like this build uses CONFIG_ENV_IS_IN_FAT targeting mmc 0:1, but the Armbian SD image ships a single ext4 partition there (confirmed with fstype mmc 0:1 → ext4), so the environment can never actually be saved.

Is this a known limitation, or is there a recommended way to get persistent SD-over-NVMe priority on this board right now?

Anyway I thought I would have ago at creating an image, I suppose given the age of the board issues are to be expected. I have had some success in fixes some of the issues encountered despite being relatively new to Armbian and Linux in general. After learning how to create patches, firstly I managed to get UART2 which was originally conflicting with the PMU as they shared the same assigned interrupt number of 3. From what I can tell this different to the normal PMU which I find that the power chip is normally referred to as there also appears to be some internal component within the A10 also called the 'PMU' . This seems to be something to do with core monitor as the A20 chip features 2 of these 'PMU's, one for each core. Looking at the user manual suggest that this should be 49. Now this has been patched I can use UART2 without getting an error although it is exposed as ttyS1 for some reason that I have yet to figure out.

The second patch I made was to get HDMI output working which I was able to do by using the Cubieboard as a point of reference as they share similar hardware. I found this out by initially using images targeted at the Cubieboard as they appear to be a lot more recent and provide HDMI out so I knew that copying the sections other would. Additionally I found  a way to get it working on my main 4K monitor after coming across a post which suggested lowering the size of the CMA buffer from the default size of 128mb to 64mb.

Now again the main problem I face is when I try to shutdown, this time it relates to a kernel panic:

[ 2508.547646] WARNING: CPU: 0 PID: 1 at drivers/i2c/i2c-core.h:41 i2c_transfer+                                                                             0x93/0xbc
[ 2508.561239] No atomic I2C transfer handler for 'i2c-1'
[ 2508.571971] Modules linked in: cfg80211 btusb btintel btrtl btbcm bluetooth a                                                                             xp20x_adc sun4i_gpadc_iio industrialio lima gpu_sched r8188eu(C) sun4i_ts ecdh_g                                                                             eneric rfkill ecc joydev input_leds sunxi_cedrus(C) v4l2_mem2mem videobuf2_dma_c                                                                             ontig videobuf2_memops videobuf2_v4l2 videobuf2_common zram evdev uio_pdrv_genir                                                                             q display_connector uio cpufreq_dt nfsd auth_rpcgss sch_fq_codel nfs_acl lockd g                                                                             race sunrpc ip_tables x_tables autofs4 pinctrl_axp209 sun4i_gpadc sunxi phy_gene                                                                             ric gpio_keys icplus(E)
[ 2508.635429] CPU: 0 PID: 1 Comm: systemd-shutdow Tainted: G         C  E     5                                                                             .15.32-sunxi #trunk
[ 2508.651044] Hardware name: Allwinner sun4i/sun5i Families
[ 2508.663328] [<c010cea9>] (unwind_backtrace) from [<c01095b9>] (show_stack+0x1                                                                             1/0x14)
[ 2508.678114] [<c01095b9>] (show_stack) from [<c09cc035>] (dump_stack_lvl+0x2b/                                                                             0x34)
[ 2508.692774] [<c09cc035>] (dump_stack_lvl) from [<c011b5a9>] (__warn+0xad/0xc0                                                                             )
[ 2508.707135] [<c011b5a9>] (__warn) from [<c09c5c23>] (warn_slowpath_fmt+0x5f/0                                                                             x7c)
[ 2508.721785] [<c09c5c23>] (warn_slowpath_fmt) from [<c0795a5f>] (i2c_transfer+                                                                             0x93/0xbc)
[ 2508.736949] [<c0795a5f>] (i2c_transfer) from [<c0795ac3>] (i2c_transfer_buffe                                                                             r_flags+0x3b/0x50)
[ 2508.752981] [<c0795ac3>] (i2c_transfer_buffer_flags) from [<c0697577>] (regma                                                                             p_i2c_write+0x13/0x24)
[ 2508.769489] [<c0697577>] (regmap_i2c_write) from [<c0694023>] (_regmap_raw_wr                                                                             ite_impl+0x48b/0x560)
[ 2508.786008] [<c0694023>] (_regmap_raw_write_impl) from [<c0694139>] (_regmap_                                                                             bus_raw_write+0x41/0x5c)
[ 2508.802806] [<c0694139>] (_regmap_bus_raw_write) from [<c06939b1>] (_regmap_w                                                                             rite+0x35/0xc8)
[ 2508.818874] [<c06939b1>] (_regmap_write) from [<c06948b5>] (regmap_write+0x29                                                                             /0x3c)
[ 2508.834263] [<c06948b5>] (regmap_write) from [<c069e723>] (axp20x_power_off+0                                                                             x23/0x30)
[ 2508.850053] [<c069e723>] (axp20x_power_off) from [<c0137ded>] (__do_sys_reboo                                                                             t+0xf5/0x16c)
[ 2508.866244] [<c0137ded>] (__do_sys_reboot) from [<c0100061>] (ret_fast_syscal                                                                             l+0x1/0x52)
[ 2508.882357] Exception stack(0xc154dfa8 to 0xc154dff0)
[ 2508.895490] dfa0:                   4321fedc bef4aaa8 fee1dead 28121969 4321f                                                                             edc 00000000
[ 2508.911883] dfc0: 4321fedc bef4aaa8 bef4aaa4 00000058 bef4aaa8 bef4aaa4 fffff                                                                             000 bef4aaac
[ 2508.928357] dfe0: 00000058 bef4aa1c b6eb81b5 b6e367e6
[ 2508.941715] ---[ end trace 8381275b8efb7dea ]---
[ 2510.584023] i2c i2c-1: mv64xxx: I2C bus locked, block: 1, time_left: 0
[ 2511.128016] Kernel panic - not syncing: Attempted to kill init! exitcode=0x00                                                                             000000
[ 2511.175494] CPU: 0 PID: 1 Comm: systemd-shutdow Tainted: G        WC  E     5                                                                             .15.32-sunxi #trunk
[ 2511.192848] Hardware name: Allwinner sun4i/sun5i Families
[ 2511.206836] [<c010cea9>] (unwind_backtrace) from [<c01095b9>] (show_stack+0x1                                                                             1/0x14)
[ 2511.223311] [<c01095b9>] (show_stack) from [<c09cc035>] (dump_stack_lvl+0x2b/                                                                             0x34)
[ 2511.239614] [<c09cc035>] (dump_stack_lvl) from [<c09c5a4d>] (panic+0xc1/0x238                                                                             )
[ 2511.255555] [<c09c5a4d>] (panic) from [<c011fd5d>] (complete_and_exit+0x1/0x1                                                                             8)
[ 2511.271612] [<c011fd5d>] (complete_and_exit) from [<fee1dead>] (0xfee1dead)
[ 2511.287376] ---[ end Kernel panic - not syncing: Attempted to kill init! exit                                                                             code=0x00000000 ]---

I have seen 1 or 2 other post which appear to be a similar issue.

Aside from that SPI does not work, but I gather this is currently a more general issue due to changes in the way the SPIDEV works. it's strange, I can enable the overlay and specify the bus and it shows up under /dev as expected but it does not appear to be sending any date when try to interface with LCD screen. I did a loopback test and it return all zero as if the pins where disconnected. The last version I found it correctly worked on was a Cubieboard image with kernel 5.10. I did come across one post which suggested a possible fix although I'm not sure if this has been implemented yet.

I know this probably a bit of a length first post but thanks for taking the time to read and I look forward to hear suggestions of where to start looking next as I know I still have a lot to learn.

Here are the logs:

http://ix.io/46XA

cheers

Ryzer

I found cubie-a5e-enable-usb3.dts  from radxa's git but could apply it.

Currently I am running 26.2.0-trunk.22.

I am looking for a forum where pcduino users can help each other.

Thank you,

Gaetano.

recently my Banana Pi Pro running Armbian 26.5.1 with Debian Trixie received a kernel update from 6.16.8 (which it has been running on for quite a while without issues) to 7.0.12. Since then, it randomly freezes shortly after booting, sometimes I also can see a kernel panic (see attached pictures).

Has anyone else run into this issue? What can I do to fix this? The old kernel no longer appears to be present in /boot, which makes it difficult to return to another kernel (trying to run something like apt-get typically quickly results in the aforementioned freeze).

I have been able to put together a patch that enables audio for H161/H618 devices.  So far only audio on HDMI works. Analog audio is still generating an error on startup.

The patches were taken from a git repository by warpme:

https://github.com/warpme/minimyth2/tree/master/script/kernel/linux-6.6/files

, and probably came from the Zunlong SDK. A lot of the code was written by Allwinner.

@pixdrift generated a version of the patches for Armbian and I continued to work on them.

I have a git repository if anyone would like to test, particularly on boards other than orangpizero3, on which I have tested.

repository:

https://github.com/stephengraf/armbian_build_sg.git

There is another repository mentioned in the Armbian Forum:

https://github.com/NickAlilovic/build

If anyone has interest and skills to debug the analog audio, the dmesg errors are:

[    7.125509]  ahub_dam-snd-soc-dummy-dai: substream ahub_dam-snd-soc-dummy-dai has no playback, no capture
[    7.125539] sunxi-snd-mach soc:ahub_dam_mach: ASoC: can't create pcm ahub_dam-snd-soc-dummy-dai :-22
[    7.125780] sunxi-snd-mach: probe of soc:ahub_dam_mach failed with error -22

Installing armbian-firmware_26.8.0-trunk.125_all.deb failed

With: data.tar lzma error....

Several months ago I got the same error but ignored it.

Now everything is almost working, I tried to find out what went wrong.

I can extract package with dpkg-deb -x on another system.

MD5sum is the same on A5E and other system.

This problem occurs on sdcard and nvme card.

Btw: it  is  the 4G version of the A5E.

Any idea how I can solve this?

Ron

 v26.2.1 for Orange Pi PC running Armbian Linux 6.12.58-current-sunxi
 

is a x86_64 binary:

$ ls -l /usr/bin/su
-rwsr-xr-x 1 root root 50800 Mar  6 13:10 /usr/bin/su

$ file /usr/bin/su
/usr/bin/su: setuid ELF 64-bit LSB executable, x86-64, version 1 (SYSV), statically linked, no section header
 

I installed the rust version, su-rs, but I thought it would be useful to warn about this. 

I checked /usr/bin and /usr/sbin and this is the only x86-64 executable.

Some may know me from previous Armbian adventures, primarily Orange Pi Zero 3... but I have jumped brands for a change of scenery (but not SoC).

When researching H61X based boards for the Zero 2 and Zero 3 development we were doing in another thread, I found the Sipeed LonganPi 3H, which is a relatively new board that took a while to find. My first impressions are that is really well made, and packs a lot in to the Raspberry Pi Zero style profile (although it also has a daughter board). It was shipped quickly in a nice quality hard plastic storage case and.. best of all.. it has two hardware buttons.. so I can reset! (very useful when you are rebooting endlessly).

You can find a review of the board here:

https://www.cnx-software.com/2023/12/29/sipeed-longan-pi3h-a-raspberry-pi-zero-sized-board-with-gigabit-ethernet-wifi-6-hdmi-and-usb-ports/

There has been some great development on GitHub here (and the documentation on their site is also good)
https://github.com/sipeed/LonganPi-3H-SDK

https://wiki.sipeed.com/hardware/en/longan/h618/lpi3h/1_intro.html

I basically started this thread as I thought I would look outside of the Orange Pi's I had and see if I could get the SDK build working in the Armbian framework. It should be noted that the SDK builds are standalone and use slightly dated uboot and kernel, but I was keen to at least get the builds working in Armbian so I can start iterating and improving.

I want it to be very clearly known that I am just migrating the great work from the above Sipeed GitHub repo (their scripts work really cleanly), and will slowly work through issues that I identify as I go. Currently I have migrated all the patches over (named the same as the original repo) until a clean/bootable build is achieved and then I will look at cleaning up the patch structure (although, in all honesty I prefer the numeric patch ordering to what exists currently in the sunxi patching directories.. but that's another discussion).

My preliminary porting work to the Armbian build framework can be found here and is configured to only support edge with a wip board configuration for the Longan Pi 3H.

https://github.com/pixdrift/armbian_build/tree/longanpi_3h

Status:

- The Armbian build completely cleanly for both the uboot (held back) and mainline kernel builds for 6.7.2 kernel.

- Of the patches from the SDK repository, roughly 10 don't currently apply (not as bad as it sounds)

- I have made some minor updates to two patches, and added comments for all problematic/failing patches

- Many of the patches are related to CPU Frequency scaling, and I expect these are failing because CPU frequency patches are already in Armbian (I will confirm in future)
- The build currently boots a separate boot partition, and that boot partition is using MBR (not GPT) as I had issues with the boot loader locating the GPT partition (haven't looked closely at this)

The good news is.. I have the board booting, with 6.7.2 and I get serial output for the boot. The bad news is, it immediately and abruptly decides that the GPU has hit a temperature threshold and shuts down the device (corrupting the FS in the process). On subsequent reboots, fsck is launched to repair the filesystem and GPU hits temperature threshold.

On investigation, I don't believe the GPU is actually hot, it's just the configuration has an issue and it's likely reporting a very high temperature value. I will try and confirm this as it may be a patch not applied correctly for GPU?

The following is the log from the serial output
 

First boot:
===========
U-Boot SPL 2024.01-rc2-armbian (Jan 24 2024 - 11:15:42 +0000)
DRAM: 4096 MiB
Trying to boot from MMC1
NOTICE:  BL31: v2.10.0  (debug):armbian
NOTICE:  BL31: Built : 10:42:19, Jan 24 2024
NOTICE:  BL31: Detected Allwinner H616 SoC (1823)
NOTICE:  BL31: Found U-Boot DTB at 0x4a083600, model: LonganPi 3H
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.


U-Boot 2024.01-rc2-armbian (Jan 24 2024 - 11:15:42 +0000) Allwinner Technology

CPU:   Allwinner H616 (SUN50I)
Model: LonganPi 3H
DRAM:  4 GiB
Core:  48 devices, 19 uclasses, devicetree: separate
WDT:   Not starting watchdog@30090a0
MMC:   mmc@4020000: 0, mmc@4022000: 1
Loading Environment from FAT... Unable to read "uboot.env" from mmc0:1...
In:    serial@5000000
Out:   serial@5000000
Err:   serial@5000000
Net:   eth0: ethernet@5020000
Unknown command 'usb' - try 'help'
Hit any key to stop autoboot:  0
switch to partitions #0, OK
mmc0 is current device
Scanning mmc 0:1...
Found U-Boot script /boot.scr
3259 bytes read in 1 ms (3.1 MiB/s)
## Executing script at 4fc00000
U-boot loaded from SD
Boot script loaded from mmc
129 bytes read in 1 ms (126 KiB/s)
30310 bytes read in 5 ms (5.8 MiB/s)
Working FDT set to 4fa00000
Failed to load '/dtb/allwinner/overlay/-fixup.scr'
18400262 bytes read in 762 ms (23 MiB/s)
23103496 bytes read in 957 ms (23 MiB/s)
Moving Image from 0x40080000 to 0x40200000, end=41880000
## Loading init Ramdisk from Legacy Image at 4ff00000 ...
   Image Name:   uInitrd
   Image Type:   AArch64 Linux RAMDisk Image (gzip compressed)
   Data Size:    18400198 Bytes = 17.5 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
## Flattened Device Tree blob at 4fa00000
   Booting using the fdt blob at 0x4fa00000
Working FDT set to 4fa00000
   Loading Ramdisk to 48e73000, end 49fff3c6 ... OK
   Loading Device Tree to 0000000048e03000, end 0000000048e72fff ... OK
Working FDT set to 48e03000

Starting kernel ...

done.
Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done.
Begin: Running /scripts/local-premount ... Scanning for Btrfs filesystems
done.
[    2.498172] thermal thermal_zone0: gpu-thermal: critical temperature reached, shutting down
[    2.506572] reboot: HARDWARE PROTECTION shutdown (Temperature too high)
[    2.519090] reboot: Power down

done.


Second boot:
============
Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done.
Begin: Running /scripts/local-premount ... Scanning for Btrfs filesystems
done.
[    2.475525] thermal thermal_zone0: gpu-thermal: critical temperature reached, shutting down
Begin: Will now [    2.484056] reboot: HARDWARE PROTECTION shutdown (Temperature too high)
check root file system ... fsck from util-linux [    2.495463] reboot: Power down
2.38.1

Next steps:
I am currently running on coffee fumes.. but when I my cognition returns, I plan to work through the remaining patches I have flagged as problematic in series.armbian in my branch. Potentially from there I will reach out to the Sipeed developers if I can't find anything obvious that is causing the above temperature issues . If that fails, I will look to hack up the image to disable the thermal protection code that is shutting the board down so I can boot and get more information about this issue (but this obviously risks the board being damaged).
 

Asking for assistance:

If you have any idea what might be causing the temp issue (ie. where to look) drop a message. I am sure I will get to it eventually when I have time, but assistance on where to focus my attention (which module/configuration components) would be a great help. That being said, I haven't looked at any of the currently failing patches so may be a quick fix!

If you have one of these boards (even if you aren't a developer) please sign up to the Armbian forums and let me know, it's always great to have other people available for testing

stable configuration for Orange Pi Zero 3 as a 24/7 SDR server.

The critical discovery: legacy kernel 6.6.75-sunxi64 is the only

stable option. The current kernel crashes within hours under SDR load.

Additional fixes:

- Blacklist aw859a WiFi driver (causes kernel instability)

- Blacklist DVB modules for RTL-SDR

- Lock libairspyhfSupport.so with chattr +i (SpyServer/SoapySDR conflict)

- Mask systemd-networkd-wait-online

- CPU governor: schedutil

- usbcore.autosuspend=-1 for USB SDR dongles

Running 3 SDRs simultaneously: RTL-SDR Blog V4, Airspy HF+, 

dedicated ADS-B. 4 antennas via HMC241 GPIO RF switch.

30+ decoders. Full Android control.

Complete guide: https://ozcet.github.io/sdr-server-guide

Right now, I’m wondering whether it would be feasible to use AI agents to help compile an Armbian image for the Orange Pi Zero 3W with a mainline kernel, while still keeping the old vendor U-Boot for compatibility. Has anyone here experimented with a similar approach or have any good suggestions or ideas?

I also really hope the official team can eventually provide a proper Armbian image for the Orange Pi Zero 3W, because I’ve run into quite a few issues with the stock official image.

MXQ-PRO H313

https://github.com/sicXnull/armbian-build/archive/refs/tags/mxqpro.zip

Summary: compile from source halts with error.

Traceback (most recent call last):
[🔨]     File "/home/e***o/Downloads/armbian-build-mxqpro/lib/tools/patching.py", line 491, in <module>
[🔨]       raise exit_with_exception
[🔨]   Exception: Failed to apply 2 patches.

Log uploaded and available at https://paste.armbian.com/dimokofipe

Thanks in advance

First I just remove "sv_SE.UTF-8, but then the Terminal complain it did not find sv_SE, so install again.

I generate the 2 locales, And thied to when I marked the local I want en_US, but it say sv_SE are active in Mate.

I tried to run:

sudo localectl set-locale en_US.UTF-8

Failed to issue method call: Access denied

I don't find any "Languish controll" at all in Mate desktop

It is right languish in terminal.

Cheers Joni

I wanted to make it run with overlayroot. So, I installed the package and added "extraargs=overlayroot=tmpfs" to armbianEnv.txt. After reboot nothing changed. In /run/initramfs/overlayroot.log
I found this:

builtin set cfgdisk='disabled'
[warning]: loaded 'overlay' module but no 'overlay' in /proc/filesystems
Unable to find driver/module. searched: overlay overlayfs
[failure]: Unable to find a driver. searched: overlay overlayfs

I looked into scripts/init-bottom/overlayroot inside the initrd, and figured out the problem: the script used grep, but grep was missing. So I added such script to /etc/initramfs-tools/hooks:

#!/bin/sh
set -e

PREREQS=""
case $1 in
        prereqs) exit 0;;
esac

. /usr/share/initramfs-tools/hook-functions

##
copy_exec /usr/bin/grep /bin

and applied it with "sudo update-initramfs -u". After reboot, I got kernel panic:

[    3.559598] Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000100

I didnt look deeper into the matter. I wonder, if it is a known problem and some solution exists already?

This is an MLIR-based lowering path from the TOSA v1 dialect to TIM-VX, VeriSilicon's OpenVX-based GPU/NPU ML Framework.

It includes the lowering from TOSA v1 to a custom timvx dialect (mirrors the TIM-VX C++ semantics) and a full lowering to C++ source.

It is currently on par in inference speed with the vendor ACUITY compiler pipeline while still giving you full control on the graph level.

In my own testing, on a Radxa Cubie A7Z \w Allwinner A733, ResNet-50 takes 8.0ms to inference, while the ACUITY-compiled baseline takes 7.3ms according to Radxa.

It all starts with Radxa/VeriSilicon's false advertisement of the NPU supporting MLIR, but turns out we just don't have it yet, so I made my own.

I have only tested the pipeline on the A733, but it should be able to be extended to any other VIP9000 variants as well.

  Want hdd because It write much data and USB 2 don't take mush more speed.

But I get a warning about a file-error or something so I run fsck on sda(hdd) was a systemdisk, but run read-only, but anyway it does not boot any more  

I think I can take the usb-hdd and run fsck from another computer? I have one system with Ubuntu on a Intel 6 gen, and Raspberry pi 500 and 5. The Pi-machine have raspberry-pi OS and the other Ubuntu 24.04.Does the machin or system have any singificans?

Or is there another fix to fix so the /boot can find sda?

But I get a warning about a file-error or something so I run fsck on sda(hdd) that was a systemdisk, but when I run I choose to do it read-only, but anyway it does not boot any more.  

I think I can take the usb-hdd and run fsck from another computer? I have one system with Ubuntu on a Intel 6 gen, and Raspberry pi 500 and 5. The Pi-machine have raspberry-pi OS and the other Ubuntu 24.04.Does the machine or system have any significans?

Or is there another fix to fix so the /boot on SD-card can find sda on USB?

/Cheers

/Edit. I posted under Orange Pi Zero2, but that was wrong place, and get moved, but at the same time get my thread classed as solved, but the solving was just to get the question on right place. I have also cleared my question a little bit and  I can not take away the other. 

cat /proc/asound/cards
 0 [Codec          ]: sun4i-codec - H616 Audio Codec
                      h616-audio-codec
 1 [HDMI           ]: HDMI - HDMI
                      HDMI
 2 [Device         ]: USB-Audio - USB PnP Sound Device
                      C-Media Electronics Inc. USB PnP Sound Device at usb-5200400.usb-1, full speed
 

I need an always USB sound card with the number of 0

I have a couple of H3 based boards (Orange Pi Zero and FriendlyArm NanoPi Duo 2). With all of them I have the same issue:
command like "reboot" turn the board off instead of rebooting.

The workaround is to add following line in /boot/armbianEnv.txt
 

extraargs=reboot=warm

Running latest image on all of the boards.

Installed Armbian (Ubuntu-noble) with XFCE desktop on an HDD(sda) from SD-card, so I need to have an SD-card in my orange pi zero 2w. I wonder if I can move /boot to an another smaller SD-card? Or do I also need an "mbr" or someting also there u-boot are?

/Cheers

If it is, how do I install U-Boot into the SPI? Is there one specifically for the a5e?

Are you able to power on the board using the GPIO pins? If so please could someone advise which pins to connect to?

I also aim to put a 5.5 x 2.1mm barrel connection on the box (with a latching press button switch for isolation) for the +5v supply and connect a short micro USB connector from the barrel socket to the board and also attach the SATA power leads directly rather than powering from the board 2 pin connector to take the load off the micro USB input.

Boot seems to start fine with all kernel files load confirmed by u-boot output (vmlinuz, ramdisk dtb, etc) but then it goes mute while starting the kernel

@TheSnowfield, you are listed as the pocketchip board maintainer (thanks a lot for your contribution! 🙏), any ideas of what am I missing? Do you have a suggestion for a working build? Thanks!

Serial UART output:

U-Boot SPL 2016.01-00115-g5f814bb (Dec 09 2016 - 23:00:24)
Fuel Gauge: 77%
Battery Voltage: 3776mV
DRAM: 512 MiB
CPU: 1008000000Hz, AXI/AHB/APB: 3/2/2
Trying to boot from NAND


U-Boot 2021.10-rc5+ (Oct 21 2021 - 14:43:51 -0500) Allwinner Technology

CPU:   Allwinner A13 (SUN5I)
Model: NextThing C.H.I.P.
I2C:   ready
DRAM:  sunxi SPL version mismatch: expected 3, got 1
512 MiB
NAND:  4096 MiB
Loading Environment from nowhere... OK
Setting up a 480x272 lcd console (overscan 0x0)
In:    serial
Out:   vidconsole
Err:   vidconsole
sunxi SPL version mismatch: expected 2, got 1
starting USB...
Bus usb@1c14000: USB EHCI 1.00
Bus usb@1c14400: USB OHCI 1.0
scanning bus usb@1c14000 for devices... 5 USB Device(s) found
scanning bus usb@1c14400 for devices... 1 USB Device(s) found
       scanning usb for storage devices... 1 Storage Device(s) found
Hit any key to stop autoboot:  0
DIP: PocketCHIP (0x1) from Next Thing Co. (0x9d011a)
Found 1 extension board(s).

Device 0: Vendor: Mass     Rev: 1.00 Prod: Storage Device
            Type: Removable Hard Disk
            Capacity: 14832.0 MB = 14.4 GB (30375936 x 512)
... is now current device
Scanning usb 0:1...
Found U-Boot script /boot/boot.scr
5475 bytes read in 4 ms (1.3 MiB/s)
## Executing script at 43100000
U-boot loaded from NAND
154 bytes read in 4 ms (37.1 KiB/s)
sun5i-r8-chip.dtb: No match
Load fdt: /boot/dtb/sun5i-r8-chip.dtb
14474151 bytes read in 780 ms (17.7 MiB/s)
10539688 bytes read in 557 ms (18 MiB/s)
Found mainline kernel configuration
25215 bytes read in 9 ms (2.7 MiB/s)
2146 bytes read in 7 ms (298.8 KiB/s)
Applying kernel provided DT fixup script (sun5i-a13-fixup.scr)
## Executing script at 45000000
Kernel image @ 0x42000000 [ 0x000000 - 0xa0d2a8 ]
## Loading init Ramdisk from Legacy Image at 43400000 ...
   Image Name:   uInitrd
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    14474087 Bytes = 13.8 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
## Flattened Device Tree blob at 43000000
   Booting using the fdt blob at 0x43000000
   Loading Ramdisk to 49232000, end 49fffb67 ... OK
   Loading Device Tree to 491c3000, end 49231fff ... OK

Starting kernel ...

Regards

Yesterday I upgraded my NanoPi Neo Plus2, during that the kernel version went from 6.12.74 (package version 26.2.0-trunk.478) to 6.18.19 (package version 26.2.0-trunk.626). This morning I noticed, that this kernel is missing the dm-snapshot.ko module. I searched the forum if anyone else is having this problem, but it appears I am the only one using this feature. I use snapshots to create consistent backups of the system.

Is there a reason why it was removed and more importantly is there a way to get it back without having to compile the kernel myself?

Greetings

PS: I should note, that I want the module back in newer kernel versions in the future. For now I downgraded to some older version that I was able to find a package for and got it working through that.

It worked on the older kernel, but now it doesn't 😞....

Supposedly this is the cause, but is it really?

Quote

DTB (device tree) does not configure GPIO reset/power for the UWE5622.

hci_uart cannot initialize the controller → hci0 is not created.

The overlay for BT in mainline 6.x does not yet exist in Trixie.

❌ Result: hciconfig -a and bluetoothctl list show nothing.

armbianmonitor -u

https://paste.armbian.com/uzudezufit

https://www.aliexpress.us/item/3256803856059047.html

I have read somewhere, that I can use an ili9341 spi driver, only by changing the resolution and changing the initialization script.

I looked in the waveshare website and github, they don't have anything for the ili9488

Then, I found some arduino code in http://www.lcdwiki.com/3.5inch_SPI_Module_ILI9488_SKU%3AMSP3520

(look for the "3.5 inch SPI Module Package(ILI9488)" link, then find the LCDWIKI_SPI.cpp

The initialization sequence is in line 1697:

				0xF7, 4, 0xA9, 0x51, 0x2C, 0x82,
				0xC0, 2, 0x11, 0x09,
				0xC1, 1, 0x41,
				0xC5, 3, 0x00, 0x0A, 0x80,
				0xB1, 2, 0xB0, 0x11,
				0xB4, 1, 0x02,
				0xB6, 2, 0x02, 0x22,
				0xB7, 1, 0xC6,
				0xBE, 2, 0x00, 0x04,
				0xE9, 1, 0x00,
				0x36, 1, 0x08,
				0xE0, 15, 0x00, 0x07, 0x10, 0x09, 0x17, 0x0B, 0x41, 0x89, 0x4B, 0x0A, 0x0C, 0x0E, 0x18, 0x1B, 0x0F,
				0xE1, 15, 0x00, 0x17, 0x1A, 0x04, 0x0E, 0x06, 0x2F, 0x45, 0x43, 0x02, 0x0A, 0x09, 0x32, 0x36, 0x0F,
				0x11, 0,
				TFTLCD_DELAY8, 120,
				0x29, 0

I am currently trying to convert it to a DTS-format init string, so that it fits my ili9341-fb.dts, which I made earlier this year:

/*
OrangePi Zero 3 -> ILI9341 LCD connections
SPI CLOCK = PH6
SPI DO (LCD MISO) = PH8 (OPIZ MISO)
SPI DI (LCD MOSI) = PH7 (OPIZ MOSI)
LCD DATA/CONTROL = PC7 *
LCD RESET = PC14 * could be any GPIO pin I want
CHIP SELECT = PH9
VCC = 3.3V PIN 17
GND = GND PIN 20
*/

/dts-v1/;
/plugin/;
/{
    compatible = "allwinner,sun50i-h616"; /*what is the H618*/
	fragment@0 {
	    target = <&pio>;
	    __overlay__{
	        display_pins: display_pins {
                    pins = "PC7", "PC14"; /* reset, DC pins, order does not matter*/
                    function = "gpio_out", "gpio_out";
                };
            };
	};
	fragment@1 {
        target = <&spi1>;
        __overlay__ {
            /* needed to avoid dtc warning */
            #address-cells = <1>;
            #size-cells = <0>;
            status="okay";
            pinctrl-names = "default";
            pinctrl-0 = <&spi1_pins>; /* Mux the PI to make sure they are set in spi Mode */
            cs-gpios = <&pio 7 9 0>;  /* PH9 chip select, H=7 */
            num-chipselects = <1>;
            display: display@0 {
                /*compatible = "adafruit,yx240qv29","ilitek,ili9341";*/
                compatible = "ilitek,ili9341";
                reg = <0>;
                pinctrl-names = "default";
                pinctrl-1 = <&display_pins>;
                spi-max-frequency = <40000000>;
                rotate = <270>; /* rotate for ili9341, rotation for yx240qv29 */
                bgr=<0>;
                fps = <15>;
                buswidth = <8>;
                height = <640>;
                width = <320>;
                reset-gpios = <&pio 2 14 1>; /* PC14 reset pin*/
                dc-gpios = <&pio 2 7 0>; /* PC7 Data control pin */
                debug = <3>;
                init = <0x10000b0 0x00
                        0x1000011
			0x20000ff
			0x100003a 0x55
			0x1000036 0x28
			0x10000c2 0x44
			0x10000c5 0x00 0x00 0x00 0x00
			0x10000e0 0x0f 0x1f 0x1c 0x0c 0x0f 0x08 0x48 0x98 0x37 0x0a 0x13 0x04 0x11 0x0d 0x00
			0x10000e1 0x0f 0x32 0x2e 0x0b 0x0d 0x05 0x47 0x75 0x37 0x06 0x10 0x03 0x24 0x20 0x00
			0x10000e2 0x0f 0x32 0x2e 0x0b 0x0d 0x05 0x47 0x75 0x37 0x06 0x10 0x03 0x24 0x20 0x00
			0x1000036 0x28
			0x1000011
			0x1000029>;
            };
        };
    };


    __overrides__ {
        rotate =  <&display>,"rotate:0";
        fps =     <&display>,"fps:0";
        debug =   <&display>,"debug:0";
    };
};

I am unsure how to start the init line, can someone help me?

Then, when I have that init string confirmed, I can use:

https://github.com/notro/panel-mipi-dbi/wiki

https://blog.csdn.net/CNflysky/article/details/125171176

To switch to the mipi-dbi driver, which would get me DRM (instead of FB)

i tried "Armbian_community_26.2.0-trunk.606_Radxa-cubie-a5e_trixie_edge_6.19.8_minimal.img"  and wlan didn't work, i think the device tree is broken Radxa-cubie-a5e kernel 6.19.x

as a quick fix, I copy the kernel 6.18.x "sun55i-a527-cubie-a5e.dtb" file to the /boot/dtb/allwinner directory to get wlan working.

[FAILED] Failed to start Apply Kernel Variables.
[FAILED] Failed to start Dispatcher daemon for systemd-networkd.
[FAILED] Failed to start Helper to synchronize boot up for ifupdown.
[DEPEND] Dependency failed for Raise network interfaces.

The system continues booting, but these errors appear every time.
Hardware:
Board: Orange Pi 3 LTS
Image: Armbian 26.2.1 Minimal / IoT
Storage: TF card
Questions:
Are these errors expected on this board?
Is there a configuration issue with network initialization?
Is this image fully supported for Orange Pi 3 LTS?
Thank you.

i could control the OTG micro USB port power on my NanoPi Neo (H3) by exporting and writing to GPIO 354 (line 2 of GPIO chip with base 352)

I'm using Kernel V6.6.62 and I created a tiny device tree overlay defining. Excerpt below:

usb@1c19000 { dr_mode = "host" }
usb0-vbus { status = "okay" }

This works fine!

For test purposes, I switched to a NanoPi Neo2 (H5) with Kernel 6.6.62 (64 bit). Here, the OTG port is powered on and is usable by default without any overlay.

But the on/off control does not work anymore. All attempts to export GPIO 354 give "write error: Device or resource busy".

Schematics show no circuit difference in controlling the OTG power. In both cases its the same pin name on H3 and H5.

The new GPIO handling of newer kernels cannot be the reason, as I use the same kernel versions on H3 and H5 (beside bit width).

Any idea whats wrong and how I can again switch on/off OTG power?

I would like to know if i can connect to my orange pi zero 3

I have already tried to connect but without success, as I am new to this I would like you to help me if possible. 

Thanks!

Sorry for my English I'm on google.

Armbian boot (26.2.0 trunk 385):

U-Boot SPL 2026.01_armbian-2026.01-S127a-P96c6-H560c-Va7f1-B2eb2-R448a (Feb 03 2026 - 12:13:55 +0000)
DRAM: 2048 MiB
Trying to boot from MMC1
NOTICE:  BL31: v2.13.0(debug):armbian
NOTICE:  BL31: Built : 12:13:32, Feb  3 2026
NOTICE:  BL31: Detected Allwinner A523 SoC (1890)
NOTICE:  BL31: Found U-Boot DTB at 0xa0c06a8, model: Radxa Cubie A5E
INFO:    Configuring SPC Controller
INFO:    BL31: Platform setup done
INFO:    GICv3 without legacy support detected.
INFO:    ARM GICv3 driver initialized in EL3
INFO:    Maximum SPI INTID supported: 287
INFO:    BL31: Initializing runtime services
INFO:    BL31: cortex_a55: CPU workaround for erratum 1530923 was applied
INFO:    PSCI: Suspend is unavailable
INFO:    BL31: Preparing for EL3 exit to normal world
INFO:    Entry point address = 0x4a000000
INFO:    SPSR = 0x3c9
ns16550_serial serial@2500000: pinctrl_select_state_full: uclass_get_device_by_phandle_id: err=-19


U-Boot 2026.01_armbian-2026.01-S127a-P96c6-H560c-Va7f1-B2eb2-R448a (Feb 03 2026 - 12:13:55 +0000) Allwinner Technology

CPU:   Allwinner A523 (SUN55I)
Model: Radxa Cubie A5E
DRAM:  2 GiB
sunxi_set_gate: (CLK#35) unhandled
Core:  88 devices, 25 uclasses, devicetree: separate
WDT:   Not starting watchdog@2050000
MMC:   mmc@4020000: 0
Loading Environment from FAT... Unable to read "uboot.env" from mmc0:1... 
In:    serial@2500000
Out:   serial@2500000
Err:   serial@2500000
Net:   eth0: ethernet@4500000
starting USB...
sun4i_usb_phy phy@4100400: External vbus detected, not enabling our own vbus
USB EHCI 1.00
USB OHCI 1.0
USB EHCI 1.00
USB OHCI 1.0
Bus usb@4101000: 1 USB Device(s) found
Bus usb@4101400: 1 USB Device(s) found
Bus usb@4200000: 1 USB Device(s) found
Bus usb@4200400: 1 USB Device(s) found
       scanning usb for storage devices... 0 Storage Device(s) found
Hit any key to stop autoboot: 0
PCIe: Acquiring resources...
PCIe: All resources acquired. Starting power-on sequence...
PCIe: Toggling external device reset (PERST#)...
PCIe: Hardware power-on sequence successful.
PCIe: Disabling DBI write protection...
PCIe: DBI  region: 0x04800000-0x04c80000
PCIe: IO   region: 0x21000000-0x22000000
PCIe: MEM  region: 0x22000000-0x30000000
PCIe: CFG  region: 0x20000000-0x21000000
PCIe: Lanes: 1, Max Speed: Gen2
  Link Status: 0x00000004
  RDLH_LINK_UP: 0
  SMLH_LINK_UP: 0
  LINK_SPEED: 0
  LINK_WIDTH: 0
  Link Status: 0x00000004
  RDLH_LINK_UP: 0
  SMLH_LINK_UP: 0
  LINK_SPEED: 0
  LINK_WIDTH: 0
  Link Status: 0x00000017
  RDLH_LINK_UP: 1
  SMLH_LINK_UP: 1
  LINK_SPEED: 0
  LINK_WIDTH: 0
pcie link up success
PCIe: Link active at Gen2

Device 0: Vendor: 0x1e0f Rev: 10410105 Prod: X06PD8L0QUM1        
            Type: Hard Disk
            Capacity: 244198.3 MB = 238.4 GB (500118192 x 512)
... is now current device
Scanning nvme 0:1...
Found U-Boot script /boot.scr
4641 bytes read in 0 ms
## Executing script at 4fc00000
U-boot loaded from SD
Boot script loaded from nvme
263 bytes read in 0 ms
Load fdt: /dtb/allwinner/sun55i-a527-cubie-a5e.dtb
37110 bytes read in 1 ms (35.4 MiB/s)
Working FDT set to 4fa00000
Failed to load '/dtb/allwinner/overlay/sun55i-a527-fixup.scr'
16552556 bytes read in 55 ms (287 MiB/s)
39950848 bytes read in 102 ms (373.5 MiB/s)
Moving Image from 0x40080000 to 0x40200000, end=0x42900000
## Loading init Ramdisk from Legacy Image at 4ff00000 ...
   Image Name:   uInitrd
   Image Type:   AArch64 Linux RAMDisk Image (gzip compressed)
   Data Size:    16552492 Bytes = 15.8 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
## Flattened Device Tree blob at 4fa00000
   Booting using the fdt blob at 0x4fa00000
Working FDT set to 4fa00000
   Loading Ramdisk to 49036000, end 49fff22c ... OK
   Loading Device Tree to 0000000048fc4000, end 0000000049035fff ... OK
Working FDT set to 48fc4000

Starting kernel ...


Armbian_community 26.2.0-trunk.385 Trixie ttyS0 

radxa-cubie-a5e login: 

Radxa Bookworm Boot:
 

[207]HELLO! BOOT0 is starting!
[210]BOOT0 commit : 33d8db429a-dirty

[214]periph0 has been enabled
[218]set pll end
[219]PL gpio voltage : 3.3V 
[224]PMU: AXP2202
[229]PMU: AXP1530
[234]power mode:33, sys_vol:920
[239]vaild para:1  select dram para0
[242]dram_para[0]:0x4b0
[245]dram_para[1]:0x8
[247]dram_para[2]:0x7070707
[250]dram_para[3]:0xd0d0d0d
[253]dram_para[4]:0xe0e
[256]dram_para[5]:0x84848484
[259]dram_para[6]:0x310a
[262]dram_para[7]:0x10001000
[265]dram_para[8]:0x0
[267]dram_para[9]:0x34
[270]dram_para[10]:0x1b
[272]dram_para[11]:0x33
[275]dram_para[12]:0x3
[277]dram_para[13]:0x0
[280]dram_para[14]:0x0
[282]dram_para[15]:0x4
[285]dram_para[16]:0x72
[287]dram_para[17]:0x0
[290]dram_para[18]:0xe
[292]dram_para[19]:0x0
[295]dram_para[20]:0x0
[297]dram_para[21]:0x26
[300]dram_para[22]:0x80808080
[303]dram_para[23]:0x6060606
[306]dram_para[24]:0x1f0b0503
[309]dram_para[25]:0x0
[312]dram_para[26]:0x3a000000
[315]dram_para[27]:0x802f3333
[318]dram_para[28]:0xc0c0bbbf
[321]dram_para[29]:0x35352f31
[325]dram_para[30]:0xc64
[327]dram_para[31]:0x48484848
[331]board init ok
[353]enable_jtag
[355]card no is 0
[357]sdcard 0 line count 4
[360][mmc]: mmc driver ver 2023-03-24 16:23
[370][mmc]: Wrong media type 0x0
[374][mmc]: ***Try SD card 0***
[395][mmc]: HSSDR52/SDR25 4 bit
[398][mmc]: 50000000 Hz
[401][mmc]: 60906 MB
[403][mmc]: ***SD/MMC 0 init OK!!!***
[414]DRAM BOOT DRIVE INFO: V0.67
[419]DRAM_VCC set to 1100 mv
[545]DRAM retraining ten 
[671]DRAM retraining ten 
[689][AUTO DEBUG]32bit,1 ranks training success!
[718]Soft Training Version: T2.0
[7773][SOFT TRAINING] CLK=1200M Stable memtest pass
[7778]DRAM CLK =1200 MHZ
[7781]DRAM Type =8 (3:DDR3,4:DDR4,7:LPDDR3,8:LPDDR4)
[7792]phy_dfs_clk1 = 800M
[8078]phy_dfs_clk2 = 400M
[8169]phy_dfs_clk3 = 150M
[8290]phy_dfs_clk0 = 1200M
[8293]DRAM MDFS VERSION INFO: V0.660
[8298]DRAM MDFS time =38892 ns
[8301]DRAM SIZE =2048 MBytes, para1 = 310a, para2 = 8000000, tpr13 = 6465
[8329]DRAM simple test OK.
[8332]dram size =2048
[8339]nsi init 2023-2-23
[8343]error:bad magic.
[8463]Loading boot-pkg Succeed(index=1).
[8467]Entry_name        = u-boot
[8476]Entry_name        = monitor
[8480]Entry_name        = scp
[8484]Entry_name        = dtb
[8487]mmc not para
[8489]Jump to second Boot.
NOTICE:  BL31: OP-TEE 32bit detected
NOTICE:  BL31: U-BOOT 32bit detected
NOTICE:  BL31: v2.5(debug):a6e1826c1
NOTICE:  BL31: Built : 10:10:43, Mar 28 2025
NOTICE:  BL31: No DTB found.
nsi init ok 2022-11-08
ERROR:   Error initializing runtime service opteed_fast


U-Boot 2018.07-11-boot-aw2501-g4f803d1684e-dirty (Dec 05 2025 - 10:08:58 +0000) Allwinner Technology

[08.641]CPU:   Allwinner Family
[08.644]Model: Radxa Cubie A5E
I2C:   ready
[08.655]DRAM:  2 GiB
[08.659]Relocation Offset is: 75e60000
[08.721]secure enable bit: 0
[08.725]PMU: AXP2202
[08.753][AXP2202] comm status : 0x0 = 0x20, 0x1 = 0x90
[08.758][AXP2202] onoff status: 0x20 = 0x4, 0x21 = 0x0
[08.763][AXP2202] reboot/charge status: 0xf0 = 0x0
[08.768]PMU: AXP1530
[08.771]CPU=1008 MHz,PLL6=600 Mhz,AHB=200 Mhz, APB1=100Mhz  MBus=600Mhz
[08.777]gic: sec monitor mode
SPI ALL:   ready
[08.782]flash init start
[08.785]workmode = 0,storage type = 1
[08.788][mmc]: mmc driver ver uboot2018:2024-10-18 9:01:00 -- uboot2018:2025-03-28 10:03:00
[08.796][mmc]: get sdc_type fail and use default host:tm1.
[08.802][mmc]: can't find node "mmc0",will add new node
[08.807][mmc]: fdt err returned <no error>
[08.811][mmc]: Using default timing para
[08.814][mmc]: SUNXI SDMMC Controller Version:0x50500
[08.843][mmc]: card_caps:0x3000000a
[08.846][mmc]: host_caps:0x3000003f
[08.851]sunxi flash init ok
get value error
[08.860]Loading Environment from SUNXI_FLASH... OK
[08.867]No ethernet found.
[08.877]Fail to get de's irq!
[08.915]NOT support bridge yet
[08.918]Warn: no find panel or bridge
[08.921]hdmi@5520000 disconnected
[08.924]drm hdmi get mode: 1920x1080@60Hz
hdmi@5520000: use force output detailed mode clock 148500 kHz, flags[5]
    H: 1920 2008 2052 2200
    V: 1080 1084 1089 1125
bus_format: 0
[09.134]the secure storage item0 copy0 magic is bad
[09.148]the secure storage item0 copy1 magic is bad
[09.152]usb burn from boot
delay time 0
weak:otg_phy_config
[09.163]usb prepare ok
[09.466]overtime
[09.471]do_burn_from_boot usb : no usb exist
cann't get the boot_base from the env
[09.494]update part info
[09.498]update bootcmd
pcie link up success
PCIe speed of Gen2
[09.908]change working_fdt 0xbbe0fe18 to 0xbbddfe18
get value error
[09.914][mmc]: get sunxi-mmc0 string failed
[09.918]The storage not support sample function
[09.924]## error: update_fdt_dram_para_from_bootpara : FDT_ERR_NOTFOUND
ret 0
[09.935]chip id : 0x0000ff10 0x00004824 0x0000d710 0x00001d96
[09.940]chip id : 0x0000ff10 0x00004824 0x0000d710 0x00001d96
[09.946]Could not find nodeoffset for used ext pmu:reg-axp1530
[09.951]update dts
curr_device:0
Device: SUNXI SD/MMC
Manufacturer ID: 3
OEM: 5344
Name: SR64G 
Bus Speed: 50000000
Mode : SD High Speed (50MHz)
Rd Block Len: 512
SD version 3.0
High Capacity: Yes
Capacity: 59.5 GiB
Bus Width: 4-bit
Erase Group Size: 512 Bytes
Hit any key to stop autoboot:  0 
starting USB...
USB0:   start sunxi  USB-DRD...
config usb clk ok
sunxi USB-DRD init ok...
USB EHCI 1.00
scanning bus 0 for devices... 1 USB Device(s) found
USB1:   start sunxi  USB1-Host...
config usb clk ok
sunxi USB1-Host init ok...
USB EHCI 1.00
scanning bus 1 for devices... 1 USB Device(s) found
       scanning usb for storage devices... 0 Storage Device(s) found

Device 0: device type unknown
... is now current device
** Bad device usb 0 **
** Bad device usb 0 **
mmc0 is current device
Scanning mmc 0:2...
Scanning mmc 0:3...
Found /boot/extlinux/extlinux.conf
Retrieving file: /boot/extlinux/extlinux.conf
ERROR: reserving fdt memory region failed (addr=bbed0000 size=7e9000)
1323 bytes read in 7 ms (184.6 KiB/s)
U-Boot menu
1:      Debian GNU/Linux 11 (bullseye) 5.15.147-13-aw2501
2:      Debian GNU/Linux 11 (bullseye) 5.15.147-13-aw2501 (rescue target)
Enter choice: 1:        Debian GNU/Linux 11 (bullseye) 5.15.147-13-aw2501
Retrieving file: /boot/initrd.img-5.15.147-13-aw2501
ERROR: reserving fdt memory region failed (addr=bbed0000 size=7e9000)
7060674 bytes read in 300 ms (22.4 MiB/s)
Retrieving file: /boot/vmlinuz-5.15.147-13-aw2501
ERROR: reserving fdt memory region failed (addr=bbed0000 size=7e9000)
20992512 bytes read in 877 ms (22.8 MiB/s)
append: root=UUID=9645203c-b680-44b6-8b18-068d9e110402 console=ttyAS0,115200n8 rootwait clk_ignore_unused mac_addr=08:ef:6c:c7:8b:ad mac1_addr=08:ef:6c:c7:8b:ac quiet splash loglevel=4 rw earlycon consoleblank=0 console=tty1 coherent_pool=2M irqchip.gicv3_pseudo_nmi=0 cgroup_enable=cpuset cgroup_memory=1 cgroup_enable=memory swapaccount=1 kasan=off
Retrieving file: /usr/lib/linux-image-5.15.147-13-aw2501/allwinner/sun55i-a527-cubie-a5e.dtb
ERROR: reserving fdt memory region failed (addr=bbed0000 size=7e9000)
161015 bytes read in 18 ms (8.5 MiB/s)
get value error
[16.446]The storage not support sample function
ret 0
[16.563]update dts
stop sunxi USB-DRD ok...
stop sunxi USB1-Host ok...
   Loading Ramdisk to 49944000, end 49fffcc2 ... OK
ERROR: reserving fdt memory region failed (addr=bbed0000 size=7e9000)
[16.598]Starting kernel ...

[16.601]total: 16601 ms

[16.603][mmc]: MMC Device 2 not found
[16.606][mmc]: mmc 2 not find, so not exit
NOTICE:  [SCP] :wait arisc ready....
NOTICE:  [SCP] :arisc version: [364dad9bcd34230512f015ab5c6cefa12bd238d0]
NOTICE:  [SCP] :arisc startup ready
NOTICE:  [SCP] :arisc startup notify message feedback
NOTICE:  [SCP] :sunxi-arisc driver is starting
NOTICE:  BL3-1: Next image address = 0x40200000
NOTICE:  BL3-1: Next image spsr = 0x3c5
[    0.071969] AW BSP version: caee29fcb3, 2025-12-09 07:23:49, RadxaOS SDK
[    0.140107] sunxi:twi_sunxi-2502000.twi0:[ERR]: pinctrl_get failed
[    0.140127] sunxi:twi_sunxi-2502000.twi0:[ERR]: TWI failed to get resource
[    0.143734] sunxi:axp2101-6-0036:[ERR]: Unable to match OF ID
[    0.310164] sunxi:ccu_ddr:[ERR]: dram_clk:1200
[    0.310191] sunxi:ccu_ddr:[ERR]: dram_div:0x1f0b0503
[    0.310832] sunxi:pin-2000000.pinctrl:[ERR]: unknown pin 
[    0.310842] sunxi:pin-2000000.pinctrl:[ERR]: unknown pin 
[    0.310886] sunxi:pin-2000000.pinctrl:[ERR]: unknown pin 
[    0.310892] sunxi:pin-2000000.pinctrl:[ERR]: unknown pin 
[    0.311482] sunxi:sunxi_uart-uart0:[ERR]: uart0 error to get fifo size property
[    0.386566] NSI_PMU 2020000.nsi-controller: no topo process for clk path type:0
[    0.394816] no topo process for topo type:0
[    0.402846] sunxi:sunxi_mmc_host-4022000.sdmmc:[ERR]: Could not get mbus clock
[    0.411011] sunxi:sunxi_mmc_host-4022000.sdmmc:[ERR]: Could not get store clock
[    0.419251] sunxi:sunxi_mmc_host-4022000.sdmmc:[ERR]: Could not get msi_lite clock
[    0.457791] sunxi:sunxi_mmc_host-4020000.sdmmc:[ERR]: Could not get mbus clock
[    0.466069] sunxi:sunxi_mmc_host-4020000.sdmmc:[ERR]: Could not get store clock
[    0.474428] sunxi:sunxi_mmc_host-4020000.sdmmc:[ERR]: Could not get msi_lite clock
[    0.475236] sunxi:sunxi_mmc_host-4022000.sdmmc:[ERR]: smc 1 p2 err, cmd 1, RTO !!
[    0.492239] sunxi:sunxi_mmc_host-4022000.sdmmc:[ERR]: smc 1 p2 err, cmd 1, RTO !!
[    0.501531] sunxi:sunxi_mmc_host-4022000.sdmmc:[ERR]: smc 1 p2 err, cmd 1, RTO !!
[    0.510880] sunxi:sunxi_mmc_host-4022000.sdmmc:[ERR]: smc 1 p2 err, cmd 1, RTO !!
[    0.520159] sunxi:sunxi_mmc_host-4022000.sdmmc:[ERR]: smc 1 p2 err, cmd 1, RTO !!
[    0.529448] sunxi:sunxi_mmc_host-4022000.sdmmc:[ERR]: smc 1 p2 err, cmd 1, RTO !!
[    0.538076] sunxi:sunxi_mmc_host-4021000.sdmmc:[ERR]: Could not get mbus clock
[    0.538726] sunxi:sunxi_mmc_host-4022000.sdmmc:[ERR]: smc 1 p2 err, cmd 1, RTO !!
[    0.546202] sunxi:sunxi_mmc_host-4021000.sdmmc:[ERR]: Could not get store clock
[    0.562758] sunxi:sunxi_mmc_host-4021000.sdmmc:[ERR]: Could not get msi_lite clock
[    0.572128] sunxi:sunxi_mmc_host-4022000.sdmmc:[ERR]: smc 1 p2 err, cmd 1, RTO !!
[    0.581414] sunxi:sunxi_mmc_host-4022000.sdmmc:[ERR]: smc 1 p2 err, cmd 1, RTO !!
[    0.590691] sunxi:sunxi_mmc_host-4022000.sdmmc:[ERR]: smc 1 p2 err, cmd 1, RTO !!
[    0.600035] sunxi:sunxi_mmc_host-4022000.sdmmc:[ERR]: smc 1 p2 err, cmd 1, RTO !!
[    0.609310] sunxi:sunxi_mmc_host-4022000.sdmmc:[ERR]: smc 1 p2 err, cmd 1, RTO !!
[    0.617707] sunxi:sunxi_mmc_host-4021000.sdmmc:[ERR]: smc 2 p1 err, cmd 52, RTO !!
[    0.627037] sunxi:sunxi_mmc_host-4021000.sdmmc:[ERR]: smc 2 p1 err, cmd 52, RTO !!
[    0.635533] sunxi:sunxi_mmc_host-4022000.sdmmc:[ERR]: smc 1 p2 err, cmd 1, RTO !!
[    0.644823] sunxi:sunxi_mmc_host-4022000.sdmmc:[ERR]: smc 1 p2 err, cmd 1, RTO !!
[    0.654111] sunxi:sunxi_mmc_host-4022000.sdmmc:[ERR]: smc 1 p2 err, cmd 1, RTO !!
[    0.663385] sunxi:sunxi_mmc_host-4022000.sdmmc:[ERR]: smc 1 p2 err, cmd 1, RTO !!
[    0.672711] sunxi:sunxi_mmc_host-4022000.sdmmc:[ERR]: smc 1 p2 err, cmd 1, RTO !!
[    0.682003] sunxi:sunxi_mmc_host-4022000.sdmmc:[ERR]: smc 1 p2 err, cmd 1, RTO !!
[    0.691285] sunxi:sunxi_mmc_host-4022000.sdmmc:[ERR]: smc 1 p2 err, cmd 1, RTO !!
[    0.700598] sunxi:sunxi_mmc_host-4022000.sdmmc:[ERR]: smc 1 p2 err, cmd 1, RTO !!
[    0.709898] sunxi:sunxi_mmc_host-4022000.sdmmc:[ERR]: smc 1 p2 err, cmd 1, RTO !!
[    0.719191] sunxi:sunxi_mmc_host-4022000.sdmmc:[ERR]: smc 1 p2 err, cmd 1, RTO !!
[    0.727648] sunxi:sunxi_mmc_host-4022000.sdmmc:[ERR]: retry:set phase failed or over retry times
[    0.737523] sunxi:sunxi_mmc_host-4022000.sdmmc:[ERR]: retry:give up
[    0.744833] sunxi:sunxi_mmc_host-4020000.sdmmc:[ERR]: sdc0 :the host don't support tuning in kernel
[    1.235336] sunxi:sunxi_sidefuse init success!
[    1.241281] inno-combphy 4f00000.phy: get select3v3-supply fail
[    1.740355] sunxi-rc-recv 2005000.irrx: sunxi_irrx_resource_get: get ir protocol failed
[    1.771768] sunxi:axp2202_battery:[ERR]: axp2202-battery device is not configed
[    1.794813] sunxi-rfkill soc@3000000:rfkill: get gpio chip_en failed
[    1.804693] [NAND][NE] Not found valid nand node on dts
[    3.128108] cma: cma_alloc: reserved: alloc failed, req-size: 512 pages, ret: -12
[    4.777883] sunxi:VE:[ERR]: 409 map_max_ve_freq_by_vf_sun55iw3(): can not match dvfs[0x1] and vol[900 mv], use default ve_freq
[    4.815646] cma: cma_alloc: reserved: alloc failed, req-size: 512 pages, ret: -12
[    4.827791] sunxipart: failed to parse sunxi_gpt!
[    5.002596] sunxi:sound-mach:[ERR]: 535 simple_parse_of(): simple_dai_link_of failed
[    5.046546] sunxi:sound-codec-hdmi:[ERR]: 442 sunxi_codec_dev_probe(): register codec-hdmi success
[    5.064198] sunxi:sound-mach:[ERR]: 535 simple_parse_of(): simple_dai_link_of failed
[    5.084859] debugfs: Directory '7114000.i2s2_plat' with parent 'sndhdmi' already present!
[    5.094216] sunxi:sunxi_mmc_host-4021000.sdmmc:[ERR]: smc 2 p1 err, cmd 52, RTO !!
[    5.105028] sunxi:sunxi_mmc_host-4021000.sdmmc:[ERR]: smc 2 p1 err, cmd 52, RTO !!
[    5.175761] axp2202-bldo1: Restricting voltage, 3300000-1800000uV
[    5.182730] sunxi-rfkill soc@3000000:rfkill: wlan power[0] (axp2202-bldo1) set voltage failed
[    5.192433] sunxi-rfkill soc@3000000:rfkill: set power failed
[    5.250133] sunxi:sunxi_mmc_host-4021000.sdmmc:[ERR]: smc 2 p1 err, cmd 7, RTO !!
[    5.258714] sunxi:sunxi_mmc_host-4021000.sdmmc:[ERR]: smc 2 p1 err, cmd 7, RTO !!
[    5.267263] sunxi:sunxi_mmc_host-4021000.sdmmc:[ERR]: smc 2 p1 err, cmd 7, RTO !!
[    5.275819] sunxi:sunxi_mmc_host-4021000.sdmmc:[ERR]: smc 2 p1 err, cmd 7, RTO !!
[    5.310636] sunxi:sunxi_mmc_host-4021000.sdmmc:[ERR]: smc 2 p1 err, cmd 52, RTO !!
[    5.320383] sunxi:sunxi_mmc_host-4021000.sdmmc:[ERR]: smc 2 p1 err, cmd 52, RTO !!
[    5.625825] aicbsp: sdio_err:<aicwf_sdio_bus_pwrctl,1404>: bus down
[    6.762994] ieee80211 phy0: 
[    6.762994] *******************************************************
[    6.762994] ** CAUTION: USING PERMISSIVE CUSTOM REGULATORY RULES **
[    6.762994] *******************************************************

Debian GNU/Linux 11 radxa-cubie-a5e ttyAS0

radxa-cubie-a5e login: 

[   11.048517] unisoc_wifi wlan0: mixed HW and IP checksum settings.
[259241.515808] unisoc_wifi wlan0: sprdwl_report_connection Asus failed status code:30!
[345665.483530] unisoc_wifi wlan0: sprdwl_report_connection sm_state (5), status: (2)!
[345665.483567] unisoc_wifi wlan0: sprdwl_report_connection Asus failed status code:1!

NetworkManager also reports:

link timed out.
Activation failed for connection 'Asus'

After the crash, restarting NetworkManager doesn’t resolve the issue. Trying modprobe -r unisoc_wifi fails, saying the module is not found. The only way to fix it is to reboot the system.

My USB WiFi dongle works fine without these issues, so it seems specific to the onboard WiFi.

Has anyone else experienced this or found a solution for this driver?

I'm getting to the point I'm going to write a cron job when the network drops to reboot the machine 🙃

my dts file:

35Lcd.dts

U-Boot SPL 2024.07 (Feb 25 2026 - 15:51:42 +0300)
DRAM: 512 MiB
Trying to boot from MMC1
CMD_SEND:0
               ARG                      0x00000000
               MMC_RSP_NONE
CMD_SEND:8
               ARG                      0x000001aa
               RET                      -110
CMD_SEND:55
               ARG                      0x00000000
               RET                      -110
CMD_SEND:0
               ARG                      0x00000000
               MMC_RSP_NONE
CMD_SEND:1
               ARG                      0x00000000
               RET                      -110
Card did not respond to voltage select! : -110
spl: mmc init failed with error: -95
SPL: failed to boot from all boot devices
### ERROR ### Please RESET the board ###

 

U-Boot SPL 2024.01_armbian-202ns16550_serial serial@1c28000: p024.01-S866c-P7738-Hadc5-Vefe9-B2eb2-R448a (Feb 06 2026 - 03:49:45 +0000) Allwinner Technology
0)
Model: FriendlyARM NanoPi NEent from FAT... Unable to use mmc 1:1...
ial
Err:   serial
Net:   No ethernet found.
starting USB...
No working controllers found
1(part 0) is current device
Scacr
5475 bytes read in 2 ms (2.6 MiB/s)
## Executing script at 43100000
U-boot loaded from eMMC or secondary SD
MMC: no card present
* **
Failed to load '/boot/armbianEnv.txt'
Load fdt: /boot/dtb/sun8i-h3-nan13293004 bytes read in 419 ms (30.3 MiB/s)
10014752 bytes read in 317 ms (30.1 MiB/s)
ion
43400000 ...
   Image Name:   uInitrd
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    13292940 Bytes = 12.7 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
## Flattened Device Tree bloing Ramdisk to 49352000, end 49fOK
   Loading Device Tree to 49
Starting kernel ...


U-Boot SPL 2024.01_armbian-2024.01-S866c-P7738-Hadc5-Vefe9-B2eDRAM: 512 MiB
Trying to boot frns16550_serial serial@1c28000: p
CPU:   Allwinner H3 (SUN8I 168Core:  64 devices, 16 uclasses, mmc@1c0f000: 0, mmc@1c10000: 2, mmc@1c11000: 1
Loading Environment from FAT... In:    serial,usbkbd
Out:   serial
Err:   serial
Autoboot in 1 seconds, press <Space> to stop
switch to partitions #0, OK
mmc1(part 0) is current device
Sca/s)
## Executing script at 4310dary SD
MMC: no card present
** Bad device specification mmc 0Failed to load '/boot/armbianEnv.txt'
Load fdt: /boot/dtb/sun8i-h3-nanopi-neo-air.dtb
13293004 bytes read in 433 ms (29.3 MiB/s)
it Ramdisk from Legacy Image at 43400000 ...
   Image Name:   uux RAMDisk Image (gzip compressed)
   Data Size:    13292940 Bytes = 12.7 MiB
   Load Address: 00000000
   Entry Point:  0000b at 43000000
   Booting using the fdt blob at 0x43000000
Working Ramdisk to 49352000, end 49fff58c ... 2e0000, end 49351fff ... OK
Worns16550_serial serial@1c28000: p19


U-Boot 2024.01_armbian-22eb2-R448a (Feb 06 2026 - 03:49:45 +0000) Allwinner Technology
O Air
DRAM:  512 MiB
ent from FAT... switch to partitions #0, OK
mmc1(part 0) is current device
Scanning mmc 1:1...
Found U-Boot script /boot/boot.scr
/s)
## Executing script at 43100000
U-boot loaded from eMMC or secondary SD
MMC: no card present
** Bad device specification mmc 0 **
Failed to load '/boot/armbianEnv.txt'
13293004 bytes read in 447 ms (2ing Ramdisk to 49352000, end 49f ing USB...
No working controlleAutoboot in 1 seconds, press <Space> to stop
switch to partitions #0, OK
mmc1(part 0) is current device
Sca0000
* Bad device specification mmc 0 **
Failed to load '/boot/armbianEnv.txt'
Load fdt: /boot/dtb/sun8i-h3-nanopi-neo-air.dtb
13293004 bytes read in 433 ms (29.3 MiB/s)
OK
## Flattened Device Tree blob at 43000000
   Booting using ing FDT set to 43000000
   Loading Ramdisk to 49352000, end 49fff58c ... OK
   Loading Device Tree to 492e0000, end 49351fff ... OK
Working FDT set to 492e0000

Starting kernel ...

I builded armbian image with compile.sh BOARD=nanopiair BRANCH=legacy RELEASE=bookworm BUILD_MINIMAL=no BUILD_DESKTOP=no KERNEL_CONFIGURE=no CLEAN_LEVEL="make,debs,cache" OVERLAYS="analog-codec i2c0 i2c1 i2c2 usbhost2 usbhost3" COMPRESS_OUTPUTIMAGE=sha,gz WIREGUARD=yes NAMESERVER=8.8.8.8 DOCKER_ARMBIAN_BASE_IMAGE="ubuntu:jammy" for Nanopi Neo Air. Image is flashed to eMMC. Is any way to solve it?

Fix that might work for Zero2w is here https://forum.armbian.com/topic/31654-orange-pi-zero-2w/ (planning to test it soon)

Can somebody confirm Opi Zero2W 1.5GB has still this issue with some Armbian images ?  Armbian minimal boots without aby issues. Not sure why it works and desktop doesnt.

apt update produces "Hash Sum mismatch"

Anyways, doing my part testing legacy boards, hahahaha

A device of mine, running Armbian, cannot communicate with an Android device in my LAN. Otherwise everything else works.

My Orange Pi Zero 2w running Armbian can ping all of my LAN IPs (and access theyre net services also) , but fails at pinging an Android device (which is connected through WiFi): "Destination Host Unreachable".

Same goes the other way around where Termux runs on the above mentioned Android 15 device but cannot ping ("Destination Host Unreachable") the host running Armbian or access it via ssh (it simply stalls).

Everything else works just fine, all of my devices connect with each other without a glitch; they can all access every other running ssh instance inside the lan (which is a mix of Windows, Linux and Android devices). 

The very same Orange Pi Zero 2w running Armbian is perfectly accessible via ssh from all other hosts and vice versa.

The Android device running Termux is capable of pinging and accessing all other ssh hosts.

And there's more; I'm running Wireguard on the Orange Pi and it works fine. it works so good that once I access the lan with the Android Device through Wireguard, I can suddenly ping the Armbian host and ssh login into it.

Always using the very same IP address (no dns involved).

I wonder where I should look. I cannot imagine what's causing it.

Any suggestions? Is this a known scenario?

ArmBian Community running on Orange Pi Zero 2w

v26.2 rolling for Orange Pi Zero2W running Armbian Linux 6.12.71-current-sunxi64

Packages:     Debian stable (trixie)

Android 15 running Termux

Android REL 15 aarch64

Linux 5.10.236-android12-9-00020

Termux googleplay.2026.02.11

There's no WiFi separation on the router side.

my Cubitruck with  Armbian 23.8.1 Bullseye  has the false Time and i can't change this.

i don't know who is the problem.

"date" says me "Mo 9. Feb 19:24:06 CET 2026" but now we have 05:26, when i set date with "sudo date -s "2026-02-09 05:26:00", it looks like it will be override in the next moment, then "date" says 

 sudo date -s "2026-02-09 05:26:00"
Mo 9. Feb 05:26:00 CET 2026
root@cubietruck ~ > date
Mo 9. Feb 19:26:27 CET 2026

 dmesg | grep -i rtc
[    0.000000] Kernel command line: root=UUID=19cf2f1d-1a31-4890-bc04-a2f1c4e4e021 rootwait rootfstype=ext4 console=ttyS0,115200 console=tty1 hdmi.audio=EDID:0 disp.screen0_output_mode=1920x1080p60 panic=10 consoleblank=0 loglevel=1 ubootpart=ba110a34-01 ubootsource=mmc usb-storage.quirks=0x2537:0x1066:u,0x2537:0x1068:u rtc-hctosys=0  sunxi_ve_mem_reserve=0 sunxi_g2d_mem_reserve=0 sunxi_fb_mem_reserve=16 cgroup_enable=memory swapaccount=1
[    0.000000] Unknown kernel command line parameters "ubootpart=ba110a34-01 ubootsource=mmc rtc-hctosys=0 sunxi_ve_mem_reserve=0 sunxi_g2d_mem_reserve=0 sunxi_fb_mem_reserve=16 cgroup_enable=memory", will be passed to user space.
[    1.553534] sun4i-drm display-engine: [drm] Cannot find any crtc or sizes
[    1.555880] sun4i-drm display-engine: [drm] Cannot find any crtc or sizes
[    1.573650] sunxi-rtc 1c20d00.rtc: registered as rtc0
[    1.573701] sunxi-rtc 1c20d00.rtc: setting system clock to 2026-02-09T18:15:12 UTC (1770660912)
[    1.755046] axp20x-i2c 1-0034: Backup (RTC) battery charging is enabled
[    2.161281]     rtc-hctosys=0

 sudo systemctl restart chrony
chronyc tracking
chronyc sources -v
Reference ID    : 00000000 ()
Stratum         : 0
Ref time (UTC)  : Thu Jan 01 00:00:00 1970
System time     : 0.000000000 seconds slow of NTP time
Last offset     : +0.000000000 seconds
RMS offset      : 0.000000000 seconds
Frequency       : 6.181 ppm slow
Residual freq   : +0.000 ppm
Skew            : 0.000 ppm
Root delay      : 1.000000000 seconds
Root dispersion : 1.000000000 seconds
Update interval : 0.0 seconds
Leap status     : Not synchronised

  .-- Source mode  '^' = server, '=' = peer, '#' = local clock.
 / .- Source state '*' = current best, '+' = combined, '-' = not combined,
| /             'x' = may be in error, '~' = too variable, '?' = unusable.
||                                                 .- xxxx [ yyyy ] +/- zzzz
||      Reachability register (octal) -.           |  xxxx = adjusted offset,
||      Log2(Polling interval) --.      |          |  yyyy = measured offset,
||                                \     |          |  zzzz = estimated error.
||                                 |    |           \
MS Name/IP address         Stratum Poll Reach LastRx Last sample
===============================================================================
^? listserver.trexler.at         0   6     0     -     +0ns[   +0ns] +/-    0ns
^? time.netzwerge.de             0   6     0     -     +0ns[   +0ns] +/-    0ns
^? 2a02:8108:4d82:e400:9677>     0   6     0     -     +0ns[   +0ns] +/-    0ns
^? static.179.181.75.5.clie>     0   6     0     -     +0ns[   +0ns] +/-    0ns
^? 2a09:e1c1:efc4:1337::123      0   6     0     -     +0ns[   +0ns] +/-    0ns
^? 2a01:7e01::f03c:94ff:fee>     2   6     1     0  +50282s[+50282s] +/-   27ms
^? nobody.yourvserver.net        0   6     0     -     +0ns[   +0ns] +/-    0ns
^? ctb01.martinmoerch.dk         0   6     0     -     +0ns[   +0ns] +/-    0ns
^? fritz.box                     0   6     0     -     +0ns[   +0ns] +/-    0ns

What can be the problem and how can i fix it.

Thank you

But DietPies support for the ZeroPi is based on armbian, so I tried this directly:

oldest image not working: Armbian_community_25.8.0-trunk.338_Zeropi_bookworm_current_6.12.35_minimal.img.xz

bootlog12.txt

newest image working: Armbian_community_25.5.0-trunk.256_Zeropi_bookworm_legacy_6.1.104_minimal.img.xz

bootlog13.txt

Does anybody have an idea what it could be?

**2. Environment:**
*   **Hardware:** Orange Pi PC (Allwinner H3)
*   **Image/Distribution:** "Forky" (appears to be an Armbian-based rolling Debian fork)
*   **Kernel:** `6.12.68-current-sunxi` (build@armbian) #1 SMP Fri Jan 30 09:28:49 UTC 2026
*   **Graphics Stack:** Modern DRM/KMS (`sun4i-drm`). The legacy `fb` driver is not active.
*   **Monitor:** Connected via HDMI. EDID is correctly read (tested with `modetest`).

**3. Steps to Reproduce:**
1.  Boot the system with the affected image on an Orange Pi PC.
2.  Log in to the text console (`tty1`).
3.  Run `stty size`. It will always return `30 90`.
4.  Observe that the terminal only uses the top-left quarter of a 1920x1080 display.

**4. Diagnostic Evidence:**
```bash
# Console size is fixed and wrong:
$ stty size < /dev/tty1
30 90

# Framebuffer is provided by DRM and reports correct resolution:
$ cat /sys/class/graphics/fb0/name
sun4i-drmdrmfb
$ cat /sys/class/drm/card0/card0-HDMI-A-1/modes | head -1
1920x1080

# Kernel boot parameters (from /proc/cmdline) include video settings, but are ignored:
root=UUID=... video=HDMI-A-1:1920x1080@60 console=tty1 ...

# All attempted fixes that FAILED:
# - Boot parameters: `fbcon=font:VGA8x16`, `vt.global_cursor_default=0`, `drm_kms_helper.edid_firmware=...`
# - Runtime commands: `resizecons`, `setupcon`, `stty rows cols`, writing to `/sys/class/graphics/fbcon/`
# - Service restarts: `getty@tty1`, `gpm`
```

**5. Expected Behavior:**
The text console should automatically scale to use the full resolution of the framebuffer. For a 1920x1080 framebuffer with an 8x16 font, the expected `stty size` should be approximately `67 240` (or `67 120` for a 16x16 font). The console should fill the entire display.

**6. Additional Notes:**
*   The same hardware works correctly with a **Debian Bookworm** image and an older kernel, where console auto-scaling functions perfectly.
*   This indicates a **regression** in the `6.12.68-current-sunxi` kernel build or its DRM/KMS configuration for the Allwinner H3.
*   The bug makes the distribution unsuitable for any headless or console-focused use case on this hardware.

**7. Questions for Maintainers:**
*   Is there a specific kernel configuration option (`CONFIG_*`) for Allwinner H3 DRM that controls TTY auto-scaling?
*   Has the `vt` or `drm` subsystem changed in a way that requires new boot parameters for this hardware?
*   Can this be worked around without a kernel recompile?

Orange Pi 3 LTS rarely recognize ethernet connection.

How to reproduce?

Flash Orange Pi 3 LTS with an image of the latest version of Armbian.

Extra Info

The latest images tested which worked flawlessly was: 

Armbian_community_25.11.0-trunk.437_Orangepi3-lts_trixie_current_6.12.47_minimal.img

Armbian_23.8.3_Orangepi3-lts_jammy_current_6.1.53_minimal.img

Images tested which didn't worked:

Armbian_community_26.2.0-trunk.151_Orangepi3-lts_trixie_current_6.12.63_minimal.img

Armbian_community_26.2.0-trunk.100_Orangepi3-lts_trixie_current_6.12.63_minimal.img

In the boot log is this line:

Quote

ERROR: FDT image overlaps OS image (OS=0x41000000..0x418750d0)

So I tried to modify `fdt_addr_r` env variable and were able to succesfully boot with theese commands executed in u-boot console:

Quote

env set fdt_addr_r 0x41900000
boot

So adding following line to /boot/armbianEnv.txt on sdcard can fix booting permanently:

Quote

fdt_addr_r=0x41900000

Complete boot log:

Quote

U-Boot SPL 2022.07-armbian (May 01 2023 - 22:12:06 +0000)
DRAM: 128 MiB
Trying to boot from MMC1


U-Boot 2022.07-armbian (May 01 2023 - 22:12:06 +0000) Allwinner Technology

CPU:   Allwinner V3s (SUN8I 1681)
Model: PineCube IP Camera
DRAM:  128 MiB
Core:  46 devices, 19 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
Net:   No ethernet found.
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
4121 bytes read in 2 ms (2 MiB/s)
## Executing script at 41900000
U-boot loaded from SD
Boot script loaded from mmc
154 bytes read in 2 ms (75.2 KiB/s)
12336677 bytes read in 512 ms (23 MiB/s)
8868048 bytes read in 369 ms (22.9 MiB/s)
Found mainline kernel configuration
18803 bytes read in 7 ms (2.6 MiB/s)
Failed to load '/boot/dtb/overlay/sun8i-v3s-fixup.scr'
Kernel image @ 0x41000000 [ 0x000000 - 0x8750d0 ]
## Loading init Ramdisk from Legacy Image at 41c00000 ...
  Image Name:   uInitrd
  Image Type:   ARM Linux RAMDisk Image (gzip compressed)
  Data Size:    12336613 Bytes = 11.8 MiB
  Load Address: 00000000
  Entry Point:  00000000
  Verifying Checksum ... OK
## Flattened Device Tree blob at 41800000
  Booting using the fdt blob at 0x41800000
ERROR: FDT image overlaps OS image (OS=0x41000000..0x418750d0)
SCRIPT FAILED: continuing...
No EFI system partition
BootOrder not defined
EFI boot manager: Cannot load any image
No ethernet found.
missing environment variable: pxeuuid
Retrieving file: pxelinux.cfg/00000000
No ethernet found.
Retrieving file: pxelinux.cfg/0000000
No ethernet found.
Retrieving file: pxelinux.cfg/000000
No ethernet found.
Retrieving file: pxelinux.cfg/00000
No ethernet found.
Retrieving file: pxelinux.cfg/0000
No ethernet found.
Retrieving file: pxelinux.cfg/000
No ethernet found.
Retrieving file: pxelinux.cfg/00
No ethernet found.
Retrieving file: pxelinux.cfg/0
No ethernet found.
Retrieving file: pxelinux.cfg/default-arm-sunxi-sunxi
No ethernet found.
Retrieving file: pxelinux.cfg/default-arm-sunxi
No ethernet found.
Retrieving file: pxelinux.cfg/default-arm
No ethernet found.
Retrieving file: pxelinux.cfg/default
No ethernet found.
Config file not found
No ethernet found.
No ethernet found.

 

U-Boot SPL 2022.10-armbian (Jun 15 2023 - 13:35:35 +0000)
DRAM: 1024 MiB
CPU: 912000000Hz, AXI/AHB/APB: 3/2/2
Trying to boot from MMC1
ns16550_serial serial@1c28000: pinctrl_select_state_full: uclass_get_device_by_phandle_id: err=-19


U-Boot 2022.10-armbian (Jun 15 2023 - 13:35:35 +0000) Allwinner Technology

CPU:   Allwinner A20 (SUN7I)
Model: LinkSprite pcDuino3
DRAM:  1 GiB
Core:  52 devices, 23 uclasses, devicetree: separate
WDT:   Not starting watchdog@1c20c90
MMC:   mmc@1c0f000: 0
Loading Environment from FAT... Unable to use mmc 0:1...
Unknown monitor
Unknown monitor
In:    serial
Out:   serial
Err:   serial
Net:   eth_designware ethernet@1c50000: Can't get reset: -2
eth0: ethernet@1c50000
230454 bytes read in 12 ms (18.3 MiB/s)
Unknown monitor
starting USB...
Bus usb@1c14000: USB EHCI 1.00
Bus usb@1c14400: USB OHCI 1.0
Bus usb@1c1c000: USB EHCI 1.00
Bus usb@1c1c400: USB OHCI 1.0
scanning bus usb@1c14000 for devices... 2 USB Device(s) found
scanning bus usb@1c14400 for devices... 1 USB Device(s) found
scanning bus usb@1c1c000 for devices... 1 USB Device(s) found
scanning bus usb@1c1c400 for devices... 1 USB Device(s) found
       scanning usb for storage devices... 0 Storage Device(s) found
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
4121 bytes read in 2 ms (2 MiB/s)
## Executing script at 43100000
U-boot loaded from SD
Boot script loaded from mmc
154 bytes read in 2 ms (75.2 KiB/s)
16660327 bytes read in 690 ms (23 MiB/s)
8480576 bytes read in 355 ms (22.8 MiB/s)
Found mainline kernel configuration
42775 bytes read in 9 ms (4.5 MiB/s)
5532 bytes read in 5 ms (1.1 MiB/s)
Applying kernel provided DT fixup script (sun7i-a20-fixup.scr)
## Executing script at 45000000
Kernel image @ 0x42000000 [ 0x000000 - 0x816740 ]
## Loading init Ramdisk from Legacy Image at 43400000 ...
   Image Name:   uInitrd
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    16660263 Bytes = 15.9 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
## Flattened Device Tree blob at 43000000
   Booting using the fdt blob at 0x43000000
EHCI failed to shut down host controller.
   Loading Ramdisk to 4901c000, end 49fff727 ... OK
   Loading Device Tree to 48fa9000, end 4901bfff ... OK
DE is present but not probed

Starting kernel ...

I will gratefully for any possible insight

Cheers

Ryzer

I have successfully built the image using the armbian configuration script (bookworm current), the board boots and runs teslausb, however, I am unable to install the driver for my wifi dongle. The error when starting the install-driver.sh script is "your kernel headers are not properly installed". I tried apt install linux-headers-current-sunxi and kernel-headers-armmp, they install successfully but I still get the same error about the kernet headers not being properly installed.

The drivers are for rtl88x2bu cloned from morrownr on github

Any help would be appreciated

Gaetano.

https://www.aliexpress.us/item/2251832431328471.html

I found these recent instructions to be able to display graphics here:

https://ryjelsum.me/homelab/xpt2046-ili9341-opi-zero/

with a reference to a previous experience (without mentioning success)

https://hackaday.io/project/190371-g-edm/log/217902-first-success-with-armbian-nanopi-and-ili9341-touch

and independently, I found these instructions and experiences here:

https://docs.armbian.com/User-Guide_Allwinner_overlays/

https://forum.armbian.com/topic/27457-connecting-banana-pi-m2-zero-with-ili9341-display-over-spi-on-latest-armbian-image/ <-just found it and it has some success with BananaPi M2 Zero

https://tech-de.netlify.app/articles/de547180/index.html

https://4pda.to/forum/index.php?showtopic=782242&st=5060#entry112401076

I connected with wires as shown in instructions: https://forum.armbian.com/topic/28674-text-version-of-orange-pi-zero-pinout/

And the LCD's LED input pin to 3.3V

I activated the spi-add-cs1 overlay in arbian-config

I copied the dts for opiZ into ~/ili9341/ili9341-touch-double-spi-cs.dts

Then, I executed:
 

cd ili9341
armbian-add-overlay ili9341-touch-double-spi-cs.dts

Then, I rebooted, and my LCD just looks gray.

My armbianEnv looks like this:

verbosity=1
bootlogo=false
console=both
disp_mode=1920x1080p60
overlay_prefix=sun8i-h3
overlays=spi-add-cs1 tve usbhost2 usbhost3
rootdev=UUID=7d9a7016-73db-4f9c-a5bd-e3e5ab53ffc4
rootfstype=ext4
user_overlays=ili9341-touch-double-spi-cs
usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u

my armbianmonitor -u: https://paste.armbian.com/arogurekiv

I am still not done checking against the experiences with Bpi M2-0, but I ask here: anyone has experience with ILI9341+XPT2046, in either OrangePi Zero or Zero 3?

Should I downgrade to Linux 6.1.53?

It depends on having sysfs files in /sys/class/gpio/

My original opi zero has these files and it works, but my opi zero3 doesn’t have these files

I learned that /sys/class/gpio is created if the linux kernel is configured with a specific option ON, as suggested in the documentation:

https://github.com/rm-hull/OPi.GPIO

https://linux-sunxi.org/GPIO 

Also, a developer has made a change on the opi.GPIO project to support opi zero3

https://github.com/rm-hull/OPi.GPIO/issues/79 

I will have time to try this tomorrow... but I want to ask: is anyone using GPIO in its most basic way?

As reference: I saw this older thread about zero3's GPIO... 

https://forum.armbian.com/topic/31493-how-to-enable-i2c3-on-orange-pi-zero-3/

It is using leebobby's "armbian" image, with raspi-config, and wiringpi

Using my original opi-zero, I never needed to use armbian-config to enable basic gpio and the python opi.gpio just worked as documented

Note: the opi.gpio only claims to support basic gpio, not i2c.

Update: these are interesting potential solutions and discussions (but they are all from before there was armbian for opiz3)

https://www.reddit.com/r/OrangePI/comments/16vfa4g/orange_pi_zero_3_gpio_python_library/

https://github.com/eutim/OPI.GPIO

https://www.reddit.com/r/OrangePI/comments/16ioyri/gpio_python_library_for_orange_pi_zero_3/

https://www.reddit.com/r/OrangePI/comments/18iveo3/how_to_control_gpio_pins_in_android_orange_pi/

With latest edge 6.15.4 the board boots fine, shutdown also clean and complete but on reboot it does not again start up. Need to powercycle😒

I gets stuck et end of shutdown. Same for latest bookworm image (I think it's 6.12x).

Earlier ones did work.

=> Any other board also affected?

=> Is for reboot the watchdog involved?

   T.

Failed to retrieve unit state: Transport endpoint is not connected

    _             _    _                                         _ _        
   /_\  _ _ _ __ | |__(_)__ _ _ _    __ ___ _ __  _ __ _  _ _ _ (_) |_ _  _ 
  / _ \| '_| '  \| '_ \ / _` | ' \  / _/ _ \ '  \| '  \ || | ' \| |  _| || |
 /_/ \_\_| |_|_|_|_.__/_\__,_|_||_|_\__\___/_|_|_|_|_|_\_,_|_||_|_|\__|\_, |
                                 |___|                                 |__/ 
 v26.2 rolling for Orange Pi Zero running Armbian Linux 6.12.63-current-sunxi

 Packages:     Debian stable (trixie)
 Support:      for advanced users (rolling release)
Failed to retrieve unit state: Transport endpoint is not connected

trying reboot:

root@orangepizero:~# reboot 
Call to Reboot failed: Connection timed out
 

OK, unpacked one of my old breadboard projects on focal Linux nanopiduo 5.10.60-sunxi #21.08.2 SMP Tue Sep 14 16:28:44 UTC 2021 armv7l armv7l armv7l GNU/Linux. CPU idles cool, so I do a:

sudo cat /sys/class/regulator/regulator.5/microvolts
1100000

It looks like 6.x kernel/nobel is using 1.3v. There it is. 1.1V. That confirms the mismatch perfectly. Your old Focal breadboard is running at 1.1V, while the modern Noble board is forcing 1.3V.

On these chips, that 0.2V difference is massive because power (and heat) scales with the square of the voltage. Moving from 1.1V to 1.3V increases heat output by about 40%, which is why one board is a stable 50°C and the other is a 96°C furnace.

So more hacking to do. I'll see if I can do a build hack.

trunk 100 works fine.

I have a board nanopi neo air with armbian linux on it.   We with my colleague try to setting up ffmpeg with cedrus264 for hardware accelerated  capturing video from ov5640-like camera device. 

There is my  armbianmonitor.  

There are my v4l2-ctl -d /dev/videox -D out:

After some reconfiguration of dts, we can successfully capture video in low fps with 

ffmpeg -f v4l2 -framerate 25 -video_size 960x720 -i /dev/video1 output.mkv

but with 

ffmpeg -f v4l2 -channel 0 -video_size 960x720 -i /dev/video1 -pix_fmt nv12 -r 30 -b:v 64k -c:v cedrus264 test.mp4

ffmpeg failed: 

Ffmpeg was buided from FFmpeg-Cedrus, also we  try follow this and use this binaries - result haven't changed. 

After some inspecting sources of ffmpeg-cedrus we found that ffmpeg try to open /dev/cedar_dev device, which don't exists in our system.  Ffmpeg fails on opening device. If we replace /dev/cedar_dev by /dev/video0, where is our cedrus driver, ffmpeg fails on ioctl IOCTL_GET_ENV_INFO.  In source, it is 99 or 101 line.

We check kernel config for configuration, provided by Sunxi-Cedrus and determine that cedrus was configured right. 

Also we  have tried all described actions on official armbian buster image for nanopi neo air and we have got the same result. 

What we does wrong? 

In orange pi zero 3, we need to stay in bookworm to get video acceleration, so this guide helps build labwc in bookworm

As a greeter, I chose pi-greeter, because it is the lightest login manager I could setup, without any X11

https://github.com/robertojguerra/opiz3-labwc-setup

I am open to read any improvements, or show me how I could make deb packages.

In the near future, I will make a step-by-step video tutorial in Youtube.

*sorry for my bad English.

I found the page https://www.armbian.com/longanpi-3h/ Sipeed LonganPi 3H but no OS images to download. Can anyone help me and give me links to ISOs or there are none yet?

I've already successfully compiled an image by adding a new config to u-boot and armbian-build, and a device tree to the linux kernel. Now I'm looking to get the WiFi working, but I can't seem to find where I can change its pin definitions.

I'm using the AP6212: the SDIO pins are connected to SDC1 (aka mmc1) like every other board, but the WL_REG_ON (aka WL-PMU-EN) and WL_HOST_WAKE (aka WL-WAKE-AP) pins are connected to GPIO pins different from all other boards, so I'll need to change their pin assignments in the kernel manually. But I can't find where are these pins defined! Do I need to change it via u-boot, the kernel, a module or some config file?

Any pointers would be appreciated! Thanks in advance

# uname -a
Linux nanopineo 5.15.25-sunxi #22.02.1 SMP Sun Feb 27 09:23:25 UTC 2022 armv7l GNU/Linux

# cat /sys/devices/platform/leds/leds/nanopi:green:status/trigger
cat: '/sys/devices/platform/leds/leds/nanopi:green:status/trigger': No such file or directory

# cat /sys/class/leds/led{0,1}/trigger
cat: /sys/class/leds/led0/trigger: No such file or directory
cat: /sys/class/leds/led1/trigger: No such file or directory

# ls -lha /sys/class/leds/
total 0
drwxr-xr-x  2 root root 0 Dec 31  1969 .
drwxr-xr-x 62 root root 0 Dec 31  1969 ..

# grep led /var/log/syslog
Feb 27 22:38:48 nanopineo kernel: [    2.532268] leds-gpio: probe of leds failed with error -16
Feb 27 22:38:48 nanopineo kernel: [    2.534730] ledtrig-cpu: registered to indicate activity on CPUs

# locate leds
/usr/bin/setleds
/usr/include/linux/uleds.h
/usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds
/usr/lib/modules/5.15.25-sunxi/kernel/drivers/input/input-leds.ko.xz
/usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/flash
/usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/led-class-flash.ko.xz
/usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/leds-an30259a.ko.xz
/usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/leds-axp20x.ko.xz
/usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/leds-bcm6328.ko.xz
/usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/leds-bcm6358.ko.xz
/usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/leds-bd2802.ko.xz
/usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/leds-cpcap.ko.xz
/usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/leds-cr0014114.ko.xz
/usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/leds-dac124s085.ko.xz
/usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/leds-el15203000.ko.xz
/usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/leds-is31fl319x.ko.xz
/usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/leds-is31fl32xx.ko.xz
/usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/leds-lm3530.ko.xz
/usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/leds-lm3532.ko.xz
/usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/leds-lm355x.ko.xz
/usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/leds-lm3642.ko.xz
/usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/leds-lm3692x.ko.xz
/usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/leds-lm3697.ko.xz
/usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/leds-lp3944.ko.xz
/usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/leds-lp3952.ko.xz
/usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/leds-lp5521.ko.xz
/usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/leds-lp5523.ko.xz
/usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/leds-lp5562.ko.xz
/usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/leds-lp55xx-common.ko.xz
/usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/leds-lp8501.ko.xz
/usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/leds-lp8860.ko.xz
/usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/leds-lt3593.ko.xz
/usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/leds-max77650.ko.xz
/usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/leds-mlxreg.ko.xz
/usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/leds-pca9532.ko.xz
/usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/leds-pca955x.ko.xz
/usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/leds-pca963x.ko.xz
/usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/leds-pwm.ko.xz
/usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/leds-regulator.ko.xz
/usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/leds-spi-byte.ko.xz
/usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/leds-tca6507.ko.xz
/usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/leds-ti-lmu-common.ko.xz
/usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/leds-tlc591xx.ko.xz
/usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/trigger
/usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/flash/leds-as3645a.ko.xz
/usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/flash/leds-ktd2692.ko.xz
/usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/flash/leds-lm3601x.ko.xz
/usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/flash/leds-rt4505.ko.xz
/usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/flash/leds-rt8515.ko.xz
/usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/trigger/ledtrig-audio.ko.xz
/usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/trigger/ledtrig-backlight.ko.xz
/usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/trigger/ledtrig-camera.ko.xz
/usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/trigger/ledtrig-gpio.ko.xz
/usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/trigger/ledtrig-netdev.ko.xz
/usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/trigger/ledtrig-oneshot.ko.xz
/usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/trigger/ledtrig-pattern.ko.xz
/usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/trigger/ledtrig-timer.ko.xz
/usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/trigger/ledtrig-transient.ko.xz
/usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/trigger/ledtrig-tty.ko.xz
/usr/share/X11/xkb/compat/ledscroll
/usr/share/man/man1/setleds.1.gz

# ls -l /proc/device-tree/leds
total 0
-r--r--r-- 1 root root 10 Apr 10 10:35 compatible
drwxr-xr-x 2 root root  0 Apr 10 10:30 led-0
drwxr-xr-x 2 root root  0 Apr 10 10:30 led-1
-r--r--r-- 1 root root  5 Apr 10 10:35 name
-r--r--r-- 1 root root  8 Apr 10 10:35 pinctrl-0
-r--r--r-- 1 root root  8 Apr 10 10:35 pinctrl-names
drwxr-xr-x 2 root root  0 Apr 10 10:30 pwr
drwxr-xr-x 2 root root  0 Apr 10 10:30 status

# ls -l /proc/device-tree/leds/led-0
total 0
-r--r--r-- 1 root root 16 Apr 10 10:36 gpios
-r--r--r-- 1 root root 19 Apr 10 10:36 label
-r--r--r-- 1 root root 10 Apr 10 10:36 linux,default-trigger
-r--r--r-- 1 root root  6 Apr 10 10:36 name

# ls -l /proc/device-tree/leds/led-1
total 0
-r--r--r-- 1 root root  3 Apr 10 10:36 default-state
-r--r--r-- 1 root root 16 Apr 10 10:36 gpios
-r--r--r-- 1 root root 17 Apr 10 10:36 label
-r--r--r-- 1 root root  6 Apr 10 10:36 name

# ls -l /proc/device-tree/leds/pwr
total 0
-r--r--r-- 1 root root 16 Apr 10 10:37 gpios
-r--r--r-- 1 root root 15 Apr 10 10:37 label
-r--r--r-- 1 root root 11 Apr 10 10:37 linux,default-trigger
-r--r--r-- 1 root root  4 Apr 10 10:37 name

# ls -l /proc/device-tree/leds/status
total 0
-r--r--r-- 1 root root 16 Apr 10 10:37 gpios
-r--r--r-- 1 root root 20 Apr 10 10:37 label
-r--r--r-- 1 root root 10 Apr 10 10:37 linux,default-trigger
-r--r--r-- 1 root root  7 Apr 10 10:37 name

# cat /proc/device-tree/leds/led-0/gpios

<nothing>

# cat /proc/device-tree/leds/led-0/label
nanopi:blue:status

# cat /proc/device-tree/leds/led-0/linux,default-trigger
heartbeat

# cat /proc/device-tree/leds/led-0/name
led-0

# cat /proc/device-tree/leds/led-1/default-state
on

# cat /proc/device-tree/leds/led-1/gpios
9

# cat /proc/device-tree/leds/led-1/label
nanopi:green:pwr

# cat /proc/device-tree/leds/led-1/name
led-1

# cat /proc/device-tree/leds/pwr/gpios
9

# cat /proc/device-tree/leds/pwr/label
nanopi:red:pwr

# cat /proc/device-tree/leds/pwr/linux,default-trigger
default-on

# cat /proc/device-tree/leds/pwr/name
pwr

# cat /proc/device-tree/leds/status/gpios

<nothing>

# cat /proc/device-tree/leds/status/label
nanopi:green:status

# cat /proc/device-tree/leds/status/linux,default-trigger
heartbeat

# cat /proc/device-tree/leds/status/name
status

In the armbian-config .dts editor I found that led-0 and led-1 are reversed from what I found above. led-0 is blue and led-1 is green. I don't know if that's a show stopper or not.

--- current.dts > edit not saved, kept original ---

1463         leds {
1464                 compatible = "gpio-leds";
1465
1466                 led-0 {
1467                         label = "nanopi:green:pwr";
1468                         gpios = <0x3f 0x00 0x0a 0x00>;
1469                         default-state = "on";
1470                 };
1471
1472                 led-1 {
1473                         label = "nanopi:blue:status";
1474                         gpios = <0x0e 0x00 0x0a 0x00>;
1475                         linux,default-trigger = "heartbeat";
1476                 };
1477         };

The config-5.15.25-sunxi file shows;

#
# LED Triggers
#
CONFIG_LEDS_TRIGGERS=y
CONFIG_LEDS_TRIGGER_TIMER=m
CONFIG_LEDS_TRIGGER_ONESHOT=m
CONFIG_LEDS_TRIGGER_DISK=y
CONFIG_LEDS_TRIGGER_MTD=y
CONFIG_LEDS_TRIGGER_HEARTBEAT=y
CONFIG_LEDS_TRIGGER_BACKLIGHT=m
CONFIG_LEDS_TRIGGER_CPU=y
CONFIG_LEDS_TRIGGER_ACTIVITY=y
CONFIG_LEDS_TRIGGER_GPIO=m
CONFIG_LEDS_TRIGGER_DEFAULT_ON=y

I booted with a previous version of DietPi and the LEDs were working as before. It looks like everything needed is there and the correct default trigger is shown etc,

I'm not sure where to look next.

armbianmonitor -u
System diagnosis information will now be uploaded to

Sunvell R69 - Linux sunvell-r69 5.4.0-rc8-sunxi #19.11.3 SMP Wed Nov 27 17:01:29 CET 2019 armv7l armv7l armv7l GNU/Linux : 

http://ix.io/232T

NanoPi Neo - Linux npi-neo 5.3.3-sunxi #5.98 SMP Sat Oct 5 18:34:15 +03 2019 armv7l GNU/Linux :

http://ix.io/232U

in dmesg it looks like
 

[10536.264427] dwmac-sun8i 1c30000.ethernet eth0: Link is Up - 100Mbps/Full - flow control rx/tx
[10568.008879] dwmac-sun8i 1c30000.ethernet eth0: Link is Down
[10571.081067] dwmac-sun8i 1c30000.ethernet eth0: Link is Up - 100Mbps/Full - flow control rx/tx
[10575.177000] dwmac-sun8i 1c30000.ethernet eth0: Link is Down
[10580.297247] dwmac-sun8i 1c30000.ethernet eth0: Link is Up - 100Mbps/Full - flow control rx/tx
[10604.873552] dwmac-sun8i 1c30000.ethernet eth0: Link is Down
[10607.945753] dwmac-sun8i 1c30000.ethernet eth0: Link is Up - 100Mbps/Full - flow control rx/tx
[10608.969632] dwmac-sun8i 1c30000.ethernet eth0: Link is Down
[10612.041827] dwmac-sun8i 1c30000.ethernet eth0: Link is Up - 100Mbps/Full - flow control rx/tx
[10631.498029] dwmac-sun8i 1c30000.ethernet eth0: Link is Down
[10633.546213] dwmac-sun8i 1c30000.ethernet eth0: Link is Up - 100Mbps/Full - flow control rx/tx
[10636.618141] dwmac-sun8i 1c30000.ethernet eth0: Link is Down

I have the feeling its could have to do with using 1GBit/1000MBit devices on the same 100MBit-Ethernet-Hub, because I do get much mor of these messages when my armbian-build-system-PC is on (which uses a onboard GBit-Ethernet-Card).
On the 100MBit-Hub there are also some othe 1GBit-Devices like the NanoPi Neo2.

On the PC I did try to force the 1GBit-Card to 100MBit with ethtool -s eth0 speed 100 autoneg off 

But that doesnt seem to help.

On other SBC-devices I could find these messages in the dmesg (and in the froum search it was a problem 4 to 2 years ago)

On the other hand there was a disscussion about a new driver version for kernel 4.1.4 at
https://forum.armbian.com/topic/4364-dwmac-sun8i- driver-v6/

With debian stretch armabian 5.41 and kernel 4.1.4.34 I did see that problem (and doenst feel it at a SSH-session) on the Sunvell R69. 

The kernel works, but installing the .deb failed because my extlinux script could not copy:

/usr/lib/linux-image-6.18.1-edge-sunxi/overlay/sun8i-h3-analog-codec.dtbo

The whole overlay folder does not exist. It does exist for  6.12.58-current-sunxi  and last time I compiled kernel for the nanopineo was 6.16.8, the overlays were created.

I remember it was also once the case with edge kernel for other SBC ( .deb package from the Armbian beta repo). That time own local build did create overlays.

I am not sure where to look or what could be wrong.
 

After upgrading to Armbian 26 (kernel version 6.12.58), the onboard network card (end0) experienced a severe degradation in transmission performance (reduced to approximately 1/10 of previous levels). Upon investigation, it was discovered that the kernel driver (dwmac-sun8i) has locked all hardware offload features (TSO/GSO/Checksum), forcing the CPU to handle all processing in software.

root@orangepi3:~# uname -r
6.12.58-current-sunxi64

root@orangepi3:~# dpkg --list | grep linux-image
ii  linux-image-current-sunxi64       26.2.0-trunk.48                         arm64        Armbian Linux current kernel image 6.12.58-current-sunxi64

root@orangepi3:~# readlink /sys/class/net/end0/device/driver
../../../../bus/platform/drivers/dwmac-sun8i

root@orangepi3:~# ethtool -k end0
Features for end0:
rx-checksumming: off
tx-checksumming: off
        tx-checksum-ipv4: off
        tx-checksum-ip-generic: off [fixed]
        tx-checksum-ipv6: off
        tx-checksum-fcoe-crc: off [fixed]
        tx-checksum-sctp: off [fixed]
scatter-gather: off
        tx-scatter-gather: off
        tx-scatter-gather-fraglist: off [fixed]
tcp-segmentation-offload: off
        tx-tcp-segmentation: off [fixed]
        tx-tcp-ecn-segmentation: off [fixed]
        tx-tcp-mangleid-segmentation: off [fixed]
        tx-tcp6-segmentation: off [fixed]
generic-segmentation-offload: off
generic-receive-offload: off
large-receive-offload: off [fixed]
rx-vlan-offload: on [fixed]
tx-vlan-offload: off [fixed]
ntuple-filters: off [fixed]
receive-hashing: off [fixed]
highdma: on [fixed]
rx-vlan-filter: off [fixed]
vlan-challenged: off [fixed]
tx-gso-robust: off [fixed]
tx-fcoe-segmentation: off [fixed]
tx-gre-segmentation: off [fixed]
tx-gre-csum-segmentation: off [fixed]
tx-ipxip4-segmentation: off [fixed]
tx-ipxip6-segmentation: off [fixed]
tx-udp_tnl-segmentation: off [fixed]
tx-udp_tnl-csum-segmentation: off [fixed]
tx-gso-partial: off [fixed]
tx-tunnel-remcsum-segmentation: off [fixed]
tx-sctp-segmentation: off [fixed]
tx-esp-segmentation: off [fixed]
tx-udp-segmentation: off [fixed]
tx-gso-list: off [fixed]
tx-nocache-copy: off
loopback: off [fixed]
rx-fcs: off [fixed]
rx-all: off [fixed]
tx-vlan-stag-hw-insert: off [fixed]
rx-vlan-stag-hw-parse: on [fixed]
rx-vlan-stag-filter: off [fixed]
l2-fwd-offload: off [fixed]
hw-tc-offload: off [fixed]
esp-hw-offload: off [fixed]
esp-tx-csum-hw-offload: off [fixed]
rx-udp_tunnel-port-offload: off [fixed]
tls-hw-tx-offload: off [fixed]
tls-hw-rx-offload: off [fixed]
rx-gro-hw: off [fixed]
tls-hw-record: off [fixed]
rx-gro-list: off
macsec-hw-offload: off [fixed]
rx-udp-gro-forwarding: off
hsr-tag-ins-offload: off [fixed]
hsr-tag-rm-offload: off [fixed]
hsr-fwd-offload: off [fixed]
hsr-dup-offload: off [fixed]
 

Could you please help look into this issue? We are looking forward to seeing it fixed in an upcoming release. Thank you very much.

Regards,

GBH

My board Nano pi neo2 

I have been trying to get sound working on my Orange Pi Zero 3, and I am facing persistent issues. I installed every operating system listed on Armbian’s Orange Pi Zero 3 page and followed all the standard setup procedures. Despite updating all packages and even performing kernel updates, I have never been able to get any sound output from the device.

I have checked multiple configurations, tried different OS images, and ensured that all drivers are up to date, but nothing works. The device otherwise functions normally, but audio simply does not come through under any circumstances.

Could you please provide guidance or a solution? Any help would be greatly appreciated.

Latest stable community release:

https://github.com/armbian/community/releases/download/24.5.0-trunk.123/Armbian_community_24.5.0-trunk.123_Orangepipc2_bookworm_current_6.6.20_minimal.img.xz

With update 23.11 -> 24.2 the orange pi pc2 no longer starts.

I tried a new sd installation and it too does not appear on the network. Right now I don't have a serial cable to check but it is possible that the network driver is missing or not working.

SD, SBC and PSU are 100% working: a revert to 23.11.2 makes it work perfectly.

apt update
Stary:1 http://deb.debian.org/debian bookworm InRelease
Stary:2 http://security.debian.org bookworm-security InRelease                                                          
Stary:3 https://download.docker.com/linux/debian bookworm InRelease                                                     
Stary:4 http://deb.debian.org/debian bookworm-updates InRelease                                                         
Stary:5 http://deb.debian.org/debian bookworm-backports InRelease                                                       
Stary:6 https://dtcooper.github.io/raspotify raspotify InRelease                                                        
Stary:7 https://github.armbian.com/configng stable InRelease                                                            
Stary:8 http://armbian.lv.auroradev.org/beta bookworm InRelease                                       
Czytanie list pakietów... Gotowe                         
Budowanie drzewa zależności... Gotowe
Odczyt informacji o stanie... Gotowe   
1 package can be upgraded. Run 'apt list --upgradable' to see it.
root@orangepi3-lts:~# apt list --upgradable
Listing... Gotowe
armbian-bsp-cli-orangepi3-lts-current/bookworm 25.11.0-trunk.401 arm64 [upgradable from: 25.8.0-trunk.49]
N: There is 1 additional version. Please use the '-a' switch to see it
root@orangepi3-lts:~# apt list --upgradable -a
Listing... Gotowe
armbian-bsp-cli-orangepi3-lts-current/bookworm 25.11.0-trunk.401 arm64 [upgradable from: 25.8.0-trunk.49]
armbian-bsp-cli-orangepi3-lts-current/now 25.8.0-trunk.49 arm64 [installed,upgradable to: 25.11.0-trunk.401]

maybe someone has already dealt with this message and error?

Does the image come with and install non free software on the computer? If so is there documentation showing how to do a fully free software installation of the Armbian_community_25.11.0-trunk.546_Lime2_trixie_current_6.12.58_minimal.img image?

Free software is software you can use, share, modify and redistribute. Thank you.

I wrote aind compile little module only for tests:

#include <linux/module.h>
#include <linux/sched.h>

static int errval = 0;

//module_param(errval,int,S_IRWXU);
module_param(errval,int,S_IWUSR|S_IRUSR|S_IWGRP|S_IRGRP);
MODULE_PARM_DESC(errval,"Value to return from init function");
int my_init_module(void)
{
	
	
    printk("errval=%d\n",errval);
	return errval;
}

void my_cleanup_module(void)
{
	printk("The module is now unloaded\n");
}
module_init(my_init_module);
module_exit(my_cleanup_module);
MODULE_LICENSE("GPL");

compile by:

make -C /lib/modules/6.6.75-current-sunxi64/build  M=$(PWD) modules

And it cause segmentation fault

onlyme@orangepizero3:~/modules/errors$ sudo insmod errs.ko
[sudo] password for onlyme: 

Message from syslogd@orangepizero3 at Mar 10 13:35:33 ...
 kernel:[  331.593726] Internal error: Oops: 0000000096000004 [#1] SMP

Message from syslogd@orangepizero3 at Mar 10 13:35:33 ...
 kernel:[  331.798432] Code: 540005a0 f9401680 aa1a03e2 aa1703e1 (f9406400) 
Segmentation fault

On Ubuntu x86 and raspbian (raspbery pi 3) it works, on orangepi zero 3 dosnet. Why?

Quote

[   22.495764] sun55i-gmac200 4510000.ethernet: deferred probe timeout, ignoring dependency
[   22.495788] sun55i-gmac200 4510000.ethernet: probe with driver sun55i-gmac200 failed with error -110
 

2025-06-05T11:29:33.367636+02:00 bananapipro2 kernel: [934985.549250] sysrq: HELP : loglevel(0-9) reboot(b) crash(c) terminate-all-tasks(e) memory-full-oom-kill(f) kill-all-tasks(i) thaw-filesystems(j) sak(k) show-backtrace-all-active-cpus(l) show-memory-usage(m) nice-all-RT-tasks(n) poweroff(o) show-registers(p) show-all-timers(q) unraw(r) sync(s) show-task-states(t) unmount(u) show-blocked-tasks(w) dump-ftrace-buffer(z) replay-kernel-logs(R)

The system continues to work (although I remember that it stooped at this point in older releases).

Is there any action required? I am afraid that this could stop my system which is running unattended for longer periods usually.

I am running v25.2.2 for Banana Pi Pro running Armbian Linux 6.12.20-current-sunxi.

I'm getting stuck trying to compile the cedar_ve kernel driver from https://github.com/uboborov/sunxi-cedar-mainline

I have downloaded the kernel source using armbian-config and then built the sunxi-cedar-mainline kernel driver. However, I fail to load the driver due to version magic:

Quote

root@nanopineo:~# modprobe cedar_ve
modprobe: ERROR: could not insert 'cedar_ve': Exec format error
root@nanopineo:~# dmesg | tail -n 1
[  653.998366] cedar_ve: version magic '5.15.80 SMP mod_unload ARMv7 thumb2 p2v8 ' should be '5.15.80-sunxi SMP mod_unload ARMv7 thumb2 p2v8 '

When trying to force the load:

Quote

root@nanopineo:~# modprobe -f cedar_ve
modprobe: ERROR: could not insert 'cedar_ve': Exec format error

But no dmesg message about magic check failure.
 

Here's some more details:

uname -r returns: 6.12.23-current-sunxi64

cat /boot/armbianEnv.txt returns:

verbosity=1
bootlogo=false
console=both
disp_mode=1920x1080p60
overlay_prefix=sun50i-h616
rootdev=UUID=adb61282-df86-4116-9688-e94c56913687
rootfstype=ext4
overlays=i2c0-pi i2c1-pi
param_i2c1_pin_sda=3
param_i2c1_pin_scl=5
user_overlays=
usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u

sudo i2cdetect -l returns:
i2c-0   i2c             DesignWare HDMI                         I2C adapter
i2c-1   i2c             mv64xxx_i2c adapter                     I2C adapter
i2c-2   i2c             mv64xxx_i2c adapter                     I2C adapter
i2c-3   i2c             mv64xxx_i2c adapter                     I2C adapter
i2c-4   i2c             mv64xxx_i2c adapter                     I2C adapter

sudo i2cdetect -y 1 returns:
     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
00:                         -- -- -- -- -- -- -- --
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
30: -- -- -- -- -- -- UU -- -- -- -- -- -- -- -- --
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
70: -- -- -- -- -- -- -- --

Here's a picture of the display:

Here's a picture of the pin layout:

VCC is going to 3.3v, GND to GND, SDA to pin 3, and SCK to pin 5

Thanks!

Feel free to ask for more details!

It should have A40I CPU, like the M2 Ultra (which is actually supported)