All Activity

Aliexpress randomly assembled electronics is expected to fail - you need to lower expectations, count on luck, read forum for clues, DIY. Little better are single board computers, then what is declared as supported, best what is platinum supported (for this use case FriendlyElec R3S would be perfect) following by Raspbbery Pi and x86 hardware. If you are looking for top first time experience buying a server, you should stick to https://www.supermicro.com/en/ I can assure you that Armbian works perfectly on any of servers they sell. But yes, price does not match.

up all night, finally got it working. list of stuff I did: download latest 2505 bookworm-xfce and reburn the u-us card 3 times. copied 40 entry /etc/hosts file from working machine. edit /etc/hostname to change it to unique name amanda, then make it immutable as that did not survive a reboot. rm 10-* in etc/netplan, rename armbian.yaml to 10-armbian.yam editing it as needed, and edit /etc/nsswitch.conf to make network setup start as "hostname files dns" rebooting after each stage. So hostname now stays at amanda, and nsswitch.conf works as ordered. I can ping yahoo.com in addition to my other local machines and have now updated 208 pkgs. rebooted looks ok. Now I can get back to making a 20T lvm out of 5 4T SSD's, But first some breakfast and a shot of insulin, and a nap while the local weather settles, its poured piss out of a cowbarn boot most of the night. Thank you for the links, they were educational.

I can confirm: https://paste.armbian.de/oxupahozud

Not sure if the target board makes a difference. But FWIW, my compilations for rockpi-4b and orangepi5-plus exhibited the issue while the one for bananapim2plus did not.

@Mike H This is a community forum, and your message is for everyone. Armbian maintainers are part of this community, but please keep in mind that support here is provided on a best‑effort basis by volunteers and maintainers who give their time when they can. In open‑source projects, especially those maintained by communities, work is prioritized based on available time, skills, and resources. Sometimes an issue might be addressed quickly; other times it may take months — or it may not be addressed at all if the effort required is too great compared to the benefit. This is a normal reality in community‑driven software development. The concept of sunk cost often plays a role in deciding whether to invest effort in fixing certain issues. It’s worth noting that even in large, well‑funded projects, some bugs remain unresolved for years. In our case, resources are far more limited — for example, Raspberry Pi OS has a budget exceeding €1M annually for one platform, while Armbian supports many platforms with a fraction of that funding, outside few boards we have some small maintaining budget, there is only a beer money, and far fewer people. Best-effort is the only promise that can be provided under such circumstances. We appreciate bug reports, even they have nothing to do with our work as we understand users often can't judge that, but we ask that no pressure be placed on contributors to resolve them on demand. In some cases, solving an issue can take weeks or even months of work, which is not something users can reasonably expect from volunteers. And there are thousands of bugs already in the to do list. Finally, please understand that part of the challenge we face is that some projects already monetize or re‑brand our work while presenting it as inexpensive and easy to maintain — when in reality, it’s not. This can create misunderstandings about the real cost and effort behind keeping a complex software stack running. Your report is welcome, but we ask for patience, understanding, and respect for the time and resources of those trying to help. Pressuring volunteers to prioritize some issue, or expecting them to personally fund the work, is neither reasonable nor effective way to fix bugs.

armbian-config way is limited in its use - it's intended for quick start when networking is simple. When you need something more complex, its always the manual way: https://docs.armbian.com/User-Guide_Networking/ If you wanna look how Armbian deals with networking in the backstage: https://github.com/armbian/build/tree/main/extensions/network In case of desktop images (original, not self constructed), XFCE will have Network manager.

You are already discussing this elsewhere. Please don't post several times about the same issue.

netplan is a joke. It looks like it might work IF ipv6 was totally disabled. everything I've entered has been applied to /dev/br0. but shown while entering it as end0 This is totally broken. Can I still put this crap in /etc/networking/interfaces.d? Help please.

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

