The assembler now exists on the deep-ink branch, and the verification is numeric, not eyeballed: hardware-decoded frames compared pixel-by-pixel against software decode — identical, at 8-bit and at 4K HDR10 (Main10). The comparison tools are committed (tools/hevc-ladder.sh) so you can reproduce the verdict yourself.

Honest status: it is NOT in the default codec list yet — that happens as v2.1 after real-playback soak, per this project's policy of only advertising what's hardware-proven (KNOWN-ISSUES, KI-2). To test today: build the branch, run with RKVA_ADVERTISE_ALL=1.

Testers wanted, especially: streams that fail with a "SPS-indexed RPS" warning in the driver log (KI-5 — a known class we can't reconstruct yet), interlaced/broadcast H.264 (KI-1), and any HEVC content that doesn't match software decode. ffprobe output + the driver log (RK_VAAPI_LOG=/path) makes a report gold.

Connecting to the guest wlan of the same router worked.

I could trace it to the backslash in the SSID which "netplan try" complained about.

Escaping that with a additional backslash made "netplan try" accept it, but the connection did not work, the interface wlan0 remained in status "state DOWN".

Changing the SSID (removing that single backslash) made it working.

I did not find something that prohibits the backslash used in the name of the SSID, so I'm unsure.

I recently upgraded my Orange Pi 5 Plus to "Armbian 26.5.1" and noticed in the MOTD (on logins) that it is still showing version "26.2.1". I found differences in this 2 files, and the latter is the one used as reference for MOTD:

cat /etc/os-release:
PRETTY_NAME="Armbian 26.5.1 trixie"
NAME="Debian GNU/Linux"
VERSION_ID="13"
VERSION="13 (trixie)"
VERSION_CODENAME=trixie
DEBIAN_VERSION_FULL=13.5
ID=debian
HOME_URL="https://www.armbian.com"
SUPPORT_URL="https://forum.armbian.com"
BUG_REPORT_URL="https://www.armbian.com/bugs"
ARMBIAN_PRETTY_NAME="Armbian 26.5.1 trixie" 

cat /etc/armbian-release:
# PLEASE DO NOT EDIT THIS FILE
BOARD=orangepi5-plus
BOARD_NAME="Orange Pi 5 Plus"
BOARDFAMILY=rockchip-rk3588
BUILD_REPOSITORY_URL=https://github.com/armbian/build
BUILD_REPOSITORY_COMMIT=77f919f6c
LINUXFAMILY=rockchip64
ARCH=arm64
BOOT_SOC=rk3588
IMAGE_TYPE=stable
BOARD_TYPE=conf
INITRD_ARCH=arm64
KERNEL_IMAGE_TYPE=Image
KERNEL_TARGET=current,edge,vendor
KERNEL_TEST_TARGET=vendor,current
FORCE_BOOTSCRIPT_UPDATE=
FORCE_UBOOT_UPDATE=
OVERLAY_DIR="/boot/dtb/rockchip/overlay"
VENDOR="Armbian"
VENDORCOLOR="247;16;0"
VENDORDOCS="https://docs.armbian.com"
VENDORURL="https://www.armbian.com"
VENDORSUPPORT="https://forum.armbian.com"
VENDORBUGS="https://www.armbian.com/bugs"
BOOTSCRIPT_FORCE_UPDATE="no"
BOOTSCRIPT_DST="boot.cmd"
VERSION=26.2.1
REVISION=26.2.1
BRANCH=edge
 

Can somebody explain why armbian-release doesn't get properly updated? I belive this is not the first time I see this, I recall seeing this behaviour from previuos upgrades too.

Thanks!

When I want to change settings, the password entry pop-up appears briefly and immediately disappears again, preventing the settings from being saved.

I performed a completely fresh installation of the computer, and the problem still occurs. What is causing this?

Any help would be appreciated.

Best regards
Albrecht

Written for: the same readers as the finding, maintainers and users; the chart is built to be attached to it or to stand alone in a forum post.

Ours versus theirs, same board, same 100-minute 4K 10-bit title, same afternoon, same kernel journal:

frames out of 143,641decoder resetsspeed

theirs, jellyfin-ffmpeg 8.1.3-1 with its bundled fork MPP100,13111,520~120 fps until it broke at 42:11

ours, system ffmpeg → rockchip-vaapi → upstream-lineage MPP143,6410106 fps, intact to the end

The chart shows it in one glance: nothing missing anywhere for either until minute 40, then orange bars at 50 to 60 percent loss for the remaining hour, green flat on zero the whole way. The speed difference is the honest cost of the guard, one decode task at a time instead of two, and it's the throughput the revert was presumably chasing.

Where everything is:

claude-pi-handoffs/20261002/FINDING-jellyfin-mpp-vp9-10bit-frame-loss.md, now with the fourth row, the throughput note and the chart reference.

ours-vs-theirs.png beside it, 1600×900, ready to attach.

after-gaps-sheet.png in the evidence folder if anyone asks what the surviving frames look like.

The evidence folder holds every log, both journal counts, the gap analysis, the test scripts and the rating with three addenda.

One disclosure kept in the document rather than buried: ours printed two MPP buffer-slot assertion lines at teardown, after the last frame, with no effect on output. Better that you say it than someone else finds it.

The output file and the source title are still on the test board under ~/probe if you want to watch the freezes before posting. Nothing else is running; the package is complete.

NO SLOP!


 

rockchip-linux/mpp 2026-08-05 snapshot (yisding's resolute packaging)
rockchip-vaapi  2.2.0 rebuilt for resolute
PipeWire / WirePlumber      1.6.9 / 0.5.17 (resolute ships 1.6.2 / 0.5.13)
MPV    stock 0.41 + our mpv.conf
ffmpeg / libva        8.0.1 / 2.23
PulseAudio—purged
baked: hi-res allowed-rates, SBC-XQ ported Lua→SPA-JSON
Bluetooth parameters applied... No Audio Stutter on wifi scans...  https://discourse.osmc.tv/t/cypress-release-fix-for-onboard-bluetooth-audio-stuttering/74345
4k@120hz patch applied... 

 

And the whole chain did exactly what the patches intended:

                           before                                                                                                                                                                                   now

v0pll24 MHz (parked on the crystal)                                                                                                                2 165 779 907 Hz — driver re-rated it to 2× the pixel clock

dclk_vop0533 250 000                                                                                                                                             1 082 889 954 (46 Hz off target, pure rounding)

PHYlts4 → lts3 → ltsl thrash, fell back to p60                                                           rk_hdptx_frl_lcpll_cmn_config rate=4000000000 → PHY clk ready → PHY lane locked → Training finish, go to ltsp

Mode fell back to 59.997 Hz                                                                                                                                                         120.000 Hz, current
 

One mode set, no fallback, zero VOP/HDMI errors, desktop alive, GPU idling at 300 MHz and 36 °C. The link came up in FRL at 4 Gbps/lane — the first time this board has negotiated FRL rather than TMDS.

So the diagnosis held: rkr7.2's new vop2_is_dclk_switch_to_cru_pll() was reading our raised 1200 MHz ceiling and therefore kept an FRL-rate mode on the HDMI PHY PLL, which in the rewritten PHY driver can't leave TMDS on its own; and VP0 had no path to v0pll, the only PLL that can be re-rated to an arbitrary pixel clock. Two patches, both small.

Also confirmed live: CMA is 512 MB (the distro value you chose), and the AFBC-reject patch is in with no AFBC complaints in the log.

 

I configured a static IP in armbian imager profile and root password and other user name and password and also other settings.

I was expecting the orange pi zero 2W to come online and me to get ping on the set IP address.

To my surprise it still asked for all those details as if the profile settings were not applied.

SBC Orange Pi Zero 2W

OS Armbian 26.11.0 Minimal Debian 13 Current 6.18.54

Armbian Imageer V2.0.4

Is it possible to make onboard sd card program as a system drive by changing the setting to allow system drives.

However it still exposes newbie to possible risk of ending up the SSD.

Please keep SD card slot as an exception to be treated as system drive.

It created "/armbian/sabnzbd" and three directories under that, "config", "download" and "incomplete", which matches the recommenations. 

Next, I installed Sonarr for TV, which created "/armbian/sonarr" and three directories under that, "config", "download" and "tvseries". While "/armbian/sonarr" and "/armbian/sabnzbd" are owned by my user, the "download" directory and "tvseries" directories were owned by root. So, I changed the ownership to my user, but it still wasn't working right.

I read up on how these containers are supposed to interact, but it looks like there should be a common download directory. Since SABnzbd has a download directory, I moved the "download" directory in "/armbian/sonarr" to a different name and then linked the "/armbian/sabnzbd/download" directory to "/armbian/sonarr/download" and the Sonarr "tvseries" directory started filling up.

Radarr and Lidarr should be set up similarly and will have root owned "download" and "movies"/"music" directories. With a common "download" directory, all the files started poplulating.

Another piece of the stack is Bazarr. Installing Bazarr "/armbian/bazarr/tv" and "/armbian/bazarr/movies" are created, but they don't point to the Sonarr and Radarr "tvseries" and "movies" directories. So that has to be fixed. 

One note is that you must stop each container before you change the directories.

Please add any other ideas for improvement or notes on how you got things to work here.
 

After an `apt update` running `apt upgrade` tries to update the `linux-libc-dev` package, which is downloaded from `ports.ubuntu.com`. However it consistently fails with a 404.

Digging around a little, it seems like this package should match the kernel that's in use, so is the underlying problem that `apt` is trying to download it from the ubuntu repo instead of the armbian one where the kernel package comes from? I have not modified any apt configuration since installing.

# HOW-TO: Hardware video decode in Google Chrome on RK3588 (Orange Pi 5B / Ubuntu-rockchip BSP)

This gets Google Chrome to decode video on the RK3588 hardware VPU (via VA-API) instead of
grinding it out on the CPU. Result: smooth 1080p and 4K playback with the CPU nearly idle.

Codecs that decode in hardware: H.264, HEVC, VP8, VP9. (No AV1 - see Problems and Fixes.)

As a bonus, the same driver also gives Firefox hardware decode.

--------------------------------------------------
WHO THIS IS FOR
--------------------------------------------------
- RK3588 / RK3588S board (Orange Pi 5B, Orange Pi 5, etc.), arm64.
- An Armbian image on the VENDOR kernel branch (the Rockchip 6.1 BSP). The vendor kernel is the
  one with Rockchip MPP - i.e. /dev/mpp_service exists. Ubuntu or Debian userland both work.
- This does NOT apply to the "current" or "edge" (mainline) kernel branches. Mainline has no MPP
  and uses a completely different path (V4L2 stateless). If /dev/mpp_service does not exist, you
  are on a mainline kernel and this guide does not apply.

Check first:

uname -r              # expect something like 6.1.0-xxxx-rockchip (BSP), not mainline
ls -l /dev/mpp_service # must exist. If "No such file or directory", you are on mainline.

--------------------------------------------------
BACKGROUND - two different paths, for different browsers
--------------------------------------------------
There are two separate hardware-decode paths on RK3588, and they cover different browsers. Know
which one you want before you start:

1) The distro CHROMIUM path (rkmpp via the V4L2 shim). On Armbian you enable this through
   armbian-config, which installs the rockchip multimedia stack - rockchip-multimedia-config,
   libv4l-rkmpp, gstreamer1.0-rockchip - from ppa:liujianfeng1994/rockchip-multimedia (see armbian
   configng PR #887). That makes the distro Chromium hardware-decode. It does NOTHING for Google
   Chrome or Firefox, and it depends on that PPA having a build for your Ubuntu release (at the
   time of writing the PPA targets Noble; newer releases such as Resolute are not covered).

2) The VA-API path (THIS guide). Google Chrome and Firefox decode through VA-API (libva), not the
   Chromium/V4L2 shim. On a fresh BSP install VA-API is broken, because the Rockchip VA-API driver
   (rockchip_drv_video.so) is not installed - so Chrome and Firefox fall back to software. This
   guide installs that driver and points Chrome at it.

Use path 1 (armbian-config) if you only want Chromium. Use this guide if you want hardware decode
in Google Chrome or Firefox. The two can coexist on the same system.

--------------------------------------------------
DOWNLOADS (with versions)
--------------------------------------------------
1) Google Chrome for arm64 (unlisted, but a genuine Google build):
   Download: https://dl.google.com/linux/direct/google-chrome-stable_current_arm64.deb
   Version tested: 151.0.7922.137-1
   Note: Google's download page only offers amd64. The arm64 file exists on the same server;
   you get it by swapping "amd64" for "arm64" in the URL. Installing the deb also adds Google's
   apt repo, so it self-updates.

2) Rockchip VA-API driver source:
   Source: https://github.com/woodyst/rockchip-vaapi
   Recommended fixes: https://github.com/woodyst/rockchip-vaapi/pull/2 (truongsinh PR #2 -
   fixes green bands, adds surface/RT-format reporting, H.264 B-frame handling, RGA blitter)
   Version: the built driver reports "Rockchip MPP VA-API Driver 0.1"

--------------------------------------------------
STEP 1 - INSTALL THE ROCKCHIP VA-API DRIVER
--------------------------------------------------
sudo apt update
sudo apt install -y build-essential pkg-config git libva-dev librockchip-mpp-dev vainfo

Note on librockchip-mpp-dev (the MPP build headers): on Armbian vendor it comes from
ppa:liujianfeng1994/rockchip-multimedia. If you have already enabled Chromium hardware decode via
armbian-config, that PPA is already added and the package installs directly. If it is not present
for your release, install the runtime lib (librockchip-mpp1) and take the matching headers from the
MPP source (https://github.com/rockchip-linux/mpp), then build against those.

git clone https://github.com/woodyst/rockchip-vaapi.git
cd rockchip-vaapi

# Recommended: apply PR #2 correctness/perf fixes
git fetch origin pull/2/head:pr2 && git checkout pr2

make

DRIDIR=$(pkg-config --variable=driverdir libva)
sudo install -m0644 rockchip_drv_video.so "$DRIDIR/rockchip_drv_video.so"

# Tell all VA-API apps to use it (applies fully after next login)
echo 'LIBVA_DRIVER_NAME=rockchip' | sudo tee -a /etc/environment

Confirm it loads:

vainfo

You want to see "va_openDriver() returns 0" and a list of VAProfile entries, e.g.:

vainfo: Driver version: Rockchip MPP VA-API Driver 0.1
VAProfileH264ConstrainedBaseline: VAEntrypointVLD
VAProfileH264Main               : VAEntrypointVLD
VAProfileH264High               : VAEntrypointVLD
VAProfileHEVCMain               : VAEntrypointVLD
VAProfileHEVCMain10             : VAEntrypointVLD
VAProfileVP8Version0_3          : VAEntrypointVLD
VAProfileVP9Profile0            : VAEntrypointVLD
VAProfileVP9Profile2            : VAEntrypointVLD

--------------------------------------------------
STEP 2 - INSTALL GOOGLE CHROME (arm64)
--------------------------------------------------
cd ~
wget https://dl.google.com/linux/direct/google-chrome-stable_current_arm64.deb
sudo apt install -y ./google-chrome-stable_current_arm64.deb

--------------------------------------------------
STEP 3 - PERSISTENT HARDWARE-DECODE LAUNCHER
--------------------------------------------------
Chrome does not read a flags directory. Two things must be true every launch:
(a) the hardware-decode flags are on, and
(b) LIBVA_DRIVER_NAME=rockchip is in Chrome's environment (its sandbox blocks auto-detect).

The reliable way is a small wrapper script plus a user-level launcher that survives Chrome's
apt updates.

Create the wrapper:

mkdir -p ~/.local/bin
cat > ~/.local/bin/google-chrome-hw <<'EOF'
#!/bin/bash
export LIBVA_DRIVER_NAME=rockchip
exec /usr/bin/google-chrome-stable \
  --enable-features=AcceleratedVideoDecoder,AcceleratedVideoDecodeLinuxGL,AcceleratedVideoDecodeLinuxZeroCopyGL \
  --ignore-gpu-blocklist --enable-gpu-rasterization --enable-zero-copy --ozone-platform-hint=auto "$@"
EOF
chmod +x ~/.local/bin/google-chrome-hw

Create a user-level launcher that points at the wrapper (overrides the system one):

mkdir -p ~/.local/share/applications
cp /usr/share/applications/google-chrome.desktop ~/.local/share/applications/
sed -i "s|/usr/bin/google-chrome-stable|$HOME/.local/bin/google-chrome-hw|g" \
  ~/.local/share/applications/google-chrome.desktop

--------------------------------------------------
STEP 4 - LOG OUT AND BACK IN (once)
--------------------------------------------------
This makes two things take effect at once: the desktop re-reads your launcher (so the dock/menu
icon uses the wrapper), and /etc/environment is applied to the whole session (so every app,
including Chrome's child processes, gets LIBVA_DRIVER_NAME).

--------------------------------------------------
STEP 5 - VERIFY IT IS ACTUALLY ON THE HARDWARE
--------------------------------------------------
Launch Chrome from the dock/menu, play any video, then:

- chrome://gpu -> "Video Decode: Hardware accelerated" (green).
- Node-level proof - while a video plays:

sudo fuser /dev/mpp_service

If that prints a chrome PID, the VPU is doing the decode. During playback a chrome process
should sit low (single-digit to low tens of percent of one core), not 150-400%.

--------------------------------------------------
PROBLEMS AND FIXES
--------------------------------------------------
1) vainfo says: "va_openDriver() returns -1" / "vaInitialize failed"
   Cause: rockchip_drv_video.so is not installed. libva sees the DRM driver "rockchip-drm",
   looks for a matching VA driver named "rockchip", and finds nothing.
   Fix: do Step 1. Confirm the file exists:
   ls -l /usr/lib/aarch64-linux-gnu/dri/rockchip_drv_video.so

2) Chrome plays video but the CPU is very high and there is no hardware decode
   a) Flags not applied. You launched plain Chrome, not the wrapper. Chrome does not read a
      chromium.d flags dir. Use the wrapper/launcher from Step 3. Check chrome://gpu.
   b) Driver name not set. Chrome's sandbox blocks VA-API auto-detect, so
      LIBVA_DRIVER_NAME=rockchip must be in Chrome's environment. The wrapper exports it, and
      /etc/environment sets it session-wide after a re-login. (Unsandboxed vainfo works without
      it; Chrome does not - do not be fooled by vainfo passing.)

3) Putting "env VAR=val" in the .desktop Exec line does nothing
   The desktop launcher does not honor an "env" prefix in Exec. Use a wrapper script that
   exports the variable, as in Step 3.

4) The dock icon still launches Chrome without the flags after you made the override
   The desktop caches the app entry. Log out and back in (Step 4). To test immediately without
   logging out: gtk-launch google-chrome

5) You quit and relaunched Chrome but it still has the old (no) flags
   Chrome is single-instance per profile. Clicking the icon again just focuses the existing
   process. Fully quit first, confirm nothing is running, then launch:
   pkill chrome ; sleep 2 ; pgrep -x chrome    # should print nothing
   (pkill chrome does NOT touch chromium - "chrome" is not inside "chromium".)

6) It looks like software even though everything is set up right
   Chrome throttles or pauses video in a background / occluded tab or window, which reads as
   "0% CPU, node idle". Test with the window focused or fullscreen. Also skip YouTube pre-roll
   ads (they are often a different codec).

7) AV1 content falls back to software
   This driver does not advertise AV1 by design (Rockchip MPP needs a full OBU bytestream, but
   VA-API hands it headerless tile data, so it cannot be wired up). H.264 / HEVC / VP8 / VP9 are
   hardware. For YouTube, set your account playback preference so it does not force AV1, and VP9
   (which is hardware here) will be used.

😎 High CPU during 4K, especially at a 120 Hz refresh
   That is compositing/present cost, not decode. Confirm decode is still on the hardware: no
   single chrome process is pegged at 300-400%, and fuser /dev/mpp_service still shows chrome.
   Setting the display to 4K@60 roughly halves the compositing CPU (a 60 fps video does not need
   a 120 Hz present rate).

