Active threads

Greetings to all; For a few hours now, as of today 2025-05-29 1418 North America/Pacific, I have been unable to update apt, receiving the following two error messages: E: Failed to fetch http://beta.armbian.com/dists/bookworm/Contents-armhf File has unexpected size (2085376 != 51213). Mirror sync in progress? [IP: 23.186.113.5 80] E: Failed to fetch http://beta.armbian.com/dists/bookworm/Contents-all File has unexpected size (44878 != 8029). Mirror sync in progress? [IP: 23.186.113.5 80] I suppose it is possible that the "mirror sync" mentioned is taking a very long time, but this seems unlikely to me. Does anyone have any ideas?

@jwillb00 I have a newer build with kernel 6.14. https://github.com/NickAlilovic/build/tree/v20250407

/_\ _ _ _ __ | |__(_)__ _ _ _ / _ \| '_| ' \| '_ \ / _` | ' \ /_/ \_\_| |_|_|_|_.__/_\__,_|_||_| v25.5.1 for Orange Pi Zero2W running Armbian Linux 6.12.23-current-sunxi64 Packages: Ubuntu stable (noble) Updates: Kernel upgrade enabled and 17 packages available for upgrade Support: DIY (community maintained) IPv4: (LAN) 192.168.***.***, 192.168.***.*** (WAN) ***.***.***.*** IPv6: *** Performance: Load: 11% Up time: 4 min Local users: 3 Memory usage: 24% of 1.93G CPU temp: 45°C Usage of /: 10% of 58G Commands: Configuration : armbian-config Upgrade : armbian-upgrade Monitoring : htop orangepi@orangepizero2w:~$ It boots into xfce wifi works, eth works and hdmi work. 1gb board with keyboard plugged into expansion board.

@remolaan I think this is the most current info that may help you:

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

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!

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,

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

Thanks Igor for your work!

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.

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.

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

Thanks both!

Any up to date Armbian image using vendor kernel should include rknpu kernel driver oob. Mainline npu driver is still pending. You can try to backport it. Check rockchip kernel mailing list.

Hi We all started at some point. But overall prepare for some frustration We don't support this device. Support was added via community effort. May work, maybe not. We don't know nor do we track status of such configurations. Regarding OPi5+. It is using - in terms of ARM socs - a fairly recent SoC, the Rockchip RK3588. Mainline support is far from feature-complete. Will take a few additional years to complete. If you need an almost feature-complete kernel, you have to use vendor branch which is based on Rockchip BSP. current (Linux 6.12.y LTS at this time) has basic support for rk3588 and is good enough for general server application, though for your usecase might not be enough. This branch will receive fixes only but no new features. edge may be sufficient. When using some graphics related I suggest to use an image with mesa-vpu extension included. Also there a two ways to make use of it: - We backported the open source Panthor driver into vendor. Can be enabled via device tree overlay (check code { font-family: Consolas,"courier new"; color: crimson; background-color: rgba(0, 0, 0, 0.2); padding: 2px; font-size: 105%; } armbian-config) - Using proprietary mali blobs is also possible. I think Jellyfin has a tutorial how to setup those: https://jellyfin.org/docs/general/post-install/transcoding/hardware-acceleration/rockchip/

