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

[AudioGod]

Yeah that all looks right and it will restart a few times and go back to the clover screen that’s all normal and then continue.

forget OpenCore for now until you have it installed using clover, my advise it let it do its thing. It will restart and select the correct drive on its own and then continue until it’s done.

Edited February 16, 2020 by AudioGod

[texasdude11]

2 minutes ago, AudioGod said:

Yeah that all looks right and it will restart a few times and go back to the clover screen that’s all normal and then continue.

forget OpenCore for now until you have it installed using clover, my advise it let it do its thing. It will restart and select the correct drive on its own and then continue until it’s done.

 

I let it do its thing but it keeps on saying that 

 

"System was automatically rebooted due to a panic".

 

[AudioGod]

1 minute ago, texasdude11 said:

 

I let it do its thing but it keeps on saying that 

 

"System was automatically rebooted due to a panic".

 

check your hardware bud, somehings not right if that’s happening.

Edited February 16, 2020 by AudioGod

[texasdude11]

Just now, AudioGod said:

check your hardware bud, somehings not right if that’s happening.

 

OK, let me try again. I know all is plugged in correctly because Windows and Ubuntu are working just fine. I took out that m.2 where I was dual booting into Windows and Ubuntu so that there is no conflict and replaced it with a new m.2 for mac os.

[AudioGod]

Just now, texasdude11 said:

 

OK, let me try again. I know all is plugged in correctly because Windows and Ubuntu are working just fine. I took out that m.2 where I was dual booting into Windows and Ubuntu so that there is no conflict and replaced it with a new m.2 for mac os.

perfect and for the hell of it use the top m.2 slot above the gpu as it’s home.

[texasdude11]

1 minute ago, AudioGod said:

perfect and for the hell of it use the top m.2 slot above the gpu as it’s home.

 

OK, i had it plugged into the middle m.2 , but I will switch to top as well, right now, i just switched to opencore just because it was faster. Once Opencore fails (lol i am assuming it will with my luck) then I will switch to top m.2 slot.

2 minutes ago, texasdude11 said:

 

OK, i had it plugged into the middle m.2 , but I will switch to top as well, right now, i just switched to opencore just because it was faster. Once Opencore fails (lol i am assuming it will with my luck) then I will switch to top m.2 slot.

Yeah, opencore failed as well. 

 

There is a clover->acpi->patched folder. Shall I remove those patches? Not sure if any custom patches/ configs is causing problems?

[AudioGod]

7 hours ago, texasdude11 said:

 

OK, i had it plugged into the middle m.2 , but I will switch to top as well, right now, i just switched to opencore just because it was faster. Once Opencore fails (lol i am assuming it will with my luck) then I will switch to top m.2 slot.

Yeah, opencore failed as well. 

 

There is a clover->acpi->patched folder. Shall I remove those patches? Not sure if any custom patches/ configs is causing problems?

 

The dsdt in the patched folder for clover is absolutely vital for clover but has nothing to do with OC, OC uses SSDTs (3 of them) and these are also vital for OC.
ive never seen somebody not able to install like this, you must be doing something wrong somewhere along the line buddy. 

im convinced your doing something wrong bud so can I suggest you start again and use a simple guide to do it with cos this shouldn’t be happening to you and I’m confused at this point.

 

Hundreds upon hundreds of people Have downloaded my EFIs since I started releasing them and your the first person that can’t get a install going so that’s why I’m looking to you or your setup for the cause. I’m sure you know what your doing bud but that’s still the one and only explanation that makes sense to me. That or your have a faulty bit of hardware somewhere along the line that you haven’t discovered as faulty yet.

 

Edited February 16, 2020 by AudioGod

[AudioGod]

@texasdude11 Send me your finished EFI that you would use to instal with and leave your info on it so I can see what’s going on if anything. 
PM it to me if your worried about other people seeing your info.

 

Edited February 16, 2020 by AudioGod

[texasdude11]

9 hours ago, AudioGod said:

@texasdude11 Send me your finished EFI that you would use to instal with and leave your info on it so I can see what’s going on if anything. 
PM it to me if your worried about other people seeing your info.

 

 

Hey @AudioGod 

 

