X1003

From Geekworm Wiki
Jump to navigation Jump to search

X1003 V1.3
X1003 V1.3
Take care the FPC direction to yellow FPC cable
X1003 V1.3 front view
X1003 V1.3 rear view
X1003 V1.3: supports official raspberry pi 5 case
X1003 V1.3: supports official raspberry pi 5 case
Raspberry pi 5 official ABS case
Installation Guide
Dimensions source file


Overview

The X1003 is a PCIE to NVME expansion board designed to support the official Raspberry Pi 5 abs case, it is very compact in size and only supports NVME ssd's of the 2230/2242 specification, but it is compatible with the Raspberry Pi 5 active cooler as well as the official red and white enclosure, but in order to install the X1003 you will need to remove the fan layer on the top of the enclosure.

This shield follows the new "PIP" design guideline from Raspberry Pi fundation ensuring that it will be easy to use and be supported long term by updates to Raspberry Pi OS - though it is very early days and things are improving rapidly there!

Geekworm PCIe to NVME Sets:

After the release of the Raspberry Pi AI Kit, we tested four PIPs: X1001, X1004, X1011, and M901. X1001, X1004, and M901 all support the hailo-8 ai ​​accelerator, but X1011 does not.

It should be noted that X1004 uses ASMedia ASM1182e PCIe switch, it can't support PCIe Gen 3 speed, so even though we forced to enable PCIe Gen 3.0 setting in Raspberry Pi 5, it is limited by ASMedia ASM1182e PCIe switch, and speed is still PCIe Gen 2.0 5Gbps speed. when you use an hailo-8 ai accelerator, Raspberry Pi Fundation highly recommends using PCIe 3.0 to achieve best performance with your AI Kit.

Our tentative conclusions are as follows:

  • If you need to use hailo-8 ai accelerator with high performance, it is recommended to use X1015/X1002/X1003/M901/ the official M.2 HAT+ etc. When choosing these PIP boards, you should focus on whether there is a conflict between the camera cable and the PIP board installation, and enable PCIe3.0 to use hailo-8 ai accelerator. At the same time, you need to prepare an SD card as the system disk.
  • If you don't care about the high performance brought by PCIe 3.0, then you can consider using X1004, so that you can use any socket of X1004 to install NVME SSD as the system disk, and another socket to install hailo-8 ai accelerator, so as to have both.
Model Compatible with Position NVMe M2 SSD Length Support Matching Case Matching Cooler Support NVMe Boot Support PCIe 3.0 Support Hailo-8 AI Accelerator
X1000 Raspberry Pi 5 Top 2230/2242 P579 Official Cooler / Argon THRML Cooler / H505/H501 Yes - Not tested
X1001 Raspberry Pi 5 Top 2230/2242/2260/2280 P579 Official Cooler / Argon THRML Cooler / H505/H501 Yes - Yes
X1002 Raspberry Pi 5 Bottom 2230/2242/2260/2280 P580 Official Cooler / Argon THRML Cooler / H505/H501 Yes - Not tested
X1003 Raspberry Pi 5 Top 2230/2242 P579 / P425 Official Cooler / H501 Only Yes - Not tested
X1004 Raspberry Pi 5 Top Dual ssd: 2280 P579-V2 Official Cooler / Argon THRML Cooler / H505/H501 Yes (Requires EEPROM 2024/05/17 version and above) NO Yes
X1015 Raspberry Pi 5 Top 2230/2242/2260/2280 P579 Official Cooler / Argon THRML Cooler / H505/H501 Yes - Yes
X1005 Raspberry Pi 5 Bottom Dual ssd: 2230/2242/2260/2280 No matching case yet Official Cooler / Argon THRML Cooler / H505/H501 Yes (Requires EEPROM 2024/05/17 version and above) NO Yes
X1011 Raspberry Pi 5 Bottom 4 ssds: 2230/2242/2260/2280 X1011-C1 Official Cooler / Argon THRML Cooler / H505/H501 Yes (eeprom 2024/05/17 and later VER) NO NO
M901 Raspberry Pi 5 Top 2230/2242/2260/2280 P579 Official Cooler / Argon THRML Cooler / H505/H501 Yes - Yes
Q100 Raspberry Pi 5 Top 2242 P579 Official Cooler / Argon THRML Cooler / H505/H501 Yes - Not tested
Q200 Raspberry Pi 5 Top Dual ssd: 2280 P579 Official Cooler / Argon THRML Cooler / H505/H501 NO - Not tested
M300 Raspberry Pi 5 Top 2230/2242 P579 Official Cooler / Argon THRML Cooler / H505/H501 Yes - Not tested
M400 Raspberry Pi 5 Top 2230/2242/2280 P579 Official Cooler/ Argon THRML Cooler / H505/H501 Yes - Not tested

