I booted the laptop after a few days of not using it. I’d purchased it recently, and had only used it for a day to configure it.
Today, I:
…and the screen remained black from thereon.
Now, when I boot, nothing appears – not even the Framework logo – and the modules flash blue and red.
The undermentioned is the best I can do, due to it not booting:
I’ve switched the side that my single stick of Framework-stock (DDR5?) SDRAM is connected to, and this has caused the blue-red lights to become red (although they did change to green and blue for about 5 seconds after a minute of flashing red).
Unfortunately, I haven’t been able to locate the alternative to My Framework Laptop (Intel 11th Gen Intel® Core™) is not powering on for an AMD CPU.
Turns out that the red flashing solely occurs when disassembled. When I reconstruct it, it becomes blue and red again, like originally. Is the intrusion detection somehow blocking me from my laptop?
Are you able to get into the BIOS, and are you able to boot from a bootable USB?
@lbkNhubert, I’m unable to access the UEFI GUI. I’ve tried F2 and F12.
Consequently, I’m unable to choose a boot device too (although I doubt it would differ, for I don’t even see the Framework icon). There is absolutely no display output.
I’ve filed a support request:
This is about order ███████████ (of an AMD FW16).
As Black display on FW16 - #5 by RokeJulianLockhart and its predecessors explain, after getting part of the way through the boot process, the display of my FW16 went black and hasn’t changed since. I can’t even access the UEFI GUI - it’s completely black, without even the Framework logo on boot. I estimated this might be due to “RAM testing”, as other forum members noted. However, leaving it for 15 minutes didn’t change anything, so I doubt it.
What’s so peculiar is how this happened after entering my LUKS password. It was a normal boot until that point - RAM checking doesn’t initiate during OS boot, surely? Although the fault is obviously with the device itself, considering I can’t access the UEFI GUI, I can’t even try accessing another OS in a live USB because of that.
After the trackpad issue (I wasn’t provided with a ticket reference to correlate this with, but it instigated order ███████████) I’m wondering whether something is fundamentally wrong with this machine. Would it be worth an RMA for the entire thing? Since it’s a paperweight right now, I’m fairly apathetic about sending it or trying to diagnose the fault with your assistance - whichever is your preference.
The mainboard had died. I was sent a replacement by Framework, and that has worked since. I’ll send my old one back soon, and attempt to ascertain what the fault was.
This topic was automatically closed 180 days after the last reply. New replies are no longer allowed.