NVMe doesn't show up
#1
Hi, I just got my pinebook pro. Upon playing it a little bit, I installed manjaro i3 on the emmc. And Installed a NVMe but for some reason NVMe doesn't show up. Do I have to somehow enable the NVMe ? (script etc.) It also doesn't show up when I do df -h
When I switch on the pinebook, power led lights up orange for 5 seconds and then turns to green is it normal?
I appreciate if you could help. Thanks in advance.
  Reply
#2
It's a power supply issue.
  Reply
#3
(10-22-2020, 07:19 AM)Samurai_Crow Wrote: It's a power supply issue.
With the nvme ? or the power led ?
  Reply
#4
(10-22-2020, 07:24 AM)Seferi Wrote:
(10-22-2020, 07:19 AM)Samurai_Crow Wrote: It's a power supply issue.
With the nvme ? or the power led ?
With current versions of the laptop and NVMe adapter.
  Reply
#5
[seferi@deep-thought ~]$ sudo journalctl -p 3 -xb
-- Logs begin at Sat 2020-10-03 20:13:07 CEST, end at Thu 2020-10-22 15:29:13 CEST. --
Oct 03 20:13:07 deep-thought kernel: busb Failed to get VBUS supply regulator
Oct 03 20:13:07 deep-thought kernel: busb rockchip_set_vbus_power ret=0
Oct 03 20:13:07 deep-thought kernel: busb Failed to get VBUS supply regulator
Oct 03 20:13:07 deep-thought kernel: busb rockchip_set_vbus_power ret=0
Oct 03 20:13:07 deep-thought kernel: busb rport->port_id=0
Oct 03 20:13:07 deep-thought kernel: busb port power on
Oct 03 20:13:07 deep-thought kernel: busb rport->port_id=1
Oct 03 20:13:07 deep-thought kernel: busb port power on
Oct 03 20:13:07 deep-thought kernel: busb rport->port_id=1
Oct 03 20:13:07 deep-thought kernel: busb port power on
Oct 03 20:13:07 deep-thought kernel: OF: graph: no port node found in /i2c@ff3d0000/fusb30x@22
Oct 03 20:13:07 deep-thought kernel: usb 2-1.2: device descriptor read/64, error -32
Oct 03 20:13:07 deep-thought kernel: rockchip-pcie f8000000.pcie: PCIe link training gen1 timeout!
Oct 03 20:13:07 deep-thought kernel: busb rport->port_id=0
Oct 03 20:13:07 deep-thought kernel: busb port power on
Oct 03 20:13:07 deep-thought kernel: usb 2-1.2: device descriptor read/64, error -32
Oct 03 20:13:07 deep-thought kernel: rockchip-dp ff970000.edp: no DP phy configured
Oct 03 20:13:07 deep-thought kernel: usb 2-1.2: device descriptor read/64, error -32
Oct 03 20:13:07 deep-thought kernel: usb 2-1.2: device descriptor read/64, error -32
Oct 03 20:13:07 deep-thought kernel: usb 2-1.2: device not accepting address 5, error -32
Oct 03 20:13:07 deep-thought kernel: usb 2-1.2: device not accepting address 6, error -32
Oct 03 20:13:07 deep-thought kernel: usb 2-1-port2: unable to enumerate USB device
Oct 22 15:21:02 deep-thought systemd-udevd[419]: event5: Failed to call EVIOCSKEYCODE with scan code 0x70066, and key code 142: Invalid argument
Oct 22 15:21:02 deep-thought systemd-udevd[419]: event5: Failed to call EVIOCSKEYCODE with scan code 0x700a5, and key code 224: Invalid argument
Oct 22 15:21:02 deep-thought systemd-udevd[419]: event5: Failed to call EVIOCSKEYCODE with scan code 0x700a6, and key code 225: Invalid argument
Oct 22 15:21:02 deep-thought systemd-udevd[438]: event3: Failed to call EVIOCSKEYCODE with scan code 0x70066, and key code 142: Invalid argument
Oct 22 15:21:02 deep-thought systemd-udevd[438]: event3: Failed to call EVIOCSKEYCODE with scan code 0x700a5, and key code 224: Invalid argument
Oct 22 15:21:02 deep-thought systemd-udevd[438]: event3: Failed to call EVIOCSKEYCODE with scan code 0x700a6, and key code 225: Invalid argument
Oct 22 15:21:02 deep-thought systemd-udevd[447]: event1: Failed to call EVIOCSKEYCODE with scan code 0x70066, and key code 142: Invalid argument
Oct 22 15:21:02 deep-thought systemd-udevd[447]: event1: Failed to call EVIOCSKEYCODE with scan code 0x700a5, and key code 224: Invalid argument
Oct 22 15:21:02 deep-thought systemd-udevd[447]: event1: Failed to call EVIOCSKEYCODE with scan code 0x700a6, and key code 225: Invalid argument
Oct 22 15:21:02 deep-thought systemd-udevd[440]: event4: Failed to call EVIOCSKEYCODE with scan code 0x70066, and key code 142: Invalid argument
Oct 22 15:21:02 deep-thought systemd-udevd[440]: event4: Failed to call EVIOCSKEYCODE with scan code 0x700a5, and key code 224: Invalid argument
Oct 22 15:21:02 deep-thought systemd-udevd[440]: event4: Failed to call EVIOCSKEYCODE with scan code 0x700a6, and key code 225: Invalid argument
Oct 22 15:21:02 deep-thought systemd-udevd[430]: event2: Failed to call EVIOCSKEYCODE with scan code 0x70066, and key code 142: Invalid argument
Oct 22 15:21:02 deep-thought systemd-udevd[430]: event2: Failed to call EVIOCSKEYCODE with scan code 0x700a5, and key code 224: Invalid argument
Oct 22 15:21:02 deep-thought systemd-udevd[430]: event2: Failed to call EVIOCSKEYCODE with scan code 0x700a6, and key code 225: Invalid argument
Oct 22 15:21:13 deep-thought lightdm[1018]: gkr-pam: unable to locate daemon control file

