@JuanEsf Is possible fist acces via SSH?

Hi @ff255, It's been a while, I'm assuming you are still getting the same error as mentioned below: Applying kernel provided DT fixup script (rockchip-fixup.scr) ## Executing script at 09000000 Wrong Ramdisk Image Format Ramdisk image is corrupt or invalid SCRIPT FAILED: continuing... The output you shared helps, but can you share a little bit more? Would need to know the following for your case: Filesize of your kernel image file Filesize of your initrd file If possible, filesize of the DT file being loaded. With those three values, we should be able to calculate the correct load addresses and try booting. (All this also presuming that your issue is that the load addresses used by U-Boot/the bootscript do not leave enough room for either a kernel or initrd file, causing one of those to overlap the start of the other.) Groetjes,

Many thanks for your replies. @Werner I can only say that I got the image via Armbian Imager, well designed for lazy people like me. This: On the Armbian Rock5 ITX web page, There are two candidates: 1 ) This one, because it's the only image in the list with variant "Gnome": or 2) this one, because it has the same size (1.4 GB), but doesn't say anything about the variant. The two images above have two different sha hashes. If it's true that isn't good for desktop (I agree with you because it doesn't work properly), I don't understand why it's tagged as "Recommended" on Armbian Imager. Anyway, I deleted everything and started from scratch, using another image tagged as "Recommended" based on Debian 13 and CLI only. This one is less complicated and till now works. @eselarm I tried two different monitors: the first one is quite modern as it supports not only many resolutions, but also different frequencies and other stuff. The second one is very basic: it can support up to 1980p at 60hz. In both cases, I got the same behavior. I also tried in the past EDK2-UEFI, but it didn't work very well on my Rock 5 ITX due to unexpected behaviors that I could not control in an effective way. That being said, unfortunately I don't have the exact filename and sha256sum of the previous image because I changed the image.

Yes you can work to make things better. But since I don't have this box (nor even one with that specific cpu version) there isn't anything I can really help you with. But anything you find/improve can be submitted back to Armbian as a PR. This stuff is all community supported, thus it depends on people like you to make improvements and submit them back for others to benefit from.

Thanks @JuanEsf