fabiosun

47:00.3 interferes with audio but I think also without you loose some usb3 ports and maybe 4 internal usb2 in 10.15.5 passing all usb controllerS does not affect audio for me but I have understood that for you is different

Are you sure about this? 23:00.4 in my case is Matisse audio 46:00.1 and 46:00.3 are many usb I think internal 3.2 slot and a bunch of rear usb

@Driftwood47:00.3? Don’t use it?

@Driftwoodare you in 10.15.5?

Aggiornato senza problemi... 🙂

@iGPU it is very weird all things have been happened with 2 different motherboard and different linux distros I can't say what you can do more to debug.. I can only say that in my experiences (with all bios available on my motherboard (I have tested all during this experience)) I have no difference behaviour IOMMU group are always the same as it is always the same group separation.. so it is difficult for me to understand

yes i did in this way i have Proxmox on sata ssd disk and sata was not passable easily connect the same disk on asmedia usb all went fine

No, for me no Maybe we will see soon some improvement if Linus Torvald has a trx40 PC as we can see from link posted before by IGPU If your system is stable why do you want to change it? Then, if you did all correctly you can install in about 5 minute Proxmox on USB (I am saying again to use Asmedia 3.2 type back port) And then copy on new installation all files you modify in your actual (and working) Proxmox to summarise: 1)backup your VM config 2)backup kvm.conf, grub, vfio.conf, blacklist.conf and modules 3) backup your modified deb files and hook script if you use them 4) disconnect your proxmox disk and install on a new usb one (I use an external case for a Samsung 840 pro ssd sized 240 Gb) 5) install proxmox 6) copy all your previously backupped files and launch all terminal command you need to reconfigure your new proxmox installation If you use a passed disk to boot in osx that's all if you use some vm disk, maybe you have to recreate efi and you have to add a step after my point 3) as 3bis) backup all your vm disk files more or less these could be a way you can proceed..and in the worst case you have also your previous Proxmox disk you can reconnect back 🙂 I have not studied at all some properties of web interface , I think is also possible to transfer all using internal web interface tools..

