Igor

Copy that, @Igor. Just learning my way around here.
 
Hopefully my donation will help a little!
 
I appreciate you and your team. Armbian is a great gift to the SBC community.

Key is not deprecated, method is. On Noble / Sid and future.
 
sudo wget https://apt.armbian.com/armbian.key -O key sudo gpg --dearmor < key | sudo tee /usr/share/keyrings/armbian.gpg > /dev/null sudo chmod go+r /usr/share/keyrings/armbian.gpg sudo echo "deb [arch=$(dpkg --print-architecture) signed-by=/usr/share/keyrings/armbian.gpg] http://apt.armbian.com $(lsb_release -cs) main $(lsb_release -cs)-utils $(lsb_release -cs)-desktop" | sudo tee /etc/apt/sources.list.d/armbian.list apt update  

Key is not deprecated, method is. On Noble / Sid and future.
 
sudo wget https://apt.armbian.com/armbian.key -O key sudo gpg --dearmor < key | sudo tee /usr/share/keyrings/armbian.gpg > /dev/null sudo chmod go+r /usr/share/keyrings/armbian.gpg sudo echo "deb [arch=$(dpkg --print-architecture) signed-by=/usr/share/keyrings/armbian.gpg] http://apt.armbian.com $(lsb_release -cs) main $(lsb_release -cs)-utils $(lsb_release -cs)-desktop" | sudo tee /etc/apt/sources.list.d/armbian.list apt update  

Tutorial has been updated to include support for GPT-partitioned images

You already have best possible desktop on this hardware. Simple and fast XFCE. Changing desktop environment won't make any vivid difference. 
https://docs.armbian.com/#key-advantages
 
XUbuntu is more or less identical to Armbian Ubuntu with XFCE subtracted for some Canonical proprietary stuff.

LXDE vs. XFCE ... not worth the troubles maintaining yet another desktop. Difference is too small. We only keep XFCE, Gnome, Cinnamon and KDE Neon in good shape. The rest waits for enthusiast https://github.com/armbian/build/tree/main/config/desktop and you can always start with a minimal CLI image and build on top any desktop you want.

You already have best possible desktop on this hardware. Simple and fast XFCE. Changing desktop environment won't make any vivid difference. 
https://docs.armbian.com/#key-advantages
 
XUbuntu is more or less identical to Armbian Ubuntu with XFCE subtracted for some Canonical proprietary stuff.

LXDE vs. XFCE ... not worth the troubles maintaining yet another desktop. Difference is too small. We only keep XFCE, Gnome, Cinnamon and KDE Neon in good shape. The rest waits for enthusiast https://github.com/armbian/build/tree/main/config/desktop and you can always start with a minimal CLI image and build on top any desktop you want.

Try to rework the script:
https://github.com/armbian/build/blob/main/packages/bsp/nanopim4/nanopim4-pwm-fan.sh#L316
Perhaps expand it to support selecting CPU / hard drive ?

Key is not deprecated, method is. On Noble / Sid and future.
 
sudo wget https://apt.armbian.com/armbian.key -O key sudo gpg --dearmor < key | sudo tee /usr/share/keyrings/armbian.gpg > /dev/null sudo chmod go+r /usr/share/keyrings/armbian.gpg sudo echo "deb [arch=$(dpkg --print-architecture) signed-by=/usr/share/keyrings/armbian.gpg] http://apt.armbian.com $(lsb_release -cs) main $(lsb_release -cs)-utils $(lsb_release -cs)-desktop" | sudo tee /etc/apt/sources.list.d/armbian.list apt update  

It should not be a problem. I already align my patches with armbian/main so this board is ready for 6.6 and 6.12. And testing images for major kernel bumps should not be a problem neither.
 
OK, I will try to do this.

The problem behind their promotion statement is that its a scam. Dietpi is bloated with proprietary scripts and they are removing packages that are dependencies for everything ... so it makes no sense at the end, just first installation of anything takes longer. But they can claim images has few MB less ... which is "better" and most of end users have no ability / interest to understand they have been conned.
https://docs.armbian.com/#comparison
Damages they create to open source, by playing dirty, that is beyond commenting.
 
 
This should also work OOB then
https://www.armbian.com/uefi-riscv64/
and you don't need to remove anything (from minimal Bookworm OS image, which is significantly lighter then Dietpi).
 
If you / anyone can confirm they are working well, we can move this to Supported section.

I just created a pull request for this. Apologies if I got the request wrong, it's been a long time since I created a PR on anything.

This was moved under a switch to prevent users for switching into kernels that are not meant for end-users.
https://github.com/armbian/build/blob/main/config/boards/rock-5b.conf#L7
 
And this
https://github.com/armbian/configng/blob/main/tools/modules/system/switch_kernels.sh
is the logic for anyone that might to change / improve this.

Hi,
 
I am trying to update the patch for kernels 6.10 and 6.11 (same code).
My first try was not successful (compile error), I will try again, I think I've understood what the patch will do, but there are a lot off differences between kernel versions 6.6 and 6.10, maybe some new lines need to be patched too.

Once it compiles and runs fine on my helios 4, I will provide the patch 😉
 
Kind regards,
Xavier.

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.

We are cleaning those builds as they have very little value. But you were lucky:
https://github.com/armbian/community/releases/tag/24.11.0-trunk.351

When you cloned our repo, you got 10 years of specific work on common work and that was contributed by 500+ people. Most of people are resolving their specific problems, yes, but we all try to do it the way that is reusable, that person behind has less work. We also got a lot of things prepared. Doing things universal should always be considered. Also because you might get help from someone. Which has absolutely same problems, but is having hardware from another vendor.
 
