Glasgood's macOS Mojave [SUCCESS][GUIDE] for Aorus Z390 Pro

[AudioGod]

8 minutes ago, larabee said:

 

I'm lost to where the differences are haha. Maybe the cache is changed when you change your EFI and that solves everything? 

Anyway, we're up and running now. So, CHEER !!!! 

 

I feel like @glasgood and many members in contributing in this thread may have create the best comprehensive guide for Gigabyte Z390 Aorus Pro that ever existed. 

 

Not as lost as I am/was buddy lol

 

And yes i could not agree with you more @glasgood and yourself especially have made this thread easily the best one out there for any Gigabyte Z390 pro and most other Aorus boards too. 

I'm glad I can do whatever little I can to help on here too and will continue to do so. I'm not the best with clover but I'm getting there but when it comes to hardware, any form of OS and fault finding that's when I'm good to go...lol

I think myself and @larabee have become Glasgood's minions somewhat...hahaha (I bow too you good sir)

Edited July 29, 2019 by AudioGod

[AudioGod]

17 minutes ago, larabee said:

 

I'm lost to where the differences are haha. Maybe the cache is changed when you change your EFI and that solves everything? 

Anyway, we're up and running now. So, CHEER !!!! 

 

I feel like @glasgood and many members in contributing in this thread may have create the best comprehensive guide for Gigabyte Z390 Aorus Pro that ever existed. 

 

 

BTW, @glasgood @AudioGod , you ever see this thing: Bool ATIController Test VRAM....

 

 

I'm not seeing any of that on my boot up bud.

[allanau]

18 hours ago, glasgood said:

 

It should work. The USB layout on the back of the board is different, so you will have to create your own USB ( SSDT or USBports.kext ) fix using hackintool. 

 

 

 OK thanks man... I am going to give it a try... I am new to Hackintosh so I think I kind of get the basics but yeah the motherboard here in Canada is on sale and its about $50 difference.

[AudioGod]

@larabee

Hi bud, I just noticed that the efi you gave to me is still using the OsxAptioFix2Drv-free2000 did you go back to it or is that a mistake/older efi of yours and if so should I switch back to OsxAptioFix3Drv?

[larabee]

1 hour ago, AudioGod said:

@larabee

Hi bud, I just noticed that the efi you gave to me is still using the OsxAptioFix2Drv-free2000 did you go back to it or is that a mistake/older efi of yours and if so should I switch back to OsxAptioFix3Drv?

 

You can switch back and forth, I was in the middle of testing my vega with the strange Bool ATI lines so I just pop in the free2000 to see if fix3drv is the culprit. 

[pkdesign]

I am lost. So where are we with memory fix drivers? I've tried all of them with and without different slide numbers and nothing but free2000 works. I haven’t updated my BIOS to 10, am in the middle of production and definitely need my computer to work.

 

And BTW, trying to calculate slide values is unbelievably confusing. I've read and re-read different methods and all are confusing. https://github.com/wmchris/DellXPS15-9550-OSX/blob/10.13/Additional/slide_calc.md comes closet to making sense but I am still not exactly sure of what I am doing. And almost nothing here makes any sense. I have been at this for days:

 

[AudioGod]

14 minutes ago, pkdesign said:

I am lost. So where are we with memory fix drivers? I've tried all of them with and without different slide numbers and nothing but free2000 works. I haven’t updated my BIOS to 10, am in the middle of production and definitely need my computer to work.

 

And BTW, trying to calculate slide values is unbelievably confusing. I've read and re-read different methods and all are confusing. https://github.com/wmchris/DellXPS15-9550-OSX/blob/10.13/Additional/slide_calc.md comes closet to making sense but I am still not exactly sure of what I am doing. And almost nothing here makes any sense. I have been at this for days:

 

 

OsxAptioFix2Drv-free2000 in genreal works just fine but can throw up errors on your memory using memtest but I have to add that in the real world your system will run just fine with no problems.