OT (about Unraid) to test I have built an Unraid test OSX VM, I did to verify if in there I have a better HighSierra support..it is not 🙂 below IOMMU groups seen in Unraid and others datas: PCI Devices and IOMMU Groups IOMMU group 0: [1022:1482] 00:01.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge IOMMU group 1: [1022:1483] 00:01.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse GPP Bridge IOMMU group 2: [1022:1483] 00:01.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse GPP Bridge IOMMU group 3: [1022:1482] 00:02.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge IOMMU group 4: [1022:1482] 00:03.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge IOMMU group 5: [1022:1482] 00:04.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge IOMMU group 6: [1022:1482] 00:05.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge IOMMU group 7: [1022:1482] 00:07.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge IOMMU group 8: [1022:1484] 00:07.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Internal PCIe GPP Bridge 0 to bus[E:B] IOMMU group 9: [1022:1482] 00:08.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge IOMMU group 10: [1022:1484] 00:08.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Internal PCIe GPP Bridge 0 to bus[E:B] IOMMU group 11: [1022:790b] 00:14.0 SMBus: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller (rev 61) [1022:790e] 00:14.3 ISA bridge: Advanced Micro Devices, Inc. [AMD] FCH LPC Bridge (rev 51) IOMMU group 12: [1022:1490] 00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship Device 24; Function 0 [1022:1491] 00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship Device 24; Function 1 [1022:1492] 00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship Device 24; Function 2 [1022:1493] 00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship Device 24; Function 3 [1022:1494] 00:18.4 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship Device 24; Function 4 [1022:1495] 00:18.5 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship Device 24; Function 5 [1022:1496] 00:18.6 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship Device 24; Function 6 [1022:1497] 00:18.7 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship Device 24; Function 7 IOMMU group 13: [144d:a804] 01:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD Controller SM961/PM961 IOMMU group 14: [1987:5012] 02:00.0 Non-Volatile memory controller: Phison Electronics Corporation E12 NVMe Controller (rev 01) IOMMU group 15: [1022:148a] 03:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Function IOMMU group 16: [1022:1485] 04:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Reserved SPP IOMMU group 17: [1022:148c] 04:00.3 USB controller: Advanced Micro Devices, Inc. [AMD] Starship USB 3.0 Host Controller IOMMU group 18: [1022:1482] 20:01.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge IOMMU group 19: [1022:1482] 20:02.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge IOMMU group 20: [1022:1482] 20:03.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge IOMMU group 21: [1022:1483] 20:03.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse GPP Bridge IOMMU group 22: [1022:1482] 20:04.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge IOMMU group 23: [1022:1482] 20:05.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge IOMMU group 24: [1022:1482] 20:07.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge IOMMU group 25: [1022:1484] 20:07.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Internal PCIe GPP Bridge 0 to bus[E:B] IOMMU group 26: [1022:1482] 20:08.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge IOMMU group 27: [1022:1484] 20:08.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Internal PCIe GPP Bridge 0 to bus[E:B] IOMMU group 28: [10de:1b02] 21:00.0 VGA compatible controller: NVIDIA Corporation GP102 [TITAN Xp] (rev a1) [10de:10ef] 21:00.1 Audio device: NVIDIA Corporation GP102 HDMI Audio Controller (rev a1) IOMMU group 29: [1022:148a] 22:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Function IOMMU group 30: [1022:1485] 23:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Reserved SPP IOMMU group 31: [1022:1486] 23:00.1 Encryption controller: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Cryptographic Coprocessor PSPCPP IOMMU group 32: [1022:148c] 23:00.3 USB controller: Advanced Micro Devices, Inc. [AMD] Starship USB 3.0 Host Controller IOMMU group 33: [1022:1487] 23:00.4 Audio device: Advanced Micro Devices, Inc. [AMD] Starship/Matisse HD Audio Controller IOMMU group 34: [1022:1482] 40:01.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge IOMMU group 35: [1022:1483] 40:01.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse GPP Bridge IOMMU group 36: [1022:1483] 40:01.3 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse GPP Bridge IOMMU group 37: [1022:1482] 40:02.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge IOMMU group 38: [1022:1482] 40:03.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge IOMMU group 39: [1022:1482] 40:04.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge IOMMU group 40: [1022:1482] 40:05.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge IOMMU group 41: [1022:1482] 40:07.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge IOMMU group 42: [1022:1484] 40:07.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Internal PCIe GPP Bridge 0 to bus[E:B] IOMMU group 43: [1022:1482] 40:08.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge IOMMU group 44: [1022:1484] 40:08.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Internal PCIe GPP Bridge 0 to bus[E:B] IOMMU group 45: [1022:57ad] 41:00.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Matisse Switch Upstream IOMMU group 46: [1022:57a3] 42:02.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Matisse PCIe GPP Bridge IOMMU group 47: [1022:57a3] 42:04.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Matisse PCIe GPP Bridge IOMMU group 48: [1022:57a3] 42:05.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Matisse PCIe GPP Bridge IOMMU group 49: [1022:57a4] 42:08.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Matisse PCIe GPP Bridge [1022:1485] 46:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Reserved SPP [1022:149c] 46:00.1 USB controller: Advanced Micro Devices, Inc. [AMD] Matisse USB 3.0 Host Controller [1022:149c] 46:00.3 USB controller: Advanced Micro Devices, Inc. [AMD] Matisse USB 3.0 Host Controller IOMMU group 50: [1022:57a4] 42:09.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Matisse PCIe GPP Bridge [1022:7901] 47:00.0 SATA controller: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] (rev 51) IOMMU group 51: [1022:57a4] 42:0a.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Matisse PCIe GPP Bridge [1022:7901] 48:00.0 SATA controller: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] (rev 51) IOMMU group 52: [1b21:3242] 43:00.0 USB controller: ASMedia Technology Inc. Device 3242 IOMMU group 53: [8086:1539] 44:00.0 Ethernet controller: Intel Corporation I211 Gigabit Network Connection (rev 03) IOMMU group 54: [8086:1539] 45:00.0 Ethernet controller: Intel Corporation I211 Gigabit Network Connection (rev 03) IOMMU group 55: [1d6a:07b1] 49:00.0 Ethernet controller: Aquantia Corp. AQC107 NBase-T/IEEE 802.3bz Ethernet Controller [AQtion] (rev 02) IOMMU group 56: [1022:148a] 4a:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Function IOMMU group 57: [1022:1485] 4b:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Reserved SPP IOMMU group 58: [1022:1482] 60:01.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge IOMMU group 59: [1022:1482] 60:02.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge IOMMU group 60: [1022:1482] 60:03.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge IOMMU group 61: [1022:1482] 60:04.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge IOMMU group 62: [1022:1482] 60:05.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge IOMMU group 63: [1022:1482] 60:07.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge IOMMU group 64: [1022:1484] 60:07.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Internal PCIe GPP Bridge 0 to bus[E:B] IOMMU group 65: [1022:1482] 60:08.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge IOMMU group 66: [1022:1484] 60:08.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Internal PCIe GPP Bridge 0 to bus[E:B] IOMMU group 67: [1022:148a] 61:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Function IOMMU group 68: [1022:1485] 62:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Reserved SPP CPU Thread Pairings Pair 1: cpu 0 / cpu 32 Pair 2: cpu 1 / cpu 33 Pair 3: cpu 2 / cpu 34 Pair 4: cpu 3 / cpu 35 Pair 5: cpu 4 / cpu 36 Pair 6: cpu 5 / cpu 37 Pair 7: cpu 6 / cpu 38 Pair 8: cpu 7 / cpu 39 Pair 9: cpu 8 / cpu 40 Pair 10: cpu 9 / cpu 41 Pair 11: cpu 10 / cpu 42 Pair 12: cpu 11 / cpu 43 Pair 13: cpu 12 / cpu 44 Pair 14: cpu 13 / cpu 45 Pair 15: cpu 14 / cpu 46 Pair 16: cpu 15 / cpu 47 Pair 17: cpu 16 / cpu 48 Pair 18: cpu 17 / cpu 49 Pair 19: cpu 18 / cpu 50 Pair 20: cpu 19 / cpu 51 Pair 21: cpu 20 / cpu 52 Pair 22: cpu 21 / cpu 53 Pair 23: cpu 22 / cpu 54 Pair 24: cpu 23 / cpu 55 Pair 25: cpu 24 / cpu 56 Pair 26: cpu 25 / cpu 57 Pair 27: cpu 26 / cpu 58 Pair 28: cpu 27 / cpu 59 Pair 29: cpu 28 / cpu 60 Pair 30: cpu 29 / cpu 61 Pair 31: cpu 30 / cpu 62 Pair 32: cpu 31 / cpu 63 USB Devices Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub 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 Bus 006 Device 002: ID 2109:0715 VIA Labs, Inc. VLI Product String Bus 007 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 007 Device 002: ID 046d:c050 Logitech, Inc. RX 250 Optical Mouse Bus 007 Device 003: ID 04d9:1702 Holtek Semiconductor, Inc. Keyboard LKS02 Bus 007 Device 004: ID 0c76:161f JMTek, LLC. USB PnP Audio Device Bus 007 Device 005: ID 0db0:543d Micro Star International USB Audio Bus 007 Device 006: ID 1462:7c60 Micro Star International MYSTIC LIGHT Bus 008 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 009 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 009 Device 002: ID 13fe:4200 Kingston Technology Company Inc. USB DISK 2.0 Bus 009 Device 003: ID 05e3:0608 Genesys Logic, Inc. Hub Bus 010 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub SCSI Devices [0:0:0:0] disk Samsung SSD 840 PRO DXM0 /dev/sda 256GB [1:0:0:0] cd/dvd USB DISK 2.0 PMAP /dev/sr0 - [1:0:0:1] disk USB DISK 2.0 PMAP /dev/sdb 1.96GB [2:0:0:0] cd/dvd PIONEER BD-RW BDR-207M 1.35 /dev/sr1 - [3:0:0:0] disk ATA HGST HTS545050A7 ACA0 /dev/sdc 500GB [4:0:0:0] disk ATA ST6000VX0023-2EF SC60 /dev/sdd 6.00TB [5:0:0:0] disk ATA ST6000VX0023-2EF SC60 /dev/sde 6.00TB [6:0:0:0] disk ATA ST10000VX0004-1Z AV01 /dev/sdf 10.0TB [7:0:0:0] disk ATA ST10000VX0004-1Z AV01 /dev/sdg 10.0TB [N:0:2:1] disk Samsung SSD 960 PRO 1TB__1 /dev/nvme0n1 1.02TB [N:1:1:1] disk Sabrent__1 /dev/nvme1n1 1.02TB I stay in proxmox 🙂