9) Do NOT add --disable-gpu-compositing
   It can cure some flicker, but it silently kills hardware video decode. Leave it off if you
   want HW video.

10) Note on the distro Chromium
    Chromium uses a different path (rkmpp via the V4L2 shim, not VA-API). On Armbian, enable that
    with armbian-config (the rockchip multimedia stack from ppa:liujianfeng1994/rockchip-multimedia,
    armbian configng PR #887) - not with this guide. This guide is for Google Chrome and Firefox,
    which the Chromium route does not cover. The two can coexist.

--------------------------------------------------
FIREFOX BONUS (same driver)
--------------------------------------------------
With the VA-API driver from Step 1 installed, Firefox also hardware-decodes:
in about:config set
  media.ffmpeg.vaapi.enabled = true
  media.hardware-video-decoding.enabled = true
Verify in about:support (Media section) or with vainfo.

--------------------------------------------------
TESTED ON
--------------------------------------------------
- Orange Pi 5B (RK3588S), GNOME on Wayland, Rockchip 6.1 BSP userland
- Developed and verified on a ubuntu-rockchip (Noble) BSP install; the procedure is the same on
  an Armbian vendor image - only the Step 1 build-package names can differ (see the note there)
- Kernel: 6.1.0-1027-rockchip (ubuntu-rockchip); Armbian vendor is the equivalent Rockchip 6.1 BSP
- google-chrome-stable: 151.0.7922.137-1
- librockchip-mpp / librockchip-mpp-dev: 1.5.0-1+git20240717.5275a9a6~noble
- libva: 2.20.0
- Driver: Rockchip MPP VA-API Driver 0.1 (woodyst/rockchip-vaapi + PR #2)
- Verified at 1080p and 4K (H.264 and VP9): /dev/mpp_service held by Chrome, CPU near idle,
  GPU load a few percent, temps in the high 50s to high 60s C.


Firefox Install

Adding since the scope of the guide includes Firefox.

#!/usr/bin/env bash
# rockchip-vaapi driver installer  --  hardware video decode (VA-API) on RK3588/RK3588S
# vendor (Rockchip 6.1 BSP) kernels. Installs the VA-API driver that Google Chrome AND
# Firefox use, then points the system at it. Companion to the HOW-TO in this thread.
#
#   Run:  sudo bash rockchip-vaapi-install.sh
#
# Driver: github.com/woodyst/rockchip-vaapi + truongsinh PR #2 (green-band / RT-format /
# H.264 B-frame / RGA fixes). Reports "Rockchip MPP VA-API Driver 0.1".
set -euo pipefail

[ "$(id -u)" = 0 ] || { echo "Please run with sudo:  sudo bash $0" >&2; exit 1; }

# This is the BSP/VA-API path. It needs /dev/mpp_service (vendor 6.1 kernel with Rockchip MPP).
# Mainline (current/edge) kernels have no MPP and use a different path -- this won't apply.
if [ ! -e /dev/mpp_service ]; then
  echo "ERROR: /dev/mpp_service not found -- you're on a mainline kernel (current/edge)." >&2
  echo "       This driver needs the VENDOR BSP kernel (uname -r shows ...-rockchip on 6.1)." >&2
  exit 1
fi

echo "==> Installing build + runtime dependencies..."
export DEBIAN_FRONTEND=noninteractive
apt-get update -y
apt-get install -y --no-install-recommends \
  build-essential pkg-config git libva-dev librockchip-mpp-dev vainfo

echo "==> Building the Rockchip VA-API driver (woodyst + PR #2)..."
tmp="$(mktemp -d)"; trap 'rm -rf "$tmp"' EXIT
git clone https://github.com/woodyst/rockchip-vaapi.git "$tmp/src"
cd "$tmp/src"
git fetch origin pull/2/head:pr2 && git checkout pr2   # correctness/perf fixes
make
[ -f rockchip_drv_video.so ] || { echo "build failed -- no rockchip_drv_video.so produced." >&2; exit 1; }

echo "==> Installing the driver..."
DRIDIR="$(pkg-config --variable=driverdir libva 2>/dev/null || echo /usr/lib/aarch64-linux-gnu/dri)"
install -d "$DRIDIR"
install -m0644 rockchip_drv_video.so "$DRIDIR/rockchip_drv_video.so"
echo "    -> $DRIDIR/rockchip_drv_video.so"

# Make all VA-API apps prefer this driver (applies fully after next login).
if ! grep -q '^LIBVA_DRIVER_NAME=rockchip$' /etc/environment 2>/dev/null; then
  echo 'LIBVA_DRIVER_NAME=rockchip' >> /etc/environment
  echo "    set LIBVA_DRIVER_NAME=rockchip in /etc/environment"
fi

echo "==> Verifying with vainfo..."
if LIBVA_DRIVER_NAME=rockchip vainfo 2>&1 | grep -q 'va_openDriver() returns 0'; then
  LIBVA_DRIVER_NAME=rockchip vainfo 2>&1 | grep -E 'Driver version|VAProfile' | sed 's/^/    /'
  echo "==> Driver loads and reports HW decode profiles.  OK"
else
  echo "!! vainfo did not confirm the driver. Full output:"
  LIBVA_DRIVER_NAME=rockchip vainfo 2>&1 | sed 's/^/    /' || true
fi

cat <<'EOF'

============================================================
 Driver installed. Log OUT and back in once (so LIBVA_DRIVER_NAME applies
 session-wide), then enable HW decode in your browser per the HOW-TO above:
   - Google Chrome : the wrapper + .desktop override (Steps 2-3)
   - Firefox       : about:config ->
       media.ffmpeg.vaapi.enabled            = true
       media.hardware-video-decoding.enabled = true

 Hardware codecs: H.264 / HEVC / VP8 / VP9   (no AV1 -- by design)
 Verify: chrome://gpu (Video Decode: Hardware accelerated), or during playback
         `sudo fuser /dev/mpp_service` should show your browser's PID.
============================================================
EOF

--------------------------------------------------
CREDITS
--------------------------------------------------
- VA-API driver: woodyst/rockchip-vaapi
- Fixes: truongsinh, PR #2
- BSP image / MPP userland: Joshua Riek (ubuntu-rockchip)

https://interfacinglinux.com/community/sbcsoftware/installing-official-chrome-for-arm64-linux-desktop/#post-1246

"Got Two Claudes & A Turntable"

"A subtle bug the vendor introduced and nobody upstream has fixed, in code you already live in. The RK3588 VOP2 port copied RK3568's layer-latch mechanism but dropped the one wait that makes it work — and mainline sidesteps the whole thing in hardware, so no one's ever going to fix it in the BSP but you.

Be honest on confidence: the code defect is register-confirmed (high); that it's the flicker rests on the mutter-direct-scanout inference (medium) — which is exactly what the MUTTER_DEBUG=disable-direct-scanout test nails in two minutes."

HW Acceleration came back, Address bars and Search bars seam better. But bringing up a thumbnail intensive news site has flickering. Expanding Fullscreen or un-maximizing has issues (use f11 to clear). I haven't messed with any flags, going to a new build and test.

But Panfork is dead and deleted, updating Mesa breaks it.
This will be my final version of the Joshua Riek Fork. I have Debian mainline working good with two caveats, No 4k@120 Or 4k@60 or 4k@100. The other is No NPU for AI.
Firefox is cleaner so it will be default.

After a boot soak and final testing I'll send the Armbian BSP PR.

Thought we had it for a minute,

defcom5-rockchip

 [  
— same Pi, same video, green                                                                                                                                                                                                                                 → clean 4K ]
 

📎 Full illustrated guide attached (unzip → open the HTML) · also online: https://defcom5-rockchip.github.io/rockchip-vaapi/

Quick start — BSP kernel only (/dev/mpp_service must exist):

cd /tmp
wget https://github.com/defcom5-rockchip/rockchip-vaapi/releases/download/v1.0.11-defcom5.vp9align1/rockchip-vaapi-driver_1.0.11+defcom5.vp9align1_arm64.deb
sudo apt install ./rockchip-vaapi-driver_1.0.11+defcom5.vp9align1_arm64.deb
Then wrap Firefox with LIBVA_DRIVER_NAME=rockchip + MOZ_DISABLE_RDD_SANDBOX=1, and enable media.ffmpeg.vaapi.enabled / media.hardware-video-decoding.enabled in about:config. Full steps — wrapper script, verify, YouTube tip — in the attached guide.

Source, credit & reproducer → github.com/defcom5-rockchip/rockchip-vaapi
Base driver: woodyst (Eduardo García-Mádico Portabella) · PR #2 fixes: truongsinh · VP9 64-align fix: defcom5-rockchip

Firefox-4K-HW-Decode-RK3588.zip

chose resolute and edge to get a 7.x kernel and 26.04 lts like system

seems to run fine - except 2 things 

1) minor - the network activity LED on my turing pi2 board doesnt flash yellow - I can live with that as long as I see activity led flashing and I can ssh just fine

2) annoying- the turing-rk1 boards get hot but I have nice heatsinks and fans applied to them .. only the fans dont work - 

Following internet guides I send 

$  echo 255 | sudo tee /sys/class/hwmon/hwmon*/pwm1

which activated the fans for a few seconds .. then they stopped .. now according to the hardware sensors my boards report upward 50°C while previously they ran at around 20 (room temperature) which is uncomfortable if I consider that the boards mostly idle (4% cpu activity) 
How can I activate the fans? If this is the wrong place to ask - please kindly point me a way where I can learn to fix it..

Cross-posting this because it took a while to untangle, and most guides out there are either
vendor-BSP/rkmpp (the wrong stack for mainline) or they stop at "it says hardware accelerated"
without checking whether it actually is.

Tested on an Orange Pi 5B, mainline Debian 13 (trixie),
kernel 7.1.3+deb13-arm64, panthor + PanVK, Wayfire. Should apply to any RK3588/RK3588S board on a
mainline stateless-decode kernel (Rock 5B, OPi 5, etc.). Corrections welcome; I'd rather this be
right than mine.

First, the thing that trips everyone up: on mainline, rkmpp is not your path.

Rockchip's MPP library (the thing that hardware-decodes at ~9% CPU on the vendor BSP images) talks
to /dev/mpp_service. That device only exists on the vendor kernel. On mainline/panthor there is no
mpp_service and there never will be, so every rkmpp-based ffmpeg/Chromium build is a dead end here.

And no, the GPU doesn't help. PanVK exposes zero VK_KHR_video_decode extensions. Mali-G610 has no
video engine. Vulkan composites and scales the decoded frames; it never produces them. The decode
blocks are separate silicon (rkvdec, Hantro) behind a separate kernel API.

The mainline path is V4L2 stateless (the request API), the work Collabora and Jernej Skrabec carry
upstream, with the userspace ffmpeg side maintained by Kwiboo (Jonas Karlman). The kernel drivers
are already there; on my box the v4l2_h264/v4l2_vp9 helpers are loaded and bound to rkvdec/hantro_vpu
out of the box. What's missing is a userspace that speaks the request API. Stock Debian ffmpeg
doesn't, so it silently decodes in software (1080p H.264 is about 600% CPU, six cores pegged).

Check what your kernel actually exposes before anything else:

  for v in /dev/video*; do echo "== $v =="; v4l2-ctl -d $v --list-formats-out 2>/dev/null | grep -oE "'[A-Z0-9]{4}'"; done

On my 7.1.3 kernel:
  /dev/video1 (rkvdec)              -> S264 S265         (H.264, HEVC)
  /dev/video2 (rk3568-vpu)         -> S264 VP8F MG2S    (H.264, VP8, MPEG-2)
  /dev/video4 (rk3588-av1-vpu-dec) -> AV1F              (AV1, advertises up to 4096x2304)
  VP9 is NOT exposed on this kernel; that is a beryllium/7.2-rc5+ restore (VP9-on-VDPU381).
  More on why that barely matters below.

Part A: system-wide HW decode (mpv, VLC, GStreamer, everything)

Build Kwiboo's FFmpeg fork, branch v4l2-request-n7.1.3. The version choice is deliberate: ffmpeg
7.1.3 is libavcodec.so.61, the same soname as Debian trixie's 7.1.5, so it is a genuine drop-in.
You swap one component and every libav app hardware-decodes with zero rebuilds. (The newer n8.x
branches are .so.62 and become an island: only the one binary you point at them benefits.)

  sudo apt install build-essential git nasm pkg-config libdrm-dev libudev-dev v4l-utils \
    libx264-dev libx265-dev libvpx-dev libopus-dev libvorbis-dev libmp3lame-dev libdav1d-dev libva-dev

  git clone -b v4l2-request-n7.1.3 https://github.com/Kwiboo/FFmpeg ffmpeg-7131 && cd ffmpeg-7131
  ./configure --prefix=/usr/local --enable-shared --disable-static \
    --enable-gpl --enable-version3 --enable-v4l2-request --enable-libdrm \
    --enable-libx264 --enable-libx265 --enable-libvpx --enable-libopus \
    --enable-libvorbis --enable-libmp3lame --enable-libdav1d --disable-vulkan --disable-doc
  make -j$(nproc)

Build gotcha that cost me an hour: do NOT add --enable-libv4l2. On n7.1.3 its libavdevice/v4l2.c
fails to compile against current libv4l headers (the SET_WRAPPERS macro). That is the webcam-capture
indev, nothing to do with request-API decode. Leave it off.

Test before installing anything system-wide, with stock mpv pointed at the fresh libs:

  LD_LIBRARY_PATH=/usr/local/lib mpv --hwdec=v4l2request-copy --gpu-api=vulkan yourfile.mp4

You want to see "Using hardware decoding (v4l2request-copy)" and pixfmt drm_prime. My numbers:
1080p H.264 went from about 600% CPU (software) to about 37% of one core.

Then package it as a .deb that Provides/Conflicts/Replaces the eight Debian libav* packages
(= 7:7.1.5-0+deb13u1) and installs your .so.61 plus symlinks into /usr/lib/aarch64-linux-gnu/. apt
treats it as satisfying the deps, so mpv/vlc/gstreamer/qt-multimedia all stay installed and all
start hardware-decoding. Cache the stock debs first (apt download the eight) so rollback is one
command.

Honest tradeoff: this replaces your system libav with a fork, so (a) the blast radius is every
media app, and (b) you now own libav security. When Debian bumps 7.1.x for a CVE, you rebuild the
one deb. I think that is a fair price for one-component maintenance versus forking every app.
Your call.

Part B: in-browser HW decode (Chromium), and a myth to kill

You do not need a forked Chromium, and you do not need the libva-v4l2-request VA-API shim for the
browser. Both are things the vendor/rkmpp world needs; mainline does not.

Two facts do the work:
  1. Debian trixie already ships Chromium 151, past the upstream 150 ANGLE roll that fixed the old
     VP9 green-artifact bug. Stock: apt install chromium.
  2. Chromium bundles its own ffmpeg, and its AcceleratedVideoDecoder talks V4L2-stateless straight
     to /dev/videoN. So Part A's libav swap is irrelevant to the browser; the two paths are
     independent.

Debian's chromium launcher sources /etc/chromium.d/*, so drop a flag file:

  # /etc/chromium.d/50-hwdecode
  export CHROMIUM_FLAGS="$CHROMIUM_FLAGS --ozone-platform-hint=auto \
    --enable-features=AcceleratedVideoDecoder,AcceleratedVideoDecodeLinuxGL,AcceleratedVideoDecodeLinuxZeroCopyGL \
    --ignore-gpu-blocklist --enable-gpu-rasterization --enable-zero-copy"

Notes:
  - The flag that actually gates it is AcceleratedVideoDecoder. The older
    AcceleratedVideoDecodeLinuxV4L2 no longer exists in 150+ and is silently ignored.
  - It needs a Wayland session. --ozone-platform-hint=auto picks it under Wayfire/wlroots.

Result: browser H.264 held /dev/video1 at about 23% of one core. AV1 held /dev/video4. Which brings
us to the part that actually stumped me.

Part 😄 the 4K@30 gotcha. cma=256M is too small, and it fails silently.

This is the reason I wrote the post. In-browser AV1 worked perfectly at 1080p: decoder node held,
about 26% of one core, 95% idle. Force the same av01 stream to 2160p and it dropped straight back to
software: one Chromium process at about 400%, /dev/video4 idle, and stats-for-nerds still reading
av01. Same codec, two outcomes.

The tell that it is not the codec: the AV1 block advertises up to 4096x2304, so 4K is in spec. It is
not a capability ceiling. The kernel log named it exactly:

  cma: __cma_alloc_frozen: alloc failed, req-size: 3421 pages, ret: -16
    hantro_postproc_alloc -> dma_alloc_attrs -> hantro_start_streaming

The Hantro decoder needs a roughly 13 MB contiguous buffer for a 4K frame, and the default cma=256M
pool was too fragmented to hand it out. hantro_start_streaming bails, and Chromium does what it is
designed to do: falls back to software, silently, with no error on screen. At 1080p the buffer is a
quarter the size and fits; at 4K it does not.

Fix (a boot argument, not a kernel rebuild): bump the CMA reservation. On the mainline extlinux
setup that is:

  # /boot/extlinux/extlinux.conf  -> in the "append ..." line(s), and
  # /etc/default/u-boot           -> U_BOOT_PARAMETERS (the template extlinux regenerates from)
  cma=256M   becomes   cma=1G

Edit both, or a future u-boot-update reverts you. Reboot. (The other fix you will see mentioned is
CONFIG_VSI_IOMMU=y, which lets the AV1 VPU scatter-gather through the IOMMU and sidestep the
contiguous requirement, but that is a kernel rebuild. The boot arg is free.)

After cma=1G (CmaTotal 1 GB): the same 4K av01 fullscreen stream went from four pegged cores to
58% of one core, 91% idle, decoder node held, zero allocation failures, and it ran cooler (47C to
36C). 256 MB is simply too small a house for 4K decode on this SoC. Ship 512M or more; I use 1G.

Codec support, honestly (this kernel): H.264 yes, HEVC yes, AV1 yes (including 4K with the CMA
bump), VP8/MPEG-2 yes, VP9 is software (not in 7.1.3; needs beryllium/7.2+). In practice the VP9
gap barely bites: because Chromium now advertises AV1 decode, YouTube negotiates av01 at every
resolution I tested (1080p and 4K), and only reaches for VP9 in ads. So I am leaving VP9 to upstream
rather than chasing a custom kernel.

