Igor

Perhaps this ? https://github.com/armbian/build/issues/6132

Oh, we are missing this utility? Will be added when possible. https://armbian.atlassian.net/browse/AR-2059

It was confirmed working with Debian Bookworm based images. For Ubuntu Jammy you need to find a way to backport Mesa driver for Noble (try nobble instead of unstable) and it will also (probably) work.

Did you read text here https://www.armbian.com/rpi5b/ ?

I don't know. It was tested on Odroid N2 and Nanopi M4. If you seek for plug and play solution and you don't want to support open source development, buy a Raspberry Pi, Odroid N2, ... I am afraid, that is not the case. https://docs.armbian.com/User-Guide_Getting-Started/#how-to-check-download-authenticity.

I have also disabled both mirrors from rotation until we develop & implement a proper solution to our router.

Can provide only dumb answer. Its not directed to you in person ... There is an add out there for almost a year. Nobody wants to use opportunity to learn and help you. Without maintaining automation ... things breaks down. Same will happen with board X, after we stop doing what we do. There is very little help elsewhere too. People don't want to know how much Armbian lost by providing you (and competitors, vendors, you ... that have no interest to cover our costs), those images. No, nobody asks, nobody cares, so we can live with what we already have. You assume this is what we do for fun? To some degree it is, but fun stops when abuse and blackmailing starts. Which is constantly present. Way too many people use all kind of tricks trying to manipulate with us to solve their computer problems in our private time. Welcome to Armbian forums Stay tuned, images will be back when they will be back.

Yes, but we are slowly applying automation. We currently don't have a dedicated person for website works and this is done by Effe with my assistance https://armbian.atlassian.net/browse/AR-909 (Automatic synchronization of board status between GitHub and website hasn't started yet)

I doubt that our last images are broken as this is one of popular devices and this is the only report I can remember. Also we are running test automation, which shows not problems. However, non working images can exists, ... we keep previous versions for you to verify quickly: "Current images doesn't work ..." ... if its something on your side (powering, SD card) or image is broken. Official images are few years old version of Armbian with different boot loader and kernel. Can you attach UART to the serial console and see where it stops?

This could be one option: But beware that most of those cards, including this one, uses SATA port multiplication. For spinning rust over gigabit line this is enough ...

Follow instructions armbian-config -> software -> install headers This is the package name: # apt search linux-headers-current-bcm2712 Sorting... Done Full Text Search... Done linux-headers-current-bcm2712/jammy 23.11.3 arm64 Armbian Linux current headers 6.1.74-current-bcm2712

VMware ESXi on non Raspberry Pi is not usable (yet) in production, to install it and forget about. Several features does not work (stable) and overall performance is questionable. Here one can observe more, dunno how up2date is that documentation ... Orangepi is good enough for running Armbian and similar OSes and here one can run KVM virtualization. That will work fine, perhaps not the best with this board as mainline kernel still has rough edges.

Make an apt update + upgrade. Kernel + header combo exists for 6.1.74 and it should be there for future versions.

We have no plans or budget to support this hardware. Finished assembly will be provided only for small selection of boards, most likely we will provide this for platinum support section only. Purpose of the topic is promoting Armbian build framework. If something can be done on board X, we can't help to make it on board Y. Without investing tens or hundreds thousands of dollars. This is your problem. Board provider problem. Not ours. Build framework can do this, but if board is not maintained ... it might not just work.

Yes. https://github.com/armbian/build/commit/833e1c20c63ea3da7f1323429828e94eaa9b52c7 We forgot to pin it to the commit / version. Its still branch: https://github.com/armbian/build/blob/v23.11/config/sources/families/odroidxu4.conf#L24

We pin major releases this way (branch v23.11) https://github.com/armbian/build/commit/d69350a88447ee64bbb50b443f86858a7f6f4075 while main (or some tag) is not. For mainline based, check this: https://github.com/armbian/build/blob/main/config/sources/mainline-kernel.conf.sh Main branch is updated and fixed daily in case upstream messes up. Just keep rebasing.