Important Notes

NVMe SSD Incompatibility List

We recommend avoiding the following NVMe SSD drives which is equipped with a Phison controller due to their proven incompatibility:

These specific models have demonstrated compatibility issues, and it is advisable to avoid them when considering NVMe SSD options for the X10xx series NVMe shield. You can run "lspci" command to check the controller brand of the SSD.

Also note:

  • Compatible with M.2 NVMe SSDs only, Not compatible with M.2 SATA SSDs, M.2 PCIe AHCI SSDs, or other M.2 non-NVMe devices
  • Older NVMe drives with less efficient flash media may not perform as well as newer drives
  • New NVMe SSDs are not partitioned and will need to be both partitioned and formatted when first connected to the Raspberry Pi before they will be accessed in the Explorer.
  • We get feedback from customers that Polaris Controller will also have compatibility problems. Please replace the other SSD test if it not work, whether it is compatible with the Raspberry Pi 5 does not depend on the X100X series boards
  • NVMEs using the MAP1202 controller may not support PCIe Gen 2, and must be forced to enable PCIe Gen 3 in order to be recognised. This is due to the fact that the controller is not backward compatible with PCIe Gen 2, and NVMEs using this controller will have compatibility issues, and are not recommended for use. Can refer to https://zhuanlan.zhihu.com/p/644984347


PS: There is also feedback from buyers that even NVME SSDs with Phison controller are supported after updating the latest firmware. Please refer to go to: X1001#comment-4638

Features

  • Compatible with Raspberry Pi 5 Active Cooler and Raspberry pi 5 official case;
  • FFC is only 22mm length.
  • With M.2 disk activity (“ACT”) LED; On: Power OK/Standby,Flashing: Reading/Writing
  • Supports 2230/2242 NVME M2 SSD only.
  • Supports additional GPIO power supply in addition to FPC power supply

Packing List

  • 1 x X1003 V1.3 NVMe SSD Shield
  • 1 x PCIe FFC cable(22mm length)
  • 1 x M2x13mm screw (fix x1003 shield to official Active cooler)
  • 1 x M2x4mm Screws (to fix MVME M2 SSD)

X1003-IMG-7424-packing-list.jpg

Installation Guide

X1003-installation-1.jpg

User Manual

Video Guide

Installation Video of X1003 https://youtu.be/RY-71-xsQ0Q

X1003 Test Video by leepsvideo https://youtu.be/RvcwV3YlNPI

Which NVMe drives work with a Raspberry Pi 5? https://youtu.be/3mUgVTBmKio

FAQ

Overview

In fact, some PIPs such as X1001 / X1002 / X1003 / X1000 etc are just an extension of the Raspberry Pi 5 PCIe, and their own hardware functions are limited. If the OS configuration and PCle FFC cable faults can be ruled out, the normal operation of PCIe (recognizing and booting) depends more on the firmware and SSD compatibility. Since October 2023, the Raspberry Pi Foundation has been updating the bootloader version to solve similar problems. You can learn more from the link below.

Raspberry Pi5 bootloader EEPROM release notes

But in fact, after several major version updates, the bootloader has basically solved the firmware issue, so the remaining is the OS configuration and SSD compatibility issues.

If you are using a very old SSD, if you are experiencing issues with it being recognised and not being able to boot, the first thing you should consider is replacing the NVME SSD.

Q1: Can't boot/recognize from NVMe SSD?

click it to zoom out

