On Wed, May 1, 2019 at 2:49 AM Chris Murphy <lists@xxxxxxxxxxxxxxxxx> wrote: > On Tue, Apr 30, 2019 at 4:17 PM Patrick O'Callaghan > <pocallaghan@xxxxxxxxx> wrote: >> On Tue, 2019-04-30 at 16:03 -0600, Chris Murphy wrote: >>> >>> Just a heads up that this can be an issue, but I'm not sure how >>> common it is. It applies to BIOS (not UEFI) firmware, and for >>> systems that originally had Fedora 20 or older installed and also >>> never had 'grub2-install' issued since then. Therefore it can be >>> prevented just by running 'grub2-install' before commencing the >>> Fedora 30 upgrade. >>> >>> https://fedoraproject.org/wiki/Common_F30_bugs#GRUB_boot_menu_is_not_populated_after_an_upgrade >>> >>> It's worth going through all the Common Bugs. >> >> The text actually says: >> >> So if you have an installation that has been updated since Fedora >> 20 or before, it is recommended to execute the grub2-install >> command before doing a system upgrade. >> >> I assume that should say "... if you have an installation that has >> NOT been updated since Fedora 20 or before ..." > > Good catch. I fixed that, and made a few other clean ups, let me > know if you spot any other problems. Strictly speaking, grub has been updated if you've upgraded from F20 to F30. But the grub stages and the grub modules haven't been updated. _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-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/users@xxxxxxxxxxxxxxxxxxxxxxx
