AudioGod's Aorus Z390 Pro Patched DSDT Mini Guide and Discussion

[stavidawg]

19 hours ago, Tiem said:

The EFI released works perfectly provided you set up your system as he suggested. Get a proper macOS installer without errors. This is crucial as people use all sorts of dumb ways to make the stick, either pulling an incompatible version or an assortment of errors that either fubar the install process or leave you with a non-working system.

 

Stop and take a step back. Make a USB installer on a real macOS running the latest OS. Ensure it's good and error free. Update your BIOS to the latest revision (F12d for the Pro and F12c for the Pro WIFI, both work with this EFI).

 

Set up the BIOS properly. You need to first enable the dGPU, save settings and reboot, then go right back into the BIOS and finish setting it up. Only then will it list the following settings:

 

• Settings -> IO Ports -> DVMT Pre-Allocated -> 64M

• Settings -> IO Ports -> DVMT Total GFX0-Allocated -> 256M

• Settings -> IO Ports -> Aperture Size -> 256MB

 

That's mostly it. Unplug all your hardware that's not necessary. If you have some kind of radiator cooling system, then you may need to do some fiddling as there are known issues with lots of fancy cooling (by fancy I mean coming from traditional air cooling like the Notcua DH-14). macOS doesn't support anything other than traditional air cooling systems (fan + heatsink).

 

You're throwing up a ton of info, way too much. I get what you're trying to do, but this EFI is bulletproof. You just toss in your EFI partition and you're good. Truly.

 

Did as you said, and for some bizarre reason keyboard and mouse just won't make the connection. Tried this on two separate usb drives having clean install of the the newest Catalina installer.

 

On a hunch (see below) I added USBInjectALL.ktext to the EFI and Viola. This leads me to believe the DSDT is not taking correctly on my build for some bizzare reason?

 

I found that my bluetooth also doesn't work, even though I'm using a BCM94360CS2 card which should/has work OOB (adaptor installed in PCIEX 1_3 just as Audio God).

 

I ran Mojave stable for a long time, and then recently tried to update to Catalina and had many issues. I did find an EFI folder that while "made" for Aorus z390 still used usbinject all which I wanted to get away from in the first place. The reason I am looking for new EFI is because when I tried to update to 10.15.3, the update failed and made my Catalina no longer bootable.

 

I would like to thank all you for you help, but it seems my MOBO is perhaps just an outlier. 

 

 

[Tiem]

OpenCore 0.5.5 was just released. Runs great outside of it messing up the boot screen resolution (both Windows and macOS are under resolution and stretched). YMMV.

 

Get to updating

[juan e. jot]

19 hours ago, Tiem said:

This is accomplished by turning off wifi in the BIOS. It effectively turns the board into a regular Pro. No difference.

Thanks for the tip, Tiem! I’ll try that vs clambering further around in the config.plist, once I get macOS up & running. For the other OSes, I’ve gotten Linux to use Broadcom drivers before, and I’m sure Windows will either auto-download & apply such, or I’ll just manually get it from Fenvi’s website.
The Pro is what I had planned on anyway for Handoff & Continuity; both NewEgg & Amazon just had a deal with the WiFi for $10 cheaper for a while, so I jumped on it (deal over now).
 

Edited February 4, 2020 by juan e. jot
Remove weird double-post

[Tiem]

Read me reply to stavidawg above. You must ensure your USB installer is free of errors and the correct one for your machine. Pulling it from a real Mac is the best way to do this. If you used any other method, the problems you face are most likely a bad installer.

 

The EFI can be tested just by booting up the USB installer. Once you replace the default EFI with the one from AudioGod, and boot using the stick, then you are essentially already running it. If all your peripherals are working during the install, then there is no issues with the EFI. It's you. Something on your end.

 

If I had to guess, you had too much clutter. There is no way to disable the M.2 slots on this board. And if you installed other OSes before macOS, then you may have to deal with errors or complications. I installed macOS first but when I installed Windows (onto a separate SATA SSD), it threw it's EFI onto the M.2 partition that macOS had created. Kinda a pain, but it illustrates how complications can easily arise.

 