I think it could be my M.2 drive. I just can't install on it. Luckily I had a spare SSD that I used to install. I plugged in efi from this guide and followed this one (which made me use intel inbuilt graphics to start with and then change config to plug in the the discreet graphics).

 

https://github.com/shiruken/hackintosh/blob/master/README.md

 

I plugged in the m.2 (that I think is buggy but it may not be?) and another m.2 which had my Windows and Ubuntu installation after I installed Catalina tho. I have setup the boot drive as SSD and it shows all my Windows and Linux and MacOS.

 

I booted into Ubuntu, formatted the m.2 drive as just a storage drive and I was hoping that I'm all set. If I stay in Ubuntu or Windows the system is super stable. However when I boot back into Mac it randomly freezes after 5-10 minutes of using it and then I have to force restart it by turning off power. It works again just fine for 5-10 minutes and then the screen freezes, and I can't move my mouse and then force restart again.

 

I wish there was a way to find out what was causing the freezes. Like some kind of logs somewhere. 

 

 

[texasdude11]

So when I rebooted the MacOs after "panic" this it asked me if I wanted to send the error report to Apple. I took a look at the report and this is what it said. I think my suspicion with the NVME drive may be right, there is an issue with "IONVMeController.cpp" which looks like somethign to do with the NVMe drive. I will take the NVME drive out and see if things work fine.

 

panic(cpu 0 caller 0xffffff7f83a604a7): nvme: "Fatal error occurred. CSTS=0x1 US[1]=0x0 US[0]=0x23 VID=0x144d DID=0xa808
. FW Revision=1B2QEXM7\n"@/BuildRoot/Library/Caches/com.apple.xbs/Sources/IONVMeFamily/IONVMeFamily-470.80.1/IONVMeController.cpp:5258
Backtrace (CPU 0), Frame : Return Address
0xffffff873800b9e0 : 0xffffff800113bb2b 
0xffffff873800ba30 : 0xffffff80012734d5 
0xffffff873800ba70 : 0xffffff8001264f4e 
0xffffff873800bac0 : 0xffffff80010e2a40 
0xffffff873800bae0 : 0xffffff800113b217 
0xffffff873800bbe0 : 0xffffff800113b5fb 
0xffffff873800bc30 : 0xffffff80018d2aa9 
0xffffff873800bca0 : 0xffffff7f83a604a7 
0xffffff873800bcc0 : 0xffffff7f83a4b47a 
0xffffff873800be20 : 0xffffff8001845e59 
0xffffff873800be90 : 0xffffff8001845d79 
0xffffff873800bec0 : 0xffffff800117d7e5 
0xffffff873800bf40 : 0xffffff800117d311 
0xffffff873800bfa0 : 0xffffff80010e213e 
      Kernel Extensions in backtrace:
         com.apple.iokit.IONVMeFamily(2.1)[6BD739D2-AAF2-36CA-AB08-1B84F0E860C2]@0xffffff7f83a3d000->0xffffff7f83a7ffff
            dependency: com.apple.driver.AppleMobileFileIntegrity(1.0.5)[A243D030-19AC-30AA-AC70-6C786DF9E6CE]@0xffffff7f82222000
            dependency: com.apple.iokit.IOPCIFamily(2.9)[ADD485B5-3EF8-37C4-B3C5-F86326E497A4]@0xffffff7f81b10000
            dependency: com.apple.driver.AppleEFINVRAM(2.1)[D1753114-1FE3-3849-A7FA-452EDAB62495]@0xffffff7f839dc000
            dependency: com.apple.iokit.IOStorageFamily(2.1)[76CF8513-C8B7-3A6F-9717-6D3F65B298BB]@0xffffff7f81e7a000
            dependency: com.apple.iokit.IOReportFamily(47)[988360A2-2E10-3014-A119-BE81BC045A10]@0xffffff7f81a49000

BSD process name corresponding to current thread: kernel_task
Boot args: dart=0 darkwake=8 agdpmod=pikera shikigva=80 -v root-dmg=file:///Install%20macOS%20Catalina.app/Contents/SharedSupport/BaseSystem.dmg

Mac OS version:
19D76

