All Activity

Automation, not guys And they it can't be quicker then others elsewhere. Armbian adds a value on top of this. We have our EDGE kernels attached to latest mainline with additional stuff from Collabora and additional stuff from our own work. They are released daily in beta channels, which here doesn't have any fancy name (rawhide). https://github.com/armbian/build/blob/main/config/sources/families/include/rockchip64_common.inc#L36 https://github.com/armbian/build/blob/main/config/sources/mainline-kernel.conf.sh#L7-L14

I moved them to production already as I got another report they are working - so they are the same, but also community build images are mixed with those links ... this needs to be fixed eventually. Thank you for comprehensive testings. Here is image for 2w if anyone have it laying around: https://fi.mirror.armbian.de/incoming/igorpecovnik/orangepizero2w/archive/

Hello again, I am struggling to install armbian on my H96Max (blue PCB RK3318_V1.4, 4G/64G). The Armbian_22.11.0-trunk_Rk3318-box_bullseye_edge_5.19.15_minimal.img image works OK (at least for the display). All the new images fail to initialise the display (a 4K HDMI monitor), either using *_minimal.img or *_gnome_desktop.img I managed to install the latest (Armbian_community_25.8.0-trunk.8_Rk3318-box_noble_current_6.12.28_gnome_desktop.img) image using the serial console. Kernel is 6.12.28 I can now connect using ssh on ethernet (the WIFI does not work yet...) I get in syslog and dmesg a LOT of the following errors: [ 2683.281403] ------------[ cut here ]------------ [ 2683.281441] [CRTC:38:crtc-0] vblank wait timed out [ 2683.281570] WARNING: CPU: 1 PID: 50 at drivers/gpu/drm/drm_atomic_helper.c:1682 drm_atomic_helper_wait_for_vblanks.part.0+0x238/0x25c [ 2683.281629] Modules linked in: cfg80211 rfcomm algif_hash algif_skcipher af_alg bnep sunrpc snd_soc_hdmi_codec hci_uart btqca hantro_vpu btrtl btintel crct10dif_ce rockchip_vdec(C) v4l2_jpeg v4l2_vp9 btbcm rockchip_rga v4l2_h264 bluetooth videobuf2_dma_contig snd_soc_spdif_tx gpio_ir_recv videobuf2_dma_sg rc_core v4l2_mem2mem rfkill videobuf2_memops videobuf2_v4l2 dw_hdmi_i2s_audio videodev dw_hdmi_cec lima snd_soc_simple_card videobuf2_common snd_soc_rockchip_spdif snd_soc_rockchip_i2s snd_soc_rk3328 snd_soc_simple_card_utils gpu_sched drm_shmem_helper mc snd_soc_core rk_crypto snd_compress rng_core snd_pcm_dmaengine snd_pcm snd_timer snd soundcore cpufreq_dt joydev zram zsmalloc binfmt_misc sch_fq_codel dm_mod autofs4 dwmac_rk stmmac_platform stmmac pcs_xpcs nvmem_rockchip_efuse rockchipdrm dw_hdmi_qp gpio_syscon dw_hdmi cec dw_mipi_dsi analogix_dp drm_display_helper adc_keys [ 2683.282340] CPU: 1 UID: 0 PID: 50 Comm: kworker/u16:2 Tainted: G B WC 6.12.28-current-rockchip64 #1 [ 2683.282375] Tainted: [B]=BAD_PAGE, [W]=WARN, [C]=CRAP [ 2683.282389] Hardware name: Rockchip RK3318 BOX (DT) [ 2683.282409] Workqueue: events_unbound commit_work [ 2683.282446] pstate: 60000005 (nZCv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--) [ 2683.282471] pc : drm_atomic_helper_wait_for_vblanks.part.0+0x238/0x25c [ 2683.282499] lr : drm_atomic_helper_wait_for_vblanks.part.0+0x238/0x25c [ 2683.282531] sp : ffff8000809dbcb0 [ 2683.282542] x29: ffff8000809dbce0 x28: 00000000000007d5 x27: 0000000000000000 [ 2683.282580] x26: 0000000000000001 x25: 0000000000000000 x24: ffff6d33cdf68000 [ 2683.282616] x23: 0000000000000001 x22: 0000000000000000 x21: ffff6d33cc6f6280 [ 2683.282654] x20: ffff6d33cdf70080 x19: 0000000000000000 x18: ffffffffffffffff [ 2683.282691] x17: 000000040044ffff x16: 00500072b5503510 x15: ffff8000809db860 [ 2683.282727] x14: 00000000ffffffea x13: ffff8000809db9f8 x12: ffffd4f64aa4ac10 [ 2683.282768] x11: 0000000000032030 x10: 0000000000031fe0 x9 : 0000000000024330 [ 2683.282805] x8 : c0000000fffff822 x7 : ffffd4f64a99aa18 x6 : 0000000000084bb0 [ 2683.282842] x5 : ffff6d34be7424c8 x4 : 0000000000000000 x3 : 0000000000000027 [ 2683.282878] x2 : 0000000000000000 x1 : 0000000000000000 x0 : ffff6d33c4c4c600 [ 2683.282918] Call trace: [ 2683.282932] drm_atomic_helper_wait_for_vblanks.part.0+0x238/0x25c [ 2683.282962] drm_atomic_helper_commit_tail_rpm+0x84/0xa0 [ 2683.282992] commit_tail+0xa4/0x18c [ 2683.283019] commit_work+0x14/0x20 [ 2683.283043] process_one_work+0x16c/0x3e4 [ 2683.283073] worker_thread+0x2d0/0x3d8 [ 2683.283097] kthread+0x10c/0x110 [ 2683.283123] ret_from_fork+0x10/0x20 [ 2683.283151] ---[ end trace 0000000000000000 ]--- This seems to come from the accelerated graphic driver. The corresponding function can be seen there: drm_atomic_helper.c This function waits for receiving a vertical blanking pulse that never comes, so the warning at line 1679 is triggered. I don't intend to do hard-core graphics so I don't care about graphic performance. In fact this lovely box will be used for hosting a headless server. Is there a way to use a legacy or un-accelerated graphic driver? If not, how could I remove entirely the graphic subsystem and use only character mode? Thanks! Michel EDIT: In fact the first warning occurs when switching to the colour frame buffer device: ... rk_gmac-dwmac ff550000.ethernet: Enable RX Mitigation via HW Watchdog Timer May 29 19:00:08 h96max kernel: rk_gmac-dwmac ff550000.ethernet: device MAC address de:10:75:60:c0:cb May 29 19:00:08 h96max kernel: Console: switching to colour frame buffer device 160x45 May 29 19:00:08 h96max kernel: ------------[ cut here ]------------ May 29 19:00:08 h96max kernel: [CRTC:38:crtc-0] vblank wait timed out May 29 19:00:08 h96max kernel: WARNING: CPU: 0 PID: 74 at drivers/gpu/drm/drm_atomic_helper.c:1682 drm_atomic_helper_wait_for_vblanks.part.0+0x238/0x25c May 29 19:00:08 h96max kernel: Modules linked in: dwmac_rk stmmac_platform stmmac pcs_xpcs nvmem_rockchip_efuse gpio_syscon rockchipdrm dw_hdmi_qp dw_hdmi cec dw_mipi_dsi analogix_dp drm_display_helper adc_keys May 29 19:00:08 h96max kernel: CPU: 0 UID: 0 PID: 74 Comm: kworker/u16:5 Tainted: G B 6.12.28-current-rockchip64 #1 May 29 19:00:08 h96max kernel: Tainted: [B]=BAD_PAGE ... So I suspect that not switching to a FB could solve my problem

