Leaderboard

@Vladimiro tutto questo cosa c'entra con hackintosh? Senza offesa ma basterebbe fare proprie ricerche... google è tuo amico.... Non siamo qui per fornire supporto dalla A alla Z riguardo a windows o altri sistemi operativi. Sul web ci sono innumerevoli guide, su come fare, installare driver etc.. Topic Chiuso perchè è andato completamente fuori "tema".

il problema l'ha sulla Z490, scritto nel titolo e non l'ha avuto su un altro hack, con questo si riferisce alla guida Credo che forse, intenda tempo fa quando ancora clover non aveva quirk etc

Nuova 11.2.1 build 20D74

@Vladimiromolto probabilmente anche l'altra volta potrebbe essere stato un problema simile..e il tuo negoziante se ne e' approfittato se ti ha tolto 170 euro pero' e' uno scotto che si deve pagare (purtroppo) e non solo in informatica.. i forum aiutano in questi casi grazie a tutte le persone che hanno provato ad aiutarti... cmq mi permetto una battuta.. il tasto TAB..no!... per favore.... 🙂 😛

Non diamo supporto a distribuzioni di alcun tipo. Permettiamo l'uso di installer regolarmente e personalmente scaricati da server apple. Sarebbe da fare..

this is mine MSI TRX40 PRO 10G IOMMU.xls.zip

@Rox67ermy motherboard has an empty slot but I thought it was a pciex1 slot thank you for your detailed tutorial 🙂

hi have you ever seen proxmox logo? Could you try to comment in this way blacklist.conf?: #blacklist snd_hda_intel #blacklist snd_hda_codec_hdmi #blacklist i915 #blacklist radeon #blacklist nouveau #blacklist nvidia #blacklist i2c-nvidia-gpu #blacklist amdgpu in this way you can operate directly from your AMD and in the shell you can execute: qm start 101 and see in grub line I 'd put only: GRUB_CMDLINE_LINUX_DEFAULT="quiet amd_iommu=on video=efifb:off" and remember to run update command: update-initramfs -u -k all update-grub and then: reboot also if you can you can use FileZilla to copy your files..

@cj750 what do you mean when younsay it boots fine? From webinterface console window you see osx ? could you post vm conf file, blacklist.conf, modules, vfio.conf, kvm.conf? also grub file would be fine

@Driftwoodin Catalina no rendering support for Nvidia in high Sierra performance in adobe or davinci resolve app are similar and maybe little better than a Radeon VII

Sooner or later I'll have to switch to an AMD graphics card too. But all these small / big problems scare me a little 🙂

frontier or rx580? UEFIi GFX bios available? Have you tested with a "rom" option?

@cj750they gave that beta bios in a private form to @DriftwoodI think he asked for new AGESA Usually they do not give any changement txt in this way

And what was your question to them? by the way asrock Taiwan in the past did for me an unlocked bios (msr related) and they asked me if I was using for OSX 🙂

@TheDaemonBarberwhy are you saying passthrough is not working? two line (locked at two initial lines) or a verbose pointing to a proxmox shell is the same..and I advice to be able to reach always Proxmox shell..in this way you can avoid in a future to have the need of using a spare pc or tablet to do minimal corrections if you need Take a look to my files you can understand better.. This is my working AMD if you want to block with only two lines..try to block also nouveau...but I repeat do not need of this blocking in modern system Archive.zip Today best AIO and best air cooler for tr4 are equivalent in my opinion... the best solution would be to build a custom one, I prefer to stay on air because I do not want have a sort of anxiety on liquid on my system This summer I will decide..but for now my Dark rock pro TR4 does a pretty good job

Also SVV stuff in bios should be mandatory to boot Proxmox VM and some stuff in IOMMU (it is in auto and it is good)

In this video you can see in framed window what happen if you blacklist stuff in big window you can see my actual situation (bad graphics in small windows is now solved using OpenCore bootloaderas I discovered time ago 🙂 ) for the guide you can follow link you find in OP of this thread

@Rocket88 you do not need to have another pc to boot VM in proxmox for trx40 and also x570 user is possible to do in different way we are usual to see in traditional proxmox guide. if you see a my early video you can see i use both method. Automatic vm boot and manual boot launching from my amd rig qm start 100 you have to play with stuff you block in blacklist.conf file. i think also all of you could achieve the same we do not need many things we find in canonic way to set proxmox. you have to try by yourself to believe.😁 About 99 code error it is a not good thing and i havent ever had it in my rig maybe it is related to Amd gpu, or to internal wifi bluetooth i have not