6.1.74 current and 6.6.13 edge are going to be available on stable repository shortly after this is done: https://github.com/armbian/os/actions/runs/7708966983

I am sure you do. Me too. I am just saying that project doesn't have enough support from users side to cover for maintaining this device. For you and all other open source projects ... I am sure you would not complain if there would be a better option out there. Making sure that everyone that reads this understands, that Armbian project is not to blame for the troubles you have. We didn't sold any promise of support, HW vendors usually do that. That is one reason why I replied and second to inform you that there is some progress on both devices so they are not completely paperweight. There is a hope. It is. I wish you all the best. See, we have something in common

What feelings do you have to people that maintain it with their free time and private savings? Do / did you help them? Without those people, hardware is just a paperweight, a fake promise. Package updates and kernel updates are common for many devices. We officially stop dealing with Helios64 long time / several years ago. I think it was even never officially supported. After that, it was up to random / nobody to maintain it. In past year there was some self organised attempts to improve Helios64 https://forum.armbian.com/tags/helios64/ while I think Helios4 works just fine and also there we have someone that will keep it in good shape.

Reason is in exploitation nature of economical relations between parties - "you don't fund our work, but steal from" vs. "we paid for hardware, software is free" vs. "Buy 16core 32Gb NVME 2.5G PCI ... hardware that runs any Linux" We would very much invest a lot more, but someone needs to pay our bills more then 0.5%. Several people behind Armbian also works full time in order to maintain this place and all our forks and upstream distributions that are "porting from Armbian: Manjaro, Arch, NixOS, Debian, ...". There is big misconception and common believe that hardware vendors helps us. Sadly no. They don't help. With small exceptions they do everything to (ab)use our work and efforts, community development, this place, you. Whatever they are communicating, their aim is to sell hardware with promise of software support, with proprietary builds and closed features where only they have the key. Such as video 3D (opened by community on old chips), acceleration (opened on old chips), AI acceleration (closed ATM). Its a love / hate relationship. Some of things that are done in this (yet another new hardware - why we need Zero 3? 4 needs only making marketing material, board is done in a day) are fun, while (real and long term) maintenance is hard and inglorious work people tend to avoid. Getting amateurs to maintain this large, complex and disorganized egocentric landscape ... is very very hard. A lot of patches we maintain are here because upstream is wild wild west, often unfriendly to community (sometimes with a good reason) and friendly to corporate that can afford to develop at required quality level standards and also a place of deceptions. Vendors efforts are done once their HW is "supported" by mainline Linux (with "supported by Armbian" its the same), but in reality, often nobody maintains those boards and its also impossible to verify if things are alright at merge time. Some patches that we made were also simply up-streamed by removing the origin. Which is the lowest act open source developers can do. Sadly this also happens and its pointless to waste time to prove and take actions. And fight for your (c) for the job you have done for free in organised manner. Armbian is here 10 years. For us maintaining is a long term mission, done in as organised way as possible in order to save our time. u-boot is yet again, a raw material. In ideal world, all this low level job should be covered by vendors. But its not done by them. Its done by you, me and people around communities as ours, once by us, once by OpenWRT, LibreElec or similar project that stick their noise into low level world.

Provide pictures of your board from both sides.

Armbian still support this way. I verified yesterday on Ubuntu Jammy derivative. Just add some command like touch /run/test following by reboot, login and see if file was created at /run I suggest you to use previous build (or latest but choose 5.4 from armbian config -> old kernels menu), freeze kernel upgrade and enjoy. I am not sure at this point what we will do with this kernel. If Hardkernel stop maintaining it, we might need to roll back to 5.4.y. I know. We are trying best to take that pain away. Also this way: https://github.com/armbian/os?tab=readme-ov-file#latest-smoke-tests-results but problem is that all this costs a lot of time and we have to cover this from our own pockets almost entirely. Even doing it for everyone, also for our competitors that only wants you (our users) but not our costs of software support.