Igor

This looks normal. Most of those boards have bootloaders at locations prior to boot partition. Boot loop. This can be many things - i would guess kernel crash and watchdog issue restart. Why that happens? Hard to tell. This way? sudo screen /dev/ttyUSB0 115200 It should prompt out something.

Quite possible, actually expected as there is no support for current kernel: https://github.com/armbian/build/blob/main/config/boards/orangepi5pro.csc#L8 and build target is not maintained by core Armbian team https://docs.armbian.com/User-Guide_Board-Support-Rules/#community-maintained

That would be good. Cubox-i has standard microUSB connector for serial console, so its easy. That would give some insights on what is happening.

Philosophy behind installations via armbian-config is that install is simple as possible, thus options are limited and hard-coded. Main folder for SW data is /armbian and there you mount additional space, if needed. If this way is not acceptable, you need to go manual way. Installing Redis, PostgreSQL and Immich, then link then together. It will be some work and there will be some troubles. Official: https://immich.app/docs/install/requirements Unofficial: https://github.com/imagegenius/docker-immich Armbian way: https://docs.armbian.com/User-Guide_Armbian-Software/Media/#immich

HDMI output might be broken on this kernel - mainline support is still fragile, perhaps for this board there is no device tree yet and it fails early.

Connected via SSH. DHCP client is automatically getting IP, so you should be able to find the device on network after few minutes ... in case HDMI output is really broken. I can't test that as device is stashed to some rack.

https://paste.armbian.com/ehuwawexih v25.5.1 image (Debian Bookworm minimal) runs on my Cubox i4, but HDMI out is untested ... images were released, only because I manage to spent some time testing and as I found out that build actually works.

Fresh Orangepi 5 image, this one: https://netcup-01.armbian.com/incoming/efectn/orangepi5/archive/Armbian_25.8.1_Orangepi5_noble_vendor_6.1.115_gnome_desktop.img.xz Your setup could be broken to some degree, but hard to tell what is missing.

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.