AudioGod's Aorus Z390 Master Patched DSDT EFI for Catalina Mini Guide and Discussion

[decat]

Thanks for the positive help, found your other post some hours ago but didn't had the time to swap them yet. Hopefully somewhere during the night.

[Benjamin Franklin]

I don’t know if you are coming from Audiogod’s Clover EFI or another. If it’s not Audiogod’s then make sure to check the /library/extensions folder for kexts that could or should be (re)moved. (Thinking of fakesmc for one).

[Blesh]

15 hours ago, Benjamin Franklin said:

Just replace your Clover EFI with the OC EFI, copy your serial, rom and mlb (and check if have MSR enabled) and you’re done. That’s what I did and it works perfectly. Very stable. On the first boot I did a clear nvram, nothing else. In case it wet sideways I had a USB with my working clover EFI ready.

Did you do that in this order?

1. Replace Clover EFI with OC EFI

2. Reboot and clear nvram (where can I clean my nvram? is there a shortcut shown on the screen?)

3. Install Big Sur

[AudioGod]

3 hours ago, Blesh said:

Did you do that in this order?

1. Replace Clover EFI with OC EFI

2. Reboot and clear nvram (where can I clean my nvram? is there a shortcut shown on the screen?)

3. Install Big Sur

When you get to the OpenCore bootpicker press the space bar to reveal the option to clear the NVram and then clear it a couple of times before booting into macOS using OC for the first time.

also make sure you remove RC scripts if you were using them in clover or your have all sorts of trouble.

Edited October 12, 2020 by AudioGod

[decat]

On 10/11/2020 at 10:09 PM, Benjamin Franklin said:

I don’t know if you are coming from Audiogod’s Clover EFI or another. If it’s not Audiogod’s then make sure to check the /library/extensions folder for kexts that could or should be (re)moved. (Thinking of fakesmc for one).

 

Indeed, (was) running AudioGod's Clover till some minutes ago and ran great since January.

Switched to the latest OC, had an security issue while booting ( see below). After a quick search in Google I had to disable the SecureBootModel and boots fine since then!

No one else had this?

 

Thanks again for the help / info all!

 

OCSB: No suitable signature - Security Violation
OCB: Apple Secure Boot prohibits this boot entry, enforcing!
OCB: LoadImage failed - Security Violation

 

[hungrywallet]

Sorry for the stupid question as I been out of the loop for a while now.

 

Does booting Windows from Opencore still transfer over the ACPI stuff from MacOS?

[Locked Down]

2 minutes ago, hungrywallet said:

Sorry for the stupid question as I been out of the loop for a while now.

 

Does booting Windows from Opencore still transfer over the ACPI stuff from MacOS?

 

No, you should be fine.

[hungrywallet]

1 minute ago, Locked Down said:

 

No, you should be fine.

 

Thanks, when was this behavior changed?  I was reading through the documentation and see no mentions of it.

[Locked Down]

3 minutes ago, hungrywallet said:

 

Thanks, when was this behavior changed?  I was reading through the documentation and see no mentions of it.

 

Can't remember the version number, but it has been good for quite a while now.

[AudioGod]

22 minutes ago, hungrywallet said:

Sorry for the stupid question as I been out of the loop for a while now.

 

Does booting Windows from Opencore still transfer over the ACPI stuff from MacOS?

Yes indeed it does buddy and always will. OC want to have the bios details the same across all OS so the ACPI carries though along with various other settings and quirks.

the ssdts are all bypassed to not affect other OS but they still all read.

Edited October 14, 2020 by AudioGod

[Locked Down]

38 minutes ago, AudioGod said:

Yes indeed it does buddy and always will. OC want to have the bios details the same across all OS so the ACPI carries though along with various other settings and quirks.

the ssdts are all bypassed to not affect other OS but they still all read.

 

In your first sentence you say "Yes......ACPI carries though along with various other settings and quirks".

 

And then you say "the ssdts are all bypassed to not affect other OS"

 

In other words you are saying they are carried through into Windows and then you say they aren't. 

 

Which one do you mean.

 

 

[AudioGod]

3 minutes ago, Locked Down said:

 

In your first sentence you say "Yes......ACPI carries though along with various other settings and quirks".

 

