Jimmy235

Which version of Unraid is needed for Macinabox? I have 6.5.3 and can`t find in apps.

So, set up a VM, installed fresh Win10 over VNC. No problem, worked fine. After shutting down and adding GPU+dumped.rom —> again nothing, black screen Last line in VM Log: 2019-05-12T16:12:50.015631Z qemu-system-x86_64: vfio: Unable to power on device, stuck in D3 2019-05-12T16:12:50.015828Z qemu-system-x86_64: vfio: Unable to power on device, stuck in D3 LibVirt Log: 2019-05-12 16:23:04.891+0000: 2996: info : libvirt version: 5.1.0 2019-05-12 16:23:04.891+0000: 2996: info : hostname: HOTSERVER 2019-05-12 16:23:04.891+0000: 2996: warning : qemuDomainObjTaint:7986 : Domain id=1 name='Windows 10 3' uuid=d65ff948-f0de-1ef1-ba42-d014e792fd1f is tainted: high-privileges 2019-05-12 16:23:04.891+0000: 2996: warning : qemuDomainObjTaint:7986 : Domain id=1 name='Windows 10 3' uuid=d65ff948-f0de-1ef1-ba42-d014e792fd1f is tainted: host-cpu 2019-05-12 16:23:58.120+0000: 2996: error : virPCIGetHeaderType:3238 : internal error: Unknown PCI header type '127' 2019-05-12 16:23:58.120+0000: 2996: error : virHostdevReAttachPCIDevices:1071 : Failed to reset PCI device: internal error: Unknown PCI header type '127' 2019-05-12 16:23:58.120+0000: 2996: error : virPCIGetHeaderType:3238 : internal error: Unknown PCI header type '127' 2019-05-12 16:23:58.120+0000: 2996: error : virHostdevReAttachPCIDevices:1071 : Failed to reset PCI device: internal error: Unknown PCI header type '127' 2019-05-12 16:24:01.405+0000: 3000: error : virPCIGetHeaderType:3238 : internal error: Unknown PCI header type '127'

Tried it with a fresh one too. Exactly the same.

With only 1 core pegged the windows circle don‘t show up even anymore XD

Over VNC I can see the Tiano Core picture and the Windows circle in a never ending loop.

Yeah, it is showing unraids output. I have 3 monitors. One is connected by DVI as unraid output and two in the second pci slot for the vm 1080. I tried it already with removing vbios.

It‘s a copy paste mistake. Today I plugged another GPU into the first PCIe slot and moved the 1080 to the second slot. It`s exactly the same error. VM starts, screens keep black, a second try starting the VM result in „PCI header type 127“ error. Log of VM: -smp 12,sockets=1,cores=12,threads=1 \ -uuid a6892ae7-daa1-15b8-e162-4eef1bdf7548 \ -display none \ -no-user-config \ -nodefaults \ -chardev socket,id=charmonitor,fd=24,server,nowait \ -mon chardev=charmonitor,id=monitor,mode=control \ -rtc base=localtime \ -no-hpet \ -no-shutdown \ -boot strict=on \ -device ich9-usb-ehci1,id=usb,bus=pci.0,addr=0x7.0x7 \ -device ich9-usb-uhci1,masterbus=usb.0,firstport=0,bus=pci.0,multifunction=on,addr=0x7 \ -device ich9-usb-uhci2,masterbus=usb.0,firstport=2,bus=pci.0,addr=0x7.0x1 \ -device ich9-usb-uhci3,masterbus=usb.0,firstport=4,bus=pci.0,addr=0x7.0x2 \ -device virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x3 \ -drive 'file=/mnt/user/backups/1stVM/Windows 10/vdisk1.img,format=raw,if=none,id=drive-virtio-disk2,cache=writeback' \ -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x4,drive=drive-virtio-disk2,id=virtio-disk2,bootindex=1,write-cache=on \ -drive file=/mnt/user/isos/Windows10x64_0519.iso,format=raw,if=none,id=drive-ide0-0-0,readonly=on \ -device ide-cd,bus=ide.0,unit=0,drive=drive-ide0-0-0,id=ide0-0-0,bootindex=2 \ -drive file=/mnt/user/isos/virtio-win-0.1.160-1.iso,format=raw,if=none,id=drive-ide0-0-1,readonly=on \ -device ide-cd,bus=ide.0,unit=1,drive=drive-ide0-0-1,id=ide0-0-1 \ -netdev tap,fd=27,id=hostnet0,vhost=on,vhostfd=28 \ -device virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:8b:6d:12,bus=pci.0,addr=0x2 \ -chardev pty,id=charserial0 \ -device isa-serial,chardev=charserial0,id=serial0 \ -chardev socket,id=charchannel0,fd=30,server,nowait \ -device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=org.qemu.guest_agent.0 \ -device vfio-pci,host=0c:00.0,id=hostdev0,bus=pci.0,addr=0x5,romfile=/mnt/user/isos/vbios/GTX1080.rom \ -device vfio-pci,host=0e:00.3,id=hostdev1,bus=pci.0,addr=0x6 \ -device vfio-pci,host=0d:00.3,id=hostdev2,bus=pci.0,addr=0x8 \ -device usb-host,hostbus=1,hostaddr=5,id=hostdev3,bus=usb.0,port=1 \ -device usb-host,hostbus=1,hostaddr=7,id=hostdev4,bus=usb.0,port=2 \ -sandbox on,obsolete=deny,elevateprivileges=deny,spawn=deny,resourcecontrol=deny \ -msg timestamp=on 2019-05-12 09:30:05.727+0000: Domain id=1 is tainted: high-privileges 2019-05-12 09:30:05.727+0000: Domain id=1 is tainted: host-cpu char device redirected to /dev/pts/0 (label charserial0) 2019-05-12T09:30:07.945915Z qemu-system-x86_64: vfio: Cannot reset device 0000:0e:00.3, depends on group 21 which is not owned. 2019-05-12T09:30:07.974404Z qemu-system-x86_64: vfio: Cannot reset device 0000:0e:00.3, depends on group 21 which is not owned. System Log: May 12 11:30:19 HOTSERVER ntpd[2022]: kernel reports TIME_ERROR: 0x41: Clock Unsynchronized ??

