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

[AudioGod]

1 minute ago, Cameron Nicholson said:

Really silly question will the pump still work, will the fans still ramp up? 

 

Also I edited my post, I don't have working NVRAM. 

Yes everything will work exactly the same, the fans are controlled by the h100i and it’s settings are stored in its firmware and the pump works the same way but gets its power from the sata power connection. 

[Cameron Nicholson]

Just now, AudioGod said:

Yes everything will work exactly the same, the fans are controlled by the h100i and it’s settings are stored in its firmware and the pump works the same way but gets its power from the sata power connection. 

Ok, is there a way to just tell macOS to ignore it?

[Tiem]

No, you can't tell macOS to ignore your cooling system.

[Cameron Nicholson]

10 hours ago, Tiem said:

No, you can't tell macOS to ignore your cooling system.

Ok,

 

Also I just updated to 10.15.2 and got a error "Critical Error, no load image, halting" something like that, I managed to boot with my OC USB and all seems fine but anyone know what causes that?

 

Also in my boot devices I still have Clover boot.efi?????

 

Thanks

Edited January 27, 2020 by Cameron Nicholson
Added information

[gabe.p]

@Cameron Nicholson I was having the same error so I used opencore from the creators github in combination with audios other files including his config.plist and got passed that error

[WizeMan]

This is just to report that I upgraded to macOS Catalina 10.15.3 and everything seems to be super OK with the OpenCore variant.

 

 

Edited January 29, 2020 by WizeMan

[AudioGod]

Everybody’s loving NDK OpenCore at the moment...there’s a clear shift from clover happening with all the die hards on the thread. Fascinating 

[pkdesign]

Not until they provide themes

[pkdesign]

Quick question about CFG LOCK. I followed instructions here:

https://khronokernel-2.gitbook.io/opencore-vanilla-desktop-guide/extras/msr-lock

and now all I see in log is:

 

0:100  0:000  MSR 0xE2 before patch 1E000000

 

Also when I test using GRUB shell is shows that variable (which was at 0x5C1) as 0x00.

 

Does this mean I have unlocked it?

[Tiem]

Updated to the public release of 10.15.3. Works fine but the update process killed my EFI clover entry for some reason. Had to restore it using BOOTICE. But both Clover and OC run it fine.

 

One thing I noticed using OC is that I got little sporadic stutters. It's nice, feels really native, but tbh, Clover operates much smoother. OC looks amazing, but it's still pretty soon in the development cycle to rely on it for a production system.

[Tiem]

39 minutes ago, pkdesign said:

Quick question about CFG LOCK. I followed instructions here:

https://khronokernel-2.gitbook.io/opencore-vanilla-desktop-guide/extras/msr-lock

and now all I see in log is:

 

0:100  0:000  MSR 0xE2 before patch 1E000000

 

Also when I test using GRUB shell is shows that variable (which was at 0x5C1) as 0x00.

 

Does this mean I have unlocked it?

That guide is wrong. Do not use setup_var 0x5C1 0x00, it will error out and not actually apply the variable. You have to use setup_var_3. You'll still receive the error, but it will patch the firmware regardless. Read more here: https://www.tonymacx86.com/threads/successfully-patched-z170x-ud5-th-cfg-lock-msr-ex02.253466/page-2#post-1847437 (see reply #26 for more details on using setup_var_3).

 

And 

Edited January 29, 2020 by Tiem

[AudioGod]

21 minutes ago, Tiem said:

Updated to the public release of 10.15.3. Works fine but the update process killed my EFI clover entry for some reason. Had to restore it using BOOTICE. But both Clover and OC run it fine.

 

One thing I noticed using OC is that I got little sporadic stutters. It's nice, feels really native, but tbh, Clover operates much smoother. OC looks amazing, but it's still pretty soon in the development cycle to rely on it for a production system.

 

your spot on there bud,

its improving really fast though so it won't be much longer before it becomes the standard I reckon.

Id say by the end of this year tbh and one other thing I'm noticing is nobody wants to know about doing intel builds anymore or should I say the percentage on new intel hack and normal builds is declining rapidly.

a perfect example is go on YouTube and look for a open core guide that isn't for a Ryzentosh? Its quiet mad.

Also at my day job for every one intel build there 7 Ryzen ones. Only 6 months ago that was the other way around...yikes intel you dropped the ball hard 

[pkdesign]

Okay, so i used the

setup_var_3 0x5C1 0x00