Kernel version:
Darwin Kernel Version 19.3.0: Thu Jan  9 20:58:23 PST 2020; root:xnu-6153.81.5~1/RELEASE_X86_64
Kernel UUID: A8DDE75C-CD97-3C37-B35D-1070CC50D2CE
Kernel slide:     0x0000000000e00000
Kernel text base: 0xffffff8001000000
__HIB  text base: 0xffffff8000f00000
System model name: iMac19,1 (XXXX--blanked--XXXX)
System shutdown begun: NO
Panic diags file unavailable, panic occurred prior to initialization

System uptime in nanoseconds: 69350937897
last loaded kext at 43331993867: @nke.webcontentfilter	5 (addr 0xffffff7f85b39000, size 24576)
loaded kexts:

 

PS: The weird part is that the m.2 drive works jsut fine in windows and linux, its only causing problems in macOS. I will remove the drive and use MacOS for sometime to see if it freezes.

 

I removed the M.2 drive and booted into the MacOS and I still get "Your Mac restarted after an error" like message, and the logs said this:

 

panic(cpu 0 caller 0xffffff7f83a604a7): nvme: "Fatal error occurred. CSTS=0x1 US[1]=0x0 US[0]=0x23 VID=0x144d DID=0xa808
. FW Revision=1B2QEXM7\n"@/BuildRoot/Library/Caches/com.apple.xbs/Sources/IONVMeFamily/IONVMeFamily-470.80.1/IONVMeController.cpp:5258
Backtrace (CPU 0), Frame : Return Address
0xffffff873800b9e0 : 0xffffff800113bb2b 
0xffffff873800ba30 : 0xffffff80012734d5 
0xffffff873800ba70 : 0xffffff8001264f4e 
0xffffff873800bac0 : 0xffffff80010e2a40 
0xffffff873800bae0 : 0xffffff800113b217 
0xffffff873800bbe0 : 0xffffff800113b5fb 
0xffffff873800bc30 : 0xffffff80018d2aa9 
0xffffff873800bca0 : 0xffffff7f83a604a7 
0xffffff873800bcc0 : 0xffffff7f83a4b47a 
0xffffff873800be20 : 0xffffff8001845e59 
0xffffff873800be90 : 0xffffff8001845d79 
0xffffff873800bec0 : 0xffffff800117d7e5 
0xffffff873800bf40 : 0xffffff800117d311 
0xffffff873800bfa0 : 0xffffff80010e213e 
      Kernel Extensions in backtrace:
         com.apple.iokit.IONVMeFamily(2.1)[6BD739D2-AAF2-36CA-AB08-1B84F0E860C2]@0xffffff7f83a3d000->0xffffff7f83a7ffff
            dependency: com.apple.driver.AppleMobileFileIntegrity(1.0.5)[A243D030-19AC-30AA-AC70-6C786DF9E6CE]@0xffffff7f82222000
            dependency: com.apple.iokit.IOPCIFamily(2.9)[ADD485B5-3EF8-37C4-B3C5-F86326E497A4]@0xffffff7f81b10000
            dependency: com.apple.driver.AppleEFINVRAM(2.1)[D1753114-1FE3-3849-A7FA-452EDAB62495]@0xffffff7f839dc000
            dependency: com.apple.iokit.IOStorageFamily(2.1)[76CF8513-C8B7-3A6F-9717-6D3F65B298BB]@0xffffff7f81e7a000
            dependency: com.apple.iokit.IOReportFamily(47)[988360A2-2E10-3014-A119-BE81BC045A10]@0xffffff7f81a49000

BSD process name corresponding to current thread: kernel_task
Boot args: dart=0 darkwake=8 agdpmod=pikera shikigva=80 -v root-dmg=file:///Install%20macOS%20Catalina.app/Contents/SharedSupport/BaseSystem.dmg

Mac OS version:
19D76

Kernel version:
Darwin Kernel Version 19.3.0: Thu Jan  9 20:58:23 PST 2020; root:xnu-6153.81.5~1/RELEASE_X86_64
Kernel UUID: A8DDE75C-CD97-3C37-B35D-1070CC50D2CE
Kernel slide:     0x0000000000e00000
Kernel text base: 0xffffff8001000000
__HIB  text base: 0xffffff8000f00000
System model name: iMac19,1 (XXX-RemovedXXX)
System shutdown begun: NO
Panic diags file unavailable, panic occurred prior to initialization