No, I still get „unknown PCI header type ˋ127ˋ" when VM started once and try‘n to start again. And the screen stays black if I try to start a fresh VM without any drivers installed. I edited my vbios originally with this video from spaceinvader yesterday.

Started in legacy instead of UEFI. Now the warning in the VM-Log is not showing up anymore, but screen keeps black.

Just updated to 6.7.0, changed to i1440fx-3.1. Same behavior as before „Failed to mmap“ vbios and screen keeps black. One more thing: As soon as I try to start the VM and it fails, I can not reboot unraid.

Tried 6.5.3 / 6.6.6 / 6.6.7 which is released in Feb. Where I can find 6.7?

I dumped the vbios directly from my own GPU. Using the same dumped vbios on all versions. On 6.5.3 it works. On all above that not.

Bastl, the strange problem here is that VM is running on 6.5.3 but NOT on any version of Unraid above 6.5.3 (including latest) I assume that the latest version of Unraid has updates for Ryzen and would be better, but I can`t use it because it`s not working.

I just put in the other USB drive and tried to boot the VM. Log of VM: (seems the warning is the GPU, not the device from Group 19) 2019-05-11 10:04:15.494+0000: shutting down, reason=failed 2019-05-11 10:05:31.106+0000: starting up libvirt version: 4.7.0, qemu version: 3.0.0, kernel: 4.18.20-unRAID, hostname: HOTSERVER LC_ALL=C PATH=/bin:/sbin:/usr/bin:/usr/sbin HOME=/ QEMU_AUDIO_DRV=none /usr/local/sbin/qemu -name 'guest=Windows 10,debug-threads=on' -S -object 'secret,id=masterKey0,format=raw,file=/var/lib/libvirt/qemu/domain-2-Windows 10/master-key.aes' -machine pc-i440fx-2.11,accel=kvm,usb=off,dump-guest-core=off,mem-merge=off -cpu host,hv_time,hv_relaxed,hv_vapic,hv_spinlocks=0x1fff,hv_vendor_id=none -drive file=/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd,if=pflash,format=raw,unit=0,readonly=on -drive file=/etc/libvirt/qemu/nvram/a6892ae7-daa1-15b8-e162-4eef1bdf7548_VARS-pure-efi.fd,if=pflash,format=raw,unit=1 -m 16896 -realtime mlock=off -smp 12,sockets=1,cores=12,threads=1 -uuid a6892ae7-daa1-15b8-e162-4eef1bdf7548 -display none -no-user-config -nodefaults -chardev socket,id=charmonitor,fd=24,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=localtime -no-hpet -no-shutdown -boot strict=on -device ich9-usb-ehci1,id=usb,bus=pci.0,addr=0x7.0x7 -device ich9-hardev=charserial0,id=serial0 -chardev socket,id=charchannel0,fd=30,server,nowait -device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=org.qemu.guest_agent.0 -device vfio-pci,host=0b:00.0,id=hostdev0,bus=pci.0,addr=0x5,romfile=/mnt/user/isos/vbios/GTX1080.rom -device vfio-pci,host=0d:00.3,id=hostdev1,bus=pci.0,addr=0x6 -device usb-host,hostbus=1,hostaddr=5,id=hostdev2,bus=usb.0,port=1 -device usb-host,hostbus=1,hostaddr=7,id=hostdev3,bus=usb.0,port=2 -sandbox on,obsolete=deny,elevateprivileges=deny,spawn=deny,resourcecontrol=deny -msg timestamp=on 2019-05-11 10:05:31.106+0000: Domain id=2 is tainted: high-privileges 2019-05-11 10:05:31.106+0000: Domain id=2 is tainted: host-cpu 2019-05-11T10:05:31.161127Z qemu-system-x86_64: -chardev pty,id=charserial0: char device redirected to /dev/pts/0 (label charserial0) 2019-05-11T10:05:33.082654Z qemu-system-x86_64: -device vfio-pci,host=0b:00.0,id=hostdev0,bus=pci.0,addr=0x5,romfile=/mnt/disk1/isos/vbios/GTX1080.rom: Failed to mmap 0000:0b:00.0 BAR 3. Performance may be slow 2019-05-11T10:05:33.303036Z qemu-system-x86_64: vfio: Cannot reset device 0000:0d:00.3, depends on group 19 which is not owned. 2019-05-11T10:05:33.306922Z qemu-system-x86_64: vfio: Cannot reset device 0000:0d:00.3, depends on group 19 which is not owned. This one is the specific warning: 2019-05-11T10:05:33.082654Z qemu-system-x86_64: -device vfio-pci,host=0b:00.0,id=hostdev0,bus=pci.0,addr=0x5,romfile=/mnt/disk1/isos/vbios/GTX1080.rom: Failed to mmap 0000:0b:00.0 BAR 3. Performance may be slow XML of VM: 1 <?xml version='1.0' encoding='UTF-8'?> 2 <domain type='kvm'> 3 <name>Windows 10</name> 4 <uuid>a6892ae7-daa1-15b8-e162-4eef1bdf7548</uuid> 5 <metadata> 6 <vmtemplate xmlns="unraid" name="Windows 10" icon="windows.png" os="windows10"/> 7 </metadata> 8 <memory unit='KiB'>17301504</memory> 9 <currentMemory unit='KiB'>17301504</currentMemory> 10 <memoryBacking> 11 <nosharepages/> 12 </memoryBacking> 13 <vcpu placement='static'>12</vcpu> 14 <cputune> 15 <vcpupin vcpu='0' cpuset='2'/> 16 <vcpupin vcpu='1' cpuset='10'/> 17 <vcpupin vcpu='2' cpuset='3'/> 18 <vcpupin vcpu='3' cpuset='11'/> 19 <vcpupin vcpu='4' cpuset='4'/> 20 <vcpupin vcpu='5' cpuset='12'/> 21 <vcpupin vcpu='6' cpuset='5'/> 22 <vcpupin vcpu='7' cpuset='13'/> 23 <vcpupin vcpu='8' cpuset='6'/> 24 <vcpupin vcpu='9' cpuset='14'/> 25 <vcpupin vcpu='10' cpuset='7'/> 26 <vcpupin vcpu='11' cpuset='15'/> 27 </cputune> 28 <os> 29 <type arch='x86_64' machine='pc-i440fx-2.11'>hvm</type> 30 <loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd</loader> 31 <nvram>/etc/libvirt/qemu/nvram/a6892ae7-daa1-15b8-e162-4eef1bdf7548_VARS-pure-efi.fd</nvram> 32 </os> 33 <features> 34 <acpi/> 35 <apic/> 36 <hyperv> 37 <relaxed state='on'/> 38 <vapic state='on'/> 39 <spinlocks state='on' retries='8191'/> 40 <vendor_id state='on' value='none'/> 41 </hyperv> 42 </features> 43 <cpu mode='host-passthrough' check='none'> 44 <topology sockets='1' cores='12' threads='1'/> 45 </cpu> 46 <clock offset='localtime'> 47 <timer name='hypervclock' present='yes'/> 48 <timer name='hpet' present='no'/> 49 </clock> 50 <on_poweroff>destroy</on_poweroff> 51 <on_reboot>restart</on_reboot> 52 <on_crash>restart</on_crash> 53 <devices> 54 <emulator>/usr/local/sbin/qemu</emulator> 55 <disk type='file' device='disk'> 56 <driver name='qemu' type='raw' cache='writeback'/> 57 <source file='/mnt/user/backups/1stVM/Windows 10/vdisk1.img'/> 58 <target dev='hdc' bus='virtio'/> 59 <boot order='1'/> 60 <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/> 61 </disk> 62 <disk type='file' device='cdrom'> 63 <driver name='qemu' type='raw'/> 64 <source file='/mnt/user/isos/Windows10x64_0519.iso'/> 65 <target dev='hda' bus='ide'/> 66 <readonly/> 67 <boot order='2'/> 68 <address type='drive' controller='0' bus='0' target='0' unit='0'/> 69 </disk> 70 <disk type='file' device='cdrom'> 71 <driver name='qemu' type='raw'/> 72 <source file='/mnt/user/isos/virtio-win-0.1.141-1.iso'/> 73 <target dev='hdb' bus='ide'/> 74 <readonly/> 75 <address type='drive' controller='0' bus='0' target='0' unit='1'/> 76 </disk> 77 <controller type='usb' index='0' model='ich9-ehci1'> 78 <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x7'/> 79 </controller> 80 <controller type='usb' index='0' model='ich9-uhci1'> 81 <master startport='0'/> 82 <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0' multifunction='on'/> 83 </controller> 84 <controller type='usb' index='0' model='ich9-uhci2'> 85 <master startport='2'/> 86 <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x1'/> 87 </controller> 88 <controller type='usb' index='0' model='ich9-uhci3'> 89 <master startport='4'/> 90 <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x2'/> 91 </controller> 92 <controller type='pci' index='0' model='pci-root'/> 93 <controller type='ide' index='0'> 94 <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/> 95 </controller> 96 <controller type='virtio-serial' index='0'> 97 <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> 98 </controller> 99 <interface type='bridge'> 100 <mac address='52:54:00:8b:6d:12'/> 101 <source bridge='br1'/> 102 <model type='virtio'/> 103 <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/> 104 </interface> 105 <serial type='pty'> 106 <target type='isa-serial' port='0'> 107 <model name='isa-serial'/> 108 </target> 109 </serial> 110 <console type='pty'> 111 <target type='serial' port='0'/> 112 </console> 113 <channel type='unix'> 114 <target type='virtio' name='org.qemu.guest_agent.0'/> 115 <address type='virtio-serial' controller='0' bus='0' port='1'/> 116 </channel> 117 <input type='mouse' bus='ps2'/> 118 <input type='keyboard' bus='ps2'/> 119 <hostdev mode='subsystem' type='pci' managed='yes'> 120 <driver name='vfio'/> 121 <source> 122 <address domain='0x0000' bus='0x0b' slot='0x00' function='0x0'/> 123 </source> 124 <rom file='/mnt/user/isos/vbios/GTX1080.rom'/> 125 <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/> 126 </hostdev> 127 <hostdev mode='subsystem' type='pci' managed='yes'> 128 <driver name='vfio'/> 129 <source> 130 <address domain='0x0000' bus='0x0d' slot='0x00' function='0x3'/> 131 </source> 132 <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/> 133 </hostdev> 134 <hostdev mode='subsystem' type='usb' managed='no'> 135 <source> 136 <vendor id 137 <product id='0xc335'/> 138 </source> 139 <address type='usb' bus='0' port='1'/> 140 </hostdev> 141 <hostdev mode='subsystem' type='usb' managed='no'> 142 <source> 143 <vendor id='0x046d'/> 144 <product id='0xc539'/> 145 </source> 146 <address type='usb' bus='0' port='2'/> 147 </hostdev> 148 <memballoon model='none'/> 149 </devices> 150 </domain>

