Igor

No, nothing happened. When I tell gnome-extensions list it return empty. On my x86 desktop running Noble Gnome.

Yes, that's the idea I guess. I played around a bit, but could not enable it with the script ... yet.

You don't need that. Most likely unrelated to this problem, but dd does not verify what was written: https://docs.armbian.com/User-Guide_Getting-Started/#flash-to-sd-card Did you try booting with defaults? Agree, that's not normal. We are seeing some regressions on Allwinner related Crust support to https://github.com/armbian/build/commit/e76540693522baec079ec7633a918a9168ce130c (responsible for low level power management operations) Nothing obvious, no quick solutions based from what is seen from the logs.

Try with one additional parameter: EXTRAWIFI="no"

@mihanson Try new builds from incoming folder https://fi.mirror.armbian.de/incoming/igorpecovnik/tritium-h5/archive/

I have deployed Debian Trixie from download pages - with success. Moved my HA instance on it without any troubles.

Well, I can't tell why USB imager doesn't work nicely. I use it ... sometimes media is not recognized and restarting it usually helps and that is the only problem I experienced with it. For other issues check https://gitlab.com/bztsrc/usbimager/-/issues There is some note that might be relevant: Another alternative tools is RPi Imager. Issues are known and those were my personal experiences while trying to understand why it doesn't work anymore. This was about a year ago, bug was filed at Balena and it seems they didn't fix it yet. Since nothing happened for months, we simply start recommending other tools. Which might not be perfect either - according to troubles you are experiencing.

Etcher is broken on big images. It is out of our power to fix that. Use USB imager or something else.

Updates should now be ok, aren't they?

Weird. Check logs and verify matching - mac - if not changing random - is usually safest way. I haven't played under network manger lately ... perhaps there lies the problem or network devices gets up with a delay. I will try to recreate during week.

OS is stable, errors you are experiencing are likely related to faulty HW component as @eselarm already exposed. And we would most likely notice such anomaly before it gets to you. There are thousands of users and this is the only report of this kind ... Boards are going to the market at high rate, while users support remains more or less the same in past 10 years https://docs.armbian.com/User-Guide_Board-Support-Rules/ Community builds and their upgrades are untested as size of Armbian can only cope with a small selection of boards we call as "standard support", where we have volunteers behind. Community builds are on Debian / Arch images level, but packed with more features. https://github.com/armbian/community?tab=readme-ov-file#purpose-of-this-repository For those - Armbian provides build and hosting infrastructure, place to meet - this forum - while everything else is anyone's problem.

Did you try renaming by using udev rule? Example: sudo nano /etc/udev/rules.d/76-rename-wifi-by-mac.rules SUBSYSTEM=="net", ACTION=="add", ATTR{address}=="b8:2d:28:5a:55:92", NAME="wlxb82d285a5592" and then proceed with whatever. Both systemd-networkd and network manager should work.

Hi. Did you add / enable required overlays ? https://chatgpt.com/share/68a49507-d420-8005-a687-04d8daf0e93a It looks like kernel support is enabled.

Armbian is Debian or Ubuntu with focus into hardware support. https://docs.armbian.com/#what-is-armbian Many operating systems in this segment are derived or use Armbian kernel (development & support) maintained by our team and surrounding community. I do agree with your findings, but this is expected in this world. Achieving and keeping full functionality on custom hardware is hard without substantiation investments or big enough crowd of volunteers / random people that knows special stuff. Both is limited. ALSA is a complex part of engineering that I only understand to some small degree. For most people, including me - is hard to comment. I hope your findings are valuable for someone that knows where to look. Isn't always like this? Sadly, in most cases, problems are solved by investing time for research - code / structure complexity is often extreme, also for people that live source code. Welcome to Armbian forum!

Do you perhaps know how we could integrate this into Armbian? I don't know much about Gnome internals - came this far: https://github.com/armbian/build/blob/main/config/desktop/common/environments/gnome/debian/postinst

I have installed AdGuard https://docs.armbian.com/User-Guide_Armbian-Software/DNS/#adguardhome on a clean Armbian bookworm on some Rockchip device running vendor kernel. Boot logs: https://paste.armbian.com/hibaporove.yaml Reboot and AdGuard normally works after: https://paste.armbian.com/enomawupip.yaml It could be some SD card issue. Try - different one. If you didn't use Armbian install method, then check system logs to see what is failing ... Armbian is Debian or Ubuntu from userspace perspective, so it could be some AdGuard install issue.

Our release will also be around Noble / Trixie + minimal image with Bookworm. For those that wants to stay on a safe side x86 images were already released: https://www.armbian.com/uefi-x86/ and few others ...

If network works - SSH to machine and https://docs.armbian.com/User-Guide_Armbian-Config/System/#alternative-kernels If that doesn't work https://docs.armbian.com/User-Guide_Troubleshooting/

Ports might not be default. Did you use port reported in armbian-config ?

🧟‍♂️🌙☕🛌 Since introducing of systemd (by default in most Linux assemblies in past 10-15 years), its the systemd way: https://www.freedesktop.org/software/systemd/man/latest/hostnamectl.html This way is also handled if armbian-config is used. Also for other things, consider looking into systemd* how-to. Netplan - i understand you might dislike it - is just a wrapper - for systemd-networkd or Network Manager.

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.

@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.