I have a Framework 11th gen laptop. There was a bios update available so like previous updates I typed the command ‘sudo fwupdmgr update’.
It prompted to download and install the new bios update. I confirmed it and rebooted like asked.
Now I am stuck in a boot loop. When the laptop starts it starts my ArchLinux install that then automatically boots into my bios. I then exit the bios and start my ArchLinux install that then boots into my bios. Etc… Etc…
I can boot from a USB stick and reinstall ArchLinux but prefer a way to preserve my current install. Is there a fwup file I can delete so my ArchLinux OS starts again without it booting into the bios?
Your os installation on disk is probably ok. It is a known issue in the release notes for the firmware update that the boot entries in the BIOS nvram can get cleared with an update and may need to be re-entered. This seems to be more common when using grub2 or a boot manager rather than booting directly into an os like with booting an os with systemd boot. Since your computer is booting into bios setup, navigate to the boot entry screen and check / update your boot entries. It might be able to search your disk for bootable images. Search the forum or contact framework support for more details as I read about this but have no experience with it to help you. Sorry.
Thanks for the info. But I think that’s not the problem.
The system loads my ArchLinux install, since the install is LUKS encrypted it asks me for my passphrase. The moment it unlocks it goes to the bios, like fwupdmgr is waiting for a action to finish.
I have tried F3 while booting and found 2 EFI entries, fwupdx64.efi and grubx64.efi.
fwupdx64.efi brings up a terminal stating that there is no updates to process and then reboots.
grubx64.efi loads my ArchLinux install, I unlock it and then it reboots to bios.
I can boot from a USB stick and see that my data on the SSD is there.
ok. Sorry, I mis-read your original post.
I’m just starting with linux so can’t be of much help. One idea that comes to mind is to boot from your USB/recovery system, mount your normal system filesystem and view the system log or any crash log to see if a reason to fail to continue to boot was logged. I’m thinking that rather than the bios update intercepting the booting, maybe there is now an incompatible kernel module or something like that.
Another idea is to prep an unused usb drive with the esp firmware update for the version that was working and roll back the update using that method.
Good luck!