A: Here are a few steps to help you troubleshoot some issues:

  1. Only Raspberry Pi OS (Bookworm) supports PCIe, Raspberry Pi OS bullseye is NOT supported, refer to https://www.raspberrypi.com/software/operating-systems/
  2. Make sure that your OS configuration (/boot/firmware/config.txt) is completely correct: refer to the tutorial:NVMe SSD boot with the Raspberry Pi 5 (will Continuously updating)
  3. Update the bootloader firmware to the last verson, refer to How to update eeprom firmware, this is very important!!! Make sure your upgrade is successful by running command vcgencmd bootloader_version
  4. Add PCIE_PROBE=1 to the eeprom, (Run sudo rpi-eeprom-config --edit command, then add this line, then press CTRL+O to write change to file, press CTRL+X to exit, then reboot)
  5. Make sure the SSD type you use is correct, only support M.2 NVME (Sata) Key-M SSD NOT support M.2 NGFF Key-B SSD. Refer to the right diagram:
  6. Make sure the FPC cable is firmly and fully inserted into the PI 5, this is very important. For X1003 shield, make sure the FPC cable direction is correct also.
  7. For some small brand SSD, consider forcing open PCIe Gen3 to test (add dtparam=pciex1_gen=3 line in config.txt then reboot), because some small brand SSDs are NOT backward compatible with PCIe Gen 2 for cost reasons.
  8. For X1003 shield, make sure the FPC cable direction is correct also. If an error still occurs, replace the FFC cable to test or purchase other PFC from here[1]to troubleshoot the issue.
  9. Read this post to get some help;
  10. Although you can also boot from a SD card, Pi OS is required for the NVMe SSD to boot, DON'T forget Flash OS into NVMe SSD.
  11. If you're flashing a fresh Pi OS into NVME SSD , DON'T forget to ENABLE PCIe to NVME SSD.
  12. Run the lspci andlsblk command to check the NVMe SSD is recognized. (NOTE: Make sure your NVMe SSD is plugged into the PCIe PIP, not just connecting PCIe PIP to the Pi5, otherwise the lspci will not be able to display any PCIe device.)
  13. Start thinking about SSD compatibility issues and try to switch to other brands of NVME SSDs. Some customers have reported that they have successfully solved their problems by replacing their SSDs.
  14. Contact us at email: support@geekworm.com, and attached your product model, OS version (run uname -a to get), bootloader version (run vcgencmd bootloader_version to get) and order number
  • How to get FPC Wires:
  • PS: The shortest length of the FPC cable here is 30mm, but the length of the FPC cable used by X1003 is only 22mm. For X1003, this may not be perfect, but you can use these FPC cables to troubleshoot the issue. DON'T buy it if you mind.
  • If the issue is confirmed to be a FFC cable, we will reimburse you the cost of purchasing the FFC cable.

Q2: Don't recognize / boot from NVME SSD?

A: If you have enabled pcie and find that you still cannot boot from NVME SSD, please perform the following actions

1. Follow the picture below to check the version of X1001 or X1000

X1001-V1.1-IMG-6871-old-new.jpg

2. If it is an Old Version, refer to How to update eeprom firmware to update the firmware with pieeprom-2023-10-30.bin file.

3. If it is an New Version, refer to How to update eeprom firmware to update the firmware to lasted version.

4. If you still have not solved the problem, please refer to the next FAQ:Q1

Q3: How to fix the 2230/2242/2260 SSD on X1001 or other PIP?

A: The X1001 and other pips does not reserve the nut column to fix the 2230/2242/2260 SSD. Based on our test, you can secure the 2230/2242/2260 SSD using an M2*6mm screw and 2pcs M2 nuts. Place one M2 nut under the SSD, then use the M2*6mm screw and the other M2 nut to fasten the SSD.

PS: As of April 2024, we have added customized copper pillar in only X1001 packing list to solve this issue, please refer to the packing list of X1001.

Q4. X1002 can't boot when install into the P580 case?

A: Please check if the FPC cable touch the metal case make shorting when install X1002 into the metal case, you can stick the electrical tape on the case to prevent the ribbon FPC cable from contacting the case to test.

Q5: Which NVMe drives work with a Raspberry Pi 5?

A: You can refer to the video: https://youtu.be/3mUgVTBmKio.

Q6: Can they support gen3 PCIe speeds or only gen2?

A:

  • All PIPs (such X1001, X1002, X1003 etc) are just an extension of the Raspberry Pi 5 PCIe interface. Apart from whether the chip on the PIP board supports PCIe 3.0 or not, the more main focus is on the Raspberry Pi 5.
  • X1004, X1011, X1005 PIP boards do not support PCIe Gen 3 speed.
Add your comment
Geekworm Wiki welcomes all comments. If you do not want to be anonymous, register or log in. It is free.


Anonymous user #21