and got the same result. Same question, so it is now unlocked? Should I not see a new entries in the BIOS/UEFI screens?

 

And yes, I deleted the KernelPM and AppleIntelCPUPM entries in my clover config.

Edited January 29, 2020 by pkdesign

[Cass67]

14 hours ago, AudioGod said:

Everybody’s loving NDK OpenCore at the moment...there’s a clear shift from clover happening with all the die hards on the thread. Fascinating 

 

Yeah its interesting and seems to do something to the hw different from Clover.  Switching to OC removes the need for me to use VoodooHDA, sleep/wake with OC and AppleALC does not panic kernel on wake like Clover does, that was enough to make the switch.. Not using NDK but stock OC btw. 

[AudioGod]

Just now, Cass67 said:

 

Yeah its interesting and seems to do something to the hw different from Clover.  Switching to OC removes the need for me to use VoodooHDA, sleep/wake with OC and AppleALC does not panic kernel on wake like Clover does, that was enough to make the switch.. Not using NDK but stock OC btw. 

how are you booting into windows if you need too?

[Cass67]

Just now, AudioGod said:

how are you booting into windows if you need too?

 

F12 boot selection..  Rarely use Windows so its no hardship..

[AudioGod]

3 minutes ago, Cass67 said:

 

F12 boot selection..  Rarely use Windows so its no hardship..

Yeah you see that’s a big problem for me.

we actually have a 2 real versions of oc under test now. V055 one dsdt free and done the way OC recommend and a second and in my opinion better version where Texem patched the real version of OC to bypass the dsdt if booting into any other OS.

both work well but using a dsdt sure is the better of the two.

that could change as we perfect things though  

Edited January 30, 2020 by AudioGod

[Cass67]

1 minute ago, AudioGod said:

Yeah you see that’s a big problem for me.

we actually have a 2 real versions of oc under test now. V055 one dsdt free and done the way OC reckoned and a second and in my opinion better version where Texem patched the real version of OC to bypass the dsdt if booting into any other OS.

both work well but using a dsdt sure is the better of the two.

that could change as we perfect things though  

Nice, Ill be keeping an eye on your findings for sure

V55 seems real nice with your DSDT, just upgraded to 10.15.3 pain free.

 

I preferred to use stock since it seems like there is less people needing to make a patch here or there to OC code to get additional features as provided with NDK.  I don't need them at this time.  Saying that if there is a potential for a fully working non DSDT build that sure would be interesting..

 

The main thing that put me off the NDK version was on the NDK thread where he said he was done with development of the mod, just maintaining to keep parity with version upgrades. If one or more who mod the original code for feature x or y get bored or move on then there is potential to be stuck.   I figured screw it, ill move to the main code base and take my chances with that..   

[AudioGod]

1 minute ago, Cass67 said:

Nice, Ill be keeping an eye on your findings for sure

V55 seems real nice with your DSDT, just upgraded to 10.15.3 pain free.

 

I preferred to use stock since it seems like there is less people needing to make a patch here or there to OC code to get additional features as provided with NDK.  I don't need them at this time.  Saying that if there is a potential for a fully working non DSDT build that sure would be interesting..

 

The main thing that put me off the NDK version was on the NDK thread where he said he was done with development of the mod, just maintaining to keep parity with version upgrades. If one or more who mod the original code for feature x or y get bored or move on then there is potential to be stuck.   I figured screw it, ill move to the main code base and take my chances with that..   

na I think you misunderstood what he meant by saying that.

all he ever wanted to achieve were the little things like bypassing dsdt and ssdt in other os and being able to select your boot drive just by selecting it and since he achieved all of that with flying colours there’s nothing left for him to do other then keep it in parity with the real deal. I think that’s a very good thing as he never tried to make he’s own version he just tweeked it and in a lot of people’s opinions made it better and good on him I say. 

[Cass67]

1 minute ago, AudioGod said:

na I think you misunderstood what he meant by saying that.

 all he ever wanted to achieve were the little things like bypassing dsdt and ssdt in other os and being able to select your boot drive just by selecting it and since he achieved all of that with flying colours there’s nothing left for him to do other then keep it in parity with the real deal. I think that’s a very good thing as he never tried to make he’s own version he just tweeked it and in a lot of people’s opinions made it better and good on him I say. 

 

