You are not logged in.
Hi,
For the first time in my life I decided to upgrade the BIOS using fwupdate instead of the usual way (downloading the iso and flash it onto a drive).
I guess I read this part on the wiki too late:
Warning: An update to your UEFI firmware may discard the current bootloader installation. It may be necessary to recreate the NVRAM entry (for example using efibootmgr) after the firmware update has been installed successful.
So what should I do now? Booting with a live usb stick and fix the bootloader stuff with efibootmgr?
Last edited by LordChaos73 (2019-03-20 14:05:54)
Offline
Yes. Depends on your vendor, some just remove all NVRAM entries on update.
Last edited by V1del (2019-03-20 13:37:03)
Offline
Booting with a live usb stick and fix the bootloader stuff
^ This but running `grub-install` or `bootctl install` should generate new boot entries, no need to faff around with efibootmgr.
Adding the --removable flag to the `grub-install` command will copy the .efi loader to the removable loader location — this should boot automatically in the absence of NVRAM entries.
Offline
Yes. Depends on your vendor, some just remove all NVRAM entries on update.
Well, fingers crossed then. I hope I won't f*@k up my installation.
Offline
LordChaos73 wrote:Booting with a live usb stick and fix the bootloader stuff
^ This but running `grub-install` or `bootctl install` should generate new boot entries, no need to faff around with efibootmgr.
Adding the --removable flag to the `grub-install` command will copy the .efi loader to the removable loader location — this should boot automatically in the absence of NVRAM entries.
So basically you're saying:
1. I should boot with a live cd
2. Mount the relevant partitions
3. chroot
4. run grub-install and I should be fine?
Offline
If you want to use the plain `chroot` command then you will have to (bind) mount the API filesystems from the live system to the chroot system beforehand. Or use `arch-chroot` instead.
Refer to the relevant ArchWiki page for the `grub-install` instructions.
Offline
If you want to use the plain `chroot` command then you will have to (bind) mount the API filesystems from the live system to the chroot system beforehand. Or use `arch-chroot` instead.
Refer to the relevant ArchWiki page for the `grub-install` instructions.
Thanks, de machine is up-and-running again.
p.s. What's up with some of the characters you sometimes type? For instance: `a and `c
p.s.s. Strange, those weird characters only show up with Chrome on a Mac, not on Linux
Last edited by LordChaos73 (2019-03-20 14:09:58)
Offline
What's up with some of the characters you sometimes type? For instance: `a and `c
They're just backticks, they indicate a command to be run and if this forum used markdown then they would show up in a tiny code box using monospace.
I think I copied the habit from JWR a while ago and now it's stuck
Offline
LordChaos73 wrote:What's up with some of the characters you sometimes type? For instance: `a and `c
They're just backticks, they indicate a command to be run and if this forum used markdown then they would show up in a tiny code box using monospace.
I think I copied the habit from JWR a while ago and now it's stuck
The funny thing is, looking at this page with the latest Chrome (MacOS) `a appears as à, `o appears as ò and so on
Offline
For the first time in my life I decided to upgrade the BIOS using fwupdate instead of the usual way (downloading the iso and flash it onto a drive).
I guess I read this part on the wiki too late:Warning: An update to your UEFI firmware may discard the current bootloader installation. It may be necessary to recreate the NVRAM entry (for example using efibootmgr) after the firmware update has been installed successful.
AFAIK this has nothing to do with using fwupdate. Every UEFI system that I've ever come across wipes the NVRAM when you update the firmware no matter how you do it.
Offline