if your using a vega 56/64 then OsxAptioFix3Drv works just as well too and doesn't chuck any errors when testing with memtest, I'm personally still testing OsxAptioFix3Drv with my vega 56 but until @glasgood finds a way to get it to work with a rx580 stick with the OsxAptioFix2Drv-free2000.

 

As for Slide, all I know is with a gigabyte z390 pro slide=0 regardless.

 

 

Edited July 31, 2019 by AudioGod

[glasgood]

2 minutes ago, pkdesign said:

I am lost. So where are we with memory fix drivers? I've tried all of them with and without different slide numbers and nothing but free2000 works. I haven’t updated my BIOS to 10, am in the middle of production and definitely need my computer to work.

 

And BTW, trying to calculate slide values is unbelievably confusing. I've read and re-read different methods and all are confusing. https://github.com/wmchris/DellXPS15-9550-OSX/blob/10.13/Additional/slide_calc.md comes closet to making sense but I am still not exactly sure of what I am doing. And almost nothing here makes any sense. I have been at this for days:

 

 

It seems that if using SMBIOS for iMac 19,1 then you will have to stick with OsxAptoFixDrv-free2000, but if you are using SMBIOS for iMac Pro 1,1 then you can use OsxAptioFix3Drv.  If switching to SMBIOS for iMac Pro then you will have to disable Internal Graphics in BIOS. 

If using AMD Vega card then you should have a perfect set up using SMBIOS for iMac Pro. If using a RX 580 card with SMBIOS for iMac Pro then wake will not function properly. 

 

I tested other memory fix alternatives and received "Couldn't allocate runtime area" error. 

Also tired different permutations of the following BIOS settings without success.

BIOS version F10

• CSM ( Enabled & Disabled )

• Vt-d ( Enabled & Disabled )

• XHCI ( Enabled & Disabled )

• XMP ( Profile 1 and none )

• DVMT Pre-Allocated ( 128 & 256 )

• DVMT Total GFX ( 128, 256, MAX )

• Other OS & Win 8 / 10

I also enabled CFG Lock (MSR 0xE2 write protection) in BIOS, interestingly the procedure including offset to unlock CFG is exact same as the Designare. ( 0x5C1 and 0x0 )

Black screen on wake only happens with SMBIOS iMacPro 1,1 when using RX 580, otherwise  sleep is perfect when using SMBIOS 19,1 with RX580.

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

[larabee]

12 minutes ago, pkdesign said:

I am lost. So where are we with memory fix drivers? I've tried all of them with and without different slide numbers and nothing but free2000 works. I haven’t updated my BIOS to 10, am in the middle of production and definitely need my computer to work.

 

And BTW, trying to calculate slide values is unbelievably confusing. I've read and re-read different methods and all are confusing. https://github.com/wmchris/DellXPS15-9550-OSX/blob/10.13/Additional/slide_calc.md comes closet to making sense but I am still not exactly sure of what I am doing. And almost nothing here makes any sense. I have been at this for days

 

 

You can flip through several pages before where @AudioGod and I tried different drivers with iMac Pro 1.1 SMBIOS. OsxAptioFix3Drv works best for both of us.

@glasgood has trouble with sleep on iMac Pro running Rx580, so if sleep is not an issue, then you can try it. 

My experience with iMac Pro SMBIOS has been very positive, I've seen increase in performance in both light and heavy workflow on Vega graphics and slight improvement with RX570/580 

 

[glasgood]

3 minutes ago, AudioGod said:

 

OsxAptioFix2Drv-free2000 in genreal works just fine but can throw up errors on your memory using memtest but I have to add that in the real world your system will run just fine with no problems.

if your using a vega 56/64 then OsxAptioFix3Drv works just well too and doesn't chuck any errors when testing with memtest, I'm personally still testing OsxAptioFix3Drv with my vega 56 but until @glasgood finds a way to get it to work with a rx580 stick with the OsxAptioFix2Drv-free2000.

 

