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

[AudioGod]

3 minutes ago, n19htz said:

I wrote to gigabyte support about this problem as well. As myhackintosh is never goes off - the problem is very annoying  Anyway^ gonna post here when I get response from gigabyte.

don’t worry buddy I’m on it and I have a hotline to gigabyte because of my real world job so they will get back to me and be honest to me too and they listen to me most of the time so they should do something about it. 
il let you know as soon as they get back to me about it if they don’t respond to you first. 

Edited April 29, 2020 by AudioGod

[pkdesign]

10 hours ago, kiko89 said:

2. Another question: is there any way to verify that MSR unlocked correctly? I ask this because despite having removed the motherboard battery before fresh install, I saw that the profile remained in bios memory.

 

Easy, open Hackintool>Utilities>AppleIntelInfo (first button near bottom):

 

You will see this:

MSR_PMG_CST_CONFIG_CONTROL........(0xE2) : 0x7E000008
------------------------------------------
 - I/O MWAIT Redirection Enable......... : 0 (not enabled)
 - CFG Lock............................. : 0 (MSR not locked)

Check CFG Lock in resulting log.

Edited April 29, 2020 by pkdesign

[Alex1982]

After removing Windows Recovery partition the issue is gone and I able to reboot into Windows from macOS "Startup Disk" utility under OC. @AudioGod, just curious, there is a NDK fork of OC which support boot picker GUI, ignoring OC quirks for other OS than macOS and some other stuff. Could you please clarify does it provide some real benefits or it is better to stick with original OC?

Edited April 29, 2020 by AlexeyNikitin

[AudioGod]

17 minutes ago, AlexeyNikitin said:

After removing Windows Recovery partition the issue is gone and I able to reboot into Windows from macOS "Startup Disk" utility under OC. @AudioGod, just curious, there is a NDK fork of OC which support boot picker GUI, ignoring OC quirks for other OS that macOS and some other stuff. Could you please clarify does it provide some real benefits or it is better to stick with original OC?

Well done buddy,

NDK OC is the same thing really but it allows me to run a dsdt using it and that’s something I can’t do on original OC. I have a ready made EFI of NDK OpenCore on page one that’s fully up to date if you want to try it.

it has a nice theme set by me on it too for the bootpicker.

 

personally I prefer the real deal OpenCore but each to there own and that’s why I have all 3 bootloaders available to download. 
 

Clover, OpenCore or the NDK fork are all equally as good as each other.

whats the best of the 3 you may ask yourself and to that I have to say clover but only for one reason and one reason alone.

Clover is release and tried tested and true where as OC is beta and a work in progress and this means with every revision it totally changes over and under the hood.

if you like to tinker and are prepared to have to change the EFI whenever I post a new one then great but if you don’t want to mess around and just want it to work and forget about it then for now stick with clover for now and done.

 

When OpenCore goes full release then il call OC the true king of bootloaders, that’s a good while away yet though. Maybe not even this year, who knows  

Edited April 29, 2020 by AudioGod

[Tiem]

Gotta say, this latest beta is actually pretty zippy. Pretty impressed actually!

[pkdesign]

On 4/28/2020 at 3:28 AM, WizeMan said:

Not that I think that Virtualbox would be a good candidate for a MacOS guest but are you saying that you got Virtualbox to work on your hackintosh? Windows throw BSOD when trying to install and Genymotion emulators do not boot! VMWare and Parallels working like a champ but I need Virtualbox for Genymotion and currently it is giving me the nerves!

Well, you sent me down quite the rabbit hole. BUT, I finally managed to get my original Virtualbox working with my Win10.

 

I keep getting a BSOD as well and couldn’t figure out what was wrong. I download VMWare and could not get that to work with my imported Vbox VM either. Hmm, must be my VM. I downloaded a pre-made VM with Win10 and it worked using Vbox and VMWare. WTF? So I matched the settings they had exactly and voila! My original VM in Virtualbox booted.

 

 

Maybe that will work for you as well.

 

But, now I'm not sure which I want to keep, Virtualbox or VMWare?

[Tiem]

6 hours ago, AlexeyNikitin said:

I just checked Windows disk with DiskUtility and it give me the next error:

This disk doesn’t contain an EFI system partition. If you want to start up your computer with this disk or include it in a RAID set, back up your data and partition this disk. : (-69767)
 

I run diskutil list and see that EFI partition present on Windows disk, but it is not on a first place(Windows Recovery partition on a first place): 

/dev/disk2 (internal, physical):

   #:                       TYPE NAME                    SIZE       IDENTIFIER

   0:      GUID_partition_scheme                        *512.1 GB   disk2

   1:           Windows Recovery                         554.7 MB   disk2s1

   2:                        EFI EFI                     104.9 MB   disk2s2

   3:         Microsoft Reserved                         16.8 MB    disk2s3

   4:       Microsoft Basic Data Windows     

 

