Pinebook Pro PCIe init issue

[R32Fanboy]

A few days ago I got the NVME adapter for my pbp. I bought an Intel 660p SSD for it, since it was marked as supported on the wiki. After install, it didn't show up in lspci or lsblk.
the output of dmesg | grep pci returns these errors:


[    2.953763] rockchip-pcie f8000000.pcie: no vpcie12v regulator found
[    3.112162] ehci-pci: EHCI PCI platform driver
[    3.174161] ohci-pci: OHCI PCI platform driver
[    3.733470] rockchip-pcie f8000000.pcie: no vpcie12v regulator found
[    4.318696] rockchip-pcie f8000000.pcie: PCIe link training gen1 timeout!
[    4.320361] rockchip-pcie: probe of f8000000.pcie failed with error -110


I tried updating U-boot on the SPI chip as well as on the SD card, I've tried Debian, Manjaro, Fedora, it's all the same.

I then turned to a friend who also owns a PBP and had them run lspci and dmesg | grep pci and their own pbp returned the same error (their pbp is a first-run preorder and I bought mine a year later.). Is this a hardware issue or is there something I'm missing in the NVME installation that allows this board to initialize it's PCIe properly?

I have this issue too, see https://forum.pine64.org/showthread.php?tid=10118 and even today, after flashing multiple spins of uboot to emmc, sd and SPI along with 2 new nvme adapter boards from Pine store, get the same pci related errors as above. (BTW, this is with first batch PBP & supported NMVe drive per wiki).  

It might be the ribbon cable conductivity on your adapter which you could verify with a multimeter as per this thread: https://forum.pine64.org/showthread.php?...904&page=2 and if so, try the adapter from ameridroid store - definitely not from Pine store.  

Won't mention the response received from Pinestore after the second adapter did not work for me and I got redirected to their IRC (but someone has already noted "worst support ever") so check the cable continuity and maybe get a new one from ameridroid?

Hope that helps and sad to see this issue is still being reported on something that has been out for nearly a year.

Why would the kernel still have this error with no cable present then? This is a documented error on several models of RockPro64s prior to the pinebook's production as well, and forum posts on it seemed to end with no good solution.