Unplug everything. If you have other OSes installed on other physical drives, unplug them. Even the M.2 slot, you would do much better if you took the card out to avoid collisions. Triple booting can be a pain as each boot loader has it's own quirks and set of pitfalls.

 

Also, please add your hardware details to your signature.

 

 

[juan e. jot]

21 hours ago, juan e. jot said:

attempting to install from the macOS Catalina Installer USB with AudioGod’s very considerate provision of a UHD630 EFI gets somewhere between 1/2 and 2/3 through the progress bar and pops up a “forbidden” or “prohibited” symbol & hangs indefinitely. Adding “-v” as a boot arg so I can see in verbose mode what’s going on just pixelates all the text out under the symbol when it pops up, yielding no info.

 

Further research confirms that building the installer from a gibmacos-downloaded copy of 10.15.3 (with AudioGod’s unmodified UHD630 EFI in the EFI partition of the installer USB stick) yields the same “forbidden” or “prohibited” symbol about 1/2 to 2/3 through the progress bar. Interestingly, when I add “-v” to the boot args to get an output of what it’s doing, the symbol still pixelates the text “under” it, but these couple of times (see below) I tried it, I let it run for long enough to see some text continuing to come across non-pixelated in patches, but not an entire line to read, and the text definitely continued to scroll (very slowly) line by line towards the top of the screen, with only black screen being added, and a white cursor in the lower left. So it’s continuing to do… something.

Lastly, I tried this both in the case’s front USB 3.0 port, and one of the motherboard’s USB 2.0 ports, using a USB 2.0 stick; same behavior either way.

Any thoughts as to what might be causing this, any fix; or if the continued activity means it’ll get to the macOS installer screen, how long to wait? It’s been scrolling slowly up the screen for at least an hour and a half now.

FURTHER UPDATE: taking a RAM stick out of B1, and then out of A1, so starting up in either case with only 8GB in a single-channel configuration, still yields the same result as above.

 

FURTHER UPDATE #2: Reading Tiem’s above suggestion, removed m.2 with the other OSes on it & attempted install again. Same result.

 

Since not address by username, I’m not absolutely sure whether Tiem’s most recent post addresses me or another poster, but if me: yes, I’ve noticed the double-posts, was unsure if others saw them (apparently they do; sorry). I think it’s something about the Tapatalk app, and I’ll likely drop its use.
 

Sorry to double-bombard so far, anyway! I’d still appreciate any insight, and don’t plan to throw any money at having someone else just do it; I’m building a Hackintosh to learn. I’m asking here because I was under the impression it’s a shared resource.

 

Thanks!

Edited February 4, 2020 by juan e. jot
Add yet more additional info, clean up rest of weird double-post

[Tiem]

Sorry dude, from your continual double posted replies I'm thinking this is just beyond you. I think you may be lacking in some very important foundational knowledge and are getting spun around.

 

You may just want to put an ad out in your local area asking for someone who can come over and set it up for you. Tossing them even $100 for the effort seems like a way better use of time vs. cost.

[map002]

Juan,

If you wipe everything you've done to date, reset your BIOS to factory settings and let someone else with some technical acumen (previous Hackintosh skills a bonus!)  come in with a fresh pair of eyes and none of your preconceptions, let them work the guide and you just watch what they do., it might be both a solution and a learning experience.

That might be the easiest way to find out what steps you've been missing or doing incorrectly.

Just don't give them advice or tell them what you think is wrong.  Let them approach it clean.

Of course, you do what you think best, but that's what I would do if I were in your shoes.  Good luck, my friend!

Edited February 4, 2020 by map002
Clarity

[AudioGod]

Blimey what have I been missing @Tiem? 

welcome to my world of banging your head against the wall. 

[WizeMan]

Hi @AudioGod & @texem

 