In our world, SoC defines how things work, not the one that put SoC on PCB and name / sell it. This means that most of the drivers are the same, especially this area is shared - low level communication protocols such as GPIO, I2C, SPI. This is always shared among boards with the same SoC. This goes further. It is shared among same families and we also already have some common generic top level API / libraries that can be used. https://docs.kernel.org/driver-api/gpio/consumer.html (but here my understanding ends, I am not updated with the state of this)
 
 
Yes, it has no point poking into. WiringPi library is a dead project for many years and its no point dealing with this. What vendors do here is, trying to be "as Rpi as possible", so they are doing their quick and dirty assemblies of that, always with partial functionality and absolute absence of maintenance. Their goal is to sell, regardless what is the quality of software. Is that your goal? I doubt.

I am not an expert in this field, so those are general tips, but there are people on and around this forum that knows this stuff well, as they developed those libraries.
 
 
I am just giving you some ideas / tips. Decision what you will do with your time is yours.

Another one that came into my mind, while replying: https://github.com/eclipse/mraa

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.

I was thinking of asking the same question.
 
Personally my feeling is if you are planning on helping Armbian by working to incorporate your efforts back into Armbian then I strongly encourage your efforts.  But I would recommend working with the Armbian developers on how you plan to do this, as it can be frustrating for you if you put in a lot of work into something, only to find disagreement from the Armbian community about how you are implementing something that might prevent it from being accepted.
 
If your intention isn't to incorporate your work back into Armbian, then you are creating just another fork (like the many that already exist), which you are entitled to do since this is open source.  But in that case I would request that you not use the limited Armbian resources to do that (i.e. our developers and infrastructure like these forums).  These forums are for Armbian developers and users, not for use by forks of Armbian that just attempt to take from Armbian without contributing back.

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. 

Great job!

Interested for integration into main config tool? https://github.com/armbian/configng Now this tools is properly made.
https://docs.armbian.com/User-Guide_Armbian-Software/#adding-example

The tutorial and automated script have been updated for images that use extlinux.conf to configure the bootloader.
 
In addition, some logic has been added to select the correct network device name (eth0 on some systems, end0 on others).
 
The script has been successfully tested on the Banana Pi F3 with the Ubuntu Noble legacy minimal image.

Probably we should switch rather to https://vscodium.com/#install ?

Many of us are using Armbian not just on ARM single board computers but also on servers (bare metal & virtual). We use our builds since we trust it more then Debian, Ubuntu, not to mention other distributions that are recklessly updating and one ends up as an OS tester and not OS user. Personally I use Armbian Jammy on Ryzen 9 workstation with great success. My primary use case is development / productivity. For the road I used to have 13" Dell notebook which recently suddenly died. It was out of warranty so I had to get something new. After some testings of various devices I settled with 12th Gen Intel i5-1240P powered Lenovo. Then I tried many general purpose distros to see how well they work and all had some (minor) troubles ... 

We are having UEFI images (common image) since some time, but UEFI nor desktops were fine tuned nor ready for such performance daily driver desktop usage. We were close, but not close enough to just run it. Past two weeks we have been lifting general UEFI support, fixed many bugs and what came out is "Armbian ultimate developers desktop build".
 

 
- improved support in GRUB (armbian wallpaper) & HiDPI GRUB support
- all preinstalled applications are normal apt packages
- current 5.15.y kernel, Jammy userland (5.19.y has some strange issues)
- snapd is not installed (user can install it)
- HiDPI support (automated adjustments on big screen resolutions)
- NVIDIA graphics acceleration with proprietary driver (x86 only)
- Intel graphics acceleration also works out of the box
- preinstalled Google Chrome (x86 only)
- preinstalled Microsoft Visual Studio Code (x86 only)
- ZFS 2.1.5 ready (apt install zfsutils-linux zfs-dkms)
- face unlock works perfectly fine on this laptop
- installation to SSD drive to dual boot with Windows 10/11 is supported Armbian classical way by transferring actual live image to the prepared partition via nand-sata-install. All you need to do is prepare spare space on your drive, Windows 10/11 or Linux, UEFI support (most if not all hardware for past 10 years has it).
 
I have tweaked images (XFCE, Gnome, Cinnamon) a bit to my personal needs, but making changes is welcome.
 
Nice to have: disk encryption within nand-sata-install, small bug fixing, additional DEs. Currently we have CLI, XFCE, Gnome and Cinnamon. Others are too buggy.
 
https://www.armbian.com/uefi-x86/
https://www.armbian.com/uefi-arm64/
 
Please report where it works and how (well)!

Key is not deprecated, method is. On Noble / Sid and future.
 
sudo wget https://apt.armbian.com/armbian.key -O key sudo gpg --dearmor < key | sudo tee /usr/share/keyrings/armbian.gpg > /dev/null sudo chmod go+r /usr/share/keyrings/armbian.gpg sudo echo "deb [arch=$(dpkg --print-architecture) signed-by=/usr/share/keyrings/armbian.gpg] http://apt.armbian.com $(lsb_release -cs) main $(lsb_release -cs)-utils $(lsb_release -cs)-desktop" | sudo tee /etc/apt/sources.list.d/armbian.list apt update  

Yes, I am working on that.
Whiptail is what I am educating me in closer right now.
 
But it will most likely be it's own script. Trying to implement the script straight up I think would become messy pretty fast, and I don't think anybody is interested in that.
 
But yes, it is happening, sometime.. xD
I was honestly hoping it would already be a reality, but my health keeps putting up roadblocks for me.