03:19 <lvrp16> nashpa: that adapter doesn't work. it needs a new adapter. that adapter is m.2 b-key.

03:19 <lvrp16> there's a 4 port version coming

03:20 <lvrp16> the m.2 on renegade elite is m.2 m-key

03:20 <lvrp16> https://en.wikipedia.org/wiki/M.2#Form_factors_and_keying

03:20 <lvrp16> m.2 hell

03:21 <lvrp16> the only ssds that work are nvme x4

06:51 <beeble> nashpa: pcie is backwards compatible. so a 3.x card should work with a 2.x host

08:37 <nashpa> lvrp16: I have the firefly-rk3399, so the m.2 b-key is what I want, right? For renegade I'm going to use my Toshiba RC100, which is B+M key

08:39 <nashpa> beeble: pcie is backwards compatible from signals POV, but some chipsets might not want to downgrade that low. Plus, with mmind00's changes the link is only training at gen1

08:39 <nashpa> without his changes the training starts at gen1 and then it tries gen2, but given that gen1 training fails, it will never get to gen2

08:40 <nashpa> I would be interested to learn from some Rockchip engineer how the training works for RK3399, I'm wondering if disabling the right phys to get a x2 link would work

08:52 <beeble> you can define the maximum link generation and the width

08:53 <beeble> also link training is defined for the downgrades. see the pci spec or at least the faq

08:53 <beeble> https://pcisig.com/faq?keys=&page=2

08:55 <beeble> so if it's a sata controller it will be most likely backwards compatible

09:15 <nashpa> beeble: yes, but I'm not sure if my Toshiba PCIe 3.1 SSD does backwards compatibility (maybe for performance reasons)

09:18 <beeble> my samsung 960 evo m.2 is working on a rk3399

09:39 <nashpa> beeble: with the Firefly adapter?

09:40 <beeble> i don't own a firefly

09:40 <nashpa> to convert from B to M key?

09:44 <beeble> i have a full size pcie slot on my board. and use a pcie to m2 adapter

09:47 <nashpa> ah, you have the pine64?

09:49 <beeble> no, a rk3399-q7 (puma) with the haikou baseboard

09:50 <nashpa> OK, understood

09:50 <nashpa> myself I wanted to validate the Firefly-RK3399 PCIe M.2 socket, and thought that just using an B+M x2 SSD it would work