Igor

https://www.armbian.com/compatible/ Here you can check a selection of compatible devices, usually in some personal / Armbian use. You probably don't need 16 port USB hub which is on that list, but that will certainly work perfectly. If you go for some cheap variants, and most of hubs are a lot cheaper, you will be chasing luck. For my purpose, automated testing of USB devices withing Armbian, I can't use cheap ones.

"Virtual disk images (such as VHD and VMDK) are intended to be used for cloud computing," https://en.wikipedia.org/wiki/IMG_(file_format)#Comparison_to_ISO_images Our build framework can generate cloud images directly https://github.com/armbian/build/blob/main/extensions/image-output-vhd.sh in case you need to automate this and you don't want to mess with additional scripting. ./compile.sh ENABLE_EXTENSIONS="image-output-vhd" Try using dd and copy entire image from USB to /dev/vdi or whatever disk device is. Please provide armbianmonitor -u and if you want to look into & help in this context, here are sources. You are also welcome to open a ticket and we both can hope someone will fix this soon. Even its probably just one-line fix, someone needs to find that line, test it to make sure it works and open a pull request.

If you don't power it via powered hub, its almost certainly this. Those USB ports are not delivering sufficient power.

They are ISO images, just compressed with .xz Yes. this should be correct ISO image, just with fixed name. If you use this link https://redirect.armbian.com/region/EU/uefi-x86/Jammy_current our redirector will give you latest image.

Thanks for the tip! Our current dirty hack is not even that and anyway doesn't work. You are welcome to remove that patch an add this one. Once merged, I can enable hardware on automated testings to see long term effects.

With last release, we have frozen sources at branch. If you need specific version, you need to change both: KERNELBRANCH='tag:v6.1.23' KERNELPATCHDIR='meson64-current' # where you have patches that match your version. In most cases they will just fit.

We had (still have) issues (broken ipv6) with primary rsync server infrastructure and secondary (which is probably your source) was out of sync until few hours ago. I have manually re-run update check and images are now in sync, while packages are not yet. Working on it ... Thank you!

Official image builder is old Armbian fork that is not maintained by anyone, so its at least security hazardous to run those low quality quickly made official builds. Anyway they are contributing nothing but build configs. You would help a lot more people, regularly, if you add config changes (what you are adding, not what you are striping out) to the Armbian build framework, which is applying fixes daily: - for build configuration - hardware support https://docs.armbian.com/Release_Changelog/ That you will not find in official software support.

sudo apt update sudo apt purge armbian-bsp-cli-odroidn2-current sudo apt install armbian-bsp-cli-odroidn2-current Should not make things worse. If it will uninstall base-files, re-install them too. But yes I am guessing here a bit as I am just remembering that we discussed this problem once and I think we have fixed it. Files exists: https://armbian.systemonachip.net/apt/pool/main/b/base-files/ Thank you! No worries.

We can't provide all variants but as we keep build framework in decent state, you can build it at any moment. If hardware features still work well, that is another story - hardware does not have official Armbian maintainer anymore. Hardkernel should take care of this, but they does this job not very well. They never see value in our work even we tried to maintain their software stack for them, their users and our competitors. https://github.com/armbian/distribution I tried to automate OMV image making, but got overwhelmed with more important and critical problems - we are seriously understaff. If someone, that is not already helping on the project, takes this, invest his time and move forward, it would help many. @houdini_69 I am thankful for every support we get! <rant> Donations are emotional trigger at best. End user financial support via donations never went over 0.5% of our costs - to paraphrase: its like covering 2 out of 365 days and expecting to have service with rights to complain 24/7 for a whole year ... Which means we still do more or less everything for free. Maintaining this fairly complex software stack costs us a lot more most people can imagine - i am tired to explain this as nobody really cares. All we have to care is to not burn out which is again hard when reward is not proportional. Also there is always another and another problem and keeping users happy is impossible. And unhappy user don't donate. This is a lot more valuable. I know what we need, but can only count on volunteers. Which in 90% aim at funny jobs avoiding hard and unpleasant tasks. That we need to hire, which is not possible ... </rant>

Try to purge bsp package and install latest from repository.

At release time, we make a branch from build framework and this was the 1st time that we also lock down sources. At least most of them. This means you can recreate identical images as those that were officially released. Since maintaining is very expensive and resources are slim, we have to focus very carefully what to maintain. Maintaining stable branch is a dedication - merging bug fixes only from main https://github.com/armbian/build/commits/main on a daily basis. As this board doesn't match "Standard support" criteria: https://docs.armbian.com/User-Guide_Board-Support-Rules/ its masked behind EXPERT="yes" switch. You can build it, but you have to understand that nobody is specifically taking care of. But you ... if you want to keep it on the requested levels of "Standard support".

There are two paths from here: - port device tree to LTS 6.1.y kernel (example) - add more recent ZFS to the stable package base (this might not be the best idea as it affects many existing installations and I saw many corruption related bugs in recent ZFS versions)

I bet you saw a big warning when you boot this image for the first time? Warning is there, because its impossible to help. Use kernel 5.10.y for better hardware support. Many functions on mainline are not even developed yet.

Some users may experience issues when downloading new v23.11 images from our website or also sometimes with apt not having the new packages. The reason is that we had a (not so) small whoopsie at the very last minute and the infra is still recovering and syncing. Easiest workaround would be to simply try multiple times until the redirector hits a mirror that has the files you want to download. Alternatively go directly to https://fi.mirror.armbian.de/ which (seems to) have all the files atm. Will work with apt as well.

Quick quess. Bug in OMV wireguard install scripts or Wireguard package dependency which removes Armbian firmware and installs kernel that has no support for Odroid XU4.

Probably, if not something else is also missing from the system ... worth trying. This is the content at sources: https://github.com/armbian/build/tree/main/packages/bsp/common/usr/lib/armbian-install

Everything looks OK and I can't find a problem at our side at short notice. Workaround. Create this file (/usr/lib/nand-sata-install/exclude.txt) with following content: /boot/* /dev/* /proc/* /sys/* /media/* /mnt/* /run/* /tmp/* /ddbr/* /var/log/journal And try again.

@RadxaYuntian

If board is supported, armbian-config will do.

Is this a new install, upgrade from, ... This is always needed to understand better what is going on: https://forum.armbian.com/topic/5699-how-to-provide-and-interpret-debug-output/

You can help developers changing this by making a pull request to include required packages into default package base - for every desktop variant.