On Wed, 2019-05-29 at 17:43 -0600, Chris Murphy wrote: > On Wed, May 29, 2019 at 5:52 AM Michal Schorm <mschorm@xxxxxxxxxx> wrote: > > Hello, > > > > I'd like to propose tiny correction for the Fedora wiki page about GRUB2 [1]. > > > > However I'm not confident enought to edit it prior to any discussions, > > so that's why I'm writing here. > > > > In the chapter "Updating GRUB 2 configuration on UEFI systems" > > In the section "Install the bootloader files" > > I believe, there should be an information added, that the 'grub2-efi' > > package *must* match your architecture. So e.g. for x86_64, you want > > the 'grub2-efi-x64' package. > > No. You can have x86_64 CPU but the firmware is 32-bit, hence ia32 > which is why there is: > > grub2-efi-ia32-1:2.02-81.fc30.x86_64.rpm > > The user space will still be 64-bit but the EFI binaries will be > 32-bit for the rare firmware floating out there that require it. There > isn't a problem with 32-bit and 64-bit EFI binaries being located on > the same EFI system volume in EFI/fedora, the firmware figures it out > (I think by filenaming convention which is mentioned in the UEFI > spec). > > My suggested change for this section: > > 🔗 Install the bootloader files > If you don't already have the relevant packages installed, do for > Fedora 22 and later versions with DNF or with YUM for older Fedora > releases: > > - dnf install grub2-efi shim > + dnf install grub2-efi-ia32 grub2-efi-x64 > - yum install grub2-efi shim Uh. We *do* have users who don't use x86_64 arch... -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