May be this is a cause of the issue?

 

1. AdviseWindows
   Type: plist boolean
   Failsafe: false
   Description: Forces Windows support in FirmwareFeatures.

   Added bits to FirmwareFeatures:
   • FW_FEATURE_SUPPORTS_CSM_LEGACY_MODE (0x1) - Without this bit it is not possible to reboot to Windows

   installed on a drive with EFI partition being not the first partition on the disk.

   • FW_FEATURE_SUPPORTS_UEFI_WINDOWS_BOOT (0x20000000) - Without this bit it is not possible to reboot to Windows installed on a drive with EFI partition being the first partition on the disk.

[AudioGod]

1 hour ago, Tiem said:

 

1. AdviseWindows
   Type: plist boolean
   Failsafe: false
   Description: Forces Windows support in FirmwareFeatures.

   Added bits to FirmwareFeatures:
   • FW_FEATURE_SUPPORTS_CSM_LEGACY_MODE (0x1) - Without this bit it is not possible to reboot to Windows

   installed on a drive with EFI partition being not the first partition on the disk.

   • FW_FEATURE_SUPPORTS_UEFI_WINDOWS_BOOT (0x20000000) - Without this bit it is not possible to reboot to Windows installed on a drive with EFI partition being the first partition on the disk.

 

Erm Mr Tiem....Meowwwwwwww

 

@Tiem Nice thinking but unfortunately this is incorrect buddy

@AlexeyNikitin the correct method is 

 

PlatformInfo/Generic/AdviseWindows=Yes

 

The Problem is when he installed windows it didn't put the EFI partition as the first one so all you do is the above and then it no longer matters and you can change the start-up disk until your heart is content 

Edited April 29, 2020 by AudioGod

[AudioGod]

@Tiem Your still using the awesome smbios 7.1 right?

 

If so I want you togo into your config and change the boot arg agdpmod=pikera into agdpmod=ignore and tell me what you think. 

Only if your still using your NAVI GPU though. 

 

Enjoy Brother 

 

MEOWWWWWWWW

 

 

1 hour ago, pkdesign said:

Well, you sent me down quite the rabbit hole. BUT, I finally managed to get my original Virtualbox working with my Win10.

 

I keep getting a BSOD as well and couldn’t figure out what was wrong. I download VMWare and could not get that to work with my imported Vbox VM either. Hmm, must be my VM. I downloaded a pre-made VM with Win10 and it worked using Vbox and VMWare. WTF? So I matched the settings they had exactly and voila! My original VM in Virtualbox booted.

 

 

Maybe that will work for you as well.

 

But, now I'm not sure which I want to keep, Virtualbox or VMWare?

 

@pkdesign Well done buddy, I love it. Awesome Stuff. 

Edited April 29, 2020 by AudioGod

[Tiem]

6 hours ago, AudioGod said:

@Tiem Your still using the awesome smbios 7.1 right?

 

If so I want you togo into your config and change the boot arg agdpmod=pikera into agdpmod=ignore and tell me what you think. 

Only if your still using your NAVI GPU though. 

 

Enjoy Brother 

 

MEOWWWWWWWW

YUP. LOVE IT!

 

Wowa, wait how does this work now? What changed in macOS?

 

Also, do you get a duplicate Dock when you shutdown? Showed up in the betas of the last release.

[MorenoAv]

Hi @AudioGod,

Yesterday and today my hack gave me a fight, presenting me with the message in the picture bellow. I din't change nothing in the bios and the settings was good to install and run OpenCore, but changed overnight?

Thanks in Advance

[AudioGod]

30 minutes ago, MorenoAv said:

Hi @AudioGod,

Yesterday and today my hack gave me a fight, presenting me with the message in the picture bellow. I din't change nothing in the bios and the settings was good to install and run OpenCore, but changed overnight?

Thanks in Advance

 

Reflash your Bios I guess.

As you don't use my EFI folder and settings pure I couldnt tell you what's going no there. nobody has experienced anything like over on either of my threads.

very strange.

 

Make sure your Booter quirks are like so for the Z390 Pro (wifi)

 

Edited April 30, 2020 by AudioGod

[AudioGod]

5 hours ago, Tiem said:

YUP. LOVE IT!

 

Wowa, wait how does this work now? What changed in macOS?

 

Also, do you get a duplicate Dock when you shutdown? Showed up in the betas of the last release.

If you mean when the dock disappears and then slides back up then yes...lol

Im coming across too 7,1 myself today full time cos I’m loving it too buddy.

 

Il PM you my 0.5.8 7,1 in a little bit,  now with OpenCanopy fully engaged  

Edited April 30, 2020 by AudioGod

[MorenoAv]

