Igor

Its a feature We decide to leave this utility on development branch (there is separate armbian-config.list in the source folder) for awhile to speed up with the integration. There is a lot of automation that is helping preventing shipping broken app. And the app itself is very simple compared to everything else.

Thank you! I did a quick look. In theory it should be operational, but we would like a clean code and common coding style ... to ease future maintenance. I hope you are O.K. that I give you instructions what to change? For me this represent more work than I just take it from you and change, but it is better if code author do those changes and you adjust PR to what is expected.

You need a video player that supports video acceleration. Mali support works as otherwise you would not be able to run Wayland.

I think those are our common defaults We made maintaining process as simple as possible. Build system takes care of most problems already and there is even automation that prepare images for release, and once those are confirmed in good shape - USB, HDMI, .... https://docs.armbian.com/Process_CI/#prepare-standard-support-images-for-release with report similar as here https://www.armbian.com/tinkerboard/ few times per year ... that's about it. Leave your contacts https://www.armbian.com/maintainer-registry/ so we can try to contact you prior to release. if you don't have time, not a problem, perhaps someone else will cover, all this work can only be at best effort principle. Board is simply taken down from supported if status is unknown. Goal is to provide best images that build system throws out - current or edge kernel. Small jobs always comes around and inner circle is first to know that, so its good to be around, even with this tiny role, small obligations.

No, that is not simple because in the build framework we only know board odroidxu4. We don't keep all their sub-variants under their different config. We have maintenance nightmare without that Many pull requests, ideas and tips that are said on this forum or sent to the code are never integrated as they don't reach completion. This is how this line of work is. Don't worry about. Take this as a fun project and try anyway. If not today, next week, next month.

It was not removed. We developed this tool from scratch and this feature was not added. It's an old board, it doesn't justify adding. We have so small resources and this won't ever passed the triage. Even its just one hour of work. I wrote instructions what to do and if you are close with BASH coding and you want to have this, you are welcome to add this https://docs.armbian.com/User-Guide_Armbian-Software/#adding-example The very moment the code is merged, tool gets this feature inside. Yes, this is the list of overlays that are loaded by default. You change that if you want something else. Yes. I noticed this folder was changed recently, but I don't know at this point if this is something we broke or Hardkernel. The case is that you need to point to where .dtbo files are. They are in /boot/dtb or in /boot/dtb/overlay and at some other boards, they might be under /boot/dtb/SOCVENDOR/overlay ...

Point of community open source development is sharing the load between projects. They choose a policy to steal from open source developers. This wording can be used when they contribute nothing to commons, nothing what they do can anyone reuse. Which is a big steal in custom arm hardware world, where kernel maintenance is everything, not unlike PC world, where distros mainly represent and artistic added value. We have to loose thousands of hours to get a device up, they run a script "and support it". This type of scam only exists in open source world, as nothing is hidden. Just a moral standards or absence of them prevents people to play bad. All our code is open and anyone can do whatever ... and there is little we can do about except informing you what is their MO. And telling you this is not something we would like to do. We would rather code, do fun stuff, cooperate, share our burdens. As sharing burden is must have in community development. The more value we generate, the better OS we make, the more they profit. By telling users how cheap hard work is, they are damaging interests and motivation of all open source developers that contribute to common efforts. Not just to Armbian. They count that you don't understand this perspective, they don't care and you will anyway forget about on day. If you invest little to nothing, little you can loose. If one have no R&D costs, if you don't maintain any infrastructure, ... Sales of somebody else work = tl;dr; diet-pi. On top of that, they were trying to offload their users complains to us. This only tells what is the level of corruption. Again you don't care who deals with the frustration you have ... Let everything hard and time consuming be pinned to the Armbian is their MO. Since ever. How one can accept such sick play? I am sure you don't. For end users its always the same - its free stuff. And you don't care who developed it or who maintains it / keep it operational. Its complicated to understand how Linux support for such a complex world is made. Certainly not as simple as they think and sale. Probably, but that has nothing to do with them. All the work (on top of mainline) is inside those folders: https://github.com/armbian/build/tree/main/patch/kernel/archive

Aha, you mean you miss this: This adds: board_name=hc1 to /boot/armbianEnv.txt and then correct DT is loaded. But also if not, it won't be big difference. You are safe to use defaults. Overlays for this kernel: As I can see, we don't have support for overlay handling at all. Not in old, not in this one. You need to edit /boot/boot.ini and add / replace it in this line: setenv overlays "i2c0 i2c1 hktft-cs-ogst" Also there is a problem here: ext4load mmc 0:1 0x60000000 /boot/dtb/overlays/${overlay}.dtbo In current circumstances, you need to have ext4load mmc 0:1 0x60000000 /boot/dtb/${overlay}.dtbo Edit: since this is the only board that is using boot.ini, we won't be adjusting armbian-config, but I have updated instructions on the download page: https://www.armbian.com/odroid-xu4/ prevent confusion and disable menu as its not supported by the tool https://github.com/armbian/configng/pull/285