Understood fine bud, just think since i have OC working as it is from the main code base and i don't need any of the features of the NDK mod then im probably better off and having less risk just using stock since there is less need for others to mod it to get the features i now rely on (if i did).  Anyway not trying to complain or knock the guys work or reasons, im just mentioning why i moved to stock and that we on here are not all on NDK (as per your post i initially replied to).  Good on him (and others) for diving in and making changes useful to him and whoever else, the plist from the NDK EFI on here is what got me going with stock which i probably would not have bothered with had it not been such a simple transition due to this.  So thanks to whoever was involved, its working out real nice !! 

[AudioGod]

1 minute ago, Cass67 said:

 

Understood fine bud, just think since i have OC working as it is from the main code base and i don't need any of the features of the NDK mod then im probably better off and having less risk just using stock since there is less need for others to mod it to get the features i now rely on (if i did).  Anyway not trying to complain or knock the guys work or reasons, im just mentioning why i moved to stock and that we on here are not all on NDK (as per your post i initially replied to).  Good on him (and others) for diving in and making changes useful to him and whoever else, the plist from the NDK EFI on here is what got me going with stock which i probably would not have bothered with had it not been such a simple transition due to this.  So thanks to whoever was involved, its working out real nice !! 

Good stuff buddy enjoy and I know you weren’t knocking him no worries, I was just explaining what he meant by what he said  

[Tiem]

5 hours ago, AudioGod said:

 

your spot on there bud,

its improving really fast though so it won't be much longer before it becomes the standard I reckon.

Id say by the end of this year tbh and one other thing I'm noticing is nobody wants to know about doing intel builds anymore or should I say the percentage on new intel hack and normal builds is declining rapidly.

a perfect example is go on YouTube and look for a open core guide that isn't for a Ryzentosh? Its quiet mad.

Also at my day job for every one intel build there 7 Ryzen ones. Only 6 months ago that was the other way around...yikes intel you dropped the ball hard 

Absolutely. Looks really promising. Even at 0.5 it runs amazing given how new it is.

 

Hey Intel had the reigns since forever. Nice to see AMD pulling the lead on processing power! I'd actually love to see Apple switch to AMD (even tho they'll most definitely just transition to ARM).

 

Also, if you're ever in need of guinea pigs, hit me up. I have a pretty barebones system. Your EFIs have always worked without no fiddling.

Edited January 30, 2020 by Tiem

[stavidawg]

So forgive me if this is a stupid question..

I have the same set up except I am using an MSI Radeon RX570, and I am unsure if perhaps my card (graphics & wifi) are in the same slots.

 

Can I use the EFI folders provided at the front page and simply edit the graphics config.plist to work with the RX570?

 

I saw that is was verified that the RX570 works, is there anyone out there using it that would wan't to share there EFI folder with me?

 

Thanks in advance!

[AudioGod]

18 minutes ago, stavidawg said:

So forgive me if this is a stupid question..

I have the same set up except I am using an MSI Radeon RX570, and I am unsure if perhaps my card (graphics & wifi) are in the same slots.

 

Can I use the EFI folders provided at the front page and simply edit the graphics config.plist to work with the RX570?

 

I saw that is was verified that the RX570 works, is there anyone out there using it that would wan't to share there EFI folder with me?

 

Thanks in advance!

You don’t need to do any editing other then adding your details, there is a EFI for your setup already.

use this one buddy  

 

Aorus Z390 Pro RX Polaris F12d EFI .zip - Use with Bios revision F12d Only (15/01/2020 Catalina 10.15.2 RX5XX Polaris DSDT Installed) SMBios 19,1

 

or for OpenCore (NDK Fork) Then use this one.

 

N-D-K OpenCore RX Polaris F12d EFI.zip - RX Polaris Series DSDT Bios F12d

Edited January 31, 2020 by AudioGod

[stavidawg]

2 hours ago, AudioGod said:

You don’t need to do any editing other then adding your details, there is a EFI for your setup already.

use this one buddy  

 

Aorus Z390 Pro RX Polaris F12d EFI .zip - Use with Bios revision F12d Only (15/01/2020 Catalina 10.15.2 RX5XX Polaris DSDT Installed) SMBios 19,1

 

or for OpenCore (NDK Fork) Then use this one.

 

N-D-K OpenCore RX Polaris F12d EFI.zip - RX Polaris Series DSDT Bios F12d

This is Wonderfull!

 

So I just tried to install the newest Catalina version (10.15.3) but after I select my "install Catalina" external drive and the apple boot screen comes up, I get the big circle with a line through it. 

 

My first question would be, are your current bios settings the same as what you have listed in post #1?

I saw that post 1 referred to using bios 11, so wasn't sure if possibly some things had changed?