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

[MaLd0n]

1 hour ago, nikosvr said:

Hi, is there a way to enable hardware encoding on RX 580?

use iMacPro1,1 or MacPro7,1

in Catalina u can use shikigva=128 or 144 with iMac19,1/2 smbios

[smintel]

On 6/7/2020 at 12:32 AM, dsynos80 said:

Yes, this is the sleep solution. Use 12c for ProWifi and load  the unlocked f12c msr unlock profile from 1st post.

Thanks - I've now updated BIOS to 12C, loaded the msg unlock profiled, updated EFI contents and clicked on the 'fix sleep image' button in hackintool. Relieved that updates have all gone fine, but frustrated that my sleep issue is still not fixed.  Any other thoughts on cause or fix? I saw that some CPU coolers cause issue but the one mentioned isn't the one I have - I have Corsair Hydro H60 - could it be related to that?

[dsynos80]

Maybe, i read before in this thread about aio coolers interfering with sleep.

I have a Kraken x62 plugged in and hve no issues though.

AG mentioned that somewhere.

[WizeMan]

16 hours ago, smintel said:

Thanks - I've now updated BIOS to 12C, loaded the msg unlock profiled, updated EFI contents and clicked on the 'fix sleep image' button in hackintool. Relieved that updates have all gone fine, but frustrated that my sleep issue is still not fixed.  Any other thoughts on cause or fix? I saw that some CPU coolers cause issue but the one mentioned isn't the one I have - I have Corsair Hydro H60 - could it be related to that?

 

15 hours ago, dsynos80 said:

Maybe, i read before in this thread about aio coolers interfering with sleep.

I have a Kraken x62 plugged in and hve no issues though.

AG mentioned that somewhere.

 

Another reason for sleep not working properly is having XMP profile enabled. I had to set my Memory Clock from 3200Mhz to 2666Mhz in order to fix sleep.

[AudioGod]

Patches and fixes for lack of sleep or instant wake.

https://dortania.github.io/USB-Map-Guide/misc/instant-wake.html

[Praetorianus]

49 minutes ago, AudioGod said:

Patches and fixes for lack of sleep or instant wake.

https://dortania.github.io/USB-Map-Guide/misc/instant-wake.html

Dear AudioGod,

 

will this fix the instant wake up caused by Corsair AIO?

[AudioGod]

19 minutes ago, Praetorianus said:

Dear AudioGod,

 

will this fix the instant wake up caused by Corsair AIO?

Yes it will (gprw.ssdt)

[Crispymac]

Update: I fixed the windows install and the system runs now smooth as hell. -> No more Hardware issue at all !!

But I still need some help.
I redid every single step of the instructions: first I forgot to change the config.plist and the same bug as before with a "crash/restart" at 3:37 of the install video happened and after rebooting and doing the next step the error log appeared after a while.

 

With the step of a changed MLB and UUID and Serial number: I can't run the Install USB anymore I receive a big fat white block sign when booting from the USB, but that seems to be random, after a couple reboots it works again and crashes again at the same step.

I used the f12c bios -> your profile and double checked everything with your screenshot - I use your Opencore EFI for iMacPro1.1.

What concerns me that my UEFI boot menu is kind of spammed and under the Boot sequence in EASY MODE in the BIOS I have  1x "Mac OS X" and 1x "Windows Boot Manager".
The first MAC OS X is there already since one of my first overall install attempts, the second windows boot manager is since my successful windows install and the third one just appeared after I unplugged ALL Disks even the single one connected prepared for install because I was surprised by FOUR empty entries in the F12 Boot menu. The install trial and windows install was allways with only one single drive connected, but I read those are in UEFI stored somewhere on the board.

Should I clean those entries in the first step(preferable without the need of a windows reinstall) or is the issue something else ?
Because I bet the issue can only come now from leftover {censored} or whatsoever.

Edited June 9, 2020 by Crispymac

[Tiem]

7 hours ago, Crispymac said:

Update: I fixed the windows install and the system runs now smooth as hell. -> No more Hardware issue at all !!

But I still need some help.
I redid every single step of the instructions: first I forgot to change the config.plist and the same bug as before with a "crash/restart" at 3:37 of the install video happened and after rebooting and doing the next step the error log appeared after a while.

 