System uptime in nanoseconds: 69350937897
last loaded kext at 43331993867: @nke.webcontentfilter	5 (addr 0xffffff7f85b39000, size 24576)
loaded kexts:

 

Just gonna keep the mac up and running and will see if it freezes or not. At the moment, the EFI that I have is from the github post at the moment. If it still freezes then I will swap it out with your efi. 

Edited February 16, 2020 by texasdude11

[texasdude11]

About 2 hours in, ran several benchmark tools for 10 minutes straight, compiled java application that took 3 minutes, installed and played fortnite (fr the first time in my life just to check if it will break anything). uninstalled fortnite. Looking solid up until now.

 

The efi that I am using (from the github link i posted on top) has no dsdt or patches folder. Please take a look at it.

 

What advantage do I get by using dsdt?

 

Thank you!

[AudioGod]

11 hours ago, texasdude11 said:

About 2 hours in, ran several benchmark tools for 10 minutes straight, compiled java application that took 3 minutes, installed and played fortnite (fr the first time in my life just to check if it will break anything). uninstalled fortnite. Looking solid up until now.

 

The efi that I am using (from the github link i posted on top) has no dsdt or patches folder. Please take a look at it.

 

What advantage do I get by using dsdt?

 

Thank you!

there’s many advantages to using a dsdt yes but I’m fascinated to know what’s going on with your build as the Oc EFI doesn’t use a DSDT so it sure isn’t that that’s the problem. It’s more like something about your setup isn’t lining up with mine to the extent that my EFI isn’t working for you,

what make and models are your m.2 drives?

as for the github EFI your using, I've seen that a few times before and it’s not that different to how I do things (more like how I used to do things before using a dsdt) so I’m surprised that works and mine doesn’t...hmmmmmm interesting.

would love to see what your doing to my EFI so I can get a reading if there’s an error going down in your info entries or Something like that as I take a view where if many work and one doesn’t then you have to look to the one that doesn’t before being able to move forward with a fix.

if you can PM me my EFI with your changes to it done then I might be able to work out what’s going on bud?

 

Update - I see from your pic your using a vertical gpu bracket.

make sure it’s plugged into the pciex16 slot at the top or even better as a test remove the vertical bracket and mount the gpu normally and test.

 

a few people have had troubles using a vertical gpu bracket on a hack and had to move where it was plugged into (to the top slot) or remove the bracket all together.

it might very well be fine but it’s something to consider.

if I can think of anything else il add to this message  

 

Could you tell me what m.2 drives you have and where they are connected on your board and also what sata ports and pcie slots are you using? 
if you have a WiFi/Bluetooth card then what’s its make and model and what slot is it connected too?

Edited February 17, 2020 by AudioGod

[decat]

Hi, 

 

Will pose the question here, if I need to move over to the Clover section let me know.

I've been running your EFI for some weeks no and it still runs fine.

 

Mojave

9700k

Aorus Master

RX 580

Clover with your latest EFI

1 SSD with WIN10 & it's own EFI

1 SSD with Mojave & Clover

 

To keep it easy for the misses the default boot drive in the BIOS was WIN10, the Mojave drive with Clover was always chosen via F12.

To eliminate this step I tried to change this in Clover.  The default boot drive in Clover was set to WIN10 by using the Volume ID.

What doesn't work anymore since the change is the countdown timer. It's set to 10 seconds but doesn't count down.

It isn't a big issue but if it could be solved = great.  It's handy when rebooting remotely.

Thx in advance.

 

 

 

[AudioGod]

3 minutes ago, decat said:

Hi, 

 

Will pose the question here, if I need to move over to the Clover section let me know.

I've been running your EFI for some weeks no and it still runs fine.

 

Mojave

9700k

Aorus Master

RX 580

Clover with your latest EFI

1 SSD with WIN10 & it's own EFI

1 SSD with Mojave & Clover

 

To keep it easy for the misses the default boot drive in the BIOS was WIN10, the Mojave drive with Clover was always chosen via F12.

