Igor
-
Posts
14614 -
Joined
-
Last visited
Content Type
Forums
Store
Crowdfunding
Applications
Events
Raffles
Community Map
Posts posted by Igor
-
-
What was already tested:
- UEFI x86 KDE Neon, Gnome, Ubuntu minimal
- MusePI Pro Xfce
- Odroid M1 KDE Neon
- Odroid N2 Xfce https://paste.armbian.com/oqegebaqey
- Orangepi 5
- Nanopi M4V2
- Odroid M2
- Radxa E54
- Rock 5C
- Orangepi 3LTS
-
We are opening public testing for upcoming Armbian images. The goal is to verify that the right images are built and that basic functionality works before boards are moved to the main download pages.
You don’t need to be a developer. Simple testing and short reports are enough.
1. Download testing images
Testing images are available here: https://fi.mirror.armbian.de/incoming/igorpecovnik/ Pick the image matching your board and choose desktop if applicable.
Once image is confirmed working, the board will be:- Moved to the main download pages
- Added to Armbian Imager
2. Check that expected images exist
Before testing, please verify that:
- Your board is listed
- The expected image variants exist
If an image (variant) seems to be missing:
-
Check the release target definitions:
https://github.com/armbian/armbian.github.io/tree/main/release-targets -
If the image should exist, check build logs to see if it failed:
https://github.com/armbian/os/actions/runs/21642728389
If you are unsure, report it anyway.
3. Flash and boot
Flash the image using Armbian Imager: https://imager.armbian.com
Boot the board and check whether it reaches:
- Login prompt (CLI images)
- Desktop (Desktop images)
If the board does not boot, serial output or photos help.
4. What to test
Please focus on basic functionality:
- Boot reliability and reboot
- Networking (Ethernet, Wi-Fi, Bluetooth)
- Display and GPU, if applicable
- Installer and first-boot experience
Advanced features can wait. Stability comes first.
5. UEFI ARM64 images
If your board might support UEFI on ARM64, please test those images on them. Working UEFI images allow us to reuse targets and reduce the number of generated images.
Reference:
https://github.com/armbian/armbian.github.io/blob/main/release-targets/reusable.yml
6. Community-supported boards
Some boards are currently released as community-supported: https://github.com/armbian/community/releases
We want to promote suitable boards to standard support which brings more image variants and much faster download. This requires:- Confirmation that basic functionality works
- Send a PR to change status from .csc to .conf
- A community member willing to step up as maintainer
If you rely on such a board and want it promoted, this is the time to help.
7. Reporting (here in this topic!)
When reporting test results, please include:
- Board model
- Image name and variant
- What works and what does not
- Logs or serial output if available
Even short reports like “Board X, image Y, boots and networking works” are useful.
Thanks to everyone helping with testing. Early feedback directly improves the release quality!
-
8 hours ago, maxsub said:
maybe needs more RAM
BTF is hungry for memory, yes. KERNEL_BTF=n and it needs less. On 16Gb+ machine you should be fine. If not memory is eaten away by something else.
-
https://github.com/armbian/os/pull/426
Once automation finishes - couple of hours, repo will have a missing package.Workaround: manually install package from https://packages.debian.org/forky/zfs-zed
-
Headers are present. https://imola.armbian.com/apt/pool/main/l/linux-headers-current-rockchip64/
Upgrade packages to latest and try again. -
3 hours ago, comp2000 said:
because it works with
Some context:
https://docs.armbian.com/User-Guide_FAQ/#why-things-stop-working
The hardest part and expensive for time is keeping functions working while kernel changes, goes up. Image you are referring too is probably a demo image with some ancient kernel that will never be changed. This is usual way to sell hardware. It is made to work, but you will stay at this very old SW stack without any real option to change or fix anything.
All functions on 300+ boards, which on top of extreme diversity, have also different revisions, quality issue ... is already not possible to keep up by entire open source community. Armbian is small part focused into SBCs and we do what we can. Work we are doing is never complete, we (nobody) can't solve bugs and especially not near to (expected) real-time. We (or community open source in total) can address a problem within weeks or months fastest as resources are tiny compared to problems that are constantly found in open source code that somebody else made. We have no option to expand the team / project as users don't care about well being of SW developers.
We can only try to keep SW stack operational on a best effort principle. Once this job becomes too expensive (<1% of costs share is on users side), we have to step back and declare support as "community". We will continue to build and ship images as they might still work for some use cases and as downstream projects will provide those Armbian images anyway.
-
Rpi support for whatever of their devices is mainly on the level of RaspberryPi OS. We use their kernels sources as base, add some additional things and release timing is different - not much difference. If they added new device, it should just work.
If anyone wants to improve support or fix WiFi -> https://github.com/armbian/build/pulls
-
On 1/22/2026 at 1:50 AM, MasterLog said:
a simple way
There is no way. You need a dedicated image for your hardware.On 1/22/2026 at 1:50 AM, MasterLog said:but it doesn't seem to support some features
-
Test automation doesn't detect any issues https://github.com/armbian/configng/actions/runs/21465331853 and since I had freshly build Armbian Trixie
on Nanopi R6S (same arch) I run install:
Spoiler2026-01-29 22:35:43.339 started, version pi-hole-v2.92test21 cachesize 10000 2026-01-29 22:35:43.339 DNS service limited to local subnets 2026-01-29 22:35:43.339 compile time options: IPv6 GNU-getopt no-DBus no-UBus no-i18n IDN2 DHCP DHCPv6 Lua TFTP no-conntrack ipset no-nftset auth DNSSEC loop-detect inotify dumpfile 2026-01-29 22:35:43.339 using nameserver 172.18.0.2#5335 2026-01-29 22:35:43.339 using only locally-known addresses for onion 2026-01-29 22:35:43.339 using only locally-known addresses for bind 2026-01-29 22:35:43.339 using only locally-known addresses for invalid 2026-01-29 22:35:43.339 using only locally-known addresses for test 2026-01-29 22:35:43.339 using only locally-known addresses for pi.hole 2026-01-29 22:35:43.339 using only locally-known addresses for lan 2026-01-29 22:35:43.339 using only locally-known addresses for internal 2026-01-29 22:35:43.339 using only locally-known addresses for home.arpa 2026-01-29 22:35:43.339 read /etc/hosts - 10 names 2026-01-29 22:35:43.339 read /etc/pihole/hosts/custom.list - 0 names 2026-01-29 22:36:02.383 query[SRV] _http._tcp.apt.armbian.com from 172.18.0.1 2026-01-29 22:36:02.392 forwarded _http._tcp.apt.armbian.com to 172.18.0.2#5335 2026-01-29 22:36:02.392 query[SRV] _https._tcp.github.armbian.com from 172.18.0.1 2026-01-29 22:36:02.392 forwarded _https._tcp.github.armbian.com to 172.18.0.2#5335 2026-01-29 22:36:02.392 query[SRV] _http._tcp.deb.debian.org from 172.18.0.1 2026-01-29 22:36:02.393 forwarded _http._tcp.deb.debian.org to 172.18.0.2#5335 2026-01-29 22:36:02.393 query[SRV] _http._tcp.security.debian.org from 172.18.0.1 2026-01-29 22:36:02.393 forwarded _http._tcp.security.debian.org to 172.18.0.2#5335 2026-01-29 22:36:02.477 reply _http._tcp.apt.armbian.com is NXDOMAIN 2026-01-29 22:36:02.478 query[A] apt.armbian.com from 172.18.0.1 2026-01-29 22:36:02.479 forwarded apt.armbian.com to 172.18.0.2#5335 2026-01-29 22:36:02.479 query[AAAA] apt.armbian.com from 172.18.0.1 2026-01-29 22:36:02.479 forwarded apt.armbian.com to 172.18.0.2#5335 2026-01-29 22:36:02.479 reply apt.armbian.com is 152.53.81.238 2026-01-29 22:36:02.481 reply _http._tcp.deb.debian.org is <SRV> 2026-01-29 22:36:02.481 reply _http._tcp.security.debian.org is <SRV> 2026-01-29 22:36:02.482 query[A] debian.map.fastlydns.net from 172.18.0.1 2026-01-29 22:36:02.483 forwarded debian.map.fastlydns.net to 172.18.0.2#5335 2026-01-29 22:36:02.483 query[AAAA] debian.map.fastlydns.net from 172.18.0.1 2026-01-29 22:36:02.483 forwarded debian.map.fastlydns.net to 172.18.0.2#5335 2026-01-29 22:36:02.483 query[A] debian.map.fastlydns.net from 172.18.0.1 2026-01-29 22:36:02.483 query[AAAA] debian.map.fastlydns.net from 172.18.0.1 2026-01-29 22:36:02.501 reply apt.armbian.com is 2a0a:4cc0:2000:34a5::1 2026-01-29 22:36:02.509 reply _https._tcp.github.armbian.com is NXDOMAIN 2026-01-29 22:36:02.511 query[A] github.armbian.com from 172.18.0.1 2026-01-29 22:36:02.511 forwarded github.armbian.com to 172.18.0.2#5335 2026-01-29 22:36:02.511 query[AAAA] github.armbian.com from 172.18.0.1 2026-01-29 22:36:02.511 forwarded github.armbian.com to 172.18.0.2#5335 2026-01-29 22:36:02.530 reply debian.map.fastlydns.net is 199.232.18.132 2026-01-29 22:36:02.538 reply debian.map.fastlydns.net is 2a04:4e42:41::644 2026-01-29 22:36:02.683 reply github.armbian.com is <CNAME> 2026-01-29 22:36:02.684 reply armbian.github.io is 2606:50c0:8003::153 2026-01-29 22:36:02.684 reply armbian.github.io is 2606:50c0:8000::153 2026-01-29 22:36:02.684 reply armbian.github.io is 2606:50c0:8001::153 2026-01-29 22:36:02.684 reply armbian.github.io is 2606:50c0:8002::153 2026-01-29 22:36:02.699 reply github.armbian.com is <CNAME> 2026-01-29 22:36:02.699 reply armbian.github.io is 185.199.110.153 2026-01-29 22:36:02.699 reply armbian.github.io is 185.199.111.153 2026-01-29 22:36:02.699 reply armbian.github.io is 185.199.108.153 2026-01-29 22:36:02.699 reply armbian.github.io is 185.199.109.153 2026-01-29 22:36:02.730 query[SRV] _http._tcp.armbian.systemonachip.net from 172.18.0.1 2026-01-29 22:36:02.730 forwarded _http._tcp.armbian.systemonachip.net to 172.18.0.2#5335 2026-01-29 22:36:03.351 query[PTR] 1.0.18.172.in-addr.arpa from 127.0.0.1 2026-01-29 22:36:03.361 config 172.18.0.1 is NXDOMAIN 2026-01-29 22:36:03.363 query[PTR] 2.0.18.172.in-addr.arpa from 127.0.0.1 2026-01-29 22:36:03.364 config 172.18.0.2 is NXDOMAIN 2026-01-29 22:36:03.384 reply _http._tcp.armbian.systemonachip.net is NXDOMAIN 2026-01-29 22:36:03.385 query[A] armbian.systemonachip.net from 172.18.0.1 2026-01-29 22:36:03.385 forwarded armbian.systemonachip.net to 172.18.0.2#5335 2026-01-29 22:36:03.385 query[AAAA] armbian.systemonachip.net from 172.18.0.1 2026-01-29 22:36:03.386 forwarded armbian.systemonachip.net to 172.18.0.2#5335 2026-01-29 22:36:03.464 reply armbian.systemonachip.net is 2a0d:f302:103:5674::2 2026-01-29 22:36:03.527 reply armbian.systemonachip.net is 46.102.157.202 2026-01-29 22:36:04.368 query[PTR] 1.0.0.127.in-addr.arpa from 127.0.0.1 2026-01-29 22:36:04.368 /etc/hosts 127.0.0.1 is localhost 2026-01-29 22:36:08.766 query[A] pi.hole from 127.0.0.1 2026-01-29 22:36:08.766 Pi-hole hostname pi.hole is 127.0.0.1 2026-01-29 22:36:39.010 query[A] pi.hole from 127.0.0.1 2026-01-29 22:36:39.010 Pi-hole hostname pi.hole is 127.0.0.1 2026-01-29 22:37:09.283 query[A] pi.hole from 127.0.0.1 2026-01-29 22:37:09.283 Pi-hole hostname pi.hole is 127.0.0.1
Spoiler2026-01-29 22:35:42.878 INFO PID of FTL process: 195 2026-01-29 22:35:42.880 INFO listening on 0.0.0.0 port 53 2026-01-29 22:35:42.880 INFO listening on :: port 53 2026-01-29 22:35:42.882 INFO PID of FTL process: 195 2026-01-29 22:35:42.882 WARNING No database file found, creating new (empty) database 2026-01-29 22:35:42.928 INFO Database version is 1 2026-01-29 22:35:42.928 INFO Updating long-term database to version 2 2026-01-29 22:35:42.942 INFO Updating long-term database to version 3 2026-01-29 22:35:42.954 INFO Updating long-term database to version 4 2026-01-29 22:35:42.962 INFO Updating long-term database to version 5 2026-01-29 22:35:42.981 INFO Updating long-term database to version 6 2026-01-29 22:35:42.989 INFO Updating long-term database to version 7 2026-01-29 22:35:42.997 INFO Updating long-term database to version 8 2026-01-29 22:35:43.017 INFO Updating long-term database to version 9 2026-01-29 22:35:43.027 INFO Updating long-term database to version 10 2026-01-29 22:35:43.044 INFO Updating long-term database to version 11 2026-01-29 22:35:43.058 INFO Updating long-term database to version 12 2026-01-29 22:35:43.069 INFO Updating long-term database to version 13 2026-01-29 22:35:43.077 INFO Updating long-term database to version 14 2026-01-29 22:35:43.085 INFO Updating long-term database to version 15 2026-01-29 22:35:43.099 INFO Updating long-term database to version 16 2026-01-29 22:35:43.107 INFO Updating long-term database to version 17 2026-01-29 22:35:43.118 INFO Updating long-term database to version 18 2026-01-29 22:35:43.126 INFO Updating long-term database to version 19 2026-01-29 22:35:43.134 INFO Updating long-term database to version 20 2026-01-29 22:35:43.154 INFO Updating long-term database to version 21 2026-01-29 22:35:43.163 INFO Database successfully initialized 2026-01-29 22:35:43.178 INFO Imported 0 queries from the on-disk database (it has 0 rows) 2026-01-29 22:35:43.178 INFO Parsing queries in database 2026-01-29 22:35:43.178 INFO Imported 0 queries from the long-term database 2026-01-29 22:35:43.178 INFO -> Total DNS queries: 0 2026-01-29 22:35:43.178 INFO -> Cached DNS queries: 0 2026-01-29 22:35:43.178 INFO -> Forwarded DNS queries: 0 2026-01-29 22:35:43.178 INFO -> Blocked DNS queries: 0 2026-01-29 22:35:43.178 INFO -> Unknown DNS queries: 0 2026-01-29 22:35:43.178 INFO -> Unique domains: 0 2026-01-29 22:35:43.178 INFO -> Unique clients: 0 2026-01-29 22:35:43.178 INFO -> DNS cache records: 0 2026-01-29 22:35:43.179 INFO -> Known forward destinations: 0 2026-01-29 22:35:43.329 WARNING Insufficient permissions to set system time (CAP_SYS_TIME required), NTP client not available 2026-01-29 22:35:43.329 INFO NTP server listening on 0.0.0.0:123 (IPv4) 2026-01-29 22:35:43.329 INFO NTP server listening on :::123 (IPv6) 2026-01-29 22:35:43.329 INFO FTL is running as user pihole (UID 1000) 2026-01-29 22:35:43.333 INFO Created SSL/TLS certificate for pi.hole at /etc/pihole/tls.pem 2026-01-29 22:35:43.333 INFO Reading certificate from /etc/pihole/tls.pem ... 2026-01-29 22:35:43.333 INFO Using SSL/TLS certificate file /etc/pihole/tls.pem 2026-01-29 22:35:43.333 INFO Web server ports: 2026-01-29 22:35:43.333 INFO - 0.0.0.0:80 (HTTP, IPv4, optional, OK) 2026-01-29 22:35:43.333 INFO - 0.0.0.0:443 (HTTPS, IPv4, optional, OK) 2026-01-29 22:35:43.333 INFO - [::]:80 (HTTP, IPv6, optional, OK) 2026-01-29 22:35:43.333 INFO - [::]:443 (HTTPS, IPv6, optional, OK) 2026-01-29 22:35:43.333 INFO Restored 0 API sessions from the database 2026-01-29 22:35:43.339 INFO Blocking status is enabled 2026-01-29 22:35:43.433 INFO Compiled 0 allow and 0 deny regex for 0 client in 0.1 msec 2026-01-29 22:35:44.330 INFO Reloading config due to pihole.toml change 2026-01-29 22:35:44.332 INFO 2 FTLCONF environment variables found (1 used, 0 invalid, 1 ignored) 2026-01-29 22:35:44.332 INFO [✓] FTLCONF_dns_upstreams is used 2026-01-29 22:35:44.333 WARNING [?] FTLCONF_LOCAL_IPV4 is unknown, did you mean any of these? 2026-01-29 22:35:44.333 WARNING - FTLCONF_debug_all 2026-01-29 22:35:44.337 INFO Wrote config file: 2026-01-29 22:35:44.337 INFO - 162 total entries 2026-01-29 22:35:44.337 INFO - 159 entries are default 2026-01-29 22:35:44.337 INFO - 3 entries are modified 2026-01-29 22:35:44.337 INFO - 1 entry is forced through environmentWorks like charm.
Make sure to do apt update + apt upgrade before you start. -
2 hours ago, DogancanYr said:
I installed pihole and unbound with Armbian's ready-made config installation, but I can't access the interface of the pihole.
Did you used most up2date armbian-config? Few days ago some critical bugs were fixed - i tested it several times and it worked ... -
1 hour ago, comp2000 said:
but where exactly is it?
Probably, my guess, issue with a boot loader - fail to / disabled by mistake power SATA port? We don't have anyone actively maintaining this kind of (10+years) hardware anymore. Support is "community / upstream" maintained "as is". But this forum / community can provide assistance to fix this. I gave a tip - where I think is the problem.
Not working feature on particular hardware is not Armbian problem. This is custom hardware world and our work is tooling https://github.com/armbian/build and best effort hardware maintenance on this principle https://docs.armbian.com/User-Guide_Board-Support-Rules/ If we try to fix everything, everyone would be long burned out ... -
13 hours ago, Gaetano said:
under any release
Userspace has nothing to do with hardware features. I don't know what is the case for A20, but for many others, OTG functionality is driven with overlays. If there are no overlays, you need to edit device tree and change its role. If that doesn't help, it is more complex problem.13 hours ago, Gaetano said:The drive appears in Windows Explorer after several minutes
More complex, perhaps days / weeks to debug and fix. Most of (Armbian) kernel developers are long gone from this 10+ years old platform
and users can't help.
Also look into previous builds. Finding out when this broke is half of the solution https://fi.mirror.armbian.de/oldarchive/or by finding a kernel that works https://docs.armbian.com/User-Guide_Armbian-Config/System/#alternative-kernels With any userspace (trixie/noble/jammy ...)
13 hours ago, Gaetano said:I am looking for a forum where pcduino users can help each other.
Probably all A10 and A20 boards share this problem.
-
Feature regressions are sadly something that happens all the time. There are many variants out there and (part of) Armbian OS is different for every board ... First resolve confusion - do you have M1 (we call it just bananapi) or M3. You mention M3 in the text, while title says M1+. Those are totally different boards.
Proceed from older images and find out when this feature stopped working:
https://fi.mirror.armbian.de/archive/
https://fi.mirror.armbian.de/oldarchive/ -
Ubuntu Noble variant already supports ZFS on 6.18.y while Trixie was added today:
https://github.com/armbian/os/pull/425
Testing:
Spoilersudo apt install zfs-dkms zfsutils-linux ^Cading package lists... 98% igorp@odroidm1:~$ sudo apt update Hit:1 http://security.debian.org trixie-security InRelease Hit:2 http://deb.debian.org/debian trixie InRelease Hit:3 http://deb.debian.org/debian trixie-updates InRelease Hit:4 http://deb.debian.org/debian trixie-backports InRelease Hit:5 https://github.armbian.com/configng stable InRelease Get:6 https://repo.armbian.com/artifacts/425/zfs-trixie trixie InRelease [50.6 kB] Get:7 https://repo.armbian.com/artifacts/425/zfs-trixie trixie/trixie-utils all Packages [866 B] Get:8 https://repo.armbian.com/artifacts/425/zfs-trixie trixie/trixie-utils arm64 Packages [2,730 B] Fetched 54.2 kB in 8s (7,025 B/s) All packages are up to date. igorp@odroidm1:~$ sudo apt install zfs-dkms zfsutils-linux Installing: zfs-dkms zfsutils-linux Installing dependencies: dkms file libmagic-mgc libmagic1t64 libnvpair3linux libuutil3linux libzfs7linux libzpool7linux Suggested packages: menu debhelper nfs-kernel-server samba-common-bin zfs-initramfs | zfs-dracut Recommended packages: fakeroot zfs-zed Summary: Upgrading: 0, Installing: 10, Removing: 0, Not Upgrading: 0 Download size: 5,170 kB Space needed: 37.5 MB / 4,520 MB available Continue? [Y/n] Get:1 http://deb.debian.org/debian trixie/main arm64 libmagic-mgc arm64 1:5.46-5 [338 kB] Get:2 http://deb.debian.org/debian trixie/main arm64 libmagic1t64 arm64 1:5.46-5 [103 kB] Get:3 http://deb.debian.org/debian trixie/main arm64 file arm64 1:5.46-5 [43.7 kB] Get:4 http://deb.debian.org/debian trixie/main arm64 dkms all 3.2.2-1~deb13u1 [60.1 kB] Get:5 https://repo.armbian.com/artifacts/425/zfs-trixie trixie/trixie-utils arm64 libnvpair3linux arm64 2.4.0-1 [61.8 kB] Get:6 https://repo.armbian.com/artifacts/425/zfs-trixie trixie/trixie-utils arm64 libuutil3linux arm64 2.4.0-1 [54.7 kB] Get:7 https://repo.armbian.com/artifacts/425/zfs-trixie trixie/trixie-utils arm64 libzfs7linux arm64 2.4.0-1 [222 kB] Get:8 https://repo.armbian.com/artifacts/425/zfs-trixie trixie/trixie-utils arm64 libzpool7linux arm64 2.4.0-1 [1,211 kB] Get:9 https://repo.armbian.com/artifacts/425/zfs-trixie trixie/trixie-utils arm64 zfsutils-linux arm64 2.4.0-1 [587 kB] Get:10 https://repo.armbian.com/artifacts/425/zfs-trixie trixie/trixie-utils arm64 zfs-dkms all 2.4.0-1 [2,488 kB] Fetched 5,170 kB in 4s (1,268 kB/s) Preconfiguring packages ... Selecting previously unselected package libnvpair3linux:arm64. (Reading database ... 61282 files and directories currently installed.) Preparing to unpack .../0-libnvpair3linux_2.4.0-1_arm64.deb ... Unpacking libnvpair3linux:arm64 (2.4.0-1) ... Selecting previously unselected package libuutil3linux:arm64. Preparing to unpack .../1-libuutil3linux_2.4.0-1_arm64.deb ... Unpacking libuutil3linux:arm64 (2.4.0-1) ... Selecting previously unselected package libzfs7linux:arm64. Preparing to unpack .../2-libzfs7linux_2.4.0-1_arm64.deb ... Unpacking libzfs7linux:arm64 (2.4.0-1) ... Selecting previously unselected package libzpool7linux:arm64. Preparing to unpack .../3-libzpool7linux_2.4.0-1_arm64.deb ... Unpacking libzpool7linux:arm64 (2.4.0-1) ... Selecting previously unselected package zfsutils-linux. Preparing to unpack .../4-zfsutils-linux_2.4.0-1_arm64.deb ... Unpacking zfsutils-linux (2.4.0-1) ... Selecting previously unselected package libmagic-mgc. Preparing to unpack .../5-libmagic-mgc_1%3a5.46-5_arm64.deb ... Unpacking libmagic-mgc (1:5.46-5) ... Selecting previously unselected package libmagic1t64:arm64. Preparing to unpack .../6-libmagic1t64_1%3a5.46-5_arm64.deb ... Unpacking libmagic1t64:arm64 (1:5.46-5) ... Selecting previously unselected package file. Preparing to unpack .../7-file_1%3a5.46-5_arm64.deb ... Unpacking file (1:5.46-5) ... Selecting previously unselected package dkms. Preparing to unpack .../8-dkms_3.2.2-1~deb13u1_all.deb ... Unpacking dkms (3.2.2-1~deb13u1) ... Selecting previously unselected package zfs-dkms. Preparing to unpack .../9-zfs-dkms_2.4.0-1_all.deb ... Unpacking zfs-dkms (2.4.0-1) ... Setting up libnvpair3linux:arm64 (2.4.0-1) ... Setting up libmagic-mgc (1:5.46-5) ... Setting up libmagic1t64:arm64 (1:5.46-5) ... Setting up file (1:5.46-5) ... Setting up dkms (3.2.2-1~deb13u1) ... Setting up zfs-dkms (2.4.0-1) ... Loading new zfs/2.4.0 DKMS files... Building for 6.18.7-current-rockchip64 Building initial module zfs/2.4.0 for 6.18.7-current-rockchip64 The kernel is built without module signing facility, modules won't be signed Running the pre_build script................................................................................................................................................... done. Building module(s)...................................................................................................................................................Once automation completes, it will be provided via normal apt update.
-
On 1/26/2026 at 12:24 PM, ChrisO said:
Anyway, the link to Armbian_community_26.2.0-trunk.151_Odroidhc4_trixie_current_6.18.2_minimal.img is not there anymore
Old automated builds are not kept. Only last three releases https://github.com/armbian/community/releases Its 300Gb / week -
-
On 1/10/2026 at 2:48 AM, Matt W. said:
Kernel Version: 6.1.115-vendor-rk35xx
It is not recommended to match ZFS with vendor kernel(s). In general. Use mainline based current / edge kernels. Here v6.18.y we also might not have suitable ZFS yet as the kernel is too fresh. But if not today, it will be avail within days / weeks. -
First testing on similar device (Odroid N2) didn't reveal any troubles. Need to locate VIM3 and try to recreate.
-
-
43 minutes ago, TRay said:
Igor, I understand the issue is complex, as you say, but for now I can only report that this didn't work.
Sure, no worries.
44 minutes ago, TRay said:please let me know what we should do next
You will notice once its fixed.
as this is not something you should adjust on the APT client side.
48 minutes ago, TRay said:I don't want to lose the work
You didn't and won't loose anything except current updating mechanism is broken.
-
2 hours ago, tutralex said:
Mirror synchronization has been going on for about a week now!?
I spent practically whole holidays to rework repository management and there are still some problems, even it was tested on and on before going into production. But beta repository, which you are having troubles with, was never tested. Only stable.
Motive: https://github.com/armbian/build/pull/9150
Affected:
https://github.com/armbian/armbian.github.io/blob/main/scripts/sync-repository.sh
https://github.com/armbian/armbian.github.io/blob/main/scripts/copy-kernel-packages.sh
https://github.com/armbian/build/blob/main/tools/repository/extract-repo.sh
https://github.com/armbian/build/blob/main/tools/repository/repo.sh
... so you might get an idea on the problem complexity
-
Current way of installing is as written on the download pages. It was verified with latest v24.11.2 image.
-
12 minutes ago, Tim Zhang said:
The host system must be Ubuntu Noble 24.04.x?
Yes, highly recommended in order to avoid troubles. We mainly use Noble and all of our build & test automation runs on Jammy / Noble. However, when using Docker, you should have more freedom.
-
How you can help test upcoming Armbian 26.02 images?
in Advanced users - Development
Posted
Here, yes. Thank you!
No, but we need to test images made for release. There is another last minute change
https://github.com/armbian/build/commit/1890d7f6566a65202f73730b469d024c20f863b8
than can, in theory, make unbootable image.
OK. Bugs will be present and we won't be fixing them at this stage. Here - if basic things works - that image boots, have connectivity and video output ... its ready to ship. All other things can be fixed with an update. If / when they are fixed.
Armbian exists to save users time so you don't need to waste your private time dealing with bad software experience which would exists without our work. Sadly most people don't understand the value Armbian projecst make.
Average Armbian developer have 100+ boards. We drown in issues they generate. All board manufacturer are happy to send us board for free and we decline many of their offers. I still have many unpacked boxes ... Without your help / engagement, we have no alternative but to keep images in automated untested (theoretically community maintained images) loop. Standard support costs us more then automated unchecked images.