All Activity

I can't understand why no one in the world has thought of releasing another 64-bit ARM motherboard with 4 SATA ports or 6 SATA ports. And that way, we don't have to end up buying a Synology or something worse... I guess we're heading for extinction like dinosaurs.

firepower https://github.com/NickAlilovic/build/releases/download/20250306/Armbian-unofficial_25.05.0-trunk_Vontar-h618_bookworm_edge_6.12.11_xfce_desktop.img.xz https://github.com/NickAlilovic/build/releases/download/20250306/Armbian-unofficial_25.05.0-trunk_Transpeed-8k618-t_bookworm_edge_6.12.11_xfce_desktop.img.xz this?

E: Unable to correct problems, you have held broken packages. [💥] error! [ Failed to install host packages; make sure you have a sane sources.list. ] [💥] Cleaning up [ please wait for cleanups to finish ]

There was ssv6x5x android drivers in the tanix and vontar firmware i upload. You could try them.

Hi catotinha, Once you know the ip that the router assigned to you (if you go to the settings of the router where you have the devices connected, and see there what the Orange Pi is) just make it in Windows that you are on the same network with the command line with administrator privileges "ssh root@192.168.1????. Then enter "root" and "1234". Then just ask ChatGPT for help and a whole world of possibilities opens up. I was just yesterday asking him for help, since mine, from time to time, freezes". So good luck, and please share your experience. It may also be useful to me. Big hug,

This 3rd party module needs both kernel headers and kernel source. The Makefile bundled with the code applies patches to an existing kernel module source code and compiles it. I ran the build script on a separate debian vm and created a tarball of the source tree. i will try to transfer it to the opi later today.

The kernel headers that you have installed are quite enough to build the kernel module, the source codes of which you have. If the source codes are already in the kernel, then you just need to configure the kernel before compiling. launch: After you finish the configuration, the build system saves your configuration file (it will tell you where it did it). Save it under the name ./config/kernel/linux-sunxi64-current.config It is assumed that you are in the armbian/build directory. launch: ./compile.sh BOARD=orangepizero2 BRANCH=current kernel

@svyatoslav there’s a driver for the wifi chip but it only works on older kernels. You’ll need to port the code over to the latest kernel. https://github.com/paolosabatino/ssv6x5x/tree/master Click on the show csc/wib/eos/tvb button. You will see x98h and other h618/h616 boxes there.

Good day people. Tell me, there is an ancient 4k ULTRA HD PRO 2/16 Gb H96MAX box (blue board). After installing armbian 23.08.0 on it, everything works well RIGHT AWAY even without using overlays. However, after apt upgrade, armbian25.2.3 arrives and the system hangs at boot. The inspection showed that in/boot/dtb/( in reality it is/boot/dtb-6.3.13-rockchip64/rockchip) there is no hardware tree). Moving the hardware tree from 23.08.0 allows the system to boot, but hdmi hangs (by ssh the system works, but the screen of the real console hangs). In addition, WiFi is no longer visible (it is not in the settings at all), connection is possible only by RJ45. Question: are there any chances to make 25.2.3 work normally (and what is needed from me for this) or just fix the system on 23.08.0? PS Many thanks to the community for working image 23.08.0

@kvvvp try this sudo update-alternatives --set iptables /usr/sbin/iptables-legacy sudo update-alternatives --set ip6tables /usr/sbin/ip6tables-legacy

wrong. auto-login is enabled on serial and hdmi only. ssh default login is always root/1234

Thanks for the reply, Pilinha. How did you manage to SSH into the system without a keyboard? I planned to do that, but then i realized that I needed to set up a root password beforehand and I could not do that without a keyboard.

Thanks, Igor. I totally understand that when this project started you guys had to take care of a handful of boards and now there must be hundreds of them and that it is not feasible to support every one of them, especially the older ones. It is indeed clearly marked as community support on the board page. I, nonetheless, accepted the challenge (I might fail, I might succeed). Thank you for your work, in general, and for the links, in particular (which I will read).

