Arch Linux User Repository

Requires importing GPG Keys to build

# Linus Torvalds
gpg --recv-keys 79BE3E4300411886

# Greg Kroah-Hartman (Linux kernel stable release signing key)
gpg --recv-keys 38DBBDC86092693E

The kernel headers are missing objtool, thus building external kernel modules fails. Adding the snippet from linux/linux-vfio package to PKGBUILD helps:

# add objtool for external module building and enabled VALIDATION_STACK option
if [ -f tools/objtool/objtool ]; then
mkdir -p "${pkgdir}/usr/lib/modules/${_kernver}/build/tools/objtool"
cp -a tools/objtool/objtool ${pkgdir}/usr/lib/modules/${_kernver}/build/tools/objtool/
fi

Sorry all that use this package that it hasn't been updated for quite some time. I'm building it to see if 4.4.52 builds correctly and should be updated later the day this comment is posted.

You might want to avoid upgrading to 4.4.20 for a while. There are potential issues with the keyboard that can prevent booting if you use encryption.

https://bugs.archlinux.org/task/50700

Requires importing GPG Keys to build

# Linus Torvalds
gpg --recv-keys 79BE3E4300411886

# Greg Kroah-Hartman (Linux kernel stable release signing key)
gpg --recv-keys 38DBBDC86092693E

upgrading to 4.4 broke my setup.

Hardware: Xeon X5650 + Sapphire Pure Black X58

Booting with intel_iommu=on will lead to CPU lockup on early boot. Seems like other people with X58 chipset got problems,too. Booting with vanilla 4.6.2 has the same problem. 4.7rc4 boots but vms are messed up. Last know working configuration is 4.1.15-vfio-lts kernel.

Please let me know if you need any more info to fix this.

I don't actually follow the linux-lts package too closely with this - it's much closer to the linux package at the time it was this older version. There are some major differences in config between linux and linux-lts that I haven't found a reason for. They have changed things as important as the preemption model, io scheduler, tickless setting, lower timer hz, and more. Almost seems like the linux-lts package is more geared toward server usage.

I've gone ahead and copied across the last 4.4.x version of linux-vfio then upgraded it to 4.4.8. So if the linux-vfio package at 4.4 worked for you, this should too. If anyone still needs 4.1, it is simple enough to check out an older version of the package from git and build that.

I say if this works with 4.4, and since you seem to like to keep in line with Arch's package equivalent that you should move up to 4.4. I don't use it on my own computer anymore, but I still build it for [markzz].

That's a good question. When I originally made this package, a lot of people seemed to be having trouble with kernels newer than 4.1, but at least for myself, those problems were solved with 4.4+ so I don't even use this package anymore.

Anyone feel strongly one way or the other?

Are you staying on the 4.1 longterm branch of the kernel or are you going to moveto the 4.4 longterm branch as Arch has in [core]?

Instead of posting that here, can you send me an email at the address listed on my AUR account [1] with a subject clearly stating the repo (like "Issue with sigs in [markzz])? If you use Telegram, you can also message me at https://telegram.me/markzz.

[1] https://aur.archlinux.org/account/markzz