Leaderboard

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

Uhm oltre a 2666mhz, se non usi anche Windows, non ha per nulla senso. Le vede "per finta", non le sfrutta e hai problemi durante il wake. Quindi, la risposta è: no. L'iMac 19,1 (o il 18 oppure l' iMacPRO 1,1 , non hanno ram oltre i 2.6GHz...quindi, le vedrebbe ma non le userebbe minimamente...o meglio non vedresti alcuna differenza.) Io monto 3200 overcloccate a 3333 , quindi oltre al profilo X1, ma perchè uso anche Win. Li le vede e le sfrutta. MacOSX (nel tuo caso) e MacOS nel mio, non le sfrutterebbero. Meglio, se vuoi avere 32GB, 4 banchi da 8 piuttosto che 2 da 16 per quanto riguarda prestazioni di timing etc... Ma precluderebbero un "futuro" passaggio a 64 per esempio... Comunque sia, vedi se sui soliti canali trovi magari in sconto o usati 2 banchi da 16 da max 2666 e vivi felice xD LoL ahahha

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

try to enable one on one the latest four..with some combinations it could start..all no

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

it seems you have changed else maybe CSm or 4g on bios? in this way you could loose some functionality on sleep/wake, reboot or shutdown you have to test

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

simply...have you connected the power on it?

It shouldnt change if you not change bios parameters like CSM/UEFI or 4g on/off if you have in BIOS however check always your debug log, if you see some skip to 0 when before you have had them to 1 , it means value of that MMIO is changed and you have to recalculate its value

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 😉

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 ;(

I would start with a more clean config.plist and you would try to solve your problem with your monitor then it is more simple to do the missing optimization (if possible 😛 ) I can't help on bluetooth configuration but you have to solve a problem and then try to solve others 🙂 so use MMIO list I have produced yesterday for you..and try to solve your monitor problem first. How? enabling or disabling whatevergreen kext clearing Nvram.. only you could test then search on bios wake on lan parameter if you have..and maybe also with this you could solve "others" problem (ask to gigabyte users here)

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

@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)

30:390 00:003 OCABC: MMIO devirt 0xEA400000 (0x181 pages, 0x8000000000000001) skip 1 now also this is fine for slowness of booting... now you have a working EFI to start If it was my system I will try to see if it is possible to boot without pikera boot args, Whaevergreen kext and so on AppleAlc is not useful for your internal Realtek audio and , I think you have to follow some indications of others Gigabyte users I do not like to fill my ACPI folder with SSDt , I have no wifi or BT so you could have the need to improve this config.plist pay always attention to your MMIO data, because ie the above one seems not present in Ploddies config..I do not why and I do not know his bios settings however welcome in almost working TRX40 community 🙂

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

config.plist.zip this config have your exact MMIO with I see in debug put in config pikera bootarg and try again post debug log and config used thanks

yes because no pikera booting in there..I have thought you have Nvidia.. 48:200 00:054 OCABC: MMIO devirt 0xE2100000 (0x81 pages, 0x8000000000000001) skip 0 48:237 00:036 OCABC: MMIO devirt 0xE3180000 (0x81 pages, 0x8000000000000001) skip 0 48:273 00:036 OCABC: MMIO devirt 0xEA400000 (0x181 pages, 0x8000000000000001) skip 0 48:309 00:036 OCABC: MMIO devirt 0xFA180000 (0x81 pages, 0x8000000000000001) skip 0 48:345 00:036 OCABC: MMIO devirt 0xFA300000 (0x100 pages, 0x8000000000000001) skip 0 48:404 00:058 OCABC: MMIO devirt 0xFEA00000 (0x100 pages, 0x8000000000000001) skip 0 48:440 00:036 OCABC: MMIO devirt 0xFEC00000 (0x1 pages, 0x8000000000000001) skip 0 48:476 00:036 OCABC: MMIO devirt 0xFEC10000 (0x1 pages, 0x8000000000000001) skip 0 48:512 00:035 OCABC: MMIO devirt 0xFED00000 (0x1 pages, 0x8000000000000001) skip 0 48:548 00:036 OCABC: MMIO devirt 0xFED40000 (0x5 pages, 0x8000000000000001) skip 0 48:602 00:053 OCABC: MMIO devirt 0xFED80000 (0x10 pages, 0x8000000000000001) skip 0 48:638 00:036 OCABC: MMIO devirt 0xFEDC2000 (0xE pages, 0x8000000000000001) skip 0 48:674 00:036 OCABC: MMIO devirt 0xFEDD4000 (0x2 pages, 0x8000000000000001) skip 0 48:710 00:036 OCABC: MMIO devirt 0xFEE00000 (0x100 pages, 0x8000000000000001) skip 0 48:747 00:036 OCABC: MMIO devirt 0xFF000000 (0x1000 pages, 0x8000000000000001) skip 0 48:805 00:058 OCABC: MMIO devirt 0x1040000000 (0x10400 pages, 0x8000000000000001) skip 0 48:841 00:036 OCABC: MMIO devirt 0x6EE0000000 (0x10400 pages, 0x8000000000000001) skip 0 48:878 00:036 OCABC: MMIO devirt 0x6F10000000 (0x10400 pages, 0x8000000000000001) skip 0 48:914 00:036 OCABC: MMIO devirt 0xCDB0000000 (0x10400 pages, 0x8000000000000001) skip 0 these are your MMIO with bios you are using by now and they are different from @Ploddlesone posted in OP of other thread My questions are: 1) same BIOS 2)CSM on or off?

