Hello,
I experienced some interesting behaviour with my Framework 13 (AMD 7640) laptop, and am curious if anyone has some insight that would explain it.
I had left my laptop on for around 9 days without being plugged in, with the lid down, so the battery was pretty low. I wanted to lift the keyboard to access the inside, and I was in a rush (which was definitely a mistake), so I just held down the power button; in retrospect I wonder if the laptop was properly powered off when I lifted and unplugged the keyboard.
After replacing everything (I did not make any hardware changes), the laptop would not boot, even when plugged in. The power button would light up, and the keyboard backlight would come on, but the screen would never display anything. This, to me, was reminiscent of a bug in earlier firmware versions, which in my experience has been patched out of the firmware version I am currently using (version 3.16). I powered off and powered back on a few times, and removed the keyboard and reattached it as well, all to no avail.
I left the laptop to charge for the afternoon, and powered it on again and it would still not boot, however this time after turning it off and back on again it booted into password prompt to unlock encryption. Now I have Debian 13 installed with a unified kernel (UKI), dracut, and TPM2 enabled with PCR binds 1+3+7+11+12+15, signed with my own secure boot keys. The type #1 (non-UKI) entries have been left as boot options, but Microsoft’s secure boot keys are deleted so Debian’s Shim should not be able to boot those options. At any rate, some PCR condition must have failed on this first successful boot (I’m guessing PCR1 or PCR3?). I rebooted again without changing anything, and this time the TPM2 worked properly. Since then everything has worked normally.
I am glad that I have a functioning system again, but am curious if anyone has some explanation for what happened.