Install the grub package. (It will replace grub-legacyAUR if that is already installed.) Then do: # grub-install --target=i386-pc */dev/sdX*
where i386-pc is deliberately used regardless of your actual architecture
Why is i386-pc deliberately used regardless of the actual architecture? Is it because i386-pc is fine for both 64 and 32 bit systems?
That makes sense. Mine is a UEFI, and I did see a x86_64-efi directory inside my /boot/grub/ directory. Can you provide an explanation for the rationale behind deliberately using i386-pc as suggested in the Arch Wiki? I assume there is a good reason behind it? The default value for --target is x86_64-efi though (according to grub-install --help).
This is what happens when you click into an Arch Wiki page and use Ctrl+F to look for keywords and then start reading the first keyword you find without considering the surrounding sections…
Wasn’t planning to run it. I saw the article you wrote here which discourages running grub-install post upgrade. I was doing some research in the hopes of learning more about the topic. This bout of curiosity was brought upon by a warning message I saw in my pacman logs.
[2022-12-10T00:46:40+0800] [ALPM-SCRIPTLET] :: To use the new features provided in this GRUB update, it is recommended
[2022-12-10T00:46:40+0800] [ALPM-SCRIPTLET] to install it to the MBR or UEFI. Due to potential configuration
[2022-12-10T00:46:40+0800] [ALPM-SCRIPTLET] incompatibilities, it is advised to run both, installation and generation
[2022-12-10T00:46:40+0800] [ALPM-SCRIPTLET] of configuration:
[2022-12-10T00:46:40+0800] [ALPM-SCRIPTLET] $ grub-install ...
[2022-12-10T00:46:40+0800] [ALPM-SCRIPTLET] $ grub-mkconfig -o /boot/grub/grub.cfg