Package Details: linux-pf-lts 4.9.24-1

Git Clone URL: https://aur.archlinux.org/linux-pf-lts.git (read-only)
Package Base: linux-pf-lts
Description: Linux kernel and modules with the pf-kernel patchset [-ck patch (BFS included), TuxOnIce, BFQ, UKSM] and aufs3. Long-term support.
Upstream URL: http://pf.natalenko.name/
Licenses: GPL2
Conflicts: linux-pf-lts
Provides: aufs3, linux=4.9.24, linux-pf-lts=4.9
Replaces: aufs3
Submitter: nous
Maintainer: nous
Last Packager: nous
Votes: 2
Popularity: 0.000000
First Submitted: 2015-01-16 18:45
Last Updated: 2017-05-11 08:28

Dependencies (18)

Required by (192)

Sources (12)

Latest Comments

dreieck commented on 2017-01-02 21:29

Indentation of the PKGBUILD is a mess. i.e. a mixture of tabulators and space. Make it uniform (best: avoid tabulators, use spaces).

nous commented on 2016-12-06 14:53

Well... 3.14 reached EOL, long live 4.4-PF-LTS.

nous commented on 2015-10-08 09:26

I intend to keep linux-pf-lts at version 3.14, as it is still one of the official kernel.org's LTS kernels (and it works flawlessly in all my boxes). I won't update to 3.18-LTS or 4.1-LTS unless 3.14 reaches End-Of-Life or I find time and appetite (very unlikely). Please also note that the pf-patchset maintainer doesn't really follow any LTS line but the latest stable.

Therefore, please don't flag it as out-of-date. However, if anybody wants to take over the maintenance of linux-pf-lts and keep it at the most recent upstream LTS, I will gladly orphan it and create a new linux-pf-lts314 or something.

nous commented on 2015-09-12 16:54

I really don't know :-)

Seriously now, I diligently copy the linux-lts config over to linux-pf-lts in every update and only tweak-in the BFS, TuxOnIce and BFQ options. If CONFIG_CGROUP_CPUACCT is active in linux-lts then it was left out by mistake.

However, I no longer have time to follow every single patchlevel update of LTS kernels; that's the reason I've implemented a "trick" in PKGBUILD to let people update the package on their own (see _patchlevel). When I get the time, I'll sync versions and configs. Thanks for the feedback!

Jeffrey4l commented on 2015-09-10 11:31

Why the config doesn't have `CONFIG_CGROUP_CPUACCT=y` configuration?

nous commented on 2015-05-31 20:52

I'm still getting a compile error, even with the linux-lts gcc5 patch:
LD [M] drivers/staging/rtl8187se/r8187se.o
drivers/staging/rtl8187se/r8180_wx.o: In function `ieee80211_increment_scans':
r8180_wx.c:(.text+0x18a0): multiple definition of `ieee80211_increment_scans'
drivers/staging/rtl8187se/r8180_core.o:r8180_core.c:(.text+0x3f70): first defined here

aslmaswd commented on 2015-05-31 14:55

please add this patch
https://projects.archlinux.org/svntogit/packages.git/tree/trunk/gcc5_buildfixes.diff?h=packages/linux-lts

nous commented on 2015-05-31 08:14

The repo is updated to 3.14.43. However, to build closed modules such as nvidia, catalyst or virtualbox, people with gcc!=4.9 would need to export IGNORE_CC_MISMATCH=1 before running dkms or mkinitcpio.

nous commented on 2015-05-30 09:08

I confirmed it.
LD [M] drivers/staging/lustre/lustre/obdclass/obdclass.o
scripts/Makefile.build:455: recipe for target 'drivers/staging' failed
make[1]: *** [drivers/staging] Error 2
Makefile:843: recipe for target 'drivers' failed
make: *** [drivers] Error 2


It also fails at patchlevel 3.14.43, which means that the maintainer of obdclass hasn't yet updated his/her code for gcc5. For the time being I'll downgrade my build box to 4.9 and populate [pfkernel] with 3.14.43...

aslmaswd commented on 2015-05-29 12:11

Failed to build with gcc 5.1.0

All comments