👍 Thanks!

sun50i-h616-spidev1_1.dtso /dts-v1/; /plugin/; / { compatible = "allwinner,sun50i-h616"; fragment@0 { target-path = "/aliases"; __overlay__ { spi1 = "/soc/spi@5011000"; }; }; fragment@1 { target = <&spi1>; __overlay__ { status = "okay"; #address-cells = <1>; #size-cells = <0>; pinctrl-names = "default"; pinctrl-0 = <&spi1_pins>,<&spi1_cs1_pin>; spidev1_1: spidev@1 { compatible = "armbian,spi-dev"; status = "okay"; reg = <1>; spi-max-frequency = <1000000>; }; }; }; };

Great news and thank you for reporting back. Do you have any idea what they changed or where they host their sources so we can have a look? There is for example this. There is another user who reported running into problems that sounded a lot like yours.

Hi, wake-on-lan should be working now due to https://github.com/armbian/build/pull/8235. Groetjes,

fixed

@Igor Armbian_25.5.1_Orangepizero3_bookworm_current_6.12.23_mi nimal.img.xz below is transcript from the 'debug uart (serial)' console, via a usb-uart dongle, it is the only way to boot up with a console , if network etc is not available. U-Boot 2024.01-armbian-2024.01-S866c-P4a40-H8869-V3d5b-Bb703-R448a (May 28 2025 - 02:53:19 +0000) Allwinner Technology CPU: Allwinner H616 (SUN50I) Model: OrangePi Zero3 DRAM: 1.5 GiB Core: 57 devices, 25 uclasses, devicetree: separate WDT: Not starting watchdog@30090a0 MMC: mmc@4020000: 0 Loading Environment from FAT... Unable to use mmc 0:1... .... _ _ _ /_\ _ _ _ __ | |__(_)__ _ _ _ / _ \| '_| ' \| '_ \ / _` | ' \ /_/ \_\_| |_|_|_|_.__/_\__,_|_||_| v25.5.1 for Orange Pi Zero3 running Armbian Linux 6.12.23-current-sunxi64 Packages: Debian stable (bookworm) Updates: Kernel upgrade enabled and 23 packages available for upgrade Support: DIY (community maintained) IPv4: (LAN) 192.168.xxx.xxx (WAN) xxx.xxx.xxx.xxx IPv6: fd00:xxxx:xxxxx, xxxxx (WAN) xxxx Performance: Load: 18% Up time: 2 min Memory usage: 9% of 1.44G CPU temp: 50°C Usage of /: 9% of 15G Commands: Configuration : armbian-config Upgrade : armbian-upgrade Monitoring : htop root@orangepizero3:~# ping google.com PING google.com (142.250.4.138) 56(84) bytes of data. 64 bytes from sm-in-f138.1e100.net (142.250.4.138): icmp_seq=1 ttl=100 time=2.77 ms 64 bytes from sm-in-f138.1e100.net (142.250.4.138): icmp_seq=2 ttl=100 time=2.79 ms ^ ethernet works root@orangepizero3:~# ip link set wlan0 up root@orangepizero3:~# iw dev wlan0 scan BSS xxxxx freq: 24xx signal: -77 dBm ^ wifi works, at least for scanning for stations, connect and AP not yet tested ^ the above is booted up on a 'rare' 1.5GB board. repeat using the same uSD card on a 4 GB board, initially the debug usb-uart console is garbled, it seemed to be a baud rate mismatch, I'm not sure why, but after a few retry it works. Perhaps it is due to bad wires. U-Boot 2024.01-armbian-2024.01-S866c-P4a40-H8869-V3d5b-Bb703-R448a (May 28 2025 - 02:53:19 +0000) Allwinner Technology CPU: Allwinner H616 (SUN50I) Model: OrangePi Zero3 DRAM: 4 GiB Core: 57 devices, 25 uclasses, devicetree: separate WDT: Not starting watchdog@30090a0 MMC: mmc@4020000: 0 Loading Environment from FAT... Unable to use mmc 0:1... ... _ _ _ /_\ _ _ _ __ | |__(_)__ _ _ _ / _ \| '_| ' \| '_ \ / _` | ' \ /_/ \_\_| |_|_|_|_.__/_\__,_|_||_| v25.5.1 for Orange Pi Zero3 running Armbian Linux 6.12.23-current-sunxi64 Packages: Debian stable (bookworm) Updates: Kernel upgrade enabled and 23 packages available for upgrade Support: DIY (community maintained) IPv4: (LAN) 192.168.xxx.xxx (WAN) xxx.xxx.xxx.xxx IPv6: fd00:xxxx:xxxxx, xxxxxxxx (WAN) xxxxxxxx Performance: Load: 12% Up time: 1 min Memory usage: 3% of 3.83G CPU temp: 46°C Usage of /: 9% of 15G Commands: Configuration : armbian-config Upgrade : armbian-upgrade Monitoring : htop root@orangepizero3:~# ping google.com PING google.com (142.251.12.139) 56(84) bytes of data. 64 bytes from se-in-f139.1e100.net (142.251.12.139): icmp_seq=1 ttl=103 time=2.69 ms 64 bytes from se-in-f139.1e100.net (142.251.12.139): icmp_seq=2 ttl=103 time=2.99 ms ^ ethernet works root@orangepizero3:~# ip link set wlan0 up root@orangepizero3:~# iw dev wlan0 scan BSS xxxxxx(on wlan0) freq: 24xx signal: -78.00 dBm ^ wifi works for scan, connect and AP not tested I'm not too sure what is the difference between v25.5.1 vs that on the boards page? https://www.armbian.com/orange-pi-zero-3/ from those links 'current' seemed to be linked to: as of current 28 May 2025 Armbian_community_25.8.0-trunk.8_Orangepizero3_bookworm_current_6.12.23_minimal.img.xz btw thanks much (to all contributors) for updating Armbian to 25.x for OrangePi Zero 3 (and likely means works for Zero 2W) as well. oh frequency scaling works as well, this is on the 4GB board root@orangepizero3:~# armbianmonitor -m Stop monitoring using [ctrl]-[c] Time CPU load %cpu %sys %usr %nice %io %irq Tcpu C.St. 01:43:36 1416 MHz 0.00 1% 0% 0% 0% 0% 0% 47.2 °C 0/7 01:43:41 480 MHz 0.00 0% 0% 0% 0% 0% 0% 47.2 °C 0/7 01:43:46 480 MHz 0.00 0% 0% 0% 0% 0% 0% 47.4 °C 0/7 01:43:51 480 MHz 0.00 0% 0% 0% 0% 0% 0% 47.0 °C 0/7 'everyone' should just get the 4GB board, make it a 'standard' lol @TRay It is a good idea to try U-Boot v2025.04 I've got a python script which can patch u-boot binary into an Armbian .img or practically any other image file (though i've only tested this in *unofficial* armbian builds) https://github.com/ag88/1.5GB_Fix_for_Armbian_on_OrangePiZero3/tree/main/tools https://github.com/ag88/1.5GB_Fix_for_Armbian_on_OrangePiZero3 i created it back then while researching solutions for the '1.5GB' problem back then. Do you have the 'bin' file for u-boot that you could share say in a zip file attached here? you can extract that 'bin' file using the 'backup' procedure documented here: https://github.com/ag88/1.5GB_Fix_for_Armbian_on_OrangePiZero3?tab=readme-ov-file#how-to-use sudo dd if=/dev/sdX of=u-boot-backup.bin bs=1024 skip=8 count=1024 But that the appropriate way would be to build the full armbian image from source including u-boot etc. Nevertheless, having the 'patched' u-boot binary would enable most here to test that by patching a distributed image file e.g. from the boards page, or from the 'test images' link as Igor has provided.

Yes I stalkered Sipeed on X social (ex Twitter), and finally they compiled a new Debian Bookworm with support for lot of USB -> converter so I'm using to control a 3D Printer. But I'll not buy this product anymore.

After cleaning up and expanding Whisper-Hindi to 3,000 hours, we now have explicit timestamp prediction, faster I/O, and fine-tuned models across all sizes, bringing us even closer to fully reliable, production-ready Hindi ASR. View the full article

Looks like most of the mainline issues will be resolved with the release of Kernel 6.16 rc1 which will hopefully be in the nest couple of weeks. I'm running Fedora rawhide with 6.15 rc7 and the only thing I'm missing is analog sound which collabora says should be in 6.16 rc1. I have dual monitors, sound over hdmi so the last biggy for me is analog sound. The reason I'm running Fedora is theses guys are pretty guick to release the latest mainline kernel.

I use the ArmBian version which is updated very often (see below) so if U-Boot v2025.04 for OZPI v3 appears in the current updates it will be possible to check and other users who have OZPI v3 with 1,1.5, 2, or 4 Gb RAM check it

Thanks Igor for your work!

Thank you for that information, @Mechano. Did you ever get this board to work, with armbian or another image?

looks like a really cool machine. unfortunately, no maintainer in armbian and I am not aware if any of the regular developpers has that SBC. It seems to be based on the H618 which it shares with the Orange Pi Zero3 which is reported working with the latest Armbian release. Did this board ever work with an older release? Is this a regression? I see somebody else mentioning they have issues with the board booting, , apparently due to issues with thermal management. And your crash apparently started in pstate.

I am also available for testing new images on Orange Pi Zero 3, while I am new to this SBC I am happy to learn. Today I have installed "Armbian_community_25.8.0-trunk.38_Orangepizero3_bookworm_current_6.12.23_minimal.img" to use for NTP server purposes. I have successfully enabled uart5 by using "overlays=uart5" and seeing GPS data with "gpsmon /dev/ttyS1". However, I also want to use PPS signal coming from my Waveshare L76K module, and the pps device does not seem to be created. I have used the following dts, from this forum: /dts-v1/; /plugin/; / { compatible = "allwinner,sun50i-h616"; fragment@0 { target = <&pio>; __overlay__ { pps_pins: pps_pins { pins = "PC7"; function = "gpio_in"; }; }; }; fragment@1 { target-path = "/"; __overlay__ { pps@0 { compatible = "pps-gpio"; pinctrl-names = "default"; /* pinctrl-0 = <&pps_pins>; */ gpios = <&pio 2 7 0>; /* PC7 */ status = "okay"; }; }; }; }; Then I did "armbian-add-overlay sun50i-h616-pps-gpio.dts" followed by a reboot. Then I do not see any PPS device. Am I missing something else?

Nice. To help other users of the forum, it would be good if you shared what fixed the issue.

To be honest, I'm confused. You reference three different systems and it is unclear to me which one it is that FTBFS for you. Let's take a step back. Do you have the latest git tree of armbian/build? Do you have any local changes? What is the exact command you for compile.sh? I will try to reproduce the problem here.

Sparking between the wires on the poles produces high-frequency pulses of high power and transmits them through the wires to consumers of electricity. Household consumers such as a TV, vacuum cleaner, refrigerator do not have a built-in high-frequency protection filter and very often fail. As for the orange, it is not protected at all. My orange was just lying on the table and was connected by an Ethernet cable to the router. Both were not power up. Lightning struck a nearby building. The Ethernet cable caught an electromagnetic pulse. The orange burned down completely and the router has only 1 port damaged. You can draw your own conclusions.

Either ignore expired cert or wait until we fixed it.

Providing logs with armbianmonitor -u helps with troubleshooting and significantly raises chances that issue gets addressed.

Trying to update Armbian_community_25.8.0-trunk.38_Radxa-zero3_bookworm_vendor_6.1.115_minimal got a problem with beta.armbian.com's certificate: Err :6 https://beta.armbian.com bookworm InRelease Certificate verification failed: The certificate is NOT trusted. The certificate chain uses expired certificate. Content of /etc/apt/sources.list.d/armbian.sources Types: deb URIs: https://beta.armbian.com Suites: bookworm Components: main bookworm-utils bookworm-desktop Signed-By: /usr/share/keyrings/armbian.gpg Something to do on my side? Denis

I have connected matrix led display on max7219 by spi to orangepi. Module max7219 have power supply from 5v. On some during a 220v power failure (sparking between wires suspended on poles), there were some disruptions in the 5v power supply. This damaged the max7219 modules and possible spi port on orange pi. After this failure, the /boot/armbianEnv.txt file contained a fragment of the logrotate file, the kernel on the orange pi is unable to initialize the spi port despite no wires being connected. After connecting a working orange pi to the max7219 module, the problem with spi initialization also appears. Dmesg does not show anything related to spi, there is no /dev/spi0.0 file. Is it possible that damage to the spi port blocks its initialization by the kernel? There was also a problem with playing music using mpd, after a while the music stops playing and the kernel reports that the sound card is not available. Re-running mpc play resumes playing music, but not for long.

This mode needs 80MHz pixel clock which is not in the table for clk-rk3568.c driver. You need a patch similar to https://lkml.org/lkml/2025/3/18/1337 to add this rate. FWIW 1280x800@63.59Hz isn't a very common mode