Leaderboard

beh allora ti assicuro che avrai un sacco di cose con cui divertirti 😁

guarda che chi fa overclock spinto, il consiglio è sempre quello di usare 2 banchi ram; se ricordo bene, 1 e 2 2 e 4 sono quelli più performanti poi non vedo il motivo di autocastrarsi con la frequenza delle RAM, anche ammettendo che macOS non le sfrutti (io non ne sono tanto convinto, le impostazioni le da il BIOS e non l'OS) e vista la irrisoria differenza di costi, RAM a 3200MHz è il giusto equilibrio; su sistemi intel oltre, le mobo che lo permettono, e le serie Z lo permettono, è comunque overclock della RAM

molta fuffa, per piattaforma intel la frequenza ad hoc, parer mio, è 3200MHz, poi vedi la latenza che ha e i costi per quello reperibile sul mercato... se vuoi o meno RAM argb o che ti interessa

Il secondo monitor già non compare più, e la scheda madre ha solo una uscita quindi ora funziona tutto

welcome here @boolean 🙂 you have to lock in your bios your great cpu @32 cores 32 threads or 64 core without SMT (better for performance) this is an OSX limits

however seems weird that skipped because values are pretty the same if I see well

check if your mmio are changed..if not it is fine 😛

could you can mount your GPU in one of these computers which work with that monitor? problem is not in your new rig I think

to do additional steps..you have to post your IOREG as I said above..from there is possible to see many things to optimize your system 😉

11:361 00:002 OCABC: MMIO devirt 0xE2100000 (0x81 pages, 0x8000000000000001) skip 1 11:364 00:003 OCABC: MMIO devirt 0xE3180000 (0x81 pages, 0x8000000000000001) skip 1 11:367 00:002 OCABC: MMIO devirt 0xEF100000 (0x181 pages, 0x8000000000000001) skip 1 11:370 00:003 OCABC: MMIO devirt 0xFA180000 (0x81 pages, 0x8000000000000001) skip 1 11:373 00:002 OCABC: MMIO devirt 0xFA300000 (0x100 pages, 0x8000000000000001) skip 1 11:376 00:002 OCABC: MMIO devirt 0xFEA00000 (0x100 pages, 0x8000000000000001) skip 1 11:379 00:002 OCABC: MMIO devirt 0xFEC00000 (0x1 pages, 0x8000000000000001) skip 1 11:382 00:003 OCABC: MMIO devirt 0xFEC10000 (0x1 pages, 0x8000000000000001) skip 1 11:385 00:002 OCABC: MMIO devirt 0xFED00000 (0x1 pages, 0x8000000000000001) skip 1 11:388 00:002 OCABC: MMIO devirt 0xFED40000 (0x5 pages, 0x8000000000000001) skip 1 11:391 00:002 OCABC: MMIO devirt 0xFED80000 (0x10 pages, 0x8000000000000001) skip 1 11:394 00:002 OCABC: MMIO devirt 0xFEDC2000 (0xE pages, 0x8000000000000001) skip 1 11:397 00:002 OCABC: MMIO devirt 0xFEDD4000 (0x2 pages, 0x8000000000000001) skip 1 11:400 00:002 OCABC: MMIO devirt 0xFEE00000 (0x100 pages, 0x8000000000000001) skip 1 11:403 00:003 OCABC: MMIO devirt 0xFF000000 (0x1000 pages, 0x8000000000000001) skip 1 11:406 00:003 OCABC: MMIO devirt 0x1040000000 (0x10400 pages, 0x8000000000000001) skip 0 11:409 00:002 OCABC: MMIO devirt 0x6EE0000000 (0x10400 pages, 0x8000000000000001) skip 0 11:412 00:002 OCABC: MMIO devirt 0x6F10000000 (0x10400 pages, 0x8000000000000001) skip 0 11:415 00:003 OCABC: MMIO devirt 0xCDB0000000 (0x10400 pages, 0x8000000000000001) skip 0 now these are like they should be Are you sure you have not touched anything in your bios settings? CSM is on or off? Before third MMIO was different and your system started check this and do not touch anything 😉

config.plist.zip before booting with this one delete open core txt log (all) then boot two times with this and post config.plist and two opencore txt debug files Do not touch anything else please

11:312 00:001 OCABC: MMIO devirt 0xEF100000 (0x181 pages, 0x8000000000000001) skip 0 NO please..let decide how to start your system (bios setting , and card in slot on it) then put here a config which boots then we will try again 🙂 last chance for you if things will change again (for my help I mean) 🙂

check this and latest you have posted 0xEF1 is not here so what does it means? you have changed something in BIOS o in your pci slot position... and in this way it is not possible to help sorry ;(

see first skip 0 ? yesterday it was to 1 🙂 check latest result we have yesterday then, for shutdown and restart you should find proper combinations I think with 1 there it could works also for you

which config are you using? your debug posted is different from what we have done yesterday check well first you have to solve your black screen (randomly happen so I thing is not config.plist related) then you can optimize your ACPI could differ from mine or from other users also with the same your motherboard So, SSDT from others have to be tuned with your system usually you have to start with a clean system and save from it an IOREG then skilled people could help to produce correct SSDT for your system

also previous debug is weird compared from the job we did yesterday you do not have to mix different MMIO from different motherboard or user bios config from this result you have to start

@infodo not panic..you not OS I mean 🙂 in my latest config you have proper MMIO list calculated for you by me reading your log If you change bios parameter MMIO list could change (parameter like CSM/UEFI or 4G if you have) Have you tested with another cable? have you tested with a HDMI/DP adaptor if you do not have another Monitor to test? Monitor I see in your video seems pretty old.. in this latest your debug all MMIO are skipped to 0 not good for future full functionality of your system (Shutdown/Sleep wake and so on)

I think it is a cable or monitor problem..but from here I can't say more now you have a pretty basic configured system, you can try to run some benchmark aqs Cinebench 15 and cinebench23 also luxmark3.1 give a great stress test on gpu then..you can try to add stuff you need (wifi? ethernet kext for your Gigabyte and so on...

config.plist.zip I hope this solve your freeze 🙂

ah maybe I have understood.. I am waiting for your latest try

change port of your gpu and yes post always bootleg.txt thank you

It is weird in my opinion how it is possible our motherboard act in so different ways in my case vfio.conf it is not usefull at all maybe it is about Agesa difference in our mb? Or for what? i have tested also old agesa but for me vfio.conf it is not important at all. @iGPU about pci bridge maybe we could find a way to ask on proxmox forum how qemu pci bridge virtual device interact wth real pci bridge and if they interact how to Add on that file missing ones

I would like suggest to all of you to try do run an ACPIDUMP in this way: download acpidump.efi and put in OC/tools (thanks @Gengik84for this) https://www.macos86.it/topic/1560-acpi-come-estrarle/?tab=comments#comment-40152 https://www.macos86.it/applications/core/interface/file/attachment.php?id=6306 Boot directly with your OSX disk (with opencore EFI and not via Linux) in my case my NVME Sabrent obviously you can access only to opencore shell try to reach your EFI folder (in my case FS1:/EFI/OC/Tools and then run: acpidump.efi boot in your system and mount your EFI backup this data then start proxmox and do the same inside proxmox/OSX/opencore you will see how VM interact with our original ACPI... Maybe some of you have the skills to understand better than me and use it to improve our VM 😉

here we go: lspci -nnk output before vm start taken with photo on my AMD rig lspci -nnk output taken inside my VM OSX via screen grab of shell (web interface) vfio.conf blacklist.conf I use my IOOMU group separations: root@pve:~# ./grp.sh IOMMU Group 0: 00:01.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge [1022:1482] IOMMU Group 1: 00:01.1 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse GPP Bridge [1022:1483] IOMMU Group 10: 00:08.1 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Internal PCIe GPP Bridge 0 to bus[E:B] [1022:1484] IOMMU Group 11: 00:14.0 SMBus [0c05]: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller [1022:790b] (rev 61) 00:14.3 ISA bridge [0601]: Advanced Micro Devices, Inc. [AMD] FCH LPC Bridge [1022:790e] (rev 51) IOMMU Group 12: 00:18.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship Device 24; Function 0 [1022:1490] 00:18.1 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship Device 24; Function 1 [1022:1491] 00:18.2 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship Device 24; Function 2 [1022:1492] 00:18.3 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship Device 24; Function 3 [1022:1493] 00:18.4 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship Device 24; Function 4 [1022:1494] 00:18.5 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship Device 24; Function 5 [1022:1495] 00:18.6 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship Device 24; Function 6 [1022:1496] 00:18.7 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship Device 24; Function 7 [1022:1497] IOMMU Group 13: 01:00.0 Non-Volatile memory controller [0108]: Samsung Electronics Co Ltd NVMe SSD Controller SM961/PM961 [144d:a804] IOMMU Group 14: 02:00.0 Non-Volatile memory controller [0108]: Phison Electronics Corporation E12 NVMe Controller [1987:5012] (rev 01) IOMMU Group 15: 03:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Function [1022:148a] IOMMU Group 16: 04:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Reserved SPP [1022:1485] IOMMU Group 17: 04:00.3 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] Starship USB 3.0 Host Controller [1022:148c] IOMMU Group 18: 20:01.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge [1022:1482] IOMMU Group 19: 20:02.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge [1022:1482] IOMMU Group 2: 00:01.2 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse GPP Bridge [1022:1483] IOMMU Group 20: 20:03.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge [1022:1482] IOMMU Group 21: 20:03.1 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse GPP Bridge [1022:1483] IOMMU Group 22: 20:04.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge [1022:1482] IOMMU Group 23: 20:05.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge [1022:1482] IOMMU Group 24: 20:07.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge [1022:1482] IOMMU Group 25: 20:07.1 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Internal PCIe GPP Bridge 0 to bus[E:B] [1022:1484] IOMMU Group 26: 20:08.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge [1022:1482] IOMMU Group 27: 20:08.1 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Internal PCIe GPP Bridge 0 to bus[E:B] [1022:1484] IOMMU Group 28: 21:00.0 VGA compatible controller [0300]: NVIDIA Corporation GP102 [TITAN Xp] [10de:1b02] (rev a1) 21:00.1 Audio device [0403]: NVIDIA Corporation GP102 HDMI Audio Controller [10de:10ef] (rev a1) IOMMU Group 29: 22:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Function [1022:148a] IOMMU Group 3: 00:02.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge [1022:1482] IOMMU Group 30: 23:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Reserved SPP [1022:1485] IOMMU Group 31: 23:00.1 Encryption controller [1080]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Cryptographic Coprocessor PSPCPP [1022:1486] IOMMU Group 32: 23:00.3 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] Starship USB 3.0 Host Controller [1022:148c] IOMMU Group 33: 23:00.4 Audio device [0403]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse HD Audio Controller [1022:1487] IOMMU Group 34: 40:01.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge [1022:1482] IOMMU Group 35: 40:01.1 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse GPP Bridge [1022:1483] IOMMU Group 36: 40:01.3 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse GPP Bridge [1022:1483] IOMMU Group 37: 40:02.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge [1022:1482] IOMMU Group 38: 40:03.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge [1022:1482] IOMMU Group 39: 40:04.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge [1022:1482] IOMMU Group 4: 00:03.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge [1022:1482] IOMMU Group 40: 40:05.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge [1022:1482] IOMMU Group 41: 40:07.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge [1022:1482] IOMMU Group 42: 40:07.1 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Internal PCIe GPP Bridge 0 to bus[E:B] [1022:1484] IOMMU Group 43: 40:08.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge [1022:1482] IOMMU Group 44: 40:08.1 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Internal PCIe GPP Bridge 0 to bus[E:B] [1022:1484] IOMMU Group 45: 41:00.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Device [1022:57ad] IOMMU Group 46: 42:02.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Device [1022:57a3] IOMMU Group 47: 42:04.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Device [1022:57a3] IOMMU Group 48: 42:05.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Device [1022:57a3] IOMMU Group 49: 42:08.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Device [1022:57a4] 46:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Reserved SPP [1022:1485] 46:00.1 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] Matisse USB 3.0 Host Controller [1022:149c] 46:00.3 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] Matisse USB 3.0 Host Controller [1022:149c] IOMMU Group 5: 00:04.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge [1022:1482] IOMMU Group 50: 42:09.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Device [1022:57a4] 47:00.0 SATA controller [0106]: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] [1022:7901] (rev 51) IOMMU Group 51: 42:0a.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Device [1022:57a4] 48:00.0 SATA controller [0106]: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] [1022:7901] (rev 51) IOMMU Group 52: 43:00.0 USB controller [0c03]: ASMedia Technology Inc. Device [1b21:3242] IOMMU Group 53: 44:00.0 Ethernet controller [0200]: Intel Corporation I211 Gigabit Network Connection [8086:1539] (rev 03) IOMMU Group 54: 45:00.0 Ethernet controller [0200]: Intel Corporation I211 Gigabit Network Connection [8086:1539] (rev 03) IOMMU Group 55: 49:00.0 Ethernet controller [0200]: Aquantia Corp. AQC107 NBase-T/IEEE 802.3bz Ethernet Controller [AQtion] [1d6a:07b1] (rev 02) IOMMU Group 56: 4a:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Function [1022:148a] IOMMU Group 57: 4b:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Reserved SPP [1022:1485] IOMMU Group 58: 60:01.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge [1022:1482] IOMMU Group 59: 60:02.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge [1022:1482] IOMMU Group 6: 00:05.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge [1022:1482] IOMMU Group 60: 60:03.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge [1022:1482] IOMMU Group 61: 60:04.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge [1022:1482] IOMMU Group 62: 60:05.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge [1022:1482] IOMMU Group 63: 60:07.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge [1022:1482] IOMMU Group 64: 60:07.1 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Internal PCIe GPP Bridge 0 to bus[E:B] [1022:1484] IOMMU Group 65: 60:08.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge [1022:1482] IOMMU Group 66: 60:08.1 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Internal PCIe GPP Bridge 0 to bus[E:B] [1022:1484] IOMMU Group 67: 61:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Function [1022:148a] IOMMU Group 68: 62:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Reserved SPP [1022:1485] IOMMU Group 7: 00:07.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge [1022:1482] IOMMU Group 8: 00:07.1 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Internal PCIe GPP Bridge 0 to bus[E:B] [1022:1484] IOMMU Group 9: 00:08.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge [1022:1482] root@pve:~# I have this in VM web interface task log: it does not interfere with a regular OSX function in my case..but I will ask for some infos in proxmox forum By the way..I have understand better if it useful to pass via FLR patches impassable controllers..I can't see any benefit to pass them..it seems also useful to fulfil with right motherboard data my PCIE device output: from this list I can't find in Qemu cfg file some controller exposed here: 82G33/g31...Express Dram Controller 82801 PCI Bridge LPC Interface controller ICH9 SMBus anda ICH9 SATA Others stuff or are things I have passed or you can find it in pve-q35-4.0.cfg I would like to know if in that cfg we can add stuff to improve also Qemu virtual devices and if so which ones?

@iGPU i think you and others are doing many tests how I did. Maybe you should try to follow some my previous finding. trx40 does not need stuff inside vfio.conf in can’t stated definitely because our system are a bit different but I am sure of this (95% that it is so) try to pass only 46:00 or only 46:00.1 and 46:00.3 you will see that 42.08.0 and 46:00.0 will be connected to vfio without declaring it in vm and this happens for many device you can pass. simple way to understand this is to connect a mouse and a keyboard to usb3 backplate internal ports then add in vm only hostpci0: your vga here hostpci1: 46:00.1 hostpci2: 46:00.3 hostpci3: your OS X nvme disk controllers ( in my case 02:00) to do in exact copy of a your starting vm named progressively i think your system starts and you can verify with lspci -nnk all stuff connected in automatic to vfio when I on my amd I will try to complete better...

@Driftwood I don't understand well..but you can ask to all people you desire..I am happy for this (Pavo or other who have experience and no preclusion in this proxmox way) Your ethernet problem is a mystery for me..I am not understanding well it..but I am sure that 8125 is not supported in OSX and maybe you need a new Mieze kext to have it fully working there. I think audio is OSX problem, but some workaround are out there (firewire audio as you say, or a well done usb audio with DAC capacity as @iGPU have. But, when I started this "journey" my goal was to have all working has my previous x299 hack 🙂 Internal Audio is no go..and I have to declare here my loss 🙂 🙂 I can only affirm that in OSX Sierra it is a driver problem and I can have a see (bad) internal audio only passing audio has single device and no as entire controller in this way: usb2: host=0c76:161f If I pass entire controller it is not working at all if I have a green speaker connected on backplate audio output. if I start without audio jack connected I have this but only one working perfect is LG (dp audio Nvidia driver related) USB Pnp Audio Device works bad the same in HS..work well in Catalina I have researched a lot on this because is the only thing I miss It is a coreaudiod related problem and also real Macs could have this problems (by the way, Realtek and usb Audio do not need of any AppleALC or voodooHDA kexts

again..on audio problem 🙂 installed Catalina 10.15.5 beta 4 USB audio is perfect ALC internal audio is not present at all if I connect my speakers on green output jack if I do not connect and reboot I see Realtek USB 2.0 audio device inbound, but connecting some speakers has no effects In High Sierra no results at all I would like to specify that I can obtain these passing all stuff I can (all usb, audio and so on) in Catalina Same configg in high Sierra no audio to see audio in high Sierra I have to pass as USB device from web interface but audio is problematic... So Catalina has better usb audio /port drivers than highSierra not tested so much in 10.15.4 release..but there I have had similar HS problem ah, as side note in HS I can't see usb 3 device (if I connect also a simple usb pen (3.0) instead usb 2.0 device are well recognised I attach my Catalina 10.15.4 ioreg where I have mapped all my USB ports testing usb2/3 devices for usb audio and internal audio (when this works 😉 ) no need of any additional kext (no AppleAlc, no voodooHDA) fabio’s iMac Pro ioreg cata.ioreg.zip

Ah I have mapped in ioreg all USB ports after passing all usb entire controllers interesting thing is that high Sierra does not see usb3 devices catalina instead yes i think also usb related problems are due to OS X versions

Hi @iGPU 25:00.3 usb 25:00.4 audio 04:00.3 usb controllers has 149c o 148c as Id ? if so you can pass it using a proper patched kerneL in my case are named 23:00.3 and 4 and 04:00.3 all were unpassable without FLR patch For WiFi/bt I can’t say because I haven’t them

source

@AllubzV and @all interested to solve audio problem try to pass all your main USB controller and boot with audio jack disconnected (in my case hostpci: 46:00)..audio instead should be 23:00.4 (and do not pass it) No need to patch FLR

about this I am also using both internal USB3 connector using my 4 usb3 external Core X9 case ports I would suggest to check in ioreg how your system sees those ports also back plate ports..some time it does some weird things..I think it is for some VM compatibility USB check see also this file in your proxmox: /usr/share/qemu-server/pve-q35-4.0.cfg here you can find many declaration about old USB ports..if you do not pass entire usb controller you should see in web interface/hardware/usb port or device disks or stuff you connect to your rig. In my opinion those lines could create some problems in our modern (and unsupported AMD) rig

for your problem (main problem) have you checked in updated bios if some new voice is there about IOMMU I mean? If you do not have done any error it is the only answer to explore because @99% it is an user errors (some time I miss myself things and I break my head to understand.. FYI I have reverted all mid Debian files to original ones, because for me passing them with FLR patch is not useful to latest my goal on this system ( internal audio 🙂) others task are reached and all controllers are passed well I hope I can find a solution for audio, but I am convinced it is an OSX problem and if you search also many original Mac are affected from this usb audio bug A solution seems to use an Audio with DAC capability or also @iGPUexternal audio I have not tested personally so if people could share experiences in this subject I will more than happy 🙂

searching on the net also real Mac have some problems (not solved for all) USB audio problem this is a partial log when audio starts to fail

@Driftwood novnc problem is related to passed gpu and none in display VM config line if you access to your amd from another pc/device you have to change that none and block gpu bybass (maybe) in my experience any problem your rig can have (if it has been working well before) is caused from an user problem 😊 network problem could be tricky if you installed Proxmox with vmxnet3 in vm config and if you pass the same network controller you will have proble or to navigate or to access to webinterface because passed ethernet will take your ip (ip you used in installation step) and conseguentially it assign a different ip to your vmxnet3 device (assuming you are in dchp for both) @iGPU this should be last question about audio😂 do you know which driver is using your working audio device?

@iGPU in verbose maybe you can see where it hangs before login ?

@AllubzVif you read I said before only problem I have i think is an OS X driver problem because with same proxmox setting in a window vm it is perfect patch is useful to pass controller but it is also possible to pass without i have asked @pavo to insert 148c address for us (trx40 user) but as I said not useful to solve @iGPU has a working usb Dac audio, but in my case I have no others usb to test..only cheaper ones and these have the same problem

If you have windows installed you can use it in my case I use grub bootloader (proxmox) to boot and decide what I want use you have to find a solution for you better for you I mean 👍

Hi @lvtz USB controller is integrated on my motherboard and in the main guide I show where I connect my "proxmox" disk. in 1) and 2) question you mix some different subject.. to install Proxmox you have to create an USB Pen (CD/DVD or what you desire) to install it Then you can choose a disk to install Proxmox (proxmox = linux) I have chosen an external USB disk..why? in this way I have all others controller (sata, NVME, and so on to pass to my VM) Best solution is to have your guest OS system in a separate drive from Proxmox disk ie if you have now a working OSX on your system you can use it with only a proper EFI to boot with it.. if you instead install OSX on a file, you can have it on your Proxmox disk..in my opinion it is better to use Proxmox disk only for few things and leave all other OSX separated from it so you need: 1) an USB/CD/DVD for iso installation file 2) boot from this one and from here you have to configure Proxmox (5 minute of your time) 3) in there you choose disk fr proxmox installation (in my case an external disk on back USB) 4) then you can create following the instructions your VM if you have an existing OSX on a separate disk you can try to "pass" that disk..I did for my NVME High Sierra Be prepared to solve different problems..but when you succeed in this task you will be happy 😉