I've extracted dtbs from my rooted device bqeel K12, could it be useful share them? @RuDy_74 I've used "Magicsee C400 Plus" dtb (I don't remember the exact name) and I got also wifi and bluetooth working. The only issue is ethernet working at 100Mbit instead of 1Gbit

Still the same with armbian 25.2.3 kernel: 6.12.22-current-rockchip64 #1 SMP PREEMPT Mon Apr 7 08:08:37 UTC 2025 aarch64 aarch64 aarch64 GNU/Linux u-boot-version: # cat /dev/mtd/by-name/U-Boot | strings | grep -B1 "u-boot,version" 2025.01-armbian-2025.01-S6d41-P41ad-H4cab-V390e-Bb703-R448a u-boot,version WARNING: could not set u-boot,version %s. # iperf3 -R -c odroidm1 Connecting to host odroidm1, port 5201 Reverse mode, remote host odroidm1 is sending [ ID] Interval Transfer Bitrate [ 5] 0.00-1.00 sec 79.2 KBytes 649 Kbits/sec [ 5] 1.00-2.00 sec 84.8 KBytes 695 Kbits/sec [ 5] 2.00-3.00 sec 206 KBytes 1.69 Mbits/sec [ 5] 3.00-4.00 sec 228 KBytes 1.87 Mbits/sec [ 5] 4.00-5.00 sec 115 KBytes 938 Kbits/sec [ 5] 5.00-6.00 sec 181 KBytes 1.48 Mbits/sec [ 5] 6.00-7.00 sec 163 KBytes 1.33 Mbits/sec ^C[ 5] 7.00-7.36 sec 9.90 KBytes 226 Kbits/sec - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate [ 5] 0.00-7.36 sec 0.00 Bytes 0.00 bits/sec sender [ 5] 0.00-7.36 sec 1.04 MBytes 1.19 Mbits/sec receiver when changing u-boot back to older u-boot (same kernel), it works as expected # cat /dev/mtd/by-name/U-Boot | strings | grep -B1 "u-boot,version" 2023.04-00035-g7dd5eb0228 u-boot,version WARNING: could not set u-boot,version %s. # iperf3 -R -c odroidm1 Connecting to host odrdoidm1, port 5201 Reverse mode, remote host odroidm1 is sending [ ID] Interval Transfer Bitrate [ 5] 0.00-1.00 sec 110 MBytes 921 Mbits/sec [ 5] 1.00-2.00 sec 110 MBytes 926 Mbits/sec [ 5] 2.00-3.00 sec 110 MBytes 926 Mbits/sec [ 5] 3.00-4.00 sec 110 MBytes 921 Mbits/sec [ 5] 4.00-5.00 sec 111 MBytes 929 Mbits/sec [ 5] 5.00-6.00 sec 111 MBytes 927 Mbits/sec [ 5] 6.00-7.00 sec 110 MBytes 919 Mbits/sec ^C[ 5] 7.00-7.79 sec 87.0 MBytes 925 Mbits/sec - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate [ 5] 0.00-7.79 sec 0.00 Bytes 0.00 bits/sec sender [ 5] 0.00-7.79 sec 858 MBytes 924 Mbits/sec receiver iperf3: interrupt - the client has terminated ethtool output: ~# ethtool end0 Settings for end0: Supported ports: [ TP MII ] Supported link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Full Supported pause frame use: Symmetric Receive-only Supports auto-negotiation: Yes Supported FEC modes: Not reported Advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Full Advertised pause frame use: Symmetric Receive-only Advertised auto-negotiation: Yes Advertised FEC modes: Not reported Link partner advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Half 1000baseT/Full Link partner advertised pause frame use: No Link partner advertised auto-negotiation: Yes Link partner advertised FEC modes: Not reported Speed: 1000Mb/s Duplex: Full Auto-negotiation: on master-slave cfg: preferred slave master-slave status: slave Port: Twisted Pair PHYAD: 0 Transceiver: external MDI-X: Unknown Supports Wake-on: ug Wake-on: d Current message level: 0x0000003f (63) drv probe link timer ifdown ifup Link detected: yes

I upgraded my ROCK5B in-place from Armbian Bookworm beta to Armbian Testing/Trixie beta and it turns out that no Ambian packages are seen (so not updated). The Debian Trixie packages do upgrade, as for example I just saw while doing full-upgrade: libavif16:arm64 (1.2.1-1.2) over (1.2.1-1.1) ... I thought something with my install, but also downloaded 'Armbian_25.8.0-trunk.50_Rock-5b_trixie_vendor_6.1.115_minimal.img' yesterday and it has the same issue (quick test via systemd-nspawn container on loopdev mounted image). My goal is at least to figure out what is best bootloader and kernel for the ROCK5B. So far I simply copied/cloned Armbian Bookworm rootfs from ROCK3A+NanoPi-R6C and did some ROCK5B specific changes like U-Boot, but not much more and it actually is already good enough. But before the ROCK5B becomes a 24/7 headless workhorse with long uptime, I thought better to prepare/check for newer Linux or potential issues. I already upgraded some other devices from Bookworm->Trixie and that is quite an improvement, for example KDE 6 performs much better/nicer than KDE5 in Bookworm. It currently uses U-Boot 'edge' and 'current' kernel and very important for me, both the 'vendor' and 'mainline current/edge' overlay for SERDES multi-PHY SATA on the M.2 E-key work (and also the NVMe keeps working). I need to drill a hole in the Radxa aluminum cooling case for the SATA cable (and serial console cable), that needs some time first. I can build and install U-Boot and kernel etc manually of -course, but i wonder why Armbian packages are not visible. Is it as expected or is something wrong? I assume it is just too early yet and that it is work in progress. I think maybe policies are an issue, but don't understand what it could be. Maybe someone has a hint. root@rock-5b:~# apt policy Package files: 100 /var/lib/dpkg/status release a=now 500 http://deb.debian.org/debian trixie/non-free-firmware arm64 Packages release o=Debian,a=testing,n=trixie,l=Debian,c=non-free-firmware,b=arm64 origin deb.debian.org 500 http://deb.debian.org/debian trixie/non-free arm64 Packages release o=Debian,a=testing,n=trixie,l=Debian,c=non-free,b=arm64 origin deb.debian.org 500 http://deb.debian.org/debian trixie/contrib arm64 Packages release o=Debian,a=testing,n=trixie,l=Debian,c=contrib,b=arm64 origin deb.debian.org 500 http://deb.debian.org/debian trixie/main arm64 Packages release o=Debian,a=testing,n=trixie,l=Debian,c=main,b=arm64 origin deb.debian.org 500 https://beta.armbian.com trixie/trixie-desktop all Packages release o=Armbian,a=trixie,n=trixie,l=Armbian,c=trixie-desktop,b=all origin beta.armbian.com 500 https://beta.armbian.com trixie/trixie-desktop arm64 Packages release o=Armbian,a=trixie,n=trixie,l=Armbian,c=trixie-desktop,b=arm64 origin beta.armbian.com 500 https://beta.armbian.com trixie/trixie-utils all Packages release o=Armbian,a=trixie,n=trixie,l=Armbian,c=trixie-utils,b=all origin beta.armbian.com 500 https://beta.armbian.com trixie/trixie-utils arm64 Packages release o=Armbian,a=trixie,n=trixie,l=Armbian,c=trixie-utils,b=arm64 origin beta.armbian.com 500 https://github.armbian.com/configng stable/main arm64 Packages release o=armbian.github.io/configurator,n=stable,l=armbian.github.io/configurator,c=main,b=arm64 origin github.armbian.com Pinned packages:

I tried the image from "armbian.atomonetworks.com" and the exact same thing happens. Thanks, I'll compare the images.

The latest Linux kernel brings expanded hardware support for MediaTek and Rockchip, enhanced graphics drivers, and more. Collabora played a key role in this release, with no less than 20 authored contributors! View the full article