All Activity

Use Armbian Imager to create SDcard with curent Release. Connect HDMI Monitor and USB Keyboard. Put Sdcard into sdcard Slot and Power the Box. Follow instruction on Monitor

I ran memtester and found memorie errors, which is probably the cause of the problem I report med earlies. Hopefully this can be solved by changing voltage er timing settings.

A question from a beginner: how do I install it to use it for the first time? Should I use a flash drive and Rufus, or is there another way? I didn't quite understand, and I couldn't find any clear information.

Let me know. I had hopes the commiter would provide upstreaming effort proof but nothing there yet.

For a start it looks like you are wiring to spi0 and so fragment0 does not make sense. It also might be causing the pa14 pin problem as the op1 does not have an spi1. Pin pa14 is used on a uart output. I suggest you get rid of fragment0 and just use armbian-config to enable spi0.

Good find! Will look through that PR more closely this weekend. Thanks.

just wanted to ask, is there any way to recompile the included drivers in the kernel after a kernel update? for instance i built the intel xe and radeon drivers into my kernel when building this image, but the kernel updates from mainline apt seem to overwrite it and the drivers go away. even when dkms installed.

That's very useful. I'm nowhere near as practiced with this, so it'll take some time to digest and plan a way forward. It does fit with what seemed to be the case, though: it's device-level issues. I'll start poking around in the specific device differences and see what shows. The great hint you've found is that this is likely affecting all CSI cameras, not just the IMX708. That's most useful. I'm not at all worried about networkmanager, because the only tweak I made in the custom build was to use systemd-networkd, which (for me, anyway) is more straightforward for embedded/minimal/CLI usage. What I haven't yet done, and probably should, is switch to debugging this in something more vanilla, like a Pi 4. At least then I can compile libcamera and friends directly on the device. The Zero 2W should be the same -- he says, hopefully.

Greetings ### [Follow-up Update] Boot Deep-Dive via Cubie-A5E DTB Masking Following up on my previous boot freeze post, I (with some assistance from Gemini - who formatted this post) managed to force the Armbian kernel to initialize by masking the sister chip profile (`sun55i-a523-cubie-a5e.dtb`) over the broken `sun55i-t527-orangepi-4a.dtb` target and injecting `clk_ignore_unused` / `irqpoll` parameters. This got us past the initial handoff hang and successfully spawned the 8-core CPU array initialization and initramfs launch (`Run /init as init process`), but the system eventually hit a permanent deadlock during the device probe phase. I don't think I can get this to go any further without some many hours spent looking at how these things work and its currently 35 degrees C here in the UK so time for a beer methinks! #### Full Boot Log Paste Link: - this is the log before using irqpoll parameter (which eventually caused a deadlock) - I can post the irqpoll logs although i wouldn't have thought irqpolling is the way to go ? https://pastebin.com/TvxTxdbp ### Either way - having just read that this post refers to irqpoll then this is the boot logfile with irqpoll added an an extraparm https://pastebin.com/TNS3DDTC #### Key Technical Takeaways from the Log Dump: 1. **PMIC / I2C Communication Failures:** The kernel initializes the AXP717 and AXP323 power chips but encounters standard timeout errors right away: ```text axp20x-i2c 0-0034: AXP20x variant AXP717 found axp20x-i2c 0-0034: Failed to set masks in 0x40: -6 axp20x-i2c 0-0034: failed to add irq chip: -6 ``` 2. **MMC / Storage Controller Deadlock:** Because the AXP717 framework drops out and the Cubie pin definitions do not line up with the Orange Pi 4A's physical board wiring, the kernel enters an endless loop waiting for internal voltage rails (`cldo3` and `bldo1`) to power up the storage controller: ```text platform 4020000.mmc: deferred probe pending: platform: wait for supplier /soc/i2c@7081400/pmic@34/regulators/cldo3 platform 4021000.mmc: deferred probe pending: platform: wait for supplier /soc/i2c@7081400/pmic@34/regulators/bldo1 ``` This prevents the storage device slot from spinning up, trapping the system right as it attempts to mount the root filesystem. Hopefully this helps isolate the unaligned power configuration loops and clock tables in the current `armbian-imager` source profile for the OPi 4A!

