https://wiki.geekworm.com/index.php?action=history&feed=atom&title=CommentStreams%3ADbf0c8052f655ca02bdbefc026b70073CommentStreams:Dbf0c8052f655ca02bdbefc026b70073 - Revision history2026-06-07T16:51:57ZRevision history for this page on the wikiMediaWiki 1.43.8https://wiki.geekworm.com/index.php?title=CommentStreams:Dbf0c8052f655ca02bdbefc026b70073&diff=35771&oldid=prevRuby: Migrated reply #64092026-04-09T17:21:24Z<p>Migrated reply #6409</p>
<p><b>New page</b></p><div>First, we don't recommend using high-end controllers on PCIe Gen 2.0 platforms. On one hand, it results in performance overkill; on the other, a few controllers are not backward compatible with PCIe Gen 2, which can easily cause instability and compatibility problems.<br />
<br />
Second, an unrecognized SSD does not always mean a compatibility issue—other factors may be at play. You can try these troubleshooting steps:<br />
<br />
:①The FFC cable only provides a maximum of 5W power, which is insufficient for SSDs with high peak power consumption. We suggest powering the SSD separately through the XH2.54 5V power connector.<br />
<br />
:②Check if your EEPROM firmware is updated (early Raspberry Pi 5 firmware does not support the initialization of new SSD controllers, refer to [https://wiki.geekworm.com/How_to_update_eeprom_firmware ''How to update eeprom firmware'']).<br />
<br />
:③Some users have tried forcing the SSD to run in PCIe Gen3 mode ('''for reference only;''' we do NOT recommend this, as official Raspberry Pi 5 does not guarantee Gen3 stability and it may cause system instability).</div>Ruby