The linux-pf thread; BFS/CK, TuxOnIce, BFQ, AUFS3

nous · 2010-08-24 10:36:04

For the fans of BFS/CK and TuxOnIce, I've created a ~~kernel26-pf~~ linux-pf AUR package based on pf-kernel.

For more information, please see the linux-pf wiki page.

Current version (3.9.3-pf) includes:
[1] mainline update: 3.9.3
[2] -ck patchset (BFS v0.425, as default task scheduler)
[3] BFQ (as default I/O scheduler)
[4] TuxOnIce
[5] ~~Interactive CPUfreq governor~~
[6] AUFS3
[7] ~~SquashFS-LZMA~~ (in-kernel as of 2.6.38)
[8] LinuxIMQ
[9] ~~l7 filter!~~
[10] ~~Linux VServer~~

I've tested it on several 64bit boxes, on a 32bit Pentium3 24/7 server, a Pentium-M Thinkpad and a Pentium4 media box. Please, feel free to test, improve and report.

If you compile it yourself, you'll be asked before build whether to use the stock -ARCH config, your running kernel's or a semi-automated tailored-to-box localmodconfig (using the remarkable modprobed-db by graysky).

For the rest, I maintain an unofficial repository with prebuilt packages for linux-pf, my AUR packages and a few more (like nvidia-pf):

[pfkernel]
Server = http://dl.dropbox.com/u/11734958/$arch

Prebuilt x86_64 packages for: Intel Pentium4/D/Nocona - Xeon, Core2, Atom, AMD Athlon64 K8, Generic x86_64
Prebuilt i686 packages for: Intel Pentium3, Pentium4, Pentium-M, Atom, Core2, AMD K7, K8, Generic i686

I use a single PKGBUILD for all versions to make my life easier, so if you want to install a core2, k8 or any other optimized package, pacman hopefully will uninstall the generic linux-pf[-headers] first; if not, then uninstall the generic ones first.

Last edited by nous (2013-05-24 17:19:47)

72linus · 2010-08-24 11:25:56

I'm getting this error as soon as it starts?

# configuration written to .config
#
make: *** No rule to make target `#-j2'. Stop.
Aborting...
The build failed.

EDIT:
my bad, I had to uncomment line 36 of /etc/makepkg.conf

MAKEFLAGS="-j2"

it's compiling now....

EDIT again:
I need to also apply 2 other patches; how would I do this?
edit the PKGBUILD?
thx

Last edited by 72linus (2010-08-24 12:12:04)

Inxsible · 2010-08-24 13:36:12

Moving to PKGBUILDS and ABS Support

lucak3 · 2010-08-24 14:01:27

I was interested in this one for some months already, but never got around to write a PKGBUILD. Glad to see someone else was more efficient than me
BTW, since i'm a Nvidia user, i submitted the nvidia-pf package to AUR [http://aur.archlinux.org/packages.php?ID=40205]
Keep it up !

72linus · 2010-08-24 14:12:35

no matter how I edit the PKGBUILD it never works
How can I apply 2 patches??

Or, why does the patch (http://nebula.pl.ua/download.php?q=8a36 … 48301758d3)
fail if i try to do it manually?

flamelab · 2010-08-24 14:17:05

Are you running yaourt or something for the building ?

I built and installed this kernel succesfully, without any prob (no makepkg.conf issue as 72linus stated).

72linus · 2010-08-24 14:50:21

I'm doing "packer -S kernel26-pf"

I think I got it, as i added this to pkgbuild

# allows you to edit config
echo "sleeping 400"
sleep 400
make menuconfig && cp -v .config ${startdir}/config && msg "Stopping build"

while it was sleeping, I added the patches I needed, moved some stuff into the src
and then proceded with the makemenuconfig part
I also let it add my /proc/config.gz from my existing custom 2.6.35.3 kernel

it's compiling now so we'll see....

Last edited by 72linus (2010-08-24 14:51:08)

flamelab · 2010-08-24 15:06:40

Well, you really should do the patching within the PKGBUILD, not outside it.

72linus · 2010-08-24 15:16:10

I cant figure out how to do that flamelab...

I have to apply 2 patches
aufs & squashfs-lzma

patch -p1 < ../aufs2.patch
patch -p1 < ../kernel-squashfs-lzma.patch

then it has to copy
Documentation/ABI/testing/debugfs-aufs to /tmp/packerbuild-0/kernel26-pf/kernel26-pf/Documentation/ABI/testing/
Documentation/ABI/testing/sysfs-aufs to /tmp/packerbuild-0/kernel26-pf/kernel26-pf/Documentation/ABI/testing

fs/aufs to /tmp/packerbuild-0/kernel26-pf/kernel26-pf/fs/

include/linux/aufs_type.h to /tmp/packerbuild-0/kernel26-pf/kernel26-pf/include/linux/

I can't figure out how to do that?

72linus · 2010-08-24 19:12:05

ok it went well
but, why is the resulting kernel 2.6.35 vs 2.6.35.3?
I thought it was 2.6.35.3?

nous · 2010-08-24 19:40:20

72linus wrote:

no matter how I edit the PKGBUILD it never works
How can I apply 2 patches??
Or, why does the patch (http://nebula.pl.ua/download.php?q=8a36 … 48301758d3)
fail if i try to do it manually?

Please, be more specific or pastebin the errors somewhere. That patch is applied against vanilla 2.6.35.

72linus · 2010-08-24 19:44:29

hello nous

excuse my ignorance please!
I only have 3 yrs in computers (1 in windows xp, 2 now in Linux)

so, I am muddling around in the linux world.

so the patch is not against the stable 2.6.35.3 but 2.6.35?

there are too many failures to pastebin too I guess..

I dont really want to manually do this anyway
if I give you the aufs/squashfs stuff could you integrate it into your -pf build or maybe release a new one?
thx

nous · 2010-08-24 19:50:21

72linus wrote:

ok it went well
but, why is the resulting kernel 2.6.35 vs 2.6.35.3?
I thought it was 2.6.35.3?

I intentionally removed the patchlevel version, as it's easier to maintain the PKGBUILD and as the pf-kernel patch author does himself. The current package is versioned as 2.6.35-pf4 and if, I understand correctly, the versioning scheme follows the official patchlevel+1 (i.e. .1==pf2, .2==pf3 etc).

nous · 2010-08-24 19:55:02

72linus wrote:

I'm getting this error as soon as it starts?
# configuration written to .config
#
make: *** No rule to make target `#-j2'. Stop.
Aborting...
The build failed.
EDIT:
my bad, I had to uncomment line 36 of /etc/makepkg.conf
MAKEFLAGS="-j2"
it's compiling now....

