Igor

Mission: provide easy way to configure OS and install services armbian-config provides configuration and installation routines for customizing and automating tasks within Armbian Linux environment. These utilities help streamline setup processes for various use cases. Key Advantages Lightweight: Minimal dependencies for optimal performance. Flexible: Supports JSON, TUI, CLI, and API interfaces. Modern: A fresh approach to configuration. Low entropy: Byte clean uninstall for most targets. Features System Configuration: Kernel management, headers, hardware tweaks. NFS and ZFS storage management. SSH user access tweaks. System updates, rolling / stable, containers update. Network Management: Fixed / dynamic IP configuration. Connecting to wireless network. Access point management. Localization Settings: Configure time zone. Set language and locales. Change hostname. Software Management: Software installation and removal. Native and containerized environment. Standardised, updatable, maintained. Compatibility This tool is tailored to works best with Armbian Linux but it has also been automatically tested on: Debian Bookworm Ubuntu Jammy Ubuntu Noble In theory it should work on all systemd APT based Linux distributions: Linux Mint, Elementary OS, Kali Linux, MX Linux, Parrot OS, Proxmox, Raspberry Pi OS, ... Getting Started Armbian config is preinstalled on Armbian. Open or login into your terminal and run: armbian-config End users: Request new software title Documentation: Armbian config | Optimised software Developers: Adding a new feature or software install title

The problem you are experiencing is probably related to some incompatibility when assembling 32bit OMV. We can't test all assemblies manually (we have no other option) on all targets. Perhaps moving installer to run-time is better? https://docs.armbian.com/User-Guide_Armbian-Software/#adding-example We will eventually add this, but help is appreciated.

I am slowly working on a script, but currently doesn't provide expected results: https://github.com/armbian/configng/blob/main/tools/modules/system/release_upgrade.sh Also it will remain as experimental as this goes into upstream bugs which are beyond our control or resources to fix after thousands of people that are behind all those packages. Where single one can cause this upgrade to break ...

Also documentation (related to this topic) is now in right state of mind: https://docs.armbian.com/User-Guide_Armbian-Software/#adding-example It is hard to add software title we never tried, installed and / or know nothing about, then expert user of this software adding it to (armbian-config) installer. We focused to make this task as simple as possible, to encourage you doing that and not opening us tasks (we already have 1000 x too many and won't ever complete). We added popular titles to the system, which have some value for us, while everything else is mocked by more important tasks in other sections. But mechanism is there - use it, its user / developer friendly. Also its a nice and easy way to contribute to the open source.

Perfect example to explain how anyone can fix such trivial problems without involving me. Which is essential for the project to survive. There are and always will be way too many problems for too little maintainers ... Bug is here, yes, and can be easily fixed, especially if you already have a solution. I am happier to provide guidance then doing this on my own (which takes a lot less efforts). Solution is adding a package here: https://github.com/armbian/build/blob/main/config/desktop/jammy/environments/gnome/config_base/packages (jammy has same packages as noble and is symlinked). Every contribution counts, even this banal. We have different Chromium versions, patched for this and that, then with and without snap ... It is a surprise that we can provide a desktop where accelerated video playback works on Rockchip RK35xx platform, which we support better then Rpi. Where all this probably just works if you download any Chromium?

If this was not mentioned in a release log https://docs.armbian.com/Release_Changelog/ and since you already asked, there is no need and you should not ask again. https://forum.armbian.com/store/category/2-support/ and I will try to hire someone for you or fix on your own. This is your problem, not ours. Buy some other hardware. it is cheaper then fixing this. I hate being an ass-hole, but If we don't stand for ourselves, nobody will, certainly not constantly unhappy and desperate free-software-riders users. Remember this rule once and forever: applying a pressure to open source developers is worse thing you can do here. There are thousands of other problems when we can only address one. And you cover 0.5% for that one: https://github.com/sponsors/armbian Do the math. There is build framework https://github.com/armbian/build download it, dig into the code and fix it. Then open a pull requests. As you can see, we are physically, emotionally and financially unable to support your (endless) greed for software perfection. Don't take this personally as its not. Most of people on cheap hardware, that fully relies on exploiting open source developers, acts similar. We develop and maintain open source software for fun and we chose what that is! With little time that is available. Average resolution time for bugs in open source software is 5-7 years and there is nothing we can do. If you scream, complain or emotionally blackmail us. Closing. @Werner Feel free to re-open, once this kernel will be supported, probably Q1 - Q2 / 2025. Only confirmation that "it works" is expected to be added here, we don't need yet another "still doesn't work" ... ever.

If you would like to use 2 years old kernel with not a single fix applied after initial release, use version of Armbian from Orangepi site. This question was answered on Orangepi download pages. For everyone. To spare answering same questions over and over again. Which is devastating for mental health and expensive when we pay everything and you nothing. Only when you like - donation.

