Can the OPI5 be Configured to Run LCNC?

Hello guys, after 9 tentatives, I'm exaclty in the same situation of Kanuboy13b!
Tentatives because for 3-4 days the main branch was (in my opinion corrupted, the second menu was not working moving arrows I saw on the screen symbols like ">[OB" instead going down through menu.
After some days doing exactly the same sequence of command, cloning the same repo, finally it works.
Now I have for the second time a ISO perfectly generated but red led, no boot.
Well.. I don't get the issue of dtb, in the boot partition I have 2 folders:

\dtb\rockchip
\dtb-5.10.110-rockchip-rk3588\rockchip

both full of dtb files.. what happens?
Do you mean something else?
What I have do to precisely? replace one of these folder with other dtb files? where I have to pick them?

I will try to build again based on Debian and see what happen, following Royka suggestions.

This job it much more strong than expected. 
 

In previous build, in final step, I saw attached warnings.
Could be critical?

royka has provided the dtb file in his latest zip, you need one that is specific to the orange pi for it to boot.
what I did was mount the boot partition and copy the dtb file in the location where all the dtb files are located. If you " ls -la" the /boot/dtb/rockchip directory prior to copying you'll notice there isn't one with the the orange pi 5 in the name. Hence why it isn't booting.

Once I copied the dtb file from royka's zip file to the boot partition, I was able to boot.

Royka, one thing I wanted ot ask is, what did you have to do to get the rtl8192cu driver for the kernel to work. Now that I was able to boot the armbian image I compiled, I noticed I was back to the point of not having wifi again.

I did do some snooping around the kernel config file and find a line in the config file for the rtl8192cu saying it was not set. I changed this to "=y" and started compiling an new image last night right before bed. No idea if it worked or not, I was going to test it when I got home from work. But, I figured I ask if that was the process or if there are other steps involved to get the OPi5 to recognize my usb dongle.

Yes changing the line
"# CONFIG_RTL8192CU is not set" to "CONFIG_RTL8192CU=y" will probably work in this case.

If you did make a change before in the config you might have a file linux-rockchip-rk3588-legacy.config.defconfig

This is since the new build system, I assume that when this file exists
it overrules the "default" linux-rockchip-rk3588-legacy.config

You could check after you've installed your new compiled kernel with:
cat /boot/config* | grep CONFIG_RTL8192CU

Usually you'll change the config in the menu because in some cases it automatically set some other required options.

The missing firmware is something you could ignore. That firmware is only needed at the moment you'll use hardware that needs that firmware.

So I am not sure if the RT was a success or not after getting the Ubuntu Jammy image up and running. 
I flashed the image with the flag enabled for the wireless driver, I was able to boot up though for some reason the initial user I had setup on startup did setup properly. None of the folders were generated for my home directory, and I had a myriad of permissions issues like not being able do download anything from a web browser. I was able to bypass all that by creating a new user and deleting the old one. 

anyrate downloaded the wayland driver, installed the linuxcnc-uspace deb package 
however I am not seeing the low latency numbers that were observed in royka's tests, least to my understanding I am not.  I've attached a screen shot of the latency test while running youtube in the background. I ran cat /proc/version and didn't see anything that eluded to the fact it was a real time kernel. So I am starting to believe that the patch and config files didn't work. 

Honestly I am starting to feel a little wary of Armbian. seems like a lot of hoops have to be jumped through to get it to work. The correct dtb file being absent on a fresh build, the user profile being bad on the first startup. I don't think I had this many issues when I did an raw Arch install on my laptop. 

Anyrate downloading the Debian image royka provided. I'll give that a crack. But I am starting to not be as optimistic with this distro.