Contribute
Register

Stork's MyHero II Build: ASUS ROG MAXIMUS Z370 HERO X - i7-8700K - AMD RX 580 - Thunderbolt 3

pastrychef

Moderator
Joined
May 29, 2013
Messages
16,510
Motherboard
Gigabyte Z390 M Gaming
CPU
i9-9900K OC'd @ 5.0GHz
Graphics
Vega 56 (Bios flashed to 64)
Mac
  1. MacBook
  2. Mac Pro
Classic Mac
  1. iBook
  2. Power Mac
  3. PowerBook
Mobile Phone
  1. iOS
Hi! I just ran a Cinebench on my OSX 10.14.3 system and Vega 56. I got 88.59FPS.
I checked my old benchmark on 10.13.5, and there I got 146.90FPS. Any ideas what could be the difference?

Now, I'm running the graphics card OOB. So I did not add any kext for it.

Cinebench is a very bad benchmark for GPUs. With a powerful video card, your benchmark results will almost certainly be bottlenecked by CPU.

I just ran Cinebench on my Vega 56 and macOS Mojave 10.14.3 and got 177.15fps.

Therefore, in your situation, the first place I would check would be to see if the CPU is running optimally.
 
Joined
Sep 27, 2010
Messages
35
Motherboard
ASUS Z370 ROG MAXIMUS X HERO
CPU
i7-8700K
Graphics
RX VEGA 56
Mac
  1. MacBook
  2. MacBook Air
  3. MacBook Pro
  4. Mac mini
Mobile Phone
  1. iOS
Now i got 139.97fps. I had a "hommade" fusiondrive with 2Xraid0 4TB disk and 500GB ssd that i used. I removed those 3 disks and all is working great again! :)

Thanks for help fast answers! you guys rock!
 
Joined
Dec 19, 2016
Messages
87
Motherboard
ASUS ROG MAXIMUS X HERO Z370
CPU
i7-8700K
Graphics
RX 580
Mac
  1. MacBook Pro
  2. Mac Pro
Mobile Phone
  1. iOS
Now i got 139.97fps. I had a "hommade" fusiondrive with 2Xraid0 4TB disk and 500GB ssd that i used. I removed those 3 disks and all is working great again! :)

Thanks for help fast answers! you guys rock!

Same MB and CPU - my RX580 gives 148.17fps.
 
Joined
Sep 27, 2010
Messages
35
Motherboard
ASUS Z370 ROG MAXIMUS X HERO
CPU
i7-8700K
Graphics
RX VEGA 56
Mac
  1. MacBook
  2. MacBook Air
  3. MacBook Pro
  4. Mac mini
Mobile Phone
  1. iOS
Has anyone tried to activate both iGPU and dGPU on this setup? I have final cut pro x crashing every time I use it and in this thread someone says that FCPX uses both GPU's so i suspect it needs the iGPU for some rendering because i get the spinning ball after few minutes of usage. I activated iGPU in BIOS. It runs fine but I notice the boot time is much longer than before.
 
Joined
Jul 7, 2010
Messages
120
Motherboard
ASUS ROG MAXIMUS HERO X Z370
CPU
i9-9900KS
Graphics
RX 580
Mac
  1. MacBook Air
Classic Mac
  1. PowerBook
Mobile Phone
  1. iOS
Has anyone tried to activate both iGPU and dGPU on this setup? I have final cut pro x crashing every time I use it and in this thread someone says that FCPX uses both GPU's so i suspect it needs the iGPU for some rendering because i get the spinning ball after few minutes of usage. I activated iGPU in BIOS. It runs fine but I notice the boot time is much longer than before.
Yeah I have both running together. Just used the BIOS settings from @pastrychef from this post https://www.tonymacx86.com/threads/...wi-fi-ac-build-w-i9-9900k-amd-vega-56.239969/ then removed all DSDT patches and anything to do with graphics injection / frame buffers as recommended on the whatevergreen GitHub. Whatevergreen seems to just do its thing and correctly inject my iGPU as headless with no display, but allowing for full hardware acceleration, with no sleep issues or anything. I checked acceleration using the free trial https://www.macxdvd.com/?ttsoft=vpmac-3.2-about-unreg
 

Attachments

  • Screen Shot 2019-02-26 at 08.04.36.png
    Screen Shot 2019-02-26 at 08.04.36.png
    95.2 KB · Views: 25
Joined
Sep 27, 2010
Messages
35
Motherboard
ASUS Z370 ROG MAXIMUS X HERO
CPU
i7-8700K
Graphics
RX VEGA 56
Mac
  1. MacBook
  2. MacBook Air
  3. MacBook Pro
  4. Mac mini
Mobile Phone
  1. iOS
Yeah I have both running together. Just used the BIOS settings from @pastrychef from this post https://www.tonymacx86.com/threads/...wi-fi-ac-build-w-i9-9900k-amd-vega-56.239969/ then removed all DSDT patches and anything to do with graphics injection / frame buffers as recommended on the whatevergreen GitHub. Whatevergreen seems to just do its thing and correctly inject my iGPU as headless with no display, but allowing for full hardware acceleration, with no sleep issues or anything. I checked acceleration using the free trial https://www.macxdvd.com/?ttsoft=vpmac-3.2-about-unreg
Im trying to load the whatevergreen Kext but it does not seem to load. Also the Hackintool does not recognice the PlatformID. What System definition are you running? There is something wrong in my setup. I changed to 19,1 to be able to export videos from FCPX.
 

Attachments

  • Screenshot 2019-02-27 at 09.30.54.png
    Screenshot 2019-02-27 at 09.30.54.png
    128.7 KB · Views: 30
