Skip to content

Commit ce05342

Browse files
committed
FAQ: Add note on re-adding bootloader entry after fw update
Signed-off-by: Matt DeVillier <matt.devillier@gmail.com>
1 parent 91b9e05 commit ce05342

1 file changed

Lines changed: 8 additions & 0 deletions

File tree

docs/faq.md

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -216,6 +216,14 @@ then reboot to test. What we're doing is copying the grub EFI boot stub from the
216216

217217
* Your ISO wasn't written to USB properly — as an image, not an ISO — and you need to redo it [using the proper tool/settings](/docs/support/bootableusb.md). Etcher or Rufus in dd mode are the recommended options. The ChromeOS Recovery tool also works properly.
218218

219+
### After a firmware update, my device won't boot my OS — what happened?
220+
221+
* Sometimes a firmware update clears boot order entries stored in NVRAM. Your OS is still installed; the firmware just no longer knows how to find it. You have two options:
222+
223+
1. **Manually re-add the boot entry:** Type `exit` to reach the UEFI settings menu, then go to Boot Manager. Add the bootloader on your internal drive (or the appropriate EFI partition) as a boot option and set it as the first boot device.
224+
225+
2. **Boot From File and reinstall your bootloader:** Select Boot From File, navigate to `/EFI/[distro name]/grubx64.efi` (or the equivalent for your bootloader), and boot into your OS. Once booted, reinstall GRUB (or whatever bootloader you use) so it re-registers the boot entry with the firmware. For GRUB on Linux: `sudo grub-install` (and optionally `sudo update-grub`).
226+
219227
## Post-Installation / OS Issues
220228

221229
### I've installed Windows or Linux, and now something doesn't work?

0 commit comments

Comments
 (0)