As for Slide, all I know is with a gigabyte z390 pro slide=0 regardless.

 

 

 

@AudioGod

 

A weird thing happened today, while testing OsxAptioFixDrv. I went into BIOS and while testing DVMT Pre-Allocated and DVMT Total GFX with different memory sizes, my computer rebooted from BIOS version F10  back into into BIOS version F5. I had to clear CMOS on motherboard and computer was able to boot back with BIOS v F10.  And now when using OsxAptioFix3Drv my hack stops during Clover boot screen " End random seed " with exact same setting that used to work with OsxAptioFix3Drv. At the moment I'm no longer testing as the switching between different memory drivers is causing havoc with BIOS. 

 

 

 

 

 

 

[larabee]

2 minutes ago, glasgood said:

 

@AudioGod

 

A weird thing happened today, while testing OsxAptioFixDrv. I went into BIOS and while testing DVMT Pre-Allocated and DVMT Total GFX with different memory sizes, my computer rebooted from BIOS version F10  back into into BIOS version F5. I had to clear CMOS on motherboard and computer was able to boot back with BIOS v F10.  And now when using OsxAptioFix3Drv my hack stops during Clover boot screen " End random seed " with exact same setting that used to work with OsxAptioFix3Drv. At the moment I'm no longer testing as the switching between different memory drivers is causing havoc with BIOS. 

 

 

 

 

That's exactly what I have encountered and reported in several other posts in this thread about BIOS resetting itself. The only difference is I have problem with the free2000 driver using your EFI, but after several bios flashing, the problem eventually goes away.

I assume your motherboard is shipped with F5 then you updated it gradually to F10. Mine is shipped with F8, so it reverted back to F8 when that happen.

[glasgood]

5 minutes ago, larabee said:

 

That's exactly what I have encountered and reported in several other posts in this thread about BIOS resetting itself. The only difference is I have problem with the free2000 driver using your EFI, but after several bios flashing, the problem eventually goes away.

I assume your motherboard is shipped with F5 then you updated it gradually to F10. Mine is shipped with F8, so it reverted back to F8 when that happen.

 

When you mentioned BIOS resetting, I thought your BIOS was resetting back to default settings and not retaining your new BIOS settings. Yeah, my motherboard shipped with F5. I'm wondering / suspecting drivers cause havoc to BIOS firmware when persistently changing drivers and BIOS settings, but if you find a driver that works and don't change BIOS settings then maybe things are different and system and BIOS firmware stays stable. I have read people have been using OsxAptoFixDrv-free2000 for a number of years and have not encountered any problem. I'm going to stay with OsxAptoFixDrv-free2000 and not mess with BIOS settings for the foreseeable future until something is certain to work with the majority of Z390 motherboards.  I do find the very late news about  OsxAptoFixDrv-free2000 strange considering how long it has been in use,   I have yet to read about the numerous users who have bricked their system using it. 

 

 

 

 

 

 

 

 

[pkdesign]

12 minutes ago, AudioGod said:

 

OsxAptioFix2Drv-free2000 in genreal works just fine but can throw up errors on your memory using memtest but I have to add that in the real world your system will run just fine with no problems.

if your using a vega 56/64 then OsxAptioFix3Drv works just as well too and doesn't chuck any errors when testing with memtest, I'm personally still testing OsxAptioFix3Drv with my vega 56 but until @glasgood finds a way to get it to work with a rx580 stick with the OsxAptioFix2Drv-free2000.

 

As for Slide, all I know is with a gigabyte z390 pro slide=0 regardless.

 

 

apianti has freaked us out with his post. I understand his concerns, especially since he wrote the driver, but free2000 is working 100% for me with no apparent errors.

 

I have a RX570 in my hack.

 

40 minutes ago, glasgood said:

 

 