please do not modify anything otherwise I will be crazy to understand I will explain what I want to do I would like that your system uses your MMIO.. so we have to convert it for you and see if in txt they are skipped to 1

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

@iGPU this is mine, I use a script given on amd discord by @pshirshov user, he should be also here I think with maybe other nickname: 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 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) to copy examples you did 46:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Reserved SPP [1022:1485] Subsystem: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Reserved SPP [1022:1485] 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 Kernel modules: xhci_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 Kernel modules: xhci_pci 47:00.0 SATA controller [0106]: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] [1022:7901] (rev 51) Subsystem: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] [1022:7901] Kernel driver in use: vfio-pci Kernel modules: ahci 48:00.0 SATA controller [0106]: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] [1022:7901] (rev 51) Subsystem: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] [1022:7901] Kernel driver in use: vfio-pci Kernel modules: ahci and this is achieved only with: hostpci9: 46:00.1 hostpci10: 46:00.3 hostpci11: 47:00 hostpci12: 48:00 47:00, 48:00 are my sata controllers: Qemu hard disk here is my Catalina on disk file the others are my mechanical disks installed and passed thanks to 47:00, 48:00 controllers

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?

@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..audio obsession for me 🙂 (in High Sierra 😉 ) https://www.usb-audio.com/support/

@Driftwood i cant see here how @Pavosolved your problem i think you are the user he said to help on amd discord channel with realtek and audio problem. i would like to have this kind of discussion in public because maybe it is usefull also for others. Just my 2 cents in this subject😁 i do not well understand your ethernet problem, in my case also aquantia card take by default an ipv6 address and i can modify it in installation step configuration according my router configuration..but maybe yours problem is different. Instead solution of scrambling iommu group is pretty simple. our trx40 motherboard had a bunch of bridges with pcie, nvme and so on some slots are shared and changing card position or eliminating / adding a nvme disk could have many of the effects you describe above as personal consideration : best trx40 mb is Gigabyte designare. It has best layout i have ever seen for its slots and a full features including a big thunderbolt value maybe fullfill all nvme slot in it could cause some problems in a proxmox/osx environment but it is the only motherboard i would like to have different of mine Trx40 asrock creator is also fine, in my case not so good because i have 8 sata disk in my rig and it seems it miss 2 sata ports.

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

I disagree (in friendship) 🙂 ok a separated disk for any OSX..but then I boot from OC or clover to execute one of them and in my VM test I have also a Catalina OSX on a qemu file. I would like to understand better problems many of you have to pass your controllers From your lspci -nnk I see it is possible to pass all controllers in the same way I do (some of them using FLR patch). Other thing I am very interested is if for you it is mandatory to put stuff on vfio.conf or in blacklist.conf..because it shouldn't (on TRX40) And, if it is mandatory I see only a main difference from our rigs..GFX card by the way @Driftwoodpassing your Blackmagic card you did my day better 🙂 Thank you

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 🙂

@Driftwood your Realtek ethernet in osx should supported from this kext by Mieze:

Have you put kext for your intel? otherwise OS X do not see it or maybe I miss your problem completely😂

