On 31/10/24 10:06, Go Canes wrote:
That's fine, things may be working in my system the way you have indicated, even though the kernels I use are 64bit.On Wed, Oct 30, 2024 at 6:11 PM Stephen Morris <steve.morris.au@xxxxxxxxx> wrote:On 30/10/24 11:51, Go Canes wrote: My output from efibootmgr is below. The boot order specified in the output is the boot order specified in my motherboard bios, not the boot orders specified in the grub menus.I don't think there is any connection between the order of the UEFI boot variables and the order things are presented in grub menus.I always wondered why there are two entries for Fedora in the bios boot settings (that both look to be the same name) and what you have said is the indication of the shim that is being booted from, I'm now wondering why there aren't two entries for Windows and Ubuntu which are also capable of running 32 bit processes. If I am indeed booting in 32 bit mode, that might explain why F40 SDDM takes a long time to load and why after the KDE desktop is displayed the system sits there thrashing the hard disks for several minutes, and the upgrade to F41 doesn't seem to have changed anything."bios boot settings" is another thing entirely. My "bios" only shows one entry: "Fedora". Even if I try to use efibootmgr to create new entries. Also, regarding shim.efi vs shimx64.efi (and grub.efi grubx64.efi) - it may be the case that shim.efi is 32-bit, but still boots a 64-bit kernel. I don't really know. I *assume* the *x64.efi entries are 64-bit, and that it implies the others are 32-bit. So, having taken a moment to look, shim.efi and shimx64.efi are identical, and there is no grub.efi, only grubx64.efi. So purge my silly comments on UEFI booting in 64-bit vs 32-bit mode from your brains. Sorry!
As I said earlier, my bios has 2 entries for Fedora (all the boot entries in my bios are named for the OS and the hard disk they are installed on), so to test your 32/64 bit theory I changed which of the two Fedora entries I was booting from, whence efibootmgr then told me I was booting from shimx64.efi instead of shim.efi.
Looking at my efi environment, I have, gcdia32.efi gcdx64.efi grubia32.efi grubx64.efi mmia32.efi mmx64.efi shim.efi shimia32.efi and shimx64.efi. I'm not sure where all of these have come from unless it is because I'm running an AMD cpu.
I have also recently been in the situation where I upgraded the version of Ubuntu I'm running, which set up its grub environment, and that upgrade changed the boot order in the Motherboard bios to boot from Ubuntu instead of Fedora, which I then had to change back.
regards,
Steve
Attachment:
OpenPGP_0x1EBE7C07B0F7242C.asc
Description: OpenPGP public key
Attachment:
OpenPGP_signature.asc
Description: OpenPGP digital signature
-- _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
