It was Nigel's mistake with tuxonice, pf-kernel has been updated against new tuxonice branch. pf2 is out.
Search Criteria
Package Base Details: linux-pf
Package Actions
| Git Clone URL: | https://aur.archlinux.org/linux-pf.git (read-only, click to copy) |
|---|---|
| Keywords: | bbr bbr3 kernel ksm linux linux-pf pf-kernel uksm uksmd v4l2loopback zstd |
| Submitter: | nous |
| Maintainer: | post-factum |
| Last Packager: | post-factum |
| Votes: | 210 |
| Popularity: | 0.40 |
| First Submitted: | 2011-07-24 12:01 (UTC) |
| Last Updated: | 2024-04-20 09:52 (UTC) |
Packages (2)
post-factum commented on 2011-01-07 23:36 (UTC)
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 (http://aur.archlinux.org/packages.php?ID=32877) doesn't even bother to include tuxonice and the kernel26-ice one (http://aur.archlinux.org/packages.php?ID=15224) 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 http://pf.natalenko.name/ before flagging as out-of-date.
<deleted-account> 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 http://git390.marist.edu/cgi-bin/gitweb.cgi?p=linux-2.6.git;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) https://aur.archlinux.org/packages.php?ID=41689.
It would be a good idea to add a few lines to the PKGBUILD to use that before streamline_config.pl, 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, https://aur.archlinux.org/packages/kernel26-bfs/kernel26-bfs/PKGBUILD
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
Pinned Comments
post-factum commented on 2023-09-25 20:30 (UTC)
Official binary builds for various x86_64 μ-arches are available here.
post-factum commented on 2023-09-25 20:20 (UTC)
pf-kernelfollows its own versioning scheme that doesn't depend on stable kernel releases versioning.X.Y.Zpackage version here corresponds tovX.Y-pfZrelease in the source code repo.