a discover...not useful but... Our internal USB Realtek USB 2.0 audio does no need any additional kext for "working"... it works (bad) with only OSX system kext

@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

I would like to share something that could be useful for Full PCi tab lovers in about my Mac / System Report /PCI from Proxmox shell (this naming for path is for latest 6.2 proxmox VE installation: nano /usr/share/qemu-server/pve-q35-4.0.cfg you will see: GNU nano 3.2 /usr/share/qemu-server/pve-q35-4.0.cfg #[device "ehci"] # driver = "ich9-usb-ehci1" # multifunction = "on" # bus = "pcie.0" # addr = "1d.7" #[device "uhci-1"] # driver = "ich9-usb-uhci1" # multifunction = "on" # bus = "pcie.0" # addr = "1d.0" # masterbus = "ehci.0" # firstport = "0" #[device "uhci-2"] # driver = "ich9-usb-uhci2" # multifunction = "on" # bus = "pcie.0" # addr = "1d.1" # masterbus = "ehci.0" # firstport = "2" #[device "uhci-3"] # driver = "ich9-usb-uhci3" # multifunction = "on" # bus = "pcie.0" # addr = "1d.2" # masterbus = "ehci.0" # firstport = "4" #[device "ehci-2"] # driver = "ich9-usb-ehci2" # multifunction = "on" # bus = "pcie.0" # addr = "1a.7" #[device "uhci-4"] # driver = "ich9-usb-uhci4" # multifunction = "on" # bus = "pcie.0" # addr = "1a.0" # masterbus = "ehci-2.0" # firstport = "0" #[device "uhci-5"] # driver = "ich9-usb-uhci5" # multifunction = "on" # bus = "pcie.0" # addr = "1a.1" # masterbus = "ehci-2.0" # firstport = "2" #[device "uhci-6"] # driver = "ich9-usb-uhci6" # multifunction = "on" # bus = "pcie.0" # addr = "1a.2" # masterbus = "ehci-2.0" # firstport = "4" # FIXME: Remove this audio0 device at the next possible time # see: https://pve.proxmox.com/pipermail/pve-devel/2019-July/038417.html # https://pve.proxmox.com/pipermail/pve-devel/2019-July/038428.html #[device "audio0"] # driver = "ich9-intel-hda" # bus = "pcie.0" # addr = "1b.0" [device "ich9-pcie-port-1"] driver = "pcie-root-port" x-speed = "16" x-width = "32" multifunction = "on" bus = "pcie.0" addr = "1c.0" port = "1" chassis = "1" [device "ich9-pcie-port-2"] driver = "pcie-root-port" x-speed = "16" x-width = "32" multifunction = "on" bus = "pcie.0" addr = "1c.1" port = "2" chassis = "2" [device "ich9-pcie-port-3"] driver = "pcie-root-port" x-speed = "16" x-width = "32" multifunction = "on" bus = "pcie.0" addr = "1c.2" port = "3" chassis = "3" [device "ich9-pcie-port-4"] driver = "pcie-root-port" x-speed = "16" x-width = "32" multifunction = "on" bus = "pcie.0" addr = "1c.3" port = "4" chassis = "4" ## # Example PCIe switch with two downstream ports # #[device "pcie-switch-upstream-port-1"] # driver = "x3130-upstream" # bus = "ich9-pcie-port-4" # addr = "00.0" # #[device "pcie-switch-downstream-port-1-1"] # driver = "xio3130-downstream" # multifunction = "on" # bus = "pcie-switch-upstream-port-1" # addr = "00.0" # port = "1" # chassis = "5" # #[device "pcie-switch-downstream-port-1-2"] # driver = "xio3130-downstream" # multifunction = "on" # bus = "pcie-switch-upstream-port-1" # addr = "00.1" # port = "1" # chassis = "6" [device "pcidmi"] driver = "i82801b11-bridge" bus = "pcie.0" addr = "1e.0" [device "pci.0"] driver = "pci-bridge" bus = "pcidmi" addr = "1.0" chassis_nr = "1" [device "pci.1"] driver = "pci-bridge" bus = "pcidmi" addr = "2.0" chassis_nr = "2" [device "pci.2"] driver = "pci-bridge" bus = "pcidmi" addr = "3.0" chassis_nr = "3" [device "pci.3"] driver = "pci-bridge" bus = "pcidmi" addr = "4.0" chassis_nr = "4" In there I commented many lines (old USB related) , this to have a better and clean situation in PCI device output in app like dpcimanager or Hackintool My tries it is always related to acquire a perfect functionality on internal audio I miss 😉 with this emu vm config I achieve this: so a bunch of EHCI and UHCI device are not loaded anymore in my system..and functionality of it seems to be the same. From picture above you can see some stuff also passed from the pve-q35-4.0.cfg file, I mean QEMU PCI-Pci bridge.. I am trying if is possible to avoid also some of this loading.You see also other stuff (first 6 lines) it seems not present in this file.. Main task/goal could be to inject here some devices we have in our rig? We will see Previous situation without commenting those lines: here less controllers passed..it is a VM I use to test so I pass few devices! DO NOT DO IT IF YOU PASS USB MOUSE OR KEYBOARD OR OTHER DEVICE AS A SINGLE USB IN WEB INTERFACE

@lvtzi would use a smaller drive for proxmox but it is a your choice as advice starts more simple you can and then when you know what are you doing you can go deeper

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 😉

@Driftwood I asked before post if you want your vm config your lspci -nnk output your modules file your kvm.conf file..and all thing could be useful motherboards are different and you have a radeon which could be more problematic...but solutions could be similar for others controller.. Stay for now with Imacpro1.1 @AllubzV I think did an example to explain that more GPU are possible also in real Mac (and obviously in our hackintosh)

ok a big improvement for me.. trying to solve audio problems I have had an idea to try to pass impassable USB controller in my case they had an id like this: 10:22,148c so I asked @Pavoto compile for me new kernel adding this patch: diff --git a/drivers/pci/quirks.c b/drivers/pci/quirks.c index 308f744393eb..9806bff34b9b 100644 --- a/drivers/pci/quirks.c +++ b/drivers/pci/quirks.c @@ -4999,6 +4999,9 @@ static void quirk_intel_no_flr(struct pci_dev *dev) DECLARE_PCI_FIXUP_EARLY(PCI_VENDOR_ID_INTEL, 0x1502, quirk_intel_no_flr); DECLARE_PCI_FIXUP_EARLY(PCI_VENDOR_ID_INTEL, 0x1503, quirk_intel_no_flr); +DECLARE_PCI_FIXUP_EARLY(PCI_VENDOR_ID_AMD, 0x148c, quirk_intel_no_flr); +DECLARE_PCI_FIXUP_EARLY(PCI_VENDOR_ID_AMD, 0x1487, quirk_intel_no_flr); + static void quirk_no_ext_tags(struct pci_dev *pdev) { struct pci_host_bridge *bridge = pci_find_host_bridge(pdev->bus); -- 2.24.1 He compiled it successfully and I have inserted in my Proxmox now all controller are passed under vfio driver (in my case no need to declare it on vfio.conf or block any drivers) Pavo added this patch in his GitHub . I think this could also be useful to pass other problematic controllers (ie thunderbolt?? ) 🙂 below my passed controller now: 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] Kernel driver in use: vfio-pci Kernel modules: xhci_pci 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: vfio-pci Kernel modules: xhci_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 Kernel modules: xhci_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 for now I haven't tested if I have additional problem using this patch.... we are on the bleeding edge..using not tested hardware for our task 😉

@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

Hi Paul, this "hole" for audio related part is a bit risky by now. Internal audio of TRX40 mb is bridged (maybe) with usb controller so this for now it is problematic I have bought also a cheap USB sound adapter and also this has problems. Display Port audio from my Nvidia GFX is perfect and I have tested with it audio features ( I am not an audio expert) but I can affirm which Proxmox/osx you can use any plugin without problem if this plugin works well in OSX Proxmox/osx installation is not affected from problem you may have with Vanilla patches method..

@iGPU I monitor my temps with my motherboard led code display in bios there is an option to monitor temps trulyspinach app does not work one kext seems to output a missing cpu Id in verbose

I did..in my case yes..no improvement but it is latest available so could have some benefit I cannot see by now I f you are unsure stay with old version

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

@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

@here USB audio partially solved.... verify few things then I will expose it how I did. I repeat USB audio not internal Realtek USB 2.0 motherboard audio for now Not usable for production.