And then you say "the ssdts are all bypassed to not affect other OS"

 

In other words you are saying they are carried through into Windows and then you say they aren't. 

 

Which one do you mean.

 

 

Yes the info inside the ssdt is  bypassed and yes they also still read but certain info is bypassed so windows still works but the acpi and the ssdts are loaded in to other OS along with certain quirks and other info.

read the manual dude and learn

Edited October 14, 2020 by AudioGod

[Locked Down]

2 minutes ago, AudioGod said:

Yes the info inside the ssdt is  bypassed and yes they also still read but certain info is bypassed so windows still works but the acpi and the ssdts are loaded in to other OS along with certain quirks and other info.

read the manual dude and learn

 

No need to be rude.

 

So in lay man's terms, the ACPI info is not passed through to Windows, as I said originally.

[hungrywallet]

4 hours ago, AudioGod said:

Yes indeed it does buddy and always will. OC want to have the bios details the same across all OS so the ACPI carries though along with various other settings and quirks.

the ssdts are all bypassed to not affect other OS but they still all read.

 

Thanks for the answer.  This causes my Windows to become deactivated like mentioned in the manual.  I'll have to see if I can add another UEFI entry so that if I need to boot into Windows I do it via UEFI instead of OpenCore.  

[AudioGod]

10 minutes ago, Locked Down said:

 

No need to be rude.

 

So in lay man's terms, the ACPI info is not passed through to Windows, as I said originally.

OpenCore wants to keep everything in line so you can go into windows and windows thinks your on a 19,1 iMac or whatever smbios your using so to do this a lot of the kernel and acpi, booter quirks, system info etc etc need to remain active for other OS to understand it’s a 19,1 iMac say but at the same time things like ssdt pm etc cause other OS to freak out so there’s bypasses inside the ssdt to stop other OS from reading it. Everything else still carries across otherwise.

 

Make since now Bro?

 

5 minutes ago, hungrywallet said:

 

Thanks for the answer.  This causes my Windows to become deactivated like mentioned in the manual.  I'll have to see if I can add another UEFI entry so that if I need to boot into Windows I do it via UEFI instead of OpenCore.  

 

That’s happening because your not using the boards true uuid and your using a generated one instead.

pull your true uuid and MAC address from your board and replace your plist info with it and that will be the end of the problem for you.

Edited October 14, 2020 by AudioGod

[Locked Down]

2 minutes ago, AudioGod said:

OpenCore wants to keep everything in line so you can go into windows and windows thinks your on a 19,1 iMac or whatever smbios your using so to do this a lot of the kernel and acpi, booter quirks, system info etc etc need to remain active for other OS to understand it’s a 19,1 iMac say but at the same time things like ssdt pm etc cause other so to freak out so there’s bypasses inside the ssdt to stop other OS from reading it. Everything else still carries across otherwise.

 

Make since now Bro?

 

So that confirms what I said - the ACPI (SSDTs) info is not passed through to Windows, or indeed Linux, just macOS.

[AudioGod]

6 minutes ago, Locked Down said:

 

So that confirms what I said - the ACPI (SSDTs) info is not passed through to Windows, or indeed Linux, just macOS.

some of the insides are bypassed not all. ACPI quirks still load and so do the ssdts just not all the info inside them.

simple as that

 

hes question was about the ACPI (as a whole I took that) not the ssdts.

can we stop with the I’m right no I’m right games now please pal?

Nice one lol

Edited October 14, 2020 by AudioGod

[Locked Down]

18 minutes ago, AudioGod said:

some of the insides are bypassed not all. ACPI quirks still load and so do the ssdts just not all the info inside them.

simple as that

 

hes question was about the ACPI (as a whole I took that) not the ssdts.

can we stop with the I’m right no I’m right games now please pal?

Nice one lol

 

Fine by me, just wanted to clear up any confusion that may exist for others reading the thread.

[AudioGod]

3 minutes ago, Locked Down said:

 

Fine by me, just wanted to clear up any confusion that may exist for others reading the thread.

 
well to be honest all you really did is cause bare confusion..lol..even to me as you can’t take the ACPI to mean a ssdt or that’s what would of been asked. My original answer is correct and hopefully you understand that now.

 