I am getting a thermal zone failure message during boot, which has always happened with kernels after 6.6, at least as far as I know. Is this error actually harmful? HardWare:NanoPi NEO2 Armbian Version: Packages: Debian stable (bookworm) v25.2.3 for NanoPi Neo 2 running Armbian Linux 6.12.20-current-sunxi64 Support: DIY (community maintained) Kernel: Linux nanopineo2 6.12.20-current-sunxi64 #1 SMP Sat Mar 22 19:54:28 UTC 2025 aarch64 GNU/Linux dmesg output [ 7.018086] core: _opp_supported_by_regulators: OPP minuV: 1320000 maxuV: 1320000, not supported by regulator [ 7.018125] cpu cpu0: _opp_add: OPP not supported by regulators (1104000000) [ 7.018245] core: _opp_supported_by_regulators: OPP minuV: 1320000 maxuV: 1320000, not supported by regulator [ 7.018258] cpu cpu0: _opp_add: OPP not supported by regulators (1200000000) [ 7.018413] core: _opp_supported_by_regulators: OPP minuV: 1340000 maxuV: 1340000, not supported by regulator [ 7.018426] cpu cpu0: _opp_add: OPP not supported by regulators (1296000000) [ 7.018552] core: _opp_supported_by_regulators: OPP minuV: 1400000 maxuV: 1400000, not supported by regulator [ 7.018564] cpu cpu0: _opp_add: OPP not supported by regulators (1368000000) [ 7.019699] thermal thermal_zone0: binding cdev cpufreq-cpu0 to trip 3 failed: -22 [ 7.019785] thermal thermal_zone0: binding cdev cpufreq-cpu0 to trip 4 failed: -22 dmesg.txt

Early May brought another round of steady advancements to the Armbian project, with progress in U-Boot updates, board enablement, firmware fixes, and notable improvements to Armbian’s growing catalog of self-hosted applications. Bootloader and Firmware Enhancements Several platforms saw significant U-Boot improvements. The Cherryba-M1 now benefits from an upgraded U-Boot and reorganized patch structure, thanks to Igor‘s work on upgrading Cherryba-M1 to latest u-boot and moving patch to new folder. Andy bumped U-Boot to v2025.04 for the Lubancat2, keeping the board current. The Radxa Rock 4 SE also migrated to this version, where Niklas refined its configuration and boot behavior. Meanwhile, the Khadas VIM3 received a broader bootloader overhaul led by Ricardo, introducing SD-first boot order, squashfs and fileenv support, and enhanced compatibility with Home Assistant OS in a comprehensive update to U-Boot for Khadas VIM3. Older configurations didn’t go unnoticed: Igor removed deprecated ATF tags for sun50iw9 / H61x, while Olaf pushed the sunxi64 platform to the latest LTS version of ATF. Expanding Device Support Armbian continues to grow its ecosystem. Rolf introduced official support for the Banana Pi M2+, making it easier for users to deploy on this compact board. On the RISC-V side, libiunc brought the kernel for the StarFive2 platform up to v6.6, ensuring ongoing support and compatibility. Installer Improvements and Runtime Fixes Improving install experience, Igor Velkov added Btrfs root subvolume support when installing to NVMe, paving the way for better snapshot and maintenance workflows. Igor also corrected missing Broadcom firmware for Raspberry Pi boards to fix wireless support and suppressed firmware warnings related to built-in Realtek USB network drivers, helping clean up logs and reduce confusion. Self-Hosted App Catalog Grows The list of installable apps during Armbian setup has expanded. Two powerful platforms are now just a selection away: Immich, a self-hosted photo and video backup system, was added with the introduction of Immich to configNG. NetBox, a leading infrastructure resource management solution, joined the roster in the addition of NetBox to Armbian configNG. Both are available via the configNG provisioning interface. Deprecations and Housekeeping Support for legacy distributions has now ended: Debian Bullseye and Ubuntu Focal and Jammy will no longer receive repository updates, as noted in the userspace status change to EOS. Elsewhere, dependency and CI maintenance continued. Automated tools like Dependabot bumped packages such as setuptools and GitHub actions for changed-files, while amazingfate restored support for the AIC8800 Wi-Fi driver by reverting a mistaken disable. Further Reading Explore the full range of updates in the official Armbian snapshot. The post Armbian Development Highlights – Early May 2025 first appeared on Armbian. View the full article

I set the version in userpatches/lib.config , then executed this: ./compile.sh BOARD=orangepizero2 BRANCH=current kernel-config KERNEL_BTF=no KERNEL_GIT=full and when the kernel menu came up, just exited to shell. Is this the kernel source directory I can point the compiler script of the module ? /build/cache/sources/linux-kernel-worktree/6.12__sunxi64__arm64$ ls arch COPYING defconfig fs io_uring Kconfig LICENSES mm rust security usr block CREDITS Documentation include ipc kernel MAINTAINERS net samples sound virt certs crypto drivers init Kbuild lib Makefile README scripts tools

this is what dmesg looks like I decided to assemble it myself, but it was not there, which one to choose? same thing, what to do next? dmesg.txt

Hi, Providing logs with armbianmonitor -u helps with troubleshooting and significantly raises chances that issue gets addressed.

if you want zfs on recent kernel you've to compile it manually, this worked on kernel 6.14.5 on Radxa Rock 5 ITX.

