Arch Linux User Repository

• Leaving eclairvoyant's comment pinned because it contains some useful information.
• Patch policy is different, but similar.
  • Primary purpose of this package are the ACS override and i915 VGA arbiter patches.
  • Upstream Arch patches will be applied to maintain parity with the standard kernel.
  • No other patches will be added.
• Package does have options that can be changed, like building with clang or disabling Arch patches.
  • Defaults will match Arch packages, except when incompatible with this package's primary patches.
  • Options are subject to change. Read PKGBUILD for details.
• Avoid commenting and flagging at the same time for the same issue.
  • Flag for common issues with standard solutions, like new releases, key changes, etc.
  • Comment for issues requiring explanation or debugging.
    • Use a pastebin for blocks of text more than a few lines.

This package exists for the specific purpose of adding ported patches based on those originally created by Alex Williamson for:

• Bypassing the default IOMMU grouping by overriding PCIe ACS support, and

• Enabling VGA arbitration support on Intel iGPUs.

Arbitrary patches will not be added.

Refer to the wiki on PCI passthrough and this blog post on IOMMU groups for risks/caveats before using this package.

Regular AUR etiquette applies as well (knowledge of makepkg and searching the wiki/Arch forums is expected, and AUR helpers or Arch-based distros that are not Arch Linux are unsupported).

archqemu: I try to keep up to date with regards to whatever version is in [core]. The problem is, on version releases (e.g. 4.14 -> 4.15), I often have to rewrite the patches (this isn't normally a problem on patch releases like 4.16.7 -> 4.16.8). Because I'm both a full time student and work full time as a software engineer, I am sometimes unable to set aside enough time to update the patches and I get to it when I can. The semester is almost over at the time of this comment, so I should be able to set aside time for sure then, if not sooner.

okay cool, thanks for your quick reply!

I was just curious if there is any systematic release schedule related to the kernel releases.

archqemu: When it's done.

When can we expect an update of this package?

Awesome thanks markzz, I didn't know this, i'm still a bit of a noob (switched from debian) i'm going to try this for the next kernel update. Thanks again.

jmandawg: This is because when you boot this kernel without building the dkms module for it, it will of course not work. Because this is information any user of DKMS should know about, I don't see a reason to pin a comment about that.

I think this is something that you should read what the wiki states on DKMS because it actually lays out the steps to make sure the module is built for your kernel in use and does not require a reinstall of the nvidia-dkms package.

https://wiki.archlinux.org/index.php/Dynamic_Kernel_Module_Support

Someone should sticky the comment by (erylflynn commented on 2016-04-21 17:23 (edited on 2016-07-28 04:34 by erylflynn))

Installing this new kernel will break Xorg if you are using nvidia-dkms, but a re-install of nvidia-dkms fixes it.

Unfortunately there is no way to search the comments on here.

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.

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).

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.