To eliminate this step I tried to change this in Clover.  The default boot drive in Clover was set to WIN10 by using the Volume ID.

What doesn't work anymore since the change is the countdown timer. It's set to 10 seconds but doesn't count down.

It isn't a big issue but if it could be solved = great.  It's handy when rebooting remotely.

Thx in advance.

 

 

 

change it too 9 seconds instead bud 

Edited February 17, 2020 by AudioGod

[decat]

Owkey, that easy huh.

Thx.

[texasdude11]

On 2/17/2020 at 3:44 AM, AudioGod said:

there’s many advantages to using a dsdt yes but I’m fascinated to know what’s going on with your build as the Oc EFI doesn’t use a DSDT so it sure isn’t that that’s the problem. It’s more like something about your setup isn’t lining up with mine to the extent that my EFI isn’t working for you,

what make and models are your m.2 drives?

as for the github EFI your using, I've seen that a few times before and it’s not that different to how I do things (more like how I used to do things before using a dsdt) so I’m surprised that works and mine doesn’t...hmmmmmm interesting.

would love to see what your doing to my EFI so I can get a reading if there’s an error going down in your info entries or Something like that as I take a view where if many work and one doesn’t then you have to look to the one that doesn’t before being able to move forward with a fix.

if you can PM me my EFI with your changes to it done then I might be able to work out what’s going on bud?

 

Update - I see from your pic your using a vertical gpu bracket.

make sure it’s plugged into the pciex16 slot at the top or even better as a test remove the vertical bracket and mount the gpu normally and test.

 

a few people have had troubles using a vertical gpu bracket on a hack and had to move where it was plugged into (to the top slot) or remove the bracket all together.

it might very well be fine but it’s something to consider.

if I can think of anything else il add to this message  

 

Could you tell me what m.2 drives you have and where they are connected on your board and also what sata ports and pcie slots are you using? 
if you have a WiFi/Bluetooth card then what’s its make and model and what slot is it connected too?

 

I'm using Samsung 970 Evo plus 1 TB. It was plugged into the topmost slot. It has been removed now.

And when that didn't work, I plugged in a sata ssd which is working flawlessly now. 

 

Now i have a Samsung 970 Evo Pro 1 TB plugged into the bottom, this one has Windows and Ubuntu on it. 

 

I have mounted GPU vertically only now when the system was stable.

 

I did notice something that I did accidentally tho. I don't have the USB cable plugged into the EVGA AIO cooler. It was plugged in when the system was unstable. But it is unplugged at the moment and the system is stable. Could unplugging the AIO cooler's USB resolve any issue? 

 

Also Everytime I restart the Mac OS i get a error that system started after an improper shutdown or something like that and shows the same error about NVME that i pasted earlier. But i just click don't send the report to apple and move on. It's not a deal breaker but I thought I'll mention that.

 

Would you be able to let me know what does the dsdt do? And what am I missing by not putting the patches? If I want to try your setup for efi, shall i just replace the efi with yours and see? If it breaks, I should be able to boot via USB with my current efi and revert, correct?

 

I was reading that dsdt is related to USB ports or something but can't get any clarity with my limited research.

Edited February 19, 2020 by texasdude11

[texasdude11]

On 2/17/2020 at 3:58 PM, AudioGod said:

change it too 9 seconds instead bud 

 

Hey @AudioGod,

 

I may need some assistance, I was working on my Mac just fine. I wanted to reboot to check if I get the error again and now I can't even get into Mac.

 

Would you know how to get into my MacOS and retrieve some files from there?

 

 

EDIT/UPDATE:

 

I was able to fix this issue by using OptioFix2Drv-free2000.efi instead the 3Drv.efi So weird, it was working till now and suddenly it stopped.

 

 

Edited February 19, 2020 by texasdude11

[AudioGod]

1 hour ago, texasdude11 said:

 

Hey @AudioGod,

 

I may need some assistance, I was working on my Mac just fine. I wanted to reboot to check if I get the error again and now I can't even get into Mac.

 

Would you know how to get into my MacOS and retrieve some files from there?

 

 

 

That is the system unable to assign a slide value and failing to allocate memory for the NVRam.

