All Activity

Armbian is a stable OS, but we don't know about what SD-card, power-supply etc you use with your Cubitruck and/or NanoPi Neo+2 The decompression error can simply mean corrupt file due to something wrong with HW. Or something could have gone wrong during download of the files that you or the system decompress. Also note you use a kernel from beta repo (25.11.0-trunk.41). I you want better control, create/build an image formatted as Btrfs, not Ext4. Then you can check where it went wrong. I have several NanoPi-NEOs, all use Btrfs. 2 run 24/7, the others not all the time and usually just get sudden power cut, but they start fine next time. I do in-place upgrade them since years. If something would go wrong, typically as the error you show, I go back to a previous Btrfs snapshot or/and backup from NAS. That is simply what you could do / have done. Maybe something went wrong with that sunxi64 kernel build on the Armbian infrastructure side, that can happen every now and then as it is beta. So Also then, protect your devices again such issues. Also please don't post kernel upgrade errors in a topic about LiPo controller chip. OK for now, but annoying

Thank you Nick, that worked! Not sure what the root cause is but will try to compare and see if I can find it. thanks again

Your answers are pretty much appreciated, and i would like to thank you for all the good work for the last 15 years @armbian.com. But, i would like to have a system that is more stable than (the last more or less two years) armbian on cubie* or friendlyarm SBCs just right now. I do need a stable OS which is able to serve pihole or other base network stuff constantly. Something like dpkg-deb (subprocess): decompressing archive '/tmp/apt-dpkg-install-mzEu51/7-linux-image-current-sunxi64_25.11.0-trunk.41_arm64.deb' (size=38908852) member 'data.tar': lzma error: compressed data is corrupt dpkg-deb: error: <decompress> subprocess returned error exit status 2 dpkg: error processing archive /tmp/apt-dpkg-install-mzEu51/7-linux-image-current-sunxi64_25.11.0-trunk.41_arm64.deb (--unpack): cannot copy extracted data for './lib/modules/6.12.35-current-sunxi64/kernel/drivers/hwmon/w83781d.ko' to '/lib/modules/6.12.35-current-sunxi64/kernel/drivers/hwmon/w83781d.ko.dpkg-new': unexpected end of file or stream ...leading to a system that is not able to boot anymore (this is today's log of 'armbian-upgrade' on a NanoPI Neo+2) makes me think about asking you if i could provide some time to test your community builds and upgrades before they will be released to the public (-: Cheers

@zink try these images https://github.com/NickAlilovic/build/releases/tag/20250306

Try this image https://github.com/NickAlilovic/build/releases/download/20250306/Armbian-unofficial_25.05.0-trunk_X98h_bookworm_edge_6.12.11_xfce_desktop.img.xz

@laibsch, this is the Radxa Custom Debian OS that is shipped on the emmc. @justanothernoobCould be I did not have this issue because my board was delivered with an empty emmc (no RoobiOS installed). Though i doubt it. Do you have the serial console full output? Also is it a typo or is the error really about `/dev/mount/mmcblk0p1` not `/dev/mmcblk0p1`. Mind `/dev/mmcblk0p1` is the emmc partition while you should be booting from the SD card. I tet installed Note also that 25.2.2 linux (current) images area lacking most devices support, while vendor 25.2 has an issue with PCIe SATA detection. THe vendor PCIe detection is fixed in latest 25.08 vendor. But that does not explain your current issue... Can you try https://fi.mirror.armbian.de/incoming/prahal/rock-5-itx/archive/ vendor images dated after 16th of August (the ones before did not have the fix for PCIe SATA detection)? Like https://fi.mirror.armbian.de/incoming/prahal/rock-5-itx/archive/Armbian_25.8.1_Rock-5-itx_noble_vendor_6.1.115_xfce_desktop.img.xz

Try to upload the old and new driver to an AI with you overlay included. Here it gives some suggestions for what you can try. The power sequence seems to be changed with the new driver and it might be too fast for your display. It suggests to put some parameters in the overlay to delay some parts, with higher chance with the first 3: Under "dsi0_panel: panel@0 {" prepare-delay-ms = <120>; reset-delay-ms = <50>; init-delay-ms = <150>; enable-delay-ms = <50>; disable-delay-ms = <50>; unprepare-delay-ms = <120>;

https://github.com/armbian/build/pull/8517 appears to fix my SFP problems.

I'm trying to install Armbian on the Tanix Tx1 Soc Allwinner H313 Mini TV Box, but this box doesn't have an SD card slot. How do I install Armbian on this box without an SD card?

I'd suggest you start by reading this thread:

@schunckt Yes, I should have clarified that drm-copy is an argument is for MPV, which according to the guide mentioned above should allow the frame-buffer to be accessed directly. It is worth noting that mpv makes use of ffmpeg under the hood. Tried with ffplay once but did not have much luck with it. last I checked VLC is not supported other than the legacy vaapi. Please see: https://linux-sunxi.org/Sunxi-Cedrus You can use the sample media from linaro: https://samplemedia.linaro.org/ Just to check are you using the ffmpeg-v4l2-request?

v25.8.1 for Rock 5B Plus running Armbian Linux 6.1.115-vendor-rk35xx

Hi everyone. What I would like to do is install Armbian on the X98H TV box. I tried many ways to do that, but I was not successful. If you know how to install Armbian on it, plz suggest to me Thanks

@Ryzer There is no "ffmpeg -hwaccel drm-copy" option. Looks like this is mpv only, which - as said - doen't work with framebuffer. glxgears also can't work because i have no OpenGL. But in general that's a good hint. I'll create some small videos with different resolutions and compressions and measure the fps. Maybe that helps to nail down the issue. btw. I've not yet tested VLC. Need to figure out if this is a ffmpeg issue or something else inside the kernel, i.e. v4l2request related ... @robertoj Trying another image doesn't make much sense for me for several other reasons. T.

Hello everyone! Could you help find image for x96q v.5.1. which have stable wifi and ethernet?!

For information, fancontrol, deamon or service systemd crash but work just with run fancontrol from shell in root. Seen to be a privileges problem like systemd log... i look this soon and post here my workaround

That's exactly what I did. I wrote a replacement for the .not_logged_in_yet file in my customize-image.sh with pre-set parameters, just like I create /root/provisioning.sh. I was just wondering if there were any other ways to do this.

Thanks @laibsch and @royk. For now, we’ve managed to get things working by running the latest vendor kernel, but using panel-simple.c from version 6.1.43. This workaround isn’t ideal, and we’ll try to investigate the root cause once we have more time. As for the log message "Expected bpc in {6,8} but got: 0", it doesn’t appear when using 6.1.43, even though the relevant source code is identical in that part.

Hi, Today i upgrade to Armbian Trixie my Helios64 with upgrade from bookworn to trixie, not clean install All seen to be Okok only with use of rk3399-kobol-helios64.dtb-6.12.xx-L2-hs400-opp file inside of original rk3399-kobol-helios64.dtb Only problems for moment are: - fancontrol not seen to work lm75 module... service crash... i will investigate soon if i have the time. - apt show warning with SHA1 checksum or anything i can't investigate for the moment

.....

aww, too bad. I kinda like the tea distribution. ;-) regardless, I still can't find a reference as to what it really is.