Hi 1) yes you can use it* 1b) no no clean installation is required 2) if you want to use an exist OSX instalaltion yes, if you use a disk in a virtual file no 3) success dipend from your skill and patience. It is not simple but many users with your same rig (a vanilla Patches supported system) are trying proxmox having less problem with compatibility for app (0 problem) and better gpu performances It is Tricky but it could work 🙂 * you have to pass your disk controller or single disk (SATA, NVME..) To have a detailed answer you have to read all the post here and also in main guide.. you can also check @Pavo GitHub , there you will find a system more similar to yours

@Driftwood if better results are obtained with a VM file disk..they are not accurate (sorry for this 🙂 ) if instead they are achieved with a passed drive or entire controller...are very good almost impossible but very good @iGPUyou can use multiple gpu (not in crossfire or SLI), software like davinci resolve and other have a great benefit with dual gpu system

ok solved 🙂 root@pve:~# pveversion -v proxmox-ve: 6.2-1 (running kernel: 5.4.34-1-pve) pve-manager: 6.2-4 (running version: 6.2-4/9824574a) pve-kernel-5.4: 6.2-1 pve-kernel-helper: 6.2-1 pve-kernel-5.4.34-1-pve: 5.4.34-2 ceph-fuse: 12.2.11+dfsg1-2.1+b1 corosync: 3.0.3-pve1 criu: 3.11-3 glusterfs-client: 5.5-3 ifupdown: 0.8.35+pve1 ksm-control-daemon: 1.3-1 libjs-extjs: 6.0.1-10 libknet1: 1.15-pve1 libproxmox-acme-perl: 1.0.3 libpve-access-control: 6.1-1 libpve-apiclient-perl: 3.0-3 libpve-common-perl: 6.1-2 libpve-guest-common-perl: 3.0-10 libpve-http-server-perl: 3.0-5 libpve-storage-perl: 6.1-7 libqb0: 1.0.5-1 libspice-server1: 0.14.2-4~pve6+1 lvm2: 2.03.02-pve4 lxc-pve: 4.0.2-1 lxcfs: 4.0.3-pve2 novnc-pve: 1.1.0-1 proxmox-mini-journalreader: 1.1-1 proxmox-widget-toolkit: 2.2-1 pve-cluster: 6.1-8 pve-container: 3.1-5 pve-docs: 6.2-4 pve-edk2-firmware: 2.20200229-1 pve-firewall: 4.1-2 pve-firmware: 3.1-1 pve-ha-manager: 3.0-9 pve-i18n: 2.1-2 pve-qemu-kvm: 5.0.0-2 pve-xtermjs: 4.3.0-1 qemu-server: 6.2-2 smartmontools: 7.1-pve2 spiceterm: 3.1-1 vncterm: 1.6-1 zfsutils-linux: 0.8.3-pve1 root@pve:~# it was simple..a file....kvm.conf 🙂 🙂 🙂 no improvement for our common problem for now I would like also to remark: useful file for my rig to modify after a clean Proxmox VE 6.2 iso: etc/modules vfio vfio_iommu_type1 vfio_pci vfio_virqfd etc/modprobe.d/kvm.conf options kvm ignore_msrs=1 /etc/default/grub.cfg quiet iommu=pt amd_iommu=on then I have used my previous VM.conf file recreating in it only EFI disk

