Igor

This https://github.com/armbian/configng/pull/424/files should fix it. Update will be avail in couple of minutes after the merge. Thank you!

This is the mechanism: https://github.com/armbian/configng/blob/main/tools/modules/system/module_armbian_firmware.sh#L106-L107 In case anyone can spot the bug. Digging into ... Trying to reproduce - fail: Recreated ! Nightly to stable, fine, going back to nightly it fails - it just removes packages, while not installing new due to repo troubles. Start-Date: 2025-02-07 07:14:22 Commandline: apt-get -o APT::Status-Fd=4 -o APT::Keep-Fds::=5 -o APT::Keep-Fds::=6 -y autopurge linux-image* Purge: linux-image-current-sunxi64:arm64 (24.11.1) End-Date: 2025-02-07 07:14:24 Start-Date: 2025-02-07 07:14:45 Commandline: apt-get -o APT::Status-Fd=4 -o APT::Keep-Fds::=5 -o APT::Keep-Fds::=6 -y autopurge linux-dtb* Purge: linux-dtb-current-sunxi64:arm64 (24.11.1) End-Date: 2025-02-07 07:14:46 Start-Date: 2025-02-07 07:15:07 Commandline: apt-get -o APT::Status-Fd=4 -o APT::Keep-Fds::=5 -o APT::Keep-Fds::=6 -y autopurge armbian-firmware* Purge: armbian-firmware:arm64 (24.11.3) End-Date: 2025-02-07 07:15:08

Have you got chance to try new variant? This part was completely rewritten (works for me), but bugs are possible. And room for improvements too.

Compatible field is reserved for almost identical boards or when image supports more devices, like Raspberry Pi 3 and 4. Base image is for Rpi4 but Rpi3 is also compatible. Other two fields are deprecated as content is generated automatically. For customization of build targets, check this https://github.com/armbian/os/wiki

You are running wrong image. "Orange Pi 3B is powered by Rockchip RK3566" while you are trying to use something for 3588. This can't work not even by force of luck. You also need to provide logs if anyone from community can help you.

Not sure if I understand you right, but perhaps here: https://github.com/armbian/build/blob/main/packages/bsp/common/usr/lib/armbian/armbian-firstrun

DNS ad blocker section: https://docs.armbian.com/User-Guide_Armbian-Software/DNS/ containerized with official images tested with networkd and Network Manager tested on arm64

For every software target: https://docs.armbian.com/User-Guide_Armbian-Software/ And every config option: https://docs.armbian.com/User-Guide_Armbian-Software/ Open ticket https://github.com/armbian/configng/issues and improving documentation on the way. Some is in the config itself https://github.com/armbian/configng/tree/main/tools/include most at https://github.com/armbian/documentation With TV boxes you need luck, its hackers, trial and error world, as there is no docs, very little, usually no people behind each design.

Impossible to answer as there are thousands of different devices which single goal is to "sell them, forget about, sell another ...". This project lack millions to be able to have people to support such exotics, so you need to invest your own time into research. Use information about similar devices that exists on this forum and elsewhere. We will try to improve response ratio this way, but on more mainstream targets first - to assemble the team that will search for answers instead of you. No other way - too many devices out there. Make a donation and comment, what those people should do. Or apply for position. Everything you need to know is written here: https://forum.armbian.com/forum/189-faq/ Without this (and similar) projects contributions, this device would be in the trash bin long time ago. Or running horrible outdated original never updated software ...

Could be. Try this one: https://imola.armbian.com/beta/pool/main/l/linux-u-boot-rockpi-s-current/

Fix was integrated https://github.com/armbian/build/commit/cafe0ff79fb69320e6c94719bef5679ec85c5ac5 and pushed to the repo that day. It should work, try with switching to beta repository just to make sure. Perhaps mechanism for updating is borked somehow? Sadly we don't have time / resources to test every contribution manually.

I spent whole weekend to improve this part of infrastructure. It dramatically improve download speed, but its hungry for resources / storage / BW so I don't know if we can afford to keep it. Result: https://dl.armbian.com/rpi5b/Noble_current_gnome.torrent All current nighly / community builds download will probably max out your download connection when using Torrent client.

This should be labelled as "untested", but its also covered by our work largerly. Keeping general stability on Allwinner SoC stack (and on boards developers use for doing this) costs just our project hundreds of engineering hours. At some release more, at some less, four times per year. Excluding all other work that needs to be done, maintaining automation, project management, ... Put "software support sponsored by Armbian team" on your product or support developers that does the work instead of you. Software perfection is what everyone wants, including us. But the problem is that everyone looks the other way, when we start talking about costs trying to get there.

https://gitee.com/bianbu-linux#introduction This is a BSP (board support package) which usually consist from: - kernel - boot loader - libraries for this and that functionality - fw flashing tools - userspace hacks - some tech documentation ... In embedded world, OS is usually custom to cover certain case. One have to build OS (with for big team tools = buildroot / yocto, while Armbian provide more human approach to make and to use. We are assembling all those elements (instead / for you) + OS generation which is distributed similar to other Linux distros. I agree we don't have good mechanisms for generating normal Debian packages. However, board userspace hacks can be put to our board support Debian package. Example: https://github.com/armbian/build/blob/main/config/boards/gateway-gz80x.conf#L15-L19

When you will add this with a PR here: https://github.com/armbian/build/blob/main/packages/bsp/common/usr/lib/armbian/armbian-firstlogin#L601 and group before that.