Is there some particular reason that SIP is disabled on the OpenCore variant?

<key>csr-active-config </key>
<data>ZwAAAA==</data>

➜  ~ csrutil status
System Integrity Protection status: disabled.
➜  ~ 

Will it hurt if I enable it? 

 

 

[texem]

The reason is some dev tools fails with SIP.

But give it a try an report plz.

 

[Tiem]

1 hour ago, WizeMan said:

Hi @AudioGod & @texem

 

Is there some particular reason that SIP is disabled on the OpenCore variant?

<key>csr-active-config </key>
<data>ZwAAAA==</data>

➜  ~ csrutil status
System Integrity Protection status: disabled.
➜  ~ 

Will it hurt if I enable it? 

 

 

https://www.insanelymac.com/forum/topic/338516-opencore-discussion/?do=findComment&comment=2674754

[Malenca]

Hi...

Very nice and useful guide.

Had to change my mobo from Asus to the Z390 Aorus Ultra due a crash on the Asus.

I followed your guide and everything was good..

Except that I'm getting a boot failure on restart. After that (switching OFF and ON again on) but shows this KP message..

May be you can help to discover why?? Been fighting with this for the past 2 days....

Installation was clean and i9 9900K, Z390 Aorus Ultra, 64 gb mem, Radeon 64 8gb. boot on Nvme Samsung 970 pro 1tb.

Attached the kernel

 

thank you for your time and help

 

Marcelo

[Tiem]

@Malenca go find a guide for the Ultra. Everything here was built for the Pro. The Ultra =/= Pro.

 

theres actually one out there with proper DSDTs too. Google-fu

[AudioGod]

@Malenca you can go one step better then what @Tiem suggested and get a EFI and DSDT made up specially for your hack so just click on the link below and follow @MaLd0n instructions and then put in a DSDT request with him.

 

To Create Your Own Patched DSDT Message @MaLd0n using the link bellow

https://www.olarila.com/forum/17-dsdt-patch-requests/

(If you want a perfect setup then getting your own patched DSDT made would be the best thing to do, Mine will work perfectly fine but different hardware no matter how small a change it is can tend to have some sort of effect on the DSDT and your setup)

Edited February 4, 2020 by AudioGod

[Tiem]

There’s actually a build for the Ultra that has fully custom DSDTs and everything g tested and working.

 

Google “aorus ultra hackintosh”, first hit.

[AudioGod]

8 minutes ago, Tiem said:

There’s actually a build for the Ultra that has fully custom DSDTs and everything g tested and working.

 

Google “aorus ultra hackintosh”, first hit.

Still nothing better then getting a personal one made up and using Mals methods.

[WizeMan]

https://www.insanelymac.com/forum/topic/338516-opencore-discussion/?do=findComment&comment=2674754

Hi. I know how to enable / disable SIP I just don’t know whether enabling it will break something. Guess I’ll have to try and see I’ll report back


Sent from my iPhone using Tapatalk

[Tiem]

~ ❯ csrutil status
System Integrity Protection status: enabled.

Took out entry in the config. No issues so far. For those wanting a more pure Hack 

[carter1810]

On 1/2/2020 at 11:40 PM, fart pants said:

Big thank you to audiogod, for this thread and top notch expertise. Also a big thank you to Maldon and glasgood for alternative solutions. At this point Im using bios f11 and audiogod’s pro nave vega zip efi, MSR profile, patches, drivers and kexts minus Whatevergreen, but before this I was testing so many variations, Its been monumental in getting my aorus pro pro back into OSX. My journey to this point wasnt easy, I think for me that Catalina is the most difficult mac OS to get stable and functioning well. Im posting a reply here because I want to help and return some support if I can. 

 

I’ve been reading a few posts with issues that I had and maybe still have and I’ll try to give some tips.

 

Resolved major issues:

 

Boot looping in post. 

 

Possible causes.  f11 bios, 32gb ram, MSR unlock profile.