It seems that if using SMBIOS for iMac 19,1 then you will have to stick with OsxAptoFixDrv-free2000, but if you are using SMBIOS for iMac Pro 1,1 then you can use OsxAptioFix3Drv.  If switching to SMBIOS for iMac Pro then you will have to disable Internal Graphics in BIOS. 

If using AMD Vega card then you should have a perfect set up using SMBIOS for iMac Pro. If using a RX 580 card with SMBIOS for iMac Pro then wake will not function properly. 

 

I tested other memory fix alternatives and received "Couldn't allocate runtime area" error. 

Also tired different permutations of the following BIOS settings without success.

BIOS version F10

• CSM ( Enabled & Disabled )

• Vt-d ( Enabled & Disabled )

• XHCI ( Enabled & Disabled )

• XMP ( Profile 1 and none )

• DVMT Pre-Allocated ( 128 & 256 )

• DVMT Total GFX ( 128, 256, MAX )

• Other OS & Win 8 / 10

I also enabled CFG Lock (MSR 0xE2 write protection) in BIOS, interestingly the procedure including offset to unlock CFG is exact same as the Designare. ( 0x5C1 and 0x0 )

Black screen on wake only happens with SMBIOS iMacPro 1,1 when using RX 580, otherwise  sleep is perfect when using SMBIOS 19,1 with RX580.

I really want to keep my 19,1 set up since that is what the specs of my hack is closest too.

 

I'd like to understand the benefit of unlocking CFG Lock. Not even sure where to unlock. Is that a BIOS setting? Currently this is what I have:

 

0:100  0:000  MSR 0x35               80010
0:100  0:000   TSC/CCC Information Leaf:
0:100  0:000    numerator     : 300
0:100  0:000    denominator   : 2
0:100  0:000   Calibrated ARTFrequency: 24011218
0:100  0:000  MSR 0xE2 before patch 1E008000
0:100  0:000  MSR 0xE2 is locked, PM patches will be turned on
0:100  0:000  MSR 0xCE              08080838_F1012400

 

Looks locked to me.

[glasgood]

Just now, pkdesign said:

apianti has freaked us out with his post. I understand his concerns, especially since he wrote the driver, but free2000 is working 100% for me with no apparent errors.

 

I have a RX570 in my hack.

 

I really want to keep my 19,1 set up since that is what the specs of my hack is closest too.

 

I'd like to understand the benefit of unlocking CFG Lock. Not even sure where to unlock. Is that a BIOS setting? Currently this is what I have:

 

0:100  0:000  MSR 0x35               80010
0:100  0:000   TSC/CCC Information Leaf:
0:100  0:000    numerator     : 300
0:100  0:000    denominator   : 2
0:100  0:000   Calibrated ARTFrequency: 24011218
0:100  0:000  MSR 0xE2 before patch 1E008000
0:100  0:000  MSR 0xE2 is locked, PM patches will be turned on
0:100  0:000  MSR 0xCE              08080838_F1012400

 

Looks locked to me.

 

CFG lock is not visible in BIOS settings, you need to use UEFITool to find the CFG lock parameter and then replace the offset using modGrubShell.

 

 

[AudioGod]

40 minutes ago, glasgood said:

 

@AudioGod

 

A weird thing happened today, while testing OsxAptioFixDrv. I went into BIOS and while testing DVMT Pre-Allocated and DVMT Total GFX with different memory sizes, my computer rebooted from BIOS version F10  back into into BIOS version F5. I had to clear CMOS on motherboard and computer was able to boot back with BIOS v F10.  And now when using OsxAptioFix3Drv my hack stops during Clover boot screen " End random seed " with exact same setting that used to work with OsxAptioFix3Drv. At the moment I'm no longer testing as the switching between different memory drivers is causing havoc with BIOS. 

 

 

 

 

 

 

 

