Can the OPI5 be Configured to Run LCNC?

Used the source from: github.com/armbian/linux-rockchip
The rt patched source is now next to the deb files.
The only thing I noticed was that when you create a deb package it automatically compresses the kernel image (which gives a missing arm64 magic error), so to workaround that I repacked it with the uncompressed kernel.

Also after installing LinuxCNC it updated the iniramfs of the old kernel and linked uInitrd to the old kernel one. To prevent that from happening it might be better to remove the old kernel (after making a backup).
Otherwise you could: sudo update-initramfs -u -k all

I've updated the deb package with the iwl driver by the way.

I plan to use your updated deb package. If there are any problems, I will try to compile it myself. Thank you.

I installed 6.1.75-rt23 on SD card and it works ok on Orange-Pi-5. I tried to put it on nvme and it didn't work. It freezes when booting. Please can you put a version that also works on nvme.  

Try this Then try open FSTAB if possible and edit it by replacing the UUID of your drive from the resulting list

Like tommylight said and I want to add that you should also check /boot/armbiEnv.txt for the same UUID. When you see a /boot mount in fstab you could remove that line too.

Here it didn't recognize the ID option by the way, in that case just leave that away, alternatively you could issue the blkid command to see the UUID.

first of all, thank you for your prompt answers.I can boot with kernel 6.1.75-vendor-rk35xx, with the 6.1.75-rt23 .debs installed, but without making the link (sudo ln -sf vmlinuz-6.1.75-rt23 Image). If I reboot and then make the link, it doesn't boot anymore. In /proc/cmdline I don't see any value for ubootpart=.

royka wrote:

... alternatively you could issue the blkid command to see the UUID.

I could not recall this to save my life when i was answering this!
Thank you for reminding me, now i will go on and forget it promptly!

I can read all the IDs in /drv/disks...., but I don't know how to enter it to recognize it.

rootdev=UUID= lotsofnumbershere
those lots of numbers have to be replaced by the ID of your drive

 The ID returned by blkid is the same that I have in armbianEnv and it is the same ID that it says it does not recognize when booting.