was it kernel 6.16?

hey all, I have been running three Rock 5B+ for some time now with Proxmox arm port, and last night I did a kernel update to the latest, and now all three SBC are running extremely slow, PVE does not load, and there are a bunch of system errors (see below). I tried going back to an older kernel, but the same errors remain. any thoughts? Aug 18 07:13:00 PMOX2 kernel: rk806 spi2.0: no dvs-setting pinctrl state Aug 18 07:13:00 PMOX2 kernel: cpu cpu0: Failed to get specification_serial_number Aug 18 07:13:00 PMOX2 kernel: cpu cpu0: Failed to get specification_serial_number Aug 18 07:13:00 PMOX2 kernel: cpu cpu0: Failed to get leakage Aug 18 07:13:00 PMOX2 kernel: cpu cpu4: Failed to get specification_serial_number Aug 18 07:13:00 PMOX2 kernel: cpu cpu4: Failed to get specification_serial_number Aug 18 07:13:00 PMOX2 kernel: cpu cpu4: Failed to get leakage Aug 18 07:13:00 PMOX2 kernel: cpu cpu6: Failed to get specification_serial_number Aug 18 07:13:00 PMOX2 kernel: cpu cpu6: Failed to get specification_serial_number Aug 18 07:13:00 PMOX2 kernel: cpu cpu6: Failed to get leakage Aug 18 07:13:00 PMOX2 kernel: arm-scmi firmware:scmi: Failed. SCMI protocol 17 not active. Aug 18 07:13:00 PMOX2 kernel: debugfs: File 'Capture' in directory 'dapm' already present! Aug 18 07:13:00 PMOX2 kernel: debugfs: File 'Capture' in directory 'dapm' already present! Aug 18 07:13:00 PMOX2 kernel: rk-multicodecs es8316-sound: ASoC: Property 'rockchip,audio-routing' does not exist or its length> Aug 18 07:13:00 PMOX2 kernel: dw-pcie fe190000.pcie: invalid resource Aug 18 07:13:00 PMOX2 kernel: dw-pcie fe190000.pcie: Failed to initialize host Aug 18 07:13:00 PMOX2 kernel: mpp_rkvdec2 fdc38100.rkvdec-core: shared_niu_a is not found! Aug 18 07:13:00 PMOX2 kernel: rkvdec2_init:1198: No niu aclk reset resource define Aug 18 07:13:00 PMOX2 kernel: mpp_rkvdec2 fdc38100.rkvdec-core: shared_niu_h is not found! Aug 18 07:13:00 PMOX2 kernel: rkvdec2_init:1201: No niu hclk reset resource define Aug 18 07:13:00 PMOX2 kernel: mpp_rkvdec2 fdc48100.rkvdec-core: shared_niu_a is not found! Aug 18 07:13:00 PMOX2 kernel: rkvdec2_init:1198: No niu aclk reset resource define Aug 18 07:13:00 PMOX2 kernel: mpp_rkvdec2 fdc48100.rkvdec-core: shared_niu_h is not found! Aug 18 07:13:00 PMOX2 kernel: rkvdec2_init:1201: No niu hclk reset resource define Aug 18 07:13:00 PMOX2 kernel: mpp_rkvenc2 fdbd0000.rkvenc-core: rockchip_init_read_margin: no regulator (venc) found: -19 Aug 18 07:13:00 PMOX2 kernel: mpp_rkvenc2 fdbd0000.rkvenc-core: Failed to get leakage Aug 18 07:13:00 PMOX2 kernel: mpp_rkvenc2 fdbd0000.rkvenc-core: error -ENODEV: _opp_set_regulators: no regulator (venc) found Aug 18 07:13:00 PMOX2 kernel: mpp_rkvenc2 fdbd0000.rkvenc-core: failed to set opp config Aug 18 07:13:00 PMOX2 kernel: mpp_rkvenc2 fdbd0000.rkvenc-core: failed to init opp info Aug 18 07:13:00 PMOX2 kernel: mpp_rkvenc2 fdbd0000.rkvenc-core: failed to init_opp_table Aug 18 07:13:00 PMOX2 kernel: rkvenc_init:2147: failed to add venc devfreq Aug 18 07:13:00 PMOX2 kernel: mpp_rkvenc2 fdbe0000.rkvenc-core: rockchip_init_read_margin: no regulator (venc) found: -19 Aug 18 07:13:00 PMOX2 kernel: mpp_rkvenc2 fdbe0000.rkvenc-core: Failed to get leakage Aug 18 07:13:00 PMOX2 kernel: mpp_rkvenc2 fdbe0000.rkvenc-core: error -ENODEV: _opp_set_regulators: no regulator (venc) found Aug 18 07:13:00 PMOX2 kernel: mpp_rkvenc2 fdbe0000.rkvenc-core: failed to set opp config Aug 18 07:13:00 PMOX2 kernel: mpp_rkvenc2 fdbe0000.rkvenc-core: failed to init opp info Aug 18 07:13:00 PMOX2 kernel: mpp_rkvenc2 fdbe0000.rkvenc-core: failed to init_opp_table Aug 18 07:13:00 PMOX2 kernel: rkvenc_init:2147: failed to add venc devfreq Aug 18 07:13:00 PMOX2 kernel: rockchip-dmc dmc: Failed to get specification_serial_number Aug 18 07:13:00 PMOX2 kernel: rockchip-dmc dmc: Failed to get leakage Aug 18 07:13:00 PMOX2 kernel: rockchip-dmc dmc: failed to get vop bandwidth to dmc rate Aug 18 07:13:00 PMOX2 kernel: rockchip-dmc dmc: failed to get vop pn to msch rl Aug 18 07:13:00 PMOX2 kernel: mali fb000000.gpu: Failed to get specification_serial_number Aug 18 07:13:00 PMOX2 kernel: mali fb000000.gpu: Failed to get specification_serial_number Aug 18 07:13:00 PMOX2 kernel: mali fb000000.gpu: Failed to get leakage Aug 18 07:13:00 PMOX2 kernel: debugfs: Directory 'fb000000.gpu-mali' with parent 'vdd_gpu_s0' already present! Aug 18 07:13:00 PMOX2 kernel: debugfs: Directory 'fb000000.gpu-mali' with parent 'vdd_gpu_s0' already present! Aug 18 07:13:00 PMOX2 kernel: RKNPU fdab0000.npu: can't request region for resource [mem 0xfdab0000-0xfdabffff] Aug 18 07:13:00 PMOX2 kernel: RKNPU fdab0000.npu: can't request region for resource [mem 0xfdac0000-0xfdacffff] Aug 18 07:13:00 PMOX2 kernel: RKNPU fdab0000.npu: can't request region for resource [mem 0xfdad0000-0xfdadffff] Aug 18 07:13:00 PMOX2 kernel: RKNPU fdab0000.npu: RKNPU: Failed to get specification_serial_number Aug 18 07:13:00 PMOX2 kernel: RKNPU fdab0000.npu: Failed to get specification_serial_number Aug 18 07:13:00 PMOX2 kernel: RKNPU fdab0000.npu: Failed to get leakage Aug 18 07:13:00 PMOX2 kernel: debugfs: Directory 'fdab0000.npu-rknpu' with parent 'vdd_npu_s0' already present! Aug 18 07:13:00 PMOX2 kernel: debugfs: Directory 'fdab0000.npu-rknpu' with parent 'vdd_npu_s0' already present! Aug 18 07:13:00 PMOX2 kernel: rk_hdmirx fdee0000.hdmirx-controller: hdmirx_cancel_cpu_limit_freq freq qos nod add Aug 18 07:13:00 PMOX2 systemd-tmpfiles[765]: Setting file flags is only supported on regular files and directories, cannot set > Aug 18 07:13:00 PMOX2 blkmapd[786]: open pipe file /run/rpc_pipefs/nfs/blocklayout failed: No such file or directory Aug 18 07:13:01 PMOX2 pmxcfs[1241]: [quorum] crit: quorum_initialize failed: 2 Aug 18 07:13:01 PMOX2 pmxcfs[1241]: [quorum] crit: can't initialize service Aug 18 07:13:01 PMOX2 pmxcfs[1241]: [confdb] crit: cmap_initialize failed: 2 Aug 18 07:13:01 PMOX2 pmxcfs[1241]: [confdb] crit: can't initialize service Aug 18 07:13:01 PMOX2 pmxcfs[1241]: [dcdb] crit: cpg_initialize failed: 2 Aug 18 07:13:01 PMOX2 pmxcfs[1241]: [dcdb] crit: can't initialize service Aug 18 07:13:01 PMOX2 pmxcfs[1241]: [status] crit: cpg_initialize failed: 2 Aug 18 07:13:01 PMOX2 pmxcfs[1241]: [status] crit: can't initialize service Aug 18 07:13:20 PMOX2 kernel: [GTP-ERR][__do_register_ext_module:79] Module [goodix-fwu] timeout

@BipBip1981 did you perform a clean install or update? I'm still using the following combination and am considering updating... 23.08.0-trunk Bookworm with Linux 6.6.8 I've had repeated connection problems over the last few months, which meant I couldn't access it via smb and all my backup jobs went wrong. However, it has been running stably again for some time now, which is very strange.