It wasn't your bad, it was my bad and it's fixed now as I stumbled upon the bug on a single-core laptop where I also had that option commented out. Not all people own multi-core boxes...

72linus wrote:

EDIT again:
I need to also apply 2 other patches; how would I do this?
edit the PKGBUILD?
thx

Yep, that's the Arch way. Keep in mind, the -pf4 patch includes the official 2.6.35.3 update.

nous · 2010-08-24 19:56:42

lucak3 wrote:

I was interested in this one for some months already, but never got around to write a PKGBUILD. Glad to see someone else was more efficient than me
BTW, since i'm a Nvidia user, i submitted the nvidia-pf package to AUR [http://aur.archlinux.org/packages.php?ID=40205]
Keep it up !

Thanks and thanks (I'm an nvidia fan myself).

72linus · 2010-08-24 19:57:33

ok
see, i'm trying to update my arch/slackware nFluxOS builds with the 2.6.35 kernel thus I need aufs/squashfs-lzma support for linux-live to work,etc
I could just use the one I have but many always want the tux,bfq,etc stuff thats why when I saw your pkgbuild I jumped on it as the Zen kernel 2.6.35 isn't released yet right?

so, if I had the knowledge I would put out my own aur build but I dont have the time to learn all about pkgbuilds,etc
as it usually goes wrong for me,etc

in Slackware it's much easier to create a pkg and thats where my forte is I guess....

so, I just need to add the 2 patches I want as I said before, to your build and its all good I guess

heres uname -r
2.6.35-pf

so, it s working good i guess and I will also compile it on my slackware build too

if you want to add the patches to your build I would be ecstatic!?

nous · 2010-08-24 20:31:36

72linus wrote:

ok
see, i'm trying to update my arch/slackware nFluxOS builds with the 2.6.35 kernel thus I need aufs/squashfs-lzma support for linux-live to work,etc
I could just use the one I have but many always want the tux,bfq,etc stuff thats why when I saw your pkgbuild I jumped on it as the Zen kernel 2.6.35 isn't released yet right?
so, if I had the knowledge I would put out my own aur build but I dont have the time to learn all about pkgbuilds,etc
as it usually goes wrong for me,etc
in Slackware it's much easier to create a pkg and thats where my forte is I guess....
so, I just need to add the 2 patches I want as I said before, to your build and its all good I guess
heres uname -r
2.6.35-pf
so, it s working good i guess and I will also compile it on my slackware build too
if you want to add the patches to your build I would be ecstatic!?

I'm sorry, I tried the aforementioned patches and they didn't apply cleanly. I used the slackware tarballs though, as I didn't want to mess with git trees, but it's just too much work for my limited time.

72linus · 2010-08-24 20:34:13

whats too much to ask?

nous · 2010-08-24 20:52:58

72linus wrote:

whats too much to ask?

Please, try to understand that fixing patches is a very time-consuming task, and time is not a commodity I can spare. I made this PKGBUILD mainly for my convenience but I would add those patches if it was quick and easy. Unfortunately, it is not.

If I were you, I would use multiple kernels in my grub menu, the -zen one for aufs/sqlzma work and -ARCH or -pf or whichever else for all the latest bells and whistles.

72linus · 2010-08-24 20:58:58

ok, thx
heres the aufs/squashfs-lzma patches
http://ponce.cc/slax-remix/

as you may know, those 2 patches are essential to creating a livecd/usb from your arch/slackware install
when combined with Ritchie's linux-live scripts

I want to use your kernel26-pf + those patches,etc and
it's ok with you if I do that?

its easier for me to "find" appropriate kernels vs compiling one because of my limited kernel knowledge
and the fact that I have 4 distro's to maintain too:)

note that all my stuff is testing/unstable; so your kernel works great in arch testing as thats all I have.

nous · 2010-08-24 22:08:11

72linus wrote:

ok, thx
heres the aufs/squashfs-lzma patches
http://ponce.cc/slax-remix/

These apply almost cleanly. I'm updating the PKGBUILD to include aufs and squashfs-lzma.

72linus wrote:

as you may know, those 2 patches are essential to creating a livecd/usb from your arch/slackware install
when combined with Ritchie's linux-live scripts
I want to use your kernel26-pf + those patches,etc and
it's ok with you if I do that?

72linus · 2010-08-24 22:27:07

thanks alot!
why do you say "almost cleanly"?

nous · 2010-08-25 09:47:12

72linus wrote:

thanks alot!
why do you say "almost cleanly"?

patch(1) croaked for a few offsets only.

72linus · 2010-08-25 16:44:05

hey man
Ok, I had some issues that maybe you can help with?

1) as soon as it started compiling it stopped saying fs/aufs no such directory,etc

