Also found someone was using the Intel 660p on a NanoPC T4. Looks to be using Armbian? Maybe I’ll give the Armbian WIP for the Rockpi4 a try over the weekend to see if their support is any better.
Tried the Armbian nightly image and I also built an Armbian dev image. Different logs but same results with no /dev/nvme* device being populated. A line from the dmesg from the Armbian images:
rockchip-pcie: probe of f8000000.pcie failed with error -22
I also put this nvme drive into a PC, no issues. After initializing the drive w/ a GPT partition and some testing, I tried reloading rockpi4b-ubuntu-bionic-minimal-20190104_2101-gpt.img and firing up the nvme directly attached and via the extension board. Still doesn’t initialize the drive. This is a quality SSD with a native nvme SMI controller (SM2263). These QLC drives would be a good combination with these devices. Some what of a shame… Seems from the messages I find on other Rockchip boards with PCI-E support, they are flaky as well. Poor PCI-e implementation?
I am sorry for your bad experience. What’s your board’s serial number? The label on the plastic board. Also, are you using the m.2 extend board or directly to the m.2 connector on rock pi 4?
Not all is bad. I had good luck setting up Rancher’s new k3s, though these 1TB NVMe drives was a large part of my project for these boards. I’ve only tried the NVMe drive in two of my three boards I purchased. The serial numbers of these boards are RADXA1903-B0668 and RAXDA1903-B0658. I tried the m.2 extend board as well as directly connecting to the m.2 connector on both boards I previously mentioned. I’m really interested in getting this NVMe model going on these boards. I’m open to helping your support diagnose the issue by providing any logs, trying new images, etc…
The board should be pretty new and it should be no problem. We haven’t actually tested this model 660P but it should also fine since it’s tested on other rk3399 platform. Do you have any other NVMe SSD to test?
I don’t have any clue why it’s not working. Do you have multimeter? If you have, you can measure if the NVMe power is on by measuring the following pad 1 or pad 2. What’s the voltage here?
The voltage is okay. Please test the 970 evo, we have tested 960 evo, it’s working very well. The speed is the fastest on ROCK Pi 4 among all the NVMe we tested.
Received the Samsung 970 EVO Plus 500G Today. Works just fine directly attached or in the m.2 Extension board. So I guess the board just doesn’t like the Intel 660P for whatever reason. I did notice that the Samsung had a tighter connection in the m.2 socket than the Intel 660P for what it’s worth.
That’s interesting, I’m guessing something wrong with the initial link training/handshake process. There have been quite a few updates around this in newer kernels. I tried Armbian’s latest build but didn’t realize until I got those Samsungs I referenced above, NVME isn’t working in their beta images for the RockPi4.
Hi,
i get the same trobble with the 512GB Version of the Intel 660P SSD, but i can´t get it to work.
I test it with my NB and it is working well. I send it back and ordered an Sabrent 256 GB Rocket NVMe PCIe for only 49€ and it works realy good.
Rock Pi 4b 4GB with O635789´s custom Debian image.
hdparm -Tt /dev/nvme0n1
/dev/nvme0n1:
Timing cached reads: 2490 MB in 2.00 seconds = 1245.58 MB/sec
Timing buffered disk reads: 1788 MB in 3.00 seconds = 595.40 MB/sec
/dev/nvme0n1:
Timing cached reads: 2464 MB in 2.00 seconds = 1232.29 MB/sec
Timing buffered disk reads: 1834 MB in 3.00 seconds = 611.12 MB/sec
I’m also in the same position. Got the 512GB Intel 660P SSD.
Linux linaro-alip 4.4.154 #13 SMP Mon Nov 5 18:25:35 CST 2018 aarch64 GNU/Linux
root@linaro-alip:~# dmesg | grep pci
[ 0.258104] of_get_named_gpiod_flags: parsed ‘gpio’ property of node ‘/vcc3v3-pcie-regulator[0]’ - status (0)
[ 0.258151] reg-fixed-voltage vcc3v3-pcie-regulator: Looking up vin-supply from device tree
[ 0.258185] vcc3v3_pcie: supplied by vcc3v3_sys
[ 0.258618] vcc3v3_pcie: at 3300 mV
[ 0.258785] reg-fixed-voltage vcc3v3-pcie-regulator: vcc3v3_pcie supplying 0uV
[ 0.365425] phy phy-pcie-phy.9: Looking up phy-supply from device tree
[ 0.365435] phy phy-pcie-phy.9: Looking up phy-supply property in node /pcie-phy failed
[ 0.366876] rockchip-pcie f8000000.pcie: GPIO lookup for consumer ep
[ 0.366886] rockchip-pcie f8000000.pcie: using device tree for GPIO lookup
[ 0.366914] of_get_named_gpiod_flags: parsed ‘ep-gpios’ property of node ‘/pcie@f8000000[0]’ - status (0)
[ 0.367153] rockchip-pcie f8000000.pcie: Looking up vpcie3v3-supply from device tree
[ 0.367164] rockchip-pcie f8000000.pcie: Looking up vpcie3v3-supply property in node /pcie@f8000000 failed
[ 0.367177] rockchip-pcie f8000000.pcie: no vpcie3v3 regulator found
[ 0.367751] rockchip-pcie f8000000.pcie: Looking up vpcie1v8-supply from device tree
[ 0.367761] rockchip-pcie f8000000.pcie: Looking up vpcie1v8-supply property in node /pcie@f8000000 failed
[ 0.367772] rockchip-pcie f8000000.pcie: no vpcie1v8 regulator found
[ 0.368333] rockchip-pcie f8000000.pcie: Looking up vpcie0v9-supply from device tree
[ 0.368342] rockchip-pcie f8000000.pcie: Looking up vpcie0v9-supply property in node /pcie@f8000000 failed
[ 0.368352] rockchip-pcie f8000000.pcie: no vpcie0v9 regulator found
[ 0.910711] rockchip-pcie f8000000.pcie: PCIe link training gen1 timeout!
[ 0.911433] rockchip-pcie: probe of f8000000.pcie failed with error -110
[ 1.447810] ehci-pci: EHCI PCI platform driver
And I believe I bricked Armbian bootloader
I will investigate today when I get physical access to RockPi
rockpi@rockpi4a:~$ sudo apt-get install rockpi4b-rk-u-boot-latest
Reading package lists... Done
Building dependency tree
Reading state information... Done
rockpi4b-rk-u-boot-latest is already the newest version (2017.09-00011-g0568348).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n] Y
Setting up rockchip-fstab (0.1) ...
sed: -e expression #1, char 0: no previous regular expression
mount all partitions
mount: /etc/fstab: parse error at line 3 -- ignored
mount: mount point vfat does not exist
mount: mount point vfat does not exist
mount: mount point vfat does not exist
dpkg: error processing package rockchip-fstab (--configure):
subprocess installed post-installation script returned error exit status 32
Errors were encountered while processing:
rockchip-fstab
E: Sub-process /usr/bin/dpkg returned an error code (1)
rockpi@rockpi4a:~$ /usr/local/sbin/rockpi4b_upgrade_bootloader.sh
This script requires root.
rockpi@rockpi4a:~$ sudo /usr/local/sbin/rockpi4b_upgrade_bootloader.sh
Doing this will overwrite bootloader stored on your boot device. it might break your system.
If this happens you will have to manually fix that outside of your ROCK Pi 4.
You are currently running on different board:
ROCK PI 4B
It may brick your device or the system unless
you know what are you doing.
Type YES to continue or Ctrl-C to abort.
YES
“Good news everyone” Intel 1TB 660P is Working on cold boot!
But I was switching OSes till I found Ubuntu Server from radxa download.
I hope I’m on way to get it running on armbian ideally with OMV.
And I’m missing sweet speeds of gen2. I hope it be easy to switch to gen2.
Because now i’m on direct read speed like USB3 SSD:
though at the same time I’m sad as I returned my Intel 660p SSDs.