north1

Thank you for your feedback, I think you are right in that my problem related to an issue with 24.8.4. I could not boot from NVME when I used kernel 6.1.75 with 24.8.4 (ie the version of images published here https://www.armbian.com/radxa-rock-5c/) I built a new image using 6.1.75 and 24.11.0 (subsequently upgraded to 24.11.1), this now boots fine from the NVME drive.

I am trying to boot my Rock 5C Lite from an NVME drive, but have experienced some problems with the vendor kernel. I followed instructions by amazingfate in this forum to create a small SD card with a u-boot image, ie I created a complete Armbian image (vendor kernel) on an SD card too boot up the Rock 5c Lite A second, small capacity SD card was inserted into the USB port using a USB adapter U-boot was transferred from /usr/lib/linux-u-boot-*/ to the small SD card: dd if=./idbloader.img of=/dev/sda seek=64 conv=notrunc status=progress dd if=./u-boot.itb of=/dev/sda seek=16384 conv=notrunc status=progress My chosen Armbian image was transferred to the NVME drive using Balena Etcher Finally I use the small SD card with u-boot in the SD card slot on the 5C Lite and the NVME drive goes in the NVME hat. I tried two different images from here on the NVME drive Debian 12 (Bookworm) with XFCE and bleeding edge kernel v6.11 Debain 12 (Bookworm) with XFCE and vendor kernel v6.1 The board boots fine from the NVME using the v6.11 kernel, but the implementation seems to be nowhere near complete. The HDMI port doesn't work, the fan is spinning at full speed but is difficult to control because CPU temp is not reported properly, etc. The bord performs well though, and reports eight functioning CPU's. The board does not boot from the NVME using the v6.1 vendor kernel. It tries to start up the kernel but gets stuck. Please see the attachment below for a copy of my complete console output at high verbosity. Would someone be able to help to get the vendor kernel to work? UART-Log_Vendor-Kernel.txt

I have not been able to recreate the initial problem. Perhaps there was a problem with my sd card or the power source earlier. I did not change either one, but I can now boot with 6.6.35 without any further problems. I would recommend to Gavin to try a different SD card or power source. I would stay clear of the gnome desktop images though, my experience is that the 3c will freeze up after idling for 10-20 mins if you run with gnome.

I haven't tried 6.1.y images but eg 6.6.32 worked fine (built this myself using standard 3C configurations in the build tool). The latest weekly build gets stuck in some kind of loop during the boot process.

Agreed, I can't get the latest Bookworm image with kernel 6.6.35 to boot

Perfect. Thank you very much

Hello, I tried the new desktop image and it boots nicely off an SD card, I haven' tried my nvme drive yet. The desktop user experience is very smooth, so well done to everyone who made this work! The ethernet port works well, but unfortunately wifi and bluetooth does not work at all, I do not even see a wifi interface if I use "ip a" (but loopback and ethernet show up). Is this a case of a missing driver in Ambian? How do I add the missing driver? Wifi and bluetooth works under debian (as provided by Radxa), so I ran "sudo lshw -C network" under debian and get the output below: description: Wireless interface physical id: a logical name: wlan0 serial: 98:03:cf:d2:32:7c capabilities: ethernet physical wireless configuration: broadcast=yes driver=aicwf_sdio driverversion=5.10.160-33-rk356x multicast=yes wireless=IEEE 802.11 Finally, please see this link for log data and information about my set-up etc, I notice there are some bluetooth error messages. https://paste.armbian.com/umazejomut