Ask Your Question

Fedora: installed kernel-headers not the same as reported by (uname -r)

asked 2018-01-28 10:21:15 -0600

ming gravatar image

I just updated my kernel in Fedora as it asked me in a routine pop-up.

After the update, this is what I have:

[root@redberret ~]# dnf info kernel-headers
Last metadata expiration check: 0:19:44 ago on Sun 28 Jan 2018 10:42:11 AM EST.
Installed Packages
Name         : kernel-headers
Version      : 4.14.14
Release      : 300.fc27
Arch         : x86_64
Size         : 4.3 M
Source       : kernel-4.14.14-300.fc27.src.rpm
Repo         : @System
From repo    : updates
Summary      : Header files for the Linux kernel for use by glibc
URL          :
License      : GPLv2 and Redistributable, no modification permitted
Description  : Kernel-headers includes the C header files that specify the interface
             : between the Linux kernel and userspace libraries and programs.  The
             : header files define structures and constants that are needed for
             : building most standard programs and are also needed for rebuilding the
             : glibc package.

[root@redberret ~]# uname -r

My system thinks I have version 4.13.9, while dnf thinks I have 4.14.14 installed.

I tried manually installing 4.14.14 via

[root@redberret ~]# dnf install kernel-4.14.14-300.fc27.x86_64
Last metadata expiration check: 0:26:20 ago on Sun 28 Jan 2018 10:42:11 AM EST.
Package kernel-4.14.14-300.fc27.x86_64 is already installed, skipping.
Dependencies resolved.
Nothing to do.

And I'm still shown 4.13.9 in $(uname -r).

In my GRUB screen, I see two options to boot from: the kernel version 4.13.9, or the rescue drive.

I googled around, and some threads suggested it was because of an old OS installation. It might be the case since I had upgraded this from Fedora 26 to Fedora 27, and that upgrade gave me some troubles.

I'm not quite sure what is going on here... Help would be really appreciated.

edit retag flag offensive close merge delete


I know this question has been here for a while, but just for the record: uname -r shows the identity of the running kernel, which has nothing to do with the kernel-headers package. As you say, Grub2 is only showing you the 4.13.9 option at boot, so it makes sense that it's the kernel you're still running. You can see a list of all installed kernels with rpm -q kernel. The real problem you'd need to solve here is why installing kernel-4.14.14-300.fc27.x86_64 (or any other newer kernel) didn't automatically update the grub config by adding a new boot entry, the way it's supposed to.

FeRDNYC gravatar imageFeRDNYC ( 2018-07-23 05:20:09 -0600 )edit

1 Answer

Sort by ยป oldest newest most voted

answered 2018-01-28 18:58:13 -0600

EnriqueGLez gravatar image

i have the same problem, can you help me? i have problems with my virtual machine

edit flag offensive delete link more


This is how you fix Vmware 14.* to run on fedora 28+ This is likely the error you must be having :

Makefile:974: "Cannot generate   ORC metadata for    CONFIG_UNWINDER_ORC=y, please install    libelf-dev, libelf-devel or    elfutils-libelf-devel".  Stop.

To fix it run the following Installation commands on Terminal ( This is for fedora ) :

-> sudo dnf install libell
-> sudo dnf install elfutils-libelf-devel

And then run Vmware from Applications or terminal : /usr/bin/vmplayer

Infinite4evr gravatar imageInfinite4evr ( 2018-08-20 09:30:53 -0600 )edit

Question Tools

1 follower


Asked: 2018-01-28 10:21:15 -0600

Seen: 2,331 times

Last updated: Jan 28 '18