Igor

FYI. Fundamental problem is that users expectations are not matching resources open source developers have to sponsor you. You are not our customer. You are a customer from someone else, a company that are also using software from us, for free. Their official images are Armbian based and they never give us a cent for that. They also removed all our names from it and returned minimal (c) and "based on" after we applied substantial pressure. Dietpi is a pirated copy pasted project. All problems we have, are copied too, nothing gets our way. Code is free, so this is hard to understand stealing, support and credits are not. They are stealing credits as they forget to tell you that "all their work and support" is originating from Armbian. They don't support anything. They fully rely on our support and they do everything to minimize value we product and glorify their (non existing) part. They even produce (fake) news on their (non existing) software development. This piracy would be smaller problem if they would at least contribute to common problems. But they don't do that. In past 10 years, you won't find much, less then 5 trivial code commits! Its amazing, but customers of free of course don't care. Free stuff from Armbian or free stuff from its copy, its the same. There are several projects that are working with us, we work with them, share problems and we are all happy. Dietpi (and also Orangepi) works against us and against you (on a long run, so you don't see it). For different reasons. We still actively maintain software you use, even you also ignore us totally. Nobody cover all hardware features on all boars. This is impossible. Word "support" is generally and largely abused. There is little we can do about / and over-expectations. We had to invest substantial amount of efforts to develop rules under which term "support" is abused less. https://docs.armbian.com/User-Guide_Board-Support-Rules/ Remember that not just all R&D but also all support costs, dealing with costumers, remain open source project financial expense. And our income are donations, which most people don't even notice. And you are telling us that we should do it better? Hardware support is hard work, not an art / cosmetic / philosophical value that is present on 90% of Linux distributions Orangepi want that software stays the same and they just want to sell you new products. So they are doing new models (illusion of progress and improvements) and each has something to tackle, bring support costs (which they don't have). Support is never improved by them. Its by us, never by Dietpi. For every 1000 contributions to common problems, they make perhaps one ... Its that bad and that obvious, but still, ordinary Joe don't see as anything wrong. Competition is healthy - yes, software doesn't need to be better, just you need be believe it is "supported". Nobody claimed anything. Our support is "best effort". Support how we see it is different how you see it and we can't change that. Armbian is not a commercial product - we work for fun. If its no fun ... "there are sources, DIY, stop complaining". End users donations only cover us 0.5% of time we lost instead of everyone, including supporting dirty players that doesn't help in resolving common problems and certainly doesn't make any donations. Donations have important motivation role. There is little developers / sponsors of software you use can do. Except placing a donate button, asking to support this. We are not doing this for money, we don't need better software and support. You do.

Hey! When those three jobs finishes: https://github.com/armbian/os/actions/runs/13238582459 https://github.com/armbian/os/actions/runs/13240767648 https://github.com/armbian/armbian.github.io/actions/workflows/generate-redirector-config.yml it should be O.K. Fundamental problem is that at this moment, repo and index is not in sync. Why that happened ... is another story, it should not happen. First job checks and updates if there is something to pull to stable repository. It pushes to 1st class repo Second job is optional in this case. Third job checks all mirrors and only serve the ones where index and files are in sync. Problem is that those jobs takes hours ... and in the mean time, repo is broken.

Yes, this is temporally problem that shows up here and there or you simply forget to run apt update before? We are having difficulties with maintaining our infrastructure (not enough people and other resources) which needs several improvements ...

Here are variants how you can support our project Board support rules: https://docs.armbian.com/User-Guide_Board-Support-Rules/ (I think you will be able to get an answer by reading this)

There is /boot/boot.ini Change this there and try.

If you happen to figure out which firmware files we need, we can copy them to smaller firmware package that is installed by default: https://github.com/armbian/firmware (pull request is welcome)

6.6. contains it, but we are moving all kernels to 6.12.y, where this seems broken - major kernel upgrades always kills some functionality, which is why our work is hard, stressful and expensive. I have tested booting this device on kernel 6.12.y, but not USB as that would make testing just a lot more expensive. Burning most of project donations, which is all we have, for a device we don't even support, just to fix this problem is destructive for project. Morally and financially. Support rules: https://docs.armbian.com/User-Guide_Board-Support-Rules/#community-maintained This is a problem of this particular device. All I can afford to do is reverting this upgrade and we forget about kernel 6.12 on this device.

What is the right Ramdisk format?

Thanks @Josua-SR! I tried with self made and this binary - we have some troubles with kernel I guess. => boot switch to partitions #0, OK mmc0 is current device Scanning mmc 0:1... Found U-Boot script /boot/boot.scr 2996 bytes read in 15 ms (194.3 KiB/s) ## Executing script at 03000000 Boot script loaded from mmc 158 bytes read in 12 ms (12.7 KiB/s) 28834 bytes read in 27 ms (1 MiB/s) 11476654 bytes read in 1086 ms (10.1 MiB/s) 8546328 bytes read in 843 ms (9.7 MiB/s) Working FDT set to 2040000 Kernel image @ 0x2080000 [ 0x000000 - 0x826818 ] Wrong Ramdisk Image Format Ramdisk image is corrupt or invalid SCRIPT FAILED: continuing... Loading Boot0000 'mmc 0' failed EFI boot manager: Cannot load any image

Yes. This file fall into incoming by mistake, two weeks too soon. Since its harmless, it will stay.

I set most used combination as we have to set some limits. Currently we are at 500 weekly images, which is already a rape for (limited) CI infrastructure After we manage to move desktops to runtime (https://github.com/armbian/configng), we will be able to remove many desktop images and provide more CLI combinations. Exactly, I think its not worth going manual exceptions way. HAS_VIDEO_OUTPUT should suffice. Server builds is heavier and comes with Network Manager, while minimal comes with systemd-networkd and less tooling. Debian based or Ubuntu, depends on what is your use case further. A very few native application suites won't work on one, while it will work on another. The rest are IHMO personal preferences and stereotypes. Ubuntu server is cleaned from Canonical things and its pretty much Debianized. Exceptions can be covered that way. This build target is common for many different TV boxes, so I assume the user-base is also bigger, so is the need I guess.

Please check updated documentation: https://github.com/armbian/documentation/pull/620 if this answers your questions clearly enough. Rendered: https://github.armbian.com/documentation/620/Process_CI/

Also try this way: https://docs.armbian.com/User-Guide_Armbian-Config/Network/#wireguard-vpn-client-server Its easier.

Added the same technology to daily rolling images - torrent download is FAST!

We were all beginners once. Welcome to Armbian forums! TV boxes has its own section. One more step is missing https://chatgpt.com/share/67a62db5-7664-8005-8104-96c849031513

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! apt update & upgrade will update armbian-config where this works as expected. Until next bug found ...

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/