Post error was a ram issue but it occurred After I installed the MSR profile, I managed to resolve the issue to some extent but I still get weird boot anomalies like power button flash when pressed but no power on and also the odd boot loop once in a while.

 

I didn’t scientifically diagnose the issue but what helped MSR profile to become more stable was indeed like audiogod’s suggestion of removing the battery from the mobo but for me I also had to reduce the ram to 16gb and run that for a few shutdowns and restarts the add the other sticks. I found bios f10 was the most stable but alas the msr profile is not suggested for any other bios revision.

 

Error 0x0000xxxx alloc type 2 runtime blah blah (This error came at the first 2 or 3 lines in verbose mode) The dreaded stop circle.

 

Causes: igfx, titan ridge pci card (and possibly something else)

Whats amazing is this error just occurred way after installation and normal use, with no change to bios settings.

 

What solved the issue was igfx disabled in bios. Unfortunately I needed it for headless mode, fcpx and acceleration. So after many hours of testing... igfx at 64mb in bios worked with the one port setting in the thunderbolt configuration menu resolved this error. I have a GC titan ridge add on card for my LG 5k display.

 

Ongoing Issues:

 

1. Sidecar worked once when I first install OS, then crapped out with device timed out error ever since. Update: its worked twice so far... Why now?

 

2. Logitech g502 not connected in GHUB, but system report/usb Identifies it properly. Someone earlier had posted the same problem, I'm unable to customise my mouse buttons.

 

3. Black screen when restarting or waking, but this is difficult to resolve because I'm running my monitor through a thunderbolt card. Don't know where the problem lies.

 

Choppy HEVC and very high bit video playback in VLC, Quicktime and unresponsiveness/crashes in Final cut pro.

 

I downloaded some very high bit 4k jelly fish test vids to test.

Possible Causes: igpu configuration in DSDT, Whatevergreen, vega 56 (and possibly something else).

 

Early stage but looks promising, using audiogod’s DSDT I added “injectintel” to clover graphics and removed Whatevergreen.

Update: Ive just had really choppy video playback with these settings. I restarted my pc and smoothness has returned. hmmm

 

Now here is what I've noticed in my trail and error testing, maybe audiogod or others can shed some light on the differences between these set ups?

 

setup 1. Audiogod’s DSDT only

 

In “about this mac”, Graphics/displays report was slow to report information ( about 4 seconds). Only my vega 56 info reports and all is looking as it should. PCI info shows the intel 630 as “Other display controller” and intel acceleration is showing in ioreg... but choppy video

 

screenShot 1

 

setup 2. Without DSDT and only using Maldon's Olarila method of a few Configuration changes through clover (sorry no actual screen shots but screenShot 2 is close but without the gpu's numbers 1 and 2 as shown)

 

In "system report" / Graphics is instant and there is no lag in getting the report as described in the above DSDT method. Now depending what ig-platform id I set in clover, I get 2 different report results. Both result in choppy video but the system report is different.  

1. Intel UHD 630 and Vega 56 is now shown in "graphics/displays". this did not occur with the above method (check screenShot 2). IOreg shows intel acceleration but there is one snag Final Cut Pro fails to launch and a crash report is generated.

