Igor

Armbian is assembled from Ubuntu or Debian packages. If problems is there, problem is here too and there is little we can do about. https://docs.armbian.com/#what-is-armbian We have a mechanism which you can use to insert patched package to our repository, which is in use in some corner cases: https://github.com/armbian/os/wiki Perhaps this is a solution, perhaps not depending on possible dependency nightmare.

First problem was fixed in predicted way. There is no more firmware warnings on upgrade / kernel install. New package is getting to the stable repository in a couple of hours, while it is already present in beta. Agree. While testing kernel, I installed Ubuntu Noble based image and ERROR: Unsupported initramfs version does not manifest there! I suspect this problem is caused by some script that is coming from RaspberryPi OS - on Debian based Armbian, we use userspace and Rpi related firmware packages from RPi OS (which is Bookworm based, so we have great / full packages compatibility). I will try to get to the bottom of this when possible. Basic problem is that in open source and especially in packages assemblies, there are always (tens of) thousands of potentially irritating issues. You noticed this one, we already have a list of many others that needs attention and there is endless list that well always be somewhere ...

Warnings are safe to ignore, happens on other platforms too, but it looks like also error. CONFIG_USB_RTL8152=y -> m should probably do. I will make a config change: https://github.com/armbian/build/pull/8116 I have noticed the initramfs error too, but it doesn't looks it breaks anything. Need to be investigated.

None of those boards are officially supported, so we are not aware on their hw support status. Those are also 32bit architecture, while we only provide 64bit support for Rpi. Did you use Armbian for Rpi? And which particular build? And on which Rpi? There are many unknown things - big difference. Hard to determine the reason from current informations.

Trixie ... let me check and fix this. I only tested Bookworm.

This is around 10 years old (!) demo / beta image that was deprecated cca. 8-9 years ago. If automated builds doesn't work (we can't cover for endless software support for endless ultra-cheap hardware), IMO your best (only) way is digging into https://docs.armbian.com/Developer-Guide_Build-Preparation/ and fixing reasons which are preventing latest kernel / boot loader to work. It might be trivial, it might be hard. Probably nobody knows without research. This will help you http://debug.armbian.de/

This should be fixed, but there might be an error with firmware package. Fix is uninstalling armbian-bsp*, updating all packages, installing bsp againg.

Struggling with repo management for past few days. It would be nice to write it from scratch, but time is an issue

That is wrong approach as we follow kernel source / standards: and this (boot script) contains the mechanism for loading it: https://github.com/armbian/build/blob/main/config/bootscripts/boot-rk35xx.cmd It should work: https://github.com/armbian/build/blob/main/config/bootscripts/boot-rk35xx.cmd#L51-L52 Is your image an upgrade from some old one? As we indeed have issues with this at some point.

Was fixed already.

We provide mainline based kernels via repository. They are up2date with what exists, but support is not complete and also not tested on this particular hardware.

There is another feature of framework, "armbian-kernel", sections that applies on top of (basic) configs: https://github.com/armbian/build/blob/main/lib/functions/compilation/armbian-kernel.sh#L205-L336 (Docker as example)

Armbian needs user space development too Examples: https://github.com/armbian/configng https://github.com/armbian/apa ... We have to deal with that. There is a lot of automation, infrastructure, ... everything has to be done in order that this machinery works. Ain't just kernel / low level stuff. Not to mention that project also needs (HTML) front-end developers and other profiles. As by the end of the day, that works falls to the people who knows kernel stuff, but if website is broken, kernel fixing has to wait ...

Understand, likewise & most of people that knows this stuff, are very busy. Hardware donation was a thing years ago, today not so much. I can add hw donation (something else) and offer tools: https://forum.armbian.com/crowdfunding/ (example) This can be prepared by anyone and nothing is expected to happen over the night.

Those older devices are patiently waiting for a dedicated enthusiast with plenty of free time and a passion for tinkering. Sadly, the current Armbian maintainers are already stretched to the limit, and expanding our support efforts just isn’t feasible right now. I had a wish, still have, to find and encourage a dedicated person to take a lead on maintaining those old devices (retro Armbian section) as we have to move them out of primary focus in order to survive. Reaching mainline is not enough. Most of our work is dealing with problems that are originating from there. Mainline is just common work, but its often in not very good state. And when problems are found, it takes months before they are fixed. And someday they are not fixed anymore as critical mass of developers, interested in this devices, is just too small or too inexperienced.