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

[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

[Tiem]

7 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 !

 

"Starting with Haswell Macs, CPU power management functionality was moved into the kernel (known as XNU CPU Power Management). KernelPm patches the kernel to prevent writes to MSR_PKG_CST_CONFIG_CONTROL (MSR 0xE2), which is frequently locked on many systems (can usually be disabled by disabling the firmware option "CFG Lock"). Without this patch, you will encounter a kernel panic if MSR 0xE2 is locked (which appears to be the case for your system)"

 

It's just one step closer to a cleaner Hack. But it's not necessary with this build. Enabling KernelPm or AppleCpuPmCfgLock/AppleXcpmCfgLock is more than fine if you can't or don't want it unlocked. Unlocked, macOS will do it's thing. Locked, Clover and OC will step in and do their thing. In both cases, you're Hack will run just fine.

 

MSR Lock doesn't interfere with any hardware whatsoever. Unlock doesn't help with your GPU or anything. It's there for the macOS kernel and power management, that's it. It's not going to knock out your peripherals or make any hardware run better (or worse).

[WizeMan]

23 minutes ago, Tiem said:

"Starting with Haswell Macs, CPU power management functionality was moved into the kernel (known as XNU CPU Power Management). KernelPm patches the kernel to prevent writes to MSR_PKG_CST_CONFIG_CONTROL (MSR 0xE2), which is frequently locked on many systems (can usually be disabled by disabling the firmware option "CFG Lock"). Without this patch, you will encounter a kernel panic if MSR 0xE2 is locked (which appears to be the case for your system)"

 

It's just one step closer to a cleaner Hack. But it's not necessary with this build. Enabling KernelPm or AppleCpuPmCfgLock/AppleXcpmCfgLock is more than fine if you can't or don't want it unlocked. Unlocked, macOS will do it's thing. Locked, Clover and OC will step in and do their thing. In both cases, you're Hack will run just fine.

 

MSR Lock doesn't interfere with any hardware whatsoever. Unlock doesn't help with your GPU or anything. It's there for the macOS kernel and power management, that's it. It's not going to knock out your peripherals or make any hardware run better (or worse).

In my case it makes my hardware run worse  

 

Tested on Clover and OpenCore with the above steps:

 

1. Unlock MSR using the Profile

2. Boot to MacOS (without unchecking KernelPM on Clover or switching the two flags to true on OpenCore)

3. Everything works fine

4. Uncheck KernelPM on Clover or switch the two flags to false on OpenCore) and reboot

5. Boot to MacOS. Bluetooth is junky. Mouse stutters and key presses on the keyboard are not consistent. After a random number of minutes (different on each boot) Bluetooth stops working. Mouse and Keyboard get disconnected but the Bluetooth icon does not show disabled or some other indication.

 

Edited February 5, 2020 by WizeMan

[Pieroman]

Thanks for the precisions @WizeMan and @Tiem you used the MQUPIN fenvi t919 but complained about it right, did you replace it ?

 I guess i'll try with the MSR unlock in the BIOS and in Clover for vanilla's sake and will see if the card works, if not I'll switch it off in Clover!

 

[WizeMan]

15 minutes ago, Pieroman said:

Thanks for the precisions @WizeMan and @Tiem you used the MQUPIN fenvi t919 but complained about it right, did you replace it ?

 I guess i'll try with the MSR unlock in the BIOS and in Clover for vanilla's sake and will see if the card works, if not I'll switch it off in Clover!

 

Yes I have the MQUPIN Fenvi FV-T919. I haven’t complained because I’m not sure it is the card’s fault. Also I have no other issues whatsoever plus Unlock With Apple Watch works which is a rare phenomenon on the hackintosh community.

Edited February 5, 2020 by WizeMan

[Tiem]

Yes, I have the MQUPIN Fenvi, which is the only "Fenvi" you can get in Canada. I could get a real Fenvi off Ali E but that will be a 3 months wait. Maybe down the line.

 

So far the only annoyance with the MQUPIN is that on post, it takes a bit of time to sometimes pick up the keyboard before it loads your Bootloader. This means you often miss the chance to enter the BIOS or pull up the boot options. Pretty annoying but once it picks up your peripherals, it's fine. In actual use (Windows and macOS) it runs just fine and the range is good. I get good reception across the house. Similar to what I got with a real 2019 MBP.

 

The real Fenvi does have pretty sophisticated antenna. I imagine if I got good one for my card, it would work more reliably. Honestly, I didn't know anything at the time, but I would never buy the card in lieu of a real Fenvi with what I know now.

 

With regards to MSR lock/unlock, you guys are turning this into a mountain when it's a molehill. If you have the raw Pro, then just flash your BIOS with the firmware provided by AG. It will be unlocked and you can go ahead and set the variable in your config file accordingly. There's no real reason to want it or to avoid it. I am on the wifi so I had to unlock mine using the modified GRUB loader. But if you are on the basic Pro, then your life will be a lot easier as it's all been literally done for you.

 

