In the last few days, there have been way more posts from people with compatibility problems, and it seems like the memory incompatibility might not just be Ramaxel modules, but any “E0” module outside of the two on the official compatibility list. It also seems like the different CPUs have different compatibility (potentially due to clock speed), I’ll be sure to post about my results with the X9 when it arrives. People on reddit have created a thread and spreadsheet with an unofficial list, which is significantly more comprehensive than the official one, at least for now.
On this (unofficial) chart, it seems like nobody has confirmed that module either way, but it appears to be “E0”, so you may have a reason to be concerned.
I managed to get my hands on 16GB of MTD8C10324N2FN026C2 at a very reasonable price a while ago, and am quite worried it won’t work, causing me to need to return the system, as there’s no real possibility of finding some other memory at this point. I figure my choices are to either add framework’s 16gb to the order, and if my module works, then to try and return just the memory, or to go without, and risk having to return the system. I’m on the X7 configuration.
Do you have a 30 days returns where you are? You could spend a couple of weeks scouring about for new RAM, and you could even make a cheeky request to see if FW would sell you a stick separately. Normally of course it needs to come with a laptop, but I’d wager they would make an exception.
Could you put in a support ticket now to ask if they can do that shortly after your laptop’s arrival?
No worries. I’d also say that if you end up selling your current RAM, you will find a buyer eventually, even if the demand will be low at present. That can only improve, so your only difficulty is if you were to need to sell immediately.
Got my Batch 5 today and since I was hit by the downgrade 64GB to 32GB, I managed to source a 64GB Lenovo stick.
It is a FRU: 5M31L87464 which should be Micron, but E0. Sadly this does not post and thus seems not compatible. Framework’s 32GB stick works without issues.
@RPL Sorry to hear that! And thanks for posting it, this is the first first-hand test of that exact FRU anywhere I’ve seen.
I have the same module (5M31L87464) waiting for my machine and I’m deciding today whether to return it, so if you have a minute, two quick questions:
What does the sticker actually say? The FRU should map to Micron MTD32C20326N8FN026C1 with a label line like 2RX8 PC5-7500-FE0-0100-NT, but Lenovo has shipped Ramaxel-made modules under neighbouring FRUs, and so far every confirmed failure has been Ramaxel or Samsung while Micron/Crucial parts have worked. If yours turns out to be Ramaxel-made it’s a very different data point from a genuine Micron failure.
Which CPU do you have? Ultra 5 325, X7 358H, or X9 388H? The community sheet shows the same module passing on one CPU and failing on another, so this might matter.
And if you still have it in hand before the return:
Did you reseat and re-torque it and try again? First boot with a new module can take a long time to train… did you leave it for a minute or two at a black screen before calling it?
Any diagnostic feedback? Power/side LED blink pattern, or just a dead black screen?
Which BIOS are you on (3.02)?
Totally understand if you’ve already boxed it up. Even just the sticker photo and CPU would help a lot.
I did try to reseat. I first tried the 64GB module. And it was just a black screen. Then tried the included 32GB module and it started with a memory training screen and then posted normally. Then tried the 64GB again, but only black screen.
Edit: just put it back in, and I have a black screen with slowly blinking red power LED. I first thought it was the input cover not being screwed down, but that did not change it. It also need a long power button press to shut down. Could of course also be a faulty module, unfortunately I have no other way to test it.
Any other things I’m happy to test, I will return it in a couple of days.
I can sadly confirm this. I have the exact same module (as I wrote in an earlier post). Tested on my new X9 388H that I received today.
Simply put, the Lenovo branded module failed to POST (RED blinking LED on the right side). I torqued it to spec and waited about 10 mins before giving up (eventhough it was perfectly clear from the blinking LED that it wasn’t going to work). Also ruled out any bent pins in the interposer
Luckily, I had ordered a Crucial LPCAMM2 module as well when FW13 Pro was first announced.(This Lenovo RAM was bought on a whim fearing that the Crucial won’t work). When I installed the Crucial module, I got the Memory Training in Progress screen right away and was able to confirm the spec of the RAM and my SSD in the BIOS. I retried the Lenovo RAM again to no avail.
I remember seeing the Unofficial list on reddit and also a note from Framework’s catastrophic on another reddit post about Ramaxel-made module that the team is looking into it (given this is supposedly the E0 revision).
Perhaps I got a bad module, or it is simply incompatible at the current BIOS revision (3.02)(Lenovo’s support page doesn’t offer anythign useful except confirming the module I have)
Thankfully I am still in the return window and will wait 1 more week before sending this back.
Yes, you can see the linked Lenovo support page for the difference. My kit only came with the RAM & no interposer. And it’s a bit too late for my return window to try to get one from Lenovo. Kapton tape could be an option, but I don’t want to damage the existing interposer from FW
Nice idea. My 64GB stick did not come with an E0 interposer, so I taped off the center line and it booted right up into memory training following a normal post.
I wont do more testing since I just used normal tape, but with a proper interposer this should work.
Question is now, where do I get one of those, they might be even more rare than a LPCAMM2 module
Funnily enough, my initial suspicion was the interposer based on the Lenovo support page. Glad you could test it (even if it means risking bending those pins). I am sure Framework can source one of these and make it available in the marketplace in the near future.
This topic is slowly starting to become frustrating.
It would be great if Framework could gradually give us a few tips on what we should pay attention to with the RAM. And whether there will possibly be BIOS updates that will improve compatibility with E0 modules.
If everyone sells off their overpriced, incompatible modules now, only to find out later that a BIOS update made them work after all, a few people here (myself included) are slowly going to flip into rage mode…