I change the text to: "we will be able to proceed once your donations for entire project reaches at least 1000 USD per month. " Even this miracle happens, we will still be making a huge loss, supporting mainly subjects that compete with us with our money (Orangepi is one of them, stealing value from us in order to sell you cheap hardware). That far away we are. I am sure GitHub supports all kinds of payment methods and random donations method supports that too. If you ask us to repair something, donation doesn't works. That is a professional service, which are paid at standard rates - this is for vendors that doesn't contribute in any way. Fixing resources are expensive and scarce. This is open source - shitty operation are not Armbian problem, but Orangepi, yours.

This is the only "fix" we can finance from your donations: "PCI support is broken on vendor kernel (6.1.xx) on versions higher then 24.8.1. Use this version and freeze kernel (armbian-config -> system) prior to updating OS. PCI works on other Rockchip 3588 devices, while fixing this on all represent expensive technical challenge which we can't finance. With Orangepi devices we have extremely high negative support budget while your yearly donations are not on the level to compensate this loss. Alternative operating systems that relies on our work face the same problem. We appreciate for your understanding." https://www.armbian.com/orangepi-5/ So does previous Armbian image. Use provided instructions or only buy (probably a bit more expensive) from vendors that supports open source developers.

Can you provide screenshot and some logs (armbianmonitor -u)

Usually catching last week. If you have followed instructions on download site, https://www.armbian.com/odroid-m1/, then you have u-boot. Which is fine.

Switch to nightly build and try. Or just wait few weeks for 2024.11 update. Are you perhaps booting with petitboot? We fixed this some time ago: https://github.com/armbian/build/pull/7245

Probably what you are asking works, best to just try image on something, perhaps VM. I only use one (1) official add-on, which is Z-wave ..

Probably related to NVME and those two commits: https://github.com/armbian/linux-rockchip/commit/16a7adc42e350ee3ff96298f295ae01f52f103bb https://github.com/armbian/linux-rockchip/commit/a095b986015598f2aa1ef1e424f766a8bb65f4a3 This fixes SATA bridge on Rock 5 ITX but possibly breaks NVME on Orange 5. As we will not maintain another special kernel for a single device, Orangepi 5, we have implemented a mechanism to prevent upgrades beyond 24.8.1 https://github.com/armbian/build/blob/main/config/boards/orangepi5.conf#L17 which might not be working properly - It should block upgrades to this kernel ...

Welcome to try with integration to https://github.com/armbian/configng We didn't set rules how to include tools from external repo yet, so this is a bit wild ... - there are unit tests in place for each command - automatic documentation generation is WIP

Will log you out automatically, at least when running desktop. In case one is running Google Chrome, this will lock it out This 10 years bug is still valid: https://askubuntu.com/questions/476918/google-chrome-wont-start-after-changing-hostname BTW. We are switching to armbian-config new generation soon and here this is done this way: https://github.com/armbian/configng/blob/main/lib/armbian-configng/config.ng.system.sh#L33-L38 If you have ideas for improvements, welcome.

That would be network / mirror sync issue. Try by adding this switch: SKIP_ARMBIAN_REPO=yes

I wish this would be that simple First, all distros are (usually) re-building packages at different time, thus by default bringing different code base. That change can be small (using same main version of kernel) or big (6.1 vs. 6.10 for example). Then. Armbian adds (ATM) 436 general patches to the kernel and we add several 3rd party drivers to the kernel. We actively maintain this kernel, unlike others. Some distributions are using our kernel, while OpenWRT AFAIK not. Which means they use some version of mainline Linux kernel with their own patches. Their focus is networking (protocols), so I would assume they are fixing those things. I doubt they are doing anything related to this hardware (wifi chip) besides adding device tree (if not yet in mainline). Fixing wireless drivers in its core is done by very few people that are not tied to any distribution in particular https://github.com/morrownr/USB-WiFi https://github.com/kimocoder ... experience will be different, especially in area of this particular hardware.

Its usually hardware / quality of the driver ... but ofc also "something in between". Armbian config way has been significantly improved, worth trying upcoming app: https://github.com/armbian/configng

We keep several oldies in the automated testing facility and Cubietruck is almost identical to Bananapi M1 and it works perfectly well: https://github.com/armbian/os?tab=readme-ov-file#cubietruck I would put my bet on wrong / not sufficient powering. Which is still there and those (old) topics are still valid. Old boards are fine! I have several boxes of them and might sent them to a museum one day We are just too small team / project to face with several hundred different devices. Old boards should, in theory, works well, but silent (as nobody monitor / maintain them) regressions comes to the code. I hope someday dedicated retro hardware section emerges on Armbian forums and further prolong life of those devices. We did / do what we can ...

I assume standard 1080p monitor? Can you grep logs for errors? Will try to reproduce when I find time. @TonyMac32 When was last time you hooked a monitor to Lepotate or similar device?

Here you can find few old builds: https://github.com/armbian/community/releases Main archive is reserved for (once) supported targets on our infra and we are already at current full capacity and (very) old archives are held only on big storage servers.