Ok, it is a not new kernel problem related..Probably new QEMU has some conflict with our bootloaders... for now stay away from this or try with a solid backup

do not update for now now also my minimal Vm hangs on ++++++++ end seed both with clover 5107 and opencore 0.58 try to revert to old kernel by now i hope it is enough to start again my VM 😂 upgrading deleted my lvm.conf file so this was the reason for the hang on ++++++++ phase (MSR related)

@iGPU scp command are in the guide and then are also obsolete in some case from an advice @Rocket88gives about using FileZilla ftp client(if you search you can find easily) link here A remainder as you did is good too 🙂 about lane sharing..this could be the big task for all of us togheters multiple "bridge" connection we have.. I think it is also an unexplored territory also for Proxmox guy and maybe in many case Windows VM is not affected from the same our problems because in there more supported stuff is (virtio drivers, spice and so on) I am convincing myself ( 🙂 ) that audio problem is not related to my poor knowledge but it is more a "system" problem I can have it perfectly working but it is not stable at all as it should be and also how Nvidia DP/Hdmi is. I would like to share an example: with many tries I have "a working" Realtek audio I launch DaVinci Resolve to produce some video you can find in macOS86 you tube channel edit video cutting, scribbling audio perfectly.. I put a cross dissolve ( a simple cross dissolve to insert macOS86 logo as a super on main video ) audio scratch during cross dissolve effect... Our system (mine in particular) can work with multiple 8k layer without any problems) but using this problematic audio it fails (I repeat..with DP audio is perfect) so it should be OSX audio driver not working well with VM previously configured part .. Searching on the net many talking about problematic audio in VM but no one gives a solution to try

