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

Just wanted to comment to thank ironicbadger and also confirm their findings I was having issues in particular with discord and FF14(FFXIV) crashing and losing sound randomly rolling back to 4.19-20 via LTS package appears to have fixed these issues.

I was running into some issues with 5.2.1 kernel today in a Windows 10 guest where 3d apps (such as Firefox, Chrome and Fusion 360) would just randomly quit.

According to my research I found the following on the VFIO discord

A new bug in kernel 5.2 is causing KMODE_EXPECTION_NOT_HANDLED and other anomalies for some people. A few folks reporting artifacting/crashing issues on 5.1 say that issue persists on 5.2 as well, but this is may be a different bug. Root cause of both issues remains unknown currently. Rollback to the last known good or LTS kernels.

I downgraded to 4.19.x via the linux-vfio-lts package and stability returned to my guest. Hope this helps someone out.

If this is a requirement for you, you will need to add this patch yourself when you build.

Any chance to add the Agesa Patch? https://clbin.com/VCiYJ

Also see: https://forum.level1techs.com/t/attention-amd-vfio-users-do-not-update-your-bios/142685

I am getting the following build error:

 Extension error:
Could not import extension kerneldoc (exception: cannot import name 
'AutodocReporter' from 'sphinx.ext.autodoc' (/usr/lib/python3.7/site-packages/sphinx/ext/autodoc/__init__.py))

As the same here: https://aur.archlinux.org/packages/linux-rt-bfq/

Following those patch instructions I deleted some lines in the PKGBUILD and I'm now compiling.

https://git.archlinux.org/svntogit/packages.git/commit/trunk?h=packages/linux&id=cfe52e9aa8168d9571bedf8a376e2cfbd25223fd

PiMaker101: One of the goals of this package is to model it after the standard linux package in the official repositories. This includes configuration options. This does not, however, stop you from changing the config yourself when you build it though.

Tested with 5.0.9 by changing the git tag in the PKGBUILD, working fine, including testing with QEMU 4.0. Noteworthy though, that I had to disable building the doc package (removed htmldocs from make), since there was a build error with sphinx.

By the way, I think it might be a good idea to change the default kernel config in this package to enable voluntary preemption (CONFIG_PREEMPT_VOLUNTARY=y), since this fixes a bug with QEMU/OMVF boot times when configured with a lot of RAM/cores (see https://forums.unraid.net/topic/72172-unraid-os-version-653-available/). Personally using this configuration, have not noticed any side-effects or performance losses on the host so far.

Just wanted to say that In regards to jmandawg and markzz that I have been updating by just changing the versions for about a week now (starting with 5.0-1) with no unexpected behaviour or side effects. Although I should state I haven't done any deep testing outside of just running my normal vms etc.

jmandawg: You can certainly try just changing the PKGBUILD with no new patches, but I would bet on the fact that the current patches will not work. The issue is, it's on my list of things I have to get done, but that list has grown in the last few months to the point where I'm trying to catch up. No ETA at this moment.

EDIT: I take it all back, it looks like the patches did apply, so I'm running a build and will quickly test it tomorrow.

Thanks for the great work, 5.0.x coming anytime soon? Or is it safe to change the _srcver and rebuild?