How to actually verify HW decode (do not trust chrome://gpu): it reports a capability ("Video
Decode: Hardware accelerated") that stays true even while a given stream decodes in software. The
only honest test is who holds the decode node, sampled during steady playback (not during an ad or
a quality ramp; those transients will lie to a CPU snapshot):

  fuser /dev/video1 /dev/video2 /dev/video4     # whoever holds it is the real decoder

Cross-check in the browser at chrome://media-internals: kVideoDecoderName is V4L2VideoDecoder, and
kIsPlatformVideoDecoder is true.

The build this ran on (for reproducibility)

Nothing exotic; the point is it is stock trixie + backports, not a vendor BSP. This is a mainline
Debian desktop I put together for the 5B (my own image line, "Pi Phreak"):

  - Board:      Xunlong Orange Pi 5B, RK3588S (4x Cortex-A76 + 4x Cortex-A55), Mali-G610 MC4, 16 GB
  - OS:         Debian 13 (trixie), with trixie-backports enabled
  - Kernel:     7.1.3+deb13-arm64, mainline (stateless V4L2 decoders, panthor), booted with cma=1G
  - GPU stack:  Mesa 26.1.2 (~bpo13), Vulkan 1.4 via PanVK on Mali-G610 (loader 1.4.309), GLES 3.1
  - Compositor: Wayfire 0.11.0 on wlroots 0.20.2 (built from source; trixie ships 0.9), plus
                swaybg / waybar / wofi / foot
  - Media:      Chromium 151 (stock Debian) + the /etc/chromium.d flags, mpv 0.40, system libav =
                the Kwiboo v4l2-request 7.1.3 drop-in (7:7.1.3-phreak1, soname-matched to 7.1.5)

Two things to flag for anyone reproducing this: Mesa/PanVK come from trixie-backports (stock trixie
Mesa is older and PanVK is not 1.4 there, a separate "package version is not hardware capability"
trap), and the 16 GB headroom is what makes a 1 GB CMA reservation painless. On an 8 GB board I would
still bump past 256M (try 512M) but keep an eye on free RAM.

Credits: Kwiboo (Jonas Karlman) for the FFmpeg v4l2-request fork; Collabora / Jernej Skrabec for the
mainline stateless decoders; the dongioia/rock5bplus-rkvdec2 writeup for the Chromium-150 flag
findings; beryllium-org for the packaging reference and the VP9/VDPU381 kernel note. I only assembled
and measured; the hard part is theirs.

Happy to answer questions or hand over the packaging scripts if it is useful.
 

Peace,
Defcom5-Rockchip

"Got 2 Claudes and A Turntable"

Sorry I got my Flagship baking and excited working on my new Debian build with the above outlined and the honey its f in due list!
2 things I've learned about AI. 
1. Don't Trust Them, you have to tell them like they are children. (They act like they know).
2. Don't Trust Them.

Java UIO 2 is the next-generation evolution of the Java UIO project, rebuilt from the ground up to leverage the Foreign Function & Memory API (FFM). By moving beyond traditional JNI, Java UIO 2 achieves unprecedented performance and hardware-level accuracy for Linux Userspace IO. Engineered for JDK 25, it provides a cutting-edge cross-platform solution for modern embedded systems.

You will see a huge improvement in performance on 64 bit systems, but I've also included a script to build ARM 32 JDK 25 with FFM which currently doesn't exist. https://github.com/sgjava/javauio2#arm32-support--modern-ffm-back-to-the-future

I'm running code on my NanoPi Duo with an image built using standard Armbian build system. That means Ubuntu 26.04 LTS and JDK 25 on boards I bought in 2017. Love Armbian!

    _             _    _
   /_\  _ _ _ __ | |__(_)__ _ _ _
  / _ \| '_| '  \| '_ \ / _` | ' \
 /_/ \_\_| |_|_|_|_.__/_\__,_|_||_|

 v26.2.1 for Odroid N2 running Armbian Linux 6.18.10-current-meson64

 Packages:     Debian stable (trixie)
 IPv4:         (LAN) 192.168.1.63 (WAN) 82.137.57.14

 Performance:

 Load:         50%               Uptime:         1m
 Memory usage: 7% of 3.69G
 CPU temp:     40°C              Usage of /:   7% of 29G
 storage /:    1% of 916G

 Tips:

 What’s new in Armbian v26.5? https://tinyurl.com/5cwr7wfh

 Commands:

 Configuration: armbian-config
 Monitoring   : htop

Last login: Fri Jul 31 12:55:32 2026 from 192.168.1.58
root@nas:~# apt list
Error: Problem parsing Provides line of librust-servo-arc-dev:arm64=0.3.0-1+b1
Error: Error occurred while processing librust-servo-arc-dev (NewVersion2)
Error: Problem with MergeList /var/lib/apt/lists/deb.debian.org_debian_dists_trixie_main_binary-arm64_Packages
Error: The package lists or status file could not be parsed or opened.
root@nas:~# apt update
Ign:1 file:/var/cache/openmediavault/archives ./ InRelease
Ign:2 file:/var/cache/openmediavault/archives ./ Release
Get:3 file:/var/cache/openmediavault/archives ./ Packages
Hit:3 file:/var/cache/openmediavault/archives ./ Packages
Hit:5 http://deb.debian.org/debian trixie InRelease
Hit:6 http://deb.debian.org/debian trixie-updates InRelease
Hit:7 http://security.debian.org trixie-security InRelease
Hit:8 http://deb.debian.org/debian trixie-backports InRelease
Hit:9 http://security.debian.org/debian-security trixie-security InRelease
Hit:10 http://httpredir.debian.org/debian trixie InRelease
Hit:11 https://openmediavault.github.io/packages synchrony InRelease
Hit:12 http://httpredir.debian.org/debian trixie-updates InRelease
Hit:13 http://httpredir.debian.org/debian trixie-backports InRelease
Hit:14 https://github.armbian.com/configng stable InRelease
Hit:4 https://packages.openmediavault.org/public synchrony InRelease
Hit:15 http://fi.mirror.armbian.de/apt trixie InRelease
Traceback (most recent call last):
  File "/usr/sbin/omv-mkaptidx", line 236, in <module>
    sys.exit(main())
             ~~~~^^
  File "/usr/lib/python3/dist-packages/click/core.py", line 1161, in __call__
    return self.main(*args, **kwargs)
           ~~~~~~~~~^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3/dist-packages/click/core.py", line 1082, in main
    rv = self.invoke(ctx)
  File "/usr/lib/python3/dist-packages/click/core.py", line 1443, in invoke
    return ctx.invoke(self.callback, **ctx.params)
           ~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3/dist-packages/click/core.py", line 788, in invoke
    return __callback(*args, **kwargs)
  File "/usr/sbin/omv-mkaptidx", line 128, in main
    cache = apt.cache.Cache()
  File "/usr/lib/python3/dist-packages/apt/cache.py", line 158, in __init__
    self.open(progress)
    ~~~~~~~~~^^^^^^^^^^
  File "/usr/lib/python3/dist-packages/apt/cache.py", line 217, in open
    self._cache = apt_pkg.Cache(progress)
                  ~~~~~~~~~~~~~^^^^^^^^^^
apt_pkg.Error: E:Problem parsing Provides line of librust-servo-arc-dev:arm64=0.3.0-1+b1, E:Error occurred while processing librust-servo-arc-dev (NewVersion2), E:Problem with MergeList /var/lib/apt/lists/deb.debian.org_debian_dists_trixie_main_binary-arm64_Packages, E:The package lists or status file could not be parsed or opened.
Reading package lists... Error!
Error: Problem parsing Provides line of librust-servo-arc-dev:arm64=0.3.0-1+b1
Error: Error occurred while processing librust-servo-arc-dev (NewVersion2)
Error: Problem with MergeList /var/lib/apt/lists/deb.debian.org_debian_dists_trixie_main_binary-arm64_Packages
Error: The package lists or status file could not be parsed or opened.
root@nas:~#

I tried to remove all the sudo rm -vf /var/lib/apt/lists/partial/*, /var/lib/apt/lists/* folders, but nothing helped.

Can you please help me out? I hope @Nico the maintainer will see this!

Best regards,
Adam

The problem it's trying to solve: if you're picking hardware for a local voice/STT workload, vendor numbers don't tell you much and blog posts go stale fast. GOESB is meant to be the place you can actually check "does this board run faster-whisper medium in real time, or do I need to drop to tiny and eat the accuracy hit."
 

Right now the leaderboard is entirely x86 and Apple Silicon — Intel N150, an old Xeon, an Apple M1 Pro — because that's what we own. There isn't a single ARM/Rockchip result on it. If you're running Armbian on an RK3588 or RK3576 board (Orange Pi 5, NanoPC-T6, ROCK 5, NanoPi M5, whatever you've got), that's a genuine gap we can't fill ourselves.
 

Worth being upfront: GOESB doesn't do RKNN/NPU acceleration today — it benchmarks faster-whisper, vosk, and whisper-cpp, all CPU-based (or CUDA/Metal where available). On a Rockchip board it runs as a plain ARM64 Linux machine, no NPU involved. Still a useful number — a clean CPU baseline — just not a substitute for NPU-accelerated inference. New runtime adapters (including an RKNN one, if anyone's interested) go in as reviewed, in-tree pull requests, not a plugin system, so that's open if anyone wants to take it on.

Install and run:

curl -fsSL https://raw.githubusercontent.com/taktx-io/GOESB/main/scripts/install.sh | sh goesb

goesb with no arguments drops you into an arrow-key menu for picking a profile/pack and running + submitting — nothing to memorize.

This is still very much a product in development. We've tested it on our own hardware, not the huge range of boards that show up on Armbian, so install or runtime hiccups on something we haven't seen are plausible. If it breaks, please file it on GitHub rather than just walking away from it — that's the fastest way to get it fixed for the next board.

Have a look at https://www.goesb.com

I'm facing with a problem on gstreamer using the lastest armbian release (minimal option) with my rockpro64.

I try to play a mp4 video file with 

gst-launch-1.0 playbin uri=file:///home/adacast/default.mp4

as you can see in the attached picture there is a negociation capabilities with DMABuf but which has failed.

is there any fixes for this?

Regards

Narcisse

Looking at the kernel configs in this repo, many of them have CONFIG_RT_GROUP_SCHED=y. This does not play nicely with modern systemd (cgroups v2), breaking things like rtkit-daemon. See https://bugs.gentoo.org/569546 and https://bugzilla.redhat.com/show_bug.cgi?id=655321. rtkit is an important part of making pulseaudio and pipewire work smoothly, as well as for many other low-latency applications.

There are a few currently available workarounds, but none are ideal:
1. Linux 6.16 or later has boot time param rt_group_sched=0 to override it, but there is still some runtime overhead. No exact alternative for earlier kernels.
2. kernel.sched_rt_runtime_us=-1 in sysctl.conf -- potentially dangerous as it removes the 95% CPU time safeguard for RT processes, leading to lockups when badly behaving processes exist.
3. disable cpu and cpuset cgroup controllers in systemd configs -- has a lot of other side effects, like preventing systemd's CPU limits for services

Since the last post on this (linked above), forcefully assigning an rt time time slice won't even work anymore, since cgroup v2 doesn't even have that ability anymore. So this kernel config option is somewhat useless now.

# Board and kernel selection
BOARD="rock-4se"  # e.g., "odroidc4", "orangepi5", etc.
BRANCH="current"
RELEASE="jammy"  # or "bookworm" for Debian

# Build options
BUILD_MINIMAL="yes"
BUILD_DESKTOP="no"
KERNEL_CONFIGURE="no"
KERNEL_BTF=no

# Use custom kernel
KERNELSOURCE="https://git.kernel.org/pub/scm/linux/kernel/git/rt/linux-stable-rt.git"
KERNELBRANCH="tag:v5.15.92-rt57"

# Enable RT patch
KERNEL_USE_GCC="yes"
KERNEL_COMPILER="aarch64-linux-gnu-"  # or aarch64-linux-gnu- for ARM64

# Disable non-needed drivers
SKIP_EXTERNAL="yes"
SKIP_BOOTSPLASH="yes"
BUILD_KSRC="no"
ENABLE_WIRELESS="no"
BLUETOOTH_SUPPORT="no"
WIREGUARD="no"

DRIVER_UWE5622="no"
DRIVER_RTL8723DU="no"
DRIVER_RTL8723DS="no"

I stored it in userpatches/config-rock-4se.h and I compile using ./compile.sh rock-4se.

I get this error with wireless patches, it seems that they are not compatible with this kernel (?)

 

[🐳|🌱] * applying patch/misc/wireless-uwe5622/uwe5622-warnings.patch                                                                                                                   
[🐳|🔨]   The text leading up to this was:                                                                                                                                              
[🐳|🔨]   --------------------------                                                                                                                                                    
[🐳|🔨]   |diff --git a/net/bluetooth/hci_sync.c b/net/bluetooth/hci_sync.c                                                                                                             
[🐳|🔨]   |--- a/net/bluetooth/hci_sync.c       (revision 58aa050aa57333b34b358234002121c59fb3af26)                                                                                     
[🐳|🔨]   |+++ b/net/bluetooth/hci_sync.c       (revision bf8ab2f58b21494ffde96979431a3da931deb48b)                                                                                     
[🐳|🔨]   --------------------------                                                                                                                                                    
[🐳|🔨]   No file to patch.  Skipping patch.                                                                                                                                            
[🐳|🔨]   1 out of 1 hunk ignored                                                                                                                                                       
[🐳|💥] * applying patch/misc/wireless-uwe5622/uwe5622-park-link-v6.1-post.patch [ failed ]                                                                                             
[🐳|💥] error! [ Patching error, exiting.  ]                                                                                                                                            
[🐳|💥] Exiting with error 43 [ at /armbian/lib/functions/logging/traps.sh:1                                                                                                            
                exit_with_error() --> lib/functions/logging/traps.sh:1                                                                                                                  
             process_patch_file() --> lib/functions/compilation/patch/patching.sh:103                                                                                                   
                 driver_uwe5622() --> lib/functions/compilation/patch/drivers_network.sh:506                                                                                            
   kernel_drivers_prepare_harness() --> lib/functions/compilation/patch/drivers-harness.sh:160                                                                                          
   kernel_drivers_create_patches() --> lib/functions/compilation/patch/drivers-harness.sh:94                                                                                            
                  do_with_hooks() --> lib/functions/general/extensions.sh:603                                                                                                           
                do_with_logging() --> lib/functions/logging/section-logging.sh:81                                                                                                       
           kernel_main_patching() --> lib/functions/compilation/kernel-patching.sh:76                                                                                                   
                 compile_kernel() --> lib/functions/compilation/kernel.sh:54                                                                                                            
   artifact_kernel_build_from_sources() --> lib/functions/artifacts/artifact-kernel.sh:240                                                                                              
    artifact_build_from_sources() --> lib/functions/artifacts/artifacts-obtain.sh:34                                                                                                    
       obtain_complete_artifact() --> lib/functions/artifacts/artifacts-obtain.sh:280                                                                                                   
       build_artifact_for_image() --> lib/functions/artifacts/artifacts-obtain.sh:392                                                                                                   
    main_default_build_packages() --> lib/functions/main/build-packages.sh:102                                                                                                          
   full_build_packages_rootfs_and_image() --> lib/functions/main/default-build.sh:31                                                                                                    
          do_with_default_build() --> lib/functions/main/default-build.sh:42                                                                                                            
         cli_standard_build_run() --> lib/functions/cli/cli-build.sh:25                                                                                                                 
        armbian_cli_run_command() --> lib/functions/cli/utils-cli.sh:136                                                                                                                
                 cli_entrypoint() --> lib/functions/cli/entrypoint.sh:176                                                                                                               
                           main() --> compile.sh:50                                                                                                                                     
 ]                                                                                                                                                                                      
[🐳|💥] Cleaning up [ please wait for cleanups to finish ]

You can see that in the conf file I tried to disable this drivers but the patches are still being applied. I also try to remove all those patches but I got errors like this:

 

$ rm patch/misc/wireless-* -rf

$./compile.sh rock-4se
...
[🐳|🔨]   HEAD is now at 81306b3f6006 'Linux 5.15.92-rt57'
[🐳|🌱] Preparing driver [ driver_generic_bring_back_ipx ]
[🐳|🌱] Reverting upstream-removed [ IPX stuff needed for Wireless Drivers ]
/armbian/patch/misc/wireless-bring-back-headers.patch: No such file or directory
patch: **** Can't open patch file /armbian/patch/misc/wireless-bring-back-headers.patch : No such file or directory
[🐳|💥] * applying patch/misc/wireless-bring-back-headers.patch [ failed ]
[🐳|💥] error! [ Patching error, exiting.  ]
[🐳|💥] Exiting with error 43 [ at /armbian/lib/functions/logging/traps.sh:1
                exit_with_error() --> lib/functions/logging/traps.sh:1
             process_patch_file() --> lib/functions/compilation/patch/patching.sh:103
   driver_generic_bring_back_ipx() --> lib/functions/compilation/patch/drivers_network.sh:33
   kernel_drivers_prepare_harness() --> lib/functions/compilation/patch/drivers-harness.sh:160
   kernel_drivers_create_patches() --> lib/functions/compilation/patch/drivers-harness.sh:94
                  do_with_hooks() --> lib/functions/general/extensions.sh:603
                do_with_logging() --> lib/functions/logging/section-logging.sh:81
           kernel_main_patching() --> lib/functions/compilation/kernel-patching.sh:76
                 compile_kernel() --> lib/functions/compilation/kernel.sh:54
   artifact_kernel_build_from_sources() --> lib/functions/artifacts/artifact-kernel.sh:240
    artifact_build_from_sources() --> lib/functions/artifacts/artifacts-obtain.sh:34
       obtain_complete_artifact() --> lib/functions/artifacts/artifacts-obtain.sh:280
       build_artifact_for_image() --> lib/functions/artifacts/artifacts-obtain.sh:392
    main_default_build_packages() --> lib/functions/main/build-packages.sh:102
   full_build_packages_rootfs_and_image() --> lib/functions/main/default-build.sh:31
          do_with_default_build() --> lib/functions/main/default-build.sh:42
         cli_standard_build_run() --> lib/functions/cli/cli-build.sh:25
        armbian_cli_run_command() --> lib/functions/cli/utils-cli.sh:136
                 cli_entrypoint() --> lib/functions/cli/entrypoint.sh:176
                           main() --> compile.sh:50
 ]
[🐳|💥] Cleaning up [ please wait for cleanups to finish ]
...

how can I fix this issue and compile that kernel branch?

Last time, the OMV install from Armbian-Config worked like a dream. Load it, update it and then click OMV in the menu. Simples!

This time it runs a lot of script as before, then finishes with "error openmediavault". That's it. The web browser says "Welcome to NGINX", so something has been installed. Ive tried an install and running the Debian scrip from the OMV GITHUB and it does not like that at all. Errors in BASH immediately.

So currently hoping for updates (from Armbian I guess?). I'm using latest Bullseye and I guess Armbian-Config is trying to install V6?

The reason of my question is, I have running homeassistant on a orangepi pc2 which work very well. On the raspberrypi 3B+ running unter raspbian, homeassistant is very slow. 

Download Armbian with HA (v25.2)
Then boot the image, wait few minutes and login via http://ip_address_of_armbian_running_ha:8123 (official onboarding manual)

Home Assistant Supervised is, more or less, a full blown Home assistant.

Install Home Assistant on any Armbian Bookworm (experimental)

Main difference between HA OS and Armbian with HA is that underlying OS here is clean Armbian Debian Bookworm and there is custom dedicated buildroot OS that is provided for a few single board computers, primarily for Raspberry Pi. We provide HA on a small selection of single board computers, but in theory, its possible to run this on (almost) all that are possible to build.
 

Quote

Changes to Armbian OS are minimal as HA is running under Docker.

I am running HA on Odroid N2+ and it works without any problems. I have z-wave network with sensors and switches, air humidifier, Android TV, Android phones, dishwasher, ... Things works flawlessly, much better then few years back when I started with home automation for a first time, with OpenHab. This time it was setup from scratch and in a matter of days, most of devices are in function, playing with automation.

Tested on:

• Odroid N2/N2+
• Odroid M1
• Nanopi R4S
• Rock 5B
• Uefi-x86
• Orangepi 5
• Nanopi M6
• Rpi400
• Khadas VIM1S
• Khadas VIM4 (Amlogic vendor kernel trouble, failing / need inspection)
• Bananapi M2 Pro

Provided for but untested (images you find on board downloads locations, seek them here https://www.armbian.com/download/😞

Bananapicm4io
Bananapim2s
Bananapim5
Bigtreetech-cb1
Khadas-edge2
Khadas-vim1
Khadas-vim2
Khadas-vim3
Khadas-vim3l
Lafrite
Lepotato
Nanopi-r6s
Odroidn2l
Onecloud
Orangepi4-lts
Orangepi5
Orangepi5-plus
Renegade
Rockpi-e
Rockpro64
Rpi4b
Rpi5b
Sk-am62b
Sk-am64b
Sk-tda4vm
Tinkerboard
Tritium-h5
Uefi-arm64

DIY

./compile.sh BOARD="uefi-x86" BRANCH=current RELEASE=bookworm ENABLE_EXTENSIONS="ha" KERNEL_CONFIGURE="no" BUILD_MINIMAL="yes"

Contribute

Support:

The supervised installation method on Armbian is not officially supported by the Home Assistant project. Additionally, installation on hardware that is not officially supported is also outside the scope of support provided by the Armbian team.

You are welcome to report high-level application issues that are reproducible on the official Home Assistant Operating System (HAOS) within the Home Assistant community or here on this forum. For any hardware-related topics, you may use the this forum; however, please be aware that official support from the Armbian team is not guaranteed.
 

• single board computer hardware https://www.armbian.com/bugs
• home assistant functions https://community.home-assistant.io/ 
  (make sure to bring up only issues that are application related, high level issues, that are likely present in official HAOS software)

Sometimes it can be handy to login via Remote desktop to my machine.

I enabled RDP through armbian -config, but I can not remote desktop to the machine. When i connect trough renmina or windows rdp, i get the xrdp login screen, but when i enter user and pasword, i get thrown out of the programm, be it srenmina or windows remote desktop. So the problem seems to be on the armbian side.

Any suggestions where to look to fix shis?

Armbian version 22.11.1 running on odroid C4.

Thks in advance

How do I install the correct Linux headers? The standard apt install linux-headers-$(uname -r) method doesn't work for armbian.
OK, there's a corresponding option in armbian-config, and it seems to run successfully, but for some reason, I only see linux-headers-6.12.74+deb13+1-arm64 and linux-headers-6.12.74+deb13+1-common in /usr/src.

Starts with a blank screen and hard crashing, see fault log.

Workaround is to use to download the deb. version as can be found on Github: https://github.com/armbian/imager/releases

Greets

crasharmbianKubuntu26.04

Running system on AMD64

crasharmbianKubuntu26.04

I'm running a few services on an Armbian-based SBC and need a reliable SMTP Service Provider for system alerts, backup reports, and application notifications.

Has anyone here used SMTP Service Provider iDealSMTP with Armbian, or compared it with other SMTP solutions for lightweight ARM servers? I'm interested in deliverability, ease of setup, and long-term reliability.

I'd appreciate any experiences or recommendations. Thanks!

Special thanks to Jamie Sinclair for creating and sharing the opifancontrol project with the community.

I have an Orange Pi 5 Max installed in a metal case and running several Docker containers, including Frigate, Immich, Samba, and others. The case originally came with a internal 30x30x10 mm fan, which was not able to provide sufficient cooling. Under load, CPU temperatures were reaching nearly 70°C.

To improve cooling, I installed an external 40x40x10 mm PWM fan that was originally used on an Odroid HC4. The fan was mounted using screws, which required drilling holes in the case cover. I also added several ventilation holes, in the case cover above the CPU area to improve airflow. After these modifications, the CPU temperature now stays around 48°C.

1. Install wiringOP

Follow the instructions from the wiringOP project:

 Download wiringOP

 $ apt-get update
 $ apt-get install -y git
 $ git clone https://github.com/orangepi-xunlong/wiringOP.git

 Build wiringOP

 $ cd wiringOP
 $ ./build clean
 $ ./build

 Verify the installation:

 $ gpio readall

This command should display the Orange Pi 5 Max GPIO pin map.

2. Configure GPIO Pin 7 as a PWM Output

 In Armbian, configure GPIO Pin 7 (PWM3_IR_M3) as a PWM output.

 $ sudo armbian-config

 Navigate to:

 System
 └─ Kernel
      └─ Overlays

 Select:

  rk3588-pwm3-m3

  Press the space bar to enable it, save the configuration, and reboot the system.

3. Install opifancontrol: https://github.com/jamsinclair/opifancontrol

 $ su
 $ cd /usr/local/bin/
 $ wget https://github.com/jamsinclair/opifancontrol/blob/main/opifancontrol.sh
 $ chmod +x /usr/local/bin/opifancontrol.sh

 $ curl -sSL https://raw.githubusercontent.com/jamsinclair/opifancontrol/main/install.sh | bash

Enable the service to start automatically at boot:

 $ systemctl enable opifancontrol.service

Start the service:

 $ systemctl start opifancontrol.service

Check the service status:

 $ systemctl status opifancontrol.service

4. PWM Fan Wiring

 I used a 5V, 4-wire, 4,000 RPM fan from an Odroid HC4.

 Connection details:

 Fan Wire   Function                     GPIO Pin

 Red            +5V Power                    Pin 4

 Black          GND                              Pin 6

 Blue            PWM Speed Control  Pin 7

 Yellow        TACH (RPM Sensor)    Not Connected

5. Adjust the Fan Control Configuration

Edit the configuration file:

 $ sudo nano /etc/opifancontrol.conf

 My settings are:

 TEMP_LOW=45
 FAN_LOW=60

 TEMP_MED=60
 FAN_MED=75

 TEMP_HIGH=70
 FAN_HIGH=100

 RAMP_UP_DELAY_SECONDS=30
 RAMP_DOWN_DELAY_SECONDS=60

After saving the configuration file, restart the service:

 $ sudo systemctl stop opifancontrol.service

 $ sudo systemctl start opifancontrol.service

With these settings and the hardware modifications described above, my Orange Pi 5 Max now operates significantly cooler, maintaining temperatures around 48°C while running multiple Docker services

I installed a fresh `Armbian_23.02.2_Nanopim4v2_bullseye_current_5.15.93_minimal.img.xz` for the Nanopi M4v2. But when I try to install `armbian-config' after an `apt update`, I got following error:
 

root@nanopim4v2:~# apt install armbian-config
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Package armbian-config is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source

E: Package 'armbian-config' has no installation candidate

also checked the apt-cache:

apt-cache showpkg armbian-config
Package: armbian-config
Versions:

Reverse Depends:
  armbian-bsp-cli-nanopim4v2,armbian-config
Dependencies:
Provides:
Reverse Provides:

Also tried the `3rd party Debian based distributions`from https://github.com/armbian/config, but got the same error.

There is also a second unsolved thread:

I stay now with the non-minimal, but is there a solution for future using of the minimal with armbian-config?

Thanks and greeting!

I’m facing yet another strange problem, and I am posting it here as well, because I think it could be OS related.

Some details about my server:

• Armbian 26.2.1 trixie
• Nginx
• Nextcloud (latest)
• MariaDB
• Letsencrypt (updated 3 weeks ago)

Until a few days ago, every browser on any of my devices could call the web gui of my server and Nextcloud presented its login page. Then, after the latest OS update, suddenly browsers tell my they can’t connect to the server, but every synching app on any of devices still work perfectly! And I can even access my files on the server by using FolderSync’s¹ internal file browser.

It is just the browsers that can’t connect any more, no matter which browser, no matter which device! There is no error message in the appropriate log files, neither in the system log, nor in Nextcloud’s own log, and the message that the browsers present is simply some variation of “I can’t connect to server”. No specific reason, no error code.

This is more than strange to me. I would get it if synching apps would have stopped working as well, but that is not the case. Does any one have an explanation for this mystery? If you need more information, just let my know!

Many thanks in advance!

(¹ Synching app on Android.)

What is causing this issue?

The official Orange Pi kernel version (Orangepizero3_1.0.4_debian_bookworm_desktop_xfce_linux6.1.31) does not have this problem and runs automatically.

Instead, I get the error: “dbus can't connect to fcitx5.”

Every time I need to open the fcitx5 settings again and click “Run” before I can input Chinese.
I have no idea what is going on.

Thanks.

# apt full-upgrade
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
The following packages have been kept back:
  libnvpair3linux libuutil3linux zfs-dkms zfsutils-linux
0 upgraded, 0 newly installed, 0 to remove and 4 not upgraded.

See that zfsutils-linux depends on libc6 >= 2.38 :

# apt show zfsutils-linux
Package: zfsutils-linux
Version: 2.4.1-1
Priority: optional
Section: contrib/admin
Source: zfs-linux
Maintainer: Debian ZFS on Linux maintainers <pkg-zfsonlinux-devel@alioth-lists.debian.net>
Installed-Size: 2,415 kB
Provides: zfsutils
Depends: libnvpair3linux (= 2.4.1-1), libuutil3linux (= 2.4.1-1), libzfs7linux (= 2.4.1-1), libzpool7linux (= 2.4.1-1), python3, gawk, libblkid1 (>= 2.16), libc6 (>= 2.38), libssl3t64 (>= 3.0.0), libudev1 (>= 183), libuuid1 (>= 2.16)
Recommends: zfs-modules | zfs-dkms, zfs-zed
Suggests: nfs-kernel-server, samba-common-bin (>= 3.0.23), zfs-initramfs | zfs-dracut
Conflicts: zfs, zfs-fuse
Breaks: spl (<< 0.7.9-2), spl-dkms (<< 0.8.0~rc1), zfs-dkms (>> 2.4.1-1...), zfs-dkms (<< 2.4.1-1)
Replaces: spl (<< 0.7.9-2), spl-dkms
Homepage: https://zfsonlinux.org/
Download-Size: 580 kB
APT-Sources: http://apt.armbian.com bookworm/bookworm-utils arm64 Packages
Description: command-line tools to manage OpenZFS filesystems

But only 2.36 only is available on Bookworm: https://packages.debian.org/bookworm/libc6

What are we supposed to do ? it looks like a build issue on zfs packages.

The directory could not be established:
Microsoft Edge has no Read/Write access rights to its directory:

C:\Users\admin\AppData\Local\com.armbian.imager\EBWebView

Should the same issue have been posted here somewhere else, I do apologize. However, before creating the help request I did try to find any entries of similar content, but in vain.

So if there's already any remedial comment on this available in the Armbian community, please provide the link.
Thanks a lot in advance. 

Meanwhile I managed to run it, however only after starting up Win11 as admin and explicitly running the programme as such.
On the contrary, if I start the OS directly into my simple user account and then try to run Armbian-Imager from there, both as regular user OR as admin, it will refuse to do its job by sending the above failure message. 

1) use the cross platform PoC written in C, the Python one that everyone is sharing contains obfuscated code (bad ju-ju) and is x86_64 specific

`git clone https://github.com/tgies/copy-fail-c`

`cd copy-fail-c`

2) compile either on your target device natively, or do what I did and cross-compile it as a static binary using an aarch64-linux-musl toolchain (this made it easy to test on different SBCs)

`PREFIX="/opt/toolchains/aarch64-linux-musl-cross" CC=aarch64-linux-musl-gcc LD=aarch64-linux-musl-ld CFLAGS="-static -fPIC -I/opt/toolchains/aarch64-linux-musl-cross/include -L/opt/toolchains/aarch64-linux-musl-cross/lib" LDFLAGS="-static -fPIE -L/opt/toolchains/aarch64-linux-musl-cross/lib" make -j$(nproc --all)`

3) pass the resulting binaries "payload" and "exploit" to your target device (if you cross compiled)

4) from an unprivileged user account not in the sudo group, run the exploit

I'm not here to point fingers but I would like to see AT LEAST an advisory of this potentially devastating bug with a public exploit available on the Armbian homepage, radio silence for over a week seems completely inappropriate to me

This is a bit surprising because the hardware was designed for running Android. I was not running much else, just Wayfire and one or two Alacritty consoles. I don't think I was running out of memory. Is it possible to get decent Waydroid performance on other arm64 hardware?

I’ve been a lurker for a while and recently flashed the latest Armbian Jammy onto a spare NanoPi NEO I had lying around. I'm currently designing a headless DIY time-tracking kiosk for a small local workshop using an RC522 RFID reader via SPI.

Reading the RFID tags and logging the raw Unix timestamps (punch-in/punch-out) to a local SQLite database was the easy part. Where I'm getting a bit stuck is the actual backend calculation logic. I need the system to accurately calculate the daily net working hours, which means automatically deducting mandatory statutory breaks (e.g., 30 mins after 6 hours of work) and tracking daily overtime.

To ensure the math is strictly accurate and handles edge cases properly, I am trying to write a Python script that replicates the exact calculation logic used by standard tools like arbeitszeitrechnerprofi.de for the backend processing.

Before I completely reinvent the wheel writing complex Python datetime scripts, has anyone here built a similar attendance or punch-clock project on Armbian?

What’s the best way to handle this data processing locally?

Would it be better to just use Node-RED for easier visual flow and logic management rather than a standalone Python daemon?

Also, any tips on GPIO reliability for the RFID reader under the recent Armbian kernels would be highly appreciated. I plan to start wiring the prototype this weekend. Thanks in advance!

armbian-leds.conf | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/armbian-leds.conf b/armbian-leds.conf
index 8108230..537ea6f 100644
--- a/armbian-leds.conf
+++ b/armbian-leds.conf
@@ -5,5 +5,5 @@ invert=0

[/sys/class/leds/rtw88-1-1.1:1.0]
trigger=phy0tpt
-brightness=1
+brightness=0 

What is this mess?
What is it for?

• I have a Helios64 NAS with 4 x HDDs running Armbian 25.11.2 with kernel 6.12.58.
• The HDDs each have a ZFS partition but the partitions aren't imported.
• The OS is running from an sd card and logging is to ram.
• Power management and spin-down on the HDDs is disabled.

Despite all this *something* is causing the heads to move every second or two.

iotop shows no disk activity . lsof +d /mnt/sda etc. shows no open files and fatrace shows files in /usr and /var but nothing on /dev/sda etc.

So, whilst it doesn't look as if any files are being accessed the HDDs are still doing something. The question is WHAT and how do I stop it ?

Any ideas ?

noticed that on the sbc "apt-get update" takes a long time,

it ignores some sources and sometimes it slow to load.

was wondering if could clean up the process, since it seem to look for "i386" but the sbc is on "arm64"

sudo apt update
[sudo] password for rich: 
OK:1 http://ports.ubuntu.com noble InRelease
Holen:2 http://ports.ubuntu.com noble-security InRelease [126 kB]              
Holen:4 https://github.armbian.com/configng stable InRelease [5.467 B]         
Holen:5 https://dl.winehq.org/wine-builds/ubuntu questing InRelease [5.719 B]  
Holen:6 http://ports.ubuntu.com noble-updates InRelease [126 kB]    
Holen:7 http://ports.ubuntu.com noble-backports InRelease [126 kB]             
Holen:3 http://armbian.lv.auroradev.org/apt noble InRelease [39,2 kB]          
Holen:8 https://github.armbian.com/configng stable/main arm64 Packages [437 B]
Holen:9 https://github.armbian.com/configng stable/main i386 Packages [437 B]
Holen:10 https://dl.winehq.org/wine-builds/ubuntu questing/main amd64 Packages [60,8 kB]
Holen:11 http://ports.ubuntu.com noble/main i386 Packages [1.329 kB]
Ign:11 http://ports.ubuntu.com noble/main i386 Packages                        
Ign:13 http://ports.ubuntu.com noble/restricted i386 Packages                  
Ign:14 http://ports.ubuntu.com noble/universe i386 Packages                    
Ign:15 http://ports.ubuntu.com noble/multiverse i386 Packages                  
Ign:16 http://ports.ubuntu.com noble-security/main i386 Packages               
Holen:17 http://ports.ubuntu.com noble-security/main arm64 Packages [2.092 kB] 
Holen:18 https://dl.winehq.org/wine-builds/ubuntu questing/main amd64 Contents (deb) [99,8 kB]
Holen:19 http://armbian.lv.auroradev.org/apt noble/noble-utils all Packages [3.136 B]
Holen:20 http://armbian.lv.auroradev.org/apt noble/noble-utils i386 Packages [3.709 B]
Holen:21 http://armbian.lv.auroradev.org/apt noble/noble-utils arm64 Packages [18,3 kB]
Holen:22 http://armbian.lv.auroradev.org/apt noble/noble-desktop arm64 Packages [137 kB]
Holen:23 http://ports.ubuntu.com noble-security arm64 Contents (deb) [191 MB]  
Holen:24 http://ports.ubuntu.com noble-security i386 Contents (deb) [61,1 MB]  
Ign:25 http://ports.ubuntu.com noble-security/restricted i386 Packages         
Holen:26 http://ports.ubuntu.com noble-security/restricted arm64 Packages [4.844 kB]
Ign:27 http://ports.ubuntu.com noble-security/universe i386 Packages           
Holen:28 http://ports.ubuntu.com noble-security/universe arm64 Packages [1.505 kB]
Ign:29 http://ports.ubuntu.com noble-security/multiverse i386 Packages         
Holen:30 http://ports.ubuntu.com noble-security/multiverse arm64 Packages [44,1 kB]
Ign:31 http://ports.ubuntu.com noble-updates/main i386 Packages                
Holen:32 http://ports.ubuntu.com noble-updates/main arm64 Packages [2.451 kB]  
Holen:32 http://ports.ubuntu.com noble-updates/main arm64 Packages [2.451 kB]  
Holen:34 http://ports.ubuntu.com noble-updates arm64 Contents (deb) [199 MB]   
Holen:34 http://ports.ubuntu.com noble-updates arm64 Contents (deb) [199 MB]
Holen:36 http://ports.ubuntu.com noble-updates i386 Contents (deb) [66,0 MB]   
Holen:37 http://ports.ubuntu.com noble-updates/restricted arm64 Packages [5.019 kB]
Ign:38 http://ports.ubuntu.com noble-updates/restricted i386 Packages          
Holen:39 http://ports.ubuntu.com noble-updates/universe arm64 Packages [2.116 kB]
Holen:39 http://ports.ubuntu.com noble-updates/universe arm64 Packages [2.116 kB]
Ign:41 http://ports.ubuntu.com noble-updates/universe i386 Packages            
Holen:42 http://ports.ubuntu.com noble-updates/multiverse arm64 Packages [45,7 kB]
Ign:43 http://ports.ubuntu.com noble-updates/multiverse i386 Packages          
Ign:44 http://ports.ubuntu.com noble-backports/main i386 Packages              
Holen:45 http://ports.ubuntu.com noble-backports arm64 Contents (deb) [786 kB] 
Ign:46 http://ports.ubuntu.com noble-backports/universe i386 Packages          
Holen:47 http://ports.ubuntu.com noble-backports/universe arm64 Packages [36,1 kB]
Ign:48 http://ports.ubuntu.com noble-backports/multiverse i386 Packages        
Ign:11 http://ports.ubuntu.com noble/main i386 Packages                        
Ign:13 http://ports.ubuntu.com noble/restricted i386 Packages                  
Ign:14 http://ports.ubuntu.com noble/universe i386 Packages                    
Ign:15 http://ports.ubuntu.com noble/multiverse i386 Packages                  
Ign:16 http://ports.ubuntu.com noble-security/main i386 Packages               
Ign:25 http://ports.ubuntu.com noble-security/restricted i386 Packages         
Ign:27 http://ports.ubuntu.com noble-security/universe i386 Packages           
Ign:29 http://ports.ubuntu.com noble-security/multiverse i386 Packages         
Ign:31 http://ports.ubuntu.com noble-updates/main i386 Packages                
Ign:38 http://ports.ubuntu.com noble-updates/restricted i386 Packages          
Ign:41 http://ports.ubuntu.com noble-updates/universe i386 Packages            
Ign:43 http://ports.ubuntu.com noble-updates/multiverse i386 Packages          
Ign:44 http://ports.ubuntu.com noble-backports/main i386 Packages              
Ign:46 http://ports.ubuntu.com noble-backports/universe i386 Packages          
Ign:48 http://ports.ubuntu.com noble-backports/multiverse i386 Packages        
Ign:11 http://ports.ubuntu.com noble/main i386 Packages                        
Ign:13 http://ports.ubuntu.com noble/restricted i386 Packages                  
Ign:14 http://ports.ubuntu.com noble/universe i386 Packages                    
Ign:15 http://ports.ubuntu.com noble/multiverse i386 Packages                  
Ign:16 http://ports.ubuntu.com noble-security/main i386 Packages               
Ign:25 http://ports.ubuntu.com noble-security/restricted i386 Packages         
Ign:27 http://ports.ubuntu.com noble-security/universe i386 Packages           
Ign:29 http://ports.ubuntu.com noble-security/multiverse i386 Packages         
Ign:31 http://ports.ubuntu.com noble-updates/main i386 Packages                
Ign:38 http://ports.ubuntu.com noble-updates/restricted i386 Packages          
Ign:41 http://ports.ubuntu.com noble-updates/universe i386 Packages            
Ign:43 http://ports.ubuntu.com noble-updates/multiverse i386 Packages          
Ign:44 http://ports.ubuntu.com noble-backports/main i386 Packages              
Ign:46 http://ports.ubuntu.com noble-backports/universe i386 Packages          
Ign:48 http://ports.ubuntu.com noble-backports/multiverse i386 Packages        
Ign:11 http://ports.ubuntu.com noble/main i386 Packages                        
Ign:13 http://ports.ubuntu.com noble/restricted i386 Packages                  
Ign:14 http://ports.ubuntu.com noble/universe i386 Packages                    
Ign:15 http://ports.ubuntu.com noble/multiverse i386 Packages                  
Ign:16 http://ports.ubuntu.com noble-security/main i386 Packages               
Ign:25 http://ports.ubuntu.com noble-security/restricted i386 Packages         
Ign:27 http://ports.ubuntu.com noble-security/universe i386 Packages           
Ign:29 http://ports.ubuntu.com noble-security/multiverse i386 Packages         
Ign:31 http://ports.ubuntu.com noble-updates/main i386 Packages                
Ign:38 http://ports.ubuntu.com noble-updates/restricted i386 Packages          
Ign:41 http://ports.ubuntu.com noble-updates/universe i386 Packages            
Ign:43 http://ports.ubuntu.com noble-updates/multiverse i386 Packages          
Ign:44 http://ports.ubuntu.com noble-backports/main i386 Packages              
Ign:46 http://ports.ubuntu.com noble-backports/universe i386 Packages          
Ign:48 http://ports.ubuntu.com noble-backports/multiverse i386 Packages        
Ign:11 http://ports.ubuntu.com noble/main i386 Packages                        
Ign:13 http://ports.ubuntu.com noble/restricted i386 Packages                  
Ign:14 http://ports.ubuntu.com noble/universe i386 Packages                    
Ign:15 http://ports.ubuntu.com noble/multiverse i386 Packages                  
Ign:16 http://ports.ubuntu.com noble-security/main i386 Packages               
Ign:25 http://ports.ubuntu.com noble-security/restricted i386 Packages         
Ign:27 http://ports.ubuntu.com noble-security/universe i386 Packages           
Ign:29 http://ports.ubuntu.com noble-security/multiverse i386 Packages         
Ign:31 http://ports.ubuntu.com noble-updates/main i386 Packages                
Ign:38 http://ports.ubuntu.com noble-updates/restricted i386 Packages          
Ign:41 http://ports.ubuntu.com noble-updates/universe i386 Packages            
Ign:43 http://ports.ubuntu.com noble-updates/multiverse i386 Packages          
Ign:44 http://ports.ubuntu.com noble-backports/main i386 Packages              
Ign:46 http://ports.ubuntu.com noble-backports/universe i386 Packages          
Ign:48 http://ports.ubuntu.com noble-backports/multiverse i386 Packages        
Fehl:11 http://ports.ubuntu.com noble/main i386 Packages                       
  404  Not Found [IP: 91.189.92.20 80]
Ign:13 http://ports.ubuntu.com noble/restricted i386 Packages                  
Ign:14 http://ports.ubuntu.com noble/universe i386 Packages                    
Ign:15 http://ports.ubuntu.com noble/multiverse i386 Packages                  
Fehl:16 http://ports.ubuntu.com noble-security/main i386 Packages              
  404  Not Found [IP: 91.189.92.20 80]
Ign:25 http://ports.ubuntu.com noble-security/restricted i386 Packages         
Ign:27 http://ports.ubuntu.com noble-security/universe i386 Packages           
Ign:29 http://ports.ubuntu.com noble-security/multiverse i386 Packages         
Fehl:31 http://ports.ubuntu.com noble-updates/main i386 Packages               
  404  Not Found [IP: 91.189.92.20 80]
Ign:38 http://ports.ubuntu.com noble-updates/restricted i386 Packages          
Ign:41 http://ports.ubuntu.com noble-updates/universe i386 Packages            
Ign:43 http://ports.ubuntu.com noble-updates/multiverse i386 Packages          
Fehl:44 http://ports.ubuntu.com noble-backports/main i386 Packages             
  404  Not Found [IP: 91.189.92.20 80]
Ign:46 http://ports.ubuntu.com noble-backports/universe i386 Packages          
Ign:48 http://ports.ubuntu.com noble-backports/multiverse i386 Packages        
Es wurden 537 MB in 2 min 2 s geholt (4.394 kB/s).                             
Paketlisten werden gelesen… Fertig
E: Fehlschlag beim Holen von http://ports.ubuntu.com/dists/noble/main/binary-i386/Packages 404  Not Found [IP: 91.189.92.20 80]
E: Fehlschlag beim Holen von http://ports.ubuntu.com/dists/noble-security/main/binary-i386/Packages 404  Not Found [IP: 91.189.92.20 80]
E: Fehlschlag beim Holen von http://ports.ubuntu.com/dists/noble-updates/main/binary-i386/Packages 404  Not Found [IP: 91.189.92.20 80]
E: Fehlschlag beim Holen von http://ports.ubuntu.com/dists/noble-backports/main/binary-i386/Packages 404  Not Found [IP: 91.189.92.20 80]
E: Einige Indexdateien konnten nicht heruntergeladen werden. Sie wurden ignoriert oder alte an ihrer Stelle benutzt.

thank you

surf.py

ip a reports:

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host noprefixroute 
       valid_lft forever preferred_lft forever
2: end0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether be:63:9c:35:dd:4f brd ff:ff:ff:ff:ff:ff
    inet 192.168.71.2/24 brd 192.168.71.255 scope global noprefixroute end0
       valid_lft forever preferred_lft forever
    inet6 fe80::bc63:9cff:fe35:dd4f/64 scope link 
       valid_lft forever preferred_lft forever

ip r reports:

192.168.71.0/24 dev end0 proto kernel scope link src 192.168.71.2 metric 100 
gene@amanda:~$ 

A ping -c1 yahoo.com kills enough time its several seconds before it reports "network is unreachable"

Can you see whats wrong, or give me the newer tracing tools to find  the error?

Thank you.

I have cubiboard 1. I see boot from sd card, system on sata,usb and nvme but i want  boot from nand, system on sata,usb and nvme. 

I was running a Radxa CM5 with a Waveshare CM4 Nano-C board, using an Armbian image for the Rock 5A. This was the only way I could get it working with mainline support. I’m aware this setup is far from standard I’m essentially using the wrong image but that’s because the Radxa CM5 IO board isn’t compatible with the Waveshare Nano board. On top of that, Armbian doesn’t officially support the CM5 RPi-CM4 IO board provided by Radxa (which does work with the Waveshare Nano, but their image is extremely unstable updating it to Trixie bricks the system).

The main issue I noticed was with Wi-Fi (using a USB Wi-Fi AC dongle). By default, it’s broken. I managed to restore it using armbian-config and network setup, but even then, the system doesn’t show any Wi-Fi options in Network Manager, despite being connected and working.

I didn’t report this earlier because my setup is quite unusual, and I couldn’t be sure if the issue was specific to me.
However, today I tested something else.
I revived my MSI GS73VR (a 2017 x86 laptop with a GTX 1060) and tried several Linux distributions. I ended up installing Armbian UEFI (the x86 version of Armbian Trixie). As a side note, the Trixie download link on the website is broken you have to dig through the internal download pages to find it.

After installing it on an NVMe drive and completing the setup, everything initially worked fine. But after one reboot, I encountered the same Wi-Fi issue: freezing and inconsistent behavior. This time, I hadn’t used armbian-config or any network tweaks. The system doesn’t properly detect or display Wi-Fi in GNOME settings, even though it is actually connected and working in the background.

So this seems to be a broader issue, not just related to my ARM setup.
I don’t know exactly what’s wrong with Armbian, but my main criticism has always been Wi-Fi support—especially for USB dongles. It feels poorly maintained and lacks consistency. I was told years ago that mainline support would resolve these issues, but Armbian UEFI on x86 should already be at that stage, shouldn’t it?

Something clearly isn’t right here. It’s frustrating because this feels like the last missing piece for an otherwise solid system.
Despite my criticism, I’ll admit Armbian has grown on me. On x86, there are better alternatives like Fedora, but on ARM, Armbian is still one of the best options.

Anyway, apologies if this is posted in the wrong place. The official channels require logs, and I don’t feel like rebuilding my old broken setup just to gather them. If no logs means no help, then so be it. Maybe I’m the only one experiencing this—but I doubt it. Most people probably just plug in Ethernet and avoid dealing with Wi-Fi altogether.
It is what it is.

The problem

I run a Kobol Helios64 as my home NAS — a five-bay ARM board that's been sitting in a sweet spot between "serious hardware" and "abandoned by its software ecosystem." I tried the usual NAS UIs. They were either too heavy, too opinionated about owning the underlying OS, or simply unmaintained. None of them gave me a clean window into my ZFS pools without dragging in a container runtime, a Node.js server, or a Python daemon alongside them.

I wanted something simple: observe and manage my storage from a browser, on a machine that stays close to a vanilla Armbian or FreeBSD install. No agents, no frameworks, no surprises.

What I built

dumpstore — a lightweight ZFS management UI written in Go. link: https://github.com/langerma/dumpstore

It's a single compiled binary with a bunge of html/js/css/ansible playbooks. No database. No Node. No container runtime.

Ansible handles writes (dataset creation, snapshots, user/group management, ACLs)

Current features:

• Pool overview — health, usage, vdev tree, fragmentation
• Live I/O statistics per pool (SSE-pushed, no polling)
• S.M.A.R.T. data per disk — temperature, power-on hours, reallocated sectors
• Dataset browser — collapsible tree, compression, quota, mountpoint
• Dataset create / edit / delete
• Snapshot management — list, create (recursive), delete
• User & group management — create, edit, delete; system users protected
• ACL management — POSIX and NFSv4, recursive apply supported
• Prometheus /metrics endpoint (because of course)
• Runs on Linux (systemd) and FreeBSD (rc.d)
• Builds with make build && sudo make install — that's it

What it is not: a full TrueNAS replacement.

SMB/NFS share management, a file browser, and ZFS send/receive are on the roadmap — but I'm building deliberately, one thing at a time.

Why Armbian specifically

The Helios64 is the reason this exists. If you're running Armbian on a Helios64, an older ARM server, or any ZFS box where you care about what's actually installed — this was built for you.

Feedback welcome

Since I'm not a developer by trade, I'm sure there are things I've done in a way that makes experienced Go or software folks cringe.

Issues, PRs, and honest feedback are very welcome.

The code is small enough to be auditable — main.go plus a handful of internal packages.

Markus Langer

Quote

verbosity=1
bootlogo=false
console=serial
overlay_prefix=sun8i-h3
rootdev=UUID=3184f3f7-027a-4d4c-81be-8e60c20d8a4a
rootfstype=ext4
overlays=i2c2 uart1 uart2 usbhost1 usbhost2
user_overlays=spi1-st7789
extraargs=usbcore.nousb=1 spidev.bufsiz=16384
usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u

/boot/overlay-user/spi1-st7789.dts:

Quote

 

/dts-v1/;
/plugin/;
/ {
    compatible = "allwinner,sun8i-h3";

    fragment@0 {
        target = <&pio>;
        __overlay__ {
            st7789_pins: st7789_pins {
                pins = "PA7", "PG11", "PA6";
                function = "gpio_out";
            };
        };
    };

    fragment@1 {
        target = <&spi1>;
        __overlay__ {
            status = "okay";
            #address-cells = <1>;
            #size-cells = <0>;
            st7789@0 {
                compatible = "sitronix,st7789v";
                reg = <0>;
                pinctrl-names = "default";
                pinctrl-0 = <&st7789_pins>;
                spi-max-frequency = <4000000>;
                rotate = <270>;
                fps = <60>;
                buswidth = <8>;
                width = <240>;
                height = <320>;
                dc-gpios    = <&pio 0 7 0>;
                reset-gpios = <&pio 6 11 0>;
                led-gpios   = <&pio 0 6 0>;
                debug = <7>;
            };
        };
    };
};

 

SPI1 is not generating any CLK or MOSI signals on the physical pins.

Looking forward for any help
Best regards, Genadi

user@nanopiair:~$ sudo apt install mpd
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 mpd : Depends: libavcodec61 (>= 7:7.0) but it is not installable
       Depends: libavfilter10 (>= 7:7.0) but it is not installable
       Depends: libavformat61 (>= 7:7.0) but it is not installable
       Depends: libavutil59 (>= 7:7.0) but it is not installable
       Depends: libflac14 (>= 1.5.0) but it is not installable
       Depends: libfmt10 (>= 10.1.1+ds1) but it is not installable
       Depends: libicu76 (>= 76.1-1~) but it is not installable
       Depends: libiso9660-12 (>= 2.2.0) but it is not installable
       Depends: libsidplayfp6 (>= 2.12.0) but it is not going to be installed
       Depends: libjs-sphinxdoc (>= 8.1) but it is not going to be installed
       Depends: sphinx-rtd-theme-common (>= 3.0.2+dfsg) but it is not going to be installed
E: Unable to correct problems, you have held broken packages.

What is the issue with missing packages ?

Edit: Solved by adding trixie repositories.

I suspect its a driver problem since gutenprint does not have the exact same model (I chose Pixma G2000 Driver in CUPS "Add Printer" menu)

#When Adding Printer
d [20/Feb/2026:03:19:36 +0700] [CGI] Finished \"{default_name=Canon_G2070_series\", out=0xffffb9ff1520...
d [20/Feb/2026:03:19:36 +0700] [CGI] \"{printer_uri_supported}\" at 367...
d [20/Feb/2026:03:19:36 +0700] [CGI] \"{$org.cups.sid}\" at 452...
D [20/Feb/2026:03:19:36 +0700] [CGI] Regular expression \".*Clean.*\"
d [20/Feb/2026:03:19:36 +0700] [CGI] Starting \"{printer_commands~.*Clean.*\" at 639, result=0...
d [20/Feb/2026:03:19:36 +0700] [CGI] Skip first part...
d [20/Feb/2026:03:19:36 +0700] [CGI] Starting at file position 639...
d [20/Feb/2026:03:19:36 +0700] [CGI] Returning at file position 700 on character \':\'...
d [20/Feb/2026:03:19:36 +0700] [CGI] Output second part...
d [20/Feb/2026:03:19:36 +0700] [CGI] Starting at file position 700...
d [20/Feb/2026:03:19:36 +0700] [CGI] Returning at file position 701 on character \'}\'...
d [20/Feb/2026:03:19:36 +0700] [CGI] Finished \"{printer_commands~.*Clean.*\", out=0xffffb9ff1520...
D [20/Feb/2026:03:19:36 +0700] [CGI] Regular expression \".*PrintSelfTestPage.*\"
d [20/Feb/2026:03:19:36 +0700] [CGI] Starting \"{printer_commands~.*PrintSelfTestPage.*\" at 742, result=0...
d [20/Feb/2026:03:19:36 +0700] [CGI] Skip first part...
d [20/Feb/2026:03:19:36 +0700] [CGI] Starting at file position 742...
d [20/Feb/2026:03:19:36 +0700] [CGI] Returning at file position 809 on character \':\'...
d [20/Feb/2026:03:19:36 +0700] [CGI] Output second part...
d [20/Feb/2026:03:19:36 +0700] [CGI] Starting at file position 809...
d [20/Feb/2026:03:19:36 +0700] [CGI] Returning at file position 810 on character \'}\'...
d [20/Feb/2026:03:19:36 +0700] [CGI] Finished \"{printer_commands~.*PrintSelfTestPage.*\", out=0xffffb9ff1520...
d [20/Feb/2026:03:19:36 +0700] [CGI] Starting \"{printer_state=5\" at 828, result=0...
d [20/Feb/2026:03:19:36 +0700] [CGI] Skip first part...
d [20/Feb/2026:03:19:36 +0700] [CGI] Starting at file position 828...
d [20/Feb/2026:03:19:36 +0700] [CGI] Returning at file position 882 on character \':\'...
d [20/Feb/2026:03:19:36 +0700] [CGI] Output second part...
d [20/Feb/2026:03:19:36 +0700] [CGI] Starting at file position 882...
d [20/Feb/2026:03:19:36 +0700] [CGI] Returning at file position 934 on character \'}\'...
d [20/Feb/2026:03:19:36 +0700] [CGI] Finished \"{printer_state=5\", out=0xffffb9ff1520...
d [20/Feb/2026:03:19:36 +0700] [Client 31] cupsdReadClient: error=0, used=0, state=HTTP_STATE_WAITING, data_encoding=HTTP_ENCODING_LENGTH, data_remaining=0,>
D [20/Feb/2026:03:19:36 +0700] [Client 31] POST / HTTP/1.1
D [20/Feb/2026:03:19:36 +0700] cupsdSetBusyState: newbusy="Active clients and dirty files", busy="Active clients and dirty files"
D [20/Feb/2026:03:19:36 +0700] [Client 31] Read: status=200, state=6
d [20/Feb/2026:03:19:36 +0700] cupsdFindBest: uri="/", limit=10...
d [20/Feb/2026:03:19:36 +0700] cupsdFindBest: Location /admin/log(10) Limit 7f
d [20/Feb/2026:03:19:36 +0700] cupsdFindBest: Location /admin/conf(11) Limit 7f
d [20/Feb/2026:03:19:36 +0700] cupsdFindBest: Location /admin(6) Limit 7f
d [20/Feb/2026:03:19:36 +0700] cupsdFindBest: Location /(1) Limit 7f
d [20/Feb/2026:03:19:36 +0700] cupsdFindBest: best=/
d [20/Feb/2026:03:19:36 +0700] [Client 31] con->uri="/", con->best=0xaaaac8741170(/)
D [20/Feb/2026:03:19:36 +0700] [Client 31] No authentication data provided.
d [20/Feb/2026:03:19:36 +0700] cupsdIsAuthorized: con->uri="/", con->best=0xaaaac8741170(/)
d [20/Feb/2026:03:19:36 +0700] cupsdIsAuthorized: level=CUPSD_AUTH_ANON, type=None, satisfy=CUPSD_AUTH_SATISFY_ALL, num_names=0
d [20/Feb/2026:03:19:36 +0700] cupsdIsAuthorized: auth=CUPSD_AUTH_ALLOW...
D [20/Feb/2026:03:19:36 +0700] [Client 31] 2.0 Get-Jobs 3
d [20/Feb/2026:03:19:36 +0700] cupsdProcessIPPRequest(0xaaaac88b11c0[31]): operation_id=000a(Get-Jobs)

#When Trying to Print Test Page
d [20/Feb/2026:03:21:19 +0700] [Job 10] Gutenprint: Reading 14874 4699
d [20/Feb/2026:03:21:19 +0700] [Job 10] Gutenprint: Tossing right 0 (0) + 9
d [20/Feb/2026:03:21:19 +0700] cupsdDeleteTemporaryPrinters: Removing unused temporary printers
d [20/Feb/2026:03:21:19 +0700] select_timeout: JobHistoryUpdate=1771607348
d [20/Feb/2026:03:21:19 +0700] [Job 10] Gutenprint: Reading 14874 4700
d [20/Feb/2026:03:21:19 +0700] cupsdDeleteTemporaryPrinters: Removing unused temporary printers
d [20/Feb/2026:03:21:19 +0700] select_timeout: JobHistoryUpdate=1771607348
d [20/Feb/2026:03:21:19 +0700] [Job 10] Gutenprint: Tossing right 0 (0) + 9
d [20/Feb/2026:03:21:19 +0700] [Job 10] Gutenprint: Tossing right 0 (0) + 9
D [20/Feb/2026:03:21:19 +0700] [Job 10] Printing page 1, 67%
D [20/Feb/2026:03:21:19 +0700] cupsdMarkDirty(---J-)
D [20/Feb/2026:03:21:19 +0700] cupsdSetBusyState: newbusy="Printing jobs and dirty files", busy="Printing jobs and dirty files"
D [20/Feb/2026:03:21:19 +0700] [Job 10] Set job-printer-state-message to "Printing page 1, 67%", current level=INFO
D [20/Feb/2026:03:21:19 +0700] [Job 10] ATTR: job-media-progress=67
d [20/Feb/2026:03:21:19 +0700] cupsdAddEvent(event=job-progress, dest=0xaaaac8751a40(Canon_G2070_series), job=0xaaaac888e2e0(10), text="Printing page %d, %d>
D [20/Feb/2026:03:21:19 +0700] Discarding unused job-progress event...
d [20/Feb/2026:03:21:19 +0700] cupsdAddEvent(event=job-progress, dest=0xaaaac8751a40(Canon_G2070_series), job=0xaaaac888e2e0(10), text="%s", ...)
D [20/Feb/2026:03:21:19 +0700] Discarding unused job-progress event...
d [20/Feb/2026:03:21:19 +0700] cupsdAddEvent(event=printer-state-changed, dest=0xaaaac8751a40(Canon_G2070_series), job=(nil)(0), text="Printer \"%s\" state >
D [20/Feb/2026:03:21:19 +0700] Discarding unused printer-state-changed event...
d [20/Feb/2026:03:21:19 +0700] cupsdDeleteTemporaryPrinters: Removing unused temporary printers
d [20/Feb/2026:03:21:19 +0700] select_timeout: JobHistoryUpdate=1771607348
d [20/Feb/2026:03:21:19 +0700] [Job 10] Gutenprint: Reading 14874 4702
d [20/Feb/2026:03:21:19 +0700] cupsdDeleteTemporaryPrinters: Removing unused temporary printers
d [20/Feb/2026:03:21:19 +0700] select_timeout: JobHistoryUpdate=1771607348
d [20/Feb/2026:03:21:19 +0700] [Job 10] Gutenprint: Tossing right 0 (0) + 9
d [20/Feb/2026:03:21:19 +0700] cupsdDeleteTemporaryPrinters: Removing unused temporary printers
d [20/Feb/2026:03:21:19 +0700] select_timeout: JobHistoryUpdate=1771607348
d [20/Feb/2026:03:21:19 +0700] [Job 10] Gutenprint: Reading 14874 4703
d [20/Feb/2026:03:21:19 +0700] cupsdDeleteTemporaryPrinters: Removing unused temporary printers
d [20/Feb/2026:03:21:19 +0700] select_timeout: JobHistoryUpdate=1771607348
d [20/Feb/2026:03:21:19 +0700] [Job 10] Gutenprint: Tossing right 0 (0) + 9
d [20/Feb/2026:03:21:19 +0700] cupsdDeleteTemporaryPrinters: Removing unused temporary printers
d [20/Feb/2026:03:21:19 +0700] select_timeout: JobHistoryUpdate=1771607348
d [20/Feb/2026:03:21:19 +0700] [Job 10] Gutenprint: Reading 14874 4704
d [20/Feb/2026:03:21:19 +0700] [Job 10] Gutenprint: Tossing right 0 (0) + 9
d [20/Feb/2026:03:21:19 +0700] cupsdDeleteTemporaryPrinters: Removing unused temporary printers
d [20/Feb/2026:03:21:19 +0700] select_timeout: JobHistoryUpdate=1771607348
d [20/Feb/2026:03:21:19 +0700] [Job 10] Gutenprint: Reading 14874 4705
d [20/Feb/2026:03:21:19 +0700] cupsdDeleteTemporaryPrinters: Removing unused temporary printers
d [20/Feb/2026:03:21:19 +0700] select_timeout: JobHistoryUpdate=1771607348
d [20/Feb/2026:03:21:19 +0700] [Job 10] Gutenprint: Tossing right 0 (0) + 9
d [20/Feb/2026:03:21:19 +0700] cupsdDeleteTemporaryPrinters: Removing unused temporary printers
d [20/Feb/2026:03:21:19 +0700] select_timeout: JobHistoryUpdate=1771607348
d [20/Feb/2026:03:21:19 +0700] [Job 10] Gutenprint: Reading 14874 4706
d [20/Feb/2026:03:21:19 +0700] cupsdDeleteTemporaryPrinters: Removing unused temporary printers
 

Is it possible somehow to upgrade the prebuilt image Armbian 12/OpenMediaVault 7 to Armbian 13/OpenMediaVault 8? Is there a guide?

*Neither Netplan nor NetworkManager are supposed to manage firewall settings.*

But they do it anyway, behind the scenes. That kind of behavior—making security changes without user consent—feels a lot like what malware does.

I’m trying to flash the following Armbian image, but Balena Etcher throws an error as soon as I load the image:

Java UIO (HawtJNI)

This was the "Old School" high-performance approach. It relied on a custom C wrapper and JNI to bridge the gap.

• How it works: You have to write a C helper file, compile it into a shared library (.so) for on ARM architecture (armv7l, aarch64), and bundle it in your JAR.
• The Overhead: Every call from Java to C has a "JNI transition cost." To minimize this, you used moveJavaToNative to bulk-transfer buffers, which added complexity to the Java code.

Java UIO 2 (FFM / Project Panama)

• The "Modern" approach. It treats native memory and functions as first-class citizens in Java.
• I now cross compile on x86_64 for arm32 and arm64.
• How it works: Java uses Linker and SymbolLookup to find functions in u8g2 or libc directly. No custom C wrapper is strictly required unless you want to simplify complex macros.
• The Overhead: Transitions are heavily optimized by the JVM (often inlined). By using MemorySegment, you can point Java directly at the UIO hardware registers or the U8g2 tile buffer.
• The Armbian Advantage: It is "Write Once, Run Anywhere" for native code. As long as the system library (like libSDL2.so) exists on the Armbian filesystem, the same JAR will work on an Orange Pi 5, a Pine64, or even a Raspberry Pi without re-compiling C code.

Basically, I'd like to understand the menu options better. Probably because it's a generic tool for all devices, the selections aren't clear (to me at least), depending on what device I'm working with.

For the most part, all I ever need to do is to copy the working SD image to the eMMC or NVME. Any armbian-install gurus lurking?

Using database: /database/filebrowser.db
Error: open /database/filebrowser.db: permission denied

in the .log file.

The developers of Filebrowser explained they introduced some breaking changes and documented the changes that have to be made to avoid that error:

- User: File Browser no longer runs as root, but as user with PID 1000 and GID 1000. You can still change this by using Docker's --user flag [https://www.docker.com/blog/understanding-the-docker-user-instruction/].
- Volumes: the volumes with the database and configuration are now aligned with the s6-overlay images. Instead of mounting the files themselves, which leads to frequent issues, you now mount the surrounding directory.

Unfortunately, these are breaking changes and will require updates on your side. Assuming you have a database.db, a .filebrowser.json and the data in /data, do the following:

1. Change the path of database in .filebrowser.json to /database/filebrowser.db
2. Rename database.db to filebrowser.db
3. Rename .filebrowser.json to settings.json
4. Put them in the same directory locally, let's say /app/filebrowser/
5. Change the permissions of both directories: sudo chown -R 1000:1000 /app/filebrowser /data
6. Mount with the flags -v /app/filebrowser:/database -v /app/filebrowser:/config - you can also choose to put them in separate directories, but it is not needed.

If you are still getting errors, please make sure that the paths/volumes you are mounting have read-write permission for user 1000:1000. For more up to date information regarding how you should use the Docker image, check filebrowser.org/installation.html#docker [https://filebrowser.org/installation.html#docker]

But how exactly to apply those changes after the container already has been created and started via armbian-config?

https://www.armbian.com/odroid-xu4/

https://www.armbian.com/zero-pi/
I understand that both SBCs are quite old and probably long forgotten by Armbian users, but I need a clean install on both and am looking for the latest existing images. 
 
I tried looking at https://armbian.lv.auroradev.org/archive, but it seems not everything is there. 
 
Thanks in advance for any help. 
 
PS 
Anyone still using these SBCs? Are there any alternatives in 2026 at reasonable prices?

The problem is the package `zfs-zed` isn't available, so I got serious problems during the update (I run Openmediavault, btw).

Any tips if it's a mistake and the package should be included, or `zfs-zed` is deprecated and I need to talk with OMV team to remove this dependency?

• I download Image form source: https://dl.armbian.com/odroidxu4/Bookworm_current_minimal-omv
• Flash Image with Rufus-4.11 --> no problem
• insert sd-card in odroid hc1 --> blue LED is flashing
• I ping to odroid with windows 'ping odroid -t -w 100'  --> replied 10 seconds, then there was no response for 40 seconds, and it repeated, I wait 30 minutes.

• I use Image from archive without OpenMedaivault --> Booting Ok
• I install OMV 7.0 manually described following link: https://docs.openmediavault.org/en/7.x/installation/on_debian.html
• in first view everything seem fine BUT:
  after restart and save settings to SD-card --> odroid restarts after 20 seconds, if you do anything with huge load, it restarts, even 'apt update' or 'apt upgrade"

I did several tests, buy a new SD-card try 3 different cards, remove hard drive remove PCB and renew thermal interface material, nothing helps. I installed it 5 to 10 times and I did the installation in different ways. Also nothing helps.

I  use my old working sd-card and I did some test, it works properly. (old means: installation is 2-3 years old)

I try 'armbianmonitor -m' --> output: 23:30:52   600/2000 MHz  0.66  19%   6%  11%   0%   0%   1%  37.0 °C  0/3

The frequency changes depending on the load, I used stress -c 8 --> frequencey 1400/2000MHz  -> works perfect

I try  Debian 12 (Bookworm) with OpenMediaVault from armbian download page. (Build Date: Jan 19, 2026)

I try 'armbianmonitor -m' --> output: 22:10:52   200/200 MHz  0.66  19%   6%  11%   0%   0%   1%  24.0 °C  0/3

The frequency was always at 200/200MHz.

I think I found the error in '/etc/default/cpufrequtils 

Both values are "0".

MAX_SPEED="0"
MIN_SPEED="0"

I compare it with my old working sd-card. The values there:

MAX_SPEED="2000000"
MIN_SPEED="600000"
 

I Update the Image:

I 'unxz' the image that I had downloaded from armbian page, 'losetup' it, 'mount' the partition and change the value in 'cpufrequtils' to MAX_SPEED="2000000" MIN_SPEED="600000".

I 'xz' the image, flash it to my sd-card and now the images works on my Odroid XU4/HC1 perfect.

Is this a bug?

Pointer or instructions appreciated

Thank you Jacques 

Thanks for any advice.

sudo apt update.

I'm trying to build from source code, and running into a problem between chroot & qemu - I'm not really sure which or both or what. When I attempt to build with SHARE_LOG=yes, I get "Error: cannot post" as the result.

So, I'm building from:

Windows 11 Home 23H2
i5-10500H

Ubuntu 24.04 WSL from Windows Terminal

I'm building for:

Orange Pi Zero 3 4gb

Armbian Edge

Bookworm Server

I get the following error:

[💲|🌱] Applying distribution specific tweaks for [ bookworm ]
[💲|🔨]   chroot: failed to run command ‘/usr/bin/env’: Exec format error
[💲|💥] Cleaning up [ please wait for cleanups to finish ]
[💲|🌿] Unmounting recursively [ SDCARD - be patient ]
[💲|🌿] Unmounting recursively [ MOUNT - be patient ]
[💲|🌿] ANSI log file built; inspect it by running: [ less -RS output/logs/log-build-7c70cb75-34bc-4c8f-8c7d-69066fb9d14c.log.ans ]
[💲|🌱] SHARE_LOG=yes, uploading log [ uploading logs ]
[💲|🌿] Log uploaded, share URL: [ <!DOCTYPE html> <html lang=en> <head> <meta charset=utf-8> <title>Error</title> </head> <body> <pre>Cannot POST /log</pre> </body> </html> ]

I believe this is related: https://github.com/armbian/build/issues/5330#issuecomment-2210559531

I tried following the steps outlined, with the following results:

$ sudo update-binfmts --enable qemu-arm
update-binfmts: warning: qemu-arm not in database of installed binary formats.
update-binfmts: exiting due to previous errors
$ arch-test
amd64
i386
win32
win64
x32

Relevant portion(s) of log:

# Armbian ANSI build logs for 7c70cb75-34bc-4c8f-8c7d-69066fb9d14c - use "less -SR" to view
# Armbian build at Tue Dec 31 15:31:16 EST 2024 on DESKTOP-IVI63TV
------------------------------------------------------------------------------------------------------------
# Repeat build: ./compile.sh build BOARD=orangepizero3 BRANCH=edge BUILD_DESKTOP=no BUILD_MINIMAL=no KERNEL_CONFIGURE=yes RELEASE=bookworm SHARE_LOG=yes
# ARGs: 'PREFER_DOCKER=no' 'ARMBIAN_RELAUNCHED=yes' 'SET_OWNER_TO_UID=1000' 'SHARE_LOG=yes' 'build'
------------------------------------------------------------------------------------------------------------
# GIT revision
   commit bab9b3fbe383a2a2b1224d2bd4ca4d26142ed020 (HEAD -> main, origin/main, origin/HEAD)
   Author: pykpkg47 <118465017+pykpkg47@users.noreply.github.com>

       rock-3a:add u-boot image for sata boot
------------------------------------------------------------------------------------------------------------
# GIT status
   On branch main
   Your branch is up to date with 'origin/main'.

   Changes not staged for commit:
     (use "git add <file>..." to update what will be committed)
     (use "git restore <file>..." to discard changes in working directory)
        modified:   config/kernel/linux-sunxi64-edge.config

   no changes added to commit (use "git add" and/or "git commit -a")
------------------------------------------------------------------------------------------------------------
### config_early_init.log
--> (0) INFO: Starting single build process [ no BOARD set ]
--> (0) INFO: Checking [ basic host setup ]
--> (0) INFO: Build host OS release [ noble ]
--> (0) INFO: Build host architecture [ amd64 ]
--> (0) INFO: Detected WSL2 - experimental support [ Windows Subsystem for Linux 2 ]
--> (5) INFO: Generating list of all available boards [ might take a while ]
--> (6) ERROR: Error 3 occurred in main shell [ at /home/eric/build/lib/functions/configuration/menu.sh:38
       dialog_if_terminal_set_vars() --> lib/functions/configuration/menu.sh:38
      interactive_config_ask_board_list() --> lib/functions/configuration/interactive.sh:149
      config_possibly_interactive_kernel_board() --> lib/functions/main/config-interactive.sh:16
       prep_conf_main_build_single() --> lib/functions/main/config-prepare.sh:21
            cli_standard_build_run() --> lib/functions/cli/cli-build.sh:22
           armbian_cli_run_command() --> lib/functions/cli/utils-cli.sh:136
                    cli_entrypoint() --> lib/functions/cli/entrypoint.sh:176
                              main() --> compile.sh:50
    ]
--> (8) INFO: Generating list of all available boards [ might take a while ]
------------------------------------------------------------------------------------------------------------
### config_source_board_file.log
--> (19) INFO: Sourcing board configuration [ /home/eric/build/config/boards/orangepizero3.csc ]
--> (19) INFO: Enabling extension [ uwe5622-allwinner ]
--> (19) CHANGE-TRACKING: change-tracking: after sourcing board file config/boards/orangepizero3.csc [ BOARDFAMILY='sun50iw9' ]
--> (19) CHANGE-TRACKING: change-tracking: after sourcing board file config/boards/orangepizero3.csc [ BOOTCONFIG='orangepi_zero3_defconfig' ]
--> (19) CHANGE-TRACKING: change-tracking: after defaulting LINUXFAMILY to BOARDFAMILY [ LINUXFAMILY='sun50iw9' ]
------------------------------------------------------------------------------------------------------------
     
     ...
     ...
     ...
     
--> (31) COMMAND: update-binfmts --enable qemu-arm
   update-binfmts: warning: qemu-arm not in database of installed binary formats.
   update-binfmts: exiting due to previous errors
   -->--> command failed with error code 2 after 0 seconds
--> (31) WARNING: stacktrace for failed command [ exit code 2:/usr/bin/env bash -e -o pipefail -c update-binfmts --enable qemu-arm
           run_host_command_logged() --> lib/functions/logging/runners.sh:193
       prepare_host_noninteractive() --> lib/functions/host/prepare-host.sh:179
                   do_with_logging() --> lib/functions/logging/section-logging.sh:81
                      prepare_host() --> lib/functions/host/prepare-host.sh:17
                 prepare_host_init() --> lib/functions/main/start-end.sh:64
          main_default_start_build() --> lib/functions/main/start-end.sh:17
             do_with_default_build() --> lib/functions/main/default-build.sh:41
            cli_standard_build_run() --> lib/functions/cli/cli-build.sh:25
           armbian_cli_run_command() --> lib/functions/cli/utils-cli.sh:136
                    cli_entrypoint() --> lib/functions/cli/entrypoint.sh:176
                              main() --> compile.sh:50 ]
--> (31) ERROR: Failed to update binfmts [ update-binfmts --enable qemu-arm ]

Java UIO offers robust Java interfaces optimized for Linux Userspace IO, emphasizing high performance. Engineered from scratch, it leverages contemporary kernel APIs, libraries, and cutting-edge code generation methodologies, embodying a state-of-the-art cross-platform solution. Rather than reinventing established paradigms, Java UIO harnesses existing standards, avoiding redundant development commonly observed in other IO libraries. Seamlessly supporting JDK 25 LTS, this framework integrates Project Lombok to streamline code, enhancing readability and conciseness.

🌍 The 32-bit & FFM Reality

With Java 25, there is no more support for X86_32, and ARM32 has limited JDKs available. While FFM (Foreign Function & Memory API) is the future, it is not supported on X86_32 or ARM32. For now, JavaUIO moves into the future providing a high-performance path for ARM32, while fully supporting ARM64 and X86_64.

Thank you in advance.

I am using an Orange Pi Zero 2W with a graphical user interface (GUI). I downloaded and installed the official Orange Pi Zero 2W image.

Unfortunately, I keep running into a Wi-Fi connection issue. After booting, the system repeatedly asks me to enter my Wi-Fi password. If I don’t enter it, I have no internet connection.

What’s interesting is:

If I disable and re-enable Wi-Fi in the network manager, it automatically reconnects to the known network without asking for the password again.

Alternatively, a system reboot also restores the Wi-Fi connection automatically.

I have already seen online that this seems to be a known issue, but I haven’t found a proper or permanent solution so far.

Has anyone experienced similar behavior or knows how to configure Wi-Fi so that it connects reliably and permanently without repeatedly asking for the password?

Thanks in advance!

dockerd[1491]: time="2025-12-27T20:55:44.808894213-05:00" level=error msg="Error writing log message" driver=json-file error="error writing log entry: write /var/lib/docker/containers/97e823567c56600b69888e6abf63189c6f586afbf6bcf06fca820eaf4ef46f7d/97e823567c56600b69888e6abf63189c6f586afbf6bcf06fca820eaf4ef46f7d-json.log: no space left on device" message=

After a while, these two messages will start repeating (these were taken from a different instance of this happening, so the PID is different):

rsyslogd[599]: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2504.0 try https://www.rsyslog.com/e/2027 ]
rsyslogd[599]: file '/var/log/syslog'[7] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2504.0 try https://www.rsyslog.com/e/2027 ]

Looking at btop when this is happening shows that the rsyslog and dockerd processes are using up most of the CPU, along with fail2ban for some reason. The full command for dockerd is:

/usr/bin/dockerd -H fd:// --containerd=/run/containerd/containerd.sock

Here are all my docker packages:

docker-buildx-plugin/trixie,now 0.30.1-1~debian.13~trixie arm64 [installed]
docker-ce-cli/trixie,now 5:29.1.3-1~debian.13~trixie arm64 [installed]
docker-ce/trixie,now 5:29.1.3-1~debian.13~trixie arm64 [installed]
docker-compose-plugin/trixie,now 5.0.0-1~debian.13~trixie arm64 [installed]

I am facing situation where new armbian images e.g. Armbian_community_26.2.0-trunk.100_Orangepizero2w_trixie_current_6.12.63_minimal is coming without nmui. 

nmtui support one wifi configuration with dhcp while assigning static ip to other wifi.

systemd-networkd does not support separate behaviour for two different wifi configruation.

Requesting to provide nmtui which is more flexible.

To elaborate the case, the dhcp is must for connecting to mobile hotspot which keeps on changing ip series. And for IoT project, I need static configuration. That's why i need armbian to allow dhcp when i am trying to ssh on mobile hotspot for initial configuration to and later switch to static ip of IoT project router.

GPIO are not enabled in device tree.

I set M to the panel-mipi-dbi kernel module parameter. I also set Y to the parameter. I also tried adjusting the .config file before running the image build. I used both Docker and non-Docker builds. I'm using Ubuntu 22.04.

W: https://github.armbian.com/configng/dists/stable/InRelease: Policy will reject signature within a year, see --audit for details
W: http://apt.armbian.com/dists/trixie/InRelease: Policy will reject signature within a year, see --audit for details

Using the --audit option I get:

W: https://github.armbian.com/configng/dists/stable/InRelease: Policy will reject signature within a year, see --audit for details
A: https://github.armbian.com/configng/dists/stable/InRelease: Sub-process /usr/bin/sqv returned an error code (1), error message is:
   Signing key on DF00FAF1C577104B50BF1D0093D6889F9F0E78D5 is not bound:
              No binding signature at time 2025-10-06T08:29:30Z
     because: Policy rejected non-revocation signature (PositiveCertification) requiring second pre-image resistance
     because: SHA1 is not considered secure since 2026-02-01T00:00:00Z
   Missing key 8CFA83D13EB2181EEF5843E41EB30FAF236099FE, which is needed to verify signature.
W: http://apt.armbian.com/dists/trixie/InRelease: Policy will reject signature within a year, see --audit for details
A: http://apt.armbian.com/dists/trixie/InRelease: Sub-process /usr/bin/sqv returned an error code (1), error message is:
   Signing key on DF00FAF1C577104B50BF1D0093D6889F9F0E78D5 is not bound:
              No binding signature at time 2025-10-07T19:06:52Z
     because: Policy rejected non-revocation signature (PositiveCertification) requiring second pre-image resistance
     because: SHA1 is not considered secure since 2026-02-01T00:00:00Z
   Missing key 8CFA83D13EB2181EEF5843E41EB30FAF236099FE, which is needed to verify signature.

So a key is missing. Where can I get it? And how to install it?

Jürgen

Quote

truncate: cannot open '/var/log/postgresql/postgresql-15-main.log' for writing: Permission denied

The directory /var/log/postgresql is owned by root (and group postgres) and has permissions drwxrwxr-t, and the file /var/log/postgresql/postgresql-15-main.log is owned by postgres (and group adm) and has permissions -rw-r-----.

In /var/log.hdd/postgresql the ownership and permissions are the same, and there are also files postgresql-15-main.log.1, postgresql-15-main.log.2.gz, postgresql-15-main.log.3.gz, ..., postgresql-15-main.log.10.gz (with the same ownership and permissions as postgresql-15-main.log).  The file postgresql-15-main.log.1 is a prefix of postgresql-15-main.log.

I have this problem only with PostgreSQL's logs; armbian-truncate-logs doesn't complain about any other log files.

Is there something I need to do to fix this, or is this a bug that will be fixed in future?

Once the symlink is removed and the directory is created instead, the installation can be completed successfully. The symlink can be recreated afterwards and authelia wil steill run normally  - until the next package update.

When I made a boot with Balena Etecher, it turned out there was an error.

Something went wrong while writing Armbian_community_26.2.0-trunk.7_Aml-s9xx-box_noble_current_6.12.58_cinnamon_desktop.img.xz to Mass Storage Device (armbi_boot, armbi_root) (/dev/sdb)

I downloaded it from the link provided at https://www.armbian.com/amlogic-s9xx-tv-box/
The file I used was Ubuntu 24.04 (Noble) Cinnamon.

When I finished flashing, Balena couldn't verify the memory card and displayed an error.
Something went wrong while writing Armbian_community_26.2.0-trunk.7_Aml-s9xx-box_noble_current_6.12.58_cinnamon_desktop.img.xz to Mass Storage Device (armbi_boot, armbi_root) (/dev/sdb)

reboot. odroidxu4 booted to console prompt
Installed xfce4-goodies package

reboot. odroidxu4 booted to console prompt
Installed lightdm

reboot. The system becomes stuck at plymouth-quit-wait.service/start

Not much I could do after this as I could not look at log messages or use $ sudo systemctl status lightdm.service

Any insight greatly appreciated

Thanks

Now only windows explorer communicates with the Pis. The Pis do not see each other nor Windows. I tried (almost) everything and nothing works.

I could not get/install WSDD

>>Package wsdd is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source

Error: Package 'wsdd' has no installation candidate>>

so I installed WSDD2 and made reference to it and still no go.

Any solution?

Thank you !!

root@opi5 /etc/apt/sources.list.d# apt-get update
Hit:1 http://deb.debian.org/debian trixie-backports InRelease
Hit:2 http://deb.debian.org/debian trixie InRelease        
Hit:3 http://deb.debian.org/debian trixie-updates InRelease
Hit:4 http://security.debian.org trixie-security InRelease 
Hit:5 https://github.armbian.com/configng stable InRelease                                            
Hit:6 http://mirror.vinehost.net/armbian/apt trixie InRelease
Reading package lists... Done
W: https://github.armbian.com/configng/dists/stable/InRelease: Policy will reject signature within a year, see --audit for details
N: Missing Signed-By in the sources.list(5) entry for 'http://deb.debian.org/debian'

```

```

root@opi5 /etc/apt/sources.list.d# apt-get update --audit
Hit:1 http://deb.debian.org/debian trixie-backports InRelease
Hit:2 http://deb.debian.org/debian trixie InRelease                                                                
Hit:3 http://deb.debian.org/debian trixie-updates InRelease                                                        
Hit:4 http://security.debian.org trixie-security InRelease                                                         
Hit:5 https://github.armbian.com/configng stable InRelease                                                         
Hit:6 http://mirror.vinehost.net/armbian/apt trixie InRelease
Reading package lists... Done
W: https://github.armbian.com/configng/dists/stable/InRelease: Policy will reject signature within a year, see --audit for details
A: https://github.armbian.com/configng/dists/stable/InRelease: Sub-process /usr/bin/sqv returned an error code (1), error message is:
   Signing key on DF00FAF1C577104B50BF1D0093D6889F9F0E78D5 is not bound:
              No binding signature at time 2025-09-08T18:12:20Z
     because: Policy rejected non-revocation signature (PositiveCertification) requiring second pre-image resistance
     because: SHA1 is not considered secure since 2026-02-01T00:00:00Z
   Missing key 8CFA83D13EB2181EEF5843E41EB30FAF236099FE, which is needed to verify signature.
N: Missing Signed-By in the sources.list(5) entry for 'http://deb.debian.org/debian'

```

**/etc/apt/sources.list.d/armbian-config.sources**

```

Types: deb
URIs: https://github.armbian.com/configng
Suites: stable
Components: main
Signed-By: /usr/share/keyrings/armbian.gpg

```

**/etc/apt/sources.list.d/armbian.sources**

```

Types: deb
URIs: http://apt.armbian.com/
Suites: trixie
Components: main  trixie-utils trixie-desktop
Signed-By: /etc/apt/trusted.gpg.d/armbian.gpg

```

**/etc/apt/sources.list.d/debian-backports.sources**

```

# Modernized from /etc/apt/sources.list
Types: deb
URIs: http://deb.debian.org/debian/
Suites: trixie-backports
Components: main  contrib non-free non-free-firmware
Signed-By:

```

**/etc/apt/sources.list.d/debian.sources**

```

# Modernized from /etc/apt/sources.list
Types: deb
URIs: http://deb.debian.org/debian/
Suites: trixie
Components: main  contrib non-free non-free-firmware
Signed-By: /usr/share/keyrings/debian-archive-keyring.gpg

# Modernized from /etc/apt/sources.list
Types: deb
URIs: http://deb.debian.org/debian/
Suites: trixie-updates
Components: main  contrib non-free non-free-firmware
Signed-By: /usr/share/keyrings/debian-archive-keyring.gpg

# Modernized from /etc/apt/sources.list
Types: deb
URIs: http://security.debian.org/
Suites: trixie-security
Components: main  contrib non-free non-free-firmware
Signed-By: /usr/share/keyrings/debian-archive-keyring.gpg

```

How to fix it?

Unfortunately, I use an Odroid N2 (and N2+) for nextcloud installed via the nextcloudpi script. Now, the support is gone and there are no longer updates for nextcloud beyond version 30.0.x available.

Currently I am running nextcloud 30.0.17. The version 30.0.x will reach end-of-support soon.

I can imagine the following alternatives:

1.  Use armbian-config to install nextcloud - but will it do the update correctly or at all esp. for my external disks which nextcloud is using ?
2. Use the image for the Odroid C2 (another arm-based SBC) and replace the kernel by the one for the Odroid N2+
3. Port the script from the Odroid C2 image to my Odroid N2
4. Buy an Raspi 4 or, even better, a Raspi 5 and use the images for that HW - how about a migration path ?

So what do you suggest ?

I think I could do all of those alternatives myself and I have an Odroid N2 and an Odroid N2+ useable for testing purposes.

One of those was planned to run HomeAssistant and I'm happy that HAOS is supported on my hardware. But that can be postponed to later.

Kind regards

Norbert

Edit: Added question for the migration path if HW changed to Raspi 4 or 5

Armianmonitor: https://paste.armbian.com/oletimumob

I have this ancient Opi+. AND I KNOW THOSE TYPES OF UPDATES ARE NOT SUPPORTED. Yet, they often succeeds and I want to upgrade my system via do-release-upgrade

For last six months I am stuck on this, attaching output from putty login screen AND lsb_release as a printscreen

My sources.list.d look like this

orangepiplus:sources.list.d:% dir
armbian-config.sources	armbian.list  ubuntu.sources
orangepiplus:sources.list.d:% cat armbian-config.sources 
Types: deb
URIs: https://github.armbian.com/configng
Suites: stable
Components: main
Signed-By: /usr/share/keyrings/armbian.gpg
orangepiplus:sources.list.d:% cat armbian.list           
deb [arch=armhf signed-by=/usr/share/keyrings/armbian.gpg] http://apt.armbian.com jammy main jammy-utils jammy-desktop
orangepiplus:sources.list.d:% cat ubuntu.sources 
Types: deb
URIs: http://ports.ubuntu.com/ubuntu-ports/
Suites: jammy jammy-updates jammy-security
Components: main restricted universe multiverse
Signed-By: /usr/share/keyrings/ubuntu-archive-keyring.gpg
orangepiplus:sources.list.d:% 

Update package noble.tar.gz is downloaded and run, but then it results in this, not sure why?

Updating repository information

No valid mirror found 

While scanning your repository information no mirror entry for the 
upgrade was found. This can happen if you run an internal mirror or 
if the mirror information is out of date. 

Do you want to rewrite your 'sources.list' file anyway? If you choose 
'Yes' here it will update all 'jammy' to 'noble' entries. 
If you select 'No' the upgrade will cancel. 

Continue [yN] y

Generate default sources? 

After scanning your 'sources.list' no valid entry for 'jammy' was 
found. 

Should default entries for 'noble' be added? If you select 'No', the 
upgrade will cancel. 

Continue [yN] 

I agree to this  but then it results in buttload of Hit/Err 404 errors, for some reason, it is a small part of it:

n http://archive.ubuntu.com/ubuntu noble/universe armhf Packages          
Err http://archive.ubuntu.com/ubuntu noble/restricted armhf Packages        
  404  Not Found [IP: 91.189.91.81 80]                                      
Err http://archive.ubuntu.com/ubuntu noble/main armhf Packages              
  404  Not Found [IP: 91.189.91.81 80]                                      
Err http://archive.ubuntu.com/ubuntu noble/multiverse armhf Packages        
  404  Not Found [IP: 91.189.91.81 80]                                      
Err http://archive.ubuntu.com/ubuntu noble/universe armhf Packages          
  404  Not Found [IP: 91.189.91.81 80]                                      
Ign http://archive.ubuntu.com/ubuntu noble/restricted armhf Packages        
Ign http://archive.ubuntu.com/ubuntu noble/main armhf Packages              
Ign http://archive.ubuntu.com/ubuntu noble/multiverse armhf Packages        
Ign http://archive.ubuntu.com/ubuntu noble/universe armhf Packages          
Err http://archive.ubuntu.com/ubuntu noble/restricted armhf Packages        
  404  Not Found [IP: 91.189.91.81 80]                                      
Ign http://archive.ubuntu.com/ubuntu noble/main armhf Packages              
Ign http://archive.ubuntu.com/ubuntu noble/multiverse armhf Packages        
Ign http://archive.ubuntu.com/ubuntu noble/universe armhf Packages          
Fetched 508 kB in 6s (84.5 kB/s)                                            

It ends like this:

es 
404 Not Found [IP: 185.125.190.82 80], E:Failed to fetch 
http://security.ubuntu.com/ubuntu/dists/noble-security/main/binary-armhf/Packages 
404 Not Found [IP: 91.189.91.82 80], E:Some index files failed to 
download. They have been ignored, or old ones used instead. 


Restoring original system state

Aborting
Reading package lists... Done    
Building dependency tree... Done 
Reading state information... Done
=== Command detached from window (Wed Apr 30 22:07:17 2025) ===

By trial and error I managed to overcome this by fully commenting out ubuntu sources (whole file) like this:

#Types: deb
#URIs: http://ports.ubuntu.com/ubuntu-ports/
#Suites: jammy jammy-updates jammy-security
#Components: main restricted universe multiverse
#Signed-By: /usr/share/keyrings/ubuntu-archive-keyring.gpg

Then  it does not ask me twice about generating default sources. And this way today it updated around 240 packages, asked for a restart too. But the system remained on 22 jammy.

Not sure why it worked.

After I run this again i get a buttload of "no candidate ver" errors and it just aborts - this is not a full output.

No candidate ver:  libpython3.10-minimal
No candidate ver:  libqt5core5a
No candidate ver:  libqt5gui5
No candidate ver:  libssl3
No candidate ver:  python3.10-minimal
No candidate ver:  resolvconf
No candidate ver:  rng-tools

Restoring original system state

Aborting
Reading package lists... Done    
Building dependency tree... Done 
Reading state information... Done

After this, now the system's time is approx 30 min late.

Cant seem to fix it either. Unable to systemd-timesyncd because some missing dependency but I will not go into details at this moment.

The same happens both on beta releases and stable.

Fully updated via armbian-upgrade

Where do I start? Clean install would be my LAST effort. I'd hate to do this

Where do I begin
 

I'm still working on video hwaccel with some progress.

Can anyone provide a confirmed working ffmpeg command line for camera capture and hardware encoding?

I dont care about the platform, either rockchip or anything else, no matter about kernel or arbiam version.

Using v4l2request is the only requirement. I'm using either 7.1.1 with libreelec patches or @Kwiboo's fork.  

I know there are a bunch of threads here and elswhere in the web but most are outdated, dealing with vaapi or other stuff, but I want to stay on v4l2 which seems to be the future.

   Thanks!

     T.

I just installed Armbian with OpenMediaVault on a Odroid HC4 (v25.8.2 for Odroid HC4 running Armbian Linux 6.12.48-current-meson64), when I tried to disable automatic updates in armbian-config it purged a lot of packages including openmediavault. Guess this is a bug, in case where should I report it?

Thanks all.

May 1st, 2025

AVAILABLE FOR ALL BOARDS on Debian Bookworm image via armbian-config
https://docs.armbian.com/User-Guide_Armbian-Software/Media/#omv

Download Armbian with OpenMediaVault (OMV) 

Currently (for testing) only 4 targets were build: rock5-itx, odroid m1, odroid xu4 and x86. Once its confirmed that works well, other targets will be assembled. 

Then boot the image, wait few minutes and login via:

http://ip_address_of_armbian_running_ha

U: admin

P: openmediavault

Test setup on Odroid M1:
 

Tested on:

• Odroid M1
• Raspberry PI 4

DIY

./compile.sh BOARD="uefi-x86" BRANCH=current RELEASE=bookworm ENABLE_EXTENSIONS="omv" KERNEL_CONFIGURE="no" BUILD_MINIMAL="yes"

The idea is `armbian-upgrade` also runs dkms install, you know, like Ubuntu, so the zfs kernel module will be automatically building together with the kernel upgrade.

Please, let me hear your thoughts about this. Maybe there is a flag to enable this already, or an open bug to implement the feature.

# apt upgrade

The following packages will be upgraded:
  armbian-firmware
1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 91.6 MB of archives.
After this operation, 92.2 kB of additional disk space will be used.
Do you want to continue? [Y/n] y
Get:1 http://netcup.armbian.com/apt bookworm/main armhf armbian-firmware all 25.2.1 [91.6 MB]
Ign:1 http://netcup.armbian.com/apt bookworm/main armhf armbian-firmware all 25.2.1
Err:1 http://apt.armbian.com bookworm/main armhf armbian-firmware all 25.2.1
  File has unexpected size (91589632 != 91589640). Mirror sync in progress? [IP: 152.53.15.45 80]
E: Failed to fetch http://apt.armbian.com/pool/main/a/armbian-firmware/armbian-firmware_25.2.1_all__1-SAe75d-B6c7f-R448a.deb  File has unexpected size (91589632 != 91589640). Mirror sync in progress? [IP: 152.53.15.45 80]

I am running an upgraded image of Ubuntu Noble on an Odroid HC1 (XU4 image):

Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 armbian-bsp-cli-odroidxu4-current : Depends: base-files (>= 24.8.2) but 24.5.5-13ubuntu10-noble is to be installed

I have looked around on some mirrors, but couldn't find a base-files package which is up-to-date.

Any help on this issue?

i am trying to autostart a remmina RDP session when a user logs in.

I started by making a .desktop file in file in the home/(xxx user name xxx).config/AutoStart and making it executable. 

the .desktop file will run fine when ran manually but doesn't start on boot

I then tried making a .service file in /home/(xxx user name xxx)/.config/systemd/user/

then doing a systemctl --user daemon-reload

then doing a systemctl --user enable (my service name)

when i do a systemctl --user start (my service name) it runs fine

on reboot it fails and when i check the status by systemctl --user status (my service name)  it comes back failed with can not open display as the fault.

what should I try next

How did you do it?

I have compiled labwc and it works great with my orange pi zero 3, with bookworm or trixie... but I can't figure out how to configure a wayland greeter.

I need to do this because my LCD driver can't work with X11 (panel-mipi-dbi-spi).

I can install it very simply by building a minimal image Trixie (Bookworm does not include labwc), then

* sudo apt install labwc seatd foot

* at the screen with usb keyboard (not from SSH) start: labwc -d -s foot

Then I am in labwc, with a terminal emulator on my HDMI screen

When I right click on the desktop and choose "Exit", I get a kernel oops:

Armbian-unofficial 25.08.0-trunk Trixie ttyS0

orangepizero3 login: Internal error: Oops - BUG: 00000000f2000800 [#1]  SMP
Modules linked in: rfcomm bnep hci_uart btqca btrtl btintel btbcm bluetooth ecdh_generic ecc sprdwl_ng sunxi_addr zram snd_soc_hdmi_codec sun50i_h6_prcm_ppu snd_soc_sunxi_machine snd_soc_sunxi_ahub panel_mipi_dbi dw_hdmi_i2s_audio dw_hdmi_cec cmdlinepart drm_mipi_dbi snd_soc_sunxi_ahub_dam spi_nor sun8i_ce backlight cfg80211 crypto_engine display_connector binfmt_misc uio_pdrv_genirq uio sprdbt_tty uwe5622_bsp_sdio rfkill configfs sunxi musb_hdrc phy_generic
CPU: 2 UID: 1000 PID: 5465 Comm: labwc Tainted: G        W           6.15.4-edge-sunxi64 #1 NONE
Tainted: [W]=WARN
Hardware name: OrangePi Zero3 (DT)
pstate: 80000005 (Nzcv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--)
pc : dma_buf_release+0x8c/0x98
lr : __dentry_kill+0xb4/0x238
sp : ffff80008779bd40
x29: ffff80008779bd40 x28: ffff0000073d6180 x27: 0000000000000000
x26: 0000000000000000 x25: 0000000000000000 x24: ffff8000820932e8
x23: ffff000007d76220 x22: ffff000002486da0 x21: ffff000023b0c440
x20: ffff000023b0c440 x19: ffff00000746e800 x18: 0000000000000000
x17: 0000000000000000 x16: 0000000000000000 x15: ffff80008779bd10
x14: 0000000000000004 x13: ffff00000890f850 x12: 0000000000000000
x11: ffff000026d434d0 x10: ffff000026d43478 x9 : 0000000000000000
x8 : ffff80008779bb60 x7 : 0000000000000000 x6 : 00000000000009a3
x5 : 0000000000000000 x4 : 0000000000002771 x3 : 0000000000000000
x2 : ffffffffffffffff x1 : ffff800080a6b2d8 x0 : 0000000000000001
Call trace:
 dma_buf_release+0x8c/0x98 (P)
 __dentry_kill+0xb4/0x238
 dput+0xdc/0x224
 __fput+0x10c/0x2d4
 ____fput+0x10/0x18
 task_work_run+0x88/0x110
 do_notify_resume+0x11c/0x138
 el0_svc+0x110/0x120
 el0t_64_sync_handler+0x104/0x130
 el0t_64_sync+0x170/0x174
Code: d65f03c0 d4210000 94001345 17fffff1 (d4210000)
---[ end trace 0000000000000000 ]---
note: labwc[5465] exited with irqs disabled
------------[ cut here ]------------
WARNING: CPU: 2 PID: 0 at kernel/context_tracking.c:127 ct_kernel_exit.constprop.0+0x8c/0x94
Modules linked in: rfcomm bnep hci_uart btqca btrtl btintel btbcm bluetooth ecdh_generic ecc sprdwl_ng sunxi_addr zram snd_soc_hdmi_codec sun50i_h6_prcm_ppu snd_soc_sunxi_machine snd_soc_sunxi_ahub panel_mipi_dbi dw_hdmi_i2s_audio dw_hdmi_cec cmdlinepart drm_mipi_dbi snd_soc_sunxi_ahub_dam spi_nor sun8i_ce backlight cfg80211 crypto_engine display_connector binfmt_misc uio_pdrv_genirq uio sprdbt_tty uwe5622_bsp_sdio rfkill configfs sunxi musb_hdrc phy_generic
CPU: 2 UID: 0 PID: 0 Comm: swapper/2 Tainted: G      D W           6.15.4-edge-sunxi64 #1 NONE
Tainted: [D]=DIE, [W]=WARN
Hardware name: OrangePi Zero3 (DT)
pstate: 200003c5 (nzCv DAIF -PAN -UAO -TCO -DIT -SSBS BTYPE=--)
pc : ct_kernel_exit.constprop.0+0x8c/0x94
lr : ct_idle_enter+0xc/0x14
sp : ffff800082213dd0
x29: ffff800082213dd0 x28: 0000000000000000 x27: 0000000000000000
x26: 0000000000000000 x25: ffff000002535140 x24: 0000000000000000
x23: 0000000000000000 x22: ffff800081f0ab98 x21: ffff000002535140
x20: ffff800081f0ab38 x19: ffff00003fd8b0f8 x18: 0000000000000001
x17: 3030303030303030 x16: 3030303030303020 x15: 0000016d01e397a2
x14: 0000016dfc674a7c x13: 000000000000005b x12: 0000000000000000
x11: ffff7fffbe127000 x10: 00000000000009e0 x9 : ffff800082213d50
x8 : ffff000002535b80 x7 : 0000000000000000 x6 : 0000000000000000
x5 : 4000000000000002 x4 : ffff7fffbe13f000 x3 : ffff800082213dd0
x2 : 4000000000000000 x1 : ffff800081c4c0f8 x0 : ffff800081c4c0f8
Call trace:
 ct_kernel_exit.constprop.0+0x8c/0x94 (P)
 ct_idle_enter+0xc/0x14
 default_idle_call+0x18/0x34
 do_idle+0x1c0/0x20c
 cpu_startup_entry+0x30/0x38
 secondary_start_kernel+0x110/0x130
 __secondary_switched+0x74/0x78
---[ end trace 0000000000000000 ]---

roberto@orangepizero3:~$ ps ax|grep labwc
   1304 tty1     Zl+    0:01 [labwc] <defunct>
   1574 ttyS0    S+     0:00 grep labwc

And the labwc process shows "defunct"

Has anybody experienced this?

Maybe my kernel is too new? I used 6.15.4 (edge). My labwc is 0.8.3

The error in the terminal that started labwc (the HDMI screen) is:

...wlr_drm_lease_v1.c:103] Destroying wlr_drm_lease_device_v1 for /dev/dri/cardiationsodifier LINEAR (0x0000.....)

XT_EGL_image_storage_compression GL_EXT_texture_storage_compression GL_MESA_bgra im...

Same error message here:

https://github.com/labwc/labwc/issues/1424

Source of wlroots, mentioned in the error:

https://github.com/swaywm/wlroots/blob/master/types/wlr_drm_lease_v1.c

A developer in the labwc group suggest this might be GPU driver related

https://github.com/labwc/labwc/discussions/2923

Can someone with an SBC other than H618 try running labwc and exiting? What about xfce in wayland mode... does it crash?

Is anyone aware of a H618 or sunxi running wayland successfully?

But now, either in kernel 6.x.x, or in bookworm, I have a 720x576 composite video output resolution, since HDMI is not connected. And there is no way I can change the resolution and make sure that the composite video output is not used.

HELP me

Linux odroidhc4 6.6.63-current-meson64:

$ sudo lsusb

Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 058f:6387 Alcor Micro Corp. Flash Drive
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub

Linux odroidhc4 6.12.19-current-meson64:
 

$ sudo lsusb 
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub

Linux odroidhc4 6.6.63-current-meson64:

$ sudo grep -i usb /var/log/syslog

2025-03-18T13:09:14.177378+03:00 odroidhc4 kernel: Kernel command line: root=UUID=ded3a0b7-2ab0-4e55-9668-bc97f00c48e8 rootwait rootfstype=ext4 splash=verbose console=ttyAML0,115200 console=tty1 consoleblank=0 coherent_pool=2M loglevel=1 ubootpart=fa0755e8-01 libata.force=noncq usb-storage.quirks=0x2537:0x1066:u,0x2537:0x1068:u,0x0bc2:0xa013:u    cgroup_enable=memory
2025-03-18T13:09:14.178647+03:00 odroidhc4 kernel: usbcore: registered new interface driver usbfs
2025-03-18T13:09:14.178651+03:00 odroidhc4 kernel: usbcore: registered new interface driver hub
2025-03-18T13:09:14.178655+03:00 odroidhc4 kernel: usbcore: registered new device driver usb
2025-03-18T13:09:14.179363+03:00 odroidhc4 kernel: usbcore: registered new interface driver usb-storage
2025-03-18T13:09:14.179411+03:00 odroidhc4 kernel: usbcore: registered new interface driver usbhid
2025-03-18T13:09:14.179678+03:00 odroidhc4 kernel: usbhid: USB HID core driver
2025-03-18T13:09:14.179926+03:00 odroidhc4 kernel: dwc3-meson-g12a ffe09000.usb: USB2 ports: 2
2025-03-18T13:09:14.179932+03:00 odroidhc4 kernel: dwc3-meson-g12a ffe09000.usb: USB3 ports: 0
2025-03-18T13:09:14.179937+03:00 odroidhc4 kernel: dwc2 ff400000.usb: supply vusb_d not found, using dummy regulator
2025-03-18T13:09:14.179945+03:00 odroidhc4 kernel: dwc2 ff400000.usb: supply vusb_a not found, using dummy regulator
2025-03-18T13:09:14.179950+03:00 odroidhc4 kernel: dwc2 ff400000.usb: EPs: 7, dedicated fifos, 712 entries in SPRAM
2025-03-18T13:09:14.179958+03:00 odroidhc4 kernel: xhci-hcd xhci-hcd.1.auto: new USB bus registered, assigned bus number 1
2025-03-18T13:09:14.179979+03:00 odroidhc4 kernel: xhci-hcd xhci-hcd.1.auto: new USB bus registered, assigned bus number 2
2025-03-18T13:09:14.179986+03:00 odroidhc4 kernel: xhci-hcd xhci-hcd.1.auto: Host supports USB 3.0 SuperSpeed
2025-03-18T13:09:14.179992+03:00 odroidhc4 kernel: usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 6.06
2025-03-18T13:09:14.179996+03:00 odroidhc4 kernel: usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
2025-03-18T13:09:14.180000+03:00 odroidhc4 kernel: usb usb1: Product: xHCI Host Controller
2025-03-18T13:09:14.180040+03:00 odroidhc4 kernel: usb usb1: Manufacturer: Linux 6.6.63-current-meson64 xhci-hcd
2025-03-18T13:09:14.180046+03:00 odroidhc4 kernel: usb usb1: SerialNumber: xhci-hcd.1.auto
2025-03-18T13:09:14.180075+03:00 odroidhc4 kernel: hub 1-0:1.0: USB hub found
2025-03-18T13:09:14.180086+03:00 odroidhc4 kernel: usb usb2: We don't know the algorithms for LPM for this host, disabling LPM.
2025-03-18T13:09:14.180091+03:00 odroidhc4 kernel: usb usb2: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 6.06
2025-03-18T13:09:14.180095+03:00 odroidhc4 kernel: usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
2025-03-18T13:09:14.180099+03:00 odroidhc4 kernel: usb usb2: Product: xHCI Host Controller
2025-03-18T13:09:14.180104+03:00 odroidhc4 kernel: usb usb2: Manufacturer: Linux 6.6.63-current-meson64 xhci-hcd
2025-03-18T13:09:14.180109+03:00 odroidhc4 kernel: usb usb2: SerialNumber: xhci-hcd.1.auto
2025-03-18T13:09:14.180112+03:00 odroidhc4 kernel: hub 2-0:1.0: USB hub found
2025-03-18T13:09:14.180673+03:00 odroidhc4 kernel: usb 1-2: new high-speed USB device number 2 using xhci-hcd
2025-03-18T13:09:14.180681+03:00 odroidhc4 kernel: usb 1-2: New USB device found, idVendor=058f, idProduct=6387, bcdDevice= 1.05
2025-03-18T13:09:14.180694+03:00 odroidhc4 kernel: usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
2025-03-18T13:09:14.180731+03:00 odroidhc4 kernel: usb 1-2: SerialNumber: 14052153001168
2025-03-18T13:09:14.180740+03:00 odroidhc4 kernel: usb-storage 1-2:1.0: USB Mass Storage device detected
2025-03-18T13:09:14.180744+03:00 odroidhc4 kernel: scsi host0: usb-storage 1-2:1.0
2025-03-18T13:09:14.180749+03:00 odroidhc4 kernel: usbcore: registered new interface driver uas
2025-03-18T13:09:14.182984+03:00 odroidhc4 kernel: systemd[1]: Reached target usb-gadget.target - Hardware activated USB gadget.

Linux odroidhc4 6.12.19-current-meson64:

$ sudo grep -i usb /var/log/syslog

2025-03-17T16:04:41.803269+03:00 odroidhc4 kernel: Kernel command line: root=UUID=ded3a0b7-2ab0-4e55-9668-bc97f00c48e8 rootwait rootfstype=ext4 splash=verbose console=ttyAML0,115200 console=tty1 consoleblank=0 coherent_pool=2M loglevel=1 ubootpart=fa0755e8-01 libata.force=noncq usb-storage.quirks=0x2537:0x1066:u,0x2537:0x1068:u,0x0bc2:0xa013:u    cgroup_enable=memory
2025-03-17T16:04:41.804641+03:00 odroidhc4 kernel: usbcore: registered new interface driver usbfs
2025-03-17T16:04:41.804644+03:00 odroidhc4 kernel: usbcore: registered new interface driver hub
2025-03-17T16:04:41.804648+03:00 odroidhc4 kernel: usbcore: registered new device driver usb
2025-03-17T16:04:41.804986+03:00 odroidhc4 kernel: usbcore: registered new interface driver usb-storage
2025-03-17T16:04:41.805199+03:00 odroidhc4 kernel: usbcore: registered new interface driver usbhid
2025-03-17T16:04:41.805205+03:00 odroidhc4 kernel: usbhid: USB HID core driver
2025-03-17T16:04:41.805347+03:00 odroidhc4 kernel: dwc3-meson-g12a ffe09000.usb: USB2 ports: 2
2025-03-17T16:04:41.805350+03:00 odroidhc4 kernel: dwc3-meson-g12a ffe09000.usb: USB3 ports: 0
2025-03-17T16:04:41.805359+03:00 odroidhc4 kernel: dwc2 ff400000.usb: supply vusb_d not found, using dummy regulator
2025-03-17T16:04:41.805365+03:00 odroidhc4 kernel: dwc2 ff400000.usb: supply vusb_a not found, using dummy regulator
2025-03-17T16:04:41.805369+03:00 odroidhc4 kernel: dwc2 ff400000.usb: EPs: 7, dedicated fifos, 712 entries in SPRAM
2025-03-17T16:04:41.805377+03:00 odroidhc4 kernel: xhci-hcd xhci-hcd.1.auto: new USB bus registered, assigned bus number 1
2025-03-17T16:04:41.805398+03:00 odroidhc4 kernel: xhci-hcd xhci-hcd.1.auto: new USB bus registered, assigned bus number 2
2025-03-17T16:04:41.805403+03:00 odroidhc4 kernel: xhci-hcd xhci-hcd.1.auto: Host supports USB 3.0 SuperSpeed
2025-03-17T16:04:41.805407+03:00 odroidhc4 kernel: usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 6.12
2025-03-17T16:04:41.805411+03:00 odroidhc4 kernel: usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
2025-03-17T16:04:41.805414+03:00 odroidhc4 kernel: usb usb1: Product: xHCI Host Controller
2025-03-17T16:04:41.805486+03:00 odroidhc4 kernel: usb usb1: Manufacturer: Linux 6.12.19-current-meson64 xhci-hcd
2025-03-17T16:04:41.805498+03:00 odroidhc4 kernel: usb usb1: SerialNumber: xhci-hcd.1.auto
2025-03-17T16:04:41.805503+03:00 odroidhc4 kernel: hub 1-0:1.0: USB hub found
2025-03-17T16:04:41.805511+03:00 odroidhc4 kernel: usb usb2: We don't know the algorithms for LPM for this host, disabling LPM.
2025-03-17T16:04:41.805515+03:00 odroidhc4 kernel: usb usb2: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 6.12
2025-03-17T16:04:41.805546+03:00 odroidhc4 kernel: usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
2025-03-17T16:04:41.805555+03:00 odroidhc4 kernel: usb usb2: Product: xHCI Host Controller
2025-03-17T16:04:41.805564+03:00 odroidhc4 kernel: usb usb2: Manufacturer: Linux 6.12.19-current-meson64 xhci-hcd
2025-03-17T16:04:41.805567+03:00 odroidhc4 kernel: usb usb2: SerialNumber: xhci-hcd.1.auto
2025-03-17T16:04:41.805571+03:00 odroidhc4 kernel: hub 2-0:1.0: USB hub found
2025-03-17T16:04:41.808197+03:00 odroidhc4 kernel: usb usb1-port2: connect-debounce failed
2025-03-17T16:04:41.813503+03:00 odroidhc4 kernel: systemd[1]: Reached target usb-gadget.target - Hardware activated USB gadget.

As I understand it, the error is:

2025-03-17T16:04:41.808197+03:00 odroidhc4 kernel: usb usb1-port2: connect-debounce failed

After rolling back to 6.6.63 kernel - USB works fine.

What other information can I provide to help identify the problem?

I have a problem with "sudo apt update && apt upgrade -y" of my Nano Pi R4S

1) if i use ru_RU.UTF-8 and RU timezone than i have:

