Infinite reboot loop

Framework Laptop 13 Linux
1

I have Framework Laptop 13 (AMD Ryzen™ 7040 Series) with Ubuntu 26.04 installed on it with dual boot via grub to Windows 11. The BIOS is the latest release for the machine.

I received an email from Framework advising me to install the Windows Driver Bundle v2.08. So I booted into Windows, downloaded the driver install package and ran it. It ran, then asked me to hit a key to reboot the system so it could finish the installation.

I pressed a key. The system rebooted.

The Framwork logo then showed. A “Reset System” message showed for a brief moment: then the system rebooted. This cycle carried on for about 20 minutes - until I grew impatient and switched the computer off. Any time I switch the computer on this loop starts running again.

What’s going on? And how can I cure it?

2

I assume that you have issue only booting to windows. If yes, have you tried to run windows in safe mode? here is instruction how to do it. in recovery mode you can try to reinstall drivers and check if it works.
there are too additional boot options to choose:

  • Enable boot logging
  • Disable automatic restart on system failure - it should prevent restart so you should be able to see what is wrong
3

I don’t even get to the grub boot menu, so I never see the Windows logo - or any other os option.

4

Have you tried taking out the ssd? Does it stop looping if you do that?

5

Can you keep tapping F2 during boot, to get into the bios screens? Or is even that not possible.
Maybe there was a hardware fault that just started, and it just happened to co-inside with the software update.
Getting into to bios will prove its an os software problem. Failing to get into bios points more towards a hardware problem.

6

Good suggestion! I can get into the bios: and if I choose “Windows” in the bios boot manager Windows boots! However, if I choose “Ubuntu” in the bios boot manager the looping starts again. This gives me something to explore tomorrow. Thank you!

7

So that pretty clearly means something about the install is majorly screwed up, probably just try to reninstall and see if that was a fluke or there is something repeatable going on.

8

Try the “boot from file” option in the bios, and select shim.efi in the ubuntu efi folder. If it boots, then all that is wrong is the efi boot record.

1 Like
9

Okay - once I realised, thanks to your feedback, that the Framework update must have stonked over my Grub boot menu, I followed the instructions in the Ubuntu community to load and run the boot-repair tool. It fixed my menu, and I have my Ubuntu back again - without a heart-stopping reinstall required. And yes, I do back my system up, but a reinstall is still a major chunk of time.
Thank you everyone for your help!

10

I suspect it was more likely a silent Windows update, which in known to stomp all over any non-Windows boot code.