Contribute
Register

[SUCCESS] Gigabyte Designare Z390 (Thunderbolt 3) + i7-9700K + AMD RX 580

I just tried it and it reports fine. Sometimes it takes a second to show up in About This Mac. It starts out blank and then changes to "Radeon PRO W6800 32 GB". Geekbench 5 Metal score is around 147,000 compared to 44,000 with the Vega 56.

Final Cut Pro X keeps crashing during render but I am not sure if it is due to the 10.6 update. I'll try with the Vega 56. Also the latest "Pro Video Formats 2.2.2" update in Software Update fails. I plan to update to OC 0.7.4 to see if anything changes and to prepare for Monterey. I'm on OC 6.6 right now.

Also, is it still the case where we have to choose between iGPU and dGPU? Or is it possible to have both? i.e.
- UHD 630: Thunderbolt adapter -> Display Port -> 4K60 display
- AMD W6800: No display plugged in. Used solely for compute tasks (Final Cut Pro X Render/Share GPU).
Is it possible to have two dGPUs?
- AMD Vega 56: Thunderbolt adapter -> Display Port -> 4K60 display
- AMD W6800: No display plugged in. Used solely for compute tasks (Final Cut Pro X Render/Share GPU).
Hi @pierceal ! Any luck trouble shooting FCP crashing with the W6800? Obviously FCP is a major use case for this card, so a major setback if this can't be resolved. Any other software issues, e.g, Da Vinci Resolve?
 
Hi @pierceal ! Any luck trouble shooting FCP crashing with the W6800? Obviously FCP is a major use case for this card, so a major setback if this can't be resolved. Any other software issues, e.g, Da Vinci Resolve?
Crashing appeared to be a few corrupted transcoded clips in the timeline. All is well now. I have run some tests comparing the Vega 56 and W6800. I can honestly say that I am disappointed in my purchase. I tested render time with 2min of 4K60 footage with color grading and nose reduction from three different cameras (BMPCC4K, iPhone 12 Pro, and GoPro 6). In the past these would cause the CPU to ramp to 100% until the Vega filled to 8GB. Now with the W6800, it does the same but stops at about 18GB VRAM and then basically sits idle. See the table for results. Money probably would have been better spent on a new MBP with an M1 max chip as I am still rocking a 2013 MBP which can't be updated to Monterey.

Screen Shot 2021-10-26 at 9.23.25 PM.png


I have only used Resolve once with the Vega 56 and everything including CPU ramped to 100%. My UPS actually got overloaded because of it and wouldn't stop alarming. I haven't used it since but I am now wondering if Resolve would utilize the full performance of the W6800.
 
Just updated my primary Designare Z390 from Big Sur 11.6.1 to Monterey 12.0.1. No problems experienced. Namely:
  • OpenCore 0.7.4.
  • Boot time is normal with ADATA SX8200 Pro NVMe SSD.
  • Fenvi FV-T919 WiFi and Bluetooth working normally without using BlueToolFixup.kext
  • As expected, Intel i211 Ethernet port does not connect because Monterey impairs the SmallTreeIntel82576 kext.
  • Intel i219 Ethernet port driven by IntelMausi.kext is okay.
All of my previous Monterey installations were on secondary Hackintosh systems, and all were fresh installs. This is my first in-place upgrade.

Note: Samsung 970 Evo and Evo Plus NVMe SSDs -- and possibly Samsung 980 NVMe SSDs -- may lead to significantly increased boot times due to trim-related issues. If macOS is installed on one of these drives, it may be best to wait a little while to see whether Acidanthera (developers of OpenCore) find a solution.
 
As a workaround, I'm using an SATA SSD (APFS) for the OS, other SATA SSDs (HFS+Encrypted) for most of my media, and the PCIe 970s (HFS+Encrypted) for samples and recording.

@jiffyslot @CaseySJ

I see a faster boot of Monterey 12.0.1 using a Samsung 860 EVO SSD connected to SATA Port 2 -- about 26 seconds, compared to 68 seconds with the Samsung 970 EVO @ M2M.

This was even a little faster than Big Sur 11.6.1 on the 970 EVO which took 34 seconds to boot.

The 860 EVO "trims took" 1.066 sec.
 
Crashing appeared to be a few corrupted transcoded clips in the timeline. All is well now. I have run some tests comparing the Vega 56 and W6800. I can honestly say that I am disappointed in my purchase. I tested render time with 2min of 4K60 footage with color grading and nose reduction from three different cameras (BMPCC4K, iPhone 12 Pro, and GoPro 6). In the past these would cause the CPU to ramp to 100% until the Vega filled to 8GB. Now with the W6800, it does the same but stops at about 18GB VRAM and then basically sits idle. See the table for results. Money probably would have been better spent on a new MBP with an M1 max chip as I am still rocking a 2013 MBP which can't be updated to Monterey.

View attachment 532189

I have only used Resolve once with the Vega 56 and everything including CPU ramped to 100%. My UPS actually got overloaded because of it and wouldn't stop alarming. I haven't used it since but I am now wondering if Resolve would utilize the full performance of the W6800.
Very good information. I lifted some benchmarks from recent YouTube reviews of the new M1 Pro and Max laptops in the post below. HEVC workflows are significantly improved, but ProRes workflows are mind-bogglingly improved per Rene Ritchie’s video.
 
Very good information. I lifted some benchmarks from recent YouTube reviews of the new M1 Pro and Max laptops in the post below. HEVC workflows are significantly improved, but ProRes workflows are mind-bogglingly improved per Rene Ritchie’s video.
@pierceal It would be nice to know how the 6800/XT/6900XT performed in these same workloads. I agree that this is pretty poor for the W6800.
 
Note: Samsung 970 Evo and Evo Plus NVMe SSDs -- and possibly Samsung 980 NVMe SSDs -- may lead to significantly increased boot times due to trim-related issues. If macOS is installed on one of these drives, it may be best to wait a little while to see whether Acidanthera (developers of OpenCore) find a solution.

It would honestly be so nice if someone could buy 10 different NVME ssd's and compare boot speed on opencore, but that is kinda messy job to do! :lol: But really good info to know when looking for a SSD to your hack.
 
Back
Top