Package Details: linux-vfio-headers 4.18.9.arch1-1

Git Clone URL: (read-only)
Package Base: linux-vfio
Description: Header files and scripts for building modules for Linux-vfio kernel
Upstream URL:
Keywords: acs arbiter assignment gpu i915 kvm override passthrough pci qemu vfio vga
Licenses: GPL2
Submitter: zman0900
Maintainer: zman0900 (markzz)
Last Packager: markzz
Votes: 47
Popularity: 0.602703
First Submitted: 2015-01-30 06:41
Last Updated: 2018-09-23 11:50

Pinned Comments

markzz commented on 2017-12-14 06:10

(4.14.5+) Because Arch itself has dropped i686 support, I have removed i686 from the PKGBUILD and there is no config file either.

electricprism commented on 2016-01-04 04:30

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

Latest Comments

1 2 3 4 5 6 ... Next › Last »

MurkyDepths commented on 2018-09-08 22:00

Sorry it took so long to reply, got busy with some other stuff.

I've done with and without AUR helpers. Pacaur seemed to work fine, without was a 70/30ish of it working or not. Over the course of some ten+ installs about 3 or 5 ended up working. Without doing anything different before the install.

Essentially, I have no idea what the problem is.

markzz commented on 2018-09-05 03:11

The -headers and -docs packages are not required to use the base package. The headers package are just that, headers for developers that need them. The docs package is also just that, documentation for the kernel and you don't need them to run the kernel.

If you are using an AUR helper, don't. They are not supported and I will not even entertain issues with packages built with them. Try building using makepkg alone and if that doesn't work, use a clean chroot (check the wiki).

If you really want to try a known good built package done in a clean chroot, you can try the package in my public repository. Again, check the wiki. I know for a fact that this PKGBUILD is known to work as I use it every day with no issue (and on an Nvidia card with the nouveau drivers).

MurkyDepths commented on 2018-09-04 18:20

When I install it asks if I want to install linux-vfio-headers and docs. They should be installed, but I don't even know. I'll go test that when I have time. If headers aren't installed that's likely the problem, if they are I'll get the version number. I'll also check dkms as you mentioned. And if anything doesn't really work, I'll try rebuilding it.

erylflynn commented on 2018-09-04 17:40

Only time I saw anything like this was when the kernel was built but the headers was not. I tried a new AUR tool and it only built the linux-vfio package, not linux-vfio-headers. Once I rebuilt everything making sure the headers installed it worked.

Check linux-vfio-headers installed version. Also "dkms status" to show if the module for your video drivers was built. If not force dkms to rebuild and see what happens.

MurkyDepths commented on 2018-09-04 17:32

I've searched as extensively as I could manage. Every time was a fresh install. With or without nvidia drivers. Blacklisting nouveau or nvidia, setting a default output card does nothing, binding the card with pci-stub and/or vfio-bind doesn't change anything. Different desktop managers changes nothing, reinstalling desktop managers and Xorg doesn't change anything. Haven't found anything special in the logs I've looked at or using dmesg(or whatever it's called, I can't recall). If there are any other drivers I need to worry about I don't know which ones they are.

Honestly I'm at my wits end, I'm far from a veteran but I'm at least a decently good user, but nothing special. Though searches on google and scouring wikis and forums I haven't found anything that solves it. I've found ones with similar problems to mine, but either with no solution or one that doesn't work for me.

Is there a way to log the installation process of linux-vfio? I've noticed some red text pop up here and there, but am not sure how to get my hands on it. Only thought of that during my writing of this. Usually, at the end, or close to it, there is usually a rather large red block of text, probably ten lines at the very least. I have no idea if these are errors or not, but if I can get my hands on that log it might help solving whatever problem is causing this. Whether that's a hardware issue or software I can't say.

markzz commented on 2018-09-03 16:25

MurkyDepths: Did you check the Wiki, the forums, Google?

I can tell you this kernel is working fine on at least my system. Check your drivers, check your logs, etc...

MurkyDepths commented on 2018-09-03 13:45

For some reason installing this now kills graphical boot and it’s stuck on a blackscreen with a blinking cursor. Non-graphical boot works fine though. Have you encountered this before? If so, do you know of a way to fix it?

MurkyDepths commented on 2018-08-30 15:42

Sorry, I'm like maybe day one on arch so I have little to no idea how AUR works properly. Though I'm learning, it doesn't stop me from being stupid.

markzz commented on 2018-08-30 14:59

The answer to that question is always "When it's done."

Also, seeing as this PKGBUILD is on 4.18.4 right now tells you something about your question...

MurkyDepths commented on 2018-08-30 14:23

Is the patch available to 4.18.*? If it isn't, how long do you think it'll be until it's updated?