No

and do you think a 710 gt could remote well that 8k display? magaraaaa 🙂 PS the problem is also we are using a complex system to boot..and adding a third gfx could be problematic...

for me Catalina is working well as high sierra if I consider USB job I pass all controllers less audio controller (xx:00.4) In Catalina usb is threated differently and USB drivers work as they do in a window VM (as bare metal), in High Sierra driver is old and for now I can use only USB 2.0 device. for both no lag at all Pay attention (for lag stuff) if you have some WIFI/BT which need usb power)..I haven't ..but it is problematic if you have

@Driftwood Apple has worked for me 🙂 catalina 10.15.5 solved my audio problem and then I have said to Pavo this and also him reached my same situation with his trx40 system (audio perfect but jack detection problematic) Now I think he is trying with Unraid and see if there could be the same or better. For now I stay in Proxmox. system is production ready and no so much time to invest to learn Unraid

Yes in that line new proxmox release does not need anymore of mce=off

Also I do not use actual patch you can find in pavo GitHub but older ones. I think he is doing multi platform experiment with this patches to try to solve Problem for other platform. I think also @Pavo could confirm this as he did in private few hour ago @iGPUif you have another working Linux you can compile by yourself I prefer @Pavogive you clear instruction because he has helped me to understand how. to all audio is working and the only problem now is audio jack Detection. by the way now i think pavo had some success we audio in unraid. Maybe it could be useful also in proxmox understand well how Unraid works