Kraid is a new Rust-based compiler for Panfrost that replaces the aging Bifrost-rooted compiler stack with a cleaner, more flexible design for modern Mali GPUs, improving IR structure, register allocation, hardware testing, and long-term maintainability. View the full article

Greetings - just investigating an issue with the opi-4a Armbian 26.8.0 minimal (edge 7.0.12) build - not getting past starting kernel. The board has a T527 - Hopefully this information is useful ? ### [Bug Report] Orange Pi 4A - Silent Hang at 'Starting kernel ...' (Trixie Minimal) **Board:** Orange Pi 4A (Allwinner A523/T527) **Image used:** Debian Trixie Minimal (Built via armbian-imager) **Installation Media:** SD Card (Class 10) **Log Type:** UART Serial Console Output (115200 baud) --- #### Description of Issue The recent community build of Debian Trixie Minimal for the Orange Pi 4A successfully clears the U-Boot / SPL stages, loads the Ramdisk and DTB from the SD card, but hangs completely silently immediately after hitting `Starting kernel ...`. The onboard status LED remains solid red with no flashing activity. #### The Technical Root Cause Looking closely at the UART initialization text, there appears to be a mismatch between the SoC detected by the low-level firmware and the Device Tree Blob (DTB) loaded by the Armbian boot script: 1. **Firmware/U-Boot Chip Detection:** TF-A and U-Boot explicitly identify the SoC as an **Allwinner A523**: ```text NOTICE: BL31: Detected Allwinner A523 SoC (1890) CPU: Allwinner A523 (SUN55I) ``` 2. **Script DTB Selection:** Immediately afterward, the automated script loads a **T527 DTB** profile: ```text Load fdt: /dtb/allwinner/sun55i-t527-orangepi-4a.dtb ``` Because the kernel tries to initialize the primary power rails and clock gates using a T527 map on an A523 layout, the CPU locks up silently at the execution handoff. --- #### Complete Boot Log (Up to the Hang) ```text U-Boot SPL 2026.01_armbian-2026.01-S127a-P60fe-Hc6a9-Vf757-Bd0d2-R448a (May 30 2026 - 05:53:33 +0000) DRAM: 2048 MiB Trying to boot from MMC1 NOTICE: BL31: v2.13.0(debug):armbian NOTICE: BL31: Built : 05:52:43, May 30 2026 NOTICE: BL31: Detected Allwinner A523 SoC (1890) NOTICE: BL31: Found U-Boot DTB at 0xa0b8ac0, model: OrangePi 4A 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 U-Boot 2026.01_armbian-2026.01-S127a-P60fe-Hc6a9-Vf757-Bd0d2-R448a (May 30 2026 - 05:53:33 +0000) Allwinner Technology CPU: Allwinner A523 (SUN55I) Model: OrangePi 4A DRAM: 2 GiB sunxi_set_gate: (CLK#35) unhandled Core: 94 devices, 24 uclasses, devicetree: separate WDT: Not starting watchdog@2050000 MMC: mmc@4020000: 0, mmc@4021000: 2, mmc@4022000: 1 Loading Environment from FAT... Unable to read "uboot.env" from mmc0:1... In: serial@2500000 Out: serial@2500000 Err: serial@2500000 Net: No ethernet found. starting USB... 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: 2 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: Failed to get switch-sel GPIO: -2 PCIe: Hardware init failed with error -2 Device 0: unknown device switch to partitions #0, OK mmc0 is current device Scanning mmc 0:1... Found U-Boot script /boot.scr 4641 bytes read in 2 ms (2.2 MiB/s) ## Executing script at 4fc00000 U-boot loaded from SD Boot script loaded from mmc 249 bytes read in 2 ms (121.1 KiB/s) Load fdt: /dtb/allwinner/sun55i-t527-orangepi-4a.dtb 33383 bytes read in 7 ms (4.5 MiB/s) Working FDT set to 4fa00000 Failed to load '/dtb/allwinner/overlay/sun55i-t527-fixup.scr' 16748327 bytes read in 814 ms (19.6 MiB/s) 41171456 bytes read in 1707 ms (23 MiB/s) Moving Image from 0x40080000 to 0x40200000, end=0x42a30000 ## Loading init Ramdisk from Legacy Image at 4ff00000 ... Image Name: uInitrd Image Type: AArch64 Linux RAMDisk Image (gzip compressed) Data Size: 16748263 Bytes = 16 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 49007000, end 49fffee7 ... OK Loading Device Tree to 0000000048f96000, end 0000000049006fff ... OK Working FDT set to 48f96000 Starting kernel ... ```