The best fix for that is to remove all power from the system and then pull the battery from the board for a few mins and then put it all back together, load back in your bios profile and carry on as normal. That’s the fix that always works but you can also try just hitting the reset button on the io plate and doing it that way. 
Also there’s a third very simple way that’s unlikely to work but worth a try first and that’s to press F11 on the clover boot picker and then restart the system.

 

i wrote in reverse order from hardest to easiest fix as the easiest fix is least likely to work.

 

what EFI are you using that this happened with?

Edited February 19, 2020 by AudioGod

[texasdude11]

1 minute ago, AudioGod said:

That is the system unable to assign a slide value and failing to allocate memory for the NVRam.

The best fix for that is to remove all power from the system and then pull the battery from the board for a few mins and then put it all back together, load back in your bios profile and carry on as normal. That’s the fix that always works but you can also try just hitting the reset button on the io plate and doing it that way. 
Also there’s a third very simple way that’s unlikely to work but worth a try first and that’s to press F11 on the clover boot picker and then restart the system.

 

i wrote in reverse order from hardest to easiest fix as the easiest fix is least likely to work.

 

what EFI are you using that this happened with?

 

I was just able to fix the issue by using OsxAptioFix2Drv-free2000.efi instead f 3Drv.efi. There was a solution in goole to use that so I did. And it apparantly worked! But it is so weird though! Why would it suddenly make me use a different efi file...

[AudioGod]

Just now, texasdude11 said:

 

I was just able to fix the issue by using OsxAptioFix2Drv-free2000.efi instead f 3Drv.efi. There was a solution in goole to use that so I did. And it apparantly worked! But it is so weird though! Why would it suddenly make me use a different efi file...

Aaahhhhhhh noooooo buddy disaster 

both the drivers you listed should not be touched.

they can cause serious damage to your system.

[texasdude11]

1 minute ago, AudioGod said:

Aaahhhhhhh noooooo buddy disaster 

both the drivers you listed should not be touched.

they can cause serious damage to your system.

 

Oh {censored}! what should i do then? 

 

I have been using the EFI from github that i posted earlier all along. I also tried booting with your efi when this issue happened and got same error. So i tried googling and this solution came up.

[AudioGod]

Please do a google on the free2000.efi and read the notes from the dev who made it. I’m just about to start work so il get back to you properly when I have a chance.

[texasdude11]

33 minutes ago, AudioGod said:

Please do a google on the free2000.efi and read the notes from the dev who made it. I’m just about to start work so il get back to you properly when I have a chance.

OK thank you my friend. I will google it. Probably good to just shutdown the computer as of now and read it in bed. It's 4 am here

 

EDIT/UPDATE:

 

WOW! Thank you for saving my hardware. I read about it and how it should not be used. That file is removed and i was able to use just the OsxAptioFix2Drv-64.efi file instead which booted the computer as well. Hopefully this wont cause any problems.

 

Edited February 19, 2020 by texasdude11

[JanRocker]

Hello again,

 

I finally built my system and I am getting ready to Hackintosh it.

 

One question. If I successfully install MACOS on a M2 SSD, could I unplug it and install another SSD in other bay to install Windows? I plan to run both Windows and MACOS from different M2 SSDs.

 

If I don't change any parameter in the Bios, could I mess something up from my MACOS or Bios during Windows installation considering that the MACOS' SSD would be unplugged?

 

 

Edited February 19, 2020 by JanRocker
Misstyping

[AudioGod]

4 hours ago, JanRocker said:

Hello again,

 

I finally built my system and I am getting ready to Hackintosh it.

 

One question. If I successfully install MACOS on a M2 SSD, could I unplug it and install another SSD in other bay to install Windows? I plan to run both Windows and MACOS from different M2 SSDs.

 

If I don't change any parameter in the Bios, could I mess something up from my MACOS or Bios during Windows installation considering that the MACOS' SSD would be unplugged?

 

 

Do it the way you asked and your have zero problems buddy.

last time I fresh booted macOS on my system I left my windows drive connected and it was fine and actually I’ve done a clean instal with windows and my macOS drive connected and again it was fine.

just to be safe though do unplug the other OS drive when installing a fresh one. Always better to play it safe my friend.