Igor

"The worst-case scenario is that you give the maintainers an opportunity to reconsider if continuing to work on the open source project is worth it." https://minimaxir.com/2023/11/open-source-dead-github/

Tells absolutely nothing. This does. BTW. Welcome to Armbian community / support.

Check if this helps here too

You mean generally? On all config files https://github.com/armbian/build/tree/main/config/kernel CONFIG_DRM_BOCHS=m CONFIG_DRM_CIRRUS_QEMU=m CONFIG_DRM_GM12U320=m -CONFIG_DRM_SIMPLEDRM=m +# CONFIG_DRM_SIMPLEDRM is not set CONFIG_TINYDRM_HX8357D=m CONFIG_TINYDRM_ILI9225=m CONFIG_TINYDRM_ILI9341=m BTW. If we want to block module per board: https://github.com/armbian/build/blob/main/config/boards/rk3318-box.tvb#L8 This automatically creates blacklist file ...

Changing to Ukrainian mirror manually https://github.com/armbian/mirror /etc/apt/sources.list.d/armbian.list https://fastmirror.pp.ua/armbian/

Use Gnome. I think it doesn't work with Cinnamon.

We refactored updating procedures, repository management, download infrastructure. This mainly impacted to the beta repository, but we (can) also copy certain packages from external / 3rd party repositories. To keep specific package more recent than distribution defaults. This is pushed to both, stable and beta repository, after executed automated test install on affected distributions. https://github.com/armbian/os/wiki/Import-3rd-party-packages tl;dr; apt update and apt upgrade remains in action, but we talked about updating packages directly from a storage we are using for caching (ORAS, currently hosted at GitHub). For now this is just an idea as GH is not the best hosting place speed / capacity wise. This text was perhaps improved too much as it only creates confusion. Applogize.

Winning a lottery at request? Expecting the impossible? ... Point of forums is asynchronous (days - months) communication and due to the extreme complexity this project is dealing with, such expectation is, sorry to say it, just crazy. Even in most popular / trivial areas. Capacity is limited. Most of people here are seeking for help while debugging and answering to that help require a lot of time, often extreme efforts (in exchange for sorrow, frustration, humiliation, aggression) on the other end. You have a problem, you shared it. That is what this forum is. Then perhaps just wait? Sometimes answer comes next day, sometimes next month, sometimes never. And this is since ever and there is little I can do. If this project would be making millions, I would hire people to support you like Raspberry Pi foundation does ... and still we are looking at much bigger complexity, so having their capacity would not be enough. Developers, those who can understand and look beyond the problem, are not always available. Just here and there. Personally, I am on a road trip and even when I will be back to the office, I am over the top with problems not just for days, but for months. Even I would be very much like to help you, I can't possibly do that in 24h. On the project level, there is no way to secure responsibility that is generally expected. Even we would be properly financed. I hope you understand my pain and frustration as there is not much we can do to improve this forum response rate. Contrary. The more (complex) stuff that will land on the market, hardest will be to respond. Producing new and new hardware is cheap. I can give you proof that its alive, but can't answer to the question, provide solution. I have no idea what is behind the problem, so there is not even a hint I could give you. Except, try older images, record bug to Jira, so those few people that maintains this place, will try to (!) fix this withing upcoming release. Patience & have a nice day. Apologize if being harsh.

We are interested for features expansions and improvements. Always Especially if that helps more people. But as we are small and overloaded ... we can only assist best effort way with hints, reviewing the code, ... Those are possibly related tickets that also waits for attention: https://armbian.atlassian.net/browse/AR-1592 https://armbian.atlassian.net/browse/AR-1881 https://armbian.atlassian.net/browse/AR-1900 and might be addressed on the way. We had a wish / dream to refactor this script, but its in fact quite a complex problem due to many different boot scenarios, exceptions, links with build framework. On top of general Linux filesystems complexity such as this.

We provide you: - build-able sources, - build engine, - ready to run images, - we try to help as much as possible, - we provide you meeting point, this community. It is unfair to pin this problem to Armbian. What you are asking doesn't work on any mainline (or Armbian) based Linux kernel and if something stop working is due lack of maintenance. We do that up to our limits, slightly over. If you want to use those displays and enjoy best hardware support, you will most likely need to use private Rockchip kernel. Where this comes by default. Please make no anger on Armbian maintainers as we are not responsible for your frustration. We are equally frustrated as there is nothing we can do to take your pain away.

It works, just you need to prepare partition in advance.

https://docs.armbian.com/User-Guide_FAQ/ We can probably develop this for you if you become our partner, if you cover expenses of this development for you, but this is not something that is missing in Armbian. tl;dr; If you need this feature, use stock kernel, or finance development. This is open source world. Nobody prevents you to add features you need.

Forum is sadly just a black hole There are way more problems that integrating resources https://docs.armbian.com/Process_Contribute/

BTW. @samond This could be very much like a Debian upstream problem ... Last week I installed Armbian Ubuntu Jammy x86 build to one of new servers and one of the things I did was changing SSH port. Works as expected.

Thank you! Will be added during a day. Dunno how we missed that, but sometimes things get lost. Appologize!

Its where Armbian community builds are made. Which are anyway not officially supported ... Armbian project maintainers does not answer any support questions regarding those builds! Support? Check general install instructions or TV box specific

You are not using original Armbian build. This way you can check if its original build: https://docs.armbian.com/User-Guide_Getting-Started/#how-to-check-download-authenticity And here you can show minimal respect to open source software you are using (even you use some random armbian fork). It will help authors paying utility bills when spending time answering your questions and you to get attention in first place. Bugs are collected this way: https://www.armbian.com/bugs If its a build framework issue, open a ticket here.

I am sure process works correctly on Armbian x86_64 https://www.armbian.com/uefi-x86/ You failed to see all those warnings? - rolling images are not supported - edge image are not supported - CI builds are not supported - development kernels are not supported Why? https://docs.armbian.com/User-Guide_FAQ/ If you find a problem, invest your own time, fix it and and sent a fix to us or upstream to kernel.org

Try Armbian OS on Raspberry Pi. Function will work. The problem is this: https://docs.armbian.com/User-Guide_FAQ/#why-does-hardware-feature-xy-work-in-old-kernel-but-not-in-more-recent-one Better hardware functionality of factory Radxa software is paid this way:

FYI. Not Armbian problem. https://github.com/radxa/kernel/issues/54