Stuck in a loop

Hey all,

So I opened my laptop this morning and instead of waking, it seems to have entered some kind of loop:

  • the keyboard backlight turns on
  • the power button lights up
  • the fans spin up
  • screen remains off

It sits like that for about 30 seconds before it seems to power off, but 5 seconds later it starts all over again. It’s stuck in some kind of a loop.

I’ve tried holding down the power button while it was lit up, but it had no effect. I was able to “break” the loop by waiting for it to power off, then hold down the power button.

With it “off”, I cracked open the case and removed the battery connector, thinking that it was just stuck trying to wake from sleep. Reconnected the battery, started it up, and it’s still in the same looping state.

I’ve emailed support, but hoping maybe someone has seen this behavior before and knows how to fix it?

It does this while plugged in?

Both on and off battery.

Solved!

Popping out the CMOS battery seemed to do the trick. I’m back on the framework as I type. I’m not exactly sure why it happened, but at least I know what to do if it happens again.

4 Likes

So I thought this was a solved issue, but the next time I put the laptop to sleep it entered the loop again, and I had to reseat the CMOS battery.

Obviously this is less than ideal.

I’m still running the firmware version (0.0.3.2) that the laptop shipped with. I tried to update via fwupdmgr last week but despite it seeming to have run, I’m still on the old version. I’m beginning to suspect that failed update has left the firmware in a somewhat broken state.

Unfortunately LVFS is still not ready but there’s a standalone updater for 3.07, the EFI Shell update:

I’ll give that a try. I was able to update to 3.06 using an Ubuntu Live CD, but now the battery isn’t charging. Whoops.

ETA: That’s going to be a problem. It seems like none of my expansion card ports are working. USB-C won’t charge. USB-A isn’t recognized, so I can’t boot to a drive with the EFI shell update.

Whoops, time to contact support.

Yanking the CMOS battery fixed the charging issue. I’m not sure if the sleep issue is fixed yet, but that’ll be the next thing to test.

Updated to 3.07 via EFI Shell/USB drive. Everything seemed to go smoothly, and everything is working afterwards. Suspend seems to work as well so it looks like things are back to normal.

Thanks for the help, @Fraoch!

2 Likes

Whew, glad that fixed it! :grin:

It’s so weird hearing these buggy things happening with framework…

I’m just now getting this issue. My laptop reset and has been in this loop. I tried everything with disconnecting the battery strap and the CMOS battery. There was at one point where it booted up with Windows saying that it couldn’t load properly. I clicked on “retry” and it just continue into the loop and I never got that screen again. I’m not entirely sure what to do next from here on…

I am having the same issue. 11th Gen Intel, latest BIOS 3.20. Taking CMOS battery seems to fix this temporarily, but it’s absolutely ridiculous to need to open laptop physically to do this every time it goes into boot loop. Any ideas?

Bookmarking, and will follow up. I’m under warranty and having the same issue after replacing a defective screen under warranty. Only difference is, CMOS battery trick doesn’t work, it’s a blinking light brick for me.

Hmmm I’m running into the same exact problem. Framework 13 with Intel 11.
I’m unable to go into hybernate or standby without it not booting up correctly, running fedora all most recent updates as of a week ago.
I need to disconnect battery cable and cmos bettery before I can get back into any type of screen. Even the bios/UEFI won’t show until I disconnect everything.
Got a new cmos battery in September but it’s still happening.
I disabled all standby and hybernate options but for some reason it happened again. I’ll probably contact support and hope to get something resolved?

I had to change these lines in /etc/default/grub
GRUB_CMDLINE_LINUX=“rhgb mem_sleep_default=deep”
to
GRUB_CMDLINE_LINUX=“rhgb mem_sleep_default=s2idle nvme.noacpi=0 acpi_sleep=nonvs”
then run
sudo grub2-mkconfig -o /boot/grub2/grub.cfg

I’m guessing the standby battery will go back to pretty bad, but at least it’s booting now.

1 Like