What happens to bootloader after firmware update?

Firmware Coreboot
1

I’m using coreboot+SEABIOS with Windows 10 on my Librem Mini v2. No dual boot, no Linux. Just Win10 on top of coreboot (v4.15) and SEABIOS. I want to update the firmware by first removing my hard drive where Windows resides (I know it’s not necessary but just in case) and then booting PureOS from USB and using coreboot_util.sh. My question is if this is going to mess up the boot process after I reattach my hard drive. If I remember correctly there is a chance that the new firmware might not be able to properly boot my previously installed Windows because it might be missing something in the bootloader. But I’m not sure if this is the case.

What should I expect?

2 Likes
2

I don’t know but make sure that you have the current version available to flash in case you have to revert.

1 Like
3

Why? Did you receive reports about latest coreboot/seabios not working?

1 Like
4

Standard practice for any upgrade. Always give yourself a way to back out in case things go pear-shaped.

Bear in mind that the average user in this forum probably doesn’t use Windows and in particular not on Purism hardware. So experience with Windows is limited, and it is also outside the Purism support boundaries.

2 Likes
5

You should be fine as long as you reattach your hard drive to the exact same slot as earlier.

1 Like
6

Hmm, thanks for letting me know. May I ask if you know technically how it works? Does the bootloader and OS (windows) entry in the bootloader reside in flash chip? If that’s the case it could be deleted when flashing.

But I think there’s a mechanism to re-create the OS entry for the bootloader when it’s empty. I’m not sure though. Hope you can enlighten me.

2 Likes
7

I know that I have zero interest providing any technical support for any user voluntarily using proprietary software:

1 Like