ScottP

Same issue here. I'll use 26.04 and go from there As it have been reported by multiple people could I suggest that the broken images are taken down to save others wasting time and also wasting hosting bandwidth downloading multiple images until they find one that works. Thanks.

I ran into this issue a while back, I just downgraded back to the 5.10 kernel as it was a production server and I didn't have time to troubleshoot it. Are the current builds in the repo no fixed? I want to upgrade again to get the newer NPU driver to try out some LLMs on it Edit: I installed the latest image: linux-image-vendor-rk35xx 24.11.2 and it appears that this issue is resolved. Many thanks!

The other issue with the vendor kernels is that the DTB seems to contain every rockchip dtb known - hundreds of them not just rk35xx - the default 256MB boot partition fills up as there is no room to have two kernel/overlay versions

Same - this kernel seems to limit number of processes - fork failed, resource temporarily unavailable. Show your user limit: ulimit -u Show what limits other processes has: grep process /proc/*/limits

I installed this kernel on a Rock 5B. Although the above fixed the issue for the original poster the failure of configure stage is not addressed. I think there is something wrong with this kernel. On my Home Assistant server some containers were failing to start and the errors pointed towards some resource/limits issue even for processes running as root. The errors were something like - fork failed, resource temporarily not available. I think update-initramfs ran into this issue producing the errors in the post. I don't have any logs since it has hard to do anything at this point, commands failing when trying to diagnose. I rolled back to 5.10 manually to get my server up and running. I think the maximum number of processes was being limited artificially low despite nothing being in /etc/security/limits* - I did see for not root users this limited to around 2k processes via ulimit -u - cant remember the exact number. If anyone is running this kernel you can check the limits for various processes - user and root alike by looking at /proc/<PID>/limits On my rolled back 5.10 legacy kernel this is 61790

I Enabled overlay for USB0. Had to comment out g_serial too otherwise get hangs and usb disconnects. Odd decision to make the only USB port this board has into client mode instead of host so g_serial can be used as another console?