W: Не удалось получить http://apt.armbian.com/dists/bookworm/InRelease 502  Bad Gateway [my_ru_ip_addres]:[Port_80]
W: Некоторые индексные файлы скачать не удалось. Они были проигнорированы, или вместо них были использованы старые версии.

Translations:

W: Failed to get http://apt.armbian.com/dists/bookworm/InRelease 502 Bad Gateway [my_ru_ip_addres]:[Port_80]
W: Some index files could not be downloaded. They were ignored or old versions were used instead.

2) if i use US locations and RU timezone than i have:

Err:7 http://fastmirror.pp.ua/armbian bookworm/main arm64 armbian-bsp-cli-nanopi-r4s-current arm64 24.11.1                                                                                                                             
  Cannot initiate the connection to fastmirror.pp.ua:80 (2a01:d0:fa02:5555:6829:17ff:fe25:da0c). - connect (101: Network is unreachable) Could not connect to fastmirror.pp.ua:80 (93.126.105.202), connection timed out
Err:9 http://fastmirror.pp.ua/armbian bookworm/main arm64 linux-dtb-current-rockchip64 arm64 25.2.1                                                                                                                                    
  Cannot initiate the connection to fastmirror.pp.ua:80 (2a01:d0:fa02:5555:6829:17ff:fe25:da0c). - connect (101: Network is unreachable)
