The only thing I could manage to get information from was this: I had to rewrite the SPI-flash and now I see: Btw, this is the output when I was using the official OrangePI Ubuntu distro:

Strangely I can't get any outcome from that command: Now I am confused if there is something else going on, however, the OrangePi official distro recognised the nvme disk.

You need the U-Boot source-code version; I at least cannot conclude on it; You can watch the start-up via serial console, then you will see. Or like this: root@rock3a:~# strings /dev/mtdblock0 | grep "U-Boot SPL 20" U-Boot SPL 2017.09-armbian (May 20 2024 - 00:46:51) I see you have 2 options: which U-Boot is used: mtdblock0 (the SPI-flash) or mmcblk0 (SD-card) ??

Hey @eselarm, Thanks for the quick answer. My goal is indeed having a more generic computer for server tasks. The version of the u-boot is: I have switched again to the orangepi5 6.18.10-current-rockchip64 kernel but still not showing nothing. Thank you.

Log shows nothing about PCIE when 6.19.0-edge-rockchip64, it does when 6.18.8-current-rockchip64 If you just upgraded the kernel via apt, then this might be the point where an older U-Boot is incompatible with newer kernel. This is the case for all Rockchip devices I have and not strange. It is like it is, so if you want edge or newest or even standard Debian sid/unstable/testing kernel, you will need to look at that in more detail. I have been spending a lot of time on it, it is simply what you want or need. If you want all RK3588 silicon HW support, so like video encoders, stick to vendor based U-Boot and kernel. I you want a generic computer that is good enough for server tasks and web-browsing etc, use mainline based U-Boot and kernel. Of course something else might be wrong, but reporting U-Boot version would be needed and helpful first I think.