On Sat, Oct 13, 2018 at 5:01 PM, Garry T. Williams <gtwilliams(a)gmail.com> wrote:
By the way, from the journal during the dnf system-upgrade reboot:
Sep 30 10:02:27 vfr dnf[831]: grub2-common.noarch 1:2.02-58.fc29
Sep 30 10:02:27 vfr dnf[831]: grub2-efi-x64.x86_64 1:2.02-58.fc29
Sep 30 10:02:27 vfr dnf[831]: grub2-pc.x86_64 1:2.02-58.fc29
Sep 30 10:02:27 vfr dnf[831]: grub2-pc-modules.noarch 1:2.02-58.fc29
Sep 30 10:02:27 vfr dnf[831]: grub2-tools.x86_64 1:2.02-58.fc29
Sep 30 10:02:27 vfr dnf[831]: grub2-tools-efi.x86_64 1:2.02-58.fc29
Sep 30 10:02:27 vfr dnf[831]: grub2-tools-extra.x86_64
1:2.02-58.fc29
Sep 30 10:02:27 vfr dnf[831]: grub2-tools-minimal.x86_64
1:2.02-58.fc29
Sep 30 10:02:28 vfr dnf[831]: shim-x64.x86_64 15-5
And now:
garry@vfr$ rpm -q grub2-common grub2-efi-x64 grub2-pc grub2-pc-modules
grub2-tools grub2-tools-efi grub2-tools-extra grub2-tools-minimal
shim-x64
grub2-common-2.02-62.fc29.noarch
grub2-efi-x64-2.02-62.fc29.x86_64
grub2-pc-2.02-62.fc29.x86_64
grub2-pc-modules-2.02-62.fc29.noarch
grub2-tools-2.02-62.fc29.x86_64
grub2-tools-efi-2.02-62.fc29.x86_64
grub2-tools-extra-2.02-62.fc29.x86_64
grub2-tools-minimal-2.02-62.fc29.x86_64
shim-x64-15-7.x86_64
garry@vfr$
Good catch. It's vaguely possible there's a bug in either shim 15-5 or
grub2-efi 2.02-58 as it relates to your firmware, that caused it to
silently fail, and the firmware did a fallback to the 2nd BootOrder,
which is the Ubuntu entry.
One way to find out, that probably isn't worth it, is to manually
downgrade to those versions, separately, to see which one (if any)
restores the problem. But, it's fixed so I probably wouldn't test it
as those versions have been superseded now.
--
Chris Murphy