2. No four second lag in generating Graphics/display report, but it only shows the Vega (basically the same result as audiogod's DSDT method but without the pci info) but Final Cut works with choppy unresponsive video.

 

setup 3. With audiogod's DSDT, InjectIntel added in clover and Whatevergreen removed from efi

 

Final Cut opens and works better with very high bitrate HEVC and h264 video, smoother frame rate out put in VLC and Quicktime, intel acceleration active in IOreg 

 

screenShot 2.

Now there are a number of differences in this method.

1. As in method 2 above when "Graphics/displays" reports the the gpu's in this way, Final Cut Pro would crash when launching.

2. GPU numbers and Infinity fabric Link were not present in any other method.

3. PCI report (I know its cosmetic) also changed (see screenshot 3). It now shows as VGA compatible? Please compare it to screenShot 1.

 

screenShot 3

 

screenShot 4

 

Without Whatevergeen I get pink/purple lines at the end of the apple boot screen but clears at login screen.

 

I have just noticed this.

 

screenShot 5

 

my Vega 56 is showing as a Vega 64, that didn't happen in my Mojave hack. Is that an issue?

 

I hope some of this info helps someone

 

Sorry I forgot to add that to get setup 3 to work I also had to set Initial display to igfx and not pci 1.

 

 

I have same trouble like you. iGPU only 0.33 so laggy when editting H264

[c1ru]

hi !

I have added a new monitor but I have some artefacts in my main monitor like dots appears randomly and something like that.

Right now I have restarted my pc and I can't get image in second monitor.

What can I check?

[Pieroman]

Hi everyone,

 

I'm about to receive my hardware for that build and I'm already so grateful for all the work that was done in here! I plan to start with the clover EFI as I'm more familiar with that but I have a question about the MSR lock :

• I ordered a Fenvi T919 for wifi/bluetooth, but read in the thread that int doesn't work well with the MSR unlocked, is that info still current, and what happens ? EDIT : it seems only @WizeMan has this problem but not @Tiem ?
• What do we actually lose by keeping MSR locked / gain by unlocking it ? I see that the unlock helps with the 5700XT but havent found much more details.  My Hack will use ethernet so the wifi card will only be used for airdrop/continuity which I can live without if need be.
• If I do keep the MSR locked, is there anything to change in the clover config.plist ? (I see that KernelPM is already true) The opencore portion of the guide shows that changes are needed depending on MSR status but not the Clover portion which is why I'm wondering. EDIT so it seems that  with MSR unlocked the clover EFI has to be modified (switch KernelPM to false) compared to the downloaded version (so opposite to OC), is that correct? If so the guide is not clear on that.
• Does the file containing the MSR unlock config (F12d_UNLOCK) also contain the correct other settings for the bios ?  RTFM, looks like it

 

Thanks for any precisions !

 

Edited February 5, 2020 by Pieroman
Additional info

[stavidawg]

On 2/3/2020 at 9:53 PM, juan e. jot said:

 

Further research confirms that building the installer from a gibmacos-downloaded copy of 10.15.3 (with AudioGod’s unmodified UHD630 EFI in the EFI partition of the installer USB stick) yields the same “forbidden” or “prohibited” symbol about 1/2 to 2/3 through the progress bar. Interestingly, when I add “-v” to the boot args to get an output of what it’s doing, the symbol still pixelates the text “under” it, but these couple of times (see below) I tried it, I let it run for long enough to see some text continuing to come across non-pixelated in patches, but not an entire line to read, and the text definitely continued to scroll (very slowly) line by line towards the top of the screen, with only black screen being added, and a white cursor in the lower left. So it’s continuing to do… something.

Lastly, I tried this both in the case’s front USB 3.0 port, and one of the motherboard’s USB 2.0 ports, using a USB 2.0 stick; same behavior either way.

Any thoughts as to what might be causing this, any fix; or if the continued activity means it’ll get to the macOS installer screen, how long to wait? It’s been scrolling slowly up the screen for at least an hour and a half now.

FURTHER UPDATE: taking a RAM stick out of B1, and then out of A1, so starting up in either case with only 8GB in a single-channel configuration, still yields the same result as above.

 

FURTHER UPDATE #2: Reading Tiem’s above suggestion, removed m.2 with the other OSes on it & attempted install again. Same result.

 

Since not address by username, I’m not absolutely sure whether Tiem’s most recent post addresses me or another poster, but if me: yes, I’ve noticed the double-posts, was unsure if others saw them (apparently they do; sorry). I think it’s something about the Tapatalk app, and I’ll likely drop its use.
 

Sorry to double-bombard so far, anyway! I’d still appreciate any insight, and don’t plan to throw any money at having someone else just do it; I’m building a Hackintosh to learn. I’m asking here because I was under the impression it’s a shared resource.

 

Thanks!

 

Sounds like you and I are in the same boat.. I'm getting the same prohibited message even after thorough trouble shooting (reflashed/reset bios now over 4 times), and I have build two other hackentoshes so I would like to think I have half a wit of how to do it correctly. If you're really ancy to get it up and running there is an EFI there that will get you up and running (https://www.tonymacx86.com/threads/z390-aorus-pro-stuck-on-apple-logo.290781/page-2#post-2067345). That said, I have had no luck "upgrading" to the newer OS (i.e. 10.15.2 -> 10.15.3) using this EFI.

 

But to echo what the others have said, getting a bullet proof EFI/Hackentosh set up is really the only way to go so you might wan't to look into getting help/paying someone in your community to get it set up correctly for you. 

[WizeMan]

11 hours ago, Tiem said:

~ ❯ csrutil status
System Integrity Protection status: enabled.

Took out entry in the config. No issues so far. For those wanting a more pure Hack 

 

Same here and so far so good as well

[WizeMan]

5 hours ago, Pieroman said:

Hi everyone,

 

I'm about to receive my hardware for that build and I'm already so grateful for all the work that was done in here! I plan to start with the clover EFI as I'm more familiar with that but I have a question about the MSR lock :

• I ordered a Fenvi T919 for wifi/bluetooth, but read in the thread that int doesn't work well with the MSR unlocked, is that info still current, and what happens ? EDIT : it seems only @WizeMan has this problem but not @Tiem ?
• What do we actually lose by keeping MSR locked / gain by unlocking it ? I see that the unlock helps with the 5700XT but havent found much more details.  My Hack will use ethernet so the wifi card will only be used for airdrop/continuity which I can live without if need be.
• If I do keep the MSR locked, is there anything to change in the clover config.plist ? (I see that KernelPM is already true) The opencore portion of the guide shows that changes are needed depending on MSR status but not the Clover portion which is why I'm wondering. EDIT so it seems that  with MSR unlocked the clover EFI has to be modified (switch KernelPM to false) compared to the downloaded version (so opposite to OC), is that correct? If so the guide is not clear on that.
• Does the file containing the MSR unlock config (F12d_UNLOCK) also contain the correct other settings for the bios ?  RTFM, looks like it

 

Thanks for any precisions !

 

 

1. I do have the issue indeed, I do not know whether it is related to the Fenvi card OR the motherboard itself. The issue appears if I use the MSR Unlock Profile and uncheck `KernelPM` (on Clover) or set `AppleCpuPmCfgLock` and `AppleXcpmCfgLock` to `false` (on OpenCore). if I use the MSR Unlock Profile and keep `KernelPM` checked (on Clover) or `AppleCpuPmCfgLock` and `AppleXcpmCfgLock` to `true` (on OpenCore) I do not have the issue, but since I am not changing these values, I have relocked the MSR as well.

 

2. I do not know what you lose with keeping the MSR locked, maybe @AudioGod and @texem can enlight us.

 

3. Precisely. Although the Clover Variants have `KernelPM` checked by default (which means that by default it supports an MSR Locked system), the OpenCore Variants have `AppleCpuPmCfgLock` and `AppleXcpmCfgLock` set to `false` by default which means if you do not change these to `true`, your system will not boot if it is MSR locked. If you decide not to unlock your MSR you must change this:

<key>AppleCpuPmCfgLock</key>
<false/>
<key>AppleXcpmCfgLock</key>
<false/>

into this:

<key>AppleCpuPmCfgLock</key>
<true/>
<key>AppleXcpmCfgLock</key>
<true/>

 

I propose that these flags become `true` by default as the MSR Unlock step is optional. What is your opinion @AudioGod?

 

To be honest, if I were you I would try to do the MSR Unlock first and give it a spin. If you do try it, please report back. It will be interesting to see if I am not alone on this.
 

 

Edited February 5, 2020 by WizeMan

[vishalchouhan]

efi catalina 10.15.3 upload