NEWS! I got Mali450 on kodi! I compiled my kodi version with the dockerfile attached. About the acceleration, quoting Claude: EDIT: to make KODI working just set Settings → Player → Videos → Render method → Direct to plane Dockerfile.cross

I usually make a quick backup before running bigger updates, especially on systems that are already working well. It also helps to reboot after the update and check armbianmonitor -u if anything seems off afterward. That can provide useful information if you need to troubleshoot.

It seems the DC port is malfunctioning. This type of board can run with both power port and the USB although I prefer the DC port because it may provider more power. You can try replacing the DC jack (5.5x2.1) or check somewhere near it, there may be issues with the power IC. Yeah currently it cannot dual boot Android and Armbian. To install Armbian, you must install the custom U-boot. Can you post the image of your board and your RKDevTool setting?

Hello experts and members, Any possibility of multi booting armbian via petitboot from microsd card or usb or emmc in odroid n2 among other OSs.

A quick diff scan: 'kompare config-6.18.34+rpt-rpi-v8 config-6.18.35-current-bcm2711' about 700 differences, no clue if this is reason for no detection. I made Debian Sid running, currently kernel 7.0.13+deb14-arm64, cam -l finds no CSI cameras, simple USBcam works fine. But is upstream_kernel=1 and there is no overlays for CSI cameras. Then copied 6.18.34+rpt-rpi-v8 kernel+initrd+dtb(o)+firmware from a running latest RPi Trixie (so 64-bit Debian based, not Raspbian re-compiled for armv6) and commented config.txt line upstream_kernel=1 and also set console to ttyS0, not ttyS1 otherwise hang at serial console. So with waveshareH NoIR (=ov5647 sensor) attached: 'cam -c 1 -C1 --file=raspicam.jpg' run as root works, however the picture is just black and white vertical lines. Then swap 6.18.34+rpt-rpi-v8 kernel+initrd+dtb(o) with the ones from 6.18.35-current-bcm2711: cam -l does not see a camera although ov5647 overlay is loaded If I use a faulty configuration, like upstream_kernel=1 the ov5647 overlay is loaded, but fails to initilize due to some i2c-csi-dsi mismatch. So it seems a typical vendor/downstream works, but upstream not. At least for upstream, the camera/sensor needs to be created and in addition, userspace might need changes. Might not only be in libcamera/rpicam, but there are potentially 10s or 100s or more changed debian packages, the most obvious 1 is NetworkManager, see RPi forum.

Hi ! I have a FriendlyElec NanoPi M5 and I want to play movies with it. But I want to squeeze everything out of this SBC ! So, I need hardware acceleration. I tested first with a OS image downloaded from FriendlyElec and mpv and (almost) everything works well. The mpv working configuration is: hwdec=rkmpp, vo=gpu, gpu-api=opengl. But I don't like that OS for other reasons, so I switched to Armbian. I installed the image "Armbian 26.5.1 KDE Wayland (Ubuntu 26.04 - vendor 6.1.115)", then I installed mpv, but when I try to play movies, it says: marus@nanopi-m5:/mnt/NAS/WDRed1/Samples/FullHD$ mpv --hwdec=rkmpp --vo=gpu --gpu-api=opengl H265.8bit.FullHD.1920x816.24fps.10Mbps.SDR.mkv ● Video --vid=1 --vlang=eng 'Carlito's Way 1993' (hevc 1920x816 23.976 fps) [default] ● Audio --aid=1 --alang=eng 'DDP 5.1 ch 640 Kb/s' (eac3 6ch 48000 Hz) [default] Unsupported hwdec: rkmpp AO: [pipewire] 48000Hz 5.1(side) 6ch floatp VO: [gpu] 1920x816 yuv420p AV: 00:00:14 / 00:01:59 (12%) A-V: 0.000 Cache: 104s/146MB Exiting... (Quit) It seems that this mpv doesn't know about rkmpp's existence... Strange ! What can I do ? Has anyone managed to play movies with mpv and full hardware acceleration on NanoPi M5 and Armbian OS?