@Driftwood you are not informed well😀 Audio is working well in latest Catalina and it is not flr patch related

1) no command line does not work . It must be on kernel 2) i asked to pavo to compile for me a kernel with 148c because we (all trx40 users) need of this id i do not know if actual patches in his github are the same he did for me on my request time ago

I would check your mb manual..because it seems vfio plugin is wrong no experience with unraid but for me is weird

On image you write asmedia 48:00.1 and this for me is not so

Thanks @iGPU it is similar to mine 04:00.3 25:00.3 could be passed with flr patch (148c) 48:00.1 and 48:00.3 pass as is without patch 44 is asmedia..i do not pass it because i have proxmox on it i do not consider any additional device you can have but msi creator has pretty similar group also @pavo has one and he is achieving the same my result

@iGPU could you post lspci -nnk output of this msi board? I would like to check because iommu seems to be weird

Hi, maybe I am missing something...are you sure of this picture above? In your pdf on your GitHub there are differences.. 🙂and as it is should not boot (gfx is not there) with our trx40 is better to pass entire usb controllers and not single device..single device may loose many functionality

This is my last schema. I can pass more stuff but all usb in my motherboard are owned by 46:00 controller...ah also audio is in there VM OS system limit USB3 detection (High Sierra) Catalina and Windows 64 have a better USB management (their drivers allow to see USB 3 devices if connected . So to a clean installation in my MSI TRX40 Pro 10G I do not use any FLR patch (no need to passthrough 23:00.3, 4:00.3 USB Controllers or 23:00.4 audio controller it is also mandatory to pass 4:00.3 and 23:00.3 (FLR Patch 148c) (do not pass 23:00:4 audio controller) All I need is 46:00, 4:00.3 and 23:00.3 controllers which I can passthrough in two different way: Hostpci5: 46:00 or hostpci6: 46:00.1 hostpci7: 46:00.3 then hostpci7: 04:00.3 hostpci7: 23:00.3 I think also for you should be the same (you have also to find your main USB controller and your exact groups). Interesting is also to check this schematic picture, inside USB/audio/chipset connections with AMD CPU:

new agesa 🙂