Jump to content

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

AudioGod

By AudioGod,
in Installation Guides

 Share
5539 posts in this topic

Recommended Posts

Tiem
Tiem
Posted
Posted
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
WizeMan
Posted
Posted (edited)
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 by WizeMan
Pieroman
Pieroman
Posted
Posted

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
WizeMan
Posted
Posted (edited)
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 by WizeMan
Tiem
Tiem
Posted
Posted (edited)

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 by Tiem
WizeMan
WizeMan
Posted
Posted (edited)
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 by WizeMan
  • Confused 1
Pieroman
Pieroman
Posted
Posted

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 ;)

WizeMan
WizeMan
Posted
Posted (edited)

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 by WizeMan
WizeMan
WizeMan
Posted
Posted
17 minutes ago, AudioGod said:

No no buddy it’s setup_var_3 you should be doing it with.

Hm I haven’t had any issues until now but I’ll be keeping an eye then, if I notice anything going wrong I’ll redo with setup_var_3. 

Pieroman
Pieroman
Posted
Posted (edited)

So the other thread about the Aorus Master was updated about the fact that MemoryAllocation.efi is the same as free2000 and thus not recommended. Any updates for the Aorus Pro? 

From my understanding Z390 boards need some kind of memory fix .efi with sometimes a custom slide value, but @AudioGod seems to recommend not putting any other memory fix .efi, I'm confused... EDIT : reading around it looks like it's hard to have the Aorus Pro with the iGPU enabled, which is required for 19,1 SMBIOS.

Edited by Pieroman
WizeMan
WizeMan
Posted
Posted
6 minutes ago, Pieroman said:

So the other thread about the Aorus Master was updated about the fact that MemoryAllocation.efi is the same as free2000 and thus not recommended. Any updates for the Aorus Pro? 

From my understanding Z390 boards need some kind of memory fix .efi with sometimes a custom slide value, but @AudioGod seems to recommend not putting any other memory fix .efi, I'm confused... EDIT : reading around it looks like it's hard to have the Aorus Pro with the iGPU enabled, which is required for 19,1 SMBIOS.


I removed MemoryAllocation.efi this morning. Cleared NVRAM and my iMac19,1 setup works fine. About mid-day I switched back from Vega 56 to Polaris RX 580 and it is also working. So I’d say at least with my setup there is no issue removing the MemoryAllocation.efi from the EFI.

 

PS: if you’ll be using OpenCore be sure to remove the entry from the Drivers section as well.

  • Thanks 1
Tiem
Tiem
Posted
Posted (edited)
2 hours ago, pkdesign said:

The only difference in that guide is that @Tiem says to use setup_var_3

Correct. Both setup_var and setup_var_3 will return the same error. But the latter will actually apply the variable and unlock your board. Using setup_var will just error out and your board will still be locked.

 

If you're not sure whether the CFG unlock offset was applied, you need to use UEFITool and IFR-Extractor to ensure the offset changed from 0x1 (locked) to 0x00 (unlocked). Relying on the fact your system can boot isn't really ideal.

 

If you have the WIFI variant of the Pro, you need to apply the patch via the modified grub shell (or hack your own firmware file). If you have a regular Pro, then AG has linked an actual unlocked BIOS firmware, which is the ideal way to remove the CFG Lock. Just flash your board with it and you're good to go.

Edited by Tiem
WizeMan
WizeMan
Posted
Posted (edited)
15 minutes ago, Tiem said:

Correct. Both setup_var and setup_var_3 will return the same error. But the latter will actually apply the variable and unlock your board. Using setup_var will just error out and your board will still be locked. 


Not correct. If setup_var was unsuccessful and left my board’s CFG Lock enabled, it wouldn’t be able to boot after setting


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

 

I do not disagree with your statement that setup_var_3 works (heck, it might work better than setup_var) but using setup_var DID disable the CFG Lock

Edited by WizeMan
Neek
Neek
Posted
Posted
1 hour ago, WizeMan said:


I removed MemoryAllocation.efi this morning. Cleared NVRAM and my iMac19,1 setup works fine. About mid-day I switched back from Vega 56 to Polaris RX 580 and it is also working. So I’d say at least with my setup there is no issue removing the MemoryAllocation.efi from the EFI.

 

PS: if you’ll be using OpenCore be sure to remove the entry from the Drivers section as well.

Can confirm that clearing NVRAM/CMOS and re-doing BIOS setting as in the guide allowed me to remove MemoryAllocation.efi.

 

When I was lazy and didn't pull the battery and reset CMOS pins I needed the extra. All is well now.

  • Like 1
Neek
Neek
Posted
Posted
23 minutes ago, pkdesign said:

I hate to sound lazy...but, can i just remove MemoryAllocation.efi and not clear NVRAM or reset my BIOS? Such a pain in the ass to do.

Boot off a backup USB w/your EFI (a version that has MA.efi removed) and see if it'll work.

 

Chances are it won't, but you may get lucky.

 

Do NOT modify your main EFI without trial booting off of an external backup that includes your proposed changes.

AudioGod
AudioGod
Posted
  • Author
Posted (edited)
29 minutes ago, pkdesign said:

Well, I was lazy. I just removed MemoryAllocation.efi and off I went. No issues rebooting after that.

For now you mean. Wait for it!!!!!!

 

clear out your nvram via clover or OC at the very least bud

Edited by AudioGod
  • Thanks 1
  • Haha 1
 Share
Go to topic listing
×
×
  • Create New...