On Sun, Oct 14, 2018, 01:35 Chris Murphy <li...@colorremedies.com> wrote:
> On Sat, Oct 13, 2018 at 5:01 PM, Garry T. Williams <gtwilli...@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. > This error happened to me too when I tried to upgrade to f29 about a week ago. fedora boot item is still there, but fails silently, and boot falls back to second item (Windows 10 in my case). Only reinstalling older versions of grub2 and shim from f28 "fixed" it. So the intermittently broken grub2/shim version theory seems plausible. Upgrading to f29 results in a booting system now. (Side note, fedora 29 continues to be unusable for me because of gdm/gnome issues with the nvidia driver, and nouveau is ... not good on 1000 series cards.) Fabio > > -- > Chris Murphy > _______________________________________________ > test mailing list -- test@lists.fedoraproject.org > To unsubscribe send an email to test-le...@lists.fedoraproject.org > 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/test@lists.fedoraproject.org >
_______________________________________________ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org 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/test@lists.fedoraproject.org
