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

[Project 2501]

29 minutes ago, eSaF said:

@Project 2501 - Hi I have the same Motherboard as you and don't have that problem, Sleep/Wake works perfect for me. The thing is with CMOS resetting you need to check that this setting in the config.plist is set like the attached. When this happens, you should down the p/c, remove the power cable, press the power button for approx 15 seconds to dispel any latent power in the capacitors. Now remove the CMOS battery for approx 15 seconds.

After replacing the battery and power cable, power up the machine which should induce a message about a BIOS reset and should boot straight into the BIOS.

 

Look at the BIOS Clock albeit the Time and Year will be wrong and will need resetting, take note at the Seconds Digits, it should be counting up the Seconds, if it is static (not moving) then the CMOS reset was not successful and will continue to be problematic but if the steps as describe are done properly, you will not have a recurrence of the CMOS problem.

My attached EFI Folder is OC 0.8.2  version with latest kexts versions, booting BS, Monterey and now Ventura with no problems, all Apple Services i.e iMessage, F/Time, Apple TV, App Store etc all perfect and working.

 

Try my folder on a test USB  drive by booting off it after cleaning the Nvram and see the result, you'll need to furnish the config.plist with your own data i.e S/N, SmUUID, ROM etc as I removed mine. Good luck.

  Hide contents

EFI.zip 84.43 MB · 0 downloads

 

 

Thanks! I'll give this a try later... too busy for a troubleshooting session.

 

The last time I did do the full CMOS reset procedure you recommended. Had no problems until I tried to sleep from the Apple menu only; so far that is the only time my CMOS resets itself.

 

My config.plist has the correct setting for DisableRtcChecksum.

 

 

[Project 2501]

Dumb Question (TM) here... I've downloaded latest OCAT_Mac.dmg, but for some reason it is version 20220219 (the latest release according to download page) for OpenCore 0.7.8.

 

I'd like to use this to make updating my EFI easier, but I'm not sure where to get the latest one that is for a later version of OC>

[Project 2501]

 

6 hours ago, eSaF said:

Go here - https://github.com/ic005k/OCAuxiliaryTools/releases - for the latest version of OCAT which will update all OC files and kexts to the latest versions pertaining to your original Settings, plus it has within an OCvalidate app to check the configuration for you as well as checking for and indication old files.

 

 

That's where I got it from, yet the "about" box and and the upper left corner of the main window say "0.7.8", but the version number is correct. If I run the OC Validate tool, it flags items specific to the newer config.plist, so it is behaving like it is designed for OC 0.7.8.

 

Ever since OC 0.7.9, for some reason every time I download the utility, I get the one for 0.7.8. I don't get it.

 

I just downloaded it again on a real iMac and took a screenshot. The app version number is correct, but the OC version is stubbornly pegged at 0.7.8. I also ran your config.plist through the validator, so I should pass, but it flagged keys that were deprecated in the newer versions of OC.

 

Update: I tried running this on Catalina and Big Sur, and got the same behavior. I'm baffled.

 

**** Solved: I figured it out... I just needed to go to Edit > Upgraded OpenCore and Kexts > hit the "Get OpenCore" button to update.

 

 

Edited June 22, 2022 by Project 2501
Solved!!!

[Anto65]

@Project 2501  Try this ...

 

https://drive.google.com/file/d/1pdSfFr6zN-vpQ-WhPoERUWqZ3tuTu1Cq/view?usp=sharing

 

 

... import the latest beta build of OC OpenCore-0.8.2-RELEASE.zip

 

[panosru]

Hello! Is there any way to enable the "listen for hey siri" option? Thanks!

 

UPDATE:

I guess I'm the only one who would like to have that feature. From what I read, T2 chip is required for it to work or connected Airpods. The iMac 2019 that my EFI uses indicates to macOS that this iMac doesn't have T2 chip since that chip was introduced from 2020 model. I wonder, if I change my profile to use iMac 2020, will it work?

 

Thanks!

Edited June 29, 2022 by panosru

[pkdesign]

Updated to OC 082 with no issues. From what I can tell, there are no changes to config.plist.

[rob1980]

On 6/23/2022 at 8:40 PM, panosru said:

Hello! Is there any way to enable the "listen for hey siri" option? Thanks!

 

UPDATE:

I guess I'm the only one who would like to have that feature. From what I read, T2 chip is required for it to work or connected Airpods. The iMac 2019 that my EFI uses indicates to macOS that this iMac doesn't have T2 chip since that chip was introduced from 2020 model. I wonder, if I change my profile to use iMac 2020, will it work?

 

Thanks!

iMac Pro 2017 profile here, hey siri works with my AirPods if that helps.

[panosru]

@rob1980 Thanks for the info! As I expected, with AirPods the option "listen for hey Siri" is available but without them it is not, right?

 

I'm trying to find a way to trick the system into show the option "Listen for Hey Siri", but so far I couldn't find any way in doing that. The option isn’t available for me:

 

 

I think that could be because of iMac19,1 profile, since - as far as I'm aware - the option to listen for "Hey Siri" introduced in 2020 models.

 

UPDATE:

I changed my SMBIOS to iMac20,2, generated new serial etc. but still, the option "Listen for Hey Siri" isn't showing up. (PS: I'm gonna keep iMac20,2 profile instead of iMac19,1)

 

UPDATE2:

Ok, in order for the option to be available, a T1/2 chip is required, or.. connect airpods... !@#$#$ Apple...

 

UPDATE3:

Returning back to iMac19,1 profile...

Edited July 10, 2022 by panosru

[panosru]

installed macOS v12.5 without any issue on OC 0.8.3 [DEV]

[Blesh]

yeah. Here as well... macOS 12.5 with OC 0.82 upgraded with OCAT without any issue.

[pkdesign]

Same here!

On 7/24/2022 at 2:11 PM, Blesh said:

yeah. Here as well... macOS 12.5 with OC 0.82 upgraded with OCAT without any issue.

 

[juan e. jot]

On 7/23/2022 at 7:48 AM, panosru said:

installed macOS v12.5 without any issue on OC 0.8.3 [DEV]

 

On 7/24/2022 at 11:11 AM, Blesh said:

yeah. Here as well... macOS 12.5 with OC 0.82 upgraded with OCAT without any issue.

 

2 hours ago, pkdesign said:

Same here!

 

The 12.5 update worked for me as well, with OC 0.8.2 via OCAT.

 

Perhaps because I used a USB stick with OC 0.8.0 in its EFI to update, rather than running an incremental update from the NVMe, it initially had a bit of trouble with WiFi and sound (sound via HDMI is a fairly common issue, usually needing a restart). Indeed, a restart fixed it & both WiFi & sound work fine now.

[Project 2501]

On 6/22/2022 at 3:22 AM, eSaF said:

@Project 2501 - Hi I have the same Motherboard as you and don't have that problem, Sleep/Wake works perfect for me. The thing is with CMOS resetting you need to check that this setting in the config.plist is set like the attached. When this happens, you should down the p/c, remove the power cable, press the power button for approx 15 seconds to dispel any latent power in the capacitors. Now remove the CMOS battery for approx 15 seconds.

After replacing the battery and power cable, power up the machine which should induce a message about a BIOS reset and should boot straight into the BIOS.

 

Look at the BIOS Clock albeit the Time and Year will be wrong and will need resetting, take note at the Seconds Digits, it should be counting up the Seconds, if it is static (not moving) then the CMOS reset was not successful and will continue to be problematic but if the steps as describe are done properly, you will not have a recurrence of the CMOS problem.

My attached EFI Folder is OC 0.8.2  version with latest kexts versions, booting BS, Monterey and now Ventura with no problems, all Apple Services i.e iMessage, F/Time, Apple TV, App Store etc all perfect and working.

 

Try my folder on a test USB  drive by booting off it after cleaning the Nvram and see the result, you'll need to furnish the config.plist with your own data i.e S/N, SmUUID, ROM etc as I removed mine. Good luck.

  Reveal hidden contents

EFI.zip 84.43 MB · 10 downloads

 

 

Hi again!

 

I finally have some free time to try out your EFI. Over a month has passed since you first attached your EFI, so I used OCAT to update OC to 0.8.2-Release; also updated the KEXTs and drivers to the latest versions.

 

I just have a few questions before I give it a test drive. I compared your EFI with my current one that was based on @AudioGod's original, and I understand most of the changes, but there are a few items I'm not sure what they are for.

 