Need to sync tags and boards at some point again...or hopefully this will work automatically at some point. Anyway, try https://github.com/armbian/build/pull/9796

Just got a ODroid M2 to play with an during initial benchmarking, noticed some weird results. I don't see an M2 specific forum, so @Werner, please move as necessary! Anyway, always interested in crypto throughput, and ARM64 crypto extensions have always put up some good results. So, a little weird when I saw that AES XTS performance seems decent, but CBC seems awful? user@odroidm2:~$ /sbin/cryptsetup benchmark aes-cbc 128b 178.5 MiB/s 162.7 MiB/s aes-cbc 256b 135.0 MiB/s 211.3 MiB/s aes-xts 256b 1399.5 MiB/s 1407.2 MiB/s aes-xts 512b 1186.7 MiB/s 1198.7 MiB/s Checking /proc/crypto seems to indicate that rk_crypto2 is being used, so on a whim, I tried doing this: user@odroidm2:~$ sudo rmmod rk_crypto2 [sudo] password for user: user@odroidm2:~$ /sbin/cryptsetup benchmark aes-cbc 128b 880.4 MiB/s 1722.3 MiB/s aes-cbc 256b 755.8 MiB/s 1247.9 MiB/s aes-xts 256b 1225.2 MiB/s 1422.5 MiB/s aes-xts 512b 1088.9 MiB/s 1123.7 MiB/s Huh. XTS speed is about the same, but CBC is an order of magnitude faster? Might not even be worth using it? Anyway, before I go digging, just curious if anyone's seen this or can reproduce on a Rockchip other than an RK3588S2? Logs from Armbian 26.2.1 (noble/current) -> https://paste.armbian.com/mudojesajo

@chaitan3 @Alex Ling Enable 1 GHz frequency for Panthor on mainline patch https://github.com/armbian/build/pull/10035

OK so the fix is working'ish. Unique problem, well more of an inconvenience, with sound. I applied the fix and works. I run, systemctl --user restart pipewire wireplumber pulseaudio and it system sounds working! Then I open Chromium and it won't play and says I need to restart my device... just a spinning circle. So while Chromium is still open I run, systemctl --user restart pipewire wireplumber pulseaudio again and the video plays and I have sound! Until I pause the video or watch a new video. The I have to run systemctl --user restart pipewire wireplumber pulseaudio AGAIN. Any ideas?

@li20034 just a reply in general. I had no issues with this method after updating to the latest on 6/20/26. Wondering if there is something I may have installed that would have made it work for me?

I managed to download an old image from a torrent archive found in a Reddit thread, where the author mentioned that Armbian was running on the Retroid Flip 2. I flashed the image: Armbian_community_26.2.0-trunk.162_Retroidpocket-rp5_noble_current_6.12.63_gnome_desktop.img However, I encountered the same error. It’s possible that something has changed in the newer console revisions or in the new bootloader.

