Clientel

Members
  • Posts

    2
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

Clientel's Achievements

Noob

Noob (1/14)

0

Reputation

  1. Hi All, 1. Just wondering if it is possible to use the bind function (BIND=XXXX:XX:XX.X|XXXX:XXX) to force unraid not to use a specific bus line so that it can be bound to a chosen VM. 2. The IOMMU group for the USB ports is Group 4. I'm trying to forcefully bind the Oculus Quest Link USB to a VM since whenever I use the checkbox method it works for a brief time, then gets disabled and/or deselected from the VM. My motherboard is a Gigabyte Aorus Z390 which only has one USB controller. I'm not sure how it's even possible that I can divide multiple USB mice/keyboards across 2 or more unique VMs but it does work for whatever reason even though they use the same IOMMU group. Unfortunately my goal, which is to connect multiple VR headsets like the oculus quest cannot be done via this method from what I have tried so far. The specific bus line is below (note I also have a Oculus Rift S on the system): Bus 001 Device 024: ID 2833:0182 Oculus Quest 2 The VM xml does show the quest attached: <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x2833'/> <product id='0x0182'/> <address bus='1' device='20'/> </source> <alias name='hostdev7'/> <address type='usb' bus='0' port='4'/> </hostdev> 3. I'm trying this since the new Sonnet USB controllers (USB3-PRO-4P10-E or USB3C-4PM-E) with Type C or Type A connections doesn't work in Unraid 6.9. I was hoping the hardware/software links of the new card would resemble the old Sonnet USB3-PRO-4PM-E with 4 unique FL1100 controllers which many have used and does work, however the new one just doesn't work the same. Maybe something to do with the Asmedia controllers and Pericom Bridge configuration, but I'm leaning towards the programming end from Unraid. If anyone knows why I am able to passthrough and bind these successfully yet not have the USB ports recognise any and all types of devices plugged in please let me know. I have manually installed Sonnet's specific drivers on the VM since by default it uses one of Microsofts generic ones for both the Controller and Hub but this still failed to get the ports functioning. You can see the full IOMMU list below with groups 22-26 representing the Sonnet Bridge and Controllers. Out of interest does anyone know what the graphics card controllers are? There are no visible USB-C ports on the RTX 2070 Super cards I'm running. IOMMU group 16:[10de:1ad9] 01:00.3 Serial bus controller [0c80]: NVIDIA Corporation TU104 USB Type-C UCSI Controller (rev a1) IOMMU group 20:[10de:1ad9] 02:00.3 Serial bus controller [0c80]: NVIDIA Corporation TU104 USB Type-C UCSI Controller (rev a1) 4. Another frustration I've had with Unraid 6.91 is the lack of update to the VM XML when usb devices are unplugging and/or changed. I shouldn't have to manually enter the XML everytime I unplug a device that is passed through to a given VM to stop VM creation and Vendor issues. IOMMU group 0:[8086:3e30] 00:00.0 Host bridge: Intel Corporation 8th/9th Gen Core 8-core Desktop Processor Host Bridge/DRAM Registers [Coffee Lake S] (rev 0a) IOMMU group 1:[8086:1901] 00:01.0 PCI bridge: Intel Corporation 6th-10th Gen Core Processor PCIe Controller (x16) (rev 0a) IOMMU group 2:[8086:1905] 00:01.1 PCI bridge: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor PCIe Controller (x8) (rev 0a) IOMMU group 3:[8086:a379] 00:12.0 Signal processing controller: Intel Corporation Cannon Lake PCH Thermal Controller (rev 10) IOMMU group 4:[8086:a36d] 00:14.0 USB controller: Intel Corporation Cannon Lake PCH USB 3.1 xHCI Host Controller (rev 10) Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 2833:2052 Oculus VR Rift S USB Hub Bus 001 Device 004: ID 2833:0051 Oculus VR Rift S Bus 001 Device 005: ID 05e3:0608 Genesys Logic, Inc. Hub Bus 001 Device 006: ID 048d:8297 Integrated Technology Express, Inc. ITE Device(8595) Bus 001 Device 007: ID 18a5:0302 Verbatim, Ltd Flash Drive Bus 001 Device 008: ID 05e3:0608 Genesys Logic, Inc. Hub Bus 001 Device 009: ID 045e:0745 Microsoft Corp. Nano Transceiver v1.0 for Bluetooth Bus 001 Device 010: ID 8087:0aaa Intel Corp. Bus 001 Device 011: ID 045e:07f8 Microsoft Corp. Wired Keyboard 600 (model 1576) Bus 001 Device 012: ID 0781:5591 SanDisk Corp. Ultra Flair Bus 001 Device 013: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 024: ID 2833:0182 Oculus Quest 2 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 002 Device 002: ID 2833:2051 Oculus VR Rift S USB Hub [8086:a36f] 00:14.2 RAM memory: Intel Corporation Cannon Lake PCH Shared SRAM (rev 10) IOMMU group 5:[8086:a370] 00:14.3 Network controller: Intel Corporation Wireless-AC 9560 [Jefferson Peak] (rev 10) IOMMU group 6:[8086:a360] 00:16.0 Communication controller: Intel Corporation Cannon Lake PCH HECI Controller (rev 10) IOMMU group 7:[8086:a352] 00:17.0 SATA controller: Intel Corporation Cannon Lake PCH SATA AHCI Controller (rev 10) [2:0:0:0] disk ATA Samsung SSD 860 3B6Q /dev/sdc 1.00TB IOMMU group 8:[8086:a340] 00:1b.0 PCI bridge: Intel Corporation Cannon Lake PCH PCI Express Root Port #17 (rev f0) IOMMU group 9:[8086:a32c] 00:1b.4 PCI bridge: Intel Corporation Cannon Lake PCH PCI Express Root Port #21 (rev f0) IOMMU group 10:[8086:a338] 00:1c.0 PCI bridge: Intel Corporation Cannon Lake PCH PCI Express Root Port #1 (rev f0) IOMMU group 11:[8086:a330] 00:1d.0 PCI bridge: Intel Corporation Cannon Lake PCH PCI Express Root Port #9 (rev f0) IOMMU group 12:[8086:a305] 00:1f.0 ISA bridge: Intel Corporation Z390 Chipset LPC/eSPI Controller (rev 10) [8086:a348] 00:1f.3 Audio device: Intel Corporation Cannon Lake PCH cAVS (rev 10) [8086:a323] 00:1f.4 SMBus: Intel Corporation Cannon Lake PCH SMBus Controller (rev 10) [8086:a324] 00:1f.5 Serial bus controller [0c80]: Intel Corporation Cannon Lake PCH SPI Controller (rev 10) [8086:15bc] 00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection (7) I219-V (rev 10) IOMMU group 13:[10de:1e84] 01:00.0 VGA compatible controller: NVIDIA Corporation TU104 [GeForce RTX 2070 SUPER] (rev a1) IOMMU group 14:[10de:10f8] 01:00.1 Audio device: NVIDIA Corporation TU104 HD Audio Controller (rev a1) IOMMU group 15:[10de:1ad8] 01:00.2 USB controller: NVIDIA Corporation TU104 USB 3.1 Host Controller (rev a1) 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 IOMMU group 16:[10de:1ad9] 01:00.3 Serial bus controller [0c80]: NVIDIA Corporation TU104 USB Type-C UCSI Controller (rev a1) IOMMU group 17:[10de:1e84] 02:00.0 VGA compatible controller: NVIDIA Corporation TU104 [GeForce RTX 2070 SUPER] (rev a1) IOMMU group 18:[10de:10f8] 02:00.1 Audio device: NVIDIA Corporation TU104 HD Audio Controller (rev a1) IOMMU group 19:[10de:1ad8] 02:00.2 USB controller: NVIDIA Corporation TU104 USB 3.1 Host Controller (rev a1) 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 IOMMU group 20:[10de:1ad9] 02:00.3 Serial bus controller [0c80]: NVIDIA Corporation TU104 USB Type-C UCSI Controller (rev a1) IOMMU group 21:[144d:a808] 03:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD Controller SM981/PM981/PM983 [N:0:4:1] disk Samsung SSD 970 PRO 1TB__1 /dev/nvme0n1 1.02TB IOMMU group 22:[12d8:2308] 04:00.0 PCI bridge: Pericom Semiconductor Device 2308 IOMMU group 23:[12d8:2308] 05:01.0 PCI bridge: Pericom Semiconductor Device 2308 IOMMU group 24:[12d8:2308] 05:02.0 PCI bridge: Pericom Semiconductor Device 2308 IOMMU group 25:[1b21:2142] 06:00.0 USB controller: ASMedia Technology Inc. ASM2142 USB 3.1 Host Controller This controller is bound to vfio, connected USB devices are not visible. IOMMU group 26:[1b21:2142] 07:00.0 USB controller: ASMedia Technology Inc. ASM2142 USB 3.1 Host Controller This controller is bound to vfio, connected USB devices are not visible. IOMMU group 27:[c0a9:540a] 09:00.0 Non-Volatile memory controller: Micron/Crucial Technology Device 540a (rev 01) [N:1:1:1] disk CT1000P2SSD8__1 /dev/nvme1n1 1.00TB
  2. According to one unraid user who reviewed on Startech directly, he has gotten 4 ports working independently across 4 different VMs on 24/02/21: https://www.startech.com/en-au/cards-adapters/pexusb3s44v There is further discussion on the thread below: https://forums.unraid.net/topic/58843-functional-multi-controller-usb-pci-e-adapter/page/3/ ^^ Note there are different revisions of the card which may impact correct passthrough: "PI40202-6X2B -> Recognized by Windows 10 guest, works great PI40202-7X2B -> Recognized by Windows 10 guest, throws code 10"