2) I manually stopped the script, moved all the aufs stuff into src and it then finished successfully

3) when trying to install the new package; many many errors appeared

error: could not open file /var/lib/pacman/local/kernel26-pf-2.6.35-pf4/depends: No such file or directory

Targets (1): kernel26-pf-2.6.35-pf4 [25.54 MB]

Total Download Size:    0.00 MB
Total Installed Size:   121.12 MB

Proceed with installation? [Y/n] 
checking package integrity...
(1/1) checking for file conflicts                                                                            [----------------------------------------------------------------] 100%
error: could not open file /var/lib/pacman/local/kernel26-pf-2.6.35-pf4/files: No such file or directory
error: could not open file /var/lib/pacman/local/kernel26-pf-2.6.35-pf4/desc: No such file or directory
error: could not open file /var/lib/pacman/local/kernel26-pf-2.6.35-pf4/desc: No such file or directory
error: could not open file /var/lib/pacman/local/kernel26-pf-2.6.35-pf4/files: No such file or directory
(1/1) upgrading kernel26-pf                                                                                  [----------------------------------------------------------------] 100%
warning: directory permissions differ on boot/
filesystem: 777  package: 755
>>>
>>> If you use the LILO bootloader, you should run 'lilo' before rebooting.
>>>
>>> Updating module dependencies. Please wait ...
WARNING: Couldn't open directory /lib/modules/2.6.35-pf: No such file or directory
FATAL: Could not open /lib/modules/2.6.35-pf/modules.dep.temp for writing: No such file or directory
>>> MKINITCPIO SETUP
>>> ----------------
>>> If you use LVM2, Encrypted root or software RAID,
>>> Ensure you enable support in /etc/mkinitcpio.conf .
>>> More information about mkinitcpio setup can be found here:
>>> http://wiki.archlinux.org/index.php/Mkinitcpio

>>> Generating initial ramdisk, using mkinitcpio.  Please wait...
==> Building image "default"
==> Running command: /sbin/mkinitcpio -k 2.6.35-pf -c /etc/mkinitcpio.conf -g /boot/kernel26-pf.img
:: Begin build
:: Parsing hook [base]
:: Parsing hook [udev]
:: Parsing hook [autodetect]
FATAL: Could not load /lib/modules/2.6.35-pf/modules.dep: No such file or directory
FATAL: Could not load /lib/modules/2.6.35-pf/modules.dep: No such file or directory
FATAL: Could not load /lib/modules/2.6.35-pf/modules.dep: No such file or directory
find: `/lib/modules/2.6.35-pf': No such file or directory
FATAL: Could not load /lib/modules/2.6.35-pf/modules.dep: No such file or directory
find: `/lib/modules/2.6.35-pf': No such file or directory
:: Parsing hook [pata]
:: Parsing hook [scsi]
:: Parsing hook [sata]
:: Parsing hook [filesystems]
:: Generating image '/boot/kernel26-pf.img'...SUCCESS
==> SUCCESS
==> Building image "fallback"
==> Running command: /sbin/mkinitcpio -k 2.6.35-pf -c /etc/mkinitcpio.conf -g /boot/kernel26-pf-fallback.img -S autodetect
:: Begin build
:: Parsing hook [base]
:: Parsing hook [udev]
:: Parsing hook [pata]
:: Parsing hook [scsi]
:: Parsing hook [sata]
:: Parsing hook [filesystems]
:: Generating image '/boot/kernel26-pf-fallback.img'...SUCCESS
==> SUCCESS
[root@nflux ~]# depmod -a
[root@nflux ~]# pacman -U kernel26-pf-2.6.35-pf4-i686.pkg.tar.xz 
resolving dependencies...
looking for inter-conflicts...

Targets (1): kernel26-pf-2.6.35-pf4 [25.54 MB]

Total Download Size:    0.00 MB
Total Installed Size:   121.12 MB

Proceed with installation? [Y/n] 
checking package integrity...
(1/1) checking for file conflicts                                                                            [----------------------------------------------------------------] 100%
(1/1) upgrading kernel26-pf                                                                                  [----------------------------------------------------------------] 100%
warning: directory permissions differ on boot/
filesystem: 777  package: 755
>>>
>>> If you use the LILO bootloader, you should run 'lilo' before rebooting.
>>>
>>> Updating module dependencies. Please wait ...
WARNING: Couldn't open directory /lib/modules/2.6.35-pf: No such file or directory
FATAL: Could not open /lib/modules/2.6.35-pf/modules.dep.temp for writing: No such file or directory
>>> MKINITCPIO SETUP
>>> ----------------
>>> If you use LVM2, Encrypted root or software RAID,
>>> Ensure you enable support in /etc/mkinitcpio.conf .
>>> More information about mkinitcpio setup can be found here:
>>> http://wiki.archlinux.org/index.php/Mkinitcpio

>>> Generating initial ramdisk, using mkinitcpio.  Please wait...
==> Building image "default"
==> Running command: /sbin/mkinitcpio -k 2.6.35-pf -c /etc/mkinitcpio.conf -g /boot/kernel26-pf.img
:: Begin build
:: Parsing hook [base]
:: Parsing hook [udev]
:: Parsing hook [autodetect]
FATAL: Could not load /lib/modules/2.6.35-pf/modules.dep: No such file or directory
FATAL: Could not load /lib/modules/2.6.35-pf/modules.dep: No such file or directory
FATAL: Could not load /lib/modules/2.6.35-pf/modules.dep: No such file or directory
find: `/lib/modules/2.6.35-pf': No such file or directory
FATAL: Could not load /lib/modules/2.6.35-pf/modules.dep: No such file or directory
find: `/lib/modules/2.6.35-pf': No such file or directory
:: Parsing hook [pata]
:: Parsing hook [scsi]
:: Parsing hook [sata]
:: Parsing hook [filesystems]
:: Generating image '/boot/kernel26-pf.img'...SUCCESS
==> SUCCESS
==> Building image "fallback"
==> Running command: /sbin/mkinitcpio -k 2.6.35-pf -c /etc/mkinitcpio.conf -g /boot/kernel26-pf-fallback.img -S autodetect
:: Begin build
:: Parsing hook [base]
:: Parsing hook [udev]
:: Parsing hook [pata]
:: Parsing hook [scsi]
:: Parsing hook [sata]
:: Parsing hook [filesystems]
:: Generating image '/boot/kernel26-pf-fallback.img'...SUCCESS
==> SUCCESS

