Package Details: linux-pf 5.18.6.pf2-1

Git Clone URL: (read-only, click to copy)
Package Base: linux-pf
Description: Linux with the pf-kernel patch (uksm, ZSTD, FSGSBASE and more)
Upstream URL:
Licenses: GPL2
Conflicts: linux-pf
Replaces: kernel26-pf
Submitter: nous
Maintainer: Thaodan
Last Packager: Thaodan
Votes: 205
Popularity: 0.34
First Submitted: 2011-07-24 12:01 (UTC)
Last Updated: 2022-06-25 14:43 (UTC)

Dependencies (19)

Required by (16)

Sources (177)

Pinned Comments

Thaodan commented on 2018-08-05 16:08 (UTC) (edited on 2019-05-07 21:22 (UTC) by Thaodan)

upstream git repo:* (

repo in /etc/pacman.conf:

Server =

import the key

sudo pacman-key --recv-keys BBFE2FD421597395E4FC8C8DF6C85FEE79D661A4
pacman-key --finger BBFE2FD421597395E4FC8C8DF6C85FEE79D661A4
sudo pacman-key --lsign-key  BBFE2FD421597395E4FC8C8DF6C85FEE79D661A4
sudo pacman-key --refresh-keys


gpg: enabled debug flags: memstat
gpg: keydb: handles=1 locks=0 parse=0 get=1
gpg:        build=0 update=0 insert=0 delete=0
gpg:        reset=0 found=1 not=1 cache=0 not=0
gpg: kid_not_found_cache: count=0 peak=0 flushes=0
gpg: sig_cache: total=2 cached=2 good=2 bad=0
gpg: random usage: poolsize=600 mixed=0 polls=0/0 added=0/0
           outmix=0 getlvl1=0/0 getlvl2=0/0
gpg: rndjent stat: collector=0x0000000000000000 calls=0 bytes=0
gpg: secmem usage: 0/32768 bytes in 0 blocks
pub   rsa2048 2015-02-13 [SC]
       BBFE 2FD4 2159 7395 E4FC  8C8D F6C8 5FEE 79D6 61A4
uid        [ ultimativ ] Björn Bidar <>
sub   rsa2048 2015-02-13 [E]

Latest Comments

jaro3 commented on 2022-06-20 16:36 (UTC)

build fails when selecting a processor family:

==> You might be prompted below for some config options

==> Hit <Y> to use your running kernel's config
==> Hit <L> to run 'make localmodconfig'
==> Hit <N> (or just <ENTER>) to build an all-inclusive kernel like stock -ARCH
    (warning: it can take a looong time)

==> Using stock ARCH kernel .config (with BFS and BFQ).

==> Kernel configuration options before build:
    <M> make menuconfig (console menu)
    <N> make nconfig (newer alternative to menuconfig)
    <G> make gconfig (needs gtk)
    <X> make xconfig (needs qt)
    <O> make oldconfig
    <L> make localyesconfig
    <ENTER> to skip configuration and use stock -ARCH defaults
  UPD     scripts/kconfig/mconf-cfg
  HOSTCC  scripts/kconfig/mconf.o
  HOSTCC  scripts/kconfig/lxdialog/checklist.o
  HOSTCC  scripts/kconfig/lxdialog/inputbox.o
  HOSTCC  scripts/kconfig/lxdialog/menubox.o
  HOSTCC  scripts/kconfig/lxdialog/textbox.o
  HOSTCC  scripts/kconfig/lxdialog/util.o
  HOSTCC  scripts/kconfig/lxdialog/yesno.o
  HOSTLD  scripts/kconfig/mconf
configuration written to .config

*** End of the configuration.
*** Execute 'make' to start the build or try 'make help'.

'.config' -> '/root/core/linux-pf.5.18.0.pf1-1/config.local'
==> ERROR: A failure occurred in build().

Thaodan commented on 2022-06-12 05:09 (UTC) (edited on 2022-06-12 05:10 (UTC) by Thaodan)

Hey, I added more prebuilds and extended the optimized builds for the remaining new mcpu mtunes.

Removed Silvermont and Ivybridge from optimzed builds from build_pkgs, add:

  • generic-v2

  • generic-v3

  • generiv-v4

  • rocketlake

  • alderlake

  • zen2

  • zen3

I'm currently looking how to fix loading of external packaged modules. The reason is that is different per optimized build because bpf support, either I avoid bpf, remove that limitation or outphase the packaged modules and prefer dkms instead.

^ @lbatalha

pythonparrot commented on 2022-04-16 17:03 (UTC) (edited on 2022-04-16 17:04 (UTC) by pythonparrot)

sha256sums of v5.15...v5.15-pf5.diff is wrong

==> source で sha256sums ファイルを検証...
    linux-5.15.tar.xz ... 成功
    config.x86_64 ... 成功
    config.i686 ... 成功
    pf_defconfig ... 成功
    linux.preset ... 成功
    v5.15...v5.15-pf5.diff ... 失敗
    prjc_v5.15-r1.patch ... 成功
    90-linux.hook ... 成功
    60-linux.hook ... 成功
    asus_zenith_ii_map.patch ... 成功

lbatalha commented on 2022-02-01 14:01 (UTC) (edited on 2022-02-01 14:40 (UTC) by lbatalha)

ZEN3 needs to be added to the _CPUSUFFIXES_KBUILD list in the PKGBUILD, otherwise when configuring the kernel if you choose ZEN3 from the list the build() step will fail with no error message (it wont enter the An non-generic CPU was selected for this kernel. option select, choosing ZEN2 works, adding ZEN3 to the PKGBUILD fixes this). It also needs adding near line 363 of the PKGBUILD, an entry for ZEN3:

          pkgdesc="${pkgdesc} AMD Zen2 optimized."
          pkgdesc="${pkgdesc} AMD Zen3 optimized."

Quantum1248 commented on 2022-02-01 13:13 (UTC)

build fails when selecting a processor family different from generic-x86-64

Thaodan commented on 2022-01-09 02:14 (UTC)

@maveric7911: Thanks for reporting, fixed.

maveric7911 commented on 2022-01-08 22:01 (UTC)

Config files sha validation needs to be updated, once I updated that in my PKGBUILD it works great. Thanks!

akurei commented on 2022-01-07 11:02 (UTC) (edited on 2022-01-07 15:48 (UTC) by akurei)

Build fails because the two config files don't match their checksum.

==> Validating source files with sha256sums...
    linux-5.15.tar.xz ... Passed
    config.x86_64 ... FAILED
    config.i686 ... FAILED
    pf_defconfig ... Passed
    linux.preset ... Passed
    v5.15...v5.15-pf5.diff ... Passed
    prjc_v5.15-r1.patch ... Passed
    90-linux.hook ... Passed
    60-linux.hook ... Passed
    asus_zenith_ii_map.patch ... Passed
==> ERROR: One or more files did not pass the validity check!

Thaodan commented on 2021-12-05 15:53 (UTC)

@jaro3: Thanks for forwarding, please create an issue on gitlab.

jaro3 commented on 2021-12-05 15:47 (UTC)

5.15.5 has this hdd cache bug:

n3rv commented on 2021-12-03 23:20 (UTC)

build fails if select "...-native optimizations autodetected by GCC" when config

post-factum commented on 2021-08-11 11:30 (UTC) (edited on 2021-08-11 11:44 (UTC) by post-factum)

Consider adding the following provides bits please:


Also, KSMBD-MODULE after the next release.

bartus commented on 2021-07-25 08:22 (UTC) (edited on 2021-07-25 08:22 (UTC) by bartus)

v5.13...v5.13-pf2.diff check sum is wrong.

$curl -s "${source[5]}"|sha256sum -
3fc6dc4e11ff3f5df5f237cfd93d3571afc3fe0e40d55b838508e3552184ebb2  -
$echo ${sha256sums[5]}

post-factum commented on 2021-07-09 13:57 (UTC)

Any luck with keeping this up to date please?

Thaodan commented on 2020-12-22 03:56 (UTC)

@Edu4rdSHL: It will be included in the next build see:

Edu4rdSHL commented on 2020-09-07 05:26 (UTC)

It's possible to include a zen2 (Ryzen 5) processors build in your precompiled packages repo?

Thaodan commented on 2020-08-23 12:43 (UTC)

Currently building the next update, will push it after its done compiling. Was moving so couldn't update. Suspend bug is fixed with new projectc patch.

jaro3 commented on 2020-08-04 01:35 (UTC)

Thanks for the new commit but in the PKGBUILD you still have:


shouldn't this be prjc_v5.7-r3.patch now??

and in the CPU optimized packages you use:


shouldn't this be

pkgdesc="${pkgdesc}... ??

jaro3 commented on 2020-07-26 13:20 (UTC)

Hangs system when entering suspend to RAM :-( Other kernels are OK, what happened in this version?

Althorion commented on 2020-04-01 19:52 (UTC)

Are you still interested in keeping this package alive? Would you like some help with that?

prettyvanilla commented on 2020-03-05 21:38 (UTC)

I noticed in passing that you still specify the base group in this package, which can be removed now after the official repos got rid of the base group some time ago (

Thaodan commented on 2019-12-04 09:08 (UTC)

You are saying this like you entitled to something.

LothaireFR commented on 2019-12-04 08:57 (UTC)

Well, we are in december now, and still nothing.

toki1990 commented on 2019-10-09 19:50 (UTC) (edited on 2019-10-09 19:51 (UTC) by toki1990)

Report for linux-pf 5.3.2-2. build stops When menuconfig is selected after the change is saved ( build completed with yay. but cpu selection not working )

naruto522ru commented on 2019-09-17 10:22 (UTC)

@Thaodan give the status comaintainer @post-factum if he, of course, wants to do so, releases will come out faster, and your task is to collect packages. Well, we won’t forget you because you have kept this project for so many years)))

SolarAquarion commented on 2019-09-04 13:46 (UTC)

Checking for updates and following stuff.

Thaodan commented on 2019-08-24 18:43 (UTC)

@SolarAquarion which have what to do with things package ? this package uses the exact same sources as the one you linked.

SolarAquarion commented on 2019-08-23 16:48 (UTC)

see the official packages by the maintainer

post-factum commented on 2019-06-04 11:46 (UTC)

Consider adding uksmd as an optdep.

Thaodan commented on 2019-05-07 21:23 (UTC)

WARNING: I changed the url to the repo my server. Please look above!

burjui commented on 2019-03-25 12:52 (UTC)

"Description: 6th Gen Core processors including Skylake." Clearly a mistake

aw1cks commented on 2019-03-13 13:32 (UTC)

Updated PKGBUILD for 5.0-pf2 -

Thaodan commented on 2019-02-18 12:35 (UTC)

Do you use some kind of AUR helper?

Thaodan commented on 2019-02-18 12:34 (UTC)

Where did you press G?

lesderid commented on 2019-02-18 12:29 (UTC) (edited on 2019-02-18 12:29 (UTC) by lesderid)

I got some dependency issues on 4.20 (I pressed 'G' for the package name choice):

warning: cannot resolve "linux-pf=4.20.4", a dependency of "linux-pf-preset-default"
warning: cannot resolve "linux-pf-preset", a dependency of "linux-pf-native"
warning: cannot resolve "linux-pf=4.20.4", a dependency of "linux-pf-preset-default"
:: The following packages cannot be upgraded due to unresolvable dependencies:
      linux-pf-native  linux-pf-preset-default

Thaodan commented on 2019-01-14 19:33 (UTC)

I currenty cant push the linux4.20 branch because of an error in the aur because of the recent mariadb/mysql update.

skyfair commented on 2018-08-28 21:32 (UTC)

its working. Thanks!

skyfair commented on 2018-08-27 21:00 (UTC)


Thaodan commented on 2018-08-27 20:56 (UTC)

have you changed the cpu arch?

skyfair commented on 2018-08-27 20:48 (UTC)

Error: the function 'package_linux-pf()' was not found for the split package 'linux-pf'

diddyonlinux commented on 2018-08-20 19:23 (UTC)

Is this supposed to match release cycle?

nazarianin commented on 2018-08-09 16:10 (UTC)

create issue on gitlab.

Thaodan commented on 2018-08-09 15:53 (UTC)

Please be more verbose! If you have a larger issue/bug, post it at gitlab.

Thaodan commented on 2018-08-05 16:09 (UTC)

@atommixz: added doc about adding the repo. see above. Builds aviable are listed in build_pkgs.

Thaodan commented on 2018-08-05 16:08 (UTC) (edited on 2019-05-07 21:22 (UTC) by Thaodan)