Pointing out that you are not even willing to put your own words into a search engine is "condescending"? That takes 5 seconds or less when you claim to have put months and months into it. You are expecting others to do the work for you. I find that quite presumptuous. And no, we do not know there is a bug in Armbian. You haven't done enough research to know enough to claim this for certain. I will put the chances of that being the case at fity-fifty at best. You also have presented no logs whatsoever (even after being asked) to even give others the moderate chance to do this work for you (for free). If you came here to vent, OK, you have now vented. If you came here for a solution, then sorry to say, but you are not even doing the very minimum to get that done.

Network setup in the latest bookworm+xfce's armbian config won't allow a network setup I've been using for 25 years. Its an all ipv4 static setup using hosts files. It apparetly asumes only valid ipv6 addresses but the nearest ipv6 enabled ISP is over 100 miles away from me in north central West Virginia USA.The idea is it will query the router for any name not found in the /etc/hosts file. Thhe switch trigger being a hardcopy /etc/resolv.conf. This is normally and instantly accomplished as dd-wrt caches previously looked up addresses. And if not found in dd-wrt's cache it relays the request to my ISP's dns server. BUT BUT BUT armbian-config refuses to accept valid ipv4 addresses by hashing them to apparently random errors, digits duplicated or left out When looking at the results no dhcp4 or 6 of is enabled as expected. So how do I fix this first boot problem? This is all on a banannapi-m5 I intend to make an amanda-3.5.4 based nas out of. Thanks for any help. The solved x tag is a lie as it won't post w/o it.

Good afternoon! Thank you for your answers and advice. I didn't buy it because it was cheap, but because I wanted to buy a server and didn't know how much it actually cost. It was my first time buying a server, and I had a bad experience.

If you look at it from my point of view there's a bug in armbian. At the very least it's now been reported even if I'm not clever enough to figure it out. You aren't showing much sympathy to the regular users trying to help out by such condescending language.

Of placing the device back with a new kernel/distro or even doing testing on it. I don't travel much and my friends who do don't have any experience nor equipment to change things.

For sure, no. It's a S905X5M https://www.hardkernel.com/shop/odroid-c5/ The C4 is a S905X3

Coming back to this... I'm not having any luck getting overlays to work, but I'll need to get out my serial logger to see what's wrong I guess. I'm trying to get the USB-C into host mode on my RockPi-S. I can do it by editing the rk3308-rock-pi-s.dtb file directly, but not using an overlay file. Here's the overlay file I've tried (usbc-host.dts): /dts-v1/; / { fragment@0 { target-path = "/usb@ff400000"; __overlay__ { dr_mode = "host"; }; }; }; and /dts-v1/; /plugin/; / { fragment@0 { target-path = "/usb@ff400000"; __overlay__ { dr_mode = "host"; }; }; }; Tried using: armbian-add-overlay usbc-host.dts as well as compiling the overlay to a .dtbo and adding the line directly into armbianEnv.txt No joy either way... Also, does anyone know why some .dtbo files also have the line /plugin/; below /dts-v1/; ?

Thank you... I will try with trixie again some time

