Received and assembled a new 13” AMD Framework laptop. Unfortunately it doesn’t boot up. Black screen and solid green LED through all the trouble shooting steps. What I have done:
Both RAM sticks, 32GB (Crucial CT2K16G56C46S5). Single RAM stick, 16GB, bank 0 and 1, then swap 2nd RAM stick.
Remove NVME (Sabrent Rocket 4.0 1TB).
Reseat NVME.
Unplug/replug screen cable to mainboard
Unplug/replug input cover
Remove NVME, RAM then try booting
Mainboard reset following (Remove the Input Cover. Press the chassis open switch in the center of the Mainboard 10 times, you must press it slowly, so press for 2 seconds. Release, wait for the red blink on the Mainboard LEDs. repeat.)
I did contact Framework support but would like to get help in the mean time. Thanks in advance.
Thank you for replying. I waited around 15-30 mins for each tests but didn’t work. I did connect to external monitor earlier but it didn’t work. However, after some more reseat, reset, and, connecting to external screen again, it actually boot up!
I am happy that mainboard seems fine. But looks like screen needs to be replaced.
Nice. Since you messed with the screen connector earlier, probably double check that it’s connected properly. You can also shine some bright light on the screen (when the screen should be displaying something), to check if the data connection is bad, or the backlight. If you see something with the light, it’s probably a backlight problem.
One other thing I would suggest, is that you check the display cable for bent pins. It is a delicate cable, similar to the battery connector, and it is possible there is damage there as well.
I am actually having the same issue for the second time on my 13th gen FW13. Mine stopped working both time when it became discharged. First time Framework sent me a new mainboard and I have not had time to contact support again about the second one. Both worked perfectly for a couple months each.
Okay, my framework 13 is finally working after replacing the display, kudos to Framework support.
I’d like to share a finding when removing the malfunctioned display, I found the connector that connects to display (not the usual connector that connects to mainboard we usually referred to) kinda loose. That connector looks very delicate so I didn’t do any further test. But I suspect that might be the cause of the failure.
Do note that I’m sharing just for the information. I think Framework might not want their customer to touch that connector for a reason.