There have been some reports of the FW16 AMD 7040 failing to wake up from sleep.
There is a power button on the mainboard if you can find it. That might be enough get it booting. Then press F2 as soon as the display shows something. That should get you into the BIOS. This is at least show the power on is working, even if Windows is not working.
I would enable to power button again, and see if it works by doing normal power on and full power off. And avoid the suspend feature.
If that works OK again, we can then look at getting suspend/resume working again.
The reset procedure is rather specific:
Quoted from FW support:
Please try the following steps and see if it helps.
A. Set the BIOS to default by tapping F2 or F12 during the boot-up, once in the BIOS, please press F9 and F10.
B. If the issue persists, please reset the mainboard using the guide below.
Please turn off the laptop and unplug the charger.
Remove the input module, touchpad module, spacers, and Mid Plate, then plug in the charger.
Slowly press the chassis open switch/case switch 10 times, holding each press for 2 seconds. Release, wait for the red blink on the mainboard LED, then repeat this step.
Please see the location of the chassis open switch for reference.
There have been cases in the past with Framework 16’s where the battery is critically low (thanks to Microsoft’s Modern Standby that constantly drains the battery) and the machine will not POST until the battery gets sufficiently charged.
This is compounded by the mainboard being stuck in a Sleep? (or some other state) and for some reason the EC does not reset itself even after long presses of the power button. One case resolved itself by finding a 30W PD charger and plugging that into the board and it trickle charged the low battery enough to a usable state again.
In the future, lookup how to enable “Hibernate” (it is off by default in Windows 11) and use that instead of Sleep/Standby. Ever since doing that my Framework 16 has yet to have an issue when I powered it back on again.
Keep working with support though; like others have said, they are the best resource and they will get it sorted out with you! You can do it!
Thanks @James3, I tried this yesterday (support gave me same guidance) but no luck. I tried it with a few different timings between the 10 presses since the guidance from support said to press the button for 2 seconds then wait for the red blinking LEDs to blink before pressing again, but no variation helped. I appreciate the suggestion though!
I appreciate the heads up on “hibernate” @pkunk, I’ll keep that in mind if/when I get this working again. Maybe that would have prevented this issue. Now I’m waiting for support to respond.
By the way, what is EC? As for a trickle charge, I have no clue how to do that but I did try starting it with the battery removed, not sure if that matters.
The EC is the abbreviation for the Embedded Controller. It is a low level controller that talks to all the subsystem components of the mainboard (battery, charger, left and right side port controllers, etc.)
My reference to trickle charging was using a USBC power delivery (PD) charger anywhere from 30-60W vs. the 180W charger that is normally used with the Framework Laptop 16. There was a case a while back where someone was able to get the totally dead Framework Laptop 16 battery charged with a 30W PD charger to get some power into the cells so the laptop worked again and the 180W charger would do its job.
I am glad you are working with support, not sure if it was made clear that the 10 presses for 2 seconds each and waiting for the red blinking of the LED between presses was clear that this is to reset the mainboard using the chassis intrusion switch circled in yellow on one of the previous pictures.
Pressing the main power button and doing this will just try to repeatedly start the laptop which it is already not responding to.
Thanks @pkunk, that’s helpful about the USBC trickle charger, I’ll keep that in mind as another option. And I appreciate your clarification on the chassis intrusion switch, that’s what I was using.
The community here is amazing. Thanks to everyone who is helping out. Long work hours give me limited windows to deal with this, thus the sometimes long gaps between my replies.
