Nvme drive not being recognised.

[vssz]

Hi all, I added a KingSpec NE-512 NVMe drive, listed as compatible in the PBP HW accessory wiki to my PBP however it is not being recognised either with the stock Debian+Mate (on eMMC) or latest Manjaro XFCE edition (on SD).  Have flashed pcm720's uboot to eMMC and SD without effect.  

I just want to use it as a data drive, at least to start with and was hoping it would just work.[url=https://wiki.pine64.org/index.php/Pinebook_Pro_Hardware_Accessory_Compatibility][/url]

Do I need to update the uboot on SPI?  Which uboot release (the one by 720pcm or sigmaris)? And which procedure (the one using rkdeveloptool or the one dd'ing to /dev/mtd0?)

All feedback welcome, thank you. 
Vidya

Code:

#lspci -vvv #dmesg | grep -i pci [    0.004174] PCI/MSI: /interrupt-controller@fee00000/interrupt-controller@fee20000 domain created [    3.638913] PCI: CLS 0 bytes, default 64 [   28.899325] rockchip-pcie f8000000.pcie: no vpcie12v regulator found [   29.988256] ehci-pci: EHCI PCI platform driver [   30.198563] ohci-pci: OHCI PCI platform driver [   32.410343] rockchip-pcie f8000000.pcie: no vpcie12v regulator found [   32.990231] rockchip-pcie f8000000.pcie: PCIe link training gen1 timeout! [   32.991341] rockchip-pcie: probe of f8000000.pcie failed with error -110 #lsblk NAME         MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT mmcblk2      179:0    0 116.5G  0 disk ├─mmcblk2p1  179:1    0    64M  0 part └─mmcblk2p2  179:2    0 116.4G  0 part mmcblk2boot0 179:32   0     4M  1 disk mmcblk2boot1 179:64   0     4M  1 disk mmcblk1      179:96   0  59.5G  0 disk ├─mmcblk1p1  179:97   0 213.6M  0 part /boot └─mmcblk1p2  179:98   0  59.2G  0 part / #nvme list Node             SN                   Model                                    Namespace Usage                      Format           FW Rev   ---------------- -------------------- ---------------------------------------- --------- -------------------------- ---------------- -------- #cat /proc/version Linux version 5.6.0-2-MANJARO-ARM (strit@on2-distcc) (gcc version 9.2.0 (GCC)) #1 SMP Thu Apr 2 21:13:13 CEST 2020 #

[xmixahlx]

use mrfixit's v2.0 uboot. replace your uboot however it is working now.

[vssz]

use mrfixit's v2.0 uboot. replace your uboot however it is working now.

Thanks,  is there a link ?  Ideally to the binaries.

[tophneal]

Thanks,  is there a link ?  Ideally to the binaries.

There is a link on the main wiki page for the PBP, there's also a link for pcm720's uboot, whihc is based on mrfixit's.

[xmixahlx]

mrfixit accepted pcm's pulls so v2.0 includes them.

[vssz]

Thanks,  is there a link ?  Ideally to the binaries.

There is a link on the main wiki page for the PBP, there's also a link for pcm720's uboot, whihc is based on mrfixit's.

OK, the PCM720 uboot I already tried (from here as mentioned in his forum post here with both stock Debian (eMMC) & Manajaro XFCE (SD)) but I cannot find the other link mentioned off the main wiki page?  Any idea?  Thanks a lot!

[tophneal]

OK, the PCM720 uboot I already tried (from here as mentioned in his forum post here with both stock Debian (eMMC) & Manajaro XFCE (SD)) but I cannot find the other link mentioned off the main wiki page?  Any idea?  Thanks a lot!

mrfixit's v2.0 uboot files can be found here: https://github.com/mrfixit2001/updates_r...filesystem

[vssz]

Ok, tried MrFixit's uboot (on SD with latest Manjaro that definitely has pcie support) but unfortunately the same result.  
Mine is a 1st batch PBP if that's of any significance.

Any suggestions?

Thanks in advance.

Code:

#dmesg | grep -i pci [    0.004232] PCI/MSI: /interrupt-controller@fee00000/interrupt-controller@fee20000 domain created [    0.261972] PCI: CLS 0 bytes, default 64 [    1.174188] rockchip-pcie f8000000.pcie: no vpcie12v regulator found [    1.205991] ehci-pci: EHCI PCI platform driver [    1.265661] ohci-pci: OHCI PCI platform driver [    1.744198] rockchip-pcie f8000000.pcie: no vpcie12v regulator found [    2.324372] rockchip-pcie f8000000.pcie: PCIe link training gen1 timeout! [    2.325559] rockchip-pcie: probe of f8000000.pcie failed with error -110 # #lsblk NAME         MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT sda            8:0    1    57G  0 disk └─sda1         8:1    1    57G  0 part /run/media/vssz/Transcend mmcblk2      179:0    0 116.5G  0 disk ├─mmcblk2p1  179:1    0    64M  0 part └─mmcblk2p2  179:2    0 116.4G  0 part mmcblk2boot0 179:32   0     4M  1 disk mmcblk2boot1 179:64   0     4M  1 disk mmcblk1      179:96   0  58.2G  0 disk ├─mmcblk1p1  179:97   0 213.6M  0 part /boot └─mmcblk1p2  179:98   0    58G  0 part / #lspci -vvv # #nvme list Node             SN                   Model                                    Namespace Usage                      Format           FW Rev   ---------------- -------------------- ---------------------------------------- --------- -------------------------- ---------------- -------- # #cat /proc/version Linux version 5.6.0-2-MANJARO-ARM (strit@on2-distcc) (gcc version 9.2.0 (GCC)) #1 SMP Thu Apr 2 21:13:13 CEST 2020 # #zgrep -i pcie /proc/config.gz |grep -v '^#' | more CONFIG_CAN_PEAK_PCIEC=y CONFIG_PCIEPORTBUS=y CONFIG_HOTPLUG_PCI_PCIE=y CONFIG_PCIEAER=y CONFIG_PCIEAER_INJECT=m CONFIG_PCIE_ECRC=y CONFIG_PCIEASPM=y CONFIG_PCIEASPM_DEFAULT=y CONFIG_PCIE_PME=y CONFIG_PCIE_ROCKCHIP=y CONFIG_PCIE_ROCKCHIP_HOST=y CONFIG_PCIE_DW=y CONFIG_PCIE_DW_HOST=y CONFIG_PCIE_DW_PLAT=y CONFIG_PCIE_DW_PLAT_HOST=y CONFIG_BRCMFMAC_PCIE=y CONFIG_MWIFIEX_PCIE=m CONFIG_QTNFMAC_PCIE=m CONFIG_DVB_SMIPCIE=m CONFIG_PHY_ROCKCHIP_PCIE=y #

[xmixahlx]

confirm nvme and not sata
reseat nvme adapter cable
reseat ssd
focus on basic detection by kernel

[vssz]

confirm nvme and not sata
>>see for yourself here on aliexpress and also listed compatible in the PBP Wiki (KingSpec NE-512). 
reseat nvme adapter cable
>>done many times
reseat ssd
>>ditto
focus on basic detection by kernel
>>Tried with my stock Debian and 5.6/5.7 Manajaro kernels. Any particular suggestion?

Ordered another PBP nvme adapter as the first version which I received needs 2 folds of the ribbon cable which might be the problem   and also an M.2 NVMe SSD enclosure to verify the SSD.  Hoping between these 2 the issue is further isolated.