Ask Your Question

Why does uname report the previous version after an upgrade?

asked 2018-05-01 21:33:15 -0500

target4cactus gravatar image

updated 2018-05-02 11:35:14 -0500

I just upgraded from fc27 to fc28 using the procedure listed at:

Before the upgrade uname -a gave me this:

Linux epoch 4.15.3-300.fc27.i686 #1 SMP Tue Feb 13 17:36:43 UTC 2018 i686 i686 i386 GNU/Linux

after the upgrade, I get this:

Linux epoch 4.16.5-200.fc27.i686 #1 SMP Fri Apr 27 19:53:46 UTC 2018 i686 i686 i386 GNU/Linux

The kernel changed from 4.15 to 4.16, but the Fedora version stayed at fc27.

Why doesn't the Fedora version change? I was expecting to see fc28.

The output from rpm -q kernel:

$ rpm -q kernel
edit retag flag offensive close merge delete


Maybe you only did a dnf update as opposed to dnf system-upgrade reboot (needs the package download before)

Or maybe you didn’t choose the most recent kernel in grub when booting.

florian gravatar imageflorian ( 2018-05-01 22:22:34 -0500 )edit

rpm -qa | grep kernel what kernels you have installed.

florian gravatar imageflorian ( 2018-05-01 22:24:11 -0500 )edit

rpm -q kernel would show the same, and perhaps faster.

villykruse gravatar imagevillykruse ( 2018-05-01 23:55:46 -0500 )edit

There is no such thing as 4.16.15 as of now.

florian gravatar imageflorian ( 2018-05-02 08:34:19 -0500 )edit

@florian -- typo, uname reported 4.16.5

target4cactus gravatar imagetarget4cactus ( 2018-05-02 11:36:00 -0500 )edit

2 Answers

Sort by » oldest newest most voted

answered 2018-05-02 00:10:21 -0500

villykruse gravatar image

If indeed you have version 4.16.15-200.fc27.i686 installed, then that one is newer than the fc28 version. For some packages, the fc27 and fc28 versions are built at the same time and have the same version number. Sometimes it can happen that a specific version of a package would appear first in fc27 and only later in fc28. In that case you must downgrade the package to get the fc28 version.

distro-sync should fix that and upgrade or downgrade as necessary to get the fc28 version.

From it seems that kernel version 4.16.15-200.fc27 was never built.

edit flag offensive delete link more


Sorry, that was a typo. uname -a actually reports: 4.16.5-200.fc27.i686

target4cactus gravatar imagetarget4cactus ( 2018-05-02 11:32:27 -0500 )edit

When I run sudo dnf distro-sync what do I use for <package-spec> ?

target4cactus gravatar imagetarget4cactus ( 2018-05-02 11:43:12 -0500 )edit

Nothing, you leave it empty, sudo dnf distro-sync, check what it wants to do before you hit Y

florian gravatar imageflorian ( 2018-05-02 13:23:48 -0500 )edit

answered 2018-05-03 11:11:22 -0500

florian gravatar image

updated 2018-05-03 11:11:38 -0500

Fedora does not delete kernels when upgrading to a new release. In your case, the .fc27 kernel remain after upgrading to F28. Just make sure you boot the latest kernel and uname -r will show you that.

grub will only show kernels that you installed using dnf - only then they get properly added to the grub config. If you manually install some pre-release kernels (not build for Fedora specifically), then you need to add the kernel manually to your boot config. If you really need the .rc kernels, at least get them from Fedora's build system, and use dnf to install.

edit flag offensive delete link more



It turns out the fc28 was installed, but it was not added to grub2.cfg. I added the kernel using grubby and rebuilt the grub configuration with grub-mkconfig.

target4cactus gravatar imagetarget4cactus ( 2018-05-08 13:46:25 -0500 )edit

Question Tools

1 follower


Asked: 2018-05-01 21:33:15 -0500

Seen: 482 times

Last updated: May 03 '18