Upgrade F29 -> F32

[jarmo]

Just upgraded from F29 to F32, all went smoothly except grub menuentry.
Upgrade didn't add entry into grub.cfg.
Boots into F32, but kernel is F29. System is 64bit.
Is this known issue? How to get F32 kernel in use. I can find
it in boot menu.

Jarmo

[Patrick O'Callaghan]

On Mon, 2020-05-18 at 15:52 +0300, jarmo wrote:
>  Just upgraded from F29 to F32, all went smoothly except grub
> menuentry.
>  Upgrade didn't add entry into grub.cfg.
>  Boots into F32, but kernel is F29. System is 64bit.
>  Is this known issue? How to get F32 kernel in use. I can find
>  it in boot menu. 
Upgrading over more than 2 versions isn't supported. Did you go from
F29 to F31 and then F31 to F32?

poc

[Ranjan Maitra]

On Mon, 18 May 2020 13:54:47 +0100 Patrick O'Callaghan <pocallaghan(a)gmail.com&gt;
wrote:

>  On Mon, 2020-05-18 at 15:52 +0300, jarmo wrote:
>  > Just upgraded from F29 to F32, all went smoothly except grub menuentry.
>  > Upgrade didn't add entry into grub.cfg.
>  > Boots into F32, but kernel is F29. System is 64bit.
>  > Is this known issue? How to get F32 kernel in use. I can find
>  > it in boot menu.
>
>  Upgrading over more than 2 versions isn't supported. Did you go from
>  F29 to F31 and then F31 to F32?
>  
I thought that the recommendation was to go n -> n+1 for each n=1,2,\ldots,N-1, where N
is the current release and is created that 12 (or so, after upgrading was possible).

Ranjan (who has stuck with it from N=1 and is very happy to have done so...)

[Patrick O'Callaghan]

On Mon, 2020-05-18 at 08:09 -0500, Ranjan Maitra wrote:
>  On Mon, 18 May 2020 13:54:47 +0100 Patrick O'Callaghan
> <pocallaghan(a)gmail.com&gt; wrote:
>  
>  > On Mon, 2020-05-18 at 15:52 +0300, jarmo wrote:
>  > > Just upgraded from F29 to F32, all went smoothly except grub menuentry.
>  > > Upgrade didn't add entry into grub.cfg.
>  > > Boots into F32, but kernel is F29. System is 64bit.
>  > > Is this known issue? How to get F32 kernel in use. I can find
>  > > it in boot menu.
>  > 
>  > Upgrading over more than 2 versions isn't supported. Did you go from
>  > F29 to F31 and then F31 to F32?
>  > 
>  
>  I thought that the recommendation was to go n -> n+1 for each n=1,2,\ldots,N-1, where
> N is the current release and is created that 12 (or so, after upgrading was possible).
It is, but when N is released N and N-1 are "current" and N-2 goes EOL
a month later, so skipping one release is supported.

poc

[jarmo]

Mon, 18 May 2020 13:54:47 +0100
Patrick O'Callaghan <pocallaghan(a)gmail.com&gt; kirjoitti:


>  Upgrading over more than 2 versions isn't supported. Did you go
> from
>  F29 to F31 and then F31 to F32?
>  
>  poc 
No, direct from 29 to 32 and everything went ok.. No errors
what so ever..

Jarmo

[Richard Shaw]

On Mon, May 18, 2020 at 7:53 AM jarmo <oh1mrr(a)nic.fi&gt; wrote:

>  Just upgraded from F29 to F32, all went smoothly except grub
> menuentry.
>  Upgrade didn't add entry into grub.cfg.
>  Boots into F32, but kernel is F29. System is 64bit.
>  Is this known issue? How to get F32 kernel in use. I can find
>  it in boot menu.
>  
Only a N+2 upgrade is supported, so you probably missed some transition
logic from one of the packages.

Thanks,
Richard

[stan]

On Mon, 18 May 2020 15:52:10 +0300
jarmo <oh1mrr(a)nic.fi&gt; wrote:

>  Just upgraded from F29 to F32, all went smoothly except grub
>  menuentry. Upgrade didn't add entry into grub.cfg.
>  Boots into F32, but kernel is F29. System is 64bit.
>  Is this known issue? How to get F32 kernel in use. I can find
>  it in boot menu. 
I think you probably made the transition to boot snippets with
this upgrade.  Something you can try.  Make sure that 
/etc/default/grub
has the settings you want, then in directory /boot/EFI/efi/fedora run
the command
grub2-mkconfig -o grub.cfg
This is for an efi boot.  If you are running legacy BIOS, the directory
is /boot/grub2, same command.

Check the output of
ls /boot/loader/entries
before and after the config update.  With snippets, if the entry is not
added there for the present kernel, it won't work.  If mkconfig
doesn't work to add it, you could try cloning one of the entries
manually, and changing it to point to the F32 kernel.

A dnf update that includes a new kernel should update everything
properly also because it should use the new tool chain.

[jarmo]

Mon, 18 May 2020 06:13:07 -0700
stan via users <users(a)lists.fedoraproject.org&gt; kirjoitti:


>  This is for an efi boot.  If you are running legacy BIOS, the
>  directory is /boot/grub2, same command. 
I have legacy boot and have tried that, does not add F32 kernel there..

>  Check the output of
>  ls /boot/loader/entries
>  before and after the config update.  With snippets, if the entry is
>  not added there for the present kernel, it won't work.  If mkconfig
>  doesn't work to add it, you could try cloning one of the entries
>  manually, and changing it to point to the F32 kernel. 
 There is F32 shown.. Have to
try that cloning.. 

Jarmo

[Michael Young]

On Mon, 18 May 2020, jarmo wrote:

>  Mon, 18 May 2020 06:13:07 -0700
>  stan via users <users(a)lists.fedoraproject.org&gt; kirjoitti:
>
>
> > This is for an efi boot.  If you are running legacy BIOS, the
> > directory is /boot/grub2, same command.
>
>  I have legacy boot and have tried that, does not add F32 kernel there.. 
I think you either need GRUB_ENABLE_BLSCFG=true set in /etc/default/grub 
which allows you (after rebuilding grub.cfg) to get the kernel 
configuration from the /boot/loader/entries/ files (though this depends on 
how recent your grub boot sector is), or to have GRUB_ENABLE_BLSCFG=false 
and possibly the grubby package installed to get the legacy (ie. before 
BLS) boot behaviour to work.

 	Michael Young

[stan]

On Mon, 18 May 2020 16:30:43 +0100 (BST)
Michael Young <m.a.young(a)durham.ac.uk&gt; wrote:

>  On Mon, 18 May 2020, jarmo wrote:
>  
>  > Mon, 18 May 2020 06:13:07 -0700
>  > stan via users <users(a)lists.fedoraproject.org&gt; kirjoitti:
>  >
>  >  
>  >> This is for an efi boot.  If you are running legacy BIOS, the
>  >> directory is /boot/grub2, same command.  
>  >
>  > I have legacy boot and have tried that, does not add F32 kernel
>  > there..  
>  
>  I think you either need GRUB_ENABLE_BLSCFG=true set in
>  /etc/default/grub which allows you (after rebuilding grub.cfg) to get
>  the kernel configuration from the /boot/loader/entries/ files (though
>  this depends on how recent your grub boot sector is), or to have
>  GRUB_ENABLE_BLSCFG=false and possibly the grubby package installed to
>  get the legacy (ie. before BLS) boot behaviour to work. 
Yes, my /etc/default/grub file has this set to true which is why it
worked for me.  I didn't add that, so it must have been the default on
install; now I know *why* things worked.  Thanks.