FrameworkComputer/SoftwareFirmwareIssueTracker

Boot loop due to charged system wanting power adapter

Opened this issue · 2 comments

Device Information

System Model or SKU

Please select one of the following

  • Framework Laptop 13 (11th Gen Intel® Core™)
  • Framework Laptop 13 (12th Gen Intel® Core™)
  • Framework Laptop 13 (13th Gen Intel® Core™)
  • Framework Laptop 13 (AMD Ryzen™ 7040 Series)
  • Framework Laptop 13 (Intel® Core™ Ultra Series 1)
  • Framework Laptop 16 (AMD Ryzen™ 7040 Series)

BIOS VERSION

03.04

DIY Edition information

If you are experiencing an issue on a DIY system, Please also fill out the memory and storage devices you are using.

Memory: Micron Technology, 691733
Storage: Western Digital, 753053

Standalone Operation

Are you running your mainboard as a standalone device. Is standalone mode enabled in the BIOS?

  • Yes
  • No

Describe the bug

Red text will occasionally appear under the framework logo stating "Please make sure system has adapter" when booting unplugged, but with ample battery (70-80%). The system will reboot and display the message several times before successfully booting. This does not occur when plugged into power.

Steps To Reproduce

Steps to reproduce the behavior:

  1. Disconnect laptop from power.
  2. Press the power button and shutdown.
  3. Press the power button to turn on laptop.

Expected behavior

Regular boot with no red text or boot loop.

Operating System (please complete the following information):

  • OS/Distribution: Fedora
  • Version: 42
  • Linux Kernel Version: 6.15.5-200.fc42.x86_64

Additional context

This problem occurred after a BIOS update.

Oh you must be stuck in a loop where it keeps trying to update.
You can remove the files in /boot/EFI/UpdateCapsule.

Removing the files in /boot/efi/EFI/UpdateCapsule appears to have resolved the boot loop.
I have, since removing the files, observed a case where the system was unplugged, at ~70%, and rebooting, where the I got red text stating, Check system adapter. However, I am unsure if this is related to the current issue. I have not been able to successfully replicate that condition.