why do you want to have beef with me anyway brother? I’m cool and actually a nice guy but anytime I read your comments they are always prickly. Maybe you don’t mean it but that’s how you come across.

 

im willing to start again if you are anyway as I just wanna be cool. That sound good to you fella?

@Locked Down Are you a U.K. bod like me?

 

Edited October 14, 2020 by AudioGod

[Locked Down]

I'm cool with anything - so laid back that I fall asleep standing up.

 

One more question for you.

 

For those who don't want Windows to think it is running on a Mac, which may cause Windows to be deactivated and need reactivating with a different key if macOS was installed after Windows, have you ever tried setting PlatformInfo  - UpdateSMBIOSMode = Custom ?

I use this on my machines and never had any issue and Windows doesn't think it is an iMac or Mac Pro or anything else.

[AudioGod]

6 minutes ago, Locked Down said:

I'm cool with anything - so laid back that I fall asleep standing up.

 

One more question for you.

 

For those who don't want Windows to think it is running on a Mac, which may cause Windows to be deactivated and need reactivating with a different key if macOS was installed after Windows, have you ever tried setting PlatformInfo  - UpdateSMBIOSMode = Custom ?

I use this on my machines and never had any issue and Windows doesn't think it is an iMac or Mac Pro or anything else.

yes and it works but I know vit doesn’t like it being in there and will stop it working sooner or later so I leave it be.

windows will only deactivate if you use a custom uuid and rom instead of the boards ones.

just pull the real ones from your motherboard and then replace the custom info in your plist with the real ones and windows will recognise it correctly and stay activated, 

any other way like doing what your doing with the Custom smbios is just hiding the problem and that’s fine too but correct is correct no?

Edited October 14, 2020 by AudioGod

[Locked Down]

Some people don't know how to do that so just wanted to make others aware that there is a work around if Windows gets deactivated and they don't have another legit key to use.

 

After all, everything about booting macOS on our own hardware is about compromises.

[AudioGod]

4 minutes ago, Locked Down said:

 

After all, everything about booting macOS on our own hardware is about compromises.

this is true but it’s not a work around I would advise and instead just tell them how to pull there own info. It’s even in the manual to read how to do it too.

again correct is correct and the way you suggest works for now but it’s nothing more then a work around and not a long term solution. As it will break sooner or later for the reason I said in my last post,

If I had more confidence in that method I would actually drop using ssdts and move over to my OpenCore DSDTs instead but I know that if I did that it would come back to bite me in an update or two so I figure it’s best to stay well away...lol...imagine the headache it would cause me? 
No Thank you very much 

[hungrywallet]

1 hour ago, AudioGod said:

OpenCore wants to keep everything in line so you can go into windows and windows thinks your on a 19,1 iMac or whatever smbios your using so to do this a lot of the kernel and acpi, booter quirks, system info etc etc need to remain active for other OS to understand it’s a 19,1 iMac say but at the same time things like ssdt pm etc cause other OS to freak out so there’s bypasses inside the ssdt to stop other OS from reading it. Everything else still carries across otherwise.

 

Make since now Bro?

 

 

That’s happening because your not using the boards true uuid and your using a generated one instead.

pull your true uuid and MAC address from your board and replace your plist info with it and that will be the end of the problem for you.

 

Thanks for the info.  Might already be too late for me since MS has already flagged my machine as being different and even changing everything back to stock is giving me issues.  I may just reinstall again and see if it activates and if not I'll just give them a call.

 

You were right though, I had a custom UUID set and brought over from Clover days.  I also never changed the ROM info for Opencore.  Set everything to match my true motherboard info so moving forward I should be fine.

 

Thanks again.

[AudioGod]

7 minutes ago, hungrywallet said:

 

Thanks for the info.  Might already be too late for me since MS has already flagged my machine as being different and even changing everything back to stock is giving me issues.  I may just reinstall again and see if it activates and if not I'll just give them a call.

 

You were right though, I had a custom UUID set and brought over from Clover days.  I also never changed the ROM info for Opencore.  Set everything to match my true motherboard info so moving forward I should be fine.

 

Thanks again.

Yes buddy that will sort it out once and for all. 
 

also you don’t need to reinstall windows just reactivate it and windows will pick it up when it see the correct info and activate again  

 

Edited October 14, 2020 by AudioGod