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! 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.

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.

New images were generated and u-boot package build with force u-boot update enabled, then shipped to repository. Testing was not performed as I don't have equipment nor time. Check Gold subscription and become a partner in covering some of the costs we had because you are using this hardware. If you would already did that, we would have a lot less situations as this one.

Do the same for max: https://github.com/armbian/os/commit/45e7773d8fa023f3c5fb3c9c1402bf3616c59031 and wait for next automated rebuild cycle of community maintained images. Then download pre-configured Gnome desktop image and forget about any other browser then preinstalled one. Also forget general understanding about desktop Linux on PC ... this is embedded Linux / custom hardware world, where things are "a bit" different. Developing and keeping functional desktop image was already on the level of miracle considering that we are operating with big negative budget and absolute absence of any support from HW dealer that makes big sales ... which are crushing ability of making things better. For you and for us. Or dive into https://docs.armbian.com/Developer-Guide_Overview/

Strange. Trying to understand, because we don't do anything unusual. Defaults are plain straightforward: https://docs.armbian.com/User-Guide_Networking/#armbian-defaults and should work. They work "at my network" Perhaps this has something to do with:

Interesting, do you have explanation?

Ubuntu image has Network Manager backend. Perhaps that is the reason?

This can be skipped, unless Debian Bookworm and Ubuntu Noble XFCE is not enough. We provide fresh, weekly automated builds at download pages https://www.armbian.com/orange-pi-plus-2/ but dunno if images works.

This is a reminder that for production quality someone needs to constantly invest time. We build community images for amateur usage and to match other projects support levels. We also keep archives of almost all older builds: https://archive.armbian.com/orangepi2/archive which could serve as a cheap workaround. We do that for many boards, but there are simply too many of them. Producing them is dirt cheap ... maintaining extremely expensive. There is also lack of cooperation from 3rd party projects and vendor in question. Support goes in reverse order, they actually harm us all the time, consume our work, contribute nothing. Orangepi also only invests in sales and does not support open source developers / projects. For our group I can tell you 1st hand, but I have solid information that others are also unlucky. We are happy to help. https://www.armbian.com/contact/ -> Quick start Not sure what is current support status. It could be very broken with weeks to invest or not so much. Last time I had those boards (2e to be precise) in the automating testing, they were not very stable. Reboot sometimes didn't bring them back, crashing on load ...

Also we fixed TUI / GUI way of setting UARTS, merged today: https://github.com/armbian/configng/issues/360 https://github.com/armbian/configng/issues/344 fixed with https://github.com/armbian/configng/pull/393

That is sadly far from reality. I can name two copycat projects that are getting from us everything and in 10 years they together made <5 fixes to common problem (less then 1 vs. 1000). Open source is a very dirty place for people that contribute. What is being worked together is within our team and few external projects that have healthy and fair attitude. Those conditions has to be met: https://docs.armbian.com/User-Guide_Board-Support-Rules/#standard-support If everything is met, which is already a miracle, there is a "must be beneficial to the Armbian project". This term helps us fighting hardware vendors abuses - this vendor owe us substantiation amount for contracted services. We can't allow to fool us at any condition. Which are in general often damaging for open source, our and similar projects. But you usually can't understand from consumer perspective, if you don't look ... why would you? You just want that everything works. Finding serious and dedicated maintainers for vendors that have abuse in the name is just impossible. I can see you are a good guy, but x % of our "customers" are total morons, few percent are total abusers and are making everything to profit from our work, contributing nothing. And by the end of the day, most people see us as guilty because shit hardware doesn't work perfectly ... as everyone (or most of people) expects. Orangepi won't add "Sponsored by Armbian" or "we are stealing software support from Armbian / open source community" to their web page, so this is the only way to tell you Don't buy from them anymore any we will be friends. They are damaging to us. And to you. Donations never went over 0.5% of costs. I am in this for 10 years. Being super polite and friendly or being an ass. Makes no difference. It is devastating for open source developers. We need to bring 99.5% to satisfy you.

Yesterday bugfix release of rockchip64-current should address this problem. In stable channel, beta is anyway having latest.