28 days ago
Score 0++
Working well for me, after installing the PCIE cable the wrong way round initially. Using an "SkHynix 256GB PCIe NVMe 2242 SSD (HFM256GD3HX015N) (OEM)" off Amazon. lspci says "0000:01:00.0 Non-Volatile memory controller: SK hynix Gold P31/PC711 NVMe Solid State Drive"

Anonymous user #20

one month ago
Score 0++
How do i activate the additional GPIO power supply in addition to FPC power supply that should be supported? I read that this could be the problem for some SSDs to not work properly.

Anonymous user #20

one month ago
Score 0++
because it delivers not enough power through the FPC alone

Lisa

29 days ago
Score 0++
Hi,X1003 does not have a 5V IN interface. If your board does not boot/recognize from SSD, please refer to the instructions in X1003#FAQ to troubleshoot the problem. Most non-recognition problems can be solved.

Anonymous user #20

one month ago
Score 0++

Any additional confirmed success with 2242 SSDs? Is there a list? Sadly also a lot of SSDs in the comments I can't order in my country. Like the Samsung or Micron

Looks like my KingSpec NXM-2242 256GB M.2 NVMe SSD is not working properly. (waiting for answer of support if there is a solution)

Anonymous user #19

one month ago
Score 0++
I tried with integral m2 NVMe gen3 x4 2230 and it does not work, but I do not know why. When the x1003 has the m2 connected no led is turned on. Only after I connect the PSU it blink a led from the m2 (not the x1003). If I disconnect the m2 and connect the PSU I can see 2 blue leds of the board. Then what is happening here? no led from the board means no power? I can't get the m2 recognized in the rpi5. Is the board fault? is the ssd? I need help with this.

Lisa

one month ago
Score 0++
Hi,Please refer here to test it X1003#FAQ and troubleshoot the problem. make sure the FPC cable is firmly and fully inserted into the PI 5, FPC cable direction is correct. Please be sure to upgrade to the latest version of firmware. If the problem is still not solved, please try to replace the FFC cable and test it.

Anonymous user #19

one month ago
Score 0++
I followed all the guides and there is no way to get it recognized by my rpi. Also the FPC is correctly connected. How is supposed that the FPC can be broken? and for me does not make sense to buy a new FPC

Lisa

one month ago
Score 0++
If it is a pre-update cable (yellow color), there may be a problem of not recognizing it. Please contact us by email [support@geekworm.com] and we will provide you with a new FPC cable.

Anonymous user #18

one month ago
Score 0++
Micron 250GB 2242 MTFDKCD256TFK worked for me with the X1003 after updating eeprom.

Anonymous user #17

2 months ago
Score 0++
Samsung PM991 does now work. You should update that in your page. I have a PM991 running right now. Key is you need to run rpi-eeprom-update -a and if you're running ubuntu you need to flash a sd drive with raspberry pi os and do the rpi-eeprom-update because ubuntu has not pushed the latest eeprom files. Once you do that you will be able to copy your ubuntu os or whatever you want. Works great.

Anonymous user #15

3 months ago
Score 0++

Anyone knows if Foresee E2M2 064G (SteamDeck original ssd nvme 2230) works with this model?

thanks

Anonymous user #14

3 months ago
Score 0++

You people are interesting GeekWorms. It would add .05 to 10 cents to add the ability to put the small nvme screw into eithe the 2242 or 2230 holes on the x 1003 device. Why not place the glued in washer in both holes. Just a thought since these tiny washers are hard to locate.

Just saying!

Anonymous user #13

3 months ago
Score 0++

dmesg shows:

[ 0.394368] brcm-pcie 1000110000.pcie: host bridge /axi/pcie@110000 ranges: [ 0.394376] brcm-pcie 1000110000.pcie: No bus range found for /axi/pcie@110000, using [bus 00-ff] [ 0.394387] brcm-pcie 1000110000.pcie: MEM 0x1b00000000..0x1bfffffffb -> 0x0000000000 [ 0.394392] brcm-pcie 1000110000.pcie: MEM 0x1800000000..0x1affffffff -> 0x0400000000 [ 0.394398] brcm-pcie 1000110000.pcie: IB MEM 0x0000000000..0x0fffffffff -> 0x1000000000 [ 0.395575] brcm-pcie 1000110000.pcie: setting SCB_ACCESS_EN, READ_UR_MODE, MAX_BURST_SIZE [ 0.395581] brcm-pcie 1000110000.pcie: Forcing gen 2 [ 0.395618] brcm-pcie 1000110000.pcie: PCI host bridge to bus 0000:00 [ 0.395620] pci_bus 0000:00: root bus resource [bus 00-ff] [ 0.395624] pci_bus 0000:00: root bus resource [mem 0x1b00000000-0x1bfffffffb] (bus address [0x00000000-0xfffffffb]) [ 0.395627] pci_bus 0000:00: root bus resource [mem 0x1800000000-0x1affffffff pref] (bus address [0x400000000-0x6ffffffff]) [ 0.395638] pci 0000:00:00.0: [14e4:2712] type 01 class 0x060400 [ 0.395665] pci 0000:00:00.0: PME# supported from D0 D3hot [ 0.396636] pci 0000:00:00.0: bridge configuration invalid ([bus 00-00]), reconfiguring [ 0.823818] brcm-pcie 1000110000.pcie: link down [ 0.828504] pci_bus 0000:01: busn_res: [bus 01-ff] end is updated to 01 [ 0.828512] pci 0000:00:00.0: PCI bridge to [bus 01] [ 0.828518] pci 0000:00:00.0: Max Payload Size set to 512/ 512 (was 128), Max Read Rq 512 [ 0.828618] pcieport 0000:00:00.0: PME: Signaling with IRQ 38 [ 0.828679] pcieport 0000:00:00.0: AER: enabled with IRQ 38 [ 0.828781] pci_bus 0000:01: busn_res: [bus 01] is released [ 0.828832] pci_bus 0000:00: busn_res: [bus 00-ff] is released [ 0.828956] brcm-pcie 1000120000.pcie: host bridge /axi/pcie@120000 ranges: [ 0.828960] brcm-pcie 1000120000.pcie: No bus range found for /axi/pcie@120000, using [bus 00-ff] [ 0.828969] brcm-pcie 1000120000.pcie: MEM 0x1f00000000..0x1ffffffffb -> 0x0000000000 [ 0.828974] brcm-pcie 1000120000.pcie: MEM 0x1c00000000..0x1effffffff -> 0x0400000000 [ 0.828982] brcm-pcie 1000120000.pcie: IB MEM 0x1f00000000..0x1f003fffff -> 0x0000000000 [ 0.828986] brcm-pcie 1000120000.pcie: IB MEM 0x0000000000..0x0fffffffff -> 0x1000000000 [ 0.830155] brcm-pcie 1000120000.pcie: setting SCB_ACCESS_EN, READ_UR_MODE, MAX_BURST_SIZE [ 0.830163] brcm-pcie 1000120000.pcie: Forcing gen 2 [ 0.830193] brcm-pcie 1000120000.pcie: PCI host bridge to bus 0001:00 [ 0.830196] pci_bus 0001:00: root bus resource [bus 00-ff] [ 0.830199] pci_bus 0001:00: root bus resource [mem 0x1f00000000-0x1ffffffffb] (bus address [0x00000000-0xfffffffb]) [ 0.830202] pci_bus 0001:00: root bus resource [mem 0x1c00000000-0x1effffffff pref] (bus address [0x400000000-0x6ffffffff]) [ 0.830211] pci 0001:00:00.0: [14e4:2712] type 01 class 0x060400 [ 0.830233] pci 0001:00:00.0: PME# supported from D0 D3hot [ 0.831076] pci 0001:00:00.0: bridge configuration invalid ([bus 00-00]), reconfiguring [ 0.935820] brcm-pcie 1000120000.pcie: link up, 5.0 GT/s PCIe x4 (!SSC) [ 0.935839] pci 0001:01:00.0: [1de4:0001] type 00 class 0x020000 [ 0.935853] pci 0001:01:00.0: reg 0x10: [mem 0xffffc000-0xffffffff] [ 0.935861] pci 0001:01:00.0: reg 0x14: [mem 0xffc00000-0xffffffff] [ 0.935868] pci 0001:01:00.0: reg 0x18: [mem 0xffff0000-0xffffffff] [ 0.935938] pci 0001:01:00.0: supports D1 [ 0.935940] pci 0001:01:00.0: PME# supported from D0 D1 D3hot D3cold [ 0.947828] pci_bus 0001:01: busn_res: [bus 01-ff] end is updated to 01 [ 0.947836] pci 0001:00:00.0: BAR 8: assigned [mem 0x1f00000000-0x1f005fffff] [ 0.947840] pci 0001:01:00.0: BAR 1: assigned [mem 0x1f00000000-0x1f003fffff] [ 0.947845] pci 0001:01:00.0: BAR 2: assigned [mem 0x1f00400000-0x1f0040ffff] [ 0.947850] pci 0001:01:00.0: BAR 0: assigned [mem 0x1f00410000-0x1f00413fff] [ 0.947855] pci 0001:00:00.0: PCI bridge to [bus 01] [ 0.947858] pci 0001:00:00.0: bridge window [mem 0x1f00000000-0x1f005fffff] [ 0.947862] pci 0001:00:00.0: Max Payload Size set to 256/ 512 (was 128), Max Read Rq 512 [ 0.947871] pci 0001:01:00.0: Max Payload Size set to 256/ 256 (was 128), Max Read Rq 512 [ 0.947923] pcieport 0001:00:00.0: enabling device (0000 -> 0002) [ 0.947952] pcieport 0001:00:00.0: PME: Signaling with IRQ 39 [ 0.948001] pcieport 0001:00:00.0: AER: enabled with IRQ 39

