• Several different power supplies.
  
• Fiddling around and reconnecting the drive, adapter board and cable.
  
• Booting from SD-card: Some thread mentioned it would help, but got the same behaviour as described above.
  
• Adding `nvme_core.default_ps_max_latency_us=0` to `/boot/extlinux/extlinux.conf` - no change (see this thread )
  
• Ensuring max_link_speed is 1 in device tree.
  
• Putting the SSD into a USB-adapter - turned up, no problems (on my PBP).
  
• Searching the net. The issue turns up with other notebooks and discs too - but never a proper solution is described.
  

• Are there any new insights into this issue?
  
• Is the Intel 660p really working flawlessly for everyone else but me?
  
• If you ran into these problems with a recent PBP / OS (2022) - what worked for you?
  
• Any information I could provide to solve this?
  

(12-25-2022, 09:42 AM)Sorry to hear about this happening on a brand new pinebook.I believe the components of the pbp are good, but they are not always assembled properly:  I know this because I configured a pinebook pro for myself, my wife, my youngest son, and my oldest son, and they were not all equal; on my eldest sons pbp, many internal connections were not seated properly:  trackpad, wifi, screen -- all had to be reseated and then they functioned.  My youngest son has the oldest of our pbs (so old it came with debian)... and yesterday, out of the blue, it's battery started failing, and would seldom get to above 10% -- this would create nvme errors, because the drive doesn't like low voltage...  it has an adata nvme drive, and I had to use nvme-utils and a startup script to set it's power level feature to "4", which was it's lowest setting (pbp doesn't supply enough power to run nvme at its max power setting).  But when the battery started failing, the nvme0 wouldn't always be recognized during startup.  I verified this by removing the battery, and connecting the battery bypass connectors.  Afterwords, nvme0 detected again, and he's back in the saddle, but we plug his pbp into ups, so it can survive the occasional power flickers in the grid that occur during storms...  However, a brand new pbp should still have a good battery.  You may need to send it back.IMHO, too many assembly line MISTAKES  are swept under the rug with Pine64's rhetoric about, since they target developers, we shouldn't complain about dead pixels and other defects.  I could care less about a dead pixel in my screen, and wouldn't complain.  But they ought to arrive new out of the box:  working -- and many do not.  Starbug Wrote: Hi all,

Put together my new PBP (running Manjaro / XFCE, u-boot is 2022.04-4), NVME-adapter and an Intel 660p 1TB SSD. Drive turned up, partitioning and formatting went fine, started copying data - and suddenly the drive vanished. Was running out of battery (maybe that caused the drive to vanish?), fiddled around some days, connected the original power adapter, drive turned up again.

The second time I wasn't that lucky. Copied data, turned the PBP off - and after starting it again, the drive didn't turn up anymore. Basically I have the same problem as described here . But the solution mentioned (flashing a certain boot loader into SPI), doesn't work for me. As the thread is already 2 years old - has anyone run into this problem recently?

`lspci` lists the controller:

Code:

# lspci
00:00.0 PCI bridge: Rockchip Electronics Co., Ltd RK3399 PCI Express Root Port
01:00.0 Non-Volatile memory controller: Intel Corporation SSD 660P Series (rev 03)

but `lsblk` doesn't show the disc (and fdisk et al don't show either):

Code:

# lsblk
NAME          MAJ:MIN RM  SIZE RO TYPE  MOUNTPOINTS
sda              8:0    1    0B  0 disk 
mmcblk2        179:0    0  58.2G  0 disk 
├─mmcblk2p1    179:1    0 457.8M  0 part  /boot
└─mmcblk2p2    179:2    0  57.8G  0 part 
  └─ROOT_MNJRO 254:0    0  57.7G  0 crypt /
mmcblk2boot0  179:32  0    4M  1 disk 
mmcblk2boot1  179:64  0    4M  1 disk 
zram0          253:0    0  5.7G  0 disk  [SWAP]´´´

`dmesg | grep nvme` shows:

Code:

# dmesg | grep nvme
[    0.000000] Kernel command line: initrd=/initramfs-linux.img console=tty1 cryptdevice=UUID=2ed9afcd-16a1-4874-8d0a-0189002f1f5c:ROOT_MNJRO root=/dev/mapper/ROOT_MNJRO rw rootwait nvme_core.default_ps_max_latency_us=0
[    1.892832] nvme nvme0: pci function 0000:01:00.0
[    1.892966] nvme 0000:01:00.0: enabling device (0000 -> 0002)
[  62.399487] nvme nvme0: Device not ready; aborting initialisation, CSTS=0x0
[  62.399526] nvme nvme0: Removing after probe failure status: -19

After doing

Code:

echo 1 > /sys/bus/pci/devices/0000:01:00.0/remove; echo 1 > /sys/bus/pci/devices/0000:00:00.0/rescan

`/dev/nvme0` turns up for a minute, but every nvmi-cli-command returns `/dev/nvme0: Resource temporarily unavailable`


What did I try?

• Several different power supplies.
  
• Fiddling around and reconnecting the drive, adapter board and cable.
  
• Booting from SD-card: Some thread mentioned it would help, but got the same behaviour as described above.
  
• Adding `nvme_core.default_ps_max_latency_us=0` to `/boot/extlinux/extlinux.conf` - no change (see this thread )
  
• Ensuring max_link_speed is 1 in device tree.
  
• Putting the SSD into a USB-adapter - turned up, no problems (on my PBP).
  
• Searching the net. The issue turns up with other notebooks and discs too - but never a proper solution is described.
  

As the mentioned thread is already 2 years old:

• Are there any new insights into this issue?
  
• Is the Intel 660p really working flawlessly for everyone else but me?
  
• If you ran into these problems with a recent PBP / OS (2022) - what worked for you?
  
• Any information I could provide to solve this?
  

Any help / hint appreciated.