10-23-2020, 06:52 PM
(10-23-2020, 05:17 PM)Seferi Wrote:(10-23-2020, 09:48 AM)Arwen Wrote: @Seferi and @ReddestDream, I read through the posts and I don't see the model of the NVMe drive you have. Please post it.
On at least one rare occasion, a person accidentally bought a M.2 SATA drive. Not NVMe. Not saying that is the case here.
On the other hand, some people have bought high performing M.2 NVMe drives. Only to find out that it won't work in the Pinebook Pro because it also draws a ton of power. And does not support power saving functions.
Further, their appears to be an occasional problem with the SoC running at PCIe 2.x speeds, (5Gbps). Some people have limited their PCIe lanes to 1.x speeds, (2.5Gbps), and then had perfect reliability. Still pretty decent performance compared to the eMMC or SD card. (4 lanes of PCIe 1.x @ 2.5Gbp, minus the protocol overhead of 20%, still gives 8Gbps / 1GBps speed.)
Thanks for the reply mate. Here is my drive:
Figured out my issue. The ribbon cable was defective and didn't have the pins on the SSD-side exposed/uncoated. The ribbon failed my continuity test with a multimeter. No signals were ever passing through it, explaining why the PBP never saw it. Apparently it wasn't uncoated properly at the factory. I purchased a new NVMe adapter kit from Ameridroid. Fingers crossed this one will work.
I had tested a Crucial 500 GB CT1000P1SSD8, Samsung 960 EVO 1 TB, and a Sabrent Rocket Q 1 TB. All these drives are NVMe and work in my NVMe USB adapter just fine. nvme wasn't even showing up in dmesg. Nothing on lspci. Nothing in nvme list. But glad it seems like it was just the ribbon and not something I did.