Armbian build error now on the next line [🐳|💥] Error 1 occurred in main shell [ at /armbian/.tmp/work-9693551e-c3dd-4d65-ae26-dc7dd901481a/uboot-write-IoNha/usr/lib/u-boot/platform_install.sh:7 dd if="$SRC"/cache/u-boot_sdmmc.fip of=$2 bs=512 seek=13312 status=noxfer > /dev/null 2>&1;

two patches make the build problems go away... plus have to specify BOOT_DEVICE=sdmmc on the make cmdline tabris@brunnt:~/build/armbian-build/cache/sources/arm-trusted-firmware/mtksoc-20250212/plat/mediatek/mt7988$ git diff . diff --git a/plat/mediatek/mt7988/bl2/bl2.mk b/plat/mediatek/mt7988/bl2/bl2.mk index 0cfae30a2..19184da07 100644 --- a/plat/mediatek/mt7988/bl2/bl2.mk +++ b/plat/mediatek/mt7988/bl2/bl2.mk @@ -16,9 +16,6 @@ BL2_IMG_HDR_SOC := mt7986 I2C_SUPPORT ?= 0 EIP197_SUPPORT ?= 0 -FDT_SOURCES += fdts/$(DTS_NAME).dts -BL2_CPPFLAGS += -DDTB_PATH=\"$(BUILD_PLAT)/fdts/$(DTS_NAME).dtb\" - BL2_CPPFLAGS += -I$(APSOC_COMMON)/drivers/spi \ -I$(MTK_PLAT_SOC)/drivers/gpio \ -I$(MTK_PLAT_SOC)/drivers/spi @@ -139,3 +136,7 @@ $(error BOOT_DEVICE has invalid value. Please re-check.) endif endif # END OF BOOT_DEVICE + +FDT_SOURCES += fdts/$(DTS_NAME).dts +BL2_CPPFLAGS += -DDTB_PATH=\"$(BUILD_PLAT)/fdts/$(DTS_NAME).dtb\" + diff --git a/plat/mediatek/mt7988/platform.mk b/plat/mediatek/mt7988/platform.mk index 7db8a33c3..233840a38 100644 --- a/plat/mediatek/mt7988/platform.mk +++ b/plat/mediatek/mt7988/platform.mk @@ -24,6 +24,7 @@ RESET_TO_BL2 := 1 PLAT_INCLUDES := -Iinclude/plat/arm/common \ -Iinclude/plat/arm/common/aarch64 \ -I$(APSOC_COMMON) \ + -I$(APSOC_COMMON)/bl2 \ -I$(APSOC_COMMON)/drivers/uart \ -I$(APSOC_COMMON)/drivers/trng/v2 \ -I$(APSOC_COMMON)/drivers/wdt \ Note that I'm *NOT* claiming this will work. Just that the bootloader *builds* with make PLAT=mt7988 BOOT_DEVICE=sdmmc Further, this is me building from inside the docker-shell, it's not doing this for me...

Does anyone have experience with getting Armbian working on an ODROID C5? Wiki Does the C4 image work on the C5?

There is no official support for offline work. You can try OFFLINE_WORK=yes but no clue if it still works.

for more fun... the bootloader doesn't appear to build. I tried both the mtksoc-20250212 and mtksoc-20250711 branches. root@c4b6c21f3c6a:/armbian/cache/sources/arm-trusted-firmware/mtksoc-20250212# make PLAT=mt7988 Building mt7988 CC plat/mediatek/mt7988/bl2/bl2_plat_init.c plat/mediatek/mt7988/bl2/bl2_plat_init.c:10:10: fatal error: bl2_plat_setup.h: No such file or directory 10 | #include <bl2_plat_setup.h> There *is* a bl2_plat_setup.h, but it's not in the mediatek/mt7988 dir but rather mediatek/apsoc_common/bl2. Fixing mediatek/platform.mk to reference that eventually produces a *new* build error root@c4b6c21f3c6a:/armbian/cache/sources/arm-trusted-firmware/mtksoc-20250212# make PLAT=mt7988 Building mt7988 make: *** No rule to make target 'fdts/.dts', needed by '/armbian/cache/sources/arm-trusted-firmware/mtksoc-20250212/build/mt7988/release/fdts/.pre.dts'. Stop.

Then Trixie arm64 is already supported BTW: just managed to use a trixie armhf armbian rootfs as a rootfs container for lxc... it just works, so packages are coming for trixie armhf too 😁 edit: trixie armhf packages added!

Thank you but my use case is orange pi zero 3 and orange pi zero 2w… they are 64 bit H618

Unfortunately, lxc containers are not supplied anymore for armhf targets (see https://github.com/lxc/lxc-ci/commit/8d7326930f824a0aeedb6be3598c64e9e9a6ce36, I read somewhere the build machine has no 32bit compatibility anymore), hence building ffmpeg on Debian Trixie for armhf (32 bits) requires some more trickery.