Good, If you think it could help other people and if you want , describe your procedure to have it working 🙂 I have had private conversation with many AMD radeon VII and seems some Radeon VII card has not a UEFI BIOS It is not confirmed directly by me, but it is a sort of "rumours", and this should be the cause of many AMD GPU card users.

@AllubzV take a look and compare with yours (I would like also others TRX40 users put their similar datas to compare) 04:00.3 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] Starship USB 3.0 Host Controller [1022:148c] Subsystem: Micro-Star International Co., Ltd. [MSI] Starship USB 3.0 Host Controller [1462:7c60] 23:00.3 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] Starship USB 3.0 Host Controller [1022:148c] Subsystem: Micro-Star International Co., Ltd. [MSI] Starship USB 3.0 Host Controller [1462:7c60] Kernel driver in use: xhci_hcd 23:00.4 Audio device [0403]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse HD Audio Controller [1022:1487] Subsystem: Micro-Star International Co., Ltd. [MSI] Starship/Matisse HD Audio Controller [1462:cb60] Kernel driver in use: vfio-pci 46:00.1 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] Matisse USB 3.0 Host Controller [1022:149c] Subsystem: Advanced Micro Devices, Inc. [AMD] Matisse USB 3.0 Host Controller [1022:1486] Kernel driver in use: vfio-pci 46:00.3 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] Matisse USB 3.0 Host Controller [1022:149c] Subsystem: Advanced Micro Devices, Inc. [AMD] Matisse USB 3.0 Host Controller [1022:148c] Kernel driver in use: vfio-pci And focalise also on Subsystem data (check also your BIOS AGESA, TRX40 ones are not updated to the last patch). Now, as you have seen FLR patch is not perfectly calibrated for TRX40 users and if you follow below link I have inserted on Proxmox forum, Stefan_R (a proxmox forum staff guy) says we have to do some others step because "we are experiment on the joy to use bleeding edge new hardware" 🙂 FLR patch was done some months ago and follow leveltech1 comment in some cases is possible to insert via kernel command (in my case it not was working) @pavo compiled that patch in a kernel (which is not the one suggested by Fabian) and it is available on his GitHub In my case is not working and for some x570 users is working partially So our goal should be how to compile new Kernel you can find in Proxmox git and then to understand if it possible to insert on a kernel line command FLR patch Proxmox Stefan_R advice level1techs FLR patch discussion Proxmox git for latest Kernel As last information I would like to share, I can pass also 23:00.4 as you can see in my above box (it uses vfio-pci kernel )but audio is problematic I can have a working internal audio via matisse audio controller or with a simple usb audio adapter bought to test this problem. Audio works..but it is not perfect (I loose it, some time is scratchy an so on) some time is perfect but usually if I change audio source from ie a video to a mp3 file ..I loose it For this I said before no ready for a professional use Nvidia Dp/hdmi is perfect. My idea is a negative idea in this subject (I hope to be very wrong on this). problem for me is due Audio osx system driver and how it is interact with trx40 CPU. In Proxmox Windows 10 64 bit VM, same linux configuration, internal audio (USB 2.0 Realtek) is perfect As last last ( 🙂 ) information I would like to advice to test audio problem (it is valid also for other problem you can have) to test with a minimal set of passed controllers.. I pass for this task only NVME controllers where I have my OSX disk and then I pass mouse/keyboard as single USB ports. To have proxmox distro installed on an USB disk could be useful to pass fine all your Sata or NVME controllers to OSX (I use back type C port of my motherboard) and doing this I loose possibility to pass my ASMedia USB controller to OSX, but both ports on it are working (simple USB port passthrough)

No differences i think problem is Proxmox/osx related in a proxmox windows environment it works as it should be

hi @Rocket88thank you for your message above for to do list 1) is a common research because OSX misses Qemu Agent so if you shutdown OSX linux will be on I think you can avoid something you used..maybe in your blacklist.conf file to pass "hangs after Ramdisk message" (it could mean you have blacklisted your GPU driver so you need to run VM from another pc/device Only you can verify this When you have time post here benchmark for your system, It could be useful for other users thank you again for posting your experience!