Re: Upgrade to Fedora 34 broke the boot menu.

2021-05-11 Thread Chris Murphy
On Tue, May 11, 2021 at 8:54 AM Björn Persson wrote: > > Adam Williamson wrote: > > Do you have any idea what went wrong? I don't recall hearing of anyone > > else having this trouble, yet. And we've definitely had pre-BLS > > installs upgraded, as people hit the GNOME login bug on them... > > The

Re: Upgrade to Fedora 34 broke the boot menu.

2021-05-11 Thread Björn Persson
Adam Williamson wrote: > Do you have any idea what went wrong? I don't recall hearing of anyone > else having this trouble, yet. And we've definitely had pre-BLS > installs upgraded, as people hit the GNOME login bug on them... The current hypothesis is that the system was using and updating /boot

Re: Upgrade to Fedora 34 broke the boot menu.

2021-05-10 Thread Adam Williamson
On Sun, 2021-05-09 at 21:40 +0200, Björn Persson wrote: > My boot menu is now repaired. > > I replaced /boot/grub2/grub.cfg with the following: > > insmod part_gpt > insmod ext2 > search --no-floppy --fs-label --set=root speedy.boot2 > insmod blscfg > blscfg > > That was good enough to find the

Re: Upgrade to Fedora 34 broke the boot menu.

2021-05-09 Thread Björn Persson
My boot menu is now repaired. I replaced /boot/grub2/grub.cfg with the following: insmod part_gpt insmod ext2 search --no-floppy --fs-label --set=root speedy.boot2 insmod blscfg blscfg That was good enough to find the kernel and get Fedora going. (Keeping all the partitions labeled pays off in s

Re: Upgrade to Fedora 34 broke the boot menu.

2021-05-08 Thread Chris Murphy
On Sat, May 8, 2021 at 3:51 PM Björn Persson wrote: > > Chris Murphy wrote: > > Does /etc/default/grub contain > > GRUB_ENABLE_BLSCFG=false > > ? > > No, it says "GRUB_ENABLE_BLSCFG=true". > > > There have been two big GRUB changes and if you followed them without > > any intervention or customiza

Re: Upgrade to Fedora 34 broke the boot menu.

2021-05-08 Thread Björn Persson
Alexander Ploumistos wrote: > Have you looked in /boot/loader/entries/ ? I don't know how they get > created, but a couple of times I've had some extra entries after an > upgrade - nothing older than Fedora N-2 though. It contains files that seem to match the menu entries I should get, none of the

Re: Upgrade to Fedora 34 broke the boot menu.

2021-05-08 Thread Björn Persson
Chris Murphy wrote: > Does /etc/default/grub contain > GRUB_ENABLE_BLSCFG=false > ? No, it says "GRUB_ENABLE_BLSCFG=true". > There have been two big GRUB changes and if you followed them without > any intervention or customizations, you get upgraded correctly. If you > make customizations or opt

Re: Upgrade to Fedora 34 broke the boot menu.

2021-05-08 Thread Chris Murphy
On Sat, May 8, 2021 at 11:36 AM Chris Murphy wrote: > > If you have BLS disabled, enable it. Recreate /boot/grub2/grub.cfg > (this is now the correct location on UEFI and BIOS). If you've > accidentally stepped on the forwarding /boot/efi/EFI/fedora/grub.cfg If you have accidentally done 'grub2-m

Re: Upgrade to Fedora 34 broke the boot menu.

2021-05-08 Thread Chris Murphy
Oh and you can delete any stale *conf files you find in /boot/loader/entries/. That will remove them from the GRUB menu. If you want the rescue kernel+initramfs updated you can just remove them as well. They'll be replaced the next time the kernel is updated, or you can reinstall a kernel. -- Chr

Re: Upgrade to Fedora 34 broke the boot menu.

2021-05-08 Thread Chris Murphy
On Sat, May 8, 2021 at 6:52 AM Björn Persson wrote: > > I used yum system-upgrade to upgrade from Fedora 32 to Fedora 34. Now > Grub complains about not finding some theme files, and then displays a > menu with two kernels from Fedora 29 and a rescue entry from Fedora 28. Does /etc/default/grub c

Re: Upgrade to Fedora 34 broke the boot menu.

2021-05-08 Thread Alexander Ploumistos
On Sat, May 8, 2021 at 6:37 PM Björn Persson wrote: > > Tomasz Torcz wrote: > > Dnia Sat, May 08, 2021 at 02:51:31PM +0200, Björn Persson napisał(a): > > > I used yum system-upgrade to upgrade from Fedora 32 to Fedora 34. Now > > > Grub complains about not finding some theme files, and then displa

Re: Upgrade to Fedora 34 broke the boot menu.

2021-05-08 Thread Björn Persson
Tomasz Torcz wrote: > Dnia Sat, May 08, 2021 at 02:51:31PM +0200, Björn Persson napisał(a): > > I used yum system-upgrade to upgrade from Fedora 32 to Fedora 34. Now > > Grub complains about not finding some theme files, and then displays a > > Missing theme files sounds like > https://bugzil

Re: Upgrade to Fedora 34 broke the boot menu.

2021-05-08 Thread Björn Persson
Neal Gompa wrote: > On Sat, May 8, 2021 at 8:53 AM Björn Persson wrote: > > > > I used yum system-upgrade to upgrade from Fedora 32 to Fedora 34. Now > > Grub complains about not finding some theme files, and then displays a > > menu with two kernels from Fedora 29 and a rescue entry from Fedora 2

Re: Upgrade to Fedora 34 broke the boot menu.

2021-05-08 Thread Tomasz Torcz
Dnia Sat, May 08, 2021 at 02:51:31PM +0200, Björn Persson napisał(a): > I used yum system-upgrade to upgrade from Fedora 32 to Fedora 34. Now > Grub complains about not finding some theme files, and then displays a Missing theme files sounds like https://bugzilla.redhat.com/show_bug.cgi?id=1944

Re: Upgrade to Fedora 34 broke the boot menu.

2021-05-08 Thread Neal Gompa
On Sat, May 8, 2021 at 8:53 AM Björn Persson wrote: > > I used yum system-upgrade to upgrade from Fedora 32 to Fedora 34. Now > Grub complains about not finding some theme files, and then displays a > menu with two kernels from Fedora 29 and a rescue entry from Fedora 28. > If I choose one of the

Upgrade to Fedora 34 broke the boot menu.

2021-05-08 Thread Björn Persson
I used yum system-upgrade to upgrade from Fedora 32 to Fedora 34. Now Grub complains about not finding some theme files, and then displays a menu with two kernels from Fedora 29 and a rescue entry from Fedora 28. If I choose one of the Fedora 29 entries, then Grub unsurprisingly fails to find the k