Leaderboard

The ASRock TrX40 Creator has two SATA controllers at 48:00.0 and 49:00.0 respectively. I got ports 5-8 working on the SATA controller at address 48:00.0 now and passedthru: VFIO options vfio=pci ids=1022:7901 VM 100.CONF hostpci6: 48:00.0,pcie=1,rombar=1 This means I can now use four internal drives on those ports (indeed, Im looking at my windows boot drive on port 5 right now!), whilst keeping the Proxmox SSD boot drive on 49:00.0, SATA port 1 (1-4 is free) from outside the hypervisor. 🙂 Here's v2 of my chart updated. Now lets get these USB ports figured out! @Rox67er

This BIOS looks good @Rox67er... Im reporting back to ASRock. I can now run my 64 cores stable too with these BIOS settings. I'm running Above 4G too and you get slightly better benchmarks.

Grazie di tutto...😀

Well I did run into the 99 error again today, I didn't change anything though. Still needs more testing I guess. I tried performance run with Above 4G on / off results below (Geekbench 5 CPU and GPU Metal score) Above 4G OFF 1282 / 23881 / 61463 (average of 4 runs) Above 4G ON 1282 / 23714 / 60924 (average of 3 runs) I would say no difference in my setup.

SSDT-4-HP_XHC_P.aml.zip

Non è calcolato, generalmente è legato al modello di iGPU e all'SMBIOS usato, per cui si sa prima: 0x3E9B0007 è quello corretto per la UHD630 desktop e SMBIOS macmini8,1 e iMac19,2 solo che con l'ultimo aggiornamento di catalina, tanti schermi neri, in parte risolti usando platform-id per la UHD630 notebook 0x3E9B0000 Se vedi con CC in graphics --> ig-platform-id e clicchi sulle frecce si apre un menù dove sono presenti tutti i framebuffer e la loro associazione. Per darti una idea, questi dati vengono estrapolati dai kext di sistema dove sono presenti al loro interno nei plist queste informazioni, per dirla alla buona, ma per farti capire, poi inseriti nelle FAQ

fai come ho detto qui:https://www.macos86.it/topic/9-mappatura-porte-usb/?do=findComment&comment=76637

si ho provato, a 2500 non va, ma credo che ad alcuni finora manco avesse funzionato, con questa versione invece ora hanno la LAN finalmente funzionante.

@Driftwood @fabiosun Well close but not completely. After reading your post I jumped in and started tweaking the bios again.... Using the above settings crashes Proxmox on boot but I noticed that when enabling AER Cap a new option showed up in bios which was disabled. After also enabling that one I can stop-start-reboot and get no 99 error. Tried it now for like 8 times... 😁 So my current bios settings for ASRock TRX40 Creator: (Still using Bios 1.63 but expect no impact from that to be honest) * Start with default UEFI settings * Set XMP profile for your RAM * Tweaked FAN settings * Advanced>Onboard Devices Configuration>SR-IOV Support>Enabled * Advanced>AMD CBS>NBIO Common Options>IOMMU>Enabled * Advanced>AMD CBS>NBIO Common option>Enable AER Cap>Enable * Advanced>AMD CBS>NBIO Common option>ACS Enable>Enable I did not need to set above 4G or anything else. Let's see if this is stable but looks like we nailed it !!! 😎

Rox67er, I was missing the line below. But nothing changed. Question when proxmox loads. And it choses the version screen. Should i see anything on the screen right after?. As soon as ProxM loads it goes to black screen. Before i started the mac os build it would log to a login root screen. Now i can only get to the GUI login from a different computer. But the only thing that has change when i did this before was my card was in slot 3 not slot 1. But still black screen. Also i change the Bios setting echo efi-framebuffer.0 > /sys/bus/platform/drivers/efi-framebuffer/unbind 3 hours later: OMG......... Speechless ................ So checked everything over and over. read 25 pages of post twice. And guide i rather not say how many times. It load to the proxmox screen like it does 1,000 of time on my TV, but then goes black when it loads. This time Im like what if i choose Proxmox environment 5.4.34-1-pve instead of 5.4.41-1-pve. It goes to black and then i see the proxmox loading file screen and there it was the root login window on my screen. I was in shock. I didnt know what to do. But i rebooted the pc again to see if it was just luck. Nope it worked on older version. So when i used web to start the VM with GPU it loaded... I cant say Thank You enough for everyone help an not giving up on me. But now i have to maybe figure out why the new version of pro does not load my card. But im so happy im pouring me glass of scotch. I know i have allot to do more. But for me this was a big step.