[ 0.948071] rp1 0001:01:00.0: bar0 len 0x4000, start 0x1f00410000, end 0x1f00413fff, flags, 0x40200

Lisa

3 months ago
Score 0++
Hi,It's hard to see what's wrong here. Please send screenshot via email[support@geekworm.com]. And tell us your order number. Thanks

Anonymous user #13

3 months ago
Score 0++

The lspci brings this answer:

0001:00:00.0 PCI bridge: Broadcom Inc. and subsidiaries Device 2712 (rev 21)

0001:01:00.0 Ethernet controller: Device 1de4:0001

Lisa

3 months ago
Score 0++

Hi,You can check the SSD controller through lspci, Not compatible with Phison controller. If the SSD is not recognized, please follow these steps to troubleshoot the problemNVMe SSD boot with the Raspberry Pi 5#FAQ

Or contact us at email: support@geekworm.com

Anonymous user #13

3 months ago
Score 0++
I have a KingSpec M.2 NVMe mounted and it does not show up with lsblk. The blue light is on. How can i check what the problem is?

Lisa

3 months ago
Score 0++
Hi,You can run "lspci" command to check the controller brand of the SSD, Not compatible with Phison controller. If the SSD is not recognized, please follow these steps to troubleshoot the problem NVMe SSD boot with the Raspberry Pi 5#FAQ Or contact us at email: support@geekworm.com

Anonymous user #12

4 months ago
Score 0++
Using a solidigm P41 plus 2230 1TB drive. Typing this comment with it as the boot drive on my Raspberry Pi 5. Followed directions on the wiki here. Had to reboot twice before it worked. Very fast.

Anonymous user #3

4 months ago
Score 0++

Got my X1003 working with my rpi5 using a "with a 512GB Inland TN436 NVMe M.2 Gen 4x4 SSD", and cloned the boot microSD to it using my Gerling's rpi-clone script.

The RPI5 doesn't want to boot from the NVMe even tho the 6 was added to the boot order line in the eeprom and the PCIE_PROBE=1 is in ther.

Anonymous user #3

4 months ago
Score 0++

UPDATE!!

RETURNED the KINGSPEC nvme. It was making it so that the X1003 had NO LIGHTS illuminated.