I'm trying to connect Nokia 5110 / PCD8544 LCD to my Orange Pi One H3 (Board v1.1). This is my wiring: Connection (LCD to OPi) Nokia 5110 LCD pin Orange Pi One pin GND GND LIGHT GND VCC 3.3v CLK PC2 (CLK) DIN PC0 (MOSI) DC PA6 CE PC3 (CE) RST PA9 This is my LCD: The backlight is working upon turning on OPi One. The official Orange Pi One H3 manual suggests using fbtft_device kernel module, which is LONG deprecated and no longer supported. On Raspberry Pi forums, someone was suggested to use a Device Tree Overlay instead. I've stumbled upon an Orange Pi Zero overlay file for my LCD. So I've changed a few lines: /dts-v1/; /plugin/; / { compatible = "allwinner,sun8i-h3"; fragment@0 { target = <&spi1>; __overlay__ { status = "okay"; spidev@0{ status = "disabled"; }; spidev@1{ status = "disabled"; }; }; }; fragment@1 { target = <&pio>; __overlay__ { opiz_display_pins: opiz_display_pins { pins = "PA9", "PA6"; function = "gpio_out"; }; }; }; fragment@2 { target = <&spi1>; __overlay__ { /* needed to avoid dtc warning */ #address-cells = <1>; #size-cells = <0>; opizdisplay: opiz-display@0{ compatible = "philips,pcd8544"; reg = <0>; pinctrl-names = "default"; pinctrl-0 = <&opiz_display_pins>; spi-max-frequency = <400000>; fps = <30>; buswidth = <8>; reset-gpios = <&pio 0 33 1>; dc-gpios = <&pio 0 7 0>; }; }; }; }; And compiled, loaded it into an DTS user directory. I've connected Arduino as a Serial-to-USB convertor to OPi and it would seem it has loaded successfully: Applying user provided DT overlay nokia5110opizero.dtbo 4185 bytes read in 14 ms (291 KiB/s) Applying kernel provided DT fixup script (sun8i-h3-fixup.scr) ## Executing script at 45000000 Kernel image @ 0x42000000 [ 0x000000 - 0xa0ea90 ] ## Loading init Ramdisk from Legacy Image at 43400000 ... Image Name: uInitrd Image Type: ARM Linux RAMDisk Image (gzip compressed) Data Size: 17670074 Bytes = 16.9 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 43000000 Booting using the fdt blob at 0x43000000 Working FDT set to 43000000 Loading Ramdisk to 48f26000, end 49ffffba ... OK Loading Device Tree to 48eb5000, end 48f25fff ... OK Working FDT set to 48eb5000 But according to armbianmonitor -u output , the overlay ends up creating new errors: [ 1.630221] sun8i-h3-pinctrl 1c20800.pinctrl: pin PA14 already requested by 1c28c00.serial; cannot claim for 1c69000.spi [ 1.630250] sun8i-h3-pinctrl 1c20800.pinctrl: error -EINVAL: pin-14 (1c69000.spi) [ 1.630269] sun8i-h3-pinctrl 1c20800.pinctrl: error -EINVAL: could not request pin 14 (PA14) from group PA14 on device 1c20800.pinctrl [ 1.630288] sun6i-spi 1c69000.spi: Error applying setting, reverse things back I know the overlay is for Zero series, but i figured it should be the same since H3 is mentioned in there. Or at least I would be glad to know how to modify this for my board. Attached below are both logs for Serial and the kernel. So far my goal is display anything, even a black square, on the screen. Would be sick to use it as a screen for console (like /dev/fb0). Hoping for your help since I'm stuck. Thanks in advance! dmesg.txt serial.txt

Checking in on Armbian, the installed raspi-firmware is 1.20250915-1~bookworm: $ apt list -a raspi-firmware raspi-firmware/trixie,trixie,now 1:1.20250915-1~bookworm all [installed] raspi-firmware/trixie,trixie 1:1.20250430-4~bookworm all raspi-firmware/trixie,trixie 1:1.20250430-3 all raspi-firmware/trixie,trixie 1:1.20250430-1 all raspi-firmware/stable 1.20240424+ds-6 all I do note there were upstream issues in this: https://github.com/raspberrypi/linux/issues/6753, but that does not 100% match, as we do not get the logs that imply that cause. And the hashes: $ shasum /boot/firmware/bootcode.bin fa4cd59207022a61a2cc645b6dfdf1d481bba07b /boot/firmware/bootcode.bin $ shasum /boot/firmware/start.elf bbd038d812d408c209005c9f8c2801ef1affc501 /boot/firmware/start.elf $ shasum /boot/firmware/fixup.dat 75e5543a3834b3fec1c9f598e2e9e9ae13e5b334 /boot/firmware/fixup.dat Latest Raspbian is using newer firmware: $ apt list -a raspi-firmware raspi-firmware/stable,stable,now 1:1.20260521-3 all [installed] raspi-firmware/stable,stable 1.20240424+ds-6 all And the Raspbian files are all different. Maybe I should try the Ubuntu Armbian and/or a minimal sid build and see how they play out.