(10-22-2020, 07:26 AM)Samurai_Crow Wrote:
(10-22-2020, 07:24 AM)Seferi Wrote:
(10-22-2020, 07:19 AM)Samurai_Crow Wrote: It's a power supply issue.
With the nvme ? or the power led ?
With current versions of the laptop and NVMe adapter.
Thanks mate. Is there a fix? What should I do?
  Reply
#6
There isn't a fix yet. If you can't make do with eMMC, you'll have to wait for a new version of the Pinebook Pro and trade up.
  Reply
#7
(10-22-2020, 07:38 AM)Samurai_Crow Wrote: There isn't a fix yet.  If you can't make do with eMMC, you'll have to wait for a new version of the Pinebook Pro and trade up.

Very strange.. If the current version of the pinebook pro and the nvme adapter is incompatible, why do they let people purchase them together..
  Reply
#8
https://forum.pine64.org/showthread.php?tid=10522

At least it didn't crash
And, BTW you are sure it is nvme and NOT sata?
  Reply
#9
(10-22-2020, 08:34 AM)wdt Wrote: https://forum.pine64.org/showthread.php?tid=10522

At least it didn't crash
And, BTW you are sure it is nvme and NOT sata?


Thanks for the reply mate. it's a nvme. I even checked the nvme list on the wiki before I bought the nvme. I got Kingston A2000. Unfortunately I couldn't make it work.
The link you sent, can I make it work with the script?
  Reply
#10
well, you have to do a little experimenting first, the page shows all the commands needed
I would check 1st with the get-feature command
And, if it doesn't work, you could search dmesg,,, dmesg|grep nvme ,, maybe the cable is bad
  Reply


Possibly Related Threads…
Thread Author Replies Views Last Post
  U-Boot with direct NVMe boot support for eMMC/SPI Flash pcm720 117 86,013 05-13-2021, 11:44 AM
Last Post: tophneal
  NVMe SSD and battery life? dieselnutjob 3 478 04-19-2021, 01:55 PM
Last Post: slyecho
  Selling Pinebook Pro 128GB version (w/ NVMe adaptor) due to lack of use VoT 3 924 03-19-2021, 03:11 AM
Last Post: jj282
  Forgot my Pinebook password. Booting from MIcroSD doesn't work. ksfoodforest 0 302 01-30-2021, 11:08 AM
Last Post: ksfoodforest
  [split] U-Boot with NVMe support, keyboard & display working as400 83 31,851 01-27-2021, 12:48 AM
Last Post: as400
  emmc vs NVMe real-world performances Henry 7 2,742 11-15-2020, 02:03 PM
Last Post: rimaille
  Pinebook Pro doesn't boot most of the time unless connected via USB-serial! nib0 16 3,640 09-29-2020, 10:24 PM
Last Post: wdt
  Soft restart doesn't work dgkPBP 9 2,154 09-19-2020, 09:40 AM
Last Post: wdt
  Unable to mount NVME (PineBook Pro) WallStreet 4 2,169 09-13-2020, 11:16 PM
Last Post: Phillip Bell
  Show us them PBPs SteveSquatch 3 1,206 09-08-2020, 04:49 PM
Last Post: SteveSquatch

Forum Jump:


Users browsing this thread: 2 Guest(s)