Had my Rock5b working quite well for a couple of months before deciding to see if I could get it booting from NVMe. Big mistake.
Initially I flashed it from a running system via /dev/mtdblock0
. After failing to get it to boot from NVMe after a couple of attempts I have a feeling I might have flashed (presumably the first 16MB of a) Debian SD image to it. Following this I wasn’t getting any HDMI output and it wouldn’t come up on the network, though depending on the inserted SD card the LEDs would appear to go through the normal boot sequence or just go into a boot-poweroff loop. But no worry - it’s unbrickable right? Just need to get into this maskrom mode people talk about…
After a couple of weeks of fiddling and finding a cable/port/power combination that would allow me to perform an apparently-successful spi flash (NVMe “armbian” image) via rkdeveloptool
, it was still doing the same thing, no HDMI output or coming up on the network. Now having a USB/TTL uart, I looked at the serial console and discovered that it is booting “perfectly” from the NVMe (this, I think, is the rock-5b_debian_bullseye_cli_2023-01-03T0407+0000_gpt.img.xz
image at this point), albeit still with no HDMI output and the kernel doesn’t appear to be finding the ethernet controller.
The r8125
module is loaded however, and dmesg
shows the normal complaints about it tainting the kernel. But there are no lines suggesting detection of a device. dmesg | grep -i eth
shows nothing of interest.
lspci -vv
shows the RTL8125 all present and correct: https://gist.github.com/risicle/af585dba5d0cc93a08ecf97fbd2dafbc, but ip link
only ever shows the loopback interface. Could it be missing some firmware?
I use this as a headless build-machine, so the HDMI isn’t my major issue (though it would be nicer to be able to use it instead of the serial console), but not having ethernet is a big problem.
I’ve tried this with both a 20W PD PSU (which ran the board fine for its first couple of months) and with 20V over a barrel jack adapter. Same results.
Any ideas?