upstream git repo:* (

repo in /etc/pacman.conf:

Server =

import the key

sudo pacman-key --recv-keys BBFE2FD421597395E4FC8C8DF6C85FEE79D661A4
pacman-key --finger BBFE2FD421597395E4FC8C8DF6C85FEE79D661A4
sudo pacman-key --lsign-key  BBFE2FD421597395E4FC8C8DF6C85FEE79D661A4
sudo pacman-key --refresh-keys


gpg: enabled debug flags: memstat
gpg: keydb: handles=1 locks=0 parse=0 get=1
gpg:        build=0 update=0 insert=0 delete=0
gpg:        reset=0 found=1 not=1 cache=0 not=0
gpg: kid_not_found_cache: count=0 peak=0 flushes=0
gpg: sig_cache: total=2 cached=2 good=2 bad=0
gpg: random usage: poolsize=600 mixed=0 polls=0/0 added=0/0
           outmix=0 getlvl1=0/0 getlvl2=0/0
gpg: rndjent stat: collector=0x0000000000000000 calls=0 bytes=0
gpg: secmem usage: 0/32768 bytes in 0 blocks
pub   rsa2048 2015-02-13 [SC]
       BBFE 2FD4 2159 7395 E4FC  8C8D F6C8 5FEE 79D6 61A4
uid        [ ultimativ ] Björn Bidar <>
sub   rsa2048 2015-02-13 [E]

whoami commented on 2018-08-05 16:03 (UTC)

ok, it's works with sudo pacman-key --lsign-key F6C85FEE79D661A4

whoami commented on 2018-08-05 15:21 (UTC) (edited on 2018-08-05 15:27 (UTC) by whoami)

I have "signature is missing error" for your key in repo now. Can't fix. I do on fresh system:

sudo rm -rf /etc/pacman.d/gnupg
sudo pacman-key --init
sudo pacman-key --populate
sudo pacman-key --refresh-key
sudo pacman-key --recv-keys BBFE2FD421597395E4FC8C8DF6C85FEE79D661A4
sudo pacman-key --lsign-key BBFE2FD421597395E4FC8C8DF6C85FEE79D661A4
~ $ LANGUAGE=C sudo pacman -Syyu
error: home-thaodan: signature from "Björn Bidar" is invalid
:: Synchronizing package databases...
 core is up to date
 extra is up to date
 community is up to date
 multilib is up to date
 home-thaodan                  37,0 KiB  12,0M/s 00:00 [#############################] 100%
 home-thaodan.sig             310,0   B  0,00B/s 00:00 [#############################] 100%
error: home-thaodan: signature from "Björn Bidar" is invalid
error: failed to update home-thaodan (invalid or corrupted database (PGP signature))
error: failed to synchronize all databases

Thaodan commented on 2018-08-05 13:54 (UTC)

@atommixz fixed, it was an issue with the DB.

whoami commented on 2018-08-05 11:44 (UTC) (edited on 2018-08-05 11:45 (UTC) by whoami)

something wrong with your repo

error: failed retrieving file 'linux-pf-4.17.4-1-x86_64.pkg.tar.xz' from : The requested URL returned error: 404

Thaodan commented on 2018-08-02 00:27 (UTC)

@tydynrain @keembre: sorry for the issue, the bug only triggered using non-batch generic builds. I found the bug and rewrote the build script. to build optimized builds just launch the build script like this: ./build_pkg <cpu> Or just with no args to build all cpu arches, just read the log and the script.</cpu>

tydynrain commented on 2018-08-01 21:17 (UTC)

@keembre, thank you for that. That line in the PKGBUILD for me appeared as:

_package() {

so I had to change it to:

package_linux-pf() {

to make it work.

Thank you again for the suggestion. It was very much appreciated.

keembre commented on 2018-08-01 14:27 (UTC)

@tydynrain line 305 add "package" before "_linux-pf" so it says "package_linux-pf"

it should compile

tydynrain commented on 2018-08-01 03:06 (UTC) (edited on 2018-08-01 03:07 (UTC) by tydynrain)

It compiled for a good while, then this error stopped the process:

==> Entering fakeroot environment...

==> ERROR: Missing package_linux-pf() function for split package 'linux-pf'

Thaodan commented on 2018-07-31 23:19 (UTC)

@tydynrain: sorry for the hassle, fixed now. See git log.

tydynrain commented on 2018-07-31 18:41 (UTC)

Error during update:

-> Found 90-linux.hook

-> Found 60-linux.hook

==> ERROR: batch_opts was not found in the build directory and is not a URL.

Thaodan commented on 2018-06-05 19:43 (UTC) (edited on 2018-06-05 19:43 (UTC) by Thaodan)

Updated to latest 4.16. Pushed 4.17 to testing branch till 4.17 is merged in arch:

Thaodan commented on 2018-05-27 14:44 (UTC)

Ok, I didn't updated to gcc 8.1. I will try later after updated to the last version.

Thaodan commented on 2018-05-27 14:43 (UTC)

I build a version right now and it failed without errors. I try a clean chroot pls

tydynrain commented on 2018-05-26 00:14 (UTC) (edited on 2018-05-26 18:05 (UTC) by tydynrain)

I've gotten build errors on three machines for linux-pf since, and no matter what I try, it refuses to build successfully. This is using trizen, but I've also used pacaur, straight makepkg, and aurutils/aursync, but it fails with all of them.

Error Message:

../lib/str_error_r.c: In function ‘str_error_r’:

../lib/str_error_r.c:25:3: error: passing argument 1 to restrict-qualified parameter aliases with argument 5 [-Werror=restrict]

snprintf(buf, buflen, "INTERNAL ERROR: strerror_r(%d, %p, %zd)=%d", errnum, buf, buflen, err);

^~~~~~~~ cc1: all warnings being treated as errors

mv: cannot stat '/tmp/trizen-tydynrain/linux-pf/src/linux-4.16/tools/objtool/.str_error_r.o.tmp': No such file or directory

LD /tmp/trizen-tydynrain/linux-pf/src/linux-4.16/tools/objtool/libsubcmd-in.o

make[3]: *** [Build:22: /tmp/trizen-tydynrain/linux-pf/src/linux-4.16/tools/objtool/str_error_r.o] Error 1

make[3]: *** Waiting for unfinished jobs....

AR /tmp/trizen-tydynrain/linux-pf/src/linux-4.16/tools/objtool/libsubcmd.a

HOSTCC arch/x86/tools/relocs_32.o

HOSTCC arch/x86/tools/relocs_64.o

make[2]: *** [Makefile:46: /tmp/trizen-tydynrain/linux-pf/src/linux-4.16/tools/objtool/objtool-in.o] Error 2

make[1]: *** [Makefile:63: objtool] Error 2

make: *** [Makefile:1687: tools/objtool] Error 2

make: *** Waiting for unfinished jobs....

HOSTCC arch/x86/tools/relocs_common.o

HOSTLD arch/x86/tools/relocs

==> ERROR: A failure occurred in build().


:: Unable to build linux-pf-preset-default - makepkg exited with code: 2

bartus commented on 2018-04-22 11:13 (UTC)

@Thaodan: I have same issue as @simona

==> Starting package_linux-pf-headers()...
cp: cannot stat 'drivers/media/dvb-core/*.h': No such file or directory

header files has been moved to include/media/ folder

simona commented on 2018-04-21 09:01 (UTC)

cp: impossibile eseguire stat di 'drivers/media/dvb-core/*.h': File o directory non esistente ==> ERRORE: Si è verificato un errore in package_linux-pf-headers(). L'operazione sta per essere interrotta... :: Errore compilando il/i pacchetto/i linux-pf-headers,linux-pf-preset-default,linux-pf

simona commented on 2018-04-20 16:38 (UTC)


LookTJ commented on 2018-04-12 02:16 (UTC)

==> ERROR: Integrity checks (sha256) differ in size from the source array.

Thaodan commented on 2018-04-08 07:30 (UTC)

the makepkg.conf file was inted for me to build i686 kernel without a clean chroot.

I pushed the next update to a testing branch like before, until 4.16-ARCH in core.

tydynrain commented on 2018-02-28 07:34 (UTC) (edited on 2018-02-28 09:22 (UTC) by tydynrain)

With the latest update (4.15.4-1) the makepkg.conf file has a few errors that prevent a successful build unless I manually fix them.

CARCH="i686" CHOST="i686-pc-linux-gnu"

Those, of course, need to be changed to "x86_64" and "x86_64-pc-linux-gnu" respectively.

Also, there is an extra space between mtune=native and -02 in CFLAGS

CFLAGS="-march=native mtune=native -O2 -pipe -fstack-protector-strong -fno-plt"

Once I changed those, it built successfully.

skyfair commented on 2018-02-22 19:04 (UTC)

kernel is working fine, thank you.

Thaodan commented on 2018-02-02 07:54 (UTC)

As long as 4.15 as is in testing. I pushed 4.14 to my testing branch on gitlab, see here:

I commit every changes needed to all modules for 4.15 here so if you want to grab everything just clone the repo of my repo.

Thaodan commented on 2017-11-21 21:41 (UTC)

As long as 4.14 I pushed 4.14 to my testing branch on gitlab, see here: Please report any issues there.

Thaodan commented on 2017-11-05 02:29 (UTC)

sorry for the delay forgot to push that to changed the url and such.

post-factum commented on 2017-10-22 17:34 (UTC)

Please use this URL to obtain patch:<base>...v<base>-pf<release>.diff e.g. since I'll be moving files to GitHub completely soon.

post-factum commented on 2017-09-06 14:49 (UTC)

Meanwhile, v4.13-pf1 is pushed…

fenrig commented on 2017-08-29 19:59 (UTC) According to ck-hack blog the bug is already fixed since 15 aug, or are there still some issues?

ibrokemypie commented on 2017-08-21 07:25 (UTC)

v4.12-pf7 is out >Finally, MuQSS CPU scheduler is fixed and merged, replacing VRQ. Works okay as usual, and I think I should do some benchmarking a-la MuQSS vs VRQ, because perceptional difference is minimal.

Thaodan commented on 2017-08-12 22:36 (UTC)

Please look at the pf website and see the issues reported there. Muqss is still broken. I'll make a experimental 4.12 branch monday.

skyfair commented on 2017-08-12 10:57 (UTC)

linux-pf 4.12.6 is out! update please

xianai commented on 2017-07-10 07:59 (UTC)

uksm for v4.12

tamjan commented on 2017-07-06 08:45 (UTC)

And, AUFS branch should work with pf version 4.11.7

bruceutut commented on 2017-07-04 04:02 (UTC)

linux-pf7 just released 3 July, update plz

arch_fenrig commented on 2017-05-31 03:03 (UTC)

For docker users who need aufs, you can switch to overlay2 (only if docker containers run on ext4 or xfs) by changing the docker.service file in systemd with ExecStart=/usr/bin/dockerd -H fd:// -s overlay2 Apparently overlay2 should be a lot faster:

2xsaiko commented on 2017-05-30 15:43 (UTC) (edited on 2017-05-30 15:43 (UTC) by 2xsaiko)

Does this have tuxonice or not? In the pkgbuild there doesn't seem to be any reference to it…

2xsaiko commented on 2017-05-29 19:41 (UTC)

And the link is no longer dead.

2xsaiko commented on 2017-05-29 12:39 (UTC) (edited on 2017-05-29 19:41 (UTC) by 2xsaiko)

There's no host, please change link ( EDIT: or rather the host is down EDIT 2: the host reponds to ping, but the webserver appears to be down

wat commented on 2017-05-21 20:48 (UTC)

Please update to 4.11-pf1

xianai commented on 2017-05-17 13:44 (UTC)

uksm for v4.11

Thaodan commented on 2017-05-15 19:31 (UTC)

Also it delays the update process.

Thaodan commented on 2017-05-15 19:29 (UTC)

since I don't use aufs4 please answer if you use it or not:

bruceutut commented on 2017-05-11 13:25 (UTC)

4.11-pf1 now released. plz update.

wat commented on 2017-04-27 21:39 (UTC)

==> Making package: linux-pf 4.10.3-2 (Thu Apr 27 14:34:02 PDT 2017) ==> Checking runtime dependencies... ==> Checking buildtime dependencies... ==> Retrieving sources... -> Found linux-4.10.tar.xz -> Found config -> Found config.x86_64 -> Found linux.preset -> Found patch-4.10-pf3.xz -> Updating aufs4-standalone git repo... Fetching origin -> Found uksm-4.10.patch -> Found 90-linux-pf.hook ==> Validating source files with sha256sums... linux-4.10.tar.xz ... Passed config ... Passed config.x86_64 ... Passed linux.preset ... Passed patch-4.10-pf3.xz ... Passed aufs4-standalone ... Skipped uksm-4.10.patch ... Passed 90-linux-pf.hook ... Passed ==> Extracting sources... -> Extracting linux-4.10.tar.xz with bsdtar -> Extracting patch-4.10-pf3.xz with xz -> Creating working copy of aufs4-standalone git repo... Reset branch 'makepkg' ==> Starting prepare()... ==> Applying pf-kernel patch patching file Documentation/admin-guide/kernel-parameters.txt patching file Documentation/arm64/silicon-errata.txt patching file Documentation/block/00-INDEX The next patch would create the file Documentation/block/bfq-iosched.txt, which already exists! Skipping patch. 1 out of 1 hunk ignored The next patch would create the file Documentation/scheduler/sched-BFS.txt, which already exists! Skipping patch. 1 out of 1 hunk ignored The next patch would create the file Documentation/scheduler/sched-MuQSS.txt, which already exists! Skipping patch. 1 out of 1 hunk ignored patching file Documentation/sysctl/kernel.txt patching file Makefile patching file arch/arm/boot/dts/at91-sama5d2_xplained.dts patching file arch/arm/boot/dts/at91-sama5d4_xplained.dts patching file arch/arm/boot/dts/sama5d2.dtsi patching file arch/arm/configs/qcom_defconfig patching file arch/arm/include/asm/kvm_mmu.h patching file arch/arm/mach-at91/pm.c patching file arch/arm64/Kconfig patching file arch/arm64/include/asm/kvm_mmu.h patching file arch/arm64/kernel/cpufeature.c patching file arch/arm64/kernel/kaslr.c patching file arch/arm64/kvm/hyp/tlb.c patching file arch/arm64/mm/dma-mapping.c patching file arch/arm64/mm/mmu.c patching file arch/c6x/kernel/ptrace.c patching file arch/h8300/kernel/ptrace.c patching file arch/metag/kernel/ptrace.c patching file arch/mips/bcm47xx/buttons.c patching file arch/mips/cavium-octeon/octeon-memcpy.S patching file arch/mips/configs/ip22_defconfig patching file arch/mips/configs/ip27_defconfig patching file arch/mips/configs/lemote2f_defconfig patching file arch/mips/configs/malta_defconfig patching file arch/mips/configs/malta_kvm_defconfig patching file arch/mips/configs/malta_kvm_guest_defconfig patching file arch/mips/configs/maltaup_xpa_defconfig patching file arch/mips/configs/nlm_xlp_defconfig patching file arch/mips/configs/nlm_xlr_defconfig patching file arch/mips/include/asm/checksum.h patching file arch/mips/include/asm/mach-ip27/spaces.h patching file arch/mips/kernel/process.c patching file arch/mips/kernel/ptrace.c patching file arch/mips/lantiq/xway/sysctrl.c patching file arch/mips/mm/sc-ip22.c patching file arch/mips/pic32/pic32mzda/Makefile patching file arch/mips/ralink/prom.c patching file arch/mips/ralink/rt288x.c patching file arch/mips/ralink/rt305x.c patching file arch/mips/ralink/rt3883.c patching file arch/mips/ralink/timer.c patching file arch/mips/sgi-ip22/Platform patching file arch/parisc/include/asm/cacheflush.h patching file arch/parisc/kernel/cache.c patching file arch/parisc/kernel/module.c patching file arch/parisc/kernel/process.c patching file arch/powerpc/boot/ patching file arch/powerpc/crypto/crc32c-vpmsum_glue.c patching file arch/powerpc/include/asm/mmu.h patching file arch/powerpc/include/asm/nohash/pgtable.h patching file arch/powerpc/kernel/cpu_setup_power.S patching file arch/powerpc/kernel/hw_breakpoint.c patching file arch/powerpc/kernel/idle_book3s.S patching file arch/powerpc/lib/sstep.c patching file arch/powerpc/platforms/cell/spufs/sched.c patching file arch/powerpc/sysdev/xics/icp-opal.c patching file arch/powerpc/sysdev/xics/xics-common.c patching file arch/s390/include/asm/processor.h patching file arch/s390/kernel/crash_dump.c patching file arch/s390/kernel/setup.c patching file arch/s390/kernel/topology.c patching file arch/s390/kvm/kvm-s390.c patching file arch/s390/mm/pgtable.c patching file arch/sparc/kernel/ptrace_64.c patching file arch/x86/Kconfig patching file arch/x86/Kconfig.cpu patching file arch/x86/Makefile patching file arch/x86/Makefile_32.cpu patching file arch/x86/events/core.c patching file arch/x86/include/asm/kvm_page_track.h patching file arch/x86/include/asm/module.h patching file arch/x86/include/asm/pkeys.h patching file arch/x86/include/asm/tlbflush.h patching file arch/x86/kernel/cpu/intel_rdt_rdtgroup.c patching file arch/x86/kernel/head64.c patching file arch/x86/kernel/tsc.c patching file arch/x86/kernel/unwind_frame.c patching file arch/x86/kvm/page_track.c patching file arch/x86/kvm/vmx.c patching file arch/x86/kvm/x86.c patching file arch/x86/mm/gup.c patching file arch/x86/mm/kasan_init_64.c patching file arch/x86/pci/xen.c patching file arch/x86/platform/goldfish/goldfish.c patching file arch/xtensa/kernel/setup.c patching file block/Kconfig patching file block/Kconfig.iosched patching file block/Makefile The next patch would create the file block/bfq-cgroup.c, which already exists! Skipping patch. 1 out of 1 hunk ignored The next patch would create the file block/bfq-ioc.c, which already exists! Skipping patch. 1 out of 1 hunk ignored The next patch would create the file block/bfq-iosched.c, which already exists! Skipping patch. 1 out of 1 hunk ignored The next patch would create the file block/bfq-sched.c, which already exists! Skipping patch. 1 out of 1 hunk ignored The next patch would create the file block/bfq.h, which already exists! Skipping patch. 1 out of 1 hunk ignored patching file block/blk-mq.c patching file crypto/Kconfig patching file crypto/Makefile patching file crypto/algif_hash.c patching file crypto/testmgr.h patching file crypto/xts.c patching file drivers/acpi/nfit/core.c patching file drivers/auxdisplay/img-ascii-lcd.c patching file drivers/bcma/main.c patching file drivers/block/loop.c patching file drivers/block/swim.c patching file drivers/bluetooth/ath3k.c patching file drivers/bluetooth/btusb.c patching file drivers/bluetooth/hci_qca.c patching file drivers/char/hw_random/amd-rng.c patching file drivers/char/hw_random/geode-rng.c patching file drivers/char/hw_random/omap-rng.c patching file drivers/char/ipmi/ipmi_msghandler.c patching file drivers/char/ipmi/ipmi_ssif.c patching file drivers/char/ppdev.c patching file drivers/char/snsc.c patching file drivers/char/tpm/tpm-interface.c patching file drivers/char/tpm/tpm_tis.c patching file drivers/char/tpm/tpm_tis_core.c patching file drivers/char/tpm/tpm_tis_core.h patching file drivers/clk/sunxi-ng/ccu-sun6i-a31.c patching file drivers/clk/sunxi-ng/ccu_mp.c patching file drivers/cpufreq/cpufreq.c patching file drivers/cpuidle/sysfs.c patching file drivers/crypto/ccp/ccp-dev.c patching file drivers/crypto/ccp/ccp-dmaengine.c patching file drivers/crypto/s5p-sss.c patching file drivers/crypto/vmx/aes_cbc.c patching file drivers/crypto/vmx/aes_xts.c patching file drivers/dax/dax.c patching file drivers/devfreq/devfreq.c patching file drivers/devfreq/governor.h patching file drivers/devfreq/governor_passive.c patching file drivers/dma/ipu/ipu_irq.c patching file drivers/firmware/efi/arm-runtime.c patching file drivers/gpu/drm/amd/amdgpu/amdgpu_drv.c patching file drivers/gpu/drm/amd/amdgpu/amdgpu_pm.c patching file drivers/gpu/drm/amd/amdgpu/dce_v11_0.c patching file drivers/gpu/drm/amd/amdgpu/gfx_v6_0.c patching file drivers/gpu/drm/amd/amdgpu/si_dpm.c patching file drivers/gpu/drm/ast/ast_drv.h patching file drivers/gpu/drm/ast/ast_main.c patching file drivers/gpu/drm/ast/ast_post.c patching file drivers/gpu/drm/drm_atomic_helper.c patching file drivers/gpu/drm/drm_edid.c patching file drivers/gpu/drm/drm_fb_helper.c patching file drivers/gpu/drm/drm_fops.c patching file drivers/gpu/drm/i915/gvt/handlers.c patching file drivers/gpu/drm/i915/i915_drv.c patching file drivers/gpu/drm/i915/i915_gem.c patching file drivers/gpu/drm/i915/i915_gem_internal.c patching file drivers/gpu/drm/i915/i915_gem_request.c patching file drivers/gpu/drm/i915/i915_gem_stolen.c patching file drivers/gpu/drm/i915/i915_irq.c patching file drivers/gpu/drm/i915/intel_dp.c patching file drivers/gpu/drm/i915/intel_drv.h patching file drivers/gpu/drm/i915/intel_lspcon.c patching file drivers/gpu/drm/i915/intel_opregion.c patching file drivers/gpu/drm/imx/imx-tve.c patching file drivers/gpu/drm/radeon/radeon_bios.c patching file drivers/gpu/drm/ttm/ttm_bo.c patching file drivers/gpu/drm/vmwgfx/vmwgfx_drv.c patching file drivers/gpu/drm/vmwgfx/vmwgfx_drv.h patching file drivers/gpu/drm/vmwgfx/vmwgfx_fifo.c patching file drivers/gpu/drm/vmwgfx/vmwgfx_irq.c patching file drivers/hid/hid-sony.c patching file drivers/hv/channel.c patching file drivers/hv/channel_mgmt.c patching file drivers/hv/connection.c patching file drivers/hv/hv.c patching file drivers/hv/hv_fcopy.c patching file drivers/hv/hv_kvp.c patching file drivers/hv/hv_snapshot.c patching file drivers/hv/hyperv_vmbus.h patching file drivers/hv/ring_buffer.c patching file drivers/hwmon/fam15h_power.c patching file drivers/hwmon/it87.c patching file drivers/hwtracing/coresight/coresight-etm-perf.c patching file drivers/hwtracing/coresight/coresight-stm.c patching file drivers/hwtracing/intel_th/core.c patching file drivers/i2c/busses/i2c-bcm2835.c patching file drivers/i2c/i2c-mux.c patching file drivers/iio/adc/ti_am335x_adc.c patching file drivers/iio/common/hid-sensors/hid-sensor-trigger.c patching file drivers/iio/counter/104-quad-8.c patching file drivers/iio/light/tsl2563.c patching file drivers/iio/magnetometer/ak8974.c patching file drivers/iio/pressure/mpl115.c patching file drivers/iio/pressure/mpl3115.c patching file drivers/infiniband/core/cma.c patching file drivers/infiniband/hw/mlx5/main.c patching file drivers/infiniband/hw/mlx5/srq.c patching file drivers/infiniband/ulp/ipoib/ipoib_cm.c patching file drivers/infiniband/ulp/ipoib/ipoib_main.c patching file drivers/infiniband/ulp/srp/ib_srp.c patching file drivers/infiniband/ulp/srp/ib_srp.h patching file drivers/input/joystick/iforce/iforce-usb.c patching file drivers/input/misc/cm109.c patching file drivers/input/misc/ims-pcu.c patching file drivers/input/misc/yealink.c patching file drivers/input/mouse/alps.c patching file drivers/input/mouse/alps.h patching file drivers/input/mouse/elan_i2c_core.c patching file drivers/input/serio/i8042-x86ia64io.h patching file drivers/input/tablet/hanwang.c patching file drivers/input/tablet/kbtab.c patching file drivers/input/touchscreen/sur40.c patching file drivers/iommu/exynos-iommu.c patching file drivers/iommu/intel-iommu.c patching file drivers/irqchip/irq-gic-v3-its.c patching file drivers/isdn/gigaset/bas-gigaset.c patching file drivers/md/dm-cache-target.c patching file drivers/md/dm-raid.c patching file drivers/md/dm-round-robin.c patching file drivers/md/dm-stats.c patching file drivers/md/dm.c patching file drivers/md/linear.c patching file drivers/md/linear.h patching file drivers/md/raid10.c patching file drivers/md/raid5.c patching file drivers/media/dvb-frontends/cxd2820r_core.c patching file drivers/media/i2c/msp3400-driver.c patching file drivers/media/media-device.c patching file drivers/media/pci/cx18/cx18-gpio.c patching file drivers/media/pci/dm1105/Kconfig patching file drivers/media/pci/ivtv/ivtv-gpio.c patching file drivers/media/pci/ivtv/ivtv-ioctl.c patching file drivers/media/pci/ivtv/ivtv-streams.c patching file drivers/media/platform/am437x/am437x-vpfe.c patching file drivers/media/radio/radio-mr800.c patching file drivers/media/radio/radio-tea5777.c patching file drivers/media/radio/tea575x.c patching file drivers/media/rc/lirc_dev.c patching file drivers/media/rc/rc-main.c patching file drivers/media/rc/serial_ir.c patching file drivers/media/usb/dvb-usb/dvb-usb-firmware.c patching file drivers/media/usb/dvb-usb/dw2102.c patching file drivers/media/usb/uvc/uvc_queue.c patching file drivers/memory/atmel-ebi.c patching file drivers/mfd/ucb1x00-core.c patching file drivers/misc/cxl/cxl.h patching file drivers/misc/cxl/main.c patching file drivers/misc/cxl/pci.c patching file drivers/misc/cxl/vphb.c patching file drivers/misc/mei/bus-fixup.c patching file drivers/misc/mei/init.c patching file drivers/misc/mei/main.c patching file drivers/misc/panel.c patching file drivers/misc/sgi-xp/xpc_channel.c patching file drivers/mmc/core/block.c patching file drivers/mmc/core/mmc.c patching file drivers/mmc/host/sdhci-acpi.c patching file drivers/mmc/host/sdhci-of-arasan.c patching file drivers/mmc/host/sdhci-of-at91.c patching file drivers/mmc/host/sdhci-pci-core.c patching file drivers/mmc/host/sdhci.c patching file drivers/mmc/host/ushc.c patching file drivers/mtd/maps/pmcmsp-flash.c patching file drivers/mtd/nand/fsl_ifc_nand.c patching file drivers/net/bonding/bond_main.c patching file drivers/net/caif/caif_hsi.c patching file drivers/net/can/usb/gs_usb.c patching file drivers/net/can/usb/peak_usb/pcan_usb.c patching file drivers/net/can/usb/usb_8dev.c patching file drivers/net/ethernet/amd/xgbe/xgbe-common.h patching file drivers/net/ethernet/amd/xgbe/xgbe-dev.c patching file drivers/net/ethernet/amd/xgbe/xgbe-drv.c patching file drivers/net/ethernet/amd/xgbe/xgbe-phy-v2.c patching file drivers/net/ethernet/broadcom/genet/bcmgenet.c patching file drivers/net/ethernet/broadcom/genet/bcmmii.c patching file drivers/net/ethernet/marvell/mvpp2.c patching file drivers/net/ethernet/mellanox/mlx5/core/cmd.c patching file drivers/net/ethernet/mellanox/mlx5/core/en.h patching file drivers/net/ethernet/mellanox/mlx5/core/en_ethtool.c patching file drivers/net/ethernet/mellanox/mlx5/core/en_main.c patching file drivers/net/ethernet/mellanox/mlx5/core/en_rep.c patching file drivers/net/ethernet/mellanox/mlx5/core/en_rx.c patching file drivers/net/ethernet/mellanox/mlx5/core/en_tc.c patching file drivers/net/ethernet/mellanox/mlx5/core/en_tx.c patching file drivers/net/ethernet/mellanox/mlx5/core/eswitch.h patching file drivers/net/ethernet/mellanox/mlx5/core/eswitch_offloads.c patching file drivers/net/ethernet/mellanox/mlx5/core/main.c patching file drivers/net/ethernet/mellanox/mlxsw/spectrum_router.c patching file drivers/net/ethernet/ti/Kconfig patching file drivers/net/geneve.c patching file drivers/net/team/team.c patching file drivers/net/tun.c patching file drivers/net/usb/lan78xx.c patching file drivers/net/usb/qmi_wwan.c patching file drivers/net/usb/usbnet.c patching file drivers/net/vrf.c patching file drivers/net/vxlan.c patching file drivers/net/wireless/ath/ath10k/core.c patching file drivers/net/wireless/ath/ath10k/hw.c patching file drivers/net/wireless/ath/ath5k/mac80211-ops.c patching file drivers/net/wireless/ath/ath9k/ar9003_eeprom.h patching file drivers/net/wireless/ath/ath9k/ath9k.h patching file drivers/net/wireless/ath/ath9k/init.c patching file drivers/net/wireless/ath/ath9k/mac.c patching file drivers/net/wireless/ath/ath9k/mac.h patching file drivers/net/wireless/ath/ath9k/main.c patching file drivers/net/wireless/broadcom/brcm80211/brcmfmac/sdio.c patching file drivers/net/wireless/intel/ipw2x00/ipw2100.c patching file drivers/net/wireless/marvell/mwifiex/pcie.c patching file drivers/net/wireless/realtek/rtlwifi/pci.h patching file drivers/net/wireless/realtek/rtlwifi/rtl8192ee/hw.c patching file drivers/net/wireless/realtek/rtlwifi/rtl8821ae/hw.c patching file drivers/net/wireless/realtek/rtlwifi/usb.c patching file drivers/net/wireless/realtek/rtlwifi/usb.h patching file drivers/ntb/test/ntb_perf.c patching file drivers/nvdimm/namespace_devs.c patching file drivers/nvdimm/nd.h patching file drivers/nvdimm/region_devs.c patching file drivers/parport/ieee1284.c patching file drivers/parport/ieee1284_ops.c patching file drivers/parport/share.c patching file drivers/pci/host/pci-hyperv.c patching file drivers/pci/host/pcie-altera.c patching file drivers/pci/hotplug/pnv_php.c patching file drivers/pci/quirks.c patching file drivers/phy/phy-qcom-ufs.c patching file drivers/pinctrl/qcom/pinctrl-msm.c patching file drivers/platform/goldfish/pdev_bus.c patching file drivers/platform/x86/intel_ips.c patching file drivers/power/reset/Kconfig patching file drivers/power/reset/at91-poweroff.c patching file drivers/power/reset/at91-sama5d2_shdwc.c patching file drivers/pwm/pwm-pca9685.c patching file drivers/regulator/core.c patching file drivers/remoteproc/qcom_mdt_loader.c patching file drivers/rtc/Kconfig patching file drivers/rtc/rtc-sun6i.c patching file drivers/rtc/rtc-wm8350.c patching file drivers/s390/block/dcssblk.c patching file drivers/s390/cio/ioasm.c patching file drivers/s390/cio/qdio_thinint.c patching file drivers/scsi/aacraid/src.c patching file drivers/scsi/fnic/fnic_scsi.c patching file drivers/scsi/libiscsi.c patching file drivers/scsi/lpfc/lpfc_hw4.h patching file drivers/scsi/lpfc/lpfc_init.c patching file drivers/scsi/lpfc/lpfc_scsi.c patching file drivers/scsi/lpfc/lpfc_sli.c patching file drivers/scsi/mpt3sas/mpt3sas_base.h patching file drivers/scsi/mpt3sas/mpt3sas_scsih.c patching file drivers/scsi/qla2xxx/qla_attr.c patching file drivers/scsi/qla2xxx/qla_def.h patching file drivers/scsi/qla2xxx/qla_init.c patching file drivers/scsi/qla2xxx/qla_isr.c patching file drivers/scsi/qla2xxx/qla_mid.c patching file drivers/scsi/qla2xxx/qla_os.c patching file drivers/scsi/qla2xxx/qla_target.c patching file drivers/scsi/scsi_dh.c patching file drivers/scsi/scsi_lib.c patching file drivers/scsi/scsi_priv.h patching file drivers/scsi/sd.c patching file drivers/scsi/snic/snic_scsi.c patching file drivers/scsi/storvsc_drv.c patching file drivers/spi/spi-s3c64xx.c patching file drivers/staging/comedi/drivers/ni_mio_common.c patching file drivers/staging/greybus/loopback.c patching file drivers/staging/lustre/lnet/lnet/lib-eq.c patching file drivers/staging/lustre/lnet/selftest/rpc.c patching file drivers/staging/rtl8188eu/core/rtw_recv.c patching file drivers/staging/rtl8712/rtl871x_recv.c patching file drivers/staging/rts5208/rtsx.c patching file drivers/staging/speakup/speakup_acntpc.c patching file drivers/staging/speakup/speakup_apollo.c patching file drivers/staging/speakup/speakup_decext.c patching file drivers/staging/speakup/speakup_decpc.c patching file drivers/staging/speakup/speakup_dectlk.c patching file drivers/staging/speakup/speakup_dtlk.c patching file drivers/staging/speakup/speakup_keypc.c patching file drivers/staging/speakup/synth.c patching file drivers/staging/unisys/visornic/visornic_main.c patching file drivers/target/target_core_device.c patching file drivers/target/target_core_pscsi.c patching file drivers/target/target_core_sbc.c patching file drivers/target/target_core_tpg.c patching file drivers/target/target_core_transport.c patching file drivers/target/target_core_user.c patching file drivers/tty/n_hdlc.c patching file drivers/tty/serial/8250/8250_pci.c patching file drivers/tty/serial/msm_serial.c patching file drivers/tty/serial/samsung.c patching file drivers/usb/class/usbtmc.c patching file drivers/usb/core/config.c patching file drivers/usb/core/hub.c patching file drivers/usb/core/quirks.c patching file drivers/usb/dwc3/dwc3-omap.c patching file drivers/usb/dwc3/gadget.c patching file drivers/usb/dwc3/gadget.h patching file drivers/usb/gadget/function/f_acm.c patching file drivers/usb/gadget/function/f_fs.c patching file drivers/usb/gadget/function/f_hid.c patching file drivers/usb/gadget/function/f_uvc.c patching file drivers/usb/gadget/udc/core.c patching file drivers/usb/gadget/udc/dummy_hcd.c patching file drivers/usb/gadget/udc/fsl_udc_core.c patching file drivers/usb/host/ohci-at91.c patching file drivers/usb/host/xhci-dbg.c patching file drivers/usb/host/xhci-plat.c patching file drivers/usb/misc/idmouse.c patching file drivers/usb/misc/iowarrior.c patching file drivers/usb/misc/lvstest.c patching file drivers/usb/misc/uss720.c patching file drivers/usb/musb/da8xx.c patching file drivers/usb/musb/musb_core.c patching file drivers/usb/musb/musb_cppi41.c patching file drivers/usb/serial/ark3116.c patching file drivers/usb/serial/console.c patching file drivers/usb/serial/cp210x.c patching file drivers/usb/serial/digi_acceleport.c patching file drivers/usb/serial/ftdi_sio.c patching file drivers/usb/serial/io_ti.c patching file drivers/usb/serial/mos7840.c patching file drivers/usb/serial/omninet.c patching file drivers/usb/serial/opticon.c patching file drivers/usb/serial/option.c patching file drivers/usb/serial/qcserial.c patching file drivers/usb/serial/safe_serial.c patching file drivers/usb/serial/spcp8x5.c patching file drivers/usb/wusbcore/wa-hc.c patching file drivers/uwb/hwa-rc.c patching file drivers/uwb/i1480/dfu/usb.c patching file drivers/vfio/vfio.c patching file drivers/video/console/fbcon.c patching file drivers/video/fbdev/omap/hwa742.c patching file drivers/video/fbdev/pxafb.c patching file drivers/virtio/virtio_balloon.c patching file drivers/vme/vme.c patching file drivers/w1/masters/ds2490.c patching file drivers/w1/w1.c patching file drivers/xen/xen-acpi-processor.c patching file fs/afs/mntpt.c patching file fs/afs/vlocation.c patching file fs/autofs4/waitq.c patching file fs/btrfs/extent-tree.c patching file fs/btrfs/inode-map.c patching file fs/btrfs/inode.c patching file fs/ceph/addr.c patching file fs/ceph/mds_client.c patching file fs/cifs/cifs_dfs_ref.c patching file fs/cifs/file.c patching file fs/crypto/crypto.c patching file fs/crypto/fname.c patching file fs/crypto/fscrypt_private.h patching file fs/crypto/keyinfo.c patching file fs/debugfs/inode.c patching file fs/ext4/extents.c patching file fs/ext4/inline.c patching file fs/ext4/inode.c patching file fs/ext4/mballoc.c patching file fs/ext4/namei.c patching file fs/ext4/super.c patching file fs/ext4/xattr.c patching file fs/ext4/xattr.h patching file fs/f2fs/dir.c patching file fs/f2fs/extent_cache.c patching file fs/f2fs/f2fs.h patching file fs/f2fs/gc.c patching file fs/f2fs/segment.c patching file fs/f2fs/segment.h patching file fs/f2fs/super.c patching file fs/fat/inode.c patching file fs/fuse/file.c patching file fs/gfs2/glock.c patching file fs/gfs2/incore.h patching file fs/jbd2/journal.c patching file fs/jbd2/revoke.c patching file fs/jbd2/transaction.c patching file fs/mount.h patching file fs/namei.c patching file fs/namespace.c patching file fs/nfs/flexfilelayout/flexfilelayout.c patching file fs/nfs/namespace.c patching file fs/nfs/nfs42proc.c patching file fs/nfs/nfs4namespace.c patching file fs/nfs/nfs4proc.c patching file fs/nfs/nfs4xdr.c patching file fs/nfsd/vfs.c patching file fs/orangefs/super.c patching file fs/pnode.c patching file fs/pnode.h patching file fs/proc/base.c patching file fs/super.c patching file fs/xfs/xfs_iomap.c patching file include/acpi/platform/acenv.h The next patch would create the file include/acpi/platform/acintel.h, which already exists! Skipping patch. 1 out of 1 hunk ignored patching file include/crypto/algapi.h patching file include/drm/drmP.h patching file include/linux/blkdev.h patching file include/linux/ccp.h patching file include/linux/ceph/osdmap.h patching file include/linux/compat.h patching file include/linux/dccp.h patching file include/linux/debugfs.h patching file include/linux/devfreq.h patching file include/linux/freezer.h patching file include/linux/fsl_ifc.h patching file include/linux/hyperv.h patching file include/linux/iio/sw_device.h patching file include/linux/init_task.h patching file include/linux/intel-iommu.h patching file include/linux/ioprio.h patching file include/linux/libnvdimm.h patching file include/linux/lockd/lockd.h patching file include/linux/log2.h patching file include/linux/mmzone.h patching file include/linux/mount.h patching file include/linux/netdevice.h patching file include/linux/ptr_ring.h patching file include/linux/sched.h patching file include/linux/sched/prio.h The next patch would create the file include/linux/skip_list.h, which already exists! Skipping patch. 1 out of 1 hunk ignored patching file include/linux/swap.h patching file include/linux/usb/quirks.h patching file include/linux/user_namespace.h patching file include/rdma/ib_sa.h patching file include/scsi/libiscsi.h patching file include/scsi/scsi_device.h patching file include/soc/at91/at91sam9_ddrsdr.h patching file include/target/target_core_base.h patching file include/trace/events/syscalls.h patching file include/uapi/linux/fs.h patching file include/uapi/linux/packet_diag.h patching file include/uapi/linux/sched.h patching file init/Kconfig patching file init/main.c patching file ipc/shm.c patching file kernel/Kconfig.hz patching file kernel/Kconfig.preempt patching file kernel/Makefile patching file kernel/audit.c patching file kernel/audit.h patching file kernel/auditsc.c patching file kernel/cgroup_pids.c patching file kernel/delayacct.c patching file kernel/events/core.c patching file kernel/exit.c patching file kernel/futex.c patching file kernel/irq/Kconfig patching file kernel/irq/manage.c patching file kernel/kthread.c patching file kernel/locking/rwsem-spinlock.c patching file kernel/membarrier.c patching file kernel/memremap.c patching file kernel/module.c patching file kernel/sched/Makefile The next patch would create the file kernel/sched/MuQSS.c, which already exists! Skipping patch. 1 out of 1 hunk ignored The next patch would create the file kernel/sched/MuQSS.h, which already exists! Skipping patch. 1 out of 1 hunk ignored patching file kernel/sched/cpufreq.c patching file kernel/sched/cpufreq_schedutil.c patching file kernel/sched/cputime.c patching file kernel/sched/deadline.c patching file kernel/sched/idle.c patching file kernel/sched/loadavg.c patching file kernel/sched/rt.c patching file kernel/sched/sched.h patching file kernel/sched/stats.c patching file kernel/signal.c The next patch would create the file kernel/skip_list.c, which already exists! Skipping patch. 1 out of 1 hunk ignored patching file kernel/sysctl.c patching file kernel/time/clockevents.c patching file kernel/time/hrtimer.c patching file kernel/time/posix-cpu-timers.c patching file kernel/time/timer.c patching file kernel/trace/trace.c patching file kernel/trace/trace_benchmark.c patching file kernel/trace/trace_selftest.c patching file kernel/ucount.c patching file mm/backing-dev.c patching file mm/filemap.c patching file mm/kasan/quarantine.c patching file mm/memcontrol.c patching file mm/mlock.c patching file mm/page_alloc.c patching file mm/percpu.c patching file mm/vmpressure.c patching file mm/vmscan.c patching file mm/workingset.c patching file net/bridge/br_forward.c patching file net/bridge/br_input.c patching file net/bridge/br_netfilter_hooks.c patching file net/ceph/osd_client.c patching file net/ceph/osdmap.c patching file net/core/dev.c patching file net/core/net-sysfs.c patching file net/core/netclassid_cgroup.c patching file net/core/pktgen.c patching file net/core/skbuff.c patching file net/core/sock.c patching file net/dccp/ccids/ccid2.c patching file net/dccp/input.c patching file net/dccp/ipv4.c patching file net/dccp/ipv6.c patching file net/dccp/minisocks.c patching file net/ipv4/af_inet.c patching file net/ipv4/fib_frontend.c patching file net/ipv4/ip_sockglue.c patching file net/ipv4/route.c patching file net/ipv4/tcp_input.c patching file net/ipv4/tcp_ipv4.c patching file net/ipv4/tcp_minisocks.c patching file net/ipv4/tcp_timer.c patching file net/ipv6/ip6_fib.c patching file net/ipv6/ip6_offload.c patching file net/ipv6/ip6_output.c patching file net/ipv6/ip6_vti.c patching file net/ipv6/netfilter/nf_conntrack_reasm.c patching file net/ipv6/tcp_ipv6.c patching file net/ipv6/udp.c patching file net/l2tp/l2tp_ip.c patching file net/mac80211/agg-rx.c patching file net/mac80211/pm.c patching file net/mac80211/rx.c patching file net/mac80211/sta_info.h patching file net/mac80211/status.c patching file net/mpls/af_mpls.c patching file net/netfilter/nf_conntrack_helper.c patching file net/netlink/genetlink.c patching file net/openvswitch/conntrack.c patching file net/openvswitch/flow_netlink.c patching file net/packet/af_packet.c patching file net/sched/act_api.c patching file net/sched/act_connmark.c patching file net/sched/act_skbmod.c patching file net/sctp/protocol.c patching file net/sctp/socket.c patching file net/socket.c patching file net/strparser/strparser.c patching file net/sunrpc/xprtrdma/rpc_rdma.c patching file net/sunrpc/xprtrdma/transport.c patching file net/sunrpc/xprtrdma/verbs.c patching file net/sunrpc/xprtrdma/xprt_rdma.h patching file net/unix/garbage.c patching file net/wireless/nl80211.c patching file net/xfrm/xfrm_policy.c patching file net/xfrm/xfrm_user.c patching file samples/seccomp/bpf-helper.h patching file security/integrity/ima/ima.h patching file security/integrity/ima/ima_api.c patching file security/integrity/ima/ima_main.c patching file sound/core/seq/seq_clientmgr.c patching file sound/core/seq/seq_fifo.c patching file sound/core/seq/seq_memory.c patching file sound/core/seq/seq_memory.h patching file sound/core/timer.c patching file sound/pci/ctxfi/cthw20k1.c patching file sound/pci/ctxfi/cthw20k2.c patching file sound/pci/hda/hda_intel.c patching file sound/pci/hda/patch_realtek.c patching file sound/pci/maestro3.c patching file sound/soc/codecs/rt5631.c patching file sound/soc/codecs/wm8350.c patching file sound/soc/codecs/wm8900.c patching file sound/soc/codecs/wm9713.c patching file sound/soc/soc-dapm.c patching file sound/usb/line6/pcm.c patching file tools/include/linux/log2.h patching file tools/testing/ktest/ patching file virt/kvm/arm/vgic/vgic-irqfd.c patching file virt/kvm/arm/vgic/vgic-mmio.c ==> ERROR: A failure occurred in prepare(). Aborting...

bruceutut commented on 2017-04-08 05:16 (UTC)

should update to pf3 plz

bruceutut commented on 2017-03-21 00:54 (UTC)

error `missing file 99-linux-pf.hook` when packaging fixed by changing it to 90

Thaodan commented on 2017-03-20 10:42 (UTC)

I've changed the source however the patching is just fine.

mo3r commented on 2017-03-20 10:35 (UTC) (edited on 2017-03-20 10:37 (UTC) by mo3r)

Pls make change link the kernel source from ftp to https Ftp now closed on Also a building process still have failure on a prepare stage: The next patch would create the file Documentation/block/bfq-iosched.txt, which already exists! Skipping patch. 1 out of 1 hunk ignored The next patch would create the file Documentation/scheduler/sched-BFS.txt, which already exists! Skipping patch. 1 out of 1 hunk ignored The next patch would create the file Documentation/scheduler/sched-MuQSS.txt, which already exists! Skipping patch. 1 out of 1 hunk ignored ... The next patch would create the file block/bfq-cgroup.c, which already exists! Skipping patch. 1 out of 1 hunk ignored The next patch would create the file block/bfq-ioc.c, which already exists! Skipping patch. 1 out of 1 hunk ignored The next patch would create the file block/bfq-iosched.c, which already exists! Skipping patch. 1 out of 1 hunk ignored The next patch would create the file block/bfq-sched.c, which already exists! Skipping patch. 1 out of 1 hunk ignored The next patch would create the file block/bfq.h, which already exists! Skipping patch. 1 out of 1 hunk ignored ... The next patch would create the file include/acpi/platform/acintel.h, which already exists! Skipping patch. 1 out of 1 hunk ignored ... The next patch would create the file include/linux/skip_list.h, which already exists! Skipping patch. 1 out of 1 hunk ignored ... The next patch would create the file kernel/sched/MuQSS.c, which already exists! Skipping patch. 1 out of 1 hunk ignored The next patch would create the file kernel/sched/MuQSS.h, which already exists! Skipping patch. 1 out of 1 hunk ignored ... The next patch would create the file kernel/skip_list.c, which already exists! Skipping patch. 1 out of 1 hunk ignored ... ==> ERROR: A failure occurred in prepare(). Aborting...

post-factum commented on 2017-03-08 18:29 (UTC)

> Maybe, some magic happened recently, and it was fixed, I have to check TOI repo and try to build some test kernel. But without promises. Okay, I've built test kernel with TOI enabled, and it still doesn't work with my disk layout. So no way.

xianai commented on 2017-03-01 03:08 (UTC)

Hi, UKSM new release is out. For v4.10 download link: any issues please feedback on

post-factum commented on 2017-02-23 18:06 (UTC)

...fixed here:

post-factum commented on 2017-02-23 18:02 (UTC)

For UKSM, orig_pte should be replaced with vmf->orig_pte due to API changes.

walkindude commented on 2017-02-23 16:06 (UTC)

-> Found patch-4.10-pf1.xz -> Updating aufs4-standalone git repo... Fetching origin -> Downloading uksm-4.9.patch... % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 0 0 0 0 0 0 0 0 --:--:-- 0:00:02 --:--:-- 0 curl: (22) The requested URL returned error: 404 Not Found ==> ERROR: Failure while downloading Aborting... ==> ERROR: Makepkg was unable to build linux-pf. ==> Restart building linux-pf ? [y/N] ==> --------------------------------- ==>

aricart commented on 2017-02-23 01:51 (UTC)

Won't compile with UKSM patch for me. mm/memory.c: In function ‘wp_page_copy’: mm/memory.c:2192:21: error: ‘orig_pte’ undeclared (first use in this function) uksm_cow_pte(vma, orig_pte); ^~~~~~~~ mm/memory.c:2192:21: note: each undeclared identifier is reported only once for each function it appears in make[1]: *** [scripts/ mm/memory.o] Error 1

post-factum commented on 2017-02-22 19:11 (UTC)

You don't need DCCP patch, it is already in 4.10.

xianai commented on 2017-02-22 13:40 (UTC)

@post-factum, Yes, it seems nothing need to be done from v4.9..v4.10 for uksm. :-) There are two pending bug-fixing patches from staff in Huawei Inc. need to be reviewed and patched back to uksm. But I don't think most desktop users will bump into them. So you may use post-factum's patch for a while. I am currently out of office for a few days. After that I will release a new version.

post-factum commented on 2017-02-21 17:07 (UTC)

The same for aufs4 [1]. [1]

post-factum commented on 2017-02-21 17:02 (UTC)

Thaodan, wanna try? [1] git merge uksm-4.9 on top of v4.10 just worked for me, but I haven't compiled it. Feel free to test. [1]

Thaodan commented on 2017-02-20 20:54 (UTC)

I'm currently waiting for uksm 4.10 and aufs4 4.10.

post-factum commented on 2017-02-20 19:34 (UTC)

Sorry, TOI is a mess and does not work for me. Honestly, I've tried to fix it, but got lost in locking mechanism that breaks cycle with RAID+LUKS+Btrfs for me, so I just abandoned it. Unfortunately, I got no help from Nigel. Maybe, some magic happened recently, and it was fixed, I have to check TOI repo and try to build some test kernel. But without promises.

nous commented on 2017-02-17 07:48 (UTC)

I've had a talk with Oleksandr (the maintainer of the pf patchset) about ToI, because it had stopped working for me even for the linux-pt-lts-3.14 (now at 4.4) series kernel I maintain, because of the backports, and I too have dropped it from the kernel config. If you don't mind running a slightly outdated kernel, you could get a copy of linux-pf-lts at around 3.14.65 or lower, which I remember used to work very well - at a point I had more than 150 hibernation/resume cycles on my laptop.

quequotion commented on 2017-02-15 05:46 (UTC)

TuxOnIce is no longer included with linux-pf since 4.6-pf1: Not sure why; git repository still gets updates: I note that patchset releases have stopped. No other hibernation option works for me; I need this back! I'm fumbling through a custom pkgbuild myself, but it's been complicated. Even if I ever figure it out, are we going to need to fork this package? (ie, linux-pf-uksm; linux-pf-tui; linux-pf-ut; etc) or is there some expectation of TUI to come back some day? I notice a branch "for-linus" in the repo--is this going in to mainline?

xianai commented on 2017-01-09 12:08 (UTC)

If uksm patch does not apply cleanly to 4.9.1, the updated patch is:

rubdos commented on 2017-01-06 12:12 (UTC) (edited on 2017-01-06 18:00 (UTC) by rubdos)

Doesn't compile from a clean environment here: EDIT: I cloned your gitlab repo, and I'm editing this comment from it.

Thaodan commented on 2016-12-15 08:17 (UTC)

i pushed the branch now, please report any issues there.

Thaodan commented on 2016-12-15 08:04 (UTC)

thanks I'll updated the pkg to 4.9 in the 4.9 branch please see on gitlab:

xianai commented on 2016-12-15 07:59 (UTC)

I've patched v4.9 kernel and tested it on my machine. However, v4.8..v4.9 contains some non-trivial changes in mmap.c, which means someone of you may want to do additional test on this patch to ensure there is no regression. In case you find anything unusual, please report to me.

Thaodan commented on 2016-12-13 11:20 (UTC)

I updated the pkg to the latest 4.8.x version. UKSM and AUF4 aren't ready for 4.9.1-pf.

mbilker commented on 2016-11-28 16:28 (UTC)

Sorry for flagging the package. I didn't see that the pkgver logic used the pf revision and not the kernel patch level.

xianai commented on 2016-11-07 03:05 (UTC)

@Thaodan Ok, I'll do this next time.

Thaodan commented on 2016-10-31 03:16 (UTC)

I think that was the reason. Please change the version number whatever change you do. Or I get issues when detecting errors and failures or even why I didn't if the patch is valid.

xianai commented on 2016-10-31 02:04 (UTC)

I fixed a kernel warning in uksm-4.8.patch. It's a trivial fix, so I updated the patch on the project site without changing the patch version number. Did that make the checksums change?

Thaodan commented on 2016-10-27 21:14 (UTC)

dont know why the checksums were changed. uksm is out of uksm but inclued by me.

maclinuxfree commented on 2016-10-27 21:09 (UTC)

"uksm-4.8.patch failed the validity check" for me, too. isn´t uksm out of linux-pf?

ijanos commented on 2016-10-24 17:42 (UTC)

uksm-4.8.patch failed the validity check

Thaodan commented on 2016-10-24 10:57 (UTC)

Bumblebee issue is fixed for my system please test again. See the bugtracker entry for updates on the issue and please report errors/success on it.

Thaodan commented on 2016-10-18 19:44 (UTC)

the freeze but cause by bfs/muqss is fixed. However at least for me and somen manjaro user bumblebee doesn't work, see:

Thaodan commented on 2016-10-16 18:51 (UTC)

Can you login into your tty or how do you get the logs? Did you try another 4.8 kernel like the ARCH one?

uudruid74 commented on 2016-10-16 18:40 (UTC)

I'm having the same problem except that I don't use Plymouth. I do have the boot logo turned on, which should be the very first thing the kernel does, but the whole screen is white and stays white and I get nothing at all on the screen. I'm pretty sure it was working with 4.7. The journal of a booting kernel is here :

Thaodan commented on 2016-10-11 08:51 (UTC)

please see this conversation on twitter, about the current status on the issue: try to boot with the arch kernel and poste your output of: journalctl -b-1 -k

Vistaus commented on 2016-10-11 08:40 (UTC)

The update to linux-pf-4.8.x makes my laptop unbootable. After selecting the kernel in Grub, the boot stops right after loading Plymouth so I can't even reach a tty from there. Tried several reboots and they all end up the same. Going back to linux-pf-4.7.x solves the issue; I can boot fine using that one. I'm using a Dell Chromebook 13 with Arch Linux fully updated and have had no issues with any of the software or hardware except that the aforementioned 4.8.x pf-kernel prevents me from booting while 4.7.x pf works fine.

Thaodan commented on 2016-10-10 12:12 (UTC)

did you build a 32bit kernel? only x86_64 has stack validation I changed that objtool is only installed when validation is enabled.

walkindude commented on 2016-10-10 11:35 (UTC)

@tamjan same for me. solved by setting CONFIG_STACK_VALIDATION=y in config:

tamjan commented on 2016-10-10 11:06 (UTC) (edited on 2016-10-10 18:44 (UTC) by tamjan)

On my box, objtool isn't built when the PKGBUILD wants to install the binary. Inserting a "( cd tools/objtool && make )" before "cp -a tools/objtool/objtool ${pkgdir}/usr/lib/modules/${_kernver}/build/tools/objtool/" makes it not fail. No idea if it's a good thing to do, though.

Thaodan commented on 2016-10-09 11:21 (UTC)

Hey I updated the pkg yesterday and synced the configs with the configs from the ARCH kernel, I used the aufs for the rcN kernel since theres no version for 4.8. if you get an issues see this: there's currently a bug that's is described in the tweet.

xianai commented on 2016-10-05 03:49 (UTC)


xianai commented on 2016-09-25 08:31 (UTC)

Hi all, UKSM for v4.7 was officially released. Please feedback at:

quequotion commented on 2016-09-21 03:24 (UTC) (edited on 2016-09-21 03:31 (UTC) by quequotion)

>kogone Did you ever get a response? If i run tuxoniceui --test it seems to be operational, but I haven't been able to suspend to disk (swapfile) for a while now with this message at boot: "resume: tux-on-ice syntax detected, but no support found" EDIT; yes, it has been removed, as of version 4.6-pf1 in June:

Thaodan commented on 2016-08-31 12:19 (UTC)

The pkg is now also on gitlab where I test things first before pushing them into the aur:

Thaodan commented on 2016-08-31 12:16 (UTC)

I tested menuconfig and nconfig, both worked fine for me. I renamed the modprobe-db stuff, changed the path of vmlinux as suggested. Also I splittet the preset from the actual package. With this change it is possible to use a kernel build for every device but use a specific preset if needed. The if the default preset is installed nothing is changed.

Thaodan commented on 2016-08-10 11:51 (UTC)

nvidia-pf has the patch already too (:

tuankiet65 commented on 2016-08-10 11:46 (UTC)

If you are using this with nvidia-dkms, you may want to update nvidia-dkms to 367.35-2 (currently in testing, should be released once linux-4.7 has gone out of testing) or apply this patch by hand

s3rb31 commented on 2016-07-25 00:02 (UTC)

I think line 552 in the PKGBUILD: ͏ ͏ ͏ ͏ install -D -m644 vmlinux "${pkgdir}/usr/lib/modules/build/${_kernver}/vmlinux" should instead be: ͏ ͏ ͏ ͏ install -D -m644 vmlinux "${pkgdir}/usr/lib/modules/${_kernver}/build/vmlinux" Because DKMS gives me the following error: ͏ ͏ ͏ ͏ ==> No kernel build modules. You must install them to use DKMS!

milkii commented on 2016-07-05 01:04 (UTC)

I'm currently getting up to: ... patching file tools/objtool/Makefile patching file tools/objtool/elf.h ==> ERROR: A failure occurred in prepare(). Aborting... makepkg -si 21.53s user 9.23s system 14% cpu 3:30.23 total Any advise on how I could debug?

kogone commented on 2016-06-10 23:42 (UTC)

is tuxonice not included anymore?

tuankiet65 commented on 2016-06-05 15:55 (UTC)

Hashes for config and config.x86_64 haven't been updated I think.

commented on 2016-04-24 18:48 (UTC)

Hi, I'm noticing a few problems: 1. modprobed_db is now modprobed-db, so that needs to be changed in the PKGBUILD. 2. When I do "L" to `make localmodconfig`, it seems to pause, but there's a question there that I don't see until I hit enter. But by then it assumes I wanted the default, which is 'n'. 3. Both menuconfig and nconfig seem to be broken because entering the keystrokes seem to enter the keystroke into the terminal rather than it being intercepted by menuconfig or ncurses. I am using xterm, but this also occurs on TTYs.

commented on 2016-04-06 10:30 (UTC)

as @aucubin notes, in order to work, change the sha256sums to: sha256sums=('401d7c8fef594999a460d10c72c5a94e9c2e1022f16795ec51746b0d165418b2' '20a7dcee51530bdcda4c20a5a99de1527ed639c276315cf02d18cb372ff41f37' '17a63957522907f2b268c3d49798f2dc5c25822e8cc7d1116d8bad4357f88029' '82d660caa11db0cd34fd550a049d7296b4a9dcd28f2a50c81418066d6e598864' '1256b241cd477b265a3c2d64bdc19ffe3c9bbcee82ea3994c590c2c76e767d99' 'b09352ee835724951aaf6a83b74ddb2964261e82ce6c800edf4fa9e8bdb11bc9' 'SKIP' '5313df7cb5b4d005422bd4cd0dae956b2dadba8f3db904275aaf99ac53894375')

aucubin commented on 2016-03-22 13:52 (UTC)

seems like you forgot to change the sha256sums of config and config.x86_64 because I needed to change them manually in the PKGBUILD to get past the checksums

lectus commented on 2015-10-21 08:18 (UTC)

@dlh: Touch the void, Luke! Just add fourth parameter "void" in AuStub definition and all will be fine. File "fs/aufs/loop.h", row 44: AuStub(struct file *, loop_backing_file, return NULL, void). ps: "Touching the Void"- book/movie about one "nearly fatal climb" of the mountain Siula Grande in the Peruvian Andes in 1985.

dlh commented on 2015-10-14 09:29 (UTC)

Does not compile fs/aufs/loop.h:44:23: error: function declaration isn’t a prototype [-Werror=strict-prototypes] AuStub(struct file *, loop_backing_file, return NULL)

post-factum commented on 2015-09-11 08:34 (UTC)

BTW, BFS issue has been fixed, and you may try latest -pf for 4.1 branch.

Thaodan commented on 2015-08-06 02:43 (UTC)

sorry for the delay about linux-pf-4.1 see here what the issue:

Det commented on 2015-06-08 05:36 (UTC)

Wouldn't it make more sense to version it as something like '4.0_pf5-1' or '4.0.pf5-1' for clarity with

Thaodan commented on 2015-05-21 12:07 (UTC)

linux-pf: upkg, synched with ARCH configs

plasma commented on 2015-05-18 18:35 (UTC)

i stumble upon this when trying to compile: CC kernel/sched/bfs.o kernel/sched/bfs.c:528:20: error: function declaration isn’t a prototype [-Werror=strict-prototypes] static inline void grq_priodl_lock() ^ kernel/sched/bfs.c:533:20: error: function declaration isn’t a prototype [-Werror=strict-prototypes] static inline void grq_priodl_unlock() ^ cc1: some warnings being treated as errors scripts/ recipe for target 'kernel/sched/bfs.o' failed

Thaodan commented on 2015-05-14 15:54 (UTC)

upkg, synched configs with arch-linux-pf except for tomoyo which is enabled but makes no performance downsides

quequotion commented on 2015-05-14 03:08 (UTC)

build keeps failing in package_linux-pf() where it makes a symlink to extramodules..... why?

jaro3 commented on 2015-05-03 05:01 (UTC)


nous commented on 2015-04-28 10:12 (UTC)

@Thaodan: I used to copy over the ARCH config once every major kernel release and just enable the extra pf-patchset features, i.e. BFS, Hz freq --> 1000, BFQ and TuxOnIce. It's less than a minute's effort and helps to keep the config in order. See also README.maintainers at Cheers!

AnAkkk commented on 2015-04-27 22:51 (UTC)

Well, I won't post the full list of config settings that aren't the same as there are many (can be seen by doing a diff), for example there are the CONFIG_SECURITY_* ones which may lower the performance.

Thaodan commented on 2015-04-27 20:59 (UTC)

It's on my list, but please if you have something to complain give more infos, more detail

AnAkkk commented on 2015-04-27 20:53 (UTC)

Could you please fix the configs to match the official archlinux ones for the non -pf settings, there are still many things that are not in sync. Most of them were modified or removed at some point, and that wasn't changed in -pf.

Thaodan commented on 2015-04-27 11:42 (UTC)

yes this is true, but you could update this too.

gborzi commented on 2015-04-27 11:39 (UTC)

Modules tuxonice_compress, tuxonice_swap and tuxonice_userui are no longer provided by the kernel, so the wiki pages about tuxonice and linux-pf need to be updated, i.e.update the line about MODULES in mkinitcpio.conf.

Thaodan commented on 2015-04-25 16:38 (UTC)

upkg, added script to build all pkgs in a row to the pkg repo

Thaodan commented on 2015-04-15 14:03 (UTC)

upkg, added option to enable batch_mode by src/batch_opts, set CPU to your favorite march and build for it

gborzi commented on 2015-03-28 21:34 (UTC)

Please add WESTMERE to the _CPUSUFFIXES_KBUILD array.

Thaodan commented on 2015-03-26 14:29 (UTC)

sorry I uploaded the wrong source package first, if you watch my git mirror you see that I already updated the pkgbuild. when its out of date please just mark it and dont post ver xx is out, this is redundant and annoing, if you have something to add adout the new ver do it.

vincent commented on 2015-03-26 14:21 (UTC)

v3.19-pf3 is out.

Thaodan commented on 2015-03-26 13:07 (UTC)

upkg, added silvermont support

post-factum commented on 2015-03-01 11:50 (UTC)

v3.19-pf2 is out with updated GCC patch.

pavbaranov commented on 2015-02-26 10:46 (UTC)

I don't know why gcc doesn't complains when try to build with wrong flag, but the simpliest solution for Intel's CPU user is add info - something like that: If you are Intel's CPU user and want to optimize your linux-pf kernel, choose MNATIVE flag. With this flag, kernel will be properly build for sure.

Thaodan commented on 2015-02-26 09:13 (UTC)

But why gcc don't complains when the March flag is wrong? I'll add the new patch as i already said but at the end of the week.

pavbaranov commented on 2015-02-25 22:06 (UTC)

MNATIVE option is ok and with it we can build proper, optimized kernel for Intel's processors. With "name" of it we cannot, becouse it's for gcc =<4.9. post-factum - it's not your's work. Of course it's yours decision use new or old graysky's patch, but maintainer linux-pf for Arch should explain us anything that is important or make patch-on-patch :)

post-factum commented on 2015-02-25 20:42 (UTC)

The funny thing is that I'm Arch user as well, but build my kernel with MNATIVE option as I guess it's up to compiler to decide what optimizations to use. Anyway, if people's lament persists, I may update graysky's patch and break Intel-specific optimizations for older GCC. I followed versioning voting inspired by Linus, and I guess I should do the same. So, vote please:

pavbaranov commented on 2015-02-25 14:45 (UTC)

No, certainly not. What Natalenko support in his patch it's his choice. But we are in Arch Linux. In Arch Linux we have gcc 4.9+. You are mainteiner of the most important part of system - kernel and offers it with not proper patch. See: for REQUIREMENTS. Since gcc 4.9 names of flags has been changed. It's impossible to build optimized kernel (any binary apps) with wrong compiler's flags. Then, maybe it's possible to build kernel with wrong flags but this kernel might be unstable or doing some things in a wrong way.

Thaodan commented on 2015-02-25 11:57 (UTC)

it if he wan'ts to support gcc 4.9+ it is his problem. It does build for intel cpus with gcc optimizations just fine.

pavbaranov commented on 2015-02-25 07:59 (UTC)

It's not a problem of Natalenko. His patch works well i.e. in Chakra, KaOS or Debian. Everywhere where GCC=<4,9 is. But not on Arch with GCC 4.9. This is a problem only with PKGBUILD not with patch. Currently the kernel builds fine with GCC optimizations only for AMD processors. For Intel's processors we can build kernel only without GCC optimizations.

Thaodan commented on 2015-02-25 01:07 (UTC)

Please ping Natalenko for this , to update the patch. I'll add the patch and fix the pkgbuild when I have time. Currently the kernel builds just fine using the old patch for haswell, sandybridge etc.

pavbaranov commented on 2015-02-25 00:56 (UTC)

Natalenko's patch uses graysky's GCC patch for GCC prior then 4.9. It means, that it use old -march CFF terminology. Just take a look at: or for new ones and inspect patch-3.19-pf1 for -march (GCC patch started from 2058 lines of Natalenko's patch). For example, for gcc 4.9 and Intel Nehalem platform proper -march flag is nehalem, but in pf patch it's old, but proper for gcc prior then 4.9, corei7. Wrong CFF flags for gcc 4.9 are for IvyBridge, SandyBridge, Haswell... etc. When PKGBUILD for your's linux-pf is started, we can choose special optimizations for specific processor. But if somebody has got i.e. SandyBridge, Natalenko's patch try to build kernel with -march=corei7-avx. It's unknown flag for GCC 4.9 and kernel will be incorectly built. In extremally causes it will result in kernel panic. Then it's impossible to build corectly kernel for (i.e.) Sandy Bridge with GCC optimizations in Arch with this PKGBUILD. I think, that your PKGBUILD should use, for example, sed command for correct this.

Thaodan commented on 2015-02-24 23:04 (UTC)

Why please explain? I you have something to add/complain please explain it in detail I can't do anything whithout valid infos.

pavbaranov commented on 2015-02-24 22:56 (UTC)

Natalenko's pf-patch uses old graysky's GCC patch (for GCC prior then 4.9). In Arch we have GCC 4.9 now, then it's impossible to build proper kernel enabling CPU-specific compile option in the Linux kernel for some Intel processors. The PKGBUILD should changes pf-patch before it's implemented.

Thaodan commented on 2015-02-24 11:53 (UTC)

nous: thanks, I added a workaround from gravsky for this, without dvb it builds just fine now. Now I just runned qconf and saved the new config. I think I have missed the changes in ARCH config .

nous commented on 2015-02-24 09:53 (UTC)

@Thaodan: About the security stuff, perhaps you accidentally copied over the .config from 3.18*? In the diff @AnAkkk posted seems so.

nous commented on 2015-02-24 09:44 (UTC)

@Tahu363: Device drivers --> <M> Multimedia support --> [*] Digital TV support. You are right, the related config options have changed, I'll update the wiki.

nous commented on 2015-02-24 09:40 (UTC)

@hzy199411 You can do it yourself in the PKGBUILD (change NUMA_off=yes). Very very few of us run multi-cpu (not multi-core) systems and NUMA creates some overhead. This kernel is desktop-oriented, not server...

hzy199411 commented on 2015-02-24 05:52 (UTC)

would you like enable CONFIG_NUMA ? or it will complain "/sys is not mounted" when I run openmpi programs.

Thaodan commented on 2015-02-23 13:02 (UTC)

I'll change the f2fs stuff the security stuff is enabled before me I ask nous why he has enabled it

AnAkkk commented on 2015-02-23 12:49 (UTC)

Well, there aren't that much differences, but there are a few. CONFIG_SECURITY_* and CONFIG_AUDIT_* are still enabled though, which can impact performance. Are they needed for anything in -pf? This might be why I get less FPS in -pf than in -ck and the default arch kernel. There are other differences, e.g. CONFIG_F2FS_FS_SECURITY and CONFIG_F2FS_CHECK_FS are not set in -pf, and they're enabled in the default kernel. I use F2FS on two of my computers so this might be useful :)

Thaodan commented on 2015-02-23 12:24 (UTC)

AnAkkk: I looked at this and the config should me like ARCH's except the pf stuff. @Tahu363: workaround for this copied from -ck look at the PKGBUILD to how this wotks if you want (you don't need to change something).

Tahu363 commented on 2015-02-23 05:51 (UTC)

Does anyone know how to fix the 3.19.1 compile issue? the arch wiki says "For people who build their own tailored kernels and compilation aborts with with an error about "missing include/config/dvb/*.h files", setting <M> at DVB for Linux at Device Drivers/Multimedia support and leaving everything else out, creates just the necessary dvb.h, which allows the compilation to continue." but menuconfig shows no such option, I believe this information may pertain to lower version kernels.

AnAkkk commented on 2015-02-22 15:34 (UTC)

I think there's more than just tuxonice, aufs3 and ck, some settings seem to have nothing to do with that. I think they were changed in the official config and weren't changed in linux-pf. For example the CONFIG_SECURITY_* ones are different. Just do a diff between the linux-pf one and and you'll see :)

Thaodan commented on 2015-02-22 14:51 (UTC)

Anakk: This is intended as taxon ice, aufs3 and ck patchset is applied. What else do you found?

Thaodan commented on 2015-02-22 14:49 (UTC)

Sorry I I'll fix this in the evening this day.

Tahu363 commented on 2015-02-22 10:36 (UTC)

The install cannot be completed. Kernel 3.19.1 wont build. Cannot stat /include/configs/dvb/*h Anyone have a fix for this? Package half installs and makes my boot hang on a "pending" operation.

vincent commented on 2015-02-20 19:08 (UTC)

There is an typo in linux.install file (3.18.1 instead of 3.19.1).

AnAkkk commented on 2015-02-20 16:59 (UTC)

Is it normal config/config.x86_64 don't match the stock kernel config ? Doing a diff between the two show many, many differences.

tamjan commented on 2015-02-18 10:00 (UTC)

Do you have TuxOnIce enabled?

Thaodan commented on 2015-02-17 21:00 (UTC)

for me it builds just fine what do you changed?

tamjan commented on 2015-02-17 20:30 (UTC)

I get this, more or less:

tamjan commented on 2015-02-17 20:28 (UTC)

This doesn't compile for me. I get error: too few arguments to function ‘memory_bm_next_pfn’, and complaints of multiple definitions of stuff. The TuxOnIce patch seems broken. Anybody else experiencing this? I run 3.17-pf4, which built fine, and I haven't changed my kernel config more than necessary.

Thaodan commented on 2015-02-15 21:28 (UTC)

update is comming, changes aufs3 branch

Thaodan commented on 2015-01-31 23:13 (UTC)

please don't report it out of date if there's no new ver.

nous commented on 2015-01-18 13:31 (UTC)

Also: the conflicts() arrays are not correctly populated; enclose the appended elements in parentheses, otherwise they are appended as raw strings: conflicts+=(${pkgbase}-${_cpusuffix}) instead of conflicts+=${pkgbase}-${_cpusuffix}

hzy199411 commented on 2015-01-18 12:32 (UTC)

kmod should in makedepends

nous commented on 2015-01-17 18:50 (UTC)

32-bit binaries also in place.

nous commented on 2015-01-07 19:10 (UTC)

Since Thaodan seems busy at the moment, I've uploaded a new set of precompiled packages at the [pfkernel] repo, with the appropriate iptables NAT modules in place. 64bit packages only, sorry. Version number 3.17.3-2.

nous commented on 2015-01-06 21:13 (UTC)

Please, fix the missing NAT modules issue ASAP.

kris7t commented on 2015-01-06 11:48 (UTC)

3.17-pf2 and 3.17-pf3 seem to build fine by bumping _pfrel to 2 and 3, respectively, and running makepkg -f >>PKGBUILD I did not try modprobed_db, just used my own .config from 3.17-pf1.

jaro3 commented on 2014-11-17 01:18 (UTC)

NAT kernel modules are disabled in the default config, is this on purpose?

fackamato commented on 2014-11-15 12:21 (UTC)

Can you please add a simple if -e or something so this doesn't break the build? cp: cannot stat ‘include/config/dvb/*.h’: No such file or directory

AnAkkk commented on 2014-11-15 10:17 (UTC)

Where did I say I am flagging anything out of date? And I know modprobed_db is not part of this kernel, it's just an option and I am pointing out it doesn't work correctly, can be useful for some other people.

AnAkkk commented on 2014-11-14 21:37 (UTC)

@TheAifam5: it works for me now with the all inclusive one, but not with modprobed_db unfortunately. It looks like modprobed_db misses some modules (or modprobe doesn't load them unless it's early boot), which causes DM_SNAPSHOT, DM_MIRROR, CONFIG_MICROCODE and others to be disabled, even if they're needed :/

Thaodan commented on 2014-11-14 00:40 (UTC)

Btw: please stay patient, if a new version is released and I didn't updated the package flag the package out of date but please wait until I update the package and don'r post version x.x is released. Give me some time.

theaifam5 commented on 2014-11-11 21:03 (UTC)

"test -e include/generated/autoconf.h -a -e include/config/auto.conf || ( \ echo >&2; \ echo >&2 " ERROR: Kernel configuration is invalid."; \ echo >&2 " include/generated/autoconf.h or include/config/auto.conf are missing.";\ echo >&2 " Run 'make oldconfig && make prepare' on kernel src to fix it."; \ echo >&2 ; \ /bin/false)" So... this happpends if i install nvidia-pf , but after this error, compilation work

theaifam5 commented on 2014-11-11 14:32 (UTC)

So.. and i dont know why not working for you.. I selected the same and after this I click ENTER .. ;)

AnAkkk commented on 2014-11-11 13:08 (UTC)

Nevermind, they seem to enabled in the config indeed. I'm not sure why they got disabled when I selected "all-inclusive kernel like stock -ARCH" though.

theaifam5 commented on 2014-11-11 13:05 (UTC)


AnAkkk commented on 2014-11-10 00:20 (UTC)

It says "Hit <N> (or just <ENTER>) to build an all-inclusive kernel like stock -ARCH" but that doesn't seem to be all-inclusive at all, it looks like this is using the config file included, which is far from arch's default, a lot of things are disabled, like CONFIG_MICROCODE, which are pretty important. Is this normal?

AnAkkk commented on 2014-11-08 20:37 (UTC)

Ah ok, thanks, I read it but missed this line :)

Thaodan commented on 2014-11-08 20:34 (UTC)

Read the info on source page, pf usally includes last patches.

AnAkkk commented on 2014-11-08 20:28 (UTC)

Yes, I know, but what I mean is that you aren't using the latest kernel sources? Latest stable is 3.17.2, but the PKGBUILD downloads the 3.17 tar.

Thaodan commented on 2014-11-08 20:26 (UTC)

for example pfs ver is: 3.17-pf1 pkgver is: 3.17.1

Thaodan commented on 2014-11-08 20:26 (UTC)

for example pfs ver is: 3.17-pf1 pkgver is: 3.17.1

AnAkkk commented on 2014-11-08 20:20 (UTC)

Are the releases always based on the first major/minor version of a kernel? For example, it's 3.16, but 3.16.7 is out since a while.

post-factum commented on 2014-11-03 21:25 (UTC)

v3.17-pf1 is out.

gim commented on 2014-10-31 15:09 (UTC)

Anonymo, I did the same thing and it works all right for about a week now.

Anonymo commented on 2014-10-31 15:03 (UTC)

Compiling now by changing changing pfrel line to 4 and sha256sum at the bottom. Seems to be working... at the fs/hfs... right now

blinxwang commented on 2014-10-25 21:05 (UTC)

pf-kernel 3.16-pf4 is out.

gim commented on 2014-10-17 09:54 (UTC)

It would be great if you implemented PGP dignature checks both for kernel and patch itself in the PKGBUILD.

X-NicON commented on 2014-09-10 17:29 (UTC)

If default config compile Error: scripts/ line 231: cmp: command not found Depending add "Diffutils"

Thaodan commented on 2014-09-07 22:08 (UTC)

updated, however rebuild is not needed as the fix patch was already added by me in the last ver, added request module

post-factum commented on 2014-09-07 21:40 (UTC)

Flagged as out-of-date due to 3.16-pf2 release :).

hzy199411 commented on 2014-09-07 07:58 (UTC)

would you like to add driver support for my "Qualcomm Atheros QCA8171 Gigabit Ethernet Card", you can change "# CONFIG_ALX is not set" to "CONFIG_ALX=m",thank you.

Thaodan commented on 2014-09-06 13:52 (UTC)

issue is fixed the forum post

Thaodan commented on 2014-09-05 14:18 (UTC)

I get the same error however I can't fix it don't know if its my fault pfs fault see:;boardseen

felixonmars commented on 2014-09-05 14:12 (UTC)

Hrm, I'm getting an error: ERROR: "resume_file" [kernel/power/tuxonice_file.ko] undefined! ERROR: "resume_file" [kernel/power/tuxonice_bio.ko] undefined! scripts/Makefile.modpost:90: recipe for target '__modpost' failed make[1]: *** [__modpost] Error 1 Makefile:1055: recipe for target 'modules' failed make: *** [modules] Error 2 make: *** Waiting for unfinished jobs....

Thaodan commented on 2014-09-05 13:48 (UTC)

run kernel config (follow pkgbuild) and set processor type and features to avx2

Anonymo commented on 2014-09-05 13:15 (UTC)

I see the option is in the PKGBUILD to build optimized kernel, I have a Haswell, does it do it automatically or do I have to edit the PKGBUILD somehow?

Thaodan commented on 2014-09-05 08:06 (UTC)

sorry I couldn't update the until yet as my old laptop broke

RibShark commented on 2014-08-24 13:29 (UTC)

3.16-pf1 is out:

abihf commented on 2014-07-18 03:17 (UTC)

would you like to update this package to 3.15 ? i tried it my self, but always got "ERROR: A failure occurred in prepare()"

ivenvd commented on 2014-06-27 07:35 (UTC)

v3.15-pf2 is out:

mid-kid commented on 2014-06-11 20:15 (UTC)

Please add kmod to makedepends, otherwise it won't compile in a chroot made with devtools, due to the "depmod" command missing at compile time.

nous commented on 2014-06-06 10:03 (UTC)

>>> Updating module dependencies. Please wait ... depmod: ERROR: could not open directory /lib/modules/3.14.1-pf: No such file or directory depmod: FATAL: could not search modules: No such file or directory >>> Generating initial ramdisk, using mkinitcpio. Please wait... ==> Building image from preset: /etc/mkinitcpio.d/linux-pf.preset: 'default' -> -k /boot/vmlinuz-linux-pf -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-pf.img ==> Starting build: 3.14.0-pf3-pf Please fix the errors, especially the -pf3-pf. % file /boot/vmlinuz-linux-pf /boot/vmlinuz-linux-pf: Linux kernel x86 boot executable bzImage, version 3.14.0-pf3-pf (nous@hyperion) #1 SMP PREEMPT Thu Jun 5 23:56:49 EEST, RO-rootFS, swap_dev 0x2, Normal VGA

Thaodan commented on 2014-04-14 04:16 (UTC)

sorry fixed

tkh23 commented on 2014-04-14 04:09 (UTC)

==> Starting package_linux-pf-headers()... cp: cannot stat ‘drivers/media/usb/sn9c102/*.h’: No such file or directory

pavbaranov commented on 2014-04-13 10:21 (UTC)

First of all, there isn't any patch at: - 404 Not Found. It should be

nous commented on 2014-04-13 09:47 (UTC)

The package version is 3.14.1-pf, but the kernel itself is versioned 3.14.0-pf (which isn't a big deal as far as installation and operation are concerned). Is this intentional? Also, KERNEL_VERSION in linux.install is at 3.13.1-pf; you might want to uncomment the relevant sed in the PKGBUILD so as to take care of it automagically, since this seems to be easily forgotten.

Thaodan commented on 2014-04-12 15:27 (UTC)


felixonmars commented on 2014-04-12 04:01 (UTC)

Reversed (or previously applied) patch detected! Skipping patch. 2 out of 2 hunks ignored -- saving rejects to file arch/x86/include/asm/module.h.rej patching file arch/x86/Kconfig.cpu Reversed (or previously applied) patch detected! Skipping patch. 9 out of 9 hunks ignored -- saving rejects to file arch/x86/Kconfig.cpu.rej patching file arch/x86/Makefile Reversed (or previously applied) patch detected! Skipping patch. 1 out of 1 hunk ignored -- saving rejects to file arch/x86/Makefile.rej patching file arch/x86/Makefile_32.cpu Reversed (or previously applied) patch detected! Skipping patch. 2 out of 2 hunks ignored -- saving rejects to file arch/x86/Makefile_32.cpu.rej

ids1024 commented on 2014-04-12 00:09 (UTC)

The cpu optimizations patch is now included in linux-pf.

mid-kid commented on 2014-04-10 21:02 (UTC)

Linux-pf 3.14-pf1 is available.

bruce commented on 2014-03-31 08:11 (UTC)

There's now a 3.13.2 linux-pf patch, just fyi :-)

Thaodan commented on 2014-03-08 10:48 (UTC)

sorry updated

alaviss commented on 2014-03-08 10:40 (UTC)

The kernel version in the install file is still 3.12.4-pf :P Please update it for depmod to work

nous commented on 2014-03-07 17:38 (UTC)

Ok, I'll rebuild.

Thaodan commented on 2014-03-07 17:34 (UTC)

nous you used an incorrent PKGBUILD wich i correct a second later, sorry but you need to rebuilt the package. All packages in my repo work fine.

nous commented on 2014-03-07 16:58 (UTC)

-core2 I've also received an email from a user (obviously of the repo binaries): From `pacman -Si linux-pf` I see that you are the packager of this package and (I assume) the maintainer of the unofficial linux-pf repository. If yes, I would like to report that the latest linux-pf-headers package have an invalid symlink which causes the `dkms autoinstall` to fail. The symlink is '/usr/lib/modules/3.13.1-pf/build' and seems to be broken, at least on my system (it points to '../../../src/linux-3.13.1-pf', which doesn't exists). Is this a problem in my system or a mistake in package creation? Could you confirm it's a package creation issue?

Thaodan commented on 2014-03-07 16:39 (UTC)

which package-suffix do you use?

nous commented on 2014-03-07 16:35 (UTC)

The "build" symlink in /usr/lib/modules/3.13.1-pf is broken, i.e. it points to /usr/src whilst the sources are in /usr/lib/modules. I use the precompiled binaries from my repo, BTW. Could you look at it? On a sidenote, WHY THE FUCK the sources are placed in a modules dir and not in /usr/src is beyond me. And I'm ranting about the stock -ARCH kernel which started it...

Thaodan commented on 2014-03-05 16:14 (UTC)


alaviss commented on 2014-03-05 02:31 (UTC)

pf-kernel have reached 3.13.1-pf. Please update the package

Thaodan commented on 2014-02-23 17:41 (UTC)

exactly, ask pf for updates. I just maintain the package and add some critical bugfix patches if needed.

clfarron4 commented on 2014-02-23 17:36 (UTC)

@sanerb: The latest pf-kernel patch was written for 3.12.4, so unless there is a patch published for the 3.13 series, I don't think this is going to be updated.

sanerb commented on 2014-02-23 05:45 (UTC)

can we get this updated for 3.13? (current base repo has 3.13.4-1 as of time of writing this)

Thaodan commented on 2014-01-15 19:01 (UTC)

I builds see my repo, I don't know what you have done but do you removed your src dir?

Dr_Drache commented on 2014-01-15 15:02 (UTC)

just to point out, I can't seem to compile. fremap.c fails patching : [code] Hunk #1 FAILED at 207. 1 out of 1 hunk FAILED -- saving rejects to file mm/fremap.c.rej patching file mm/madvise.c patching file mm/memory.c Hunk #1 succeeded at 2777 (offset 32 lines). Hunk #2 succeeded at 3492 (offset 36 lines). patching file mm/mmap.c Hunk #1 succeeded at 251 with fuzz 2 (offset 1 line). Hunk #2 succeeded at 870 (offset 10 lines). Hunk #3 succeeded at 1642 (offset 20 lines). Hunk #4 succeeded at 2433 (offset 21 lines). Hunk #5 succeeded at 2454 (offset 23 lines). Hunk #6 succeeded at 2864 (offset 36 lines). patching file mm/msync.c patching file mm/nommu.c patching file fs/file_table.c patching file fs/inode.c patching file fs/namespace.c patching file fs/notify/group.c patching file fs/notify/mark.c patching file fs/open.c patching file fs/splice.c patching file security/commoncap.c patching file security/device_cgroup.c patching file security/security.c patching file kernel/printk/printk.c Hunk #1 succeeded at 60 with fuzz 2 (offset 2 lines). patching file init/Kconfig Hunk #1 succeeded at 1102 (offset 113 lines). Hunk #2 succeeded at 1113 (offset 113 lines). patching file arch/x86/include/asm/module.h patching file arch/x86/Kconfig.cpu patching file arch/x86/Makefile Hunk #1 succeeded at 67 with fuzz 1 (offset 10 lines). patching file arch/x86/Makefile_32.cpu ======================================================= ======================================================= (needs IKCONFIG and IKCONFIG_PROC) (warning: it can take a looong time) aura >>= Would you like to continue anyway? [Y/n] n aura >>= Building failed. [/code]

Thaodan commented on 2013-12-28 17:10 (UTC)

I don't know what you have done but the headers are included in the headers package and not in the kernel package

ilkyest commented on 2013-12-28 16:59 (UTC)

well, I don't know why, or if it's right, but on pkgbuild, on here # If the following is set, stop right there. We only need the headers for # dependent drivers' compiling (nvidia, virtualbox etc) # get kernel version make prepare I've unmarked the "make prepare" and, yes, now headers

Thaodan commented on 2013-12-28 14:54 (UTC)

compile as usual

ilkyest commented on 2013-12-28 13:04 (UTC)

how do I compile it with kernel headers? I need to virtualbox and nvidia driver

Thaodan commented on 2013-12-22 03:19 (UTC)


mikeroll commented on 2013-11-30 15:47 (UTC)

3.12 is out, please update :)

Thaodan commented on 2013-11-24 23:04 (UTC)


aiu commented on 2013-11-24 22:58 (UTC)

Sorry, I flagged it as out-of-date by mistake.

Thaodan commented on 2013-11-07 01:42 (UTC)

@sir: np @nous: I'm doing on this already.

sir_lucjan commented on 2013-11-06 22:49 (UTC)

@ Thaodan - I'm sorry - I looked only at the version number. My mistake - once again I'm sorry.

nous commented on 2013-10-31 18:35 (UTC)

I moved a box from linux-pf to linux-pf-p3 and the respective header packages didn't conflict, i.e. linux-pf-headers-p3 tried to install over linux-pf-headers and failed. Could you fix that? The conflicts() array in package_linux-pf-headers() should be determined more or less like the one in package_linux-pf...

nous commented on 2013-10-29 21:53 (UTC)

justin8: It's NOT an issue. Please, do read the post right on top of Zorael's for a rationale. Just enable DVB, it'll only create dvb.h, nothing else will burden the kernel and everybody will be happy.

justin8 commented on 2013-10-29 04:16 (UTC)

The issue reported by Zorael in January is still present. The build will fail if you do not choose any DVB modules for your kernel...

Thaodan commented on 2013-10-25 02:56 (UTC)

updated, added changes ARCH .config

Thaodan commented on 2013-10-19 18:14 (UTC)

@sir_lucjan: why do you reported it out of date?

Thaodan commented on 2013-10-07 18:24 (UTC)

updated;bcache is now enabled

demon012 commented on 2013-10-02 08:25 (UTC)

FYI Aufs still broken with "aufs loop_backing_file() is not defined". Not your problem though as it is upstreams fault.

Thaodan commented on 2013-10-01 20:34 (UTC)

should be fixed now

walkindude commented on 2013-10-01 19:48 (UTC)

but I always get: DEPMOD 3.11.2-pf-pf

Thaodan commented on 2013-10-01 17:17 (UTC)

replaced the P (eg. removing the subver) by the way Arch patches the localversion[1]. [1]

Thaodan commented on 2013-10-01 15:40 (UTC)

updated aufs is now enabled gain.

demon012 commented on 2013-09-27 06:30 (UTC)

@jakob unfortunately no packages are built for the atom processors but thanks for the link, @Thaodan awesome thanks for the link. Followed you and starred the repo.

Thaodan commented on 2013-09-27 03:56 (UTC)

@demon012 if you want older PKGBUILDS check my git repo, here the 3.10 version:

jakob commented on 2013-09-26 22:42 (UTC)

@demon012, check the repository:

demon012 commented on 2013-09-26 21:48 (UTC)

Thaodan, in that case do you happen to have the older 3.10 PKGBUILD handy? I did not keep the older package and now my aufs setup is not working and neither linux-pf or linux-aufs_friendly are working at the moment due to this same bug.

Thaodan commented on 2013-09-26 08:18 (UTC)

I don't used it, at the time I updated the package aufs3 wasn't ready for 3.11

demon012 commented on 2013-09-26 08:12 (UTC)

The AUFS3 patch you are using is causing the error: "aufs au_loopback_init:136: loop_backing_file() is not defined" and it making aufs3 cease to work. Apparently the patch had this function added and then it was for some reason removed: . Need to get that other patch in this package to make it work.

SydMax commented on 2013-09-16 15:39 (UTC)

Hi, Thaodan. Is there any reason, why you have ignored twice reports on this issue: "The patchlevel option seems to be the wrong way around - 'p' removes the patch version, <enter> keeps it." The fix in PKGBUILD is obvious, why not to implement it?

Thaodan commented on 2013-09-09 15:14 (UTC)

updated, aufs3 ins't ready

Thaodan commented on 2013-09-06 22:53 (UTC)

thanks, fixed

post-factum commented on 2013-09-06 21:50 (UTC)

PILEDRIVER target (line 434) has got a typo: pkgname"${pkgbase}-piledriver" Should be pkgname="${pkgbase}-piledriver" BULLDOZER target has the same issue.

brunogm commented on 2013-07-20 18:05 (UTC)

Hi, problem with CONFIG_MNATIVE=y. # CONFIG_MEMTEST is not set # CONFIG_MK8 is not set # CONFIG_MK10 is not set # CONFIG_MBARCELONA is not set # CONFIG_MBOBCAT is not set # CONFIG_MBULLDOZER is not set # CONFIG_MPILEDRIVER is not set # CONFIG_MPSC is not set # CONFIG_MATOM is not set # CONFIG_MCORE2 is not set # CONFIG_MCOREI7 is not set # CONFIG_MCOREI7AVX is not set # CONFIG_MCOREAVXI is not set # CONFIG_MCOREAVX2 is not set # CONFIG_GENERIC_CPU is not set CONFIG_MNATIVE=y

Thaodan commented on 2013-07-18 22:35 (UTC)

updated packages NOTE: I added patch from to fix the issue please report issues

J4913 commented on 2013-07-09 19:36 (UTC)

The patchlevel option seems to be the wrong way around - 'p' removes the patch version, <enter> keeps it.

Thaodan commented on 2013-06-16 19:40 (UTC)

With wrong page I mean that this is the page of the nvidia module for linux-pf and not the page of linux-pf.

Thaodan commented on 2013-06-16 10:57 (UTC)

fixed, there was an typo related to piledriver and to generic build.

sinatosk commented on 2013-06-16 10:29 (UTC)

Now it's just saying there is an error... ==> Starting build()... ======================================================= ==> You might be prompted below for some config options ======================================================= ==> Hit <Y> to use your running kernel's config (needs IKCONFIG and IKCONFIG_PROC) ==> Hit <L> to run 'make localmodconfig' ==> Hit <N> (or just <ENTER>) to build an all-inclusive kernel like stock -ARCH (warning: it can take a looong time) ==> Using stock ARCH kernel .config (with BFS, BFQ and TuxOnIce enabled). ==> Kernel configuration options before build: <M> make menuconfig (console menu) <N> make nconfig (newer alternative to menuconfig) <G> make gconfig (needs gtk) <X> make xconfig (needs qt) <O> make oldconfig <L> make localyesconfig <ENTER> to skip configuration and use stock -ARCH defaults X HOSTCC scripts/basic/fixdep CHECK qt SHIPPED scripts/kconfig/ MOC scripts/kconfig/qconf.moc HOSTCC scripts/kconfig/conf.o SHIPPED scripts/kconfig/zconf.lex.c SHIPPED scripts/kconfig/zconf.hash.c HOSTCXX scripts/kconfig/qconf.o HOSTCC scripts/kconfig/ HOSTLD scripts/kconfig/qconf scripts/kconfig/qconf Kconfig Fontconfig warning: "/etc/fonts/conf.d/50-user.conf", line 14: reading configurations from ~/.fonts.conf is deprecated. # # configuration written to .config # ‘.config’ -> ‘/home/username/pkg/linux-pf/config.local’ ==> ERROR: A failure occurred in build(). Aborting...

sinatosk commented on 2013-06-16 10:27 (UTC)

forgot to mention... this is 3.9.4-4 I'm talking about

Thaodan commented on 2013-06-16 10:04 (UTC)


Thaodan commented on 2013-06-16 09:41 (UTC)


commented on 2013-06-16 04:50 (UTC)

I got the same issue "PKGBUILD: line 273: 0: command not found" with a custom config. Looking at the PKGBUILD, there's something screwy going on in the relevant section - it's trying to figure out what CPU you're compiling for and failing miserably. Several variables appear to be misnamed, etc. For the time being, here's a workaround: Comment out line 273 and add CPU="GENERIC" (or something else if you're not compiling for the generic CPU target) just before the cp command around 283.

felixonmars commented on 2013-06-15 14:20 (UTC)

PKGBUILD: line 273: 0: command not found I'm using stock settings :(

Thaodan commented on 2013-06-15 11:39 (UTC)

should be fixed.

commented on 2013-06-15 05:21 (UTC)

I can't set k10

commented on 2013-06-14 10:48 (UTC)

I already downloaded 3.9.4 from repo and updated with "pacman -U" But now it is ok with "pacman -S" too. Thanks.

nous commented on 2013-06-14 10:07 (UTC)

firebbs: you probably caught the repo at updating the packages to 3.9.4. Please try again.

Thaodan commented on 2013-06-13 20:25 (UTC)

I think you mean nous repo? If yes ask him in his thread. If not: there's no generic linux-pf package in my repo.

commented on 2013-06-13 20:19 (UTC)

#pacman -Syu --ignore filesystem,bash error: failed retrieving file 'linux-pf-3.9.3-1-x86_64.pkg.tar.xz' from : The requested URL returned error: 404 NOT FOUND warning: failed to retrieve some files error: failed retrieving file 'linux-pf-headers-3.9.3-1-x86_64.pkg.tar.xz' from : The requested URL returned error: 404 NOT FOUND

Thaodan commented on 2013-06-10 19:21 (UTC)

Updated PKGBUILD, aufs3 is enabled again (url to gitrepo was wrong).

SydMax commented on 2013-06-05 14:54 (UTC)

It seems that handlers of <P> or <Enter> answers in PKGBUILD is mixed up and are in contradiction with descriptions.

Thaodan commented on 2013-05-28 20:58 (UTC)


mikeroll commented on 2013-05-28 20:45 (UTC)

Someone forgot to add MK10=y to egrep in line 266. Please fix. Otherwise build fails for K10 cpus.

Thaodan commented on 2013-05-24 11:50 (UTC)

The $_kernelname var is set in line 12, to pf. There must be something in your scripts.

nous commented on 2013-05-24 11:20 (UTC)

It must be something in my 32bit chroot then. I'm using distcc to shorten compile time and there's a strong warning in the wiki against distcc/multilib: Anyway, I've pointed at the issue because linux-pf used to compile/pack correctly in the chroot a few revisions ago.

Thaodan commented on 2013-05-23 21:35 (UTC)

Using 32bit makepkg.conf and gcc-multilib

nous commented on 2013-05-23 21:12 (UTC)

I must pin this down. Are you building in an i686 chroot or natively?

Thaodan commented on 2013-05-23 20:37 (UTC)

As you see it doesn't.

nous commented on 2013-05-23 20:34 (UTC)

Found an easy one: when copy/pasting from linux-ARCH you _must_ change ${_kernelname:--ARCH} to ${_kernelname:--pf}.

Thaodan commented on 2013-05-23 20:28 (UTC)

It's your script or system. I builded it just fine without any issues and with the correct path see:

Thaodan commented on 2013-05-23 18:31 (UTC)

I'm searching it, but as the settting of EXTRAVERSION isn't depent on $CARCH I don't see it. You may search on your own.

nous commented on 2013-05-23 18:17 (UTC)

I have an i686 server box running 3.8.2-3-pf and updated to 3.9.2-pf but not rebooted yet. The new kernel modules and headers are installed in /usr/lib/modules/3.9.0-ARCH and /usr/src/linux-3.9.0-ARCH and the running kernel's version is 3.8.0, instead of 3.8.2-pf. So, there's definitely something broken in the PKGBUILD.

Thaodan commented on 2013-05-23 18:02 (UTC)

Hmm, It should I don't see anything in the PKGBUILD.

nous commented on 2013-05-23 17:54 (UTC)

It might be my repo build script, but whereas the x86_64 packages correctly show install paths suffixed with 3.9.3-pf (i.e. in /usr/src and /usr/lib/modules), the i686 ones show instead 3.9.0 (without -pf). The returned kernel version (uname -r) might also be wrong in i686, but I haven't booted one to check.

commented on 2013-05-23 11:00 (UTC)

This package mentions AUFS3 in the title, but if I'm not mistaken the patches/includes are missing. Just FYI currently shows patches for 3.9; it would be great to see these re-added if it isn't too much trouble. My hope is for the ability to use Docker ( which unfortunately requires AUFS for now...

Thaodan commented on 2013-05-22 22:25 (UTC)

updated, added patch to enanble cpufreq/intelp with ivybridge cpus.

trizen commented on 2013-05-09 19:01 (UTC)

'bc' package should be included in makedepends array, otherwise: CC kernel/itimer.o HZFILE kernel/hz.bc BC kernel/timeconst.h /bin/sh: bc: command not found make[1]: *** [kernel/timeconst.h] Error 127 make: *** [kernel] Error 2 ==> ERROR: A failure occurred in build(). Aborting...

Thaodan commented on 2013-05-04 23:39 (UTC)


walkindude commented on 2013-05-04 21:10 (UTC)

wrong sum for pf patch

nous commented on 2013-04-12 06:14 (UTC)

Sorry to be such a noisy chap, but I think you should put the PKGBUILD section between lines 150-289 into build(), i.e. from if [[ "$_BATCH" != "y" ]]; to export CPU Rationale: if someones wants to retry compiling with 'makepkg -e', so as to not unpack and patch again the source tree, then he (or she) won't be presented with the configuration/customization options. I use this option extensively either manually or scripted, especially for building the optimized repository binaries.

nous commented on 2013-04-10 17:34 (UTC)

You forgot again to update the configs, the build script stops at the same points. % diff -u config.x86_64 config.local --- config.x86_64 2013-03-16 22:39:26.000000000 +0200 +++ config.local 2013-04-10 20:32:01.343274958 +0300 @@ -1,6 +1,6 @@ -# Linux/x86_64 3.8.1-pf Kernel Configuration +# Linux/x86_64 3.8.2-pf Kernel Configuration @@ -303,8 +303,6 @@ CONFIG_CFQ_GROUP_IOSCHED=y CONFIG_IOSCHED_BFQ=y CONFIG_CGROUP_BFQIO=y -# CONFIG_DEFAULT_DEADLINE is not set -# CONFIG_DEFAULT_CFQ is not set CONFIG_DEFAULT_BFQ=y # CONFIG_DEFAULT_NOOP is not set CONFIG_DEFAULT_IOSCHED="bfq" @@ -341,6 +339,7 @@ CONFIG_NO_BOOTMEM=y # CONFIG_MEMTEST is not set # CONFIG_MK8 is not set +# CONFIG_MK10 is not set # CONFIG_MBARCELONA is not set # CONFIG_MBOBCAT is not set # CONFIG_MBULLDOZER is not set @@ -5287,6 +5286,8 @@ # CONFIG_EDD_OFF is not set CONFIG_FIRMWARE_MEMMAP=y CONFIG_EFI_VARS=y +CONFIG_EFI_VARS_PSTORE=y +# CONFIG_EFI_VARS_PSTORE_DEFAULT_DISABLE is not set CONFIG_DELL_RBU=m

Thaodan commented on 2013-04-08 09:52 (UTC)


lockheed commented on 2013-04-08 09:46 (UTC)

Does that version finally include appropriate /include/linux/version.h file to enable installation of nvidia-pf package?

nous commented on 2013-04-08 07:07 (UTC)

I also found tremendously helpful to regularly commit to the bitbucket repo, so I could easily revert mistakes or use a past version which worked better in my laptop.

Thaodan commented on 2013-04-08 07:03 (UTC)

Ah something that I forgot :)

nous commented on 2013-04-08 07:01 (UTC)

With every upstream kernel update new options are introduced, which are not always 'default'; others are changed by some patches. You can see which ones if you press <ENTER> at the second prompt (kernel configuration options before build). In my box it stops at the CPU selection and at EFI vars.

Thaodan commented on 2013-04-08 06:48 (UTC)

I used the old config whats bad with them?

nous commented on 2013-04-08 06:45 (UTC)

You should 'make nconfig' (or any *config you prefer) through the PKGBUILD in both i686 and x86_64 and rename the resulting config.local into config and config.x86_64 respectively, then regenerate the sha256sums. I know it's trivial, but my repo build scripts find unresolved configuration options and stop prompting for input.

Thaodan commented on 2013-04-07 22:14 (UTC)

Updated the package added prepare() removed the two drm-i915 patches.

Thaodan commented on 2013-04-07 21:55 (UTC)

I'll update the PKGBUILD yet but the packages will not come until the next day or later.

walkindude commented on 2013-04-07 21:52 (UTC)

3.8.2 is out

nous commented on 2013-03-30 19:54 (UTC)

Due to increasingly pressing real-life obligations, my free time is less than required to provide quality maintainance of such a demanding package. It's been a wonderful ride, thanks for your support and kind words. Good luck, Thaodan!

Thaodan commented on 2013-03-28 02:43 (UTC)

Updated my builds for sandbridge and ivvy bridge (NUMA off, removed minor version string):

commented on 2013-03-20 09:04 (UTC)

Works fine (all other 3.8 version I "had cannot stat ‘/tmp/yaourt-tmp-indie/aur-linux-pf/src/linux.preset’: No such file or directory"... and I have an x64 CPU ;))

Thaodan commented on 2013-03-20 08:51 (UTC)

Nous: I suggest to add the option to disable NUMA it the beginning of the PKGBUILD instead adding it in build()

mytbk commented on 2013-03-19 02:59 (UTC)

@indie: Me,too. I think the submitter should try building a package to ensure the PKGBUILD is okey before submitting.

indie commented on 2013-03-19 02:52 (UTC)

install: cannot stat ‘/tmp/yaourt-tmp-indie/aur-linux-pf/src/linux.preset’: No such file or directory

Thaodan commented on 2013-03-18 19:40 (UTC)

Just add the functionality from linux-ck like I did (this disables NUMA by default if not enabled): (i915 currently not applied),

nous commented on 2013-03-18 16:37 (UTC)

I'll post a PKGBUILD with the i915 patches ASAP, as that bug's a showstopper. The CPU optimization patches will follow soonest if not with the former. I've also been considering the feasibility of NUMA in linux-pf's scope. Is there ANY one needing it?

Thaodan commented on 2013-03-18 07:55 (UTC)

My GDocs folder with my builds optimized for sandy- and ivvy bridge (comming soon): NUMA is disabled in this build.

Thaodan commented on 2013-03-18 07:49 (UTC)

You may use the updated gcc patch from linux-ck?

Thaodan commented on 2013-03-18 03:37 (UTC)

You may add patches from FS #34327?

nous commented on 2013-03-17 20:25 (UTC)

felixonmars: Are you using any kind of compiler cache, like ccache? It's certainly not linux-pf related. mytbk: Thanks, it slipped from the -ARCH portion; I'll rename the linux-pf.{preset|install} files to just linux.* soon, as the relevant section uses $pkgbase anyway. First generic i686 and x86_64 3.8-pf series are already in the pfkernel repo, optimized builds added every hour or so. Please report any problems here, especially tuxonice related.

mytbk commented on 2013-03-17 04:21 (UTC)

and also 'linux-pf.install' is written as 'linux.install'.

mytbk commented on 2013-03-17 03:46 (UTC)

I think the string 'linux.preset' in this PKGBUILD should be 'linux-pf.preset'.

felixonmars commented on 2013-03-17 03:30 (UTC)

I'm getting a strange error: unrecognized ELF data encoding 0: drivers/atm/eni.o make[2]: *** [drivers/atm/eni.o] Error 1

nous commented on 2013-03-06 07:27 (UTC)

No idea but I'm guessing postfactum is awaiting all patches to sync with 3.8.

Thaodan commented on 2013-03-06 00:41 (UTC)

Any succes torwards linux 3.7.10?

nous commented on 2013-03-01 22:35 (UTC)

I just tried both URLs and the one without /pub/ fails. % wget -Y off Resolving (, Connecting to (||:21... connected. Logging in as anonymous ... Logged in! ==> SYST ... done. ==> PWD ... done. ==> TYPE I ... done. ==> CWD (1) /linux/kernel/v3.x ... No such directory ‘linux/kernel/v3.x’. The one with /pub/ works.

commented on 2013-03-01 17:08 (UTC)

Hi, Can't install here, default link broken to download Vanilla kernel at this time... To succeed I have replaced it manually by this one : in PKGBUILD compiling now so not a big deal. BR,

nous commented on 2013-02-16 23:57 (UTC)

3.7.5-2 is for i686 users only: -1's config was vanilla -ARCH without any -pf settings... sorry.

nous commented on 2013-02-04 13:07 (UTC)

3.7.4-2's only change is a move from ZCACHE to ZCACHE2 so as I won't forget to implement it later. Do not bother updating.

jnbek commented on 2013-01-27 05:07 (UTC)

is there not a post on the forums for the purpose of discussing this kernel and it's package? Can we please move these discussions here: as opposed to here. This comment system is to report build errors and to give thanks to the maintainer for being the kick ass mofo to be making this kernel so easily available in the first place... Feature requests and other assorted 'zOMFG!!! I NEEDZ AnaLogtV!!!!' can be discussed in the Forum post.

nous commented on 2013-01-16 21:14 (UTC)

Zorael: This has been discussed time and again (see older comments here); I synchronize my PKGBUILD with the stock ARCH, therefore the default linux-pf contains DVB. Just enable Analog TV under Device Drivers -> Multimedia without anything else to have dvb.h created. Creating an exception for this is not an option as I will most certainly forget to re-create it at the next update.

commented on 2013-01-16 20:36 (UTC)

Fails to build if you opted to not compile any DVB drivers; ==> Starting package_linux-pf-headers()... cp: cannot stat ‘include/config/dvb/*.h’: No such file or directory ==> ERROR: A failure occurred in package_linux-pf-headers(). One dirty workaround is to just append || true to the offending command (line ~557). Would you mind adding that? Or maybe you'd prefer some more elegant logic around that and the other these-files-should-be-there fixes.

felixonmars commented on 2013-01-12 15:25 (UTC)

@nous Sorry I've found out that the problem was caused by testing/file 5.12 (which is not present now).

nous commented on 2013-01-09 19:17 (UTC)

I admit I hadn't tested, so I went ahead and compiled it. It works ok. Are you using any pacman wrapper?

felixonmars commented on 2013-01-09 12:09 (UTC)

I'm getting the following error when upgrading from 3.7.1-3 to 3.7.1-4: (1/2) upgrading linux-pf [------------------------------------------------------] 100% >>> Updating module dependencies. Please wait ... >>> Generating initial ramdisk, using mkinitcpio. Please wait... ==> Building image from preset: 'default' -> -k /boot/vmlinuz-linux-pf -c /etc/mkinitcpio.conf -g /boot/initramfs-linux- pf.img ==> ERROR: invalid kernel specified: `/boot/vmlinuz-linux-pf' ==> Building image from preset: 'fallback' -> -k /boot/vmlinuz-linux-pf -c /etc/mkinitcpio.conf -g /boot/initramfs-linux- pf-fallback.img -S autodetect ==> ERROR: invalid kernel specified: `/boot/vmlinuz-linux-pf' error: command failed to execute correctly

nous commented on 2013-01-08 16:14 (UTC)

klazutin: :)

commented on 2013-01-08 13:48 (UTC)

>To compile nvidia, until they sniff the change in 3.7: sudo ln -s /usr/src/linux-$(uname -r)/include/generated/uapi/linux/version.h /usr/src/linux-$(uname -r)/include/linux/version.h Just wanted to note that this is also required to compile VMWare modules. Took me a while to figure out.

nous commented on 2013-01-07 09:38 (UTC)

You should report this to the BFS developers, it must be very hardware-specific. I've tested connecting the charger in two laptops with no issues.

commented on 2013-01-05 14:23 (UTC)

i have kernel panic, when plugin charger (trobles with BFS). if i change bfs to noop - work fine.

jnbek commented on 2013-01-04 15:46 (UTC)

I got the prompt for _SUBLEVEL and it worked like peaches and creme, thanks again for being so proactive @nous :D

jnbek commented on 2013-01-01 00:40 (UTC)

@nous: I really appreciate your quick action to suggestions and queries. I will test the _SUBLEVEL prompt here in a while when I have a chance to upgrade. Thanks again for your hard work in acquiescing to my nonsensical whims :)

nous commented on 2012-12-31 23:38 (UTC)

To compile nvidia, until they sniff the change in 3.7: sudo ln -s /usr/src/linux-$(uname -r)/include/generated/uapi/linux/version.h /usr/src/linux-$(uname -r)/include/linux/version.h As for the sublevel prompt, it would only appear when a non-generic CPU was selected; fixed in 3.7.1-3 (hopefully). Happy 2013!

jnbek commented on 2012-12-31 15:21 (UTC)

yea, I been meaning to mention this for a few days, and keep forgetting for one reason or a thousand. I have yet to be prompted by the PKGBUILD if I want to set _SUBLEVEL=y or not.. I go through the questions, and it just goes straight to the build... defaulting to no sublevel... Not sire what the issue is, I've just gone and set it to Y manually in the PKGBUILD to accomodate my sometimes seedy desires. But now that I remember, I can now live my life to it's fullest knowing that I have finally reported my _SUBLEVEL issue here :D

jahiy commented on 2012-12-31 11:59 (UTC)

Please set _SUBLEVEL to "y"(default), or nvidia cannot be complied correctly without SUBLEVEL!!

nous commented on 2012-12-22 11:52 (UTC)

"Core2 is one that the kernel devs include in the source." Thank you.

graysky commented on 2012-12-22 11:01 (UTC)

@nous - Core2 vs generic was only 88 ms faster. Core2 is one that the kernel devs include in the source. If you are rejecting the others based on your argument about practical significance, then why are you offering any optimized builds? Based on these data, they all offer, in you option, no practical significance. Do you see the disconnect here?

nous commented on 2012-12-22 10:32 (UTC)

@Thaodan: The gcc-4.7 patch is there, the optimizations are enabled but I won't pass them onto the package name beyond the in-kernel maximum (i.e. core2 and k8). To put an end to this, there's already provision for extreme optimization enthusiasts in the PKGBUILD: uncomment the 'export KCFLAGS="-march=native -Ofast"' line just before make bzImage and one gets the fastest kernel in the universe one's CPU can run (I do, for my core2 laptop). That been said, I won't add optimizations into the PKGBUILD other than those from the upstream kernel. @graysky: The same obvious fact is stated in lkml; statistically significant does not mean practically significant. As I've written elsewhere, I believe the kernel developers know better than me when to include a CPU optimization into the kernel configuration. Please, if it's not a great hassle, run a comparison between core2 and avx-i kernels. We've spent more time on this topic than all our CPU's combined would've saved running coreavx kernels for several thousand years.

Thaodan commented on 2012-12-21 23:51 (UTC)

BTW: nvidia-pf detecs all builds that I added fine without any issues.

Thaodan commented on 2012-12-21 23:50 (UTC)

nous: I don't say build all aviable optimisations, I only say inclue it in the PKGBUILD nothing more.

jnbek commented on 2012-12-21 15:01 (UTC)

egads, aur spam!!! lol, woke up this morning to an inbox full of notices from this pkg... :D Love a well used package.

graysky commented on 2012-12-21 14:25 (UTC)

@nous - You're missing the point. Upstream already includes optimization options in the nconfig that give the same order of decrease (hundreds of milliseconds) vs. generic. The options the patch introduces just expands the existing menu. The real point is that there are statistically significant gains by using them -- at least on the machines I looked at... for more, see and the reply.

nous commented on 2012-12-21 13:39 (UTC)

Thaodan: Good to know, as I've included in the PKGBUILD the option to follow the 3-number versioning in 3.7 (right after the CPU-naming selection); it leaves SUBLEVEL at the original upstream number with no further tweaking.

nous commented on 2012-12-21 13:33 (UTC)

About the proposed optimization schemes and the benchmarks graysky provided: the slowest tested CPU vs GENERIC gives a echo '(191.9256-191.8459)/191.8459*100'|bc -l .04154375986143045000 WOW! 0.0415% gain in performance! 79.7 timeless and torturing milliseconds after 191 seconds of wait. And, mind you, that gain is against the GENERIC kernel. Now, if graysky is kind enough to compare a core2 kernel vs an avx-i, I bet my sideburns that the measured gain won't be greater than 1 millisecond, if that. It's just nonsensical and futile; optimize your userspace, not the kernel. Again, see and read the comments [0]. Thaodan: thanks for your work but I won't spend 20 hours (40 minutes * 15 CPUs * 2 arches) compiling 30 different kernels which run barely 1/10th of a second faster in benchmarks than linux-pf (and 1/1000th second faster than linux-pf-[core2|k8]. Not to mention the nvidia-pf mess that'll ensue. graysky: I've queued the watchdog patch for inclusion, thanks. [0] Read It was the last thing I ever did on Gentoo before moving to Arch.

Thaodan commented on 2012-12-21 12:38 (UTC)

nous: i fixed it by setting SUBLEVEL in /usr/src/linux-pf-3.7/Makefile to "1"

nous commented on 2012-12-21 11:59 (UTC)

Thaodan: I do. % cat /usr/lib/modules/3.6-pf/build/include/linux/version.h #define LINUX_VERSION_CODE 198144 #define KERNEL_VERSION(a,b,c) (((a) << 16) + ((b) << 8) + (c)) % cat /usr/lib/modules/3.7-pf/build/include/linux/version.h cat: /usr/lib/modules/3.7-pf/build/include/linux/version.h: No such file or directory % cat /usr/lib/modules/3.7.0-1-ARCH/build/include/linux/version.h cat: /usr/lib/modules/3.7.0-1-ARCH/build/include/linux/version.h: No such file or directory It would seem version.h is missing from 3.7. A simple copy from a *-headers-3.6 will temporarily resolve this.

Thaodan commented on 2012-12-21 05:25 (UTC)

Has someone an idea why drivers like nvidia don't build if SUBLEVEL in /usr/src/linux-pf-3.7 is empty?

Thaodan commented on 2012-12-21 03:40 (UTC)

My modifed PKGBUILD with proper pkgnames and description for optimized builds, I addded grayskys docs and disable numa (if not enabled) and I the upstream fix for watchdog regression as suggest:

graysky commented on 2012-12-20 22:32 (UTC)

/type on/typo/

graysky commented on 2012-12-20 22:27 (UTC)

...also, there is a type on in the kernel-33-gcc47-0 patch which I emailed the author about but haven't heard back from him. See:

graysky commented on 2012-12-20 22:26 (UTC)

@nous - Does the pf set contain this fix? If not you might wanna add it.

nous commented on 2012-12-20 22:20 (UTC)

Fixed, thanks. The repo is being populated right now.

cian1500ww commented on 2012-12-20 20:38 (UTC)

@walkindude Yep, you're right, the PKGBUILD for 3.7 in Arch testing doesn't have mtd in the for loop either.

walkindude commented on 2012-12-20 20:10 (UTC)

@cian1500ww because of for i in acpi asm-generic config crypto drm generated linux math-emu \ media mtd net pcmcia scsi sound trace video xen; do cp -a include/${i} "${pkgdir}/usr/src/linux-${_kernver}/include/" done in PKGBUILD i just deleted mtd and everything worked.. by the way, I got this when I wanted to build modules for virtualbox: DKMS make.log for vboxhost-4.2.4 for kernel 3.7-pf (x86_64) Fri Dec 21 00:07:23 MSK 2012 make: Entering directory `/usr/src/linux-3.7-pf' LD /var/lib/dkms/vboxhost/4.2.4/build/built-in.o LD /var/lib/dkms/vboxhost/4.2.4/build/vboxdrv/built-in.o CC [M] /var/lib/dkms/vboxhost/4.2.4/build/vboxdrv/linux/SUPDrv-linux.o In file included from /var/lib/dkms/vboxhost/4.2.4/build/vboxdrv/include/iprt/types.h:129:0, from /var/lib/dkms/vboxhost/4.2.4/build/vboxdrv/include/VBox/types.h:30, from /var/lib/dkms/vboxhost/4.2.4/build/vboxdrv/linux/../SUPDrvInternal.h:35, from /var/lib/dkms/vboxhost/4.2.4/build/vboxdrv/linux/SUPDrv-linux.c:31: include/linux/types.h:5:30: fatal error: uapi/linux/types.h: No such file or directory compilation terminated. make[2]: *** [/var/lib/dkms/vboxhost/4.2.4/build/vboxdrv/linux/SUPDrv-linux.o] Error 1 make[1]: *** [/var/lib/dkms/vboxhost/4.2.4/build/vboxdrv] Error 2 make: *** [_module_/var/lib/dkms/vboxhost/4.2.4/build] Error 2 make: Leaving directory `/usr/src/linux-3.7-pf'

cian1500ww commented on 2012-12-20 19:23 (UTC)

I'm getting the following error when packing linux-pf-headers: "cp: cannot stat ‘include/mtd’: No such file or directory" I'm using the default config.

Thaodan commented on 2012-12-19 18:08 (UTC)

Anyone has an idea how is the state of tuxonice for linux-3.7?

jnbek commented on 2012-12-18 22:40 (UTC)

Muchas Gracias @jakob

jakob commented on 2012-12-18 07:01 (UTC)

@jnbek: pfkernel is the repo maintained by nous. No idea who set up the other one or what's the benefit.

jnbek commented on 2012-12-18 03:40 (UTC)

which of the 'unofficial user repos' mirror this pkg? pflinux or linux-pf ? seems there are two...

commented on 2012-12-17 16:08 (UTC)

@jnbek Thanks, it worked.

jnbek commented on 2012-12-16 19:00 (UTC)

@nous: w00t!!! thanks :) @Decepteiskon, remove it, and it's corresponding md5sum (4th line from the bottom iirc, starts with d) from the PKGBUILD, this patch never actually applied, well at least for quite a while. The maintainer has stated that this will be removed when the 3.7 build is released.

commented on 2012-12-16 18:39 (UTC)

Can't compile, error: curl: (22) The requested URL returned error: 404 Not Found ...given when downloading interactive-governor.tar.gz

nous commented on 2012-12-15 18:03 (UTC)

Ok then, the customer is always right! I'll give the 2/3-digit kernel version option in 3.7-pf.

jnbek commented on 2012-12-14 20:31 (UTC)

When I did it last night, using yaourt it removed the old 3.6-pf and installed the 3.6.11-pf just fine. And there's no 3.6-pf dir in /lib/modules seems fine.

nous commented on 2012-12-14 19:14 (UTC)

@jnbek: A simple versioning preference option and an "if-fi" around the SUBLEVEL sed would be enough for that, but I don't know what happens if one compiles a 3-digit linux-pf and at the next update one forgets to select again a 3-digit version: does pacman remove the old modulesdir from /usr/lib/modules or it ends up accomodating both 3.7.1-pf and 3.7-pf? In the pacman manpage it says -U is "remove-then-add", so I'm guessing we're OK but what happens with 2-digit kernver packages downloaded from the repo and installed with -S over a previous 3-digit version?

jnbek commented on 2012-12-14 18:49 (UTC)

@ nous, I totally understand the rationale, I guess I came across a little on teh smartass side of the discussion initially. Perhaps, a possible solution would be a -fullversion package for those that don't mind the nvidia/vbox compilings, and then this one keeping the 2 digit versioning for the folks who don't wish to compile. I mean, it is just a one line difference in the PKGBUILD, that way you could do some A/B testing, if you will, to see which of the two get's the most attention, then y'all can at that point decide which of the two seems best. Just a thought.

nous commented on 2012-12-14 18:07 (UTC)

Incidentally, I've been having this discussion with post-factum (the patchset author) a couple of days now. Here's an excerpt from my rationale on why we should stick to 2-digit versioning: "[...] if we want to show the patchlevel and increment it with every release, then I'm OK with that, but there is an unbeatable advantage in leaving the patchlevel out of the kernel version: binary modules don't need rebuilding with every update and that was the way of linux-ARCH a few months back, until Tobias decided he didn't mind rebuilding nvidia and virtualbox with every kernel update." Most of the boxes I own or run sport an nvidia card and I hate it when I update the kernel and Xorg won't start at the next reboot due to a simple bump from 3.6.1 to 3.6.2. It's just unproductive.

J4913 commented on 2012-12-14 18:06 (UTC)

Yeah, I was aware of that. I only have PHC (which seems to be working with '3.6.11-pf' without a recompile, somehow) and VirtualBox (which is taken care of by the DKMS service). Either way, I needed to do it to test something in CrashPlan - it seems to fail to use inotify if the kernel version is only <major>.<minor>, for some crazy reason.

jnbek commented on 2012-12-14 17:51 (UTC)

@ J4913 just keep in mind, nous and the AUR maintainers have set it that way to prevent external module problems, so, you will likely need to rebuild any RAID, nVidia/ATI, Wireless, etc modules to accommodate the 3 level kernel value. I personally don't use any of that stuff so it's not an issue for me, I prefer a proper smelling uname -r as well, but if you find yourself having to spend 937 years rebuilding modules, you may want to relent as run it as offered.

J4913 commented on 2012-12-14 17:37 (UTC)

Actually, no, you're entirely correct: that was what I wanted. Thanks.

J4913 commented on 2012-12-14 09:29 (UTC)

Actually, what I wanted was the same version name as the stock kernel (which is just the version without '-pf', right?).

nous commented on 2012-12-14 06:40 (UTC)

The pf-patchset includes more patches than just BFS/CK. Post-factum is waiting for them to sync with upstream 3.7 before releasing 3.7-pf, unless some delay more than a few days in which case they're temporarily omitted from the patchset.

jnbek commented on 2012-12-14 04:07 (UTC)

-ck kernel just released 3.7.1, as an fyi

jnbek commented on 2012-12-14 03:47 (UTC)

@ J4913 Remove this line ~237: sed -ri 's|^(SUBLEVEL =).*|\1|' Makefile to keep the 3.6.11-pf style uname -r

J4913 commented on 2012-12-14 00:38 (UTC)

Is there an easy way to change the kernel name? I changed _kernelname and fixed _pfpatchname, but it still calls itself '3.6-pf' (output of 'uname -r').

nous commented on 2012-12-13 17:57 (UTC)

About time. Just comment it out, it didn't apply for months now anyway. I'll remove it with 3.7.1-pf.

J4913 commented on 2012-12-13 11:22 (UTC) seems to be deleted.

nous commented on 2012-12-09 16:45 (UTC)

Pastebin the error messages somewhere.

commented on 2012-12-09 13:08 (UTC)

Can't use non-standard config. Localmod/menuconfig - no matter.

Burning_aces commented on 2012-11-30 02:28 (UTC)

Just did then, building package now, will edit if it doesn't work. Thanks Nous

nous commented on 2012-11-29 07:00 (UTC)

Have you tried checking "Digital TV support"?

Burning_aces commented on 2012-11-29 04:47 (UTC)

That isn't an option for me

nous commented on 2012-11-13 11:15 (UTC)

The config options have changed slightly, but I believe all one needs is: Device Drivers ---> Multimedia Support ---> [*] DVB/ATSC adapters

Burning_aces commented on 2012-11-13 02:14 (UTC)

yeah, unless I did it wrong, that still didnt work... I can post the .config I used?

nous commented on 2012-11-12 12:30 (UTC)

Press "All comments" button and see the solution below. It's been discussed many times before.

Burning_aces commented on 2012-11-12 07:38 (UTC)

==> Starting package_linux-pf-headers()... cp: cannot stat âinclude/config/dvb/*.hâ: No such file or directory ==> ERROR: A failure occurred in package_linux-pf-headers(). Keep getting this at the end of the makepkg.

nous commented on 2012-11-07 11:32 (UTC)

@lockheed: My bad, I commented-out "depends=('linux-pf')" in package_linux_headers() and forgot the "&& depends=${depends}-${cpuopt}" directive below. Please use -dd in pacman, I'm uploading a new PKGBUILD.

lockheed commented on 2012-11-07 10:44 (UTC)

I can't upgrade linux kernel any more, because it has a vicious circle dependency: warning: cannot resolve "-core2", a dependency of "linux-pf-headers-core2" :: The following package cannot be upgraded due to unresolvable dependencies: linux-pf-headers-core2 Do you want to skip the above package for this upgrade? [y/N] error: failed to prepare transaction (could not satisfy dependencies) :: linux-pf-headers-core2: requires -core2

Thaodan commented on 2012-11-07 08:28 (UTC)

@nous: exept that it dosn't inclueds a propper conflicts array its not.

nous commented on 2012-11-07 07:44 (UTC)

It doesn't. It purposedly seds all newer AMD and Intel CPUs into k8 and core2 respectively. As I said before, it's non-sensical to create so many different packages for every single CPU out there. Furthermore, your submitted PKGBUILD besides being from an earlier (pre 3.6.8-pf) version, doesn't deal with a very important aspect: the conflicts() array, which is already a mess. Thanks for your interest and your work, but I won't implement it. Besides, if you really want the ultimately optimized kernel, I have provided the proper key in the PKGBUILD many months ago: uncomment the 'export KCFLAGS="-march=native -Ofast"' line just before the final make. Then see for a definitive explanation of my rationale.

Thaodan commented on 2012-11-07 02:46 (UTC)

your package detects false package names for the processor that were added with the '' patch. So I updated my modifed PKGBUILD according to your latest changes:

Thaodan commented on 2012-11-07 00:34 (UTC)

@nous: thanks that you've inclued the patch to set the right -march -mtune for past intel core2 processors!

nous commented on 2012-10-30 23:03 (UTC)

@travnick: I downloaded virtualbox-modules-bfs (, ran 'sed -i s/bfs/pf/g PKGBUILD', renamed virtualbox-modules-bfs.install into virtualbox-modules-pf.install and I got a perfect virtualbox-modules-pf package ( But I won't maintain it as I don't use virtualbox. I will compile it though and put it in [pfkernel] if someone keeps it up-to-date. @Thaodan: That's a negative. Virtualbox might be picky, but nvidia-pf (which I use) works without recompiling throughout patchlevels. I really can't see _one_ reason for a user to know the exact patchlevel of a running kernel, other than bug reporting, in which case it's easily obtainable by other means.

Thaodan commented on 2012-10-30 22:27 (UTC)

@Martdadinata666: as for me just cause uname shoud report the right kernel release.

travnick commented on 2012-10-30 20:26 (UTC)

As I wrote: When kernel updates, old modules (eg virtualbox) still are there and make conflicts, they are not loadable "ERROR: could not insert 'vboxdrv': Exec format error ERROR: could not insert 'vboxnetflt': Exec format error ERROR: could not insert 'vboxnetadp': Exec format error" But you cannot simply create new ones with dkms (virtualbox-hook), because the old one exist in kernel modules folder ... "Module vboxhost/4.2.2 already installed on kernel 3.6-pf/x86_64" So you must uninstall (remove vbox modules) and do dkms remove to remove old builds from dkms. But maybe there is need to create vbox package dedicated to linux-pf

martadinata666 commented on 2012-10-30 14:15 (UTC)

hmm, why you need to name this versionas 3.6.4? as long as im using this kernel, if you have modules like vbox, you just need to rebuild this modules if this kernel update to major version 3.5 to 3.6 or when virtualbox upgrade...

Thaodan commented on 2012-10-30 13:01 (UTC)

Ah ok thanks. A suggestion please rename the kernel release (the from uname) to the release number of the based kernel release, actual: 3.6.4.

nous commented on 2012-10-30 10:25 (UTC)

The pf-kernel patchset does not closely follow the, as it increments with updates from various patches, but usually includes the latest stable linux kernel. 3.6.6-pf apparently includes 3.6.4 from See

martadinata666 commented on 2012-10-29 23:31 (UTC)

so afaik, this have its own patch package which u can use just on bare linux 3.6 not 3.6.x :)

Thaodan commented on 2012-10-29 21:38 (UTC)

So its not 3.6.4?

Det commented on 2012-10-29 17:46 (UTC)


Thaodan commented on 2012-10-29 13:57 (UTC)

One question: Is it right that the kernel version is 3.6?

Thaodan commented on 2012-10-29 13:13 (UTC)

@nous I don't that there shoud be packages for all these cpu familys, its just nice too have, if you need i can upload builds for corei7avx and coreavxi

nous commented on 2012-10-29 12:59 (UTC)

@claudiaj: I've not encountered the zram issue myself, on several computers I run this kernel. The reports you point to indicate it's not linux-pf related though; therefore, we should expect a fix from upstream.

nous commented on 2012-10-29 07:40 (UTC)

I'm building 3.6.6-pf for i686 now. The problem with dropbox is solved, and right now the daemon is uploading 3.6.5-2/64-bit; 3.6.6 for x86_64 will follow before the end of the day. @Thaodan: it's not the menuconfig I'm concerned about, it's the PKGBUILD which should reflect the extra CPUs and the extra time, cpu-power and webspace needed to build and accommodate the additional packages. Which, I still insist, are not worth building as there's no gain whatsoever in performance kernel-wise. That being said, I might add the patch to an upcoming release, but I'll have to decide whether or not let the PKGBUILD know about i7*.

commented on 2012-10-28 23:40 (UTC)

@jakob: I had no intention to come off as rude. My main concern is zram, I just noted that after nous has stated 'Should be OK now', still 404's, indicating that not all is gravy just yet. I have this unfortunate tendency to spend days fine tuning menuconfig getting rid of stuff I'll never use and adding things I might think I'd like to see. Just my luck would have it though, there's always an update ready by the time I finish :P

Thaodan commented on 2012-10-28 23:33 (UTC)

@nou: this patch dosn't modifies the kernel code it just adds the option to set the right -march and -mtune for cpus that are never than year 2007 in menuconfig.

jakob commented on 2012-10-28 23:07 (UTC)

Hey claudiaj, this service by nous is an exceptional contribution that he has been committing since a long time now! I think we should be a bit more patient if there are computer problems on his side! It's always possible to just build the kernel, the PKGBUILDs are there, if you're in such need to have it now!

commented on 2012-10-28 22:40 (UTC)

I'm getting an insane amount of zram errors in dmesg [305870.803049] zram: Error allocating memory for compressed page: 121722, size=4118 [305870.803089] Write-error on swap-device (254:0:973776) Seems related to this Still getting 404 on the dropbox repo. How long do you imagine 'OK now' means working again?

nous commented on 2012-10-28 20:50 (UTC)

@dkasak: I upgraded my main dropbox box (which is headless)to systemd and lost all connectivity to it, as setting a static IP with systemd requires user intervention. Should be OK now.

nous commented on 2012-10-28 20:07 (UTC)

@Thaodan: thanks for your work, but I intend to follow the upstream kernel optimization options. Allow me to elaborate: 1. I believe Linus and the rest of the kernel developers know their job better than me. 2. Extreme kernel optimizations offer very little performance-wise; it's far more beneficial to optimize in user-space. Please, read this post of mine about it: 3. By large, newest CPUs offer only a few additional instruction sets, mostly multimedia-related, like Advanced Vector Extensions; the AES-NI instruction set is really not worth to mention, unless one AES encrypts-decrypts all day long. Therefore, a new CPU choice usually enters the kernel only after a major architecture evolution.

dkasak commented on 2012-10-28 11:04 (UTC)

I've been getting this error for a few days when trying to install from the unofficial repo: error: failed retrieving file 'linux-pf-core2-3.6.5-2-x86_64.pkg.tar.xz' from : The requested URL returned error: 404 NOT FOUND.

Thaodan commented on 2012-10-28 02:47 (UTC)

Forgot to mod everything in the PKGBUILD to be conform with the changes:

Thaodan commented on 2012-10-28 02:19 (UTC)

If forgot to say that it only affects Kconfig/menuconfig.

Thaodan commented on 2012-10-28 02:16 (UTC)

Added patch to include -march and -mtune flags for corei7, corei7-avx core-avxi and core-avx2 etc that were intrued in gcc 4.6 and 4.7 use it if you need: Patch: --- linux-pf/PKGBUILD 2012-10-26 11:34:57.000000000 +0200 +++ PKGBUILD 2012-10-28 03:03:53.340907261 +0100 @@ -33,7 +33,9 @@ "interactive-governor.tar.gz::" 'change-default-console-loglevel.patch' 'dcache.patch' - "${_pfpatchhome}${_pfpatchname}.bz2") # the -pf patchset + "${_pfpatchhome}${_pfpatchname}.bz2" # the -pf patchset + "" +) _aufs3git="git://" _aufs3name=aufs3 @@ -100,6 +102,8 @@ msg "Patching dcache.c" patch -Np1 -i "${srcdir}/dcache.patch" + # added gcc 4.7 support for Kconfig and menuconfig + patch -Np1 -i "${srcdir}/kernel-33-gcc47-0.patch" if [ "$CARCH" = "x86_64" ]; then cat "${startdir}/config.x86_64" >| .config else @@ -188,7 +192,7 @@ ;; esac cp -v .config ${startdir}/config.local - CPU=`egrep "MK8=y|MCORE2=y|MPSC=y|MATOM=y|MPENTIUMII=y|MPENTIUMIII=y|MPENTIUMM=y|MPENTIUM4=y|MK7=y|CONFIG_GENERIC_CPU=y|M686=y" ./.config` + CPU=`egrep "MK8=y|MCORE2=y|MPSC=y|MATOM=y|MPENTIUMII=y|MPENTIUMIII=y|MPENTIUMM=y|MPENTIUM4=y|MK7=y|CONFIG_GENERIC_CPU=y|M686=y|MBARCELONA=y|MBOBCAT=y|MBULLDOZER=y|MPILEDRIVER=y|MCOREI7=y|MCOREI7AVX=y|MCOREAVXI=y|MCOREAVX2=y" ./.config` CPU=`sed -e "s/CONFIG_M\(.*\)=y/\1/" <<<$CPU` CPU=`sed -e "s/CONFIG_GENERIC_CPU=y/GENERIC/" <<<$CPU` CPU=`sed -e "s/^686$/GENERIC/" <<<$CPU` @@ -571,4 +575,6 @@ 'd537a358c9f8b9cbcad34ba99f88af070f54d99c66d3e5d3d4734576ed2fb6e1' 'b9d79ca33b0b51ff4f6976b7cd6dbb0b624ebf4fbf440222217f8ffc50445de4' 'c49eca2478b7d911ee95a61c3f9080082b982ba4de34b9acff9b1ff2d5224957' - 'f9cf30022dcb86a70891c5c1f64713fa4da108beec72e5e264942c674268a6b6') + 'f9cf30022dcb86a70891c5c1f64713fa4da108beec72e5e264942c674268a6b6' + '8f2dad5b89dac8c76c3dd3ad902928d6032ec2c6ada41d873d752bad5586b154')

nous commented on 2012-10-25 19:36 (UTC)

That exactly was the purpose of removing the patchlevel number from the kernel version: to let binary blobs work without the need to recompile throughout all a given minor version series (e.g. 3.6.[1-N]-pf). The nvidia-pf module for one works as intended since 3.6.1-pf, at least on my computers. I wasn't aware of the virtualbox situation... I'll test it with the next -pf release and if your report is confirmed, I'll either consider changing the versioning scheme or creating an AUR package for virtualbox-pf-modules. At any rate, if you can and want create it yourself I'll happily compile it and include it in the [pfkernel] repo, just like nvidia-pf.

travnick commented on 2012-10-25 09:42 (UTC)

Shouldn't this package create folders in /usr/lib/modiles like: 3.6.3-1-pf instead of 3.6-pf? When kernel updates, old modules (eg virtualbox) still are there and make conflicts, they are not loadable "ERROR: could not insert 'vboxdrv': Exec format error ERROR: could not insert 'vboxnetflt': Exec format error ERROR: could not insert 'vboxnetadp': Exec format error" But you cannot simply create new ones with dkms (virtualbox-hook), because the old one exist in kernel modules folder ... "Module vboxhost/4.2.2 already installed on kernel 3.6-pf/x86_64"

nous commented on 2012-10-22 00:15 (UTC)

It's a known and discussed issue (search previous comments); just enable DVB without any drivers.

neitrino commented on 2012-10-21 18:29 (UTC)

Hmm.. 1. pacman -Syu 2. yaourt -S linux-rt Localmod and see: DEPMOD 3.6-pf -> Compressing package... ==> Starting package_linux-pf-headers()... cp: cannot stat ‘include/config/dvb/*.h’: No such file or directory ==> ERROR: A failure occurred in package_linux-pf-headers().

nous commented on 2012-10-20 07:13 (UTC)

Why don't you just put "echo cfq >| /sys/block/sda/queue/scheduler" in /etc/rc.local? CFQ is a quite large chunk of code to build into kernel, and some people (me included) use linux-pf on memory-restrained boxes too. That said though, it would make more sense to make to make NO-OP the default I/O scheduler and leave all other modularized, but we're addressing the silent majority here who just want their kernels to boot.

3V0LU710N commented on 2012-10-19 13:18 (UTC)

@nous: I've found if I want to use CFQ instead of BFQ as my main disk scheduler, I need to put in the mkinitcpio.conf modules section "cfq_iosched". Shouldn't it be better to have CFQ compiled as a "built-in" option in the kernel (like linux-ck does with CFQ and BFQ), so, we just needed to put "elevator=cfq" in the grub cmdline? Cheers and keep up the good work...

nous commented on 2012-10-04 23:45 (UTC)

Aufs3 isn't yet ready for 3.6; therefore it's disabled on configs.

martadinata666 commented on 2012-10-04 12:20 (UTC)

i already got to 3.6 you can edit the pkgbuild to patch the pf-patch and the console-level, and logo-linux patch only... Build success here, in my try... using another patch like i2c, channel-negative-one-maxim patch will get reject :)

PLum commented on 2012-10-04 10:57 (UTC)

When You find some time please update to new 3.6.1-pf :-), thx

nous commented on 2012-09-20 05:21 (UTC)

I think I also had some section mismatches but building continued. All binaries are available at the pfkernel repo.

martadinata666 commented on 2012-09-17 10:08 (UTC)

well pretty weird .... LD arch/x86/boot/setup.elf OBJCOPY arch/x86/boot/setup.bin BUILD arch/x86/boot/bzImage Setup is 17040 bytes (padded to 17408 bytes). System is 2749 kB CRC 4470713b Kernel: arch/x86/boot/bzImage is ready (#1) WARNING: modpost: Found 3 section mismatch(es). To see full details build your kernel with: 'make CONFIG_DEBUG_SECTION_MISMATCH=y' make[1]: *** [__modpost] Error 1 make: *** [modules] Error 2 ==> ERROR: A failure occurred in build(). Aborting...

J4913 commented on 2012-09-17 09:03 (UTC)

Fixed in the update, thanks.

nous commented on 2012-09-17 07:09 (UTC)

3.4.5-1 is up for grabs.

post-factum commented on 2012-09-17 04:48 (UTC)

Try to change depmod -b "$pkgdir" -F "$_kernver" to depmod -b "$pkgdir/usr" -F "$_kernver"

J4913 commented on 2012-09-16 19:21 (UTC)

I'm getting the same error that wind1r commented about: INSTALL sound/soundcore.ko DEPMOD 3.5-pf ERROR: could not open directory /home/j/linux-pf/pkg/linux-pf/lib/modules/3.5-pf: No such file or directory FATAL: could not search modules: No such file or directory ==> ERROR: A failure occurred in package_linux-pf(). Aborting... And similarly, the modules are in usr/lib/ (as, it seems, they should be). I don't know enough about depmod and stuff to know what other information might be useful.

post-factum commented on 2012-09-16 12:37 (UTC)

@leodag: do not hurry nous — he won't release updated PKGBUILD without me :).

leodag commented on 2012-09-14 23:42 (UTC)

upstream's 3.5.4 was released :)

nous commented on 2012-09-04 20:44 (UTC)

Wtf... Tobias introduced new thingamajigs into his PKGBUILD.

walkindude commented on 2012-09-04 20:11 (UTC)

%.*}.3-3 ?

nous commented on 2012-08-18 19:15 (UTC)

Sorry guys, it was a patch I forgot to remove from 3.5.1...

martadinata666 commented on 2012-08-18 17:33 (UTC)

@leodag i compiled by comment the amifritz section,,, i also get that error

leodag commented on 2012-08-18 17:14 (UTC)

When installing linux-pf 3.5.2-1, I get this: <many, many patches> ==> Patching for restless souls patching file net/wireless/chan.c Hunk #1 succeeded at 84 (offset 35 lines). Hunk #2 succeeded at 136 (offset 57 lines). patching file kernel/printk.c Hunk #1 succeeded at 61 (offset 3 lines). patching file drivers/isdn/hardware/mISDN/avmfritz.c Reversed (or previously applied) patch detected! Skipping patch. 3 out of 3 hunks ignored -- saving rejects to file drivers/isdn/hardware/mISDN/avmfritz.c.rej ==> ERROR: A failure occurred in build(). Aborting... The build failed. I'm using packer as a pacman wrapper, but almost always building linux-pf with it works.

commented on 2012-07-18 23:47 (UTC)

Wow, worked with the latest update. Sorry.

nous commented on 2012-07-18 20:42 (UTC)

Strange, are you using a pacman/makepkg wrapper to build?

commented on 2012-07-18 03:57 (UTC)

I getting error: INSTALL /var/abs/local/linux-pf/pkg/linux-pf/lib/firmware/yamaha/ds1e_ctrl.fw DEPMOD 3.4-pf ERROR: could not open directory /var/abs/local/linux-pf/pkg/linux-pf/lib/modules/3.4-pf: No such file or directory FATAL: could not search modules: No such file or directory While: ls /var/abs/local/linux-pf/pkg/linux-pf/usr/lib/modules/3.4-pf extramodules kernel modules.builtin modules.order

nous commented on 2012-06-22 05:55 (UTC)

I'll test on my personal box, along with the alleged TRANSPARENT_HUGEPAGE-breaks-TOI issue. If it works and does not break other things, I'll apply it in the PKGBUILD.

Huulivoide commented on 2012-06-21 19:51 (UTC)

It would seem it is needed to run 'make headers_install' for aufs3 headers to be installed correctly. Simple cp will result in non-working unusable headers. Currently aufs3-util package cannot be built with linux-pf due to this very reason, even after using the CPPFLAGS hack provided in comments. Please take a look at this mailinglist conversation, expecially the 6th message.

commented on 2012-06-19 09:43 (UTC)

My internet connection now is not cool enough to download and compile kernel, but about a year ago i used kernel without initrd and modules and it was booting faster. I have 8gb of RAM.

nous commented on 2012-06-18 18:20 (UTC)

On my laptop zram boot parameter is 'zram.num_devices=2', not zram.zram_num_devices.

nous commented on 2012-06-18 17:54 (UTC)

If you're low on physical RAM, you might want to append the keywords 'zcache' and 'zram.zram_num_devices=N' to the kernel boot parameters, where N your CPU cores, in order to activate zcache and allocate all memory to the CPUs for zram. Also, install zramswap from the AUR and add zramswap to /etc/rc.conf DAEMONS array. The results are impressive.

nous commented on 2012-06-18 17:34 (UTC)

Vekt: you realize that you won't probably get a measurable speed-up, don't you? Please, apply the following patch to PKGBUILD and test your new kernel with bootchart. If there's significant increase, I'll implement it (and probably build one kernel for my laptop too). --- PKGBUILD 2012-06-18 01:06:09.000000000 +0300 +++ PKGBUILD.koko 2012-06-18 20:29:22.762549123 +0300 @@ -183,2 +183,3 @@ echo " <O> make oldconfig" + echo " <L> make localyesonfig" echo " <ENTER> to skip configuration and start compiling" @@ -196,2 +197,4 @@ ;; + l) make localyesconfig + ;; default)

commented on 2012-06-18 09:45 (UTC)

Please, add a posibility to compile it with "make localyesconfig". I wouldn't like to have any modules in my system in order to make it boot faster, but there is no possibility to do "make localyesconfig"... Thank you.

J4913 commented on 2012-06-15 19:14 (UTC)

Ah, great. Thanks.

nous commented on 2012-06-15 19:00 (UTC)

Not strange at all, see and update to 3.4.1-4.

J4913 commented on 2012-06-15 11:29 (UTC)

I got an e-mail about a comment here, but it seems to have been removed. I'm on the 3.4 stock kernel now, and it's working fine - strange.

J4913 commented on 2012-06-14 10:58 (UTC)

I seem suddenly to have lost the ability to run 32-bit programs with this (on a 64-bit system), both with the repo versions and when I compile myself. The stock kernel works fine, but it's not on 3.4 yet, so I don't know if it's 3.4 or just pf. Any ideas?

nous commented on 2012-06-12 20:48 (UTC)

When asked by the PKGBUILD, make menuconfig, go to "Power management and ACPI options" and deselect "Enhanced Hibernation (TuxOnIce)".

Burning_aces commented on 2012-06-12 17:21 (UTC)

@nous: Sorry, I meant how do I build the kernel without Tuxonice

nous commented on 2012-06-12 15:33 (UTC)

Burning_aces: see

Burning_aces commented on 2012-06-12 14:44 (UTC)

How do I disable TOI?

nous commented on 2012-06-12 05:55 (UTC)

Disable zcache and zram (they're in staging), as they currently break TOI.

Burning_aces commented on 2012-06-11 22:04 (UTC)

I keep getting the following error: CC kernel/power/tuxonice_compress.o kernel/power/tuxonice_compress.c: In function ‘toi_compress_write_page’: kernel/power/tuxonice_compress.c:183:25: error: too few arguments to function ‘memory_bm_test_bit_index’ In file included from kernel/power/tuxonice.h:24:0, from kernel/power/tuxonice_compress.c:19: kernel/power/power.h:339:12: note: declared here kernel/power/tuxonice_compress.c:183:25: warning: left-hand operand of comma expression has no effect [-Wunused-value] make[2]: *** [kernel/power/tuxonice_compress.o] Error 1 make[1]: *** [kernel/power] Error 2 make: *** [kernel] Error 2 ==> ERROR: A failure occurred in build(). Aborting...

nous commented on 2012-06-10 16:20 (UTC)

Erm... it should be 'hg update 40', not 'revert'. Glad it worked otherwise though.

commented on 2012-06-10 14:48 (UTC)

wow, it compiled like a charm! ty, nous!

commented on 2012-06-10 13:43 (UTC)

@nous unfortunatly: $ hg revert 40 40: no such file in rev 015486e5e37d trying to compile with "_minor=3 \n _pfrel=6" Thank you

nous commented on 2012-06-10 11:43 (UTC)

Scratch that, it won't probably work as it's a minor version bump, not just a patchlevel one. Do the following: $ hg clone $ cd linux-pf $ hg revert 40 And you'll have 3.3.6-pf ready for compilation.

nous commented on 2012-06-10 11:18 (UTC)

Just download this tarball and edit the PKGBUILD as follows: _minor=3 _pfrel=6 and build with 'makepkg --skipinteg'

commented on 2012-06-10 11:05 (UTC)

Hi, nous! Unfortunatly I updated to 3.4 from 3.3 mindlessly this time, and now i'm having some heavy mindfuck with radeon video. how could i get a previos version of your excelent package for Archlinux? It would be awesome, if you share the PKGBUILD for v.3.3! Hope for you reply! Thanks

nous commented on 2012-06-05 11:15 (UTC)

You might succeed compiling nvidia-pf by editing its PKGBUILD and setting good and bad kernver.

lockheed commented on 2012-06-05 11:11 (UTC)

I just upgraded linux-pf before reading this thread and before discovering nvidia-pf is not compatible with it. I have not a very nice feeling that once I reboot, I am screwed.:)

nous commented on 2012-06-05 11:06 (UTC)

3.4.1-1 is up but not for grabs (unless you build yourself and don't use tuxonice); it croaks when compiling tuxonice_compress.o, so you shouldn't remove 3.3.6 just yet. Please wait for 3.4.1-2.

nous commented on 2012-06-01 12:16 (UTC)

The current version is 3.3.6; please update your database. What's more, p4 somehow fails to build with my repobuild script on i686. You'll have to use either p3 or the generic one, sorry.

cuihao commented on 2012-06-01 11:54 (UTC)

error: failed retrieving file 'linux-pf-p4-3.3.4-1-i686.pkg.tar.xz' from : The requested URL returned error: 404

post-factum commented on 2012-04-27 16:31 (UTC)

You are welcome to visit pf-kernel community forum:

msx commented on 2012-04-16 03:46 (UTC)

Hi all, adding this repo to your /etc/pacman.conf will let you download an already compiled linux-pf kernel that matches your CPU architecture: [pfkernel] # Generic and optimized binaries of the ARCH kernel patched with BFS, TuxOnIce, BFQ, Aufs3 # linux-pf, kernel26-pf, gdm-old, nvidia-pf, nvidia-96xx, xchat-greek, arora-git Server =$arch

nous commented on 2012-04-13 20:49 (UTC)

I could, but it's not practical and difficult PKGBUILD-wise, as it would require several changes. It's much easier for you to configure and compile the package once, and then use the "Hit <Y> to use your running kernel's config" PKGBUILD option at every subsequent compile (that's how I do it for my laptop tailored linux-pf). To considerably reduce compile time, you could install modprobed_db from the AUR ( and use the "Hit <L> to run 'make localmodconfig'" option the _first_ time you compile your custom kernel.

shadowed87 commented on 2012-04-13 14:03 (UTC)

hello, thanks for this awesome pkg...a question: is it possible to add in the repository a kernel with these config (for laptops) Notebook / mobile device: 300 Hz Tickless Full preemption CPU frequency scaling, ondemand default taken here:

nous commented on 2012-04-09 05:47 (UTC)

ericab: In both AUR and repo, nvidia-pf is updated; please retry.

commented on 2012-04-09 01:53 (UTC)

arg; ==> Finished making: linux-pf 3.3.1-2 (Sun Apr 8 18:08:53 PDT 2012) ==> Continue installing linux-pf ? [Y/n] ==> [v]iew package contents [c]heck package with namcap ==> --------------------------------------------------- ==> loading packages... resolving dependencies... looking for inter-conflicts... error: failed to prepare transaction (could not satisfy dependencies) :: nvidia-pf: requires linux-pf<3.3

nous commented on 2012-04-07 23:01 (UTC)

Latest linux-pf and nvidia-pf for all CPUs are up for grabs at [pfkernel]

nous commented on 2012-04-06 05:30 (UTC)

That version is too old, try 'pacman -Syw linux-pf-atom'

gaougalos commented on 2012-04-05 10:58 (UTC)

Is there a problem on this package (linux-pf-atom-3.2.7-2-i686.pkg.tar.xz) on your repo? $ pacman -Sw linux-pf-atom resolving dependencies... Targets (1): linux-pf-atom-3.2.7-2 Total Download Size: 39.68 MiB Proceed with download? [Y/n] y :: Retrieving packages from pfkernel... error: failed retrieving file 'linux-pf-atom-3.2.7-2-i686.pkg.tar.xz' from : The requested URL returned error: 404 warning: failed to retrieve some files from pfkernel error: failed to commit transaction (download library error) Errors occurred, no packages were upgraded.

nous commented on 2012-04-03 21:04 (UTC)

Sorry guys, 3.2.7-4 was a working draft for 3.3 and was uploaded by mistake. 3.2.7-3 still is the latest and greatest.

ryosei commented on 2012-04-03 12:48 (UTC)

and here...

hermes14 commented on 2012-04-03 12:48 (UTC)

And here...

lockheed commented on 2012-03-31 15:49 (UTC)

And here.

commented on 2012-03-31 15:39 (UTC)

The same problem here: ==> Starting package_linux-pf-headers()... cp: cannot stat `include/aufs3': No such file or directory ==> ERROR: A failure occurred in package_linux-pf-headers(). Aborting...

commented on 2012-03-31 04:30 (UTC)

I have a problem with 3.2.7-4 and stock arch config ==> Starting package_linux-pf-headers()... cp: cannot stat `include/aufs3': No such file or directory ==> ERROR: A failure occurred in package_linux-pf-headers(). Aborting... ==> ERROR: Makepkg was unable to build linux-pf.

nous commented on 2012-03-31 00:10 (UTC)

You can't, it's obsoleted. The latest binaries are at 3.2.7-3. Try 'pacman -Sy linux-pf-core2'. Alternatively, download from the AUR and edit $pkgrel in the PKGBUILD.

commented on 2012-03-30 12:35 (UTC)

Where can we get linux-pf-core2-3.2.7-2-i686.pkg.tar.xz from? sudo pacman -S linux-pf-core2 resolving dependencies... looking for inter-conflicts... Targets (1): linux-pf-core2-3.2.7-2 Total Download Size: 39.66 MiB Total Installed Size: 56.85 MiB Proceed with installation? [Y/n] y :: Retrieving packages from pfkernel... error: failed retrieving file 'linux-pf-core2-3.2.7-2-i686.pkg.tar.xz' from : The requested URL returned error: 404 warning: failed to retrieve some files from pfkernel error: failed to commit transaction (download library error) Errors occurred, no packages were upgraded.

commented on 2012-03-25 11:49 (UTC)

That explains it. I have a single-core CPU.

nous commented on 2012-03-16 13:34 (UTC)

I took the time to compile a wiki page for linux-pf:

nous commented on 2012-03-12 22:40 (UTC)

It works. TuxOnIce people, add this to your /etc/hibernate/tuxonice.conf: "ProcSetting no_multithreaded_io 1".

post-factum commented on 2012-03-12 21:22 (UTC)

Possible temporary fix: Give it a try.

post-factum commented on 2012-03-08 23:23 (UTC)

Here is my call for help with TOI+BFS issue:

nous commented on 2012-03-03 18:48 (UTC)

TOI scans the partitions for a hibernation image, so it should even work without any directives.

technic93 commented on 2012-03-02 17:33 (UTC)

I have resume=swap:/dev/sdxx instead if resume=/dev/sdxx, could this cause the error?

commented on 2012-03-02 14:58 (UTC)

What exactly is error -22 by the way? I have the "resume" hook enabled and "lzo" in the MODULES list of mkinitcpio.conf. I am using pm-utils with the UPower dbus scripts. I have a file in /etc/pm/sleep.d that sets /sys/power/tuxonice/compression/algorithm to "lzo". I have another file in /etc/pm/config.d that sets the variable "SLEEP_MODULE" to "tuxonice". I also passed "resume=/dev/sdxx" to my kernel, with "sdxx" being my swap partition. Hope that helps.

nous commented on 2012-03-01 06:00 (UTC)

Can't confirm. I built TOI into the kernel and it fails with -22.

technic93 commented on 2012-02-29 14:14 (UTC)

Good news, I'll try it too.

commented on 2012-02-29 13:35 (UTC)

Good news: I hibernated then blacklisted lzo with the kernel command line. The system then fails to resume with an error "failed to initialize compressor". That means the lzo compressor is indeed being used.

commented on 2012-02-29 09:13 (UTC)

@technic93: I am not completely sure if lzo is used by TuxOnIce or not, but both /sys/power/tuxonice/compression/algorithm and the /etc/hibernate config file are set to use lzo. Plus hibernation is quite faster than when using the built-in function. I will test further to see if lzo is being used or not.

technic93 commented on 2012-02-29 07:17 (UTC)

Hi deathfantasy, is LZO actually used by tuxonice?

commented on 2012-02-29 06:46 (UTC)

nous: I built LZO as a module.

nous commented on 2012-02-27 17:55 (UTC)

deathfantasy: Please elaborate: did you also build the compressor in-kernel? Which one, lzo or lzf?

commented on 2012-02-27 12:48 (UTC)

I built TuxOnIce into the kernel instead of as a module, and it works for me.

nous commented on 2012-02-24 21:42 (UTC)

I've personally tested lzf and it fails too.

technic93 commented on 2012-02-24 15:39 (UTC)

I guess we could add lzf module to the config.

technic93 commented on 2012-02-23 20:12 (UTC)

thank you, I've not found this in wiki.

nous commented on 2012-02-23 16:02 (UTC)

technic93: Please see my comment on 13 Nov 2011 13:59:23. You must add your allocator of choice to /etc/mkinitcpio.conf, MODULES array [e.g. toi_swap, toi_compress (which still fails to resume with lzo; compressor must be disabled) and optionally toi_userui].

technic93 commented on 2012-02-23 15:37 (UTC)

Hi, Why neither CONFIG_TOI_FILE nor CONFIG_TOI_SWAP is on by default?

nous commented on 2012-02-07 17:46 (UTC)

It's not PKGBUILD related; it downloads ok here, but I use wget instead of curl at the DLAGENTS array in /etc/makepkg.conf: DLAGENTS=('ftp::/usr/bin/wget -c --passive-ftp -t 3 --waitretry=3 -O %o %u' 'http::/usr/bin/wget -c -t 3 --waitretry=3 -O %o %u' 'https::/usr/bin/wget -c -t 3 --waitretry=3 --no-check-certificate -O %o %u' 'rsync::/usr/bin/rsync -z %u %o' 'scp::/usr/bin/scp -C %u %o') The relevant option in wget for https is '--no-check-certificate'.

leafonsword commented on 2012-02-07 12:36 (UTC)

-> 正在下载 interactive-governor.tar.gz... % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 0 0 0 0 0 0 0 0 --:--:-- 0:00:01 --:--:-- 0curl: (77) error setting certificate verify locations: CAfile: /etc/ssl/certs/ca-certificates.crt CApath: none ==> 错误: 无法下载 interactive-governor.tar.gz 正在放弃...

nous commented on 2012-01-27 09:04 (UTC)

You need to update the nvidia-pf package first, the one from the AUR is fine.

commented on 2012-01-27 01:54 (UTC)

thanks @nous, @crush that issue is fixed now, but now a new one ! see it here:

nous commented on 2012-01-26 20:32 (UTC)

I had fixed it quite a while ago (see, but an older version of the PKGBUILD somehow slipped in. Uploaded fixed version again.

liviucmg commented on 2012-01-26 19:46 (UTC)

@ericab I'm getting the same thing. I suppose the default kernel doesn't come with the config options. You can use <N> without a problem, thought.

commented on 2012-01-26 18:58 (UTC)

anyone able to help with this ?? --------------------------------- ======================================================= ==> You might be prompted below for some config options ======================================================= ==> Hit <Y> to use your running kernel's config (needs IKCONFIG and IKCONFIG_PROC) ==> Hit <L> to run 'make localmodconfig' ==> Hit <N> (or just <ENTER>) to build an all-inclusive kernel like stock -ARCH (warning: it can take a looong time) Y ==> running 'sudo modprobe configs' ==> ERROR: A failure occurred in build(). Aborting... ==> ERROR: Makepkg was unable to build linux-pf. ==> Restart building linux-pf ? [y/N] ==> --------------------------------- ==>

nous commented on 2012-01-24 14:47 (UTC)

Thanks for the feedback on compiling. Your second couple of lines should be reversed; I'll put it in the next update.

commented on 2012-01-24 12:41 (UTC)

Had the same error as user crush. Just fetched the package again and it compiles now. Also a note on the PKGBUILD: makepkg automatically decompresses every file in ${source}. The following lines can be changed: _pfpatchname="patch-${_basekernel}.${_pfrel}${_kernelname}.bz2" -> _pfpatchname="patch-${_basekernel}.${_pfrel}${_kernelname}" ${_pfpatchhome}${_pfpatchname}.bz2) # the -pf patchset -> ${_pfpatchhome}${_pfpatchname}) # the -pf patchset bzip2 -dc ${srcdir}/${_pfpatchname} | patch -Np1 -> patch -Np1 -i ${_pfpatchname} It doesn't really make any real difference though. Thanks for the package !

nous commented on 2012-01-24 11:34 (UTC)

Beats the crap out of me. This morning I tested it and worked OK, then it broke. I took the CVE patch from and it worked again...

liviucmg commented on 2012-01-24 09:19 (UTC)

I'm getting the following error: $ aurget -S linux-pf [...] ==> Fetching and applying aufs3 patches [...] patching file security/security.c patching file fs/proc/base.c Hunk #1 succeeded at 194 (offset -4 lines). Hunk #2 succeeded at 205 (offset -4 lines). Hunk #3 succeeded at 214 (offset -4 lines). Hunk #4 FAILED at 699. Hunk #5 succeeded at 821 (offset 64 lines). Hunk #6 succeeded at 830 (offset 64 lines). Hunk #7 succeeded at 862 (offset 64 lines). Hunk #8 succeeded at 882 (offset 64 lines). 1 out of 8 hunks FAILED -- saving rejects to file fs/proc/base.c.rej ==> ERROR: A failure occurred in build(). Aborting... It worked fine just yesterday before the update. Any ideas?

nous commented on 2012-01-24 07:17 (UTC)

hyperion:[nous]:/tmp% ./mempodipper =============================== = Mempodipper = = by zx2c4 = = Jan 21, 2012 = =============================== [+] Opening socketpair. [+] Executing child from child fork. [+] Waiting for transferred fd in parent. [+] Opening parent mem /proc/23140/mem in child. [+] Sending fd 5 to parent. [+] Received fd at 5. [+] Assigning fd 5 to stderr. [+] Reading gpasswd for exit@plt. [+] Resolved exit@plt to 0x4018a0. [+] Calculating gpasswd padding. [+] Seeking to offset 0x401890. [+] Executing gpasswd with shellcode. sh-4.2# Please, everyone UPDATE to 3.2.1-5

nous commented on 2012-01-22 21:36 (UTC)

@vadik I'm waiting for linux-ARCH to change that before I do it too.

commented on 2012-01-22 15:21 (UTC)

kmod replaces module-init-tools.

commented on 2012-01-20 09:22 (UTC)

Thank you Nous. After updating works .

nous commented on 2012-01-19 22:02 (UTC)

It was not the headers after all. Somehow, /usr/src/linux-3.2-pf/vmlinux was getting stripped. I recompiled a generic x86_64 linux-pf and now it works (I had the same problem here compiling nvidia) - virtualbox compiles OK too. You can download it from the repo, the optimized binaries are on their way.

commented on 2012-01-19 18:44 (UTC)

The problem may be in the headers. Just to test I made a simple cp -rv /usr/src/linux-3.2.1-1-ARCH /usr/src/linux-3.2-pf and he compiled but the module did not work .

nous commented on 2012-01-19 18:33 (UTC)

Googling around, I saw some talk (mainly by archers) with the same problem, with 3.1.9-ARCH (3.2 too), related to libarchive. I'll investigate more; in the meanwhile, if anyone finds a solution please post.

post-factum commented on 2012-01-19 18:20 (UTC)

The issue with TOI as module is fixed by Nigel but not pushed to git repo yet. I expect it to be included in 3.2.2-pf. @lgf: I've got no idea :/. Probably, some problem with headers?

commented on 2012-01-19 17:25 (UTC)

After upgrading to 3.2 and have got an error when compiling the modules VirtualBox and catalyst, in both cases is the same (FATAL: vmlinux is truncated. Sechdrs [i]. Sh_offset = 18446744073709551615> sizeof (* hrd) = 64) if it goes to boot the default kernel even this also being the 3.2 modules compiled without problem.

post-factum commented on 2012-01-19 00:33 (UTC)

I'll mail him.

nous commented on 2012-01-18 23:11 (UTC)

Somehow, the freeze_kernel_threads and in_suspend symbols are not passed to the kernel image, with tuxonice as all-modules. It's not that important to devote time to it. Maybe just email Nigel?

post-factum commented on 2012-01-18 22:21 (UTC)

If there are any ideas how to fix it, you are welcome.

nous commented on 2012-01-18 11:29 (UTC)

"<*> Enhanced Hibernation (TuxOnIce)" seems to do the trick. The rest of the submenu are again modules.

nous commented on 2012-01-18 07:01 (UTC)

The error is not PKGBUILD related; it only appears with tuxonice configured as modules. I just tested a different config with built-in tuxonice and it compiled OK.

hermes14 commented on 2012-01-17 23:18 (UTC)

Same error here

nixtrian commented on 2012-01-17 20:22 (UTC)

build halts with: BUILD arch/x86/boot/bzImage Setup is 17036 bytes (padded to 17408 bytes). System is 2521 kB CRC e0604fdd Kernel: arch/x86/boot/bzImage is ready (#1) ERROR: "freeze_kernel_threads" [kernel/power/tuxonice_core.ko] undefined! ERROR: "in_suspend" [kernel/power/tuxonice_core.ko] undefined! WARNING: modpost: Found 9 section mismatch(es). To see full details build your kernel with: 'make CONFIG_DEBUG_SECTION_MISMATCH=y'

nous commented on 2012-01-17 18:15 (UTC)

Updated and uploaded (untested, as usual :) Will start batch building now, expect the repos to be populated by tommorow morning EET.

nixtrian commented on 2012-01-17 16:03 (UTC)

3.2 released

Rolinh commented on 2012-01-09 08:25 (UTC)

Don't flag it out of date because it is not the same version as mainline. The latest pf-kernel patch is 3.1.6 at this point, as you can see here:

nous commented on 2011-11-28 21:47 (UTC)

LinuxIMQ is back in. If you want it though, you'll have to configure it in yourselves.

nous commented on 2011-11-21 21:53 (UTC)

Cheers, bardo. I've used a few diff tools from time to time but none quite impressed me. Although I must admit I'm not their most expert user. I'll have a look at meld too.

bardo commented on 2011-11-21 19:09 (UTC)

@nous: might not be the holy grail, but I suggest using meld when you need to compare a newer PKGBUILD to your customizations, it saves a lot of headaches. You can also try vimdiff if you are more frugal or dislike gtk. Or just "svn diff" the latest official build with the version you synchronized to, discover what changed since then and decide what to integrate in your package. HTH :)

nous commented on 2011-11-20 20:32 (UTC)

@kalpik: The ones from /lib/modules/3.1-pf/kernel/kernel/power [_bio, _compress (lzo still fails here), _core, _file/_swap and _userui] I believe that specifying one (e.g. tuxonice_swap) which depends on _bio and _core would do, but haven't tested as I don't use an initrd. @myra: That's about how I had it till recently: [[ -e include/config/dvb/ ]] && cp include/config/dvb/*.h ${pkgdir}/usr/src/linux-${_kernver}/include/config/dvb/ The thing is, I _must_ synchronize with the official linux-ARCH; their config, patches/fixes and packaging on every minor bump. It's very tedious and tiring for a maintainer to compare line-by-line two huge PKGBUILDs and merge them into one. This time I forgot to add the aforementioned line, which resulted in your error (mine too!) But as I explained, I decided to leave it as it was. You see, for people running custom/tailored kernels, selecting <M> for DVB for Linux at "Device Drivers/Multimedia support" and leaving everything else out, creates just the necessary dvb.h without any further demands.

commented on 2011-11-20 19:28 (UTC)

nous: About the dvb headers, would it not be as easy to add this to the PKGBUILD # mkdir -p "${pkgdir}/usr/src/linux-${_kernver}/include/config/dvb/" if [ -a include/config/dvb/*.h ] ; then cp include/config/dvb/*.h "${pkgdir}/usr/src/linux-${_kernver}/include/config/dvb/*.h fi Seems as though that would save building the modules. I haven't installed my build yet cause I don't want to rebuild nvidia until tonight, but the packaging succeeds this way. Myra

kalpik commented on 2011-11-20 04:26 (UTC)

"tuxonice is no longer built-in; You MUST add the relevant modules in your /etc/mkinitcpio.conf MODULES array" What modules do I need to add?

nous commented on 2011-11-19 19:49 (UTC)

Since the headers package section is taken as-is from linux-ARCH, which has almost all options 'moduled', it expects the dvb headers in place. I too have had this error in my tailored laptop config and circumvented it simply by enabling as module the dvb submenu in drivers/multimedia.

lucak3 commented on 2011-11-19 11:58 (UTC)

Sorry for deleted message, i found the real problem: - _kernver too has KARCH problem

lucak3 commented on 2011-11-19 11:50 (UTC)

There are some problems in package_linux-pf-headers(): - Missing include/config/dvb/*.h files (i did build again to confirm it wasn't a temp issue) - Used KARCH variable defined only in package_linux-pf()

nous commented on 2011-11-17 22:43 (UTC)

Thanks to Julian who caught an incomplete path in the aufs3 branch, 3.1.1-7 fetches the aforementioned patch too.

nous commented on 2011-11-15 21:04 (UTC)

My bad, guys. See I also reverted to the good ol' 3.X-pf versioning scheme for modules, as having to rebuild nvidia or other binary blobs when pf is incremented is redundant.

ryosei commented on 2011-11-15 20:00 (UTC)

I've got the same issue and I'm not using yaourt... I do "makepkg -i" get an error then I do "pacman -U -- -3.1.1-5-x86_64.pkg.tar.xz linux-pf-headers-3.1.1-5-x86_64.pkg.tar.xz" and i get an error again... it seems to me that the name of the package don't get catch by the first packaging operation makepkg does... I don't know much about split packages so I can't tell what is the cause but surely something seems wrong...

commented on 2011-11-15 19:34 (UTC)

@nous, how can i get this package installed then ? ive got the same problem as gfang

nous commented on 2011-11-15 13:52 (UTC)

As of 3.1.1-5, linux-pf is a split package: linux-pf and linux-pf-headers. @gfang It's yaourt's issue; perhaps it's got something to do with the oodoo PKGBUILD does to get past the AUR parser...

commented on 2011-11-15 00:39 (UTC)

Compile completes successfully but error on install... "error: missing package name in /tmp/yaourt-tmp-root/PKGDEST.I3H/-3.1.1-5-i686.pkg.tar.xz" "error: '/tmp/yaourt-tmp-root/PKGDEST.I3H/-3.1.1-5-i686.pkg.tar.xz': invalid or corrupted package" Reproduced on both i686 and x86_64 machines.

nous commented on 2011-11-14 10:16 (UTC)

@Cdh The kernel CPU configuration menu doesn't offer i[357] as an option. Therefore, I won't force things unnecessarily. However, you can set your KCFLAGS and KCPPFLAGS per your heart's desire at the 'make' directive in the PKGBUILD (and cross your fingers :) See for an explanation as to why I don't. @shahid and strephil: I'll let you know, thanks for stepping up.

haagch commented on 2011-11-13 23:57 (UTC)

I guess core2 should work for i3/i5/i7 first and second generation, but will there be separate packages?

krevedko commented on 2011-11-13 19:59 (UTC)

noun, you can review my candidature for new maintainer. I have several self-written pkgbuilds here.

nous commented on 2011-11-13 17:52 (UTC)

The interactive governor patch breaks compilation - disabled.

commented on 2011-11-13 17:18 (UTC)


nous commented on 2011-11-13 13:59 (UTC)

The interactive CPU governor is available as of 3.1.1-3! AUFS3 has not yet sync'ed with 3.1; this means that my precompiled repo packages which are being furiously compiled right now, will not sport it. Those who need it, will have to makepkg themselves. Also: tuxonice is no longer built-in; You MUST add the relevant modules in your /etc/mkinitcpio.conf MODULES array or your boxes won't resume.

nous commented on 2011-11-13 13:47 (UTC)

The interactive CPU governor is available as of 3.1.1-3! AUFS3 has not yet sync'ed with 3.1; this means that my precompiled repo packages which are being furiously compiled right now, will not sport it.

strephil commented on 2011-11-13 13:32 (UTC)

I know bash and Arch well and I could manage to maintain PKGBUILD. I although have some experience in kernel compilation.

nous commented on 2011-11-12 21:18 (UTC)

AUFS3 is not yet ported to 3.1, thus the error. I'm sorry I uploaded an untested PKGBUILD, but my free time has become really scarce... I've uploaded a new one, with sanity check on aufs3 git. When aufs-3.1 becomes available, it should be pulled automagically.

xF0E commented on 2011-11-12 14:26 (UTC)

ty guys, solved by removing aufs patch.

post-factum commented on 2011-11-12 14:01 (UTC)

@xF0E: or you may try to change this string in PKGBUILD: git checkout origin/aufs3.0 to git checkout origin/aufs3.1 and try to build again. It seems, that nous has forgotten about it.

post-factum commented on 2011-11-12 13:56 (UTC)

@xF0E: that function is defined by aufs3-loopback.patch file, you may checkout aufs3.0 and check yourself.

post-factum commented on 2011-11-12 13:55 (UTC)

@xF0E: loop_real_file function in drivers/block/loop.c is related to aufs and appears ONLY in aufs. So, you've patched pf-kernel with aufs before build. Please, revert aufs or disable it in PKGBUILD and try again.

xF0E commented on 2011-11-12 13:35 (UTC)

@post-factum ty for your comment: just some screens above LD error i found this: drivers/block/loop.c: In function ‘loop_real_file’: drivers/block/loop.c:661:32: error: ‘const struct super_operations’ has no member named ‘real_loop’ drivers/block/loop.c:662:33: error: ‘const struct super_operations’ has no member named ‘real_loop’ make[2]: *** [drivers/block/loop.o] Error 1 make[1]: *** [drivers/block] Error 2 make: *** [drivers] Error 2 make: *** Waiting for unfinished jobs.... this is not aufs relataed, since i don't checked aufs support before compilation start.

post-factum commented on 2011-11-12 12:22 (UTC)

@xF0E: try to find errors above.

post-factum commented on 2011-11-12 12:21 (UTC)

Yep, aufs seems to be broken.

xF0E commented on 2011-11-12 12:21 (UTC)

unfortunately i get this error on compiling the source every time i try to build the kernel: LD net/built-in.o ==> ERROR: A failure occurred in build(). Aborting... ==> ERROR: Makepkg was unable to build linux-pf

prMoriarty commented on 2011-11-12 11:39 (UTC)

fs/aufs/super.c:758:2: error: unknown field ‘real_loop’ specified in initializer

nous commented on 2011-11-06 19:06 (UTC)

You are 100% right but I'm still using this on my laptop for its working lzo, so I'll allow myself a small "maintainer's prerogative"...

schivmeister commented on 2011-11-06 10:33 (UTC)

Please request a merge with linux-pf, else let's help remove packages with older naming schemes since they disturb the consistency of the repos and the distribution in general. The working state of a specific version is independent of the naming scheme.

nous commented on 2011-10-28 20:04 (UTC)

Thanks for pointing out, added git to makedepends.

prMoriarty commented on 2011-10-28 18:47 (UTC)

add to dependencies: "git"

nous commented on 2011-10-27 14:11 (UTC)

Please, be more specific: which patch? The patches that could break the process are the aufs3 ones from git. They already are covered with the || operator, as you described (as a matter of fact, the moment I uploaded the package at least one wouldn't apply cleanly and its exit status was caught by that ||).

dflt commented on 2011-10-27 12:11 (UTC)

I'm getting build error from this pkg. It's because some patches apply partialy and exiting with status diffrent then 0. So you need to add at the end of every line that contains patch sth like this: || echo asdf, so the whole line should look like this: patch -p1 blablabla ||echo asdf (echo returns 0 as default and || means OR so if patch does not run succesly bash executes echo and echo returns 0 and everyone is happy)

nous commented on 2011-10-26 11:17 (UTC)

Gr1N: just hit <ENTER> at all prompts. But then again, you'll get the generic pf kernel which is also available at the repo and that kinda beats the purpose of self-compiling.

commented on 2011-10-26 09:30 (UTC)

Before starting compile I see message with three paragraphs. Tell me please which one to choose?

post-factum commented on 2011-10-24 16:53 (UTC)

pf-kernel website is available via IPv6.

nous commented on 2011-10-23 11:44 (UTC)

Thanks for noticing. Moved to aufs3 from git.

Axon commented on 2011-10-22 21:24 (UTC)

Chakra repo with aufs patches is dead for now. I think, links to will be more reliable.

nous commented on 2011-10-19 06:12 (UTC)

Yes. LZO compression with tuxonice broke at pf4. For people with less swap space than RAM (like myself) LZO's a must. Others should move to linux-pf anyway. To absolutely use the last kernel26-pf4, you can download the package tarball, change pf3 to pf4 in the PKGBUILD and build it with 'makepkg --skipinteg'.

shadowed87 commented on 2011-10-19 05:15 (UTC)

is it there any reason not to use 2.6.39-pf4 instead of pf3 ??

nous commented on 2011-10-08 17:53 (UTC)

I'm waiting for linux-pf to start working with lzo'ed tuxonice. Once that happens, I'll request deletion and transfer of comments/votes.

falconindy commented on 2011-10-08 17:29 (UTC)

Can this be deleted?

commented on 2011-09-24 22:03 (UTC)

change link for: thanks.

nous commented on 2011-08-31 17:50 (UTC)

3.0.3-pf incorporates the new aufs3 tree and the interactive cpufreq governor.

nous commented on 2011-08-29 09:04 (UTC)

Yeah, same here with lzo and lzf. See and

aarone commented on 2011-08-29 06:23 (UTC)

I have an i686 machine (Atom N450, specifically), and I get -22 errors when trying to resume using lzo compression. Lzf also doesn't work (as some have reported it does) -- it yields an error code of -5 with a message about "decompression yielded XXXX bytes instead of 4096" (where XXXX is a number slightly less than 4096). This is with the latest version (3.0.2) of linux-pf. The last kernel version where suspend/resume consistently works for me is 2.6.37. 2.6.38 and .39 die silently on resume (some fiddling with transparent hugepages once made the problem seem to go away, I can't remember the details). And the 3.0 series has the -22 error.

nous commented on 2011-08-26 16:22 (UTC)

I just read a couple of threads over at the Gentoo forums and it would seem that the -22 decompression error only concerns x86_64 kernels. Can anyone on i686 confirm that? I only have access to 64bit boxes and they all fail. Also, someone reported that non-BFS kernels don't get that error...

nous commented on 2011-08-24 09:00 (UTC)

@skydrome Fixed, thanks. It seems that dropbox gets confused when more than a few computers are linked.

skydrome commented on 2011-08-23 20:08 (UTC)

in your repo, the packages are all current, but the db still shows old versions. Specifically: the -k7, -k8, and -p4 builds

nous commented on 2011-08-22 19:13 (UTC)

Please, see the post below about the default linux-pf I/O scheduler (BFQ) and post some feedback. I'm not satisfied with its performance, but I'd want to hear from others.

nous commented on 2011-08-22 17:44 (UTC)

Please, do not flag as out-of-date before checking the project page. 3.0.3 is incorporated into linux-pf-3.0.2

nous commented on 2011-08-21 09:39 (UTC)

@jgottula Either dropbox has just changed something or I did something wrong. In any case, please fall back to the original URL which I just tested and verified to work. [pfkernel] Server =$arch In case you're trying to access the repo through a browser, dropbox it doesn't allow directory listing. One can only download specific files with a full url (e.g. In the past few days I also run a cronjob on my main server that generates an index.html for all public directories, thus allowing people to browse the repo by appending index.html to the URL:

jgottula commented on 2011-08-21 01:38 (UTC)

Sorry to bother, but the Dropbox URL has been giving a 404 for the past day or two (the one works). Also, and I don't know if this is related to the Dropbox being inaccessible, when I attempt to pacman -S linux-pf using the URL, the database downloads successfully but I get that the package is corrupted (it downloads within a second, so it's probably pulling down a 404 page or something).

nous commented on 2011-08-19 06:09 (UTC)

@Phate666 See where xclaude reported working compressed hibernation with lzf.

commented on 2011-08-19 05:36 (UTC)

ohhh yes .. sorry ... downloading...

post-factum commented on 2011-08-19 05:10 (UTC)

@willianholtz: see my previous comment. 3.0.2-pf contains 3.0.3.

commented on 2011-08-19 04:03 (UTC)

waiting for 3.0.3....

Phate666 commented on 2011-08-18 22:13 (UTC)

tuxonice still broken

nous commented on 2011-08-18 10:54 (UTC)

Updated. LZF is enabled as module in this version, as some people have reported success at resuming with it.

post-factum commented on 2011-08-17 21:14 (UTC)

3.0.2-pf is out. Note, that it contains Linux 3.0.3!!!

nous commented on 2011-08-15 12:11 (UTC)

The repo is now populated with the precompiled generic and optimized linux-pf packages. Also with a new, easier to remember hostname alias. [pfkernel] Server =$arch or Server =$arch People who use hibernation should either disable tuxonice compression or switch to swsusp.

jakob commented on 2011-08-13 21:37 (UTC)

kalpik: I have the same error: -22, although I’ve built-in lzo now instead of module

post-factum commented on 2011-08-13 19:50 (UTC)

@nous: I've given up using TuxOnIce, because suddenly built-in hibernation works well for me.

kalpik commented on 2011-08-13 16:46 (UTC)

So, tuxonice still not functional? Error -22?

nous commented on 2011-08-13 16:45 (UTC)

Could you be more specific? What's the error? Anyway, I'm not going to break the PKGBUILD yet for pacman3 in favor of pacman4.

Huulivoide commented on 2011-08-13 15:51 (UTC)

Doesent currently work with testing version of pacman4, it doesent aplly any of the patches. its the noextraxt if clause that breaks it ^^

nous commented on 2011-08-13 14:20 (UTC)

I deleted my previous uneducated post about lzf. It seems that lzo is the only available/working (de)compressor for tuxonice. @kalpik: My old Pentium 3 at home is working overtime to build the i686 packages (6 hours for each one, 4 so far; generic, atom, k8 and core2). I'm building the generic x86_64 one on my laptop. You'll have to wait 'til Aug 16 for the rest as I don't want to stress my laptop in this heat.

kalpik commented on 2011-08-13 13:32 (UTC)

When are you planning to update your repo? :)

nous commented on 2011-08-13 13:02 (UTC)

It's built-in in my laptop config. Does yours resume OK?

post-factum commented on 2011-08-13 12:55 (UTC)

Probably, the trouble is in lzo module? Try to compile it as built-in, not a module.

nous commented on 2011-08-13 12:01 (UTC)

Yeah, I was just informing the users. For the time being, I've changed the compressor in /etc/hibernate/tuxonice.conf from 'lzo' to 'none'.

post-factum commented on 2011-08-12 19:26 (UTC)

Concerning TuxOnIce it's better to interact with Nigel. I've just merged it, nothing more…

nous commented on 2011-08-12 14:29 (UTC)

Fixed. BTW, tuxonice resume still croaks with error -22...

lucak3 commented on 2011-08-12 09:39 (UTC)

In the package renaming options, you left the old kernel26-pf name: # Give option to rename package according to CPU echo echo "==============================================================" msg "Hit <ENTER>: to create a package named kernel26-pf"

nous commented on 2011-08-11 22:22 (UTC)

It boots fine here on my Vostro with SLUB.

nous commented on 2011-08-11 21:40 (UTC)

Hey people! The new and shiny linux-pf is waiting. Check If some wish to stick with kernel26-pf for a little longer, it's recommended to use 2.6.39-pf3 in order to have a working tux-on-ice. This package will eventually be deleted. Thank you all.

post-factum commented on 2011-08-11 21:25 (UTC)

I've already caught 1 panic with SLOB. Hope, SLUB won't panic.

nous commented on 2011-08-11 20:05 (UTC)

Please test and report either here or at

lucak3 commented on 2011-08-11 14:24 (UTC) -> Let's hope pf gets out soon :)

post-factum commented on 2011-08-04 21:23 (UTC)

We've moved to new server. I hope, you haven't noticed that :). In case of some troubles mail me, please.

post-factum commented on 2011-08-04 21:23 (UTC)

We've moved to new server. I hope, you haven't noticed that :). In case of some troubles mail me, please.

nous commented on 2011-07-30 20:49 (UTC)

This might be my second-to-last post here, as kernel26 is being dropped in favor of linux 3.0. The versioning pattern of the respective linux-pf has been finalized to linux-pf 3.x.y, as requested by Oleksandr, where y is the actual pf version. This also makes my life easier, as it allows for updates not related to the pf-patchset to be reflected on the pkgrel number and give timely notifications to users. Awaiting for Con Kolivas to publish BFS for 3.0, linux-pf stays at 3.0.0 and builds a stock ARCH kernel. In the meantime, the "old" kernel26-pf has been updated not to conflict with linux-headers, as those who have the pfkernel repo might have noticed. The new linux-pf resides at and my last post here will announce the transition to it.

nous commented on 2011-07-30 20:44 (UTC)

OK, the versioning pattern has been finalized to linux-pf 3.x.y, as requested by Oleksandr, where y is the actual pf version. This also makes my life easier, as it allows for updates not related to the pf-patchset to be reflected on the pkgrel number and give timely notifications to users. Awaiting for Con Kolivas to publish BFS for 3.0, linux-pf stays at 3.0.0 and builds a stock ARCH kernel. In the meantime, the "old" kernel26-pf has been updated not to conflict with linux-headers, as those who have the pfkernel repo might have noticed.

commented on 2011-07-28 14:58 (UTC)

I also use a custom config, but I have removed mkinitcpio from the PKGBUILD and the install script. I just thought it would be nice to do it "properly" without editing the PKGBUILD. I haven't thought of the possibility of just ignoring the warnings. Thank you for the hint.

nous commented on 2011-07-28 10:08 (UTC)

@euri I use a custom config for my laptop without initramfs. Just build as usual, remove the 'initrd=' line from grub and ignore the mkinitcpio warnings. Just make sure you have compiled-in your hard disk controller and root filesystem driver.

commented on 2011-07-28 07:41 (UTC)

Is it possible to add an option for a kernel without initramfs?

post-factum commented on 2011-07-27 21:44 (UTC)

Unfortunately, 3.0-pf will be released not so soon as expected. -ck as well as BFQ isn't ready and won't be for a week or two. Also, consider changing version numbers. I'll use such a scheme: 3.x.y-pf where x equals to current mainline kernel version (e.g., 0) and y equals to pf-kernel release (e.g., 1). So, the first version will be 3.0.1-pf.

nous commented on 2011-07-27 10:06 (UTC)

I modified the PKGBUILD to not provide kernel26-headers so as to avoid conflict with the mainstream linux kernel package. Awaiting the release of the pf-patchset for linux-pf-3.0, I'm rebuilding all the 64-bit and the generic i686 binaries of the pfkernel repo.

jgottula commented on 2011-07-26 21:37 (UTC)

That sounds reasonable to me. I'm also looking at the linux-mainline package at the moment because it's also installed on my system, and it definitely provides headers in /usr/src/, but it just omits the whole kernel26-headers bit, and it never seemed to have a problem installing with linux-headers present.

nous commented on 2011-07-26 21:18 (UTC)

The linux-pf package installs its headers in /usr/src/linux-pf and they are available to any (nvidia comes to mind) driver that might ask for them. No conflict with linux-arch.

nous commented on 2011-07-26 21:15 (UTC)

The new linux-headers provides, replaces AND conflicts with kernel26-headers. Thus, it's impossible to force pacman to install any other kernel that also provides kernel26-headers. It makes no sense to make linux-pf provide 'linux-pf-headers' (which package would ask for it anyway?). I'm thinking of removing that 'provides' altogether, certainly before the pf patchset for 3.0 becomes available. Any objections?

jgottula commented on 2011-07-26 10:07 (UTC)

I don't think it is strictly because of providing linux-headers, because kernel26-pf (the old version) provided kernel26-headers and that was never a conflict; rather, I think it's the conflicts=('kernel26-headers') bit that is meant to rule out mixing 2.6.x headers with 3.x headers, but which mistakenly overlooks the fact that the new linux-headers package provides kernel26-headers presumably as a backwards compatibility thing... someone want to back me up on this?

sva_h4cky0 commented on 2011-07-26 09:50 (UTC)

@ jgottula bcoz linux-pf provide linux-header

jgottula commented on 2011-07-26 09:12 (UTC)

I'm also getting the following conflict when I try to install linux-pf-core2 alongside Arch's regular linux 3.0-1 and linux-headers 3.0-1 packages: linux-pf-core2 and linux-headers are in conflict (kernel26-headers). Remove linux-headers? [y/N] I seem to recall that kernel26-pf-core2 didn't mind kernel26-headers being installed concurrently. Perhaps this is cropping up because linux-headers provides kernel26-headers, with which this package has an explicit conflict?

nous commented on 2011-07-26 08:33 (UTC)

Right! I had already downloaded the kernel tarball and makepkg skipped that step...

jgottula commented on 2011-07-26 06:57 (UTC)

The PKGBUILD appears to be trying to grab linux-3.0.tar.bz2 from, whereas it should really be looking in /v3.0/. The build was failing for me until I made that amendment in my local PKGBUILD file.

nous commented on 2011-07-24 13:19 (UTC)

Same archbbs project page: Freshmeat changelog:

nous commented on 2011-07-24 13:15 (UTC)

At you'll find the new linux-pf package. I'm waiting for the assorted patches to be prepared. For now it just builds a stock ARCH kernel.

nous commented on 2011-07-24 13:08 (UTC)

Well, it builds now but uses the stock ARCH config.

nous commented on 2011-07-15 18:53 (UTC)

Again, the pf patchset contains the latest kernel patchlevel with pf-patchset ≥ patchlevel. When in doubt check the related kernel26-pf page at or the changelog at freshmeat:

jakob commented on 2011-07-15 17:31 (UTC)

though I wasn’t quite right, as the answer is located 8 lines below my last citation: it says: “Included patches: [m] mainline update;” So this is, where .3 is actually coming in…

commented on 2011-07-15 11:52 (UTC)

jakob: Thanks for your answer.

jakob commented on 2011-07-15 11:04 (UTC)

marceliq: Have a look at “Latest patch 2.6.39-pf4 (11.07.2011), applies to bare 2.6.39 kernel with no stable patches” So, pf4 IS the current version. But beware: tuxonice, as noted already by Phate666 (and I can confirm that) doesn’t work with pf4. pf3 works, however.

commented on 2011-07-15 11:01 (UTC)

Hi. Is it posible to update this to a newest kernel version Thanks.

nous commented on 2011-07-14 11:11 (UTC)

OK. I modified the PKGBUILD to provide one last option regarding the package name. Users that compile kernel26-pf themselves will have the option to have a package name that reflects or not their processor. That option affects ONLY the name of the package, not the actual package optimization (if any).

jakob commented on 2011-07-13 22:05 (UTC)

I removed the [pfkernel] repo very consciously since I had the impression of dropbox being rather slow and additionally found a localmodconfig kernel more attractive. True, kernel compilation takes some time, but mostly, I consider it fun and since my thinkpad is running so smooth in all regards, I enjoy this last resort of tinkering around currently. Instead of putting in another query whether to name the pkg appropriately or not, it may be better to comment out lines 202-237 of the current PKGBDUILD. We won’t have as neatly named packages anymore then, but that shouldn’t be a too big caveat. Are there other opinions on this?

nous commented on 2011-07-13 20:31 (UTC)

If you add the [pfkernel] repo in your pacman.conf, you'll be given the option to use the updated binaries whenever available, as I build optimized packages for all major processors with every update. I could add an option to PKGBUILD to control the package name for those who compile it themselves, I just don't like too many questions and options. Tell me what you think.

jakob commented on 2011-07-13 17:13 (UTC)

What I found a problem for me is the automatic renaming of the pkg (in my case to kernel26-pf-core2): thus, an update isnt recognized as there’s no such pkg.

nous commented on 2011-07-13 12:16 (UTC)

Your kernel or repo's? If the latter, tell me your cpu/architecture to give you a link for a pf3. Due to real-life delays, I haven't upgraded myself to pf4 (some maintainer, huh?)...

Phate666 commented on 2011-07-13 09:56 (UTC)

TuxOnIce stopped working with pf4. After waking up from suspend to disk, image reading crashes with an IO error

GI_Jack commented on 2011-07-10 22:08 (UTC)

yeah its fixed it wasn't -pf it was my chroot. thanks

nous commented on 2011-07-06 09:13 (UTC)

"mkinitcpio -p kernel26-pf"

nous commented on 2011-06-26 21:10 (UTC)

Done. You still need to manually copy your old .config (or zcat from /proc/config.gz) into the source tree.

commented on 2011-06-26 19:00 (UTC)

Would be good to include a 'make oldconfig' option in the build menu.

Cape commented on 2011-06-26 12:56 (UTC)

Recompiling the kernel solved the problem... it appears that i somehow configured the kernel without the "-pf" suffix.

nous commented on 2011-06-25 12:24 (UTC)

@Cape I can't reproduce the bug. Are you using makepkg or some wrapper like yaourt/clyde? Running 'make kernelrelease' inside $builddir/src/linux-2.6.39 should return '2.6.39-pf', otherwise something's broken on your side.

lucak3 commented on 2011-06-25 07:57 (UTC)

It would be better to report nvidia-pf problems on its AUR page :) BTW, if you are referring to this: ------------------------------------------------------------------------------------------ NVIDIA: calling KBUILD... test -e include/generated/autoconf.h -a -e include/config/auto.conf || ( \ echo; \ echo " ERROR: Kernel configuration is invalid."; \ echo " include/generated/autoconf.h or include/config/auto.conf are missing.";\ echo " Run 'make oldconfig && make prepare' on kernel src to fix it."; \ echo; \ /bin/false) ------------------------------------------------------------------------------------------ then i can assure you there is no problem: it's a known KBUILD harmless bug, it just prints what it would do, easily understandable with a bit of sh knowledge. But of course you can check if it really picked up the correct headers: just check some lines under that and you should see: cc -Wp,-MD,/home/luca/nvidia-pf/src/NVIDIA-Linux-x86-275.09.07/kernel/.nv.o.d -nostdinc -isystem /usr/lib/gcc/i686-pc-linux-gnu/4.6.0/include -I/usr/src/linux-2.6.39-pf/arch/x86/include As you can note, if the last part with -I has -pf in the path, you're good.

Cape commented on 2011-06-24 12:00 (UTC)

@Nous: I'm building my own on i686. I don't have kernel-headers installed but: cape ~ $ pacman -Qo /usr/src/linux-2.6.39*/* 2>/dev/null /usr/src/linux-2.6.39-ARCH/vmlinux is owned by kernel26 /usr/src/linux-2.6.39/Kconfig is owned by kernel26-pf-core2 2.6.39-pf2 /usr/src/linux-2.6.39/linux-2.6.39 is owned by kernel26-pf-core2 2.6.39-pf2 /usr/src/linux-2.6.39/Makefile is owned by kernel26-pf-core2 2.6.39-pf2 /usr/src/linux-2.6.39/Module.symvers is owned by kernel26-pf-core2 2.6.39-pf2 /usr/src/linux-2.6.39/vmlinux is owned by kernel26-pf-core2 2.6.39-pf2 And modules are also stored in '/lib/modules/2.6.39' (and the 'build' symlink correctly points to '/usr/src/linux-2.6.39/') Plus, when i build nvidia-pf, the installer keeps telling me that the sources for the current kernel are not correctly configured... PS: i've used the Qt frontend to configure the kernel + localmodconfig and modprobed_db.

nous commented on 2011-06-23 14:43 (UTC)

@Cape Are you using a repo package or your own? Which version? i686 or x86_64 arch? In all my boxes I get (depending on the CPU) the following: % pacman -Qo /usr/src/linux-2.6.39*/* 2>/dev/null /usr/src/linux-2.6.39-ARCH/Kconfig is owned by kernel26-headers /usr/src/linux-2.6.39-ARCH/Makefile is owned by kernel26-headers /usr/src/linux-2.6.39-ARCH/Module.symvers is owned by kernel26-headers /usr/src/linux-2.6.39-ARCH/vmlinux is owned by kernel26 /usr/src/linux-2.6.39-pf/Kconfig is owned by kernel26-pf-k8 2.6.39-pf2 /usr/src/linux-2.6.39-pf/Makefile is owned by kernel26-pf-k8 2.6.39-pf2 /usr/src/linux-2.6.39-pf/Module.symvers is owned by kernel26-pf-k8 2.6.39-pf2 /usr/src/linux-2.6.39-pf/linux-2.6.39-pf is owned by kernel26-pf-k8 2.6.39-pf2 /usr/src/linux-2.6.39-pf/vmlinux is owned by kernel26-pf-k8 2.6.39-pf2 The 'build' symlink in /lib/modules/2.6.39-pf/ is correct too. Are you sure it's not nvidia-pf's fault? To have a generic package name remove lines 196-241.

Cape commented on 2011-06-22 20:29 (UTC)

I've noticed that sources from this build are stored in "/usr/src/linux-2.6.39/" causing nvidia-pf to complain about not finding the kernel (unless i modify the PKGBUILD). Shouldn't it be "/usr/src/linux-2.6.39-pf/"? Also, i don't want my package to be called "kernel26-pf-core2" so if i comment out everything from line 196 to line 235, will i be fine? Thanks in advance

nous commented on 2011-06-04 21:47 (UTC)

Thanks, jakob. @antiwinhacker Unfortunately, dropbox doesn't allow normal browsing, you have to put it somewhere in /etc/pacman.conf or /etc/pacman.d/unofficial (and include it from /etc/pacman.conf).

jakob commented on 2011-06-04 19:58 (UTC)

Just an awesome package! Almost easier and certainly faster than downloading the package each time from dropbox. Thanks alot!

commented on 2011-06-04 18:04 (UTC)

I just installed your package, thanks for the great work! I have a AMD Athlon X2 250 CPU. Your dropbox repository is not reachable, it is moving?

jakob commented on 2011-06-03 01:46 (UTC)

Ah yeah. Just did that: However, I deleted my aufs* files in ~/tmp/pkgs/sources, downloaded fresh copies et voila: it works: and patch application works fine :) I seemed to have broken soures or somethig like that Thanks for your hint!

nous commented on 2011-06-02 19:47 (UTC)

@jakob: please, try downloading the tarball with 'wget -Y off' and report back. The filesizes should be (see also orion:[nous]:/tmp/kernel26-pf% ls -l total 660 -rw-r--r-- 1 nous users 17622 Jun 1 19:28 PKGBUILD -rw-r--r-- 1 nous users 2727 May 19 09:46 aufs2-base.patch -rw-r--r-- 1 nous users 976 May 19 09:46 aufs2-kbuild.patch -rw-r--r-- 1 nous users 7781 May 19 09:46 aufs2-standalone.patch

jakob commented on 2011-06-02 12:59 (UTC)

I can confirm slane’s issue. After makepkg -g >> PKGBUILD, I have the following sums which don’t fail: Unfortunately, the patches don’t apply and building breaks with applying aufs2-patches.

nous commented on 2011-06-02 08:33 (UTC)

I can't confirm. It works OK, I even tried it manually with wget and sha256sum and the sums check out. Are you using a proxy?

commented on 2011-06-02 08:16 (UTC)

Hello, ==> Validating source files with sha256sums... aufs2-base.patch ... FAILED aufs2-kbuild.patch ... FAILED aufs2-standalone.patch ... FAILED

post-factum commented on 2011-05-31 19:00 (UTC)

That's it.

post-factum commented on 2011-05-23 21:31 (UTC)

Well, guys, I guess, Nigel is busy at the moment and still cannot update TuxOnIce against 2.6.39 tree. But other things are already merged, so you can give them test by cloning pf-kernel from my github account, compiling it and reporting. I'd really appreciate it. One more thing =). I'll immediately release 2.6.39-pf1 as soon as all components arrive.

nous commented on 2011-05-23 21:20 (UTC)

There's no download link on the project's page. Usually, Oleksandr flags as out-of-date when he's ready.

smoge commented on 2011-05-23 17:49 (UTC)

.39 is ready?

nous commented on 2011-04-23 18:53 (UTC)

But anyway, one can safely disable that patch, it's only for those uneasy spirits that delve into the dark arts of WEP cracking...

nous commented on 2011-04-23 18:52 (UTC)

Funny, it works from here... % wget -Y off --2011-04-23 21:50:19-- Resolving (, 2001:41d0:1:1b00:213:186:33:2 Connecting to (||:80... connected. HTTP request sent, awaiting response... 200 OK Length: 1021 [text/plain] Saving to: “channel-negative-one-maxim.patch” 100%[=======================================================================>] 1,021 --.-K/s in 0s 2011-04-23 21:50:19 (117 MB/s) - “channel-negative-one-maxim.patch” saved [1021/1021]

akurei commented on 2011-04-23 15:53 (UTC)

-> Downloading channel-negative-one-maxim.patch... --2011-04-23 17:45:23-- Resolving 2001:41d0:1:1b00:213:186:33:2, Connecting to|2001:41d0:1:1b00:213:186:33:2|:80... connected. HTTP request sent, awaiting response... Read error (Connection reset by peer) in headers. Retrying. My patch: URL: RAW:

post-factum commented on 2011-04-22 19:25 (UTC)

-pf6 with 38.4 included is out.

nous commented on 2011-04-22 08:48 (UTC)

Thanks, fixed.

commented on 2011-04-22 07:56 (UTC)

there is a small typo in the PKGBUILD, nconfig is selectable via "c" key not "n".

post-factum commented on 2011-04-21 18:49 (UTC)

-pf5 brings BFSv401.

post-factum commented on 2011-04-15 17:50 (UTC)

-pf4 is out. It contains 38.3, which reverts buggy commit that caused troubles with hibernation, so Anvin's patch is also removed.

nous commented on 2011-04-13 16:01 (UTC)

A trouble-free kernel, for a change...

nous commented on 2011-04-11 19:26 (UTC)

Great. Updated and started building.

post-factum commented on 2011-04-11 15:53 (UTC)

-pf3 is out. -ck3 and hibernation regression fix have been merged.

commented on 2011-04-05 13:24 (UTC)

Just a feedback: it works like a charm now! :)

nous commented on 2011-04-05 11:32 (UTC)

post-factum: Correct, the patch is just a temporary fix. freakazoid88: It's my laptop tailored config, I'm sorry it slipped through. Fixed now. bicer: The aufs2 patches are fetched from the chakra repo. I chose this approach to let makepkg warn me for updates 'cause I rarely check for them myself. The patches were updated a little after the last PKGBUILD was uploaded. Also fixed, one can always override the sums with 'makepkg --skipinteg'.

commented on 2011-04-03 22:28 (UTC)

Nous could you please confirm SUMs of aufs2-base.patch, aufs2-kbuild.patch, and aufs2-standalone.patch are correct. They're failing verification. Thank You.

commented on 2011-04-03 15:17 (UTC)

The file config.x86_64 looks quite strange, it's not set at the default values o.O Can anyone confirm that?

post-factum commented on 2011-04-03 10:06 (UTC)

I guess, cr4-restore.patch is not final version of patch, so I'll recommend using it, but still waiting for Thanks.

nous commented on 2011-04-02 22:42 (UTC)

New pf2.5 PKGBUILD with cr4-restore.patch fixes resume. The repo is not updated, sorry. Those who need hibernate/resume functionality, please download and compile.

nous commented on 2011-04-02 20:43 (UTC)

post-factum: Since this is is critical, and because I'll be far from computers for the next 2 days, how about upgrading 2.5 to pf3 now so I put my dropbox server to work, populating the repo with the prebuilts? BFS 372 performs significantly better than 363.

nous commented on 2011-04-02 20:36 (UTC)

Included patch from Tested to work, resume continues now.

post-factum commented on 2011-04-02 20:32 (UTC)

OK, thanks for info!

commented on 2011-04-02 19:37 (UTC)

Resume issue: I guess we need to wait for 38.3, TOI or BFS seems not to be buggy as for 38.1 (pf1) it works, I currently run 372-test2 patch on top of pf1...

post-factum commented on 2011-04-02 13:24 (UTC)

No idea :/. Try to disable BFS, then BFQ. If not — TuxOnIce is buggy.

nous commented on 2011-04-02 12:52 (UTC)

Grrrr, still hangs on resume.

post-factum commented on 2011-04-02 11:13 (UTC)

Ok, I've released -pf2.5. Please, test it and report here or to me using email.

nous commented on 2011-04-02 09:59 (UTC)

Why don't you upload it as patch-2.6.38-pf2.5.bz2 for the rest to test, and make it pf3 in due time?

post-factum commented on 2011-04-02 09:37 (UTC)

I'm testing new BFS version right now. [pf@eternity]:[~][0]% dmesg | grep BFS [ 1.364306] BFS CPU scheduler v0.372 by Con Kolivas. [pf@eternity]:[~][0]% uname -a Linux eternity 2.6.38-pf2.5 #1 SMP PREEMPT Sat Apr 2 11:16:23 EEST 2011 i686 Intel(R) Pentium(R) Dual CPU T2330 @ 1.60GHz GenuineIntel GNU/Linux

post-factum commented on 2011-04-02 07:48 (UTC)

Well, I suspect some deadlock to be present in one of pf2 patches. I guess, this is BFS problem, and I'm waiting for next BFS release.

nous commented on 2011-03-31 16:05 (UTC)

Easiest way to downgrade: change _pfrel=pf2 to pf1 in PKGBUILD and build with 'makepkg --skipinteg'

nous commented on 2011-03-31 09:15 (UTC)

As Kirugs has reported, -pf2 is broken for me too. It fails to resume on 2 desktops and 1 laptop...

nous commented on 2011-03-30 14:32 (UTC)

Kirugs: obviously, as -pf1 works, your setup is ok and you wait for the next tuxonice update. Since hibernation is a necessity for my laptop, I had to hold back updates more than a couple of times in the past. shadowed87: sha256sums updated, but I'm not rebuilding the repo packages just for aufs - I doubt anyone uses it anyway :)

shadowed87 commented on 2011-03-30 08:50 (UTC)

aufs has been updated on chakra, sha256 are different ;)

commented on 2011-03-30 06:14 (UTC)

pf2 is broken for me. Hibernate doesn't work, going sleep works, but resuming ends with blinking caps lock, nothing in logs. I tried pfkernel repo and situation is the same, except that it gave me no blinking caps. pf1 works brilliant, so I'm reverting to that.

nous commented on 2011-03-29 09:00 (UTC)

shadowed87 commented on 2011-03-29 08:56 (UTC)

anyone knows where to find a pf changelog? i really can't find it..

nous commented on 2011-03-29 04:35 (UTC)

hellnest: Silly me, I saw that error in my laptop and I just enabled dvb in menuconfig... Meh, I'm either getting lazier or dumber. Fixed and cheers.

hellnest commented on 2011-03-28 21:55 (UTC)

@nous - cp include/config/dvb/*.h ${pkgdir}/usr/src/linux-${_kernver}/include/config/dvb/ + [[ -e include/config/dvb/ ]] && cp include/config/dvb/*.h ${pkgdir}/usr/src/linux-${_kernver}/include/config/dvb/ Like your comment on -ck page. You must modify PKGBUILD to make it success. My build now success thanks once again :)

hellnest commented on 2011-03-28 19:44 (UTC)

Ok thanks for your help, :) I didn't read a whole comments sorry ^^

nous commented on 2011-03-28 19:42 (UTC)

hellnest: Downgrade to make 3.81-5 from [core], I had similar errors (fackamato also reported it, see comments) and I currently have it pinned with IgnorePkg.

hellnest commented on 2011-03-28 19:17 (UTC)

I need some enlightment here... >.<" 10times try compile it without success make[1]: *** No rule to make target `/home/lee/AUR/kernel26-pf/pkg/lib/firmware/./', needed by `/home/lee/AUR/kernel26-pf/pkg/lib/firmware/atmsar11.fw'. Stop. make: *** [_modinst_post] Error 2

nous commented on 2011-03-27 12:13 (UTC)

litemotiv I was hit by the error you reported; googling it I found that it's caused by binutils-2.21

nous commented on 2011-03-27 00:33 (UTC)

shadowed87 yup, but it's gonna take a couple of days... My 32bit box is slow.

shadowed87 commented on 2011-03-26 23:53 (UTC)

wonderful...thank you as usual... one it possible to add core2 version to i686 repository?

nous commented on 2011-03-26 22:55 (UTC)

Thanks everyone for the feedback. Missing /lib/modules/2.6.38-pf/build symlink fixed. Forgotten version 37 chakra patches updated to 38. CheariX, as Alger noted, if you run optimized kernel26-pf you won't see the updates until my prebuilt optimized packages hit the pfkernel repo.

post-factum commented on 2011-03-26 20:36 (UTC)

I'm not going to include BFS 363-test2 into pf-kernel until it become stable.

shadowed87 commented on 2011-03-26 16:35 (UTC)

@Alger I had the same problem...executing sudo ln -s /usr/src/linux-2.6.38-pf/ /lib/modules/2.6.38-pf/build all was fine with nvidia drivers

commented on 2011-03-26 15:51 (UTC)

@CheariX Yaourt can't detect because you have other name package installed like kernel26-pf-core2 so it's differ from this as far as i think this is the reason

CheariX commented on 2011-03-26 15:17 (UTC)

Why can't yaourt detect new version? This problem was from 2.6.37-pf2 up to 2.6.37-pf6 and now with 2.6.38, yaourt still thinks kernel26-pf is up to date...

shadowed87 commented on 2011-03-26 14:46 (UTC)

why not these patches? instead of

commented on 2011-03-26 14:28 (UTC)

aren't we need a simlink /lib/modules/build/2.6.38-pf/build to /usr/src/linux-2.6.38-pf or something like this , because i can't build ati properity driver now

nous commented on 2011-03-26 13:47 (UTC)

@graysky - Thanks for the heads-up, but as far as BFS is concerned, I'm just following the pfkernel patchset, whose author anyway is a close follower of CK's blog and I suspect he'll implement this promising patch very soon.

graysky commented on 2011-03-26 13:37 (UTC)

Nous - you might wanna add this patch to ck1:

nous commented on 2011-03-26 13:17 (UTC)

Alright, alright. Four kernel configuration options for all tastes.

commented on 2011-03-26 08:21 (UTC)

I suggest write this to PKGBUILD: msg "Run make menuconfig(console), gconfig(GTK based) or xconfig(Qt based) before build? (m/g/x/N)" read answer case "$answer" in m | M) make menuconfig cp -v .config ${startdir}/config.local ;; g | M) make gconfig cp -v .config ${startdir}/config.local ;; x | X) make xcongig cp -v .config ${startdir}/config.local ;; default) ;; esac

nous commented on 2011-03-26 02:18 (UTC)

It's very easy to put that in the PKGBUILD, but it's just another configuration option; I've also been asked to use xconfig or gconfig instead of menuconfig. It would be rather annoying for most people to have the PKGBUILD asking a ton of questions before actually building the package, while one could just issue 'sed -i s/menuconfig/nconfig/ PKGBUILD' before makepkg.

misc commented on 2011-03-26 01:27 (UTC)

It would be great if an option for nconfig were to be included in this PKGBUILD.

nous commented on 2011-03-19 11:33 (UTC)

If the stock -ARCH kernel has the same issue, then something might wrong with your build tools. I really can't imagine where you should start, but you could grep the main kernel Makefile for 'export' directives (I see make, awk, perl, gcc among others; definitely more in submakefiles) and reinstall them. It's really weird, have you tested on another box?

Cape commented on 2011-03-18 22:35 (UTC)

Nope... same output, but still i'm unable to enter that submenu. The same happens in /usr/src/linux-2.6.37-ARCH cape ~/Packages/kernel26-pf/src/linux-2.6.37 $ make menuconfig HOSTCC scripts/basic/fixdep HOSTCC scripts/basic/docproc HOSTCC scripts/kconfig/conf.o HOSTCC scripts/kconfig/kxgettext.o HOSTCC scripts/kconfig/lxdialog/checklist.o HOSTCC scripts/kconfig/lxdialog/inputbox.o HOSTCC scripts/kconfig/lxdialog/menubox.o HOSTCC scripts/kconfig/lxdialog/textbox.o HOSTCC scripts/kconfig/lxdialog/util.o HOSTCC scripts/kconfig/lxdialog/yesno.o HOSTCC scripts/kconfig/mconf.o SHIPPED scripts/kconfig/ SHIPPED scripts/kconfig/lex.zconf.c SHIPPED scripts/kconfig/zconf.hash.c HOSTCC scripts/kconfig/ HOSTLD scripts/kconfig/mconf scripts/kconfig/mconf Kconfig # # configuration written to .config # *** End of the configuration. *** Execute 'make' to start the build or try 'make help'.

nous commented on 2011-03-18 21:37 (UTC)

I just tested the PKGBUILD again on an i686 box without problems. Please do the following and see if you get any errors. 1. Download the kernel26-pf tarball, untar and run makepkg 2. At the '==> Run make menuconfig before build? (y/N)' prompt press CTRL-C 3. cd into src/linux-2.6.37 and run 'make menuconfig', check the processor option and exit menuconfig My output is the following: ================================ proxy:[nous]:/temp/pkgbuild/kernel26-pf/src/linux-2.6.37% make menuconfig HOSTCC scripts/basic/fixdep HOSTCC scripts/basic/docproc HOSTCC scripts/kconfig/conf.o HOSTCC scripts/kconfig/kxgettext.o HOSTCC scripts/kconfig/lxdialog/checklist.o HOSTCC scripts/kconfig/lxdialog/inputbox.o HOSTCC scripts/kconfig/lxdialog/menubox.o HOSTCC scripts/kconfig/lxdialog/textbox.o HOSTCC scripts/kconfig/lxdialog/util.o HOSTCC scripts/kconfig/lxdialog/yesno.o HOSTCC scripts/kconfig/mconf.o SHIPPED scripts/kconfig/ SHIPPED scripts/kconfig/lex.zconf.c SHIPPED scripts/kconfig/zconf.hash.c HOSTCC scripts/kconfig/ HOSTLD scripts/kconfig/mconf scripts/kconfig/mconf Kconfig # # configuration written to .config # *** End of the configuration. *** Execute 'make' to start the build or try 'make help'. ===================================== What happens if you run 'sudo make menuconfig' in /usr/src/linux-2.6.38-ARCH?

Cape commented on 2011-03-18 13:07 (UTC)

I'm on i686 and i'm using makepkg. Of course, i answer "y" when asked to run menuconfig. The problem is that "Processor type and features ---> Processor family" is "locked", i can't enter the submenu... It's the same if choose localmodconfig, vanilla or current kernel config. I also noticed that other options are locked.

nous commented on 2011-03-16 22:06 (UTC)

Cape: It's not normal. I assume you follow "Processor type and features ---> Processor family", right? Can you be more specific? (i686 or x86_64? makepkg or yaourt/clyde? etc) I also assume of course that you answer 'y' to "==> Run make menuconfig before build? (y/N)"

Cape commented on 2011-03-16 20:19 (UTC)

Maybe i'm doing something wrong, but i'm not able to choose my cpu family in menuconfig. It's the same if i choose locamodconfig, running kernel or stock... I just can't edit that entry. Is it normal?

commented on 2011-03-15 17:07 (UTC)

Thank you Christos. I will try the prebuild version from your repo first. :-)

nous commented on 2011-03-15 16:59 (UTC)

litemotiv: that option is for users that already have a tailored kernel for their systems and don't want to compile the entire kernel tree. Using that option entails manual configuring of the uncovered options the pf-patchset provides, i.e. what you were asked and it's normal. Had you answered 'yes' to 'make menuconfig' question before, you'd be directed to the more user-friendly menu configuration. If you used that option on, say, the stock -ARCH kernel you'd have no gain whatsoever, since that's a generic kernel. You'd have to deselect the unneeded options/modules one by one, but that's usually a one-time chore. Google for 'kernel configure' for more. As for the compilation error, I haven't bumped into it, ever. I compile 6 i686 and 5 x86_64 pf-kernels for my unofficial repo and I've never seen that error. What's worse, that's an assembler error and I hate x86 assembly. Have you tried a clean compile? A different binutils version?

commented on 2011-03-14 17:24 (UTC)

Thanks for this, nice installer too. :-) Two questions: I chose the current-running-kernel config option, this then gave a lot of the PF-specific options a default value of No (example: BFQ [N/y/m/]). Is this fixable, or is it just the way it works? Secondly, i'm getting a compilation error: AS arch/x86/kernel/entry_64.o arch/x86/kernel/entry_64.S: Assembler messages: arch/x86/kernel/entry_64.S:1531: Error: .size expression does not evaluate to a constant Is this just a temporary source problem that i have to wait a bit for to get fixed? Thanks again, -lite

nous commented on 2011-03-09 16:52 (UTC)

pf6 is bump

nous commented on 2011-03-01 23:21 (UTC)

Changelog of pf4 to pf5: BFQ updated to version 2.

nous commented on 2011-02-10 17:02 (UTC)

Indeed, I had uploaded a previous source tarball without the relevant patch line. Nice catch.

floft commented on 2011-02-10 01:33 (UTC)

I installed this kernel for the b44 fix, but I still got a kernel panic when trying to connect via ethernet. I looked at the swiotlb.c file and the patch wasn't being applied, so I modified the PKGBUILD to apply the included patch and now it works. I'm not sure if this is as expected or not...

shadowed87 commented on 2011-02-08 17:48 (UTC)

tnx man, you're a great mantainer

nous commented on 2011-02-02 20:52 (UTC)

A patch to fix the b44 kernel panic is included. Darn, .37 is not the best kernel I've run.

nous commented on 2011-01-26 21:12 (UTC)

@shadowed87 I just put the libata-alignment.patch in. I'm rebuilding the 64bit packages right now; those unaffected by the bug, do not need to upgrade.

shadowed87 commented on 2011-01-26 18:59 (UTC)

the problem for me is that after udev 165 upgrade some days ago, sometimes there is a kernel panic on boot, this happens with all kernels but not all I downgrade temporarily udev... here is the bug report: and now they have patched all archlinux kernel for this it's a shame not to have the fix in this package...

nous commented on 2011-01-26 17:43 (UTC)

The ARCH patchset is mostly the archlinux bootlogos and a few other minor patches most of which conflict with BFS/BFQ/TuxOnIce. It's just not worth isolating the clean ones (and not wise either, considering they probably need the dirty ones).

shadowed87 commented on 2011-01-26 11:53 (UTC)

why don't you add arch patches?

nous commented on 2011-01-20 17:17 (UTC)

New prebuilt packages for all needs! x86_64 packages for: Intel Pentium4/D/Nocona Xeon - Core2 - Atom, AMD Athlon64 K8, Generic x86_64 i686 packages for : Intel Pentium3 - Pentium4 - -Pentium-M - Atom, AMD K7, Generic i686 [pfkernel] Server =$arch

nous commented on 2011-01-17 12:04 (UTC)

@elmariachi I think that should be reported at

commented on 2011-01-17 10:45 (UTC)

==> Attempting to run /usr/bin/reload_database from modprobe_db... WARNING: Module led_class not found. Aborting... wasn't this fixed already?

nous commented on 2011-01-11 22:31 (UTC)

A quick fix for the nvidia-pf without the need for reinstallation: # cd /lib/modules/2.6.37-pf # rm -f source build # ln -sf /usr/src/linux-2.6.37-pf build You *may* need to force the next update to overwrite the link.

nous commented on 2011-01-11 22:03 (UTC)

@Cape please, see my previous comment as it applies to your condition too. The oversight I mentioned was related also to not copying all the necessary header files correctly :/ It was the same reason as yours that lead me to discover and fix it. I should update the pf#, but it won't follow pfkernel's own version and I don't like decimals (if you see the PKGBUILD, I cannot just update -pf2 to -pf2-1, as the $pkgrel variable (which controls the revision) is reserved for the pf version itself and no more dashes are allowed. So, please, reinstall, either from the repo (if on x86_64, including nvidia-pf) or from the AUR, they have been fixed. The i686 packages build in a slow P3 and will be available shortly.

Cape commented on 2011-01-11 20:18 (UTC)

I'm trying to build nvidia-pf, but it complains about "determining the kernel version". The nvidia-pf PKGBUILD points the nvidia installer to "/lib/modules/2.6.37-pf/build" witch doesn't exist. The stock arch kernel instead, contains "/lib/modules/2.6.36-ARCH/build" as a link to "/usr/src/2.6.36-ARCH/". Should i create that link manually? Or did i messed up something during the kernel configuration?

nous commented on 2011-01-10 10:10 (UTC)

To all users of kernel26-pf: I had an oversight in the .37 PKGBUILD that left inside the firmware files, so if pacman complained about conflicting files in /lib/firmware during the installation, please delete the kernel26-pf package from /var/cache/pacman/packages (if you used the prebuilt repo package), uninstall and re-install both kernel26-pf and linux-firmware so you don't have any conflicting files in future updates.

nous commented on 2011-01-08 17:00 (UTC)

For those who don't tweak much their kernels or are bored of compiling, assorted kernel26-packages can be found at the repo below. [pfkernel] # kernel26-pf, kernel26-pf-p3, kernel26-pf-k8, kernel26-pf-core2, nvidia-pf, squid3, arora-git Server =$arch

nous commented on 2011-01-08 16:27 (UTC)

I've built successfully the generic x86_64 version (check the pfkernel repo: search for unofficial user repositories in archwiki) and I'm building right now the optimized 64-bit ones and the generic i686 version without errors. Wrapper scripts like yaourt are known to have problems with the AUR; please use 'aurdownload kernel26-pf' from aurscripts and just 'makepkg -i' inside the kernel26-pf directory.

commented on 2011-01-08 15:46 (UTC)

Doesn't build for me: HOSTCC scripts/basic/fixdep HOSTCC scripts/basic/docproc HOSTCC scripts/kconfig/conf.o HOSTCC scripts/kconfig/kxgettext.o SHIPPED scripts/kconfig/ SHIPPED scripts/kconfig/lex.zconf.c SHIPPED scripts/kconfig/zconf.hash.c HOSTCC scripts/kconfig/ HOSTLD scripts/kconfig/conf scripts/kconfig/conf --silentoldconfig Kconfig fs/Kconfig:194: can't open file "fs/aufs/Kconfig" make[2]: *** [silentoldconfig] Error 1 make[1]: *** [silentoldconfig] Error 2 make: *** No rule to make target `include/config/auto.conf', needed by `include/config/kernel.release'. Stop. Aborting... ==> ERROR: Makepkg was unable to build kernel26-pf. ==> Restart building kernel26-pf ? [y/N] ==> ------------------------------------ ==> ==> WARNING: Following packages have not been installed: kernel26-pf This could be the problem: ==> Applying pf-kernel patch bzip2: skipping "/tmp/yaourt-tmp-root/aur-kernel26-pf/src/patch-2.6.37-pf2.bz2": not a regular file ==> Applying aufs2 and squashfs-lzma patches patching file fs/namei.c patching file fs/splice.c patching file include/linux/namei.h patching file include/linux/splice.h patching file fs/Kconfig patching file fs/Makefile patching file include/linux/Kbuild patching file fs/file_table.c patching file fs/inode.c patching file fs/namei.c patching file fs/namespace.c patching file fs/notify/group.c patching file fs/notify/mark.c patching file fs/open.c patching file fs/splice.c patching file security/commoncap.c patching file security/device_cgroup.c patching file security/security.c bzip2: skipping "/tmp/yaourt-tmp-root/aur-kernel26-pf/src/aufs2.1-2010-12-20.patch.bz2": not a regular file

nous commented on 2011-01-08 10:24 (UTC)

LZO compression is implemented now into mainline kernel hibernation and it should be as fast as tuxonice, but I still like the latter's framebuffer interface.

post-factum commented on 2011-01-08 09:46 (UTC)

BTW, I've deactivated tuxonice for my laptop, because hibernation works better without it.

nous commented on 2011-01-08 08:28 (UTC)

Grrrrreat! I'd hate to lose tuxonice.

post-factum commented on 2011-01-07 23:36 (UTC)

It was Nigel's mistake with tuxonice, pf-kernel has been updated against new tuxonice branch. pf2 is out.

nous commented on 2011-01-07 17:13 (UTC)

To Oleksandr: I use tuxonice extensively, as it behaves especially well on my vostro 1500 and thinkpad r50e laptops. It behaved equally well on my desktops at home and at work until 2.6.36, which is when it started failing to suspend. That said, I would regret to see it go but I barely have time to maintain this package, not to mention messing with reversing patchsets. The kernel26-ck maintainer ( doesn't even bother to include tuxonice and the kernel26-ice one ( has kept BFS at v0.357. I'll keep maintaining this package, but I'll certainly keep 2.6.36-pf6 on my laptops until it's too outdated or this is resolved. To all: package updated to 2.6.37-pf1, you'll need to say "y" to "make menuconfig" until I find some time to go through the new kernel config. The aufs2 and squashfs-lzma patches too will be temporarily be removed until I find the aforementioned time (or someone else compiles a patchset for 2.6.37-pf1).

post-factum commented on 2011-01-07 15:18 (UTC)

Any ideas about tuxonice? See pf-kernel site for details.

nous commented on 2011-01-07 10:40 (UTC)

Please, please, please, see before flagging as out-of-date.

commented on 2011-01-04 15:06 (UTC)

Thanks for this. Knocks at least 2W off my power consumption. Boots faster too!

nous commented on 2011-01-01 22:30 (UTC)

Thy will is done. :)

graysky commented on 2011-01-01 15:21 (UTC)

@lucak3 - thanks for the kind words - glad you're finding that script useful. @nous - you should know that according to Steven (the author of the streamline script), calling it directly isn't right. He recommends calling it make localmodconfig instead. Also know that for 2.26.37, there is a fixed version of his script. See;a=commitdiff;h=8ef17fa2ef8be74b946e725c2afb0e2a54981da1;hp=20d190473328b90755eb2434cf2d26b73a53ef23 If you look in my PKGBUILD for kernel26-ck I pull the git version and replace the 2.6.32.x version with it, then call the make localmodconfig.

lucak3 commented on 2011-01-01 15:17 (UTC)

I found interesting and useful the use of modprobed_db script in AUR (by graysky) It would be a good idea to add a few lines to the PKGBUILD to use that before, as in kernel26-bfs. This reduces to these lines --------------------------- msg "If you have modprobe_db installed, running reload_database now" if [ -e /usr/bin/reload_database ]; then /usr/bin/reload_database fi --------------------------- as you can see here,

nous commented on 2011-01-01 09:25 (UTC)

Hrmpf... I re-introduced the aufs2 and squashfs-lzma patch into the package, but I inadvertedly applied it against the vanilla kernel tree... so it wiped completely the pf patch. Apologies, it should be fixed now.

MaJia321 commented on 2011-01-01 08:15 (UTC)

Why doesn't config.x86_64 have CONFIG_SCHED_BFS=y ? Thanks

nous commented on 2010-12-30 00:41 (UTC)

Re-introduced aufs2 and squashfs-lzma patches.

commented on 2010-12-06 22:02 (UTC)

I am a robot. This is not an official message. AUR guidelines suggest to not include binaries. Examples: kernel26-pf/logo_linux_clut224.ppm.bz2 kernel26-pf/logo_linux_mono.pbm.bz2 kernel26-pf/logo_linux_vga16.ppm.bz2 Feel free to disregard this as you would any other comment. This robot will not post here again.

nous commented on 2010-11-29 15:37 (UTC)

Links updated.

post-factum commented on 2010-11-29 14:18 (UTC)

Please, update links to pf-kernel site. I've changed its domain name to Old links still works via redirect.

LookTJ commented on 2010-11-24 00:44 (UTC)

it has mainline update.

LookTJ commented on 2010-11-23 22:38 (UTC)

nous, sorry about that, won't happen again from me.

nous commented on 2010-11-23 12:39 (UTC)

FFS, I've said it so many times, kernel26-pf follows, NOT! DO NOT FLAG AS OUT-OF-DATE.

nous commented on 2010-11-21 18:57 (UTC)

mpsnets I've never used it and my time is really sparse.... Why don't you copy an existing PKGBUILD of, say, -kernel26-ck and create a new package, as lucak3 did with nvidia-pf?

commented on 2010-11-19 12:46 (UTC)

Please You need to create the package vhba-module-pf!

graysky commented on 2010-11-18 22:23 (UTC)

Plus, see what ck has to say about it: Con Kolivas wrote: I've had every man and his dog either drop into IRC or email me asking me what my thoughts are on the grouping tasks by tty layer patch discussed here: Phoronix link and slashdot. I guess people didn't understand my 2.6.36-ck1 announcement clearly enough, so I'll quote it again here: Those following the development of the patches for interactivity at massive load, I have COMPLETELY DROPPED them as they introduce regressions at normal workloads, and I cannot under any circumstances approve changes to improve behaviour at ridiculous workloads which affect regular ones. I still see precisely zero point at optimising for absurd workloads. Proving how many un-niced jobs you can throw at your kernel compiles is not a measure of one's prowess. It is just a mindless test. Remember, I already had developed a hierarchical tree-based penalty patch for BFS and blogged about it here. I can do it in a 10 line patch for BFS, but it introduced regressions, which is why I dropped it (see earlier blog entry here: further-updates-on-hierarchical-tree). Again, I can't for the life of me see why you'd optimise for make -j64 on a quad core machine. It is one workload, unique to people who compile all the time, but done in a way you wouldn't normally do it anyway. It is not going to magically make anything else better. If for some god-forsaken reason you wanted to do that, you could already do that with nice, or even better, by running it SCHED_IDLEPRIO. nice -19 make -j 64 blahblah or schedtool -D -e make -j64 blahblah It's not really that hard folks... And if you really really really still want the feature for BFS, the patch that does the hierarchical tree based penalty is rolled into a bigger patch (so a lot more than just the 10 lines I mentioned) that can also group threads and enable/disable the features and it's still here: bfs357-penalise_fork_depth_account_threads.patch It is worth noting also that the mainline approach costs you in throughput, whereas this patch is virtually free. EDIT: I forgot to mention that for YEARS now I've been using my "toolsched" wrapper scripts that do this automatically. See toolsched for the scripts. Make always starts as SCHED_IDLEPRIO for me at home.

nous commented on 2010-11-18 21:41 (UTC)

From what I read, the patch groups tty-originated tasks, which has little to do with the desktop: Besides: 1st, the patch doesn't apply cleanly and I don't have the time to fix it and 2nd, nice(1) behaves very well with BFS.

commented on 2010-11-18 19:16 (UTC)

This thinking of putting the patch on autogroup-pf? See

nous commented on 2010-11-04 20:12 (UTC)

@fackamato: It's make's fault (and it's random). Downgrade to make from [core].

fackamato commented on 2010-11-04 19:09 (UTC)

Hm. Am I doing something wrong? It won't work for me. This is the error: IHEX2FW firmware/keyspan_pda/keyspan_pda.fw IHEX2FW firmware/keyspan_pda/xircom_pgs.fw IHEX firmware/cpia2/stv0672_vp4.bin H16TOFW firmware/vicam/firmware.fw Aborting... I've deleted the src dir but it's the same.

nous commented on 2010-10-31 22:09 (UTC)

Fixed, thanks.

commented on 2010-10-31 14:26 (UTC)

@nous - Could you take a look at "config.x86_64". Some things like BFQ are not being set correctly. Is this just me? CONFIG_IOSCHED_BFQ=y | # CONFIG_IOSCHED_BFQ is not set CONFIG_CGROUP_BFQIO=y | # CONFIG_DEFAULT_DEADLINE is not set CONFIG_DEFAULT_BFQ=y | CONFIG_DEFAULT_CFQ=y CONFIG_DEFAULT_IOSCHED="bfq" | CONFIG_DEFAULT_IOSCHED="cfq"

nous commented on 2010-10-30 15:03 (UTC)

@sht0rm -ck2 is included in -pf1, check line 1483 of kernel/sched_bfs.c, "BUG_ON(rq != this_rq());" is removed. BTW, I'm not russian/ukrainian :p

commented on 2010-10-30 11:07 (UTC)

Можете включить patch -ck2 или он уже включен? Являюсь владельцем intel 4965, и вайфай заглючил. Can you include an -ck2 patch in your kernel, or it already included? I am an owner of this wifi chip 0c:00.0 Network controller: Intel Corporation PRO/Wireless 4965 AG or AGN [Kedron] Network Connection (rev 61) in my laptop, and I have a problems with 2.6.26-pf1.

nous commented on 2010-10-29 19:22 (UTC)

LinuxIMQ hasn't released a patch for 2.6.36, so the author of pfkernel ditched it. I also ditched aufs2 and squashfs-lzma, because I couldn't find patches to apply cleanly in 2.6.36. I'm building generic and optimized binaries right now to upload at the repo.

drexya commented on 2010-10-27 22:24 (UTC)

The Con Kolivas patchset is very impressive, x264 encoding (on the same clip) with stock kernel = ~ 15fps, with this kernel = ~ 20fps !

nous commented on 2010-10-22 15:09 (UTC)

Please, do not flag as out-of-date before checking the pf-kernel page. The author is waiting for IMQ to sync with 2.6.36 before releasing -pf1. [EDIT] Please, again, DO NOT FLAG AS OUT-OF-DATE! This package follows - NOT

nous commented on 2010-10-12 08:08 (UTC)

Thanks for the suggestion, I replaced the relevant section from your package.

graysky commented on 2010-10-11 22:10 (UTC)

@nous - you might wanna modify your make localmodconfig line to call the script directly as that make lmc never worked right. See my PKGBUILD in the kernel26-ck package for more.

nous commented on 2010-10-11 18:24 (UTC)

@graysky I vaguely remember that despite my MAKEFLAGS="-j2" in /etc/makepkg.conf, makepkg only used 1 core as I could see it in the xfce4 CPU monitor. Those lines intended to fix that and were forgotten since. Nice catch!

graysky commented on 2010-10-11 15:34 (UTC)

Nice package, thanks for maintaining it. Aren't the following lines redundant? # Make some good use of MAKEFLAGS MAKEFLAGS=`grep -v '#' /etc/makepkg.conf | grep MAKEFLAGS= | sed s/MAKEFLAGS=// | sed s/\"//g` # get kernel version make ${MAKEFLAGS} prepare

nous commented on 2010-10-11 08:01 (UTC)

I'm sorry, I uploaded a test PKGBUILD, it's fixed now.

gaougalos commented on 2010-10-11 07:42 (UTC)

scripts/kconfig/conf -s arch/x86/Kconfig *** *** You have not yet configured your kernel! *** (missing kernel config file ".config") *** *** Please run some configurator (e.g. "make oldconfig" or *** "make menuconfig" or "make xconfig"). *** make[2]: *** [silentoldconfig] Error 1 make[1]: *** [silentoldconfig] Error 2 make: *** No rule to make target `include/config/auto.conf', needed by `include/config/kernel.release'. Stop. Aborting... [christos@christos-arch kernel26-pf]$ cd

nous commented on 2010-10-11 06:26 (UTC) Here CK says he has received a few negative reports about the fork depth patch and will not merge it into the main BFS patch set. For the time being, I'll keep it in the PKGBUILD since it works oh-so-nice for me, but if anyone reports bad behavior I'll remove it.

nous commented on 2010-10-10 07:32 (UTC)

Alright, I was curious about the fork_depth patch so I applied it. I was so impressed by the results, that I updated the PKGBUILD. I haven't changed the version number though, so people will have to explicitly install from the AUR. I started 'grep -ir nous /' and fired up a dozen of the heaviest apps I have installed in my laptop one after the other, switching between them, clicking here and there, playing video and audio. Not a single frame or sound skip, no click action delayed. Superb.

nous commented on 2010-10-09 12:23 (UTC)

@jens It's my understanding that those patches are highly experimental, but Con Kolivas is quickly intergrating them into the main -ck patchset, given enough positive feedback. I don't want to mess with them right now since my systems are responsive enough as they are already and I don't want ranting from people who use kernel26-pf and experience Bad Things. The interbench results though that CK posted are so impressive that I think the patch will be possibly merged in the next BFS version.

jens commented on 2010-10-09 09:39 (UTC) Sorry, I´m just not sure, are the above patches already included in this package? Thanks

nous commented on 2010-10-01 20:37 (UTC)

@sht0rm I can't confirm, it boots fine in my 5 boxes.

commented on 2010-09-30 12:45 (UTC)

in last build i have an error "waiting for udev uevents to be processed [BUSY]" and system stay to long on this message.

nous commented on 2010-09-29 16:28 (UTC)

@mpsnets Great! Could you post your configs (/etc/hibernate/* and /etc/mkinitcpio.conf) to the forum kernel26-pf thread? Pankajmore reported trouble resuming...

commented on 2010-09-28 20:04 (UTC)

Here it works perfectly. It's the best I've found so far. It works perfectly and suspend to RAM Suspend to disk. I have a Core2Duo 4GB RAM ArchLinux x86_64.

pankajmore commented on 2010-09-28 19:10 (UTC)

this kernel is awesome , the system feels very snappy , but sadly hibernation doesn't work , after hibernation , during "..kernel and process data ..." the caps lock led continuously blinks and i have to manually power down by pressing the power button , kernel26-ice works perfectly , so tuxonice works fine on my hardware , does anybody else has issues with hibernation??

nous commented on 2010-09-28 07:04 (UTC)

@kazuo It's already there! Make sure you don't download some older version through a proxy.

kazuo commented on 2010-09-27 20:17 (UTC)

And nous, please what about adding a '-k' to the 'bzip2 -d ${startdir}/logo_linux_*.bz2' so the logo files are not deleted after every makepkg?

lucak3 commented on 2010-09-27 15:07 (UTC)

pf10 patchset out

commented on 2010-09-23 20:19 (UTC)

sorry, fixed. I uninstalled everything and installed again.

commented on 2010-09-23 19:26 (UTC)

I finished upgrading this package and when I run "yaourt-Syu - aur" keeps appearing on the list of packages to update ==> Package upgrade only (new release): aur/kernel26-pf pf7 pf7-2.6.35 -> pf8 -- # uname -rv 2.6.35-pf #1 SMP PREEMPT Thu Sep 23 15:13:36 BRT 2010

nous commented on 2010-09-22 18:30 (UTC)

The is basically the mainstream .5 patch, plus aufs2 and the archlogos. The pf patch already contains the .5 patch. I'm adding the archlogos now.

commented on 2010-09-22 12:37 (UTC)

Why do not you use the patch ArchLinux? ""

nous commented on 2010-09-21 18:06 (UTC)

The fixed kernel packages have been uploaded. 64-bit users, please update your kernels.

nous commented on 2010-09-19 11:32 (UTC)

@harryNID Touched!

commented on 2010-09-19 09:36 (UTC)

aufs2-sqlzma.patch.bz2 1970-Jan-01 04:13:08 107.3K application/x-bzip kernel26.preset 1970-Jan-01 04:13:08 0.4K text/plain These files were created a year before I was born? You might want to touch them. Anyway, what's up with these timestamps? Looks kinda suspicious!

nous commented on 2010-09-18 13:47 (UTC)

After the local root exploit that affects 64-bit kernels (described at and confirmed to work in my 64-bit boxes), I updated the PKGBUILD. Until further notice, PLEASE DO NOT USE THE PREBUILT PACKAGES FROM THE X86_64 REPO, unless you're on a single-user machine and you really know your stuff.

nous commented on 2010-09-17 21:11 (UTC)

The repo has moved to dropbox, please update your unofficial mirrorlist. [pfkernel] Server = or Server = In x86_64 you can find core2 and k8 optimized packages. I use a single PKGBUILD for all versions to make my life easier, so make sure you uninstall any existing kernel26-pf package before you install the -core2 or -k8, otherwise you'll have lots of conflicting files.

nous commented on 2010-09-17 11:03 (UTC)

I was just informed the dns record of the repo was deleted. I'm setting up another, I'll update the information as soon as I'm done.

gaougalos commented on 2010-09-17 10:37 (UTC)

error: failed retrieving file 'pfkernel.db.tar.gz' from : No address record error: failed to update pfkernel (No address record)

nous commented on 2010-09-04 22:02 (UTC)

We now have an unofficial repository for pf-kernel and nvidia-pf, thanks to gtklocker. [pfkernel] Server = or Server = On x86_64 you can find core2 and k8 optimized packages. I use a single PKGBUILD for all versions to make my life easier, so make sure you uninstall any existing kernel26-pf package before you install the -core2 or -k8, otherwise you'll have lots of conflicting files.

nous commented on 2010-08-30 17:52 (UTC)

Since the updates come out more often than some anticipate, it's highly recommended to have a kernel config tailored for your boxes. Use hwd or hwdetect to show you your hardware modules and build the disk controller (and tuxonice and lzo) in-kernel. Everything else can be modules and loaded at startup with /etc/rc.conf. Initrd is not needed this way and you'll reduce kernel build time to a small fraction. Keep at least one alternative kernel (e.g. the stock arch kernel) as a backup.

nous commented on 2010-08-30 09:49 (UTC)

@lucak3 I'll try :) But I can't possibly compile and update the prebuilt packages every single time...

lucak3 commented on 2010-08-30 08:22 (UTC)

pf7 patchset out: are you planning to update every time they release one? It seems this patchset updates very frequently...

nous commented on 2010-08-29 20:38 (UTC)

@MaJia321 GOT IT! It's make's fault. Downgrading to 3.81-5 from [core] solves the problem.

drexya commented on 2010-08-29 18:43 (UTC)

Thanks for the prebuilt packages.

nous commented on 2010-08-28 20:17 (UTC)

AMD Athlon64 K8 optimized package: sha256sum: d525b8abbcba2201696fbe8a3a1b544b20ceb731f45a28a84d5c8c2c24dc4a74 Intel Core2 optimized package: sha256sum: 3eef5f67963113f925e3a228515c49bb4f05ba5aa991d3295f4a8cec6d985398 Generic x86_64 package: sha256sum: c057d32fb0c782d1988a7ee98369247c1248d922245b6c37bda7094d2676a8c8 Generic i686 package: sha256sum: 4661d12c3a13d20939e4c78acde34c9a2c33e5bab842bfacdf1f36e7b1fe8cd4

lucak3 commented on 2010-08-27 19:30 (UTC)

pf6 patchset out (for

nous commented on 2010-08-27 16:21 (UTC)

Prebuilt packages to be found at Main differences from stock archlinux kernel: - BFS as default task scheduler - BFQ as default I/O scheduler - CONFIG_HZ_1000 - TuxOnIce built-in - SquashFS-LZMA and AUFS2

commented on 2010-08-27 07:40 (UTC)

Nice. Привет землякам.

MaJia321 commented on 2010-08-27 01:54 (UTC)

@nous Thanks ;)

nous commented on 2010-08-26 09:52 (UTC)

@MaJia321 I had that same error a couple of times, couldn't pin it down. Try building straight with makepkg instead of using wrappers or download one of the prebuilt packages.

MaJia321 commented on 2010-08-26 01:46 (UTC)

Sorry for the error : $.... INSTALL sound/usb/usx2y/snd-usb-usx2y.ko MKDIR /var/abs/local/kernel26-pf/pkg/lib/firmware/acenic/ make[1]: *** No rule to make target `/var/abs/local/kernel26-pf/pkg/lib/firmware/./', needed by `/var/abs/local/kernel26-pf/pkg/lib/fi.fw'. Stop. make[1]: *** Waiting for unfinished jobs.... MKDIR /var/abs/local/kernel26-pf/pkg/lib/firmware/adaptec/ make: *** [_modinst_post] Error 2 Aborting... Thanks.

commented on 2010-08-25 20:43 (UTC)

@mpsnets: The version of the kernel built, using this package is indeed See for yourself:

commented on 2010-08-25 16:23 (UTC)

kernel 2.6.35 out relesed !

commented on 2010-08-25 14:13 (UTC)

pf5 out! Seeing that it's automatically added via the "special file" (direct link to newest version from hp) perhaps the out of date flag was wrong of me, if so sorry -- mind you that the description is out of date tho!

nous commented on 2010-08-24 08:55 (UTC)

The latest pf4 patch updates to kernel The PKGBUILD has been tested in 2 Arch64 machines and the original config.x86_64 has been modified to include -ck1 by default and tuxonice as modules. Please, submit a good 32bit config. I haven't tested tuxonice hibernation yet, make sure you read first before you hibernate in the middle of your work! If you run a vanilla/custom kernel, you can use its own config - you'll be asked so before build.