Fetched 159 MB in 1min 58s (1,341 kB/s)                                                                                                                                                                                                
E: Failed to fetch http://fastmirror.pp.ua/armbian/pool/main/a/armbian-bsp-cli-nanopi-r4s-current/armbian-bsp-cli-nanopi-r4s-current_24.11.1_arm64__1-PC980a-V0406-H3400-B6e44-R7697.deb Cannot initiate the connection to fastmirror.pp.ua:80 (2a01:d0:fa02:5555:6829:17ff:fe25:da0c). - connect (101: Network is unreachable) Could not connect to fastmirror.pp.ua:80 (93.126.105.202), connection timed out
E: Failed to fetch http://fastmirror.pp.ua/armbian/pool/main/l/linux-dtb-current-rockchip64/linux-dtb-current-rockchip64_25.2.1_arm64__6.12.12-Sd914-D7b0b-P083d-C67e9Heb51-HK01ba-Vc222-B8de6-R448a.deb  Cannot initiate the connection to fastmirror.pp.ua:80 (2a01:d0:fa02:5555:6829:17ff:fe25:da0c). - connect (101: Network is unreachable)
E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?

I mean connection failed

As for accessibility you can use free hosting for the Arambian repository for users located in Russia.

@Igor @Werner could you pls to change for RU users arambian repo, for example, it may be https://sourceforge.net/ servers by default update and upgrade, and problem with Arambian update and upgrade will be sloved for RU users

I mean https://sourceforge.net/
Because they provide free hosting and free repository hosting for OpenSource projects
For example, if you know VPN PassWall/PassWall2 uses https://sourceforge.net/ for repository hosting.

Connection to http://apt.armbian.com/ servers is not available in Russia right now or it may be my provider problems.
Connection to http://fastmirror.pp.ua/ servers is not available in Russia right now or it may be my provider problems.
Connection to https://sourceforge.net/ servers is available in Russia right now. <-

Or could you pls advise how i can fix the problem ?