Dietpi is group of people (one scripting guy and two support for forums) that download images and resell under different name. There is no build process of Dietpi, there is no development. Its mainly repacking / sales of our & others work for their gain. Dietpi is a group that in 10 years of existence managed to return less then 5 fixes they found (every line is a fix of something. This is just a work into common code for past 3 months). They never contributed in common efforts, they never return anything to people they are taking from, from us and from you. We are not alone, but hey, they compete with us, they say Debian and our work is trash, while they use numbers manipulation (kilobytes of packages on images, processes at start and similar BS) to support selling their scam. Its a shame that such projects are held accountable and being compared. We don't compare with them, but here you can see some insight https://docs.armbian.com/#key-advantages (dietpi is one of armbian downstream projects) If our image doesn't work and theirs works, is certainly a work of randomness. How they made their image? They developed a bash script, that they use to convert / rebrand any Debian based image into Dietpi. In this process it is impossible to improve what is already broken. That is hard work, and they never did any of it. Since kernel updates are directly linked to, a copy of our packages, they are not bringing any changes ... Images are untested, but I am sure it can't be worse then a copycat: https://www.armbian.com/odroidc1/ Thank you. Dietpi did little to nothing. Not here and not with other devices they "support".

Its not a problem of armbian-config but we messed up while packing device tree overlay. We have to fix this and sent out service update. But that will take few weeks. In the mean time copy dtbo files into subfolder: root@odroidxu4:~# mkdir -p /boot/dtb/overlay root@odroidxu4:~# mv /boot/dtb/*.dtbo /boot/dtb/overlay/ Then it will work.

Try from here https://rsync.armbian.com/incoming/efectn/orangepi5/archive/

OMV install touches many things in the system which is beyond our possibility & interest to know. This is probably a question for OMV forums.

By default, with Ubuntu, yes, with Armbian no. We pull snap free version from Mozilla PPA team: https://github.com/armbian/os/blob/main/external/firefox-noble.conf and apply hack - repack with higher version then provided by Ubuntu: https://github.com/armbian/scripts/blob/main/.github/workflows/download-and-test-external.yml#L258-L269 following by pushing to our repositories. This is control file: Package: thunderbird Version: 9:128.5.0+build1-0ubuntu0.24.04.1~mt1armbian1 Architecture: armhf Maintainer: Ubuntu Mozilla Team <ubuntu-mozillateam@lists.ubuntu.com> Installed-Size: 247933 Depends: libasound2t64 (>= 1.0.16), libatk1.0-0t64 (>= 1.12.4), libc6 (>= 2.38), libcairo-gobject2 (>= 1.10.0), libcairo2 (>= 1.10.0), libdbus-1-3 (>= 1.9.14), libfontconfig1 (>= 2.12.6), libfreetype6 (>= 2.3.5), libgcc-s1 (>= 4.3), libgdk-pixbuf-2.0-0 (>= 2.22.0), libglib2.0-0t64 (>= 2.38.0), libgtk-3-0t64 (>= 3.13.7), libharfbuzz0b (>= 0.6.0), libpango-1.0-0 (>= 1.14.0), libpangocairo-1.0-0 (>= 1.14.0), libstdc++6 (>= 12), libx11-6, libx11-xcb1 (>= 2:1.8.7), libxcb-shm0, libxcb1, libxcomposite1 (>= 1:0.4.5), libxcursor1 (>> 1.1.2), libxdamage1 (>= 1:1.1), libxext6, libxfixes3, libxi6, libxrandr2 (>= 2:1.4.0), libxrender1, zlib1g (>= 1:1.1.4) Recommends: myspell-en-us | hunspell-dictionary | myspell-dictionary, libcanberra0, libdbusmenu-glib4, libdbusmenu-gtk3-4 Suggests: thunderbird-gnome-support, ttf-lyx, libotr5 Conflicts: mozilla-thunderbird Breaks: enigmail (<< 2:2.2), jsunit (<< 0.2.2-2ubuntu1), thunderbird-gnome-support (<= 3.0.4+nobinonly-0ubuntu3), tinyjsd (<< 1.2+git1-1ubuntu1) Replaces: mozilla-thunderbird, thunderbird-gnome-support (<= 3.0.4+nobinonly-0ubuntu3) Provides: mail-reader Section: mail Priority: optional Description: Email, RSS and newsgroup client with integrated spam filter Thunderbird is a full-featured email, RSS and newsgroup client that makes emailing safer, faster and easier than ever before. It supports different mail accounts (POP, IMAP, Gmail), has a simple mail account setup wizard, one- click address book, tabbed interface, an integrated learning spam filter, advanced search and indexing capabilities, and offers easy organization of mails with tagging and virtual folders. It also features unrivalled extensibility. and there is no dependency for snapd. I will need to look closely when time permits.

This is fix, just perhaps too noisy. If you don't want to see those messages, change this on your system: https://github.com/armbian/os/commit/36fc679bbb38cdff4223e14a0552c638f577d56b Without you will have your HA always unhealthy. Background: https://github.com/home-assistant/supervisor/issues/4381 This should happen only once after reboot. As we are running a vendor kernel on those devices, there could be issues beyond our control. Once LTS kernel will be available for this HW, we recommend to switch to it. I am running HA, with the exact same method, on Odroid N2 running mainline kernel. Everything works perfectly stable for months.

This package is hosted at our repository, you can delete the list: sudo rm -f /etc/apt/sources.list.d/githubcli.list For the Firefox, I have to check. Our package should be snapd free. Perhaps try to uninstall firefox, remove snapd and install firefox again (should be downloaded from armbian repo).