Hi bastl, I am not trying to passthrough the device in Group 19. I just checked the marks for Mouse&Keyboard. I tried even without them.

Hi, I am trying out unRAID on my Ryzen RIG, but have problems to get a VM working with proper GPU passthrough on any version above 6.5.3 . I tried it with the same .ROM-file as used on 6.5.3, also tried without it but no chance. The VM starts, screen gets black and stays black. If I force to stop VM and try to start again, I get "unknown pci header type '127' " The log is then showing a warning that group 19 ([1022:1455] 0d:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Device 1455) is not in ownership and that it will be slow.... Do I miss something which has to be done above this version? My Setup: Ryzen 1700 Crosshair VI X370 (latest BIOS) GTX1080 My System Devices: IOMMU group 0: [1022:1452] 00:01.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) PCIe Dummy Host Bridge IOMMU group 1: [1022:1453] 00:01.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) PCIe GPP Bridge IOMMU group 2: [1022:1453] 00:01.3 PCI bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) PCIe GPP Bridge IOMMU group 3: [1022:1452] 00:02.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) PCIe Dummy Host Bridge IOMMU group 4: [1022:1452] 00:03.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) PCIe Dummy Host Bridge IOMMU group 5: [1022:1453] 00:03.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) PCIe GPP Bridge IOMMU group 6: [1022:1452] 00:04.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) PCIe Dummy Host Bridge IOMMU group 7: [1022:1452] 00:07.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) PCIe Dummy Host Bridge IOMMU group 8: [1022:1454] 00:07.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Internal PCIe GPP Bridge 0 to Bus B IOMMU group 9: [1022:1452] 00:08.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) PCIe Dummy Host Bridge IOMMU group 10: [1022:1454] 00:08.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Internal PCIe GPP Bridge 0 to Bus B IOMMU group 11: [1022:790b] 00:14.0 SMBus: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller (rev 59) [1022:790e] 00:14.3 ISA bridge: Advanced Micro Devices, Inc. [AMD] FCH LPC Bridge (rev 51) IOMMU group 12: [1022:1460] 00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 0 [1022:1461] 00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 1 [1022:1462] 00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 2 [1022:1463] 00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 3 [1022:1464] 00:18.4 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 4 [1022:1465] 00:18.5 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 5 [1022:1466] 00:18.6 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 6 [1022:1467] 00:18.7 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 7 IOMMU group 13: [144d:a808] 01:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD Controller SM981/PM981 IOMMU group 14: [1022:43b9] 02:00.0 USB controller: Advanced Micro Devices, Inc. [AMD] Device 43b9 (rev 02) [1022:43b5] 02:00.1 SATA controller: Advanced Micro Devices, Inc. [AMD] Device 43b5 (rev 02) [1022:43b0] 02:00.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] Device 43b0 (rev 02) [1022:43b4] 03:00.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 300 Series Chipset PCIe Port (rev 02) [1022:43b4] 03:02.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 300 Series Chipset PCIe Port (rev 02) [1022:43b4] 03:03.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 300 Series Chipset PCIe Port (rev 02) [1022:43b4] 03:04.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 300 Series Chipset PCIe Port (rev 02) [1022:43b4] 03:05.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 300 Series Chipset PCIe Port (rev 02) [1022:43b4] 03:06.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 300 Series Chipset PCIe Port (rev 02) [1022:43b4] 03:07.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 300 Series Chipset PCIe Port (rev 02) [1b21:1343] 04:00.0 USB controller: ASMedia Technology Inc. ASM1143 USB 3.1 Host Controller [8086:1539] 05:00.0 Ethernet controller: Intel Corporation I211 Gigabit Network Connection (rev 03) [8086:24fd] 06:00.0 Network controller: Intel Corporation Wireless 8265 / 8275 (rev 78) [10ec:8168] 08:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 06) IOMMU group 15: [10de:1b80] 0b:00.0 VGA compatible controller: NVIDIA Corporation GP104 [GeForce GTX 1080] (rev a1) [10de:10f0] 0b:00.1 Audio device: NVIDIA Corporation GP104 High Definition Audio Controller (rev a1) IOMMU group 16: [1022:145a] 0c:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Device 145a IOMMU group 17: [1022:1456] 0c:00.2 Encryption controller: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Platform Security Processor IOMMU group 18: [1022:145c] 0c:00.3 USB controller: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) USB 3.0 Host Controller IOMMU group 19: [1022:1455] 0d:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Device 1455 IOMMU group 20: [1022:7901] 0d:00.2 SATA controller: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] (rev 51) IOMMU group 21: [1022:1457] 0d:00.3 Audio device: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) HD Audio Controller USB Devices: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 004: ID 0c70:f001 MCT Elektronikladen Bus 001 Device 005: ID 046d:c335 Logitech, Inc. G910 Orion Spectrum Mechanical Keyboard Bus 001 Device 006: ID 058f:6387 Alcor Micro Corp. Flash Drive Bus 001 Device 007: ID 046d:c539 Logitech, Inc. Bus 001 Device 008: ID 041e:322c Creative Technology, Ltd Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub