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

AudioGod
AudioGod
Posted
  • Author
Posted
4 minutes ago, eSaF said:

Bro I get the feeling that AG likes to wind us up proper with all his new toys and gadgets - it's a case of the 'Haves and the Have Nots'. :hysterical: But despite this one failing, he's a Bro for life. :thumbsup_anim:


You got me all wrong if you think that then bro. Don’t hate on me cos I have a job that flings toys my way permanently, With the exception on the MacMini I rarely buy my hardware. 

  • Like 1
AudioGod
AudioGod
Posted
  • Author
Posted
12 minutes ago, eSaF said:

Bro you gotta get me a job wid dat company!!!!!:hysterical: cause dat aint no job!!! that is a hobby, tell them I don't need no pay :hysterical: :hysterical: :hysterical: to sweeten the deal. :hysterical:

:hysterical: You try a week in my shoes and then say that...lol

If only.

  • Like 1
  • Haha 1
hackinbot
hackinbot
Posted
Posted

Hey all, just checking in and want to give thanks to this awesome crew.

 

Finally decided to update to Catalina yesterday (was holding out for some software to finally catch up).

 

Updated the bios to F12K and used AudioGod's OC 0.6.3 EFI to update MacOS to 10.15.7.

 

I tried the Clover EFI also, but for Clover to work with FileVault, I had to do the following:

  • Add AppleUiSupport.efi
  • Add AppleGenericInput.efi
  • Remove 'preboot' from the hidden volumes in the GUI section

All of this stuff is baked into the OpenCore EFI so if anybody's using FileVault, I recommend using @AudioGod's OpenCore EFI.

  • Like 2
Tiem
Tiem
Posted
Posted

So follow up because I’m going back to a Mac and have already sold my Hack. Have about a week.

 

no issues with USB since. Been only about 5 days but that’s longer than I have gone beforehand so all signs point to either the case ports or potentially USB3 gen 2 ports (less likely).

 

incidentally I had lots of GPU crashes with the updated DSDTs. Switching back to the older ones and not a single crash since. Just sayin. Unrelated to USB woes as it may be.

 

cheers.

 

PS: I’ll update you guys till my Hack goes cold but for those having USB issues, maybe try pulling the case ports. And I’m on the latest z390 pro bios.

  • Like 2
Blesh
Blesh
Posted
Posted
On 12/1/2020 at 8:44 AM, Tiem said:

So follow up because I’m going back to a Mac and have already sold my Hack. Have about a week.

 

no issues with USB since. Been only about 5 days but that’s longer than I have gone beforehand so all signs point to either the case ports or potentially USB3 gen 2 ports (less likely).

 

incidentally I had lots of GPU crashes with the updated DSDTs. Switching back to the older ones and not a single crash since. Just sayin. Unrelated to USB woes as it may be.

 

cheers.

 

PS: I’ll update you guys till my Hack goes cold but for those having USB issues, maybe try pulling the case ports. And I’m on the latest z390 pro bios.

 

 

Try to set the C-State in your BIOS to AUTO. I did this, now one and a half week later I never got any USB crashes since then. Try it but I can't promise anything.

  • Thanks 1
Tiem
Tiem
Posted
Posted
10 hours ago, Blesh said:

 

 

Try to set the C-State in your BIOS to AUTO. I did this, now one and a half week later I never got any USB crashes since then. Try it but I can't promise anything.

{censored} sorry. I actually have mine set to off. Forgot to mention that. Still going strong. No USB crashes since making the changes.

hackinbot
hackinbot
Posted
Posted

Upgraded to Big Sur 11.0.1... all went well... but now this:

 

 

Ridiculous. Using a Logitech G502... reduced polling rate to 125 Hz and just moving the cursor around still spikes WindowServer to ~40% CPU.

scotty pro
scotty pro
Posted
Posted
On 12/3/2020 at 3:51 AM, hackinbot said:

Upgraded to Big Sur 11.0.1... all went well... but now this:

 

 

Ridiculous. Using a Logitech G502... reduced polling rate to 125 Hz and just moving the cursor around still spikes WindowServer to ~40% CPU.

that's obviously a big bug in Catalina, I have the same mouse on Mojave and I have just had a look and it is around 8-12%

  • Like 1
stangen
stangen
Posted
Posted (edited)

Updated to Big Sur, but decided to rollback to Catalina. Apple TV not worked, unlock with Apple Watch too. 

(Latest @AudioGod OC with latest bios)


P.S. Unpairing and pairing again do the magic. Now iWatch is able to unlock the Big Sur. Only Apple TV refuse to work. 

 

Gigabyte Z390 Aorus Pro / i7-9700K / AMD RX5700 XT / 16 GB RAM

 

 

 

Edited by stangen
AudioGod
AudioGod
Posted
  • Author
Posted
41 minutes ago, pkdesign said:

FYI: I've update to 0.6.4 with no issues (except missing dual boot).

 

FIX: I had to set ScanPolicy to 0

ScanPolicy is set to 0 as standard on my EFIs so it’s not a problem. 

juan e. jot
juan e. jot
Posted
Posted (edited)
On 12/8/2020 at 2:25 PM, pkdesign said:

FYI: I've update to 0.6.4 with no issues (except missing dual boot).

 

FIX: I had to set ScanPolicy to 0

Ditto: I had a similarly good experience (my ScanPolicy was already set to 0), after replacing (in different folders/from different downloads, so be aware of both where to get them, and where to replace them.  Also while we're at it, when to hold 'em, and when to fold 'em. :D):

  • From OpenCore 0.6.4-RELEASE,
    • BOOTx64.efi,
    • OpenCore.efi,
    • Bootstrap.efi,
    • AudioDxe.efi,
    • OpenCanopy.efi,
    • OpenRuntime.efi,
    • OpenShell.efi, and
    • ResetSystem.efi,
  • Then the following kexts from different downloads:
    • AirportBrcmFixup.kext,
    • AppleALC.kext,
    • Lilu.kext,
    • SMCProcessor.kext,
    • SMCSuperIO.kext,
    • VirtualSMC.kext, and
    • WhateverGreen.kext.

I then took a deep breath, restarted, made sure boot order was to my liking in UEFI BIOS, reset NVRAM, re-set all of the multi-boot pointers to my liking on my triple-boot system, let it start up to Big Sur, and:

 

It works… or at least, I have yet to find a way it doesn't so far. [Notes lack of "crossed fingers" emoji on the forum.] That said, I'll await AudioGod's update to the EFI, at very least to compare, especially the config.plist (which I didn't change at all), and potentially to get updates to .amls and any .efis or .kexts he might update on his own.

 

Off to go clear other caches & then re-set defaults; keeping my old 0.6.3 EFI on hand on the USB for now, just in case. But so far, so good. Good luck!

 

EDIT: Found upon tinkering around that the System Firmware Version for SMBIOS iMac19,1 has been updated from 1037.140.50.0.0 (which SilentKnight & other EclecticLightCo apps still expect; no idea whether the fruit company does) to 1554.50.2.0.0. Also, I usually run with SIP enabled (feel about that however you like), and it apparently also now has "SSV enabled," which may refer to Big Sur's "Signed System Volume," though I haven't noticed (and to be fair, haven't looked for) it previously.

 

Edited by juan e. jot
Added interesting tidbits about System Firmware Version, SSV
pkdesign
pkdesign
Posted
Posted
17 hours ago, AudioGod said:

ScanPolicy is set to 0 as standard on my EFIs so it’s not a problem. 

That's how I found the error, by comparing your EFI to my new one. Yours is always the master! Unfortunately I can’t just use your EFI as is, I've made too may edits (i.e. audio, open canopy icons and settings, serial of course, etc.) 

 

I really, really hope the in the future, OC will have some sort of updater so you don't have to go through each and every setting everytime you update. It takes hours. ProperTree is helpful but not perfect. It always wants to set things back to "standard" which is how you end up with small glitches like this.

  • Like 1
WizeMan
WizeMan
Posted
Posted
3 hours ago, pkdesign said:

That's how I found the error, by comparing your EFI to my new one. Yours is always the master! Unfortunately I can’t just use your EFI as is, I've made too may edits (i.e. audio, open canopy icons and settings, serial of course, etc.) 

 

I really, really hope the in the future, OC will have some sort of updater so you don't have to go through each and every setting everytime you update. It takes hours. ProperTree is helpful but not perfect. It always wants to set things back to "standard" which is how you end up with small glitches like this.


You don’t have to go through each and every setting. Just open Differences.pdf and update / add / remove whatever is needed.

juan e. jot
juan e. jot
Posted
Posted (edited)

This was going to be an edit to my initial observations about upgrading to OC 0.6.4, but it's gotten long enough, that I suppose I'll post it in its own reply:

 

Since upgrading to OC 0.6.4 on 12/8 (or 8/12 for folks on the other side of the pond), I've noticed several times the quick flicker of a non-catastrophic error message during bootup (between the manufacturer splash screen and the -v scrolling bootup status text), and kept meaning to catch a video of it. I now have, and it appears to say "OCS: Failed to calculate size of false field containing <empty> as type integer, context <PlayChime>!" (see attached screen shot, to compare my reading of that text to your own).

IMG_6405.thumb.PNG.a4d8ef1fa93374a05f411e915a4daefa.PNG

I know that Big Sur is finally back to playing a boot chime officially, even if OC has unofficially been allowing the use of one (a .wav file in side EFI>OC>Resources>Audio) for the past few point releases. I personally don't use it, not having installed a case speaker (and not assuming the driver to get it through either HDMI to the monitor, or through the board's ALC to the audio out jacks on either the back of the motherboard or front of the case, has been loaded yet in the boot process). As such, to the opposite of setting up a boot chime as on https://dortania.github.io/OpenCore-Post-Install/cosmetic/gui.html#setting-up-boot-chime-with-audiodxe (maybe because the chime is no longer invoked by AudioDxe, but natively?), I keep my config.plist's "PlayChime" boolean set to "False."

 

