Package Details: linux-pf 6.11.pf4-1

Git Clone URL: https://aur.archlinux.org/linux-pf.git (read-only, click to copy)
Package Base: linux-pf
Description: The pf-kernel and modules
Upstream URL: https://pfkernel.natalenko.name
Keywords: bbr bbr3 kernel ksm linux linux-pf pf-kernel uksm uksmd v4l2loopback zstd
Licenses: GPL-2.0-only
Provides: KSMBD-MODULE, linux-pf, NTFS3-MODULE, UKSMD-BUILTIN, V4L2LOOPBACK-MODULE, VIRTUALBOX-GUEST-MODULES, WIREGUARD-MODULE
Replaces: virtualbox-guest-modules-arch, wireguard-arch
Submitter: nous
Maintainer: post-factum
Last Packager: post-factum
Votes: 209
Popularity: 0.22
First Submitted: 2011-07-24 12:01 (UTC)
Last Updated: 2024-11-06 15:49 (UTC)

Dependencies (17)

Required by (14)

Sources (2)

Pinned Comments

post-factum commented on 2023-09-25 20:30 (UTC) (edited on 2024-10-08 14:21 (UTC) by post-factum)

Official binary builds for various x86_64 ISA levels are available here.

Latest Comments

« First ‹ Previous 1 .. 50 51 52 53 54 55 56 57 58 59 60 .. 106 Next › Last »

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 http://termite.apcdn.com/full/84760.jpg 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 'http://www.linuxforge.net/linux/kernel/kernel-33-gcc47-0.patch' patch. So I updated my modifed PKGBUILD according to your latest changes: http://pastebin.com/fYSd7hgT

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 (https://aur.archlinux.org/packages.php?ID=62966), 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 (https://aur.archlinux.org/packages.php?ID=64162). 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 kernel.org, 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 kernel.org. See http://freecode.com/projects/pf-kernel.

« First ‹ Previous 1 .. 50 51 52 53 54 55 56 57 58 59 60 .. 106 Next › Last »