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 .. 43 44 45 46 47 48 49 50 51 52 53 .. 106 Next › Last »

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: https://bbs.archlinux.org/viewtopic.php?pid=1212358#p1212358 :)

<deleted-account> 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.

<deleted-account> 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!

« First ‹ Previous 1 .. 43 44 45 46 47 48 49 50 51 52 53 .. 106 Next › Last »