Since the message flickers by and boot continues, I'm assuming I have nothing to do but clean up (probably remove) an entry or two from my config.plist to banish it. But since it's now native to Big Sur & not invoked via AudioDxe, might there be more aggressive measures (a contextual update to AppleALC.kext, or a dummy .efi to be written or something?) to let the system know, "Yeah I know the fruit company again has decided to sing the praises of macOS yet again; I have nothing at this stage of the boot out of which to sing them, so shut up!" Any concern in letting it flicker by, until I can do that?

Edited by juan e. jot
Light text error editing upon reread.
juan e. jot
juan e. jot
Posted
Posted
1 hour ago, texem said:

PlayChime is now <string> .. </string>

 

 

 

35 minutes ago, panosru said:

In a reddit post I saw that you set <string>Auto</string> for PlayChime

Thanks, folks!  That did it!  Guess I'll go read a little more deeply into Differences.pdf, to see if there's anything else I'm missing that didn't get a flicker of a non-catastrophic error message.

DoYouBelieveInMiracles
DoYouBelieveInMiracles
Posted
Posted (edited)

Hello everyone and especially @AudioGod :D

I have the exact same rig as the guide and I am about to attempt to hackintosh with Big Sur.

I was wondering since I am going the OpenCore route if it is mandatory to update my BIOS to f12k. If it is, do you propose the USB flash?

I am afraid that it’s risky business What do you think?

Edited by unknownharris
AudioGod
AudioGod
Posted
  • Author
Posted (edited)

OpenCore 0.6.4 EFI Update (Big Sur Ready), 13nd December 2020 

(Use With Bios Revision F12K or Newer)

 

The EFIs and DSDTs have now been updated to the my latest versions.

Changes made include,

AppleALC 1.5.5,

Lilu 1.5.0,

WhateverGreen 1.4.5,

VirtualSMC 1.1.9,

AirportBrcmFixup 2.1.2,

IntelMausi 1.0.4,

OpenCore Updated to Revision 0.6.4 (Big Sur Ready),

OpenCanopy is Enabled as Standard,

SSDT-Plug and SSDT-PMC Have been freshly pulled and rewritten using bios F12k,

SSDT-EC-USBX.aml has now been added to the ACPI,

USBPort.kext has been rewritten manually and is now named USBMap.kext and the power tables are now being done via SSDT-EC-USBX instead of directly inside the USB.kext,

Plus other major tweaks and changes to all of the configs

 

OpenCore EFI Update v0.6.4 - 13/12/2020

OC 064 19,1 Z390 Pro EFI 131220.zip - OpenCore v0.6.4, SMBios iMac19,1

OC 064 1,1 Z390 Pro EFI 131220.zip - OpenCore v0.6.4, SMBios iMacPro1,1 (IGPU Disabled)


PLEASE DON’T FORGET TO RESET YOUR NVRAM BEFORE BOOTING INTO THE NEW EFI FOR THE FIRST TIME,

 

Note - If your not using a 5700 XT or any other Navi GPU then remove agdpmod=pikera from the boot arguments.

Note 2 - Do not try to carry across your old OpenCore Config.plist to the new EFI as to many changes have occurred in 0.6.0. Use the new Config.plist instead.

 

For OpenCore Using PlistEdit Pro add your details by modifying the following 

453128831_Screenshot2020-01-16at19_25_01.thumb.png.7a9beac3ccc0096941fc4a0ec07b8248.png

 