That is the gigabytes dual bios kicking in, so when the normal bios went wrong (probably due to memory allocation) it reverts to the backup bios. just pull the battery with the mains disconnected and wait a minute and then put it all back and it will revert back. 

Its all got bait messy over all of this...lol....I was curious so I downloaded [url="http://www.insanelymac.com/forum/topic/279450-why-insanelymac-does-not-support-tonymacx86/"]#####[/url] to see what that used as standard and sure enough its the OsxAptioFix2Drv-free2000.efi so it just goes to show what just about everybody sticking with at this point.

Edited July 31, 2019 by AudioGod

[glasgood]

1 minute ago, AudioGod said:

 

That is the gigabytes dual bios kicking in, so when the normal bios went wrong (probably due to memory allocation) it reverts to the backup bios. just pull the battery with the mains disconnected and wait a minute and then put it all back and it will revert back. 

Its all got bait messy over all of this...lol....I was curious so I downloaded [url="http://www.insanelymac.com/forum/topic/279450-why-insanelymac-does-not-support-tonymacx86/"]#####[/url] to see what that used as standard and sure enough its the OsxAptioFix2Drv-free2000.efi so it just goes to show what just about everybody sticking with at this point.

 

The Gigabyte dual bios did cross my mind, I had a look at the Aorus Pro Hand book and could not find any mention of it.   I just short circuited to two CLR_CMOS pins on the board to do the reset. 

 

 

[larabee]

9 minutes ago, AudioGod said:

 

That is the gigabytes dual bios kicking in, so when the normal bios went wrong (probably due to memory allocation) it reverts to the backup bios. just pull the battery with the mains disconnected and wait a minute and then put it all back and it will revert back. 

Its all got bait messy over all of this...lol....I was curious so I downloaded$#$%&* TONY to see what that used as standard and sure enough its the OsxAptioFix2Drv-free2000.efi so it just goes to show what just about everybody sticking with at this point.

 

@glasgood @AudioGod Switching back and forth actually causing my Vega to freak out and now I'm testing the stability of it again since it constantly fail video memory check. Now it started to develop weird artifact in windows. 

I'm able to reproduce the Bool ATI Controller Test VRAM Failed  just by switching back and forth the driver + SMBIOS definition. So be aware of that. 

 

About the bios reverting back to original version when it's shipped, I think it totally makes sense because dual bios actually retain the factory bios in case of disaster. I noticed that on my old board too when I messed up the flash. 

Edited July 31, 2019 by larabee

[AudioGod]

7 minutes ago, glasgood said:

 

The Gigabyte dual bios did cross my mind, I had a look at the Aorus Pro Hand book and could not find any mention of it.   I just short circuited to two CLR_CMOS pins on the board to do the reset. 

 

 

 

Yeah its in there but they dont go into detail in the manual. it in every single gigabyte Aorus board as far as I know.

Next time make sure you pull the battery before you short the pins just to be sure buddy.

 

@larabee @glasgood Im sticking with OsxAptioFix3Drv for now as its giving me the best results and no memory errors but I'm doing a build for somebody else tomorrow and I will probably go down the OsxAptioFix2Drv-free2000.efi road just to be safe, as for it busting hardware...I have not read a single thing about anybody getting kaboomed so il take that with a pinch of salt..lol

Edited July 31, 2019 by AudioGod

[larabee]

4 minutes ago, AudioGod said:

 

@larabee @glasgood Im sticking with OsxAptioFix3Drv for now as its giving me the best results and no memory errors but I'm doing a build for somebody else tomorrow and I will probably go down the OsxAptioFix2Drv-free2000.efi road just to be safe, as for it busting hardware...I have not read a single thing about anybody getting kaboomed so il take that with a pinch of salt..lol

 

@AudioGod I'm buying another identical system to use free2000 and compare with OsxAptioFix3Drv and possibly buying new vega just in case.

 