/tmp/packerbuild-0/kernel26-pf/kernel26-pf/PKGBUILD: line 230: cd: /tmp/packerbuild-0/kernel26-pf/kernel26-pf/pkg/lib/modules/2.6.35-pf: No such file or directory
==> Tidying install...
  -> Purging other files...
  -> Compressing man and info pages...
  -> Stripping unneeded symbols from binaries and libraries...
==> WARNING: Package contains reference to $srcdir

even though it says it cant open such&such, all the files are there, etc
so maybe it was a path issue?

however; I installed it 2x using "pacman -U"
the 2nd time there were less errors?!
and even though theres all those messages it booted successfully with no problems?!
lol

so, I guess there's some things to fix,etc?

Thanks for adding the aufs/squashfs stuff for me too!
I'm gonna try it on my x86_64 install on same PC and see whats up
my pc can do both 32 and 64; although its old:)

[root@nflux ~]# uname -r
2.6.35-pf-arch32

Last edited by 72linus (2010-08-25 16:46:19)

Cdh · 2010-08-25 17:16:56

Can someone test tuxonice with this kernel and btrfs as /?

I tried it and on resuming the btrfs filesystem was broken (so make a backup before!!!).

http://pastebin.com/YEjBxfeR

Arch Linux

#1 2010-08-24 10:36:04

The linux-pf thread; BFS/CK, TuxOnIce, BFQ, AUFS3

#2 2010-08-24 11:25:56

Re: The linux-pf thread; BFS/CK, TuxOnIce, BFQ, AUFS3

#3 2010-08-24 13:36:12

Re: The linux-pf thread; BFS/CK, TuxOnIce, BFQ, AUFS3

#4 2010-08-24 14:01:27

Re: The linux-pf thread; BFS/CK, TuxOnIce, BFQ, AUFS3

#5 2010-08-24 14:12:35

Re: The linux-pf thread; BFS/CK, TuxOnIce, BFQ, AUFS3

#6 2010-08-24 14:17:05

Re: The linux-pf thread; BFS/CK, TuxOnIce, BFQ, AUFS3

#7 2010-08-24 14:50:21

Re: The linux-pf thread; BFS/CK, TuxOnIce, BFQ, AUFS3

#8 2010-08-24 15:06:40

Re: The linux-pf thread; BFS/CK, TuxOnIce, BFQ, AUFS3

#9 2010-08-24 15:16:10

Re: The linux-pf thread; BFS/CK, TuxOnIce, BFQ, AUFS3

#10 2010-08-24 19:12:05

Re: The linux-pf thread; BFS/CK, TuxOnIce, BFQ, AUFS3

#11 2010-08-24 19:40:20

Re: The linux-pf thread; BFS/CK, TuxOnIce, BFQ, AUFS3

#12 2010-08-24 19:44:29

Re: The linux-pf thread; BFS/CK, TuxOnIce, BFQ, AUFS3

#13 2010-08-24 19:50:21

Re: The linux-pf thread; BFS/CK, TuxOnIce, BFQ, AUFS3

#14 2010-08-24 19:55:02

Re: The linux-pf thread; BFS/CK, TuxOnIce, BFQ, AUFS3

#15 2010-08-24 19:56:42

Re: The linux-pf thread; BFS/CK, TuxOnIce, BFQ, AUFS3

#16 2010-08-24 19:57:33

Re: The linux-pf thread; BFS/CK, TuxOnIce, BFQ, AUFS3

#17 2010-08-24 20:31:36

Re: The linux-pf thread; BFS/CK, TuxOnIce, BFQ, AUFS3

#18 2010-08-24 20:34:13

Re: The linux-pf thread; BFS/CK, TuxOnIce, BFQ, AUFS3

#19 2010-08-24 20:52:58

Re: The linux-pf thread; BFS/CK, TuxOnIce, BFQ, AUFS3

#20 2010-08-24 20:58:58

Re: The linux-pf thread; BFS/CK, TuxOnIce, BFQ, AUFS3

#21 2010-08-24 22:08:11

Re: The linux-pf thread; BFS/CK, TuxOnIce, BFQ, AUFS3

#22 2010-08-24 22:27:07

Re: The linux-pf thread; BFS/CK, TuxOnIce, BFQ, AUFS3

#23 2010-08-25 09:47:12

Re: The linux-pf thread; BFS/CK, TuxOnIce, BFQ, AUFS3

#24 2010-08-25 16:44:05

Re: The linux-pf thread; BFS/CK, TuxOnIce, BFQ, AUFS3

#25 2010-08-25 17:16:56

Re: The linux-pf thread; BFS/CK, TuxOnIce, BFQ, AUFS3

Board footer