With the step of a changed MLB and UUID and Serial number: I can't run the Install USB anymore I receive a big fat white block sign when booting from the USB, but that seems to be random, after a couple reboots it works again and crashes again at the same step.

What concerns me that my UEFI boot menu is kind of spammed and under the Boot sequence in EASY MODE in the BIOS I have  1x "Mac OS X" and 1x "Windows Boot Manager".

Underlined: KASLR, or rather macOS cannot allocate a free space in memory. These have been entirely fixed with this board and EFI. If you are seeing those using OC or Quirks/Clover then you probably have a really fubared CMOS. Pull the battery and clear it. That's why it seems random to you. Because sometimes it will acquire space to load macOS and other times it won't.

 

Italic. It doesn't really matter. UEFI entries do nothing with the functioning of your system. Clear them out if you like but OC and Windows both do things and you learn to stop fighting with it. The bulletproof way to set up OC is to use the bootstrap.efi. That way you can clear out every entry if you like and never lose access to your bootloader.

[smintel]

5 hours ago, AudioGod said:

Yes it will (gprw.ssdt)

Thanks - would like to try this but don't fully understand how to apply the patches - they appear to be for OpenCore - do they work with Clover too? Where do I put the files exactly? I guess the .aml files goes in ACPI/patched with the other .aml files - but what do I do with the .plist file? Thanks in advance. 

[Crispymac]

 

 

 

1

2 hours ago, Tiem said:

Underlined: KASLR, or rather macOS cannot allocate a free space in memory. These have been entirely fixed with this board and EFI. If you are seeing those using OC or Quirks/Clover then you probably have a really fubared CMOS. Pull the battery and clear it. That's why it seems random to you. Because sometimes it will acquire space to load macOS and other times it won't.

 

Italic. It doesn't really matter. UEFI entries do nothing with the functioning of your system. Clear them out if you like but OC and Windows both do things and you learn to stop fighting with it. The bulletproof way to set up OC is to use the bootstrap.efi. That way you can clear out every entry if you like and never lose access to your bootloader.

