Igor

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/

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.