Joined
Sep 27, 2010
Messages
35
Motherboard
ASUS Z370 ROG MAXIMUS X HERO
CPU
i7-8700K
Graphics
RX VEGA 56
Mac
  1. MacBook
  2. MacBook Air
  3. MacBook Pro
  4. Mac mini
Mobile Phone
  1. iOS
Im trying to load the whatevergreen Kext but it does not seem to load. Also the Hackintool does not recognice the PlatformID. What System definition are you running? There is something wrong in my setup. I changed to 19,1 to be able to export videos from FCPX.
Now it seems to work! I had not checked the updated guide in Post 1, so I missed that there was this new MultiBeast with whatevergreen support. I'm using system definition iMac 18,3. I have iGPU (headless) and Vega56 active at the same time. Only thing I need to fix now is iMessage. Thanks for the help!

Edit: OK. I was too fast to write here. Both cards are active but when running an export from Final Cut Pro X the machine reboots. So, something is not correct. Any ideas?

Edit2: I was able to fix this crashing FCPX by creating a patch in hackingtool following this guide. I open hackingtool, selected FrameBuffer MacOS 10.14. PlatformID: 0x3E910003 then clicked patch and Generate Patch. I pasted following to the Devices section in plist.conf and rebooted. Now i run BruceX in 14 sec. and have iGPU enabled with Vega56

Code:
        <key>Properties</key>
        <dict>
            <key>PciRoot(0x0)/Pci(0x2,0x0)</key>
            <dict>
                <key>AAPL,ig-platform-id</key>
                <data>
                AwCRPg==
                </data>
            </dict>
        </dict>
 
Last edited:
Joined
Jul 7, 2010
Messages
120
Motherboard
ASUS ROG MAXIMUS HERO X Z370
CPU
i9-9900KS
Graphics
RX 580
Mac
  1. MacBook Air
Classic Mac
  1. PowerBook
Mobile Phone
  1. iOS
Now it seems to work! I had not checked the updated guide in Post 1, so I missed that there was this new MultiBeast with whatevergreen support. I'm using system definition iMac 18,3. I have iGPU (headless) and Vega56 active at the same time. Only thing I need to fix now is iMessage. Thanks for the help!

Edit: OK. I was too fast to write here. Both cards are active but when running an export from Final Cut Pro X the machine reboots. So, something is not correct. Any ideas?

Edit2: I was able to fix this crashing FCPX by creating a patch in hackingtool following this guide. I open whatevergreen, selected FrameBuffer MacOS 10.14. PlatformID: 0x3E910003 then clicked patch and Generate Patch. I pasted following to the Devices section in plist.conf and rebooted. Now i run BruceX in 14 sec. and have iGPU enabled with Vega56

Code:
        <key>Properties</key>
        <dict>
            <key>PciRoot(0x0)/Pci(0x2,0x0)</key>
            <dict>
                <key>AAPL,ig-platform-id</key>
                <data>
                AwCRPg==
                </data>
            </dict>
        </dict>
Glad you seem to have it working now. I am also on iMac 18,3 but am still not injecting any graphics properties or GPU DSDT patches in Clover. Whatevergreen seems to be doing what it says in its manuals and correctly identifying my setup and assigning the correct platform ID.

It took me ages to get working as well but I thought that was because I am still running High Sierra (for Pro Tools compatibility) and it was only when I replaced AppleIntelCFLGraphicsFramebuffer.kext with the version from 10.14 that it correctly recognised my UHD630 in Hackintool. I Just checked and it is also saying I have a Platform ID 0x3E910003, and has all the connectors listed as Dummy so I guess that says whatevergreen is handling it all pretty well.
 

Attachments

  • Screen Shot 2019-02-27 at 12.10.18.png
    Screen Shot 2019-02-27 at 12.10.18.png
    41.5 KB · Views: 23
Joined
Sep 27, 2010
Messages
35
Motherboard
ASUS Z370 ROG MAXIMUS X HERO
CPU
i7-8700K
Graphics
RX VEGA 56
Mac
  1. MacBook
  2. MacBook Air
  3. MacBook Pro
  4. Mac mini
Mobile Phone
  1. iOS
Glad you seem to have it working now. I am also on iMac 18,3 but am still not injecting any graphics properties or GPU DSDT patches in Clover. Whatevergreen seems to be doing what it says in its manuals and correctly identifying my setup and assigning the correct platform ID.

It took me ages to get working as well but I thought that was because I am still running High Sierra (for Pro Tools compatibility) and it was only when I replaced AppleIntelCFLGraphicsFramebuffer.kext with the version from 10.14 that it correctly recognised my UHD630 in Hackintool. I Just checked and it is also saying I have a Platform ID 0x3E910003, and has all the connectors listed as Dummy so I guess that says whatevergreen is handling it all pretty well.
Your iGPU says Mobile while mine says Desktop. I think i got the missing parts from selecting the frame buffer MaOS 10.14.
 

Attachments

  • Screenshot 2019-02-27 at 13.23.04.png
    Screenshot 2019-02-27 at 13.23.04.png
    136.1 KB · Views: 41
Joined
Jul 7, 2010
Messages
120
Motherboard
ASUS ROG MAXIMUS HERO X Z370
CPU
i9-9900KS
Graphics
RX 580
Mac
  1. MacBook Air
Classic Mac
  1. PowerBook
Mobile Phone
  1. iOS
Your iGPU says Mobile while mine says Desktop. I think i got the missing parts from selecting the frame buffer MaOS 10.14.
Tried booting with your platform ID clover devices patch and it is exactly the same as letting whatevergreen injection on the fly - Still says UHD630 (Mobile). Wonder if that is because I am on High Sierra rather than Mojave, or because I have not updated the Framebuffer.kext since version 10.14.0. I will pull over the 10.14.3 version from my MacBook when I get the time just out of curiosity! Not like I even do any video encoding, but just like getting things to work :)
 
Top