Igor

Support for rotation is better in modern 6.18.y Linux. Fastest is to download image and try https://www.armbian.com/boards/roc-rk3399-pc But VPU acceleration in rotated screen might be a problem ... and you will need to generate Gnome desktop image to facilitate Wayland or no fun.

What's new in armbian-config desktops Pick how much desktop you want — at install time and after Three tiers (minimal / mid / full) instead of one monolithic install. Minimal = DE + display manager + a terminal (~500 MB). Mid adds a browser and everyday apps (~1 GB). Full adds office + creative tools (~2.5 GB). And you can move between tiers later — armbian-config knows the delta and only adds or removes what changed, no reinstall. Clean uninstall, every time Every install records a manifest of exactly which packages it added. Removal undoes only those — packages that were already on the system before you installed the desktop stay put. No more "I uninstalled XFCE and lost half my system." One YAML per desktop, no per-distro hacks Each DE is a single declarative file in tools/modules/desktops/yaml/. Adding or maintaining a desktop no longer means editing scripts; you describe what you want and the engine figures out releases, arches, browsers, and overrides. Adding a new desktop is a YAML edit and a parser smoke test, not a hunt through bash. Same desktop, every supported distro and arch Per-release and per-arch overrides handle the awkward edges: missing packages on armhf, the riscv64 ports that lag behind, the package that got renamed in Ubuntu noble. Same YAML works on Debian bookworm/trixie and Ubuntu noble across amd64 / arm64 / armhf / riscv64. Smart browser selection The literal token browser resolves to the right package per platform automatically — Chromium where it exists, Epiphany on platforms where Chromium is broken, Firefox-ESR on Debian riscv64. No more bug reports about "Chromium won't install on RISC-V." Custom vendor archives, done right Optional repo: block per DE with full support for: signed-by GPG keyring (no apt-key), per-release suite paths (e.g. SpacemiT's per-snapshot bianbu archive), multi-suite fan-out (one archive, six deb lines for security/updates/customization channels), wider component lists than main, and APT pin preferences in the same place. Removed cleanly on uninstall. Auto-login that doesn't trash your config Enable / disable autologin for gdm3, sddm, or lightdm via in-place sed edits — your WaylandEnable=false and other customizations stay intact. Branches on ID=ubuntu from /etc/os-release, so it writes to the right file (Debian's daemon.conf vs Ubuntu's custom.conf) without guessing from the codename. A weekly AI driven self-audit catches drift A scheduled workflow scans the YAML matrix against armbian/build's supported releases and the live Debian/Ubuntu archives — flags releases not yet covered, flags packages that no longer exist upstream — then opens a draft PR with proposed YAML fixes. Dead packages and missing releases stop accumulating silently. armbian-config --api module_desktops User documentation: https://docs.armbian.com/User-Guide_Armbian-Config/System/#desktop

Worth trying all of them.

Open source projects like ours operate with very limited resources, and infrastructure such as mirrors is maintained on a best-effort basis. We’re aware that things are not always perfect, but addressing this properly requires dedicated maintainers - something we never had. If you’d like to help improve the situation, we’d genuinely welcome someone stepping in to take ownership of this part of the infrastructure. Improving scripts to make this information correct and other things that are missing ... Perhaps contanting mirror owner would already be a solution. I understand - but our mirror system isn’t a standard Debian-style setup. The “empty mirrors” you’re seeing are a cosmetic problem. Only status isn’t automatically pruned yet, so entries can remain listed after they’re no longer active. This does not affect users: traffic is routed through apt.armbian.com and dl.armbian.com, which only serve from working mirrors. What’s missing is automation to keep the public listing in sync - not mirror functionality itself. One of those https://actions.armbian.com/?repo=armbian.github.io needs further development. Our rsync server works: rsync -av rsync://rsync.armbian.com/dl/ I have no clue as this mirror is not under our direct control. Edit: I sent email to administrator of AARNet.

At the begginging of the page https://docs.armbian.com/Mirrors/#introduction it is written how the system works. What we don't provide on that list is current status of which are live in in sync. However you can check this at any moment: curl http://apt.armbian.com/mirrors | jq

Kernel 3.4 was the last known version supporting NAND boot. Since its deprecation nearly a decade ago, equivalent NAND support has not been integrated into mainline kernels.

Did you ran apt update + upgrade + reboot before ? Edit: we might add warning if installed and running kernel version differs. I ran into this problem myself.

They don't provide images for armhf anymore. Last build was 3 years ago: https://hub.docker.com/r/owncloud/server/tags?page=1&ordering=last_updated&name=v7 We made a notice that its compatible for amd64 and arm64: https://docs.armbian.com/User-Guide_Armbian-Software/Media/#owncloud but our installer doesn't filter that out yet. Official Docker way, it won't work. Try something else, perhaps

Did you perhaps upgrade kernel and forgot to reboot?

https://docs.armbian.com/Process_Contribute/#adding-a-new-board

[ 1.234958] rockchip-pcie f8000000.pcie: PCIe link training gen1 timeout! [ 1.235032] rockchip-pcie f8000000.pcie: probe with driver rockchip-pcie failed with error -110 PCI support on this SoC has never been fully stable. Patch that tries to mitigate the issue, exists: https://github.com/armbian/build/blob/main/patch/kernel/archive/rockchip64-6.18/rk3399-fix-pci-phy.patch Not really much we can do more - use a kernel that it works, try current one with few reboots, ... I know its not perfect but we have nobody that can afford investing few weeks trying to fix this. Imagine the frustration if nothing will be improved - which I highly suspect for this case.

We made several test install on Windows 11 and it always worked ... bugs are possible. Best here: https://github.com/armbian/imager/issues And add perhaps more information about the OS, hardware, any special settings that might play a role here. I don't think there is. As far as I can recall, we haven't see this problem yet. Let's ping main developer - if he has any ideas. @SuperKali But as this is a complex software with possible bugs deep down in some libraries, or even Windows itself - I assume you run with all updates?

Try to build from this PR: https://github.com/armbian/build/pull/9381 - use CURRENT branch - enable additional DEBUT if it doesn't proceed - leave u-boot as is or try with most recent

Latest is behind translation: Debian Trixie https://dl.armbian.com/helios64/Trixie_current_minimal with preinstalled OMV: https://dl.armbian.com/helios64/Trixie_current_minimal-omv

https://github.com/armbian/build/blob/main/config/boards/bigtreetech-cb2.conf#L8 Nope. We don't support vendor kernel for other then 3588 and more recent. We don't maintain vendor kernel for this hardware (nor any other 3566 AFAIK), so it might be some work and its all on you. Mainline support is very mature, however I don't know about the status of specific features you are interested in. IMO its not worth going vendor route on this hw.