PLEASE NOTE - These EFIs are setup to be used with your msr Unlocked so make sure you use the correct bios settings listed below or use the F12K Unlocked Profile I have provided.

 

Additional Downloads

mb_bios_z390-aorus-pro_f12k.zip - Aorus Z390 Pro Bios Firmware F112K

mb_bios_z390-aorus-pro-wifi_f12j.zip - Aorus Z390 Pro Wifi Bios Firmware F112J

PlistEdit Pro.zip - PlistEdit Pro (use to edit OpenCore)


PLEASE NOTE - MSR Unlock is now baked into the BIOS as a setting so you no longer need my bios profile to unlock your MSR.

 

Bios Update F12K (F12J Pro Wifi) and Bios Settings


PLEASE NOTE - MSR Unlock is now baked into the BIOS as a setting so you no longer need my bios profile to unlock your MSR.

 

BIOS SETTINGS (Bios Revision F12k & F12j Pro Wifi)

 

• Enter BIOS -> Press Delete -> Enter Setup

• Save & Exit -> Load Optimized Defaults

• Boot -> CFG Lock -> Disabled

• Boot -> Windows 8/10 Features -> Win 8/10 WHQL

• Boot -> CSM Support -> Disabled (Can be set to Enabled if need be but try to have it set to Disabled first)

• Favourites -> Extreme Memory Profile (X.M.P.) -> Profile1

• Favourites -> VT-d -> Disabled (Can be set to Enabled or Disabled, Your choice)

• Settings -> IO Ports -> Internal Display Output -> PCIe 1 Slot

• Settings -> IO Ports -> Internal Graphics -> Enabled (Disabled If Using SMBios 1,1)

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

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

• Settings -> IO Ports -> Aperture Size -> 256MB
• Settings -> IO Ports -> Wifi -> Disabled (Z390 Pro Wifi Only)

• Settings -> IO Ports -> Audio Controller -> Enabled

• Settings -> IO Ports -> Above 4G Decoding -> Enabled

• Settings -> IO Ports -> USB Configuration -> Legacy USB Support -> Auto

• Settings -> IO Ports -> USB Configuration -> XHCI Hands-off -> Enabled

• Settings -> Miscellaneous -> Software Guard Extensions (SGX) -> Disabled

• Settings -> Platform Power -> Platform Power Management -> Enabled

• Settings -> Platform Power -> ErP -> Enabled

• Settings -> Platform Power -> RC6(Render Standby) -> Enabled

• Save & Exit → Save & Exit Setup

 

F12K BIOS Profile With MSR Unlocked & All The Correct Settings Dialled in for you - The Easy Way 

@texem has made this bios profile for you all to use that will unlock CFG on your motherboard making it play alot more friendly with the NVRam.

It also has all the bios settings listed on this guide pre done and saved onto the profile.



Z390 PRO BIOS PROFILE - F12k.zip - Use with Z390 PRO Bios Revision F12K ONLY

Z390 PRO WIFI BIOS PROFILE - F12J.zip - Use with Z390 PRO WIFI Bios Revision F12J ONLY (Coming Soon)

 

1 - Download the profile and save it to a USB Key

2 - Go into the bios,

3 - Load the profile, 

4 - Save and exit

5 - Go straight back into the bios and save your bios to a new profile and name it Default or something like that.

6 - Save the changes and then restart and your done, your motherboard will now be CFG (MSR) Unlocked and all the correct settings will be dialled in for you.

 

SORRY ITS LATE EVERYBODY.

Edited by AudioGod
  • Like 6
  • Thanks 4
jimborae
jimborae
Posted
Posted
2 hours ago, AudioGod said:

 

For anybody that's interested.

 

 

Interested! 

 

Except my Ryzentosh Big Sur build is with a Gigabyte Aorus Pro X370, be interesting to see if your EFI works with my kit.  

AudioGod
AudioGod
Posted
  • Author
Posted
4 minutes ago, jimborae said:

 

Interested! 

 

Except my Ryzentosh Big Sur build is with a Gigabyte Aorus Pro X370, be interesting to see if your EFI works with my kit.  


hmmmmmm you might want to disable the USBMap.kext before trying it as I don’t think usb is the same but otherwise it should work with everything else including usb kext free.

jimborae
jimborae
Posted
Posted
13 minutes ago, AudioGod said:


hmmmmmm you might want to disable the USBMap.kext before trying it as I don’t think usb is the same but otherwise it should work with everything else including usb kext free.


hmmm I’ll give it go then when I have some time free. Thanks 

 Share
Go to topic listing
×
×
  • Create New...