No, unfortunately not. But there was an image, among many others that I tested that worked, but it had other problems, I don't remember anymore. And even if I want to recover it, I can't find it anymore. I spent a lot of time testing a lot of images, and then I just started putting in a folder the ones that ran well at boot and started without problems. I have a four or five, but all without working usb ports. However, since I only wanted to install the Pi-Hole on it, I found that I could access it via a computer via SSH. And since then everything has been much easier, even higher with the help of our friend CHATGPT!! And even then, the image that finally worked is where I installed the Pi-Hole. must have problems. From time to time it freezes. I see that I'll have to test others. If there is news, I will say so. And if you also have any news, please share it. Hug

We just figured out we have dropped packing kernel sources at some point. Until we figure out how to re-enable that or if this makes sense, use build framework to add a custom module. It has the ability to do that. Allwinner kernel is heavily patched, version is not necessarily latest, quite distanced from mainline, while Amlogic, on the other hand, is closer, changed less.

Welcome on board. This will be a huge difference, so be open for learning, have a lot of patience. https://docs.armbian.com/User-Guide_Board-Support-Rules/ One of the key challenges we face is that maintaining older hardware is both time-consuming and costly. With limited financial and community support, the resources we have are already stretched thin across the entire project. Our team is very small—currently, we have only one dedicated maintainer for the Allwinner software stack that is focused into latest 64bit Allwinner family (H6/H6xxx). Other projects often face similar constraints, often relying on a single contributor who can do anything. For example, in our collaboration with LibreELEC (LE), we benefit from some shared efforts, but both sides are still primarily driven by individual volunteers working on a best-effort basis. If priorities shift, progress can be delayed significantly—and unfortunately, Armbian doesn't have the capacity to pick up. I’m sharing this openly in the hope that it raises awareness. Personally, I would love to see continued support for legacy devices. But to make that happen, we need to ask: who is willing and able to invest weeks or months each year required to maintain these older platforms? What you can do? Try to understand how this works, connect with people that share your problem (all similar board owners with interest that it is maintained) - invest time to learn. Probably USB ports are just not enabled - check this: https://docs.armbian.com/User-Guide_Armbian-Config/System/#device-tree-overlays

Yes correct the SSV6252p is hard to get it run because no support , the MSN8800D i think was a old chip from i-phone or a clone from something , support looks bad ( only some one match with google ) but its have nothimng to do with emmc support , maybe this board has nand or eMCP memmory and than also emmc not found ( Nand only in legacy image support , eMCP only with correct led-config sometimes) when you have exp in hot air soldering maybe swap the wifi this a best solution or use usb stick

Broadcom brcmsmac(PCIe) and brcmfmac(SDIO/USB) drivers https://wireless.docs.kernel.org/en/latest/en/users/drivers/brcm80211.html Broadcom brcmfmac driver Support for both 32 and 64 bit Linux kernels Firmware installation Current For SDIO driver you need to copy the nvram for your system and place it in /lib/firmware/brcm. The nvram file name depends on the chip you have. The kernel log will tell you the exact file name. For the USB driver no nvram file is strictly needed: in fact, the driver only loads the firmware blob and does not look for an nvram text file. However, the nvram parameters are still required and they are already part of the firmware blob. This is a TRX file which contains the nvram parameters as a sequence of zero-terminated plain text strings, appended at the end of the last section. For an example of how to modify/add nvram parameters for USB devices, see this post: https://elimo.io/2-4ghz-coexistence-reverse-engineering-broadcom-chips-to-enable-packet-traffic-arbitration/ The firmware files are located in the linux-firmware repository and can be copied as is to /lib/firmware/brcm. SDIO chip on older kernels (before 3.13) In kernel priors to v3.13 the SDIO driver used generic firmware names. Below are the instruction Use the nvram file installed in your system and copy it to /lib/firmware/brcm/brcmfmac-sdio.txt The firmware can be found in the linux-firmware repository. For 4329: cp brcm/brcmfmac4329.bin /lib/firmware/brcm/brcmfmac-sdio.bin For 4330: cp brcm/brcmfmac4330.bin /lib/firmware/brcm/brcmfmac-sdio.bin Alternatively, when not available the Android version can be used as well: git clone https://android.googlesource.com/platform/hardware/broadcom/wlan firmware files: bcmdhd/firmware/bcm4329/fw_bcm4329.bin bcmdhd/firmware/bcm4330/fw_bcm4330_b2.bin NVRAM from EFI Some new devices are storing the nvram which is needed in addition to the firmware by the driver in an EFI variable and the Windows driver can access it (this file should be optional in the case of PCIe devices). Currently brcmfmac does not support this automatically. First mount the efi vars into sysfs: mount -t efivarfs none /sys/firmware/efi/efivars The content of the nvram is in this file: /sys/firmware/efi/efivars/nvram-74b00bd9-805a-4d61-b51f-43268123d113 Copy this file where brcmfmac expects the nvram, for example: cat /sys/firmware/efi/efivars/nvram-74b00bd9-805a-4d61-b51f-43268123d113 > /lib/firmware/brcm/brcmfmac43241b4-sdio.txt