Igor

OK. This was very first official test build and problems are more than expected. Its possible but can't check since I only have this one.

Scroll down and pick version with kernel 5.4: https://www.armbian.com/orange-pi-4/#kernels-archive-all Version 4.4.y is without HDMI ATM, 5.4.y have HDMI ... it takes little longer to boot, be patient. My is with NPU.

Kernel is talking with the hardware. Armbian deals with single board computers where things are somehow different - its bridge between embedded and desktop world ... We usually provide two kernels per hardware in many (any supported if you build image on your own) Debian derived user-land combination you want: Stretch, Buster, Jessie, Xenial, Bionic, ... This can surely be fixed on any variant, but as I said ... we have some troubles with securing matched headers atm.

USB issues on Odroid C2 are know but not this weird We need someone to recreate, then this issue will become interested. If this is happening just to you it can be something wrong with your HW ...

Is this the one read by boot script located on the SD card? From older images you need to do this: but in case you have doing manual changes to the fstab and system in general, it can fail.

No, issue is not C2, nor exactly Armbian specific. Probably you are pointing to wrong UUID for / device in armbianEnv.txt on your boot media ...

Providing logs with armbianmonitor -u significantly raises chances that issue is getting addressed. Board obviously boots without changing anything ... moving to bug tracker. That's few years old Armbian which could have been fixed a long time ago. Please try to recreate this situation on a freshly installation.

Yes, it works there I thought it will be the other way around. 5.4.y looks stable to me ... but I do use a heatsink and a good power source. http://ix.io/28ro

It works to some degree ... screen is black, but you can boot from SD card ... by inserting it in. (self made image - will try from the download l8r) More: http://ix.io/28r8

They are on holidays ... but files are here: https://drive.google.com/open?id=1QMU5n-7fCx28cQPH_lu2L0wrFWeC3G45

Headers will be updated to (compatible and installable from armbian-config) version once we are finish with this (around 2 weeks): This is amateur service and we already made this experience very simple. Headers can install from armbian-config or the way piVCCU suggessts ... if everything is ok. There are also some issues with kernel headers https://github.com/armbian/build/pull/1754 https://github.com/armbian/build/issues/1751 which means also experienced people have issues. What you can try is to build from sources and enable header compilation ... https://docs.armbian.com/Developer-Guide_Build-Options/ its a little bit more work, but doable.

In about a year (or more) most/all features will come to the modern kernel and (hopefully) work perfectly. Which is why we provide both kernels.

Noted & confirmed. UDOO is not actively maintained, but we do make images since most of the things (imx6 kernel wise) works ... I'll see if this can be fixed without wasting days. What about this image? https://dl.armbian.com/_old/udoo/nightly/Armbian_5.94.190826_Udoo_Debian_buster_dev_5.2.10_minimal.7z

Images done. Process finished without troubles this time.

Started.