Okay, I tried the CMOS reset, and nothing can be fubared anymore, the second issue gets postponed until I have any working build, unless someone here thinks its necessary.
But I still receive those fat "prohibitory" signs almost all the time, I constantly change something (tying clover instead of OC using the iMac1,1 instead of the 19,1. Or i change some bios settings. until I reset again to the basic profile, but I am honestly unsure which settings are the right one, because the discussion forums 1st page list differs from the screenshot partly and the MSR unlock profile also does not cover all setting.

I am super confused because I can not find where the issue is because there needs to be some minor mistake I just oversee... nothing else can be the reason, but I am sure we can find that in the long run
And whatever I change seems to make it worse

[freakermonguer]

OpenCore. Installed Update 10.15.5 . Everything works.

 

Steps: 

 

Install an reboot.

On Reboot Choose "MacOsx Installation" drive - or similar name.

 

It might reboot a couple of times. On the first run it stalled. But I pressed a key and rebooted (might be not related). Then rebooted same drive and ended installation.

 

 

Edited June 9, 2020 by freakermonguer
version

[Tiem]

@Crispymac

 

https://dortania.github.io/OpenCore-Desktop-Guide/extras/kaslr-fix.html

 

First off, add -v to your boot arguments. Having a Ø in your face is meaningless. With the verbose flag you'll likely see the following error:

 

Error allocating 0x1197b pages at 0x0000000017a80000 alloc type 2
Couldn't allocate runtime area

Only 244/256 slide values are usable!

Or some variation of that. That is your CMOS being too cluttered to allocated a slide with enough space. KASLR is finicky. This was an issue 6 months ago. You could go 100 reboots just fine and then one day, it just won't work no matter how many times you try. This is where the slide=0 value, AptioMemoryFix, Quirks, and even lots of code within OC all originated from.

 

If you still see problems after pulling the battery on the board, try refreshing the firmware. That will always reset the memory and the settings. Believe it or not but boards have bugs and bugs affecting your hardware directly can be a massive headache.

 

As I said tho, this used to be an issue. With real NVRAM, proper ACPI mapping, today, on this hardware and EFI, you should not have this issue.

[aslocombe]

I have been at this install for about 4 days now with 0 success.  The hardware is as follows:

 

Intel® Core™ i9-9900K 3.60GHz
GIGABYTE Z390 AORUS PRO WIFI
4 X 16GB  DDR4-2666
Seagate 1TB 2.5in SATA3 BarraCuda SSD
Onboard Graphics for now (I have a AMD Radeon® RX 580 8GB on its way in a week.)

 

I have tried the full guide to the letter at:
https://dortania.github.io/OpenCore-Desktop-Guide/config.plist/coffee-lake.html

 

I cam across this post which is specific the the board I am using and though it would help, but I still cant get past the error.

 

It always fails at this point:
[EB|#LOG:EXITBS:START] 2020-06-10T05:13:19

 

Which according to the guide is any of the following at :
https://dortania.github.io/OpenCore-Desktop-Guide/troubleshooting/troubleshooting.html#stuck-on-eblogexitbsstart

 

ProvideConsoleGop is likely missing as this is needed for transitioning to the next screen, this was originally part of AptioMemoryFix but is now within OpenCore as this quirk. Can be found under UEFI -> Output

 

Missing kernel patches(only applies for AMD CPUs, make sure they're OpenCore patches and not Clover. Clover uses MatchOS while OpenCore has MinKernel and Maxkernel)

IgnoreInvalidFlexRatio missing, this is needed for Broadwell and older. Not for AMD and Skylake or newer

 

AppleXcpmExtraMsrs may be required, this is generally meant for Pentiums, HEDT and other odd systems not natively supported in macOS. Do not use on AMD

 

SetupVirtualMap may be needed depending on the firmware, generally this quirk should be avoided but most Gigabyte users and older hardware(Broadwell and older) will need this quirk to boot.

 

RebuildAppleMemoryMap may not be a fan of your firmware, disabling this quirk isn't recommended but may be required on some laptops and certain desktops

 

Another possible problem is that some users either forget or cannot disable CFG-Lock in the BIOS(specifically relating to a locked 0xE2 MSR bit for power management, obviously much safer to turn off CFG-Lock). Do note this is for Intel users only, not AMD. When this happens, there's a couple of possible fixes:

 

Fixing CFG Lock
Enable AppleXcpmCfgLock and AppleCpuPmCfgLock, this disables PKG_CST_CNFIG_CONTROL within the XNU and AppleIntelCPUPowerManagement respectively. Not recommended long term solution as this can cause instability.

 

The MSR is talked about in this thread and I have followed those instructions.  

 

I updated the BIOS to F12C
I applied the F12c Unlock Profile
I saved the Profile and use it.

I have all the settings in the BIOS set as per the original post in this thread.

 

Below are other things I have tried:

I have removed all other drives.

I have reduced the Memory to one stick of 16B.

I have tried with and without the Real MAC Address in the SMBIOS.

I have tried creating the boot media on a Macbook and also on Windows.

I have tried DSDT with SSDTTime

I have tried clover and it fails as well.

 

Please see the attached log from the opencore boot.  It's the log from OpenCore built with Windows following their guide.

 

I wasn't able to get the log from the boot using this threads files, but it errors in the exact same spot.

I have also attached a photo of the screen where it always fails.

 

I have built many Hackingtoshes before, but I have never been stuck on one build this long.  Any help would be greatly appreciated.
 

 

opencore-2020-06-10-051301.txt

[freakermonguer]

I have a problem on the booting sequence with OpenCanopy

 

When the OpenCanopy screen is shown with the drives to choose I see all the EFI partitions in my drives. I have a lot of drives and they have EFI partitions. I see them all. Is there a way to hide this drives and only show the drives with OSx installed?

 

 

[texem]

ScanPolicy is your friend, read the doc's ..

 

btw: better you have only one EFI partition in your system and always boot from there.

 

[freakermonguer]

3 hours ago, texem said:

ScanPolicy is your friend, read the doc's ..

 

btw: better you have only one EFI partition in your system and always boot from there.

 

I boot only from one EFI partition, but I have another EFI partition as backup. They don't interfere with each other. And they give me no trouble. Also there are other drives I want to hide.

 

Scan Policy as I read in OpenCore Manual is not for this, it's for defining which device types to scan for OS. I just want to hide partitions and tell openCore not to show them

 

[Tiem]

20 hours ago, texem said:

btw: better you have only one EFI partition in your system and always boot from there.

Each OS should have it's own EFI folder unless you're installing them on a single HD.

 

There is no scenario where you would want to install Windows on Drive 0 and macOS on Drive 1 and then use a single EFI to load them both. OC is good about hiding any partition that is not bootable. TM backups are a good example of that. They create an EFI but do not use partition. OC will hide those if you hide auxiliary set.

[jimborae]

15 hours ago, Tiem said:

Each OS should have it's own EFI folder unless you're installing them on a single HD.

 

There is no scenario where you would want to install Windows on Drive 0 and macOS on Drive 1 and then use a single EFI to load them both. OC is good about hiding any partition that is not bootable. TM backups are a good example of that. They create an EFI but do not use partition. OC will hide those if you hide auxiliary set.

 

Yes there is scenario, and it's one I dont want to be in but appears to be the only way to it.  I came across it last night. 

 

So it appears that the Z390 Pro does not support support booting from a PCIE Slot based NVME SSD or at least mine doesn't. I have an Intel 750 PCIE NVME SSD in the bottom PCIE X4 slot, the bios refuses to see it and cant boot from it. This is my new OC Mac OS drive, I have Windows in the top M2A PCIE NVME slot. 

 

If I boot OpenCore from USB it sees the the Intel drive and allows me to boot from it, so if I moved the OC EFI folder to the Windows drive I should then be able to boot from which ever hard drive I want to. Not tried it yet but......it's a scenario and as I said not an ideal one. I'd much rather be able to get the bios recognise the Intel PCIE SSD in the 4x slot but wierdly it would seem it doesn't support this. 

   

Edited June 12, 2020 by jimborae

[WizeMan]

6 hours ago, jimborae said:

 

Yes there is scenario, and it's one I dont want to be in but appears to be the only way to it.  I came across it last night. 

 

So it appears that the Z390 Pro does not support support booting from a PCIE Slot based NVME SSD or at least mine doesn't. I have an Intel 750 PCIE NVME SSD in the bottom PCIE X4 slot, the bios refuses to see it and cant boot from it. This is my new OC Mac OS drive, I have Windows in the top M2A PCIE NVME slot. 

 

If I boot OpenCore from USB it sees the the Intel drive and allows me to boot from it, so if I moved the OC EFI folder to the Windows drive I should then be able to boot from which ever hard drive I want to. Not tried it yet but......it's a scenario and as I said not an ideal one. I'd much rather be able to get the bios recognise the Intel PCIE SSD in the 4x slot but wierdly it would seem it doesn't support this. 

   

 

Or instead of messing up with your Windows EFI partition, you could drop your EFI into a very small footprint usb stick and boot from it.

[Tiem]

8 hours ago, jimborae said:

 

Yes there is scenario, and it's one I dont want to be in but appears to be the only way to it.  I came across it last night. 

 

So it appears that the Z390 Pro does not support support booting from a PCIE Slot based NVME SSD or at least mine doesn't. I have an Intel 750 PCIE NVME SSD in the bottom PCIE X4 slot, the bios refuses to see it and cant boot from it. This is my new OC Mac OS drive, I have Windows in the top M2A PCIE NVME slot. 

 

If I boot OpenCore from USB it sees the the Intel drive and allows me to boot from it, so if I moved the OC EFI folder to the Windows drive I should then be able to boot from which ever hard drive I want to. Not tried it yet but......it's a scenario and as I said not an ideal one. I'd much rather be able to get the bios recognise the Intel PCIE SSD in the 4x slot but wierdly it would seem it doesn't support this. 

   

Really don't get why you're arguing with everyone. Your knowledge is pretty poor. You confuse bootloaders with BIOSes. And you claim this board doesn't support booting from PCIe SSDs when in fact it works just fine off a USB. Also Windows has no issues with any drive, PCIe, SATA, M.2.. any drive. So clearly it's not the board is it. If it works in Windows it's not the board. It's your EFI. Which you FUBARed despite AG making it pretty childlike to install.

 

Go for it man. You got this. 

Edited June 12, 2020 by Tiem
typo

[pkdesign]

@jimborae Ignore his rudeness. He's a bit of an a*hole.

 

I have exactly the same board and honestly, you really need to wipe everything clear and just use @AudioGod EFI (whether Clover or OpenCore) as is except for adding your serial number, etc. It's like two lines. Unlocking your MSR is dead simple and has been covered a hundred times on this board.

 

I can boot from NVMe, and Windows I have installed on a separate SSD. I can do this using Clover or F12 at boot. I can even switch back and forth from Clover to OC (installed on a USB, although I wouldn't recommend doing that regularly).

 

AudioGod has made creating a hack using an AORUS board (several versions) the simplest thing i have ever experienced in my 10+ years of hacking.

 

EDIT:

Oh sorry, I thought you had the WiFi version.

Edited June 12, 2020 by pkdesign

[jimborae]

50 minutes ago, Tiem said:

Really don't get why you're arguing with everyone. Your knowledge is pretty poor. You confuse bootloaders with BIOSes. And you claim this board doesn't support booting from PCIe SSDs when in fact it works just fine off a USB. Also Windows has no issues with any drive, PCIe, SATA, M.2.. any drive. So clearly it's not the board is it. If it works in Windows it's not the board. It's your EFI. Which you FUBARed despite AG making it pretty childlike to install.

 

Go for it man. You got this. 

 

WTF! Are you sure you've not got me mixed up with someone else cos I'm confused as to where your agression is coming from. I'm not argueing with you or anyone else I'm mearly pointing out that I seem to have a fairly niche use case when using an Intel 750 pcie SSD because my board can not detect it in the bios.

 

Is my knowledge poor??? Probably but I'm still learning but I know enough to get by and when to look for help. But I didn't make any claims about my knowledge either though, and no I'm not confusing bioses with bootloaders. 

 

Also my EFI is fine thank you very much, it isn't fubared in any way shape of form, unless you'd care to explain to the contrary in a civilised tone.    

Edited June 12, 2020 by jimborae

[pkdesign]

@jimborae Read my above comment. He has been a thorn in the side of everyone on this board at some point. And a horse's ass (or arse for my brit friends.)

Edited June 12, 2020 by pkdesign

[jimborae]

5 minutes ago, pkdesign said:

@jimborae Ignore his rudeness. He's a bit of an a*hole.

 

I have exactly the same board and honestly, you really need to wipe everything clear and just use @AudioGod EFI (whether Clover or OpenCore) as is except for adding your serial number, etc. It's like two lines. Unlocking your MSR is dead simple and has been covered a hundred times on this board.

 

I can boot from NVMe, and Windows I have installed on a separate SSD. I can do this using Clover or F12 at boot. I can even switch back and forth from Clover to OC (installed on a USB, although I wouldn't recommend doing that regularly).

 

AudioGod has made creating a hack using an AORUS board (several versions) the simplest thing i have ever experienced in my 10+ years of hacking.

 

 

Thanks PK for the kind & understanding words.

 

Just to be clear I'm not talking about a PCIE M.2 NVMe SSD, my normal mac install is on the M.2 PCIe SSD in my sig and that is detected works fine when installed. The issue is board bios I think unless someone can tell me what I'm missing. 

 

Also to clear up any confusion I'm using AG's excellent OC EFI with only my serials etc changed and when the normal hackintosh SSD is installed, can do all the things that you can do.  

 

It's wierd because on my Ryzentosh build, using an X570 Aorus Pro, this Intel drive is detected in the bios with no issues and I can select it as a boot drive with no issues.   

 

The only thing I can think of is that I may not have cloned the old hackintosh SSD correctly when using Carbon Copy Cloner. But I checked the EFI partition and put my working EFI folder in there. 

 

Anyways I'll have more of a play with it tonight.    

20 minutes ago, pkdesign said:

@jimborae Read my above comment. He has been a thorn in the side of everyone on this board at some point. And a horse's ass (or arse for my brit friends.)

 

Horse's arse, if you please........I'm one of those Brit friends