NVME problems

[mamboman777]

Well, I took my Intel 660p to my brother's house and put it in his windows box and it was working, firmware updated, and showing nothing wrong.  When I dropped it back in my Pinebook Pro...nothing.  So I decided to investigate some and completely took out the main board of the PBP.  After reassembling I booted and the NMVe was there!  Drove back home and the NVMe is no longer listed as a drive.  Any idea what's going on?  So, I now know, it's not the NVME's fault.  I guess next I buy a new adapter or cable?  If that doesn't work, then what?  Main board?  

I've got an UART adapter on the way, so maybe I can tell what's up in the boot sequence.  I get the impression that something is not initializing correctly.  The last major change I made was to go to PCM720's spiflash.bin on the spi to try to get boot happening directly from the NVMe.  After all this I'm considering going to U-Boot on EMMC and system on NVME. 


Any thoughts or suggestions welcome.  Thanks!

-Josh

[Samurai_Crow]

It's probably the power coming from the board wasn't adequate. I've heard on this forum somewhere that the next version of the PBP will have a power lead straight from the battery.

[xmixahlx]

the intel 660p shouldn't be drawing too much power, it is one of the lower draw PS0 options at 3.5w max.

reseat the ribbon cable.

[mamboman777]

the intel 660p shouldn't be drawing too much power, it is one of the lower draw PS0 options at 3.5w max.

reseat the ribbon cable.

I have tried reseating the ribbon multiple times. Should I purchase a new adapter kit to replace the ribbon and adapter?

---

It's probably the power coming from the board wasn't adequate.  I've heard on this forum somewhere that the next version of the PBP will have a power lead straight from the battery.

Nvme was functioning properly (for almost a year) prior to the problem. Issue started when I started booting from nvme after completing spiflash. Furthermore, nvme is not found when booting from eMMC or SD.

---

Another piece to the puzzle, boot time is MUCH slower with nvme installed.

[mamboman777]

Update: I tried cleaning the cable with rubbing alcohol, cleaning the board connectors with air, and reseating the cable. Still not working. I'm looking forward to getting my UART cable in so I can see if there's error messages there.

[mamboman777]

Ok...well...apparently the NVME is seen by the system in some sort of capacity.  After reading this thread :https://github.com/clearlinux/distribution/issues/392 I tried lspci -nn and got this readout:

Code:

01:00.0 Non-Volatile memory controller: Intel Corporation SSD 660P Series (rev 03)

So!  The board does know that the drive is there, but somehow can't be bothered to wake it?

[xmixahlx]

what does lsblk say? what is on the drive?

[mamboman777]

what does lsblk say? what is on the drive?

There is currently nothing on the drive.  I reformatted it on another machine last night when testing it.  Output of lsblk:

Code:

mmcblk2      179:0    0  58.2G  0 disk
├─mmcblk2p1  179:1    0 213.6M  0 part /boot
└─mmcblk2p2  179:2    0    58G  0 part /
mmcblk2boot0 179:32   0     4M  1 disk
mmcblk2boot1 179:64   0     4M  1 disk
zram0        252:0    0   5.6G  0 disk [SWAP]

[appelgriebsch]

I’ve the same issue with the Intel 660p. Was using it as my root partition for ca. 1 month without issues. It was still working yesterday evening before I shut it down (suspend is not working with a nvme installed), and after restart this afternoon the OS didn’t came up. So I took a last known working version from microSD and it booted very slowly. At the end it shows me that the nvme isn’t mounted, so I checked dmesg and found this:

Code:

nvme nvme0: Device not ready; aborting initialization, CSTS=0x0
nvme nvme0: Removing after probe failure status: -19

It is also responsible for the long boot time (there is a 30sec delay before those lines are listed).

I already opened the case and checked the cable and nvme connection in the adapter. I also reflashed the latest u-boot to both spi and eMMC, but it shows no success.

Any idea what might be the cause for this problem?

[mamboman777]

I’ve the same issue with the Intel 660p. Was using it as my root partition for ca. 1 month without issues. It was still working yesterday evening before I shut it down (suspend is not working with a nvme installed), and after restart this afternoon the OS didn’t came up. So I took a last known working version from microSD and it booted very slowly. At the end it shows me that the nvme isn’t mounted, so I checked dmesg and found this:

Code:

nvme nvme0: Device not ready; aborting initialization, CSTS=0x0
nvme nvme0: Removing after probe failure status: -19

It is also responsible for the long boot time (there is a 30sec delay before those lines are listed).

I already opened the case and checked the cable and nvme connection in the adapter. I also reflashed the latest u-boot to both spi and eMMC, but it shows no success.

Any idea what might be the cause for this problem?

I do not know what causes this problem, but I know how to get out of it...or at least what works for me.  I do not remember where I got the SPI flash, but I have one that always wakes the drive up.  I suspect the problem is something with the way that the newer U-Boot loads the 660P that makes it get to an un-reachable state, but I can't figure out what causes it to be un-reachable  Maybe something to do with APST? Like I said, I don't really know.  The way I get out of it is boot to the SD card and flash one of the SPI flash's that preceeded the main-line U-Boot SPI flash.  PM me and I can get the file to you.

-Josh