Ask Your Question

Kernel version discrepancies

asked 2015-06-09 13:30:18 -0500

Jmlevick gravatar image

Why does this happen?:

image description

image mirror:

I decided to give Ksplice another shot with F22 and although I'm not getting boot errors after running the upgrade this time, I'm getting weird kernel version dicrepancies like in the image, any thoughts?

P.S. Now with F22 DO instances manage their kernels internally, which means upgrading via any method should reflect the most current verision installed.

edit retag flag offensive close merge delete


Try rpm -qa |sort|grep kernel-4.* to see installed kernel packages. Maybe you do have the kernel-4.0.4-303.fc22.x86_64 installed but did not boot with it.

cgonz31 gravatar imagecgonz31 ( 2015-06-09 16:37:20 -0500 )edit

Maybe a problem of old cache...

davidva gravatar imagedavidva ( 2015-06-09 19:46:51 -0500 )edit

Did you restart into the new kernel after the upgrade? uname -r should return the currently running kernel.

bthomas gravatar imagebthomas ( 2015-06-10 20:16:24 -0500 )edit

1 Answer

Sort by ยป oldest newest most voted

answered 2015-06-11 15:57:14 -0500

mhayden gravatar image

Digital Ocean has used external kernels for quite some time now. They actually have a list of approved Fedora kernels that are held outside of your instance. They keep that list of kernels updated fairly regularly but there's usually a lag for new updates. Once the list gets updated, you should be able to switch kernels from within the Digital Ocean control panel.

I haven't found a way around this quite yet. Other providers, like Vultr, allow you to run your own kernels and that might be a better place to test ksplice.

Editorial: My gut says they do this so that users don't run potentially malicious kernels but it still doesn't make good sense even if that's the reason.

edit flag offensive delete link more

Question Tools



Asked: 2015-06-09 13:30:18 -0500

Seen: 142 times

Last updated: Jun 09 '15