Replaced it with a 512GB Inland TN436 NVMe M.2 Gen 4x4 SSD from amazon [WORKS even tho it has Phison E19 controller]. It arrived today, i put it in the X1003 and i had lights. I added the 6 to the end of the boot order in the eeprom. Device showed up. I ran the rpi-clone script (geerling's from his git). It went through all the glorious cloning motions.

Now i'm just working on getting the rpi5 to boot from it.

  1. lspci

0000:00:00.0 PCI bridge: Broadcom Inc. and subsidiaries Device 2712 (rev 21) 0000:01:00.0 Non-Volatile memory controller: Phison Electronics Corporation PS5019-E19 PCIe4 NVMe Controller (DRAM-less) (rev 01) 0001:00:00.0 PCI bridge: Broadcom Inc. and subsidiaries

NOTICE the Phison controller WORKING with this NVMe! E19

Anonymous user #11

4 months ago
Score 0++
CL1-3D128-Q11 NVMe SSSTC 128GB is working great, although it is small. Never seen a pi run so fast.

Anonymous user #9

4 months ago
Score 0++
Works well with SSD SK Hynix BC711 512go 2242

Anonymous user #3

4 months ago
Score 0++
Which Phison controller is the problem? E21 or E13? Or BOTH??

Anonymous user #3

4 months ago
Score 0++
does NOT work with KINGSPEC NX 2230 512GB -- this PCIe m-keyed m.2 nvme makes the lights on the X1003 go out.

Anonymous user #10

4 months ago
Score 0++

Yo he probado con un KingSpec M.2 NVMe 512 GB 2242 y reconoce la unidad, las luces permanecen encendidas, copia la SD al SSD sin problemas, pero luego no arranca desde el PCIe.

¿alguna solución?

Anonymous user #8

4 months ago
Score 0++

Transcend MTE400S 1 TB NVMe PCIe Gen3 x4 M.2 2242 (TS1TMTE400S) seems not to be compatible. First installation tests succsessfully. Image copy worked, but lot of error messages while booting. Raspi freezes after boot.

Booting with an usb nvme-adapter was successfull. No errors.

Anonymous user #16

2 months ago
Score 0++

Hi, I confirm that Transcend PCIe SSD Gen3 x4 with MTE400S controller (I have with the 256Gb version), didnt't work. First of all, you have to push dtparam=pciex1_gen=3 in the config.txt configuration file. All other value (as dtparam=pciex1 or dtparam=pciex1_gen=2) can works, but with a very slow boot, a very slow login, and all commands are also very slow (it can takes several minutes !). In second hand, if you can boot and play with your RPi5, I always experienced an I/O error with this SSD after 5', 1 hour, or 3 hours. It depends (of what ?) but at the end, the only way is to reboot your RPi5 to start again.

Also for me, this behavior is not acceptable with a system which is supposed to run 24/7....

Lisa

2 months ago
Score 0++

Hello,@Anonymous user #17 ;please refer to NVMe SSD boot with the Raspberry Pi 5#FAQ and Try the following test it: 1/Run the lspci andlsblk command to check the NVMe SSD is recognized. 2/Add PCIE_PROBE=1 to the eeprom, (Run sudo rpi-eeprom-config --edit command, then add this line, then press CTRL+O to write change to file, press CTRL+X to exit, then reboot) 3/Update the bootloader firmware to the last verson, refer to How to update eeprom firmware, this is very important!!!And finally be sure to run the command vcgencmd bootloader_version to check if your upgrade was successful!

4/replace the FFC cable to test.

Anonymous user #7

4 months ago
Score 0++

Samsung SSD 256GB PM991 M.2 2242 42mm PCIe 3.0 x4 NVMe MZALQ256HAJD MZ-ALQ2560 Solid State Drive PCIE 2

Category Test Result HDParm Disk Read 419.51 MB/sec HDParm Cached Disk Read 412.94 MB/sec DD Disk Write 284 MB/s FIO 4k random read 106113 IOPS (424455 KB/s) FIO 4k random write 79379 IOPS (317519 KB/s) IOZone 4k read 183492 KB/s IOZone 4k write 144399 KB/s IOZone 4k random read 57374 KB/s IOZone 4k random write 156830 KB/s

Score: 36347

PCIE 3

Category Test Result HDParm Disk Read 803.88 MB/sec HDParm Cached Disk Read 746.26 MB/sec DD Disk Write 391 MB/s FIO 4k random read 140273 IOPS (561095 KB/s) FIO 4k random write 81269 IOPS (325079 KB/s) IOZone 4k read 228398 KB/s IOZone 4k write 174821 KB/s IOZone 4k random read 62406 KB/s IOZone 4k random write 196858 KB/s

Score: 43955

Anonymous user #7

4 months ago
Score 0++
Samsung SSD 256GB PM991 M.2 2242 42mm PCIe 3.0 x4 NVMe MZALQ256HAJD MZ-ALQ2560 Solid State Drive also works

Anonymous user #6

4 months ago
Score 0++
what do the leds mean? i have 2 blue ones, but i cant see the nvme

Anonymous user #6

4 months ago
Score 0++
Can you suggest a compatible m2? apparently the one that i bought is not compatible.

Walker

4 months ago
Score 0++
Lexar Play 1TB NVME or HV2000 NVME SSD

Anonymous user #5

4 months ago
Score 0++

With Corsair M600 1TB:

nvme0n1 showed up in my lsblk, but with a size of 1 MB. Doesn't appear to be compatible. I see now that it has a Phison E21T controller, along with almost every other SSD I can find.

I'll try the Lexar Play 1TB the other commenter successfully used.

Anonymous user #5

4 months ago
Score 0++

Lexar SSD Play 1TB showed up, successfully configured as the only disk and booted from it.

Using test script from "Benchmark ssd on linux: How to measure the same things as crystaldiskmark does in windows" on Unix StackExchange.

Results:

Sequential Q32T1 Read: 407MB/s [ 12 IOPS] Sequential Q32T1 Write: 407MB/s [ 12 IOPS]

4KB Q8T8 Read: 397MB/s [ 99319 IOPS] 4KB Q8T8 Write: 394MB/s [ 98554 IOPS]

4KB Q32T1 Read: 392MB/s [ 98225 IOPS] 4KB Q32T1 Write: 367MB/s [ 91838 IOPS]

4KB Read: 62MB/s [ 15675 IOPS]

4KB Write: 154MB/s [ 38605 IOPS]

Anonymous user #2

4 months ago
Score 0++

With Lexar Play 1TB NVME m.2 2230 ssd:

Raspberry Pi Diagnostics - version 0.13 Tue Jan 30 22:11:17 2024

Test : SD Card Speed Test Run 1 prepare-file;0;0;720175;1406 seq-write;0;0;753287;1471 rand-4k-write;0;0;520126;130031 rand-4k-read;263196;65799;0;0 Sequential write speed 753287 KB/sec (target 10000) - PASS Random write speed 130031 IOPS (target 500) - PASS Random read speed 65799 IOPS (target 1500) - PASS

Test PASS

Anonymous user #2

4 months ago
Score 0++

Using a RPI 5 with Geekworm X1003 and a Lexar Play 1TB NVME m.2 SSD

Raspberry Pi Diagnostics - version 0.13 Tue Jan 30 22:11:17 2024


Test : SD Card Speed Test

Run 1

prepare-file;0;0;720175;1406

seq-write;0;0;753287;1471

rand-4k-write;0;0;520126;130031

rand-4k-read;263196;65799;0;0

Sequential write speed 753287 KB/sec (target 10000) - PASS

Random write speed 130031 IOPS (target 500) - PASS

Random read speed 65799 IOPS (target 1500) - PASS

Test PASS

Anonymous user #4

4 months ago
Score 0++
Can you tell us which SSDs you have confirmed to be working properly?

Walker

4 months ago
Score 0++
Hi, according to buyer feedback, the Lexar Play M.2 2230 NVMe 1TB SSD is compatible with the X1003

Walker

4 months ago
Score 0++
We are now also collecting feedback from our buyers in order to provide it to other buyers

Anonymous user #4

4 months ago
Score 0++
Are there any SSDs that have been tested by gekworm? I would like to know that.

Anonymous user #4

4 months ago
Score 0++
It seems that gekworm does not have the recommended SSD.

Anonymous user #4

4 months ago
Score 0++
Did you develop it using only HV2000?

Anonymous user #3

4 months ago
Score 0++

Is there some reason this should fail to work when using the raspberry pi imager UBUNTU image?

i've followed all of the directions i can find here and on the internet and nothing works.

Walker

4 months ago
Score 0++
Hello, you can contact us via our email: support@geekworm.com we will do our best to solve your problem(By the way, provide your order number)

Anonymous user #3

4 months ago
Score 0++
it only comes with the ability to mount a 2242. there is no not supplied for 2230.

Walker

4 months ago
Score 0++
Yes, only comes with 2242 fixing screws, if you need to install 2230, you need to prepare your own tools.

Anonymous user #2

4 months ago
Score 0++
Currently using with a Lexar Play M.2 2230 NVMe 1TB SSD. Works perfectly, boots Raspberry Pi OS with no issues. Running Gen 3 speed set in config.txt. Used 3M double-sided tape to hold SSD to X1003 adapter.

Walker

4 months ago
Score 0++
Thanks for sharing.

Anonymous user #1

4 months ago
Score 0++
Can you add a list of recommended drives that are known good?

Walker

4 months ago
Score 0++
Hi, X1003's recommended drives , in general, are compatible, only some types of drives are not compatible, please refer to Important Notes , we are currently collecting feedback from buyers as well.