I need to separate these IOMMU clusters so Nvidia components stay isolated. Here’s the breakdown of your groups and contents:
- Group 0: Host bridge, Intel Xeon E3-1200 v3 DRAM controller
- Group 1: PCI bridge, Intel Xeon E3-1200 v3/4th Gen Core PCI Express x16 controller
- Group 2: PCI bridge, Intel Xeon E3-1200 v3/4th Gen Core PCI Express x8 controller
- Group 3: VGA compatible controller, AMD Baffin (ATI)
- Group 4: Audio device, AMD Baffin HDMI/DP audio
- Group 5: NVIDIA TU116 graphics card audio controller
- Group 6: USB controller, NVIDIA TU116 USB 3.1 host controller
- Group 7: ISA bridge, Intel Z97 Chipset LPC controller
- Group 8: SATA controller, Intel 9 Series chipset family
- Group 9: SMBus controller, Intel 9 Series chipset family
- Group 10: IOMMU Bridge, Intel Z97 Chipset LPC
- Group 11: Ethernet controller, Realtek RTL8111/8168/8411 PCIe Gigabit Ethernet controller
- Group 12: USB xHCI controller, Intel 9 Series chipset family
- Group 13: Communication controller, Intel ME Interface #1
- Group 14: Audio device, Intel SMBus controller
- Group 15: PCI Express Root Port, Intel 9 Series chipset family
- Group 16: PCI Bridge, ASMedia Technology PCIe to PCI bridge
I’m considering isolating the Nvidia hardware from everything else. This will help with compatibility and troubleshooting.
You might install the recommended kernel with the patch already installed. https://aur.archlinux.org/packages/linux-vfio If not, merge the patch with the source code at https://aur.archlinux.org/cgit/aur.git/p...ides.patch Use the patch command to combine changes and follow the guidance at https://www.pair.com/support/kb/pairclou...-and-patch Then include "pcie_acs_override=downstream,multifunction" in your kernel arguments.
Sure, I can help clarify those points. Installing a new kernel involves updating your system's core files, which can be done through your distribution's package manager or by following specific instructions for the kernel version you're targeting. The "kernal command line" refers to the terminal commands used to manage and configure the kernel during installation. It’s essential to understand these steps carefully to avoid issues.
Regarding the VFIO package, it’s a tool for managing firmware updates on certain devices, but it doesn’t directly relate to installing a new kernel. If you're unsure, checking your system's documentation or seeking guidance from community forums might be more helpful. Let me know if you need further details!
I’ve reviewed a lot of material and realized I just need to follow makepkg as usual. It’s currently being built, though I was hoping for a different outcome. I’m hoping everything works out. If something goes wrong during installation, don’t worry—facepalming is fine.
It stopped executing and now every time I launch it it shows this message: makepkg -si. This means the package build failed. When I try again, it asks to update the git repository and then continues. The process is checking dependencies, downloading sources, applying patches, and verifying signatures before finalizing. If any step fails, it stops and reports issues like missing configuration files or invalid kernel settings.
I received it! I apologized for sending multiple messages, as I struggled to understand and any guidance helped a lot.
Key points:
- IOMMU Group 0: Host bridge with Intel Xeon E3-1200 v3 DRAM controller (rev 06)
- IOMMU Group 1: PCI bridge for Xeon E3-1200 v3/4th Gen Core (rev 06)
- IOMMU Group 10: USB controller from Intel 9 Series (rev 01d.0)
- IOMMU Group 11: ISA bridge and SATA controller details
- IOMMU Group 12: AMD graphics card with Radeon RX series (rev cf)
- IOMMU Group 13: Audio output from AMD graphics (rev a1)
- IOMMU Group 14: NVIDIA TU116 graphics with GeForce GTX 1660 (rev a1)
- IOMMU Group 15: Audio output from NVIDIA TU116 (rev a1)
- IOMMU Group 16: USB controller from NVIDIA TU116 (rev a1)
- IOMMU Group 17: Serial bus controller from NVIDIA (rev a1)
- IOMMU Group 18: Ethernet controller from Realtek (rev 04)
- IOMMU Group 19: Ethernet bridge from ASMedia (rev 06)
- IOMMU Group 2: USB xHCI controller
- IOMMU Group 3: USB xHCI controller
- IOMMU Group 4: Communication controller
- IOMMU Group 5: USB EHCI controller
- IOMMU Group 6: HD Audio controller
- IOMMU Group 7: PCI Express root port bridge
- IOMMU Group 8: PCI Bridge from Intel
- IOMMU Group 9: PCI Express Root Port bridge
- IOMMU Group 13: Audio output
- IOMMU Group 14: VGA compatible controller
- IOMMU Group 15: High definition audio controller
- IOMMU Group 16: USB Type-C controller
- IOMMU Group 17: USB Type-C UCSI controller
Thank you for your support!
No worries man, I appreciate the help. I seem to have another problem. One of the steps on the wiki to set my devices up for pass through has me run this command, which returns an error: sudo mkinitcpio -p linux59 ==> Building image from preset: /etc/mkinitcpio.d/linux59.preset: 'default' -> -k /boot/vmlinuz-5.9-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-5.9-x86_64.img ==> ERROR: '/lib/modules/5.9.11-3-MANJARO' is not a valid kernel module directory ==> Building image from preset: /etc/mkinitcpio.d/linux59.preset: 'fallback' -> -k /boot/vmlinuz-5.9-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-5.9-x86_64-fallback.img -S autodetect ==> ERROR: '/lib/modules/5.9.11-3-MANJARO' is not a valid kernel module directory I think something somewhere hasnt update after manually patching the kernal. Running uname returns this: Linux Tempest 5.9.14-arch1-1-vfio #1 SMP PREEMPT Mon, 14 Dec 2020 04:15:14 +0000 x86_64 GNU/Linux But I noticed that in my settings manager it says Im running kernel version 5.9.11-3, not 5.9.14: This might not be related to my issue, but my best guess says it is. Do you have any idea how I could go about fixing this? Thank you very much for your time.