Lastly, make a decision which boot loader you want to use. Clover will do Clover things but will also set up a pretty solid Hack. OC is new and volatile. It's more for testing. Let it mature if you literally don't know anything about Hackintoshes and just stick to Clover.

Edited February 5, 2020 by Tiem

[WizeMan]

24 minutes ago, Tiem said:

Yes, I have the MQUPIN Fenvi, which is the only "Fenvi" you can get in Canada. I could get a real Fenvi off Ali E but that will be a 3 months wait. Maybe down the line.

 

So far the only annoyance with the MQUPIN is that on post, it takes a bit of time to sometimes pick up the keyboard before it loads your Bootloader. This means you often miss the chance to enter the BIOS or pull up the boot options. Pretty annoying but once it picks up your peripherals, it's fine. In actual use (Windows and macOS) it runs just fine and the range is good. I get good reception across the house. Similar to what I got with a real 2019 MBP.

 

The real Fenvi does have pretty sophisticated antenna. I imagine if I got good one for my card, it would work more reliably. Honestly, I didn't know anything at the time, but I would never buy the card in lieu of a real Fenvi with what I know now.

 

With regards to MSR lock/unlock, you guys are turning this into a mountain when it's a molehill. If you have the raw Pro, then just flash your BIOS with the firmware provided by AG. It will be unlocked and you can go ahead and set the variable in your config file accordingly. There's no real reason to want it or to avoid it. I am on the wifi so I had to unlock mine using the modified GRUB loader. But if you are on the basic Pro, then your life will be a lot easier as it's all been literally done for you.

 

Lastly, make a decision which boot loader you want to use. Clover will do Clover things but will also set up a pretty solid Hack. OC is new and volatile. It's more for testing. Let it mature if you literally don't know anything about Hackintoshes and just stick to Clover.

First of all you don’t have to be a know-it-all or rude. Also you don’t need to dictate about what we discuss here or what boot loader we use and why. I like to think that people of all hackintosh experience levels are welcome to join this conversation and discuss since we are sharing the same motherboard as well as the hackintosh-fever. The boot loader we’ ll use is also our choice and everyone can switch between OpenCore and Clover whenever they want, since @AudioGod and @texem have made it possible with their rock solid variants.

 

Last but not least, it’s not a matter of wondering why it doesn’t work on Clover or OpenCore. I’ve been having issues with disabling the Kernel Power Management Patches on an MSR UNLOCKED configuration which replicate on both Clover and OpenCore and that’s what we are discussing about, since @Pieroman read about these issues and wanted to know more.

Edited February 5, 2020 by WizeMan

[peyt52]

Does anyone know if this will work with the Aorus Z390 Elite? Thanks

[Pieroman]

Guys I didn’t want to start a fight  thanks to both of you!

This isn’t my first hack but from what you see in my signature it’s been a long time! I’ll stick to clover for now especially since I already know it. I’m happy to see that by the looks of it it should be even easier than in the old times...

The hardest thing now... is to wait for my PC case to arrive by the post, I have received everything else and don’t want to run it on the table with that crazy heavy 5700xt 

[Tiem]

Installed the beta. Prefer HDR Mode is new

 

Edited February 6, 2020 by Tiem

[HSaints]

please make CFG Unlock (MSR) for z390 aorus elite  @AudioGod thank.

[texem]

OMG, switch on your brain and do it yourself !  https://khronokernel-2.gitbook.io/opencore-vanilla-desktop-guide/extras/msr-lock

 

[WizeMan]

I've managed to manually disable CFG Lock on F12d UEFI and this way I am not seeing the issues that I had when using the ready-made profile. Bluetooth is working as expected. I did that using OpenCore and I uploaded the OpenCore Variants here with the modifications needed in order to be able to manually do it.

 

The steps are:

 

1. MAKE SURE YOU ARE ON F12d UEFI
2. Download your flavour (Navi / Vega or Polaris)
3. Update config.plist with your Serial, MLB, Board ID.
4. Copy EFI folder to your EFI partition as usual.
5. Configure UEFI settings as described by our awesome dude @AudioGod
6. On the OpenCore Boot Picker press space and select Modified Grub Shell
7. Enter "setup_var 0x5C1 0x00" (without the quotation marks) and press enter. You will see an error but it has worked indeed.
8. Reboot and Enjoy!

 

 

PS: The only difference with @AudioGod's EFI packs are:

1. Added Tools/modGRUBShell.efi under EFI/OC
2. Added the modGRUBShell.efi entry under Misc/Tools on config.plist

 

N-D-K OpenCore RX Polaris F12d EFI.zip

N-D-K OpenCore Navi Vega VII F12d EFI.zip

Edited February 6, 2020 by WizeMan