Ask Your Question

Is it possible to just use a LTS kernel on Fedora?

asked 2018-02-28 00:03:24 -0500

BH2017 gravatar image

updated 2018-03-01 01:20:40 -0500

I do like Fedora, but for some bizarre reason the 4.15.x series kernel seems to not be working well with systemd for me. Several disk-related services (those that mount file systems based on the contents of /etc/fstab) fail and the system fails to boot. This isn't exclusive to Fedora either, for me Debian unstable, openSUSE Tumbleweed and Arch Linux face the same problem with the 4.15.x kernel, despite working fine on earlier kernels. Oddly systemd-free bleeding edge distros like Gentoo and Void do not seem to have this problem.

What I do know is that the 4.14.x and earlier series kernels work fine on Fedora. In fact I'm typing this from F27 running on the 4.14.18 kernel, so is there a way I can use the 4.14.x series kernels, while still getting bug fix and security updates (i.e. I don't want to just stay on 4.14.18 while new patches come out for the 4.14.x series) until this issue is resolved?

EDIT: To be clear, however, I only want the LTS of the kernel, everything else the standard Fedora versions. I thought this'd be obvious, but clearly I expect people to think more like me than they do.

edit retag flag offensive close merge delete


Let me ask you this: since Fedora doesn't supply LTS anything, where are you going to find an LTS kernel and support files that will install and run on Fedora?

sideburns gravatar imagesideburns ( 2018-03-01 02:22:46 -0500 )edit

I was hoping there was a LTS kernel provided by Fedora somewhere I hadn't looked. But if not maybe from a Copr, or some other third party repo. Or a nice automated build tool for creating your own custom kernel whenever a new kernel in the LTS series comes out. But alas it seems I'm out of luck.

BH2017 gravatar imageBH2017 ( 2018-03-01 02:29:10 -0500 )edit

Have you tried the following tutorial? I'm having the same problem as you are and will test this tutorial later today.

maasal gravatar imagemaasal ( 2018-03-18 09:19:24 -0500 )edit

1 Answer

Sort by » oldest newest most voted

answered 2018-02-28 17:02:45 -0500

Aeyoun gravatar image

updated 2018-02-28 17:03:42 -0500

It sounds like your time would be better spent trying to identifying why your disks fail to mount and not trying to cling on to an older kernel release. How do they fail? How do you configure your disks? I’m assuming your customizing your fstab directly? Do you use stable GUIDs to identify your partitions? IS the file’s SELinux labelling intact?

Fedora has no LTS releases, and no edition shipping with the LTS kernel. You can contribute to the stability of the latest stable Kernel release by participating in Kernel regression testing. You can of course pin an older Kernel release, but this isn’t really supported.

You can’t have it both ways: Either you use a slow-moving distribution where nothing changes, or you use a rapid-moving distribution.

edit flag offensive delete link more


The systemd services just time out. Most of my fstab is left as it was from the Anaconda installer, only change I made was adding:

/dev/sdb1    /data    ext4    defaults 0 1

to it. My fstab is: . Frankly I doubt my fstab is relevant as how would it be a problem with the 4.15.x series kernels, but not the 4.14.x series kernel? SELinux labelling is fine, when it's not almost all services fail, in this case it's just the disk-related services that are failing. If SELinux labelling was off I wouldn't be able to boot with any kernel.

BH2017 gravatar imageBH2017 ( 2018-02-28 23:05:39 -0500 )edit

Plus of course if it weren't the 4.15.x kernel and systemd having a problem this shouldn't affect other systemd-using bleeding-edge distros.

BH2017 gravatar imageBH2017 ( 2018-02-28 23:29:03 -0500 )edit

Oh and all I wanted to use the LTS of was the kernel. Everything else bleeding-edge. This is possible on the bleeding-edge distros Arch, Gentoo, Manjaro and Void. I was hoping a LTS kernel was available from somewhere like it is on these distros.

BH2017 gravatar imageBH2017 ( 2018-02-28 23:35:47 -0500 )edit

Wouldn't these regression tests only work if the system could actually successfully boot on the defective kernel? I've read the info at the link you gave, followed one of the links there (namely ) and so far it seems like I actually have to be able to boot the problem kernel and be able to access the command-line to run these tests. When this problem I'm having with the 4.15.x kernels occurs the system doesn't boot to a system where I can actually open a terminal, not even an agetty terminal (i.e. those opened with Ctrl + Alt + Fn).

BH2017 gravatar imageBH2017 ( 2018-03-01 01:05:43 -0500 )edit

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Question Tools

1 follower


Asked: 2018-02-28 00:03:24 -0500

Seen: 398 times

Last updated: Mar 01