Ok @AudioGod, thanks for your answer and I'll do that, but before I'm checking if my Booter quirks are equal to yours... 

Forgot to ask flashing the bios is possible in macOS or have to be done in windows?

Edited April 30, 2020 by MorenoAv

[AudioGod]

35 minutes ago, MorenoAv said:

Ok @AudioGod, thanks for your answer and I'll do that, but before I'm checking if my Booter quirks are equal to yours... 

Forgot to ask flashing the bios is possible in macOS or have to be done in windows?

Do it Direct in the bios using Q flash and make sure your using the latest firmware too.

good luck  

[MorenoAv]

Thanks 

[MorenoAv]

All done, it was my windows 10, causing all the fuss, first re flashed the bios and then re installed windows 10....

After that it was changing bios settings and boot macOS Catalina, and repair the boot, now my windows boot with OpenCore but is the first entry and is the one selected at boot an d I don't know how to change that... 

Thanks man @AudioGod, one more time...

[AudioGod]

12 minutes ago, MorenoAv said:

All done, it was my windows 10, causing all the fuss, first re flashed the bios and then re installed windows 10....

After that it was changing bios settings and boot macOS Catalina, and repair the boot, now my windows boot with OpenCore but is the first entry and is the one selected at boot an d I don't know how to change that... 

Thanks man @AudioGod, one more time...

Awesome.
As long as your happy then I’m happy.

Anytime buddy 

 

@MorenoAv make sure you have PlatformInfo/Generic/AdviseWindows=Yes set in the config too.

 

Sorry if you meant making macOS the default drive and your not using OpenCanopy then select the drive you want to default too at the bootpicker and press control and enter.

If you are using OpenCanopy then you have to do it from within Catalina in preferences, startup disk.  

Edited April 30, 2020 by AudioGod

[MorenoAv]

Yep very happy dancing and jumping all around... lool

[n19htz]

what is the best way to install windows 10 on separate SATA SSD on hackintosh running OC 0.5.7 Catalina 10.15.4 the way it could be natively swapped with Startup Disk utility?

[AudioGod]

13 minutes ago, n19htz said:

what is the best way to install windows 10 on separate SATA SSD on hackintosh running OC 0.5.7 Catalina 10.15.4 the way it could be natively swapped with Startup Disk utility?

Remove the Catalina drive and boot windows like normal and then once it’s all done put your cat drive back and away you go.

This is the most fool proof way and avoids any problems that could arise.

 

Edited April 30, 2020 by AudioGod

[Tiem]

7 hours ago, AudioGod said:

If you mean when the dock disappears and then slides back up then yes...lol

Im coming across too 7,1 myself today full time cos I’m loving it too buddy.

 

Il PM you my 0.5.8 7,1 in a little bit,  now with OpenCanopy fully engaged  

I always try and keep up to date on OC (and any kext really). OpenCanopy has come a LONG way. They just added in working timeouts so there is very little NDK brings these days. Updating macOS still feels flakey compared to Clover but the rest is just amazing. I honestly can't believe the devs have come so far in less than 6 months. I mean where was OC 6 months ago? Basically just starting out and now look at it. Unbelievable

[panosru]

Today I noticed that when I powerup my computer, while on Aorus logo, just before Apple's logo appears I'm getting on the top left of the screen in red colour the following messages:

 

Error: Already started returned from OpenRuntime.efi
Error: Already started returned from AptioMemoryFix.efi

Although it does not affect the boot of the general workflow of the computer, I wonder if anyone else has those messages and if they are something I should worry about.

 

Thanks!

[AudioGod]

19 minutes ago, panosru said:

Today I noticed that when I powerup my computer, while on Aorus logo, just before Apple's logo appears I'm getting on the top left of the screen in red colour the following messages:

 

Error: Already started returned from OpenRuntime.efi
Error: Already started returned from AptioMemoryFix.efi

Although it does not affect the boot of the general workflow of the computer, I wonder if anyone else has those messages and if they are something I should worry about.

 

Thanks!

Hello mate, long time no see on here.

 

What you doing with Aptiomemoryfix and OpenRuntime?

Wtf is going on there, what Efi are you using?

that can’t be one of mine or you have done some funky stuff to it.

 
clover or OpenCore?

 

has somebody else been giving you duff advise cos sure looks like it me....oh dear 

Edited April 30, 2020 by AudioGod

[panosru]

hmm, strange, I redownloaded your latest EFI and indeed you don't have those files in your EFI... Could it be possible that they ended up there after I updated to latest clover version?

 

Actually I also have FSInject.efi and FwRuntimeServices.efi in addition to AptioMemoryFix.efi and the files you have in your EFI folder... 

 

Everything else seems to be fine.

 

I assume that it is safe for me to remove unnecessary files from UEFI folder then.