@TheDaemonBarber if you use Proxmox you can use both boot loader and a minimal set of patches If you are in "Vanilla" you have to use opencore because latest clover do not work in a good way with AMD patches

@Rox67er i have tested during this journey all bios available for my motherboard with all of these i have the same functionality and group separation i do not think Agesa is your problem now also your motherboard has agesa 1.0.0.4 with latest bios posted few messages above ehm sorry for asrock 1.0.03 patch c only for now

I would like also to add that in a Windows VM (Proxmox) audio is also perfect I can pass it via entire controller or as a single USB device from web interface perfect. Problem is (I repeat my self) driver in HighSierra (maybe too old for our new hardware)

Hi @iGPU in High Sierra problem is USB driver I can't see any USB3 device connected.. I have also a VM with "only" 32threads set..Problem is the same I have tested roughly in the same way with Unraid..same problem Catalina is perfect instead ( I have only problem I said with jack detection) but ie my cheap USB audio is perfect also with speaker connected @ cold boot

@Driftwooda my curiosity 🙂 which case do you have? temperatures are fine with that Noctua? TY

by the way @Driftwooddo you know a PCIE Audio card supported in HighSierra? I would like to test because in this OS audio is working well only via DP port (GPU Audio)

Hi @iGPUI do not know your EFI folder, but if you pass cpu as Host you can clean so much your VM args. Also is a good news if it is verified about Archlinux microcode save..also a bit terrific news..if it is a not controllable by users feature 🙂

Remember..for me Catalina is only to see audio well... My gfx is not supported and I am patching Nvidia driver to have two monitor working at correct resolution 🙂

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

@Driftwood47:00.3? Don’t use it?

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

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

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

new agesa 🙂

If any of you have time and desire to read I have explained here what I understood about my USB controllers and how they are managed by Proxmox. I hope for an answer that will enlighten us in understanding some small parts that are missing to have a more capillary control over the Proxmox / OSX coupling https://forum.proxmox.com/threads/trx40-amd-usb-controllers-question.70504/

@cj750 welcome here I will happy you also partecipate with your point of view. It is interesting to see also newbie (in this task) experience..because maybe we are doing the same errors 🙂 If you have time put your rig in signature so we can see better motherboard and cpu you use 🙂 Thank you

Catalina 10.15.5? No

seeing your VM conf I could imagine which some problem could happen to your system because you allocate (maybe) to much memory for VM if you have in total 128Gb..in my case in my previous attempts I have had put about 122000..and vm not was stable in that case I am not using also huge page stuff.. is it useful for you? and so when/where do you see benefit?

Catalina OS seems to push a bit more about performance..obviusly same EFI to boot

Hi first of all thank you to you and all people are keeping updating this thread with their experiences I appreciate it so much About 7-5 error when you boot proxmox, you should have to update your proxmox.I opened a thread on Proxmox support site time ago. Now with latest proxmox kernel that errors could not appears anymore Instead a bunch ACPI error could always happen For both (7-5 errors and acpi errors) a man of proxmox stuff said it is not a problem at all. I have not specifically competence to understand if It is true..so I have to accept as it is link to thread I said before

updated to latest security fix for now I have to patch Nvidia web to have acceleration as usual..waiting for Nvidia new updated driver

if I have understood your problem.. when you stay in proxmox ip/ethernet step, you can see all ethernet device installed (and that proxmox sees) in your system try to choose wifi one if there. I have no wifi so I can't say more about this

@Rox67er have you solved understand your 99 code Error? searching on the net could be a simple bios corruption or a big problem with cpu pin socket about vfio.conf my motherboard has no wifi/no bt i can pass all controller if i use Flr, and i have all usb on my rig active now i am not using anymore flr kernel patches because I have the same functionality without passing audio controller/ 2 usb controller also important to say is that osx driver is the main actor imho. high sierra does not recognize any usb3 controller but osx catalina i installed from 10.15.5 beta to the release have nice improvement for usb i loose many time for this problem but problem was inside high sierra. For me is important to have it working in high sierra cause my gpu is not supported from newer osx i would also suggest you to install on a vm disk file also windows 10 64 bit you can install in a flash it and from there you can verify if your problem is a linux configuration problem or if it is a Os problem.

Both usb Realtek audio and cheap USB audio work well in latest OS X release... for more infos read also main fix in this release...