1. SSDT-6.aml: This is not present in my current EFI. I'm not sure what this does.
2. eSaFNVMeFix.kext: Neither NVMeFix.kext or eSaFNVMeFix.kext are present in my current EFI. How is this different from the regular NVMeFix.kext? Where do I go to keep this updated?
3. USBMap.kext: This is missing from @eSaF's EFI, but is present in mine. Not needed anymore? How are USB ports mapped in your EFI?
4. Model Identifier iMac20,2: I've been using iMac19,1 up to this point. I assume this is a better match.

Thanks again for posting your EFI! Hopefully it will solve my sleep issues.

 

[Project 2501]

On 7/28/2022 at 3:46 AM, eSaF said:

@Project 2501 - To answer your questions, 1. The SSDT-6.aml is the USB Mapped file that replaced the USBMap.kext and was created using the USBTool Box (https://www.google.com/url?sa=t&rct=j&q=&esrc=s&source=web&cd=&cad=rja&uact=8&ved=2ahUKEwjQqNeZr5v5AhXMiVwKHX9aBhQQFnoECAYQAQ&url=https%3A%2F%2Fgithub.com%2FUSBToolBox%2Ftool&usg=AOvVaw25yEK7NBqRx4bnk68nMm1x)

2. The eSaFNVMeFix.kext is a modified NVMeFix.kext to display 'Apple SSD Controller' instead of 'Generic SSD Controller' in System Report but is purely cosmetic (see attached) and is catered solely for my machine, I should have removed it and use the generic NVMeFix.kext, there is a tutorial on I/M how this is done.

3. USBMap.kext as explained in 1.

4. Model Identifier iMac20,2 is what I use for preference, use whatever Mac model is to your liking.

  Reveal hidden contents

 

 

Well, I finally got a chance to try it out. I changed the ID to iMac19,1, added the SSDT for the Titan Ridge TB3 card, and removed boot picker themes I won't be using... Of course, I reset the NVRAM as well. I'm currently using the BIOS setting recommended by @AudioGod's original guide.

 

Unfortunately, it still doesn't sleep properly if I choose to do it manually from Apple menu. I haven't tried letting it sleep from inactivity. However, the sleep behavior has changed. When I try to wake it from sleep, it reboots instead. This is marginally better, since the previous behavior had it "hang" after waking, leaving me with an unresponsive machine with no display output, and it would cause my BIOS to reset.

 

For some reason, my Windows 10 drive in the boot picker menu is shown as "Windows 11 Pro" instead of the drive name.

 

The boot picker icons are displayed larger and the background picture fills the entire screen now. With my previous EFI, the background picture was centered on the background color and the icons were displayed smaller.

 

I was startled to hear the Apple startup chime! Never bothered to turn this on before since I installed an old school piezoelectric beeper.

 

Oh well... even though it didn't solve my sleep issues, it didn't hurt to update to the latest OC and drivers.

 

 

[Ziadantosh]

On 7/23/2022 at 3:48 PM, panosru said:

installed macOS v12.5 without any issue on OC 0.8.3 [DEV]

Great to hear! @panosru

I have almost identical hardware to yours, so just follow the guide in the beginning of this post + latest OC and OCAT would work fine? I am aiming for latest Monterey

Edited August 1, 2022 by Ziadantosh
added a mention

[pkdesign]

Updated to OC 083 with OCAT with no issues.

[juan e. jot]

6 hours ago, pkdesign said:

Updated to OC 083 with OCAT with no issues.

Same here, with 12.5. Model firmware now appears to be declared old (I check using EclecticLightCo’s SilentKnight), but functionality remains.

Expected model firmware is often updated by the fruit company with OS updates, but sometimes afterwards (as in this case). For our hacks, nothing actually gets updated in NVRAM, hence SilentKnight being the only nag.

Just wait for the next full OC release, or if you think it’s stable enough (and important enough to you; YMMV), watch OC commits on GitHub for an OC 0.8.4 pre-release with updated model firmware .yaml’s.

Due to no loss in functionality, this will likely be a non-issue for most… unless the fruit company may be watching who gets OS updates but somehow resists their model firmware updates.

And when that cat-and-mouse game all gets to be too much to maintain, there’s (gasp!) always Linux.

Digressions aside, happy hacking!

[Ziadantosh]

Hi everyone,

 

I would a simple advice if possible, basically I have Mojave (Clover) on a small SSD and seems to be working so I occatinally use for browsing and downloading.

I have also Big Sur 11.0.1 Beta on another SSD which boots up fine using OC 0.6.x

Now I'd like to install Monterey to replace Big Sur on the same disk, and I made a USB installer but I got a fatal error straight away, I don't know what I did wrong!

I am thinking to start over, so download Monterey to the USB, then customize EFI - My Mobo config works for both above so I don't think I need to change anything there.

 

Any advice on simple 1,2,3 steps?

 

Hardware:

i9-9900K | GA-Z390 Auros Pro | Sapphire Nitro+ RX 480 8GB (works fine in Mojave and Big Sur) | 16GB Corsair vengence RGB Pro | 500GB SSD

 

Many thanks in advance

[pkdesign]

38 minutes ago, Ziadantosh said:

Hi everyone,

 

I would a simple advice if possible, basically I have Mojave (Clover) on a small SSD and seems to be working so I occatinally use for browsing and downloading.

I have also Big Sur 11.0.1 Beta on another SSD which boots up fine using OC 0.6.x

Now I'd like to install Monterey to replace Big Sur on the same disk, and I made a USB installer but I got a fatal error straight away, I don't know what I did wrong!

I am thinking to start over, so download Monterey to the USB, then customize EFI - My Mobo config works for both above so I don't think I need to change anything there.

 

Any advice on simple 1,2,3 steps?

 

Hardware:

i9-9900K | GA-Z390 Auros Pro | Sapphire Nitro+ RX 480 8GB (works fine in Mojave and Big Sur) | 16GB Corsair vengence RGB Pro | 500GB SSD

 

Many thanks in advance

 

Just follow the steps in the original post BUT update to OC 0.8.3. Then create a boot USB with that EFI and see if it boots and works properly. If it does, you can then copy that EFI to the EFI partition on your SSD.

 

OCAT if your friend. I use to do all this updating manually but OCAT just works so well.

 

[Ziadantosh]

21 minutes ago, eSaF said:

If you're still using OC 0.6.x as indicated in your post, it is grossly outdated for starters. I would suggest using OCAT app to update OC and all your kexts files and then take it from there.

That's exactly what I am trying to do now, hopefully it won't break!

But let's say updated and happy, next step I need to create Monterey USB installer, this is where I am a little confused as to what to replace in the EFI of the USB, or should I just copy the current EFI from my Big Sur when I update it with OCAT?

[pkdesign]

I may not understand your question, but I have never used an installer USB (at least not for many years). I have just updated via Software Update and havn't had a problem.

[Cipha]

Hey guys, I just installed a WD Black NVME but I only get speeds around 1.5gb read and write in Blagmagic speed test. 

 

Do have to change anything to use its full potential? I also see the loading beach ball a lot of time, like something is really limiting performance.

 

I used to have a Samsung NVME before which ran great but booted very slow...

[deeveedee]

@Cipha after posting the below (which you should still read), I learned something about M.2 on Aorus Z390 Pro: The two M.2 slots have different bandwidth sharing properties, so their performance will vary depending on the other accessories installed in your rig.  It may be that your M.2 slot is operating in x2 mode or is sharing bandwidth depending on what other devices (including any SATA drives) are installed in your rig.

 

@Cipha I happened to see your post and while I don't have your same system, you should expect to see better performance from your WD Black NVMe drive.  My BlackMagic speed test results are below.  Here are the questions I would ask:

• What is the specific model and capacity of your WD Black NVMe Drive?
• Did you purchase your drive new or used?
• Have you booted the drive in Windows to make sure it has the latest firmware?
• Have you tested the drive in Windows with a tool like Crystal Disk Info to examine the drive for errors?
• How full is the drive?

BlackMagic Speedtest for WD SN750 Black NVMe drive (500GB)

Spoiler

 

If this issue isn't specific to the Aorus Z390 Pro (the topic of this thread), your quesiton may be off-topic, so you may need to move this discussion to another thread.

Edited August 4, 2022 by deeveedee

[Cipha]

@deeveedee Thank you! Your stats look good, just what I would have expected.

 

It's the SN750 with 1TB storage

it was bought new

it is abour 35% full

 

I didn't booted the drive into windows. I will see if I can update the firmware in macos as well.

 

Any other ideas - aside from firmware - what could cause this?

I could find any similar problems with this SSD

[panosru]

Updated to OC v0.8.4 [DEV], works fine. It requires the "LoadEarly" property under UEFI -> Drivers to be set to false for all efis except OpenRuntime.efi: