Chris C

Hello again, Yes, I read the documentation, that's why I said my UART adapter doesn't work and I ordered a compatible one which is on its way. I managed to somehow solve my issue. Luckily I had another SSD lying around (Kingston) which works without any issue and is recognized every time and bootable. My original SSD (Crucial) has no hardware problems though, because I used it in an x86 Ubuntu machine and works without any problem whatsoever. So although I managed to solve my situation, the underlying problem is still there and may re-surface to someone else. I would like to re-state that the 25.5.1 armbian desktop does not even boot (edge or vendor) and the 25.2.2 boots but barely works on my board. Thanks for the time. PS. I ended up using JR ubuntu, because although non-supported anymore, it was the only one working. If you find my situation is worth further investigation and you would like to look into it, I can send you the serial logs once I get the proper adapter.

Thank you @royk, @going, @eselarm for your time and suggestions. I really appreciate it. I tried a lot of things, you mentioned, out of which none was working. Again, ultimately I wanted to install noble gnome, but the 25.5.1 image doesn't boot at all. So I found the older 25.2.2 noble gnome and that did indeed boot and I was able to proceed. Interestingly this image seems to consistently detect the nvme every time. That being said, it acts very weirdly. it's extremely slow to the point that you can barely open any app, it takes a minute to change a page in settings, and sudo basically is not working (hangs indefinitely). The desktop / workspaces / app launcher are very smooth though and htop shows all 8 cores practically at idle. Also when I boot, it first shows the splash screen (armbian loading), and then goes black indefinitely and I have to press the power button to go to the login screen (looks like it suspends after boot immediately). Poweroff doesn't work either, it hangs. With this weird situation I was able to install the bootloader into the SPI, but I wasn't able to do an upgrade or install the full system on the nvme. Do you have any input on this? Some additional notes: - All of the tests above were done with a brand new sandisk 64gb SD + balenaetcher with verify on macos. - I've also tried Joshua Riek's 24.04 image and although it has the nvme issue, the OS runs very smoothly without any lag. - Although the noble gnome image seems to consistently find the nvme, the minimal 25.5.1 image does not. - My UART adapter doesn't work and a CH340 one is on it's way for boot logs.

Thanks @royk, Can you please elaborate a bit on how to try out the kernel you sent? Isn't it for orange pi 5? How do I build an image out of it for the rock 5b+?

Thanks for the suggestion, I appreciate it. Unfortunately it didn't do anything. I've tried the args one at a time, combined, still nothing. One thing I noticed, I can consistently get the nvme to properly show up, during the first boot of radxa's image. (ie. flashing the radxa image to an SD, booting for the first time to the desktop, the nvme will be detected and work properly). Rebooting after that is a hit or miss and generally only cold boots sometimes work. I also tried the args you suggested in the radxa official image and still the same. Btw for everything I mention, the armbian SPI image was installed. My only assumption is that some irrelevant delay related to the first boot, gives time for the nvme to initialize? On subsequent boots I get "pcie link fail" during boot, and again, lspci works, lsblk doesn't. Also I would like to use armbian ubuntu desktop which I can't at the moment, since the noble gnome image doesn't boot at all.

Hello, I've recently bought a rock 5B plus. I have a brand new crucial P310 nvme 1TB with the goal to boot from it. As the title says, sometimes the nvme drive is properly detected, sometimes not. (Everytime the controller is visible in lspci, but only sometimes shows in lsblk). When the drive is properly detected, I can write to it and it works fine, without issues. I've noticed that it is more likely to be detected on a cold boot (ie. if I turn off the power and come back the next day, the first time it will probably show up). I have the official radxa 65w PD power adapter (although I've also tried a lot more during the process with the same results). I tried with the official radxa debian image, and with armbian, and the results are exactly the same on both. Btw, I would like to mention that armbian noble gnome doesn't boot even from the sd card (blue led but no display output, I let it for over 10 minutes), only the minimal/iot works. I don't know what else to try at this point, I can post any info / logs you may want. Thanks!