I can come to a safe conclusion that the drivers themselves do NOT cause any hardware problems, SWITCHING DRIVERS BACK AND FORTH, on the other hand, may cause serious issues. 

[AudioGod]

2 minutes ago, larabee said:

 

@AudioGod I'm buying another identical system to use free2000 and compare with OsxAptioFix3Drv and possibly buying new vega just in case.

 

I can come to a safe conclusion that the drivers themselves do NOT cause any hardware problems, SWITCHING DRIVERS BACK AND FORTH, on the other hand, may cause serious issues. 

 

@larabee Yeah for sure, You have to do a full shut down when flicking between them because your changing the way the memory allocation sets about everytime you flick from one to other. A full shutdown should avoid that problem though as it clears out the system properly.

[larabee]

11 minutes ago, AudioGod said:

Yeah for sure, You have to do a full shut down when flicking between them because your changing the way the memory allocation sets about everytime you flick from one to other. A full shutdown should avoid that problem though as it clears out the system properly.

I've made the mistake of just restarting and that causes a world of hurt haha. 

[glasgood]

@larabee @AudioGod

 

May be I should just rename  OsxAptioFix2Drv-free2000.efi as OsxAptioFixDrv.efi inside EFI folders, then mostly everyone will be happy. As they say  "ignorance is bliss"  

[pkdesign]

1 hour ago, glasgood said:

 

CFG lock is not visible in BIOS settings, you need to use UEFITool to find the CFG lock parameter and then replace the offset using modGrubShell.

 

 

Oh no! I'm not messing with that!

[hackinbot]

4 hours ago, glasgood said:

It seems that if using SMBIOS for iMac 19,1 then you will have to stick with OsxAptoFixDrv-free2000, but if you are using SMBIOS for iMac Pro 1,1 then you can use OsxAptioFix3Drv.  If switching to SMBIOS for iMac Pro then you will have to disable Internal Graphics in BIOS. 

If using AMD Vega card then you should have a perfect set up using SMBIOS for iMac Pro. If using a RX 580 card with SMBIOS for iMac Pro then wake will not function properly. 

 

I tested other memory fix alternatives and received "Couldn't allocate runtime area" error. 

Black screen on wake only happens with SMBIOS iMacPro 1,1 when using RX 580, otherwise  sleep is perfect when using SMBIOS 19,1 with RX580.

 

I'm using OsxAptioFix3Drv with a Sapphire Nitro+ RX 580 4GB and sleep + wake works perfectly. SMBIOS iMacPro1,1. UHD630 is disabled in BIOS.

 

Only the DisplayPorts work on this card (I think because WhateverGreen is selecting the wrong framebuffer). I have dual monitors set up with the DisplayPorts. Both sleep and wake perfectly.

 

How can I help troubleshoot?

Edited July 31, 2019 by hackinbot

[glasgood]

49 minutes ago, hackinbot said:

I'm using OsxAptioFix3Drv with a Sapphire Nitro+ RX 580 4GB and sleep + wake works perfectly. SMBIOS iMacPro1,1. UHD630 is disabled in BIOS.

 

Only the DisplayPorts work on this card (I think because WhateverGreen is selecting the wrong framebuffer). I have dual monitors set up with the DisplayPorts. Both sleep and wake perfectly.

 

How can I help troubleshoot?

 

Maybe, possibly the Sapphire Nitro was officially supported along with the Sapphire Pulse by Apple in their eGPU developer kit.  I did try a custom SSDT for my RX580 and also added in the part number for one of the supported RX-580 from the dev kit into the SSDT and the sleep issue still remained. If you can test my Clover folder I would appreciate that. My SSDT should give you the proper Orinoco framebuffer for your RX 580. Clover attached below, it includes the SSDT for RX580, also I will attach a secondary SSDT for you to test on your RX580.

 

CLOVER.zip

 

SSDT-RX-580-2.aml

 

 

 

 

Edited July 31, 2019 by glasgood