Jump to content

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


AudioGod
5,966 posts in this topic

Recommended Posts

17 hours ago, laxattack said:

I switched to OpenCore and no longer had any kernel panics

 

Happy new year to all,

 

 

Q: did you ever test the latest EFI from here based on OCQuirks ? 

Wondering which OC EFI did you use , own configured, DSDT based or SSDT-only  ?

 

 

Link to comment
Share on other sites

21 hours ago, AudioGod said:

@Tiem I’ve just had a brain wave moment :hysterical:

The hub your using is it a USB 3 one and if it is are you up trying to use usb3 and usb2 devices off it because if you are you might be pushing he boundary’s of what the usb patching can do so do me a favour and try running just the mouse off the hub via a usb 2 port from the system with no other devices attached to the hub and tell me the result please brah?

its just a theory and not a fact but it does make some sense. :) 

I've got an earlier model G502 which I'm pretty positive is just USB 2.0. With just the mouse plugged into HS13 (the 4 USB 2.0) this is what Hackintool outputs (I disabled Legacy USB support in the BIOS):

 

1735888996_ScreenShot2020-01-02at2_02_06AM.thumb.png.c701ea88bf2398d7835f72c9e533a6dc.png

 

The ordering actually looks a lot better now. G HUB still can't see my mouse, but google shows even people with legit Mac's can sometimes not get it working so it might just be Logitech.

Link to comment
Share on other sites

Just now, Tiem said:

I've got an earlier model G502 which I'm pretty positive is just USB 2.0. With just the mouse plugged into HS13 (the 4 USB 2.0) this is what Hackintool outputs (I disabled Legacy USB support in the BIOS):

 

1735888996_ScreenShot2020-01-02at2_02_06AM.thumb.png.c701ea88bf2398d7835f72c9e533a6dc.png

 

The ordering actually looks a lot better now. G HUB still can't see my mouse, but google shows even people with legit Mac's can sometimes not get it working so it might just be Logitech.


bro for the third time, hackintosh can’t display the patching info correctly and will not reflect what the usb output are actually doing because of the way the patching works,

your getting a picture from it but it’s also an incorrect one.

im not going to explain that again to you brother....lol dam it lol

Link to comment
Share on other sites

Big thank you to audiogod, for this thread and top notch expertise. Also a big thank you to Maldon and glasgood for alternative solutions. At this point Im using bios f11 and audiogod’s pro nave vega zip efi, MSR profile, patches, drivers and kexts minus Whatevergreen, but before this I was testing so many variations, Its been monumental in getting my aorus pro pro back into OSX. My journey to this point wasnt easy, I think for me that Catalina is the most difficult mac OS to get stable and functioning well. Im posting a reply here because I want to help and return some support if I can. 

 

I’ve been reading a few posts with issues that I had and maybe still have and I’ll try to give some tips.

 

Resolved major issues:

 

Boot looping in post. 

 

Possible causes.  f11 bios, 32gb ram, MSR unlock profile.

Post error was a ram issue but it occurred After I installed the MSR profile, I managed to resolve the issue to some extent but I still get weird boot anomalies like power button flash when pressed but no power on and also the odd boot loop once in a while.

 

I didn’t scientifically diagnose the issue but what helped MSR profile to become more stable was indeed like audiogod’s suggestion of removing the battery from the mobo but for me I also had to reduce the ram to 16gb and run that for a few shutdowns and restarts the add the other sticks. I found bios f10 was the most stable but alas the msr profile is not suggested for any other bios revision.

 

Error 0x0000xxxx alloc type 2 runtime blah blah (This error came at the first 2 or 3 lines in verbose mode) The dreaded stop circle.

 

Causes: igfx, titan ridge pci card (and possibly something else)

Whats amazing is this error just occurred way after installation and normal use, with no change to bios settings.

 

What solved the issue was igfx disabled in bios. Unfortunately I needed it for headless mode, fcpx and acceleration. So after many hours of testing... igfx at 64mb in bios worked with the one port setting in the thunderbolt configuration menu resolved this error. I have a GC titan ridge add on card for my LG 5k display.

 

Ongoing Issues:

 

1. Sidecar worked once when I first install OS, then crapped out with device timed out error ever since. Update: its worked twice so far... Why now?

 

2. Logitech g502 not connected in GHUB, but system report/usb Identifies it properly. Someone earlier had posted the same problem, I'm unable to customise my mouse buttons.

 

3. Black screen when restarting or waking, but this is difficult to resolve because I'm running my monitor through a thunderbolt card. Don't know where the problem lies.

 

Choppy HEVC and very high bit video playback in VLC, Quicktime and unresponsiveness/crashes in Final cut pro.

 

I downloaded some very high bit 4k jelly fish test vids to test.

Possible Causes: igpu configuration in DSDT, Whatevergreen, vega 56 (and possibly something else).

 

Early stage but looks promising, using audiogod’s DSDT I added “injectintel” to clover graphics and removed Whatevergreen.

Update: Ive just had really choppy video playback with these settings. I restarted my pc and smoothness has returned. hmmm

 

Now here is what I've noticed in my trail and error testing, maybe audiogod or others can shed some light on the differences between these set ups?

 

setup 1. Audiogod’s DSDT only

 

In “about this mac”, Graphics/displays report was slow to report information ( about 4 seconds). Only my vega 56 info reports and all is looking as it should. PCI info shows the intel 630 as “Other display controller” and intel acceleration is showing in ioreg... but choppy video

 

screenShot 1

2048099529_screenshotuhdother.thumb.jpg.0f4c525ddac9596a1d75ffa6985dee19.jpg

 

setup 2. Without DSDT and only using Maldon's Olarila method of a few Configuration changes through clover (sorry no actual screen shots but screenShot 2 is close but without the gpu's numbers 1 and 2 as shown)

 

In "system report" / Graphics is instant and there is no lag in getting the report as described in the above DSDT method. Now depending what ig-platform id I set in clover, I get 2 different report results. Both result in choppy video but the system report is different.  

1. Intel UHD 630 and Vega 56 is now shown in "graphics/displays". this did not occur with the above method (check screenShot 2). IOreg shows intel acceleration but there is one snag Final Cut Pro fails to launch and a crash report is generated.

2. No four second lag in generating Graphics/display report, but it only shows the Vega (basically the same result as audiogod's DSDT method but without the pci info) but Final Cut works with choppy unresponsive video.

 

setup 3. With audiogod's DSDT, InjectIntel added in clover and Whatevergreen removed from efi

 

Final Cut opens and works better with very high bitrate HEVC and h264 video, smoother frame rate out put in VLC and Quicktime, intel acceleration active in IOreg 

 

screenShot 2.

1607850017_Screenshot2019-12-30at19_53_25.thumb.png.4c064a6c411d02c36417ca11c3c255df.pngimageproxy.php?img=&key=c17464ef1b1b51c7

Now there are a number of differences in this method.

1. As in method 2 above when "Graphics/displays" reports the the gpu's in this way, Final Cut Pro would crash when launching.

2. GPU numbers and Infinity fabric Link were not present in any other method.

3. PCI report (I know its cosmetic) also changed (see screenshot 3). It now shows as VGA compatible? Please compare it to screenShot 1.

 

screenShot 3

1846594303_Screenshot2020-01-02at13_56_03.thumb.png.f8489b13bd91e3dc23a975f60251b811.png

 

screenShot 4

283750828_Screenshot2020-01-02at15_35_55.thumb.png.f981aa49c8c095dc663a31760c93ce2b.png

 

Without Whatevergeen I get pink/purple lines at the end of the apple boot screen but clears at login screen.

 

I have just noticed this.

 

screenShot 5

1360485683_Screenshot2020-01-02at14_27_33.thumb.png.39c20567df6a3f54d41e289723d3d9ec.png

 

my Vega 56 is showing as a Vega 64, that didn't happen in my Mojave hack. Is that an issue?

 

I hope some of this info helps someone

 

Sorry I forgot to add that to get setup 3 to work I also had to set Initial display to igfx and not pci 1.

 

 

Edited by fart pants
Added info
Link to comment
Share on other sites

@fart pants I’m not sure where to start with all that info but that amount of errors you have made with your changes are huge.

il start off igpu enabled, you want to be headless and not showing in hardware info, the way you have it is totally wrong and not running in headless mode.

for the vega, you shouldn’t be injecting it via clover and just use whatevergreen. I used to use the same Vega56 pulse as you do before I swapped it for the nitro and then the 5700xt and everything was perfect the way it’s set up now.

My method is the same as MaLd0ns method as the guy helps me out loads and does me DSDTs for me and glassgood uses my EFI’s now himself and he’s guides now point to my downloads so we are all on the same page when it comes to how a EFI is meant to be setup.

can you send a copy of your EFI for me to examine please buddy? 
 

By the way your user name is awesome....:hysterical::hysterical:

Edited by AudioGod
Link to comment
Share on other sites

4 minutes ago, AudioGod said:

@fart pants I’m not sure where to start with all that info but that amount of errors you have made with your changes are huge.

il start off igpu enabled, you want to be headless and not showing in hardware info, the way you have it is totally wrong and not running in headless mode.

for the vega, you shouldn’t be injecting it via clover and just use whatevergreen. I used to use the same Vega56 pulse as you do before I swapped it for the nitro and then the 5700xt and everything was perfect the way it’s set up now.

My method is the same as MaLd0ns method as the guy helps me out loads and does me DSDTs for me and glassgood uses my EFI’s now himself and he’s guides now point to my downloads so we are all on the same page when it comes to how a EFI is meant to be setup.

can you send a copy of your EFI for me to examine please buddy? 
 

By the way your user name is awesome....:hysterical::hysterical:

 

hello audiogod, Haha yeh the name is classic... 

 

"il start off igpu enabled, you want to be headless and not showing in hardware info, the way you have it is totally wrong and not running in headless mode."

yep that's what I wanted but I was losing frames and getting choppy video playback with very high bitrate H264 and HEVC videos. That why I experimented. I must admit I never noticed it before when headless in my Mojave hack but I never edited 4k or above back then but I'm planning to now.

 

"for the vega, you shouldn’t be injecting it via clover and just use whatevergreen."

I'm not, see screenshot 4. Just Injectintel, unless your DSDT is injecting it? I'm using your Navi/Vega zip efi in your first post. Yeh I used MaLd0ns guide at Olarila for headless 8700K along time ago for Mojave and it worked a treat. His new guide for 9900k shows that he is able to remove whatevergreen.

 

https://olarila.com/forum/viewtopic.php?t=10565#p86617

 

I can't explain why but I'm getting better performance with method 3 its calculated fluke. Its early days, it may mess-up something else.

 

"can you send a copy of your EFI for me to examine please buddy?"

Sure no problem, thanks for looking.

EFI.zip

Link to comment
Share on other sites

6 hours ago, fart pants said:

 

hello audiogod, Haha yeh the name is classic... 

 

"il start off igpu enabled, you want to be headless and not showing in hardware info, the way you have it is totally wrong and not running in headless mode."

yep that's what I wanted but I was losing frames and getting choppy video playback with very high bitrate H264 and HEVC videos. That why I experimented. I must admit I never noticed it before when headless in my Mojave hack but I never edited 4k or above back then but I'm planning to now.

 

"for the vega, you shouldn’t be injecting it via clover and just use whatevergreen."

I'm not, see screenshot 4. Just Injectintel, unless your DSDT is injecting it? I'm using your Navi/Vega zip efi in your first post. Yeh I used MaLd0ns guide at Olarila for headless 8700K along time ago for Mojave and it worked a treat. His new guide for 9900k shows that he is able to remove whatevergreen.

 

https://olarila.com/forum/viewtopic.php?t=10565#p86617

 

I can't explain why but I'm getting better performance with method 3 its calculated fluke. Its early days, it may mess-up something else.

 

"can you send a copy of your EFI for me to examine please buddy?"

Sure no problem, thanks for looking.

EFI.zip


I will take a good look though that EFI tomorrow buddy and report back with my findings. :thumbsup_anim: 

Link to comment
Share on other sites

First of all, I want to say "thank you so much" for your help

 

Although my new hackintosh seems to be in good working condition, audio is not working and was wondering what I have to do to make it work

Here is my HW spec.

• Intel i5 9600K 
• Gigabyte AORUS Z390 PRO with f11 BIOS
• Sapphire Pulse RX970 4GB (connected to LG monitor with DisplayPort)
• Samsung 970 EVO 1TB NVMe SSD macOS Mojave

Sound Output is set to LG Ultra HD via DisplayPort

 

I used the 19,1 Z390 Pro RX EFI.zip and set to iMacPro1,1

 

You can find the kext I have in the attachment.

 

Could anyone please help?

 

 

Screen Shot 2020-01-02 at 7.37.44 PM.png

Link to comment
Share on other sites

3 hours ago, AudioGod said:

@hackinhacker Are you trying to send audio down the Gpus HDMI output or from the sound card?

 

Also are you using my latest EFI or an older one?

I was assuming the audio should automajically should be coming out of the Sapphire GPU RX570 DisplayPort :)  I am using your not so old EFI which was downloaded on 12/17. 

Link to comment
Share on other sites

10 minutes ago, hackinhacker said:

I was assuming the audio should automajically should be coming out of the Sapphire GPU RX570 DisplayPort :)  I am using your not so old EFI which was downloaded on 12/17. 

Am I supposed to use DSDT.RX Series.zip  as well as the 19,1 Z390 Pro RX EFI.zip ??  If that is the case, then I didn't use the DSDT.RX Series.zip 

Link to comment
Share on other sites

14 minutes ago, hackinhacker said:

Am I supposed to use DSDT.RX Series.zip  as well as the 19,1 Z390 Pro RX EFI.zip ??  If that is the case, then I didn't use the DSDT.RX Series.zip 

 

I'm not sure if this would help troubleshooting.  The system report is showing the LG monitor to be the output source and recognizes the output port as DisplayPort.

Screen Shot 2020-01-02 at 11.24.20 PM.png

Link to comment
Share on other sites

5 hours ago, hackinhacker said:

 

I'm not sure if this would help troubleshooting.  The system report is showing the LG monitor to be the output source and recognizes the output port as DisplayPort.

Screen Shot 2020-01-02 at 11.24.20 PM.png


Can you please show a screen shot of your sound/output tab? Make sure your output is the displayport if it is present. Also can you take a look at ioreg info? 
 

sorry, forget the make sure bit, i just read this properly.

Edited by fart pants
Link to comment
Share on other sites

6 hours ago, hackinhacker said:

 

I'm not sure if this would help troubleshooting.  The system report is showing the LG monitor to be the output source and recognizes the output port as DisplayPort.

Screen Shot 2020-01-02 at 11.24.20 PM.png


that’s strange, I’ve just noticed that your outputs are showing wrong.

have you done something different to the EFI and the way audio works?

go into your clover config and make sure your audio layout is 7.

 

Also what is a RX970 when it’s at home?

ive never heard of that gpu before????

i know of a Nvidia GTX970 or do you mean a RX570?

 

Send me a copy of your EFI to look at please matey. :) 

Edited by AudioGod
Link to comment
Share on other sites

@fart pants Your using SMBios 19,2 and this is incorrect. Use SMBios 19,1 or MacPro 1,1 with IGPU disabled but not 19,2

You don't need to over install clover like you have and if you do then DO NOT INSTALL RC Scripts as its not needed.

 

Try again and this time dont do anything other then create new details for 19,1 everything is setup correctly for your setup with my EFI.

 

Heres your EFI back cleaned up and changed to the correct smbios for you. Ive made some minor changes and put the GPU injection back to how it should be and reinserted WEG 1.3.6. make new details and try it as it is please and let me know how you get on?

 

FartPants EFI.zip

Link to comment
Share on other sites

35 minutes ago, hackinhacker said:

I think I broke my hackintosh. lol Instead of replacing the EFI on the HD, I renamed the old one to EFI.OLD, and copied the provided new EFI onto the HD, now the screen is showing the Apple logo then it gets stuck at the apple logo screen after the clover boot prompt. sigh....

What EFI was that?

i asked to see your EFI bud and I never provided you with a new one.

i can help you out but I need to understand what’s going on first..lol

use your usb stick install to gain access back into your system if your locked out or if it’s the memory failing to allocate to the nvram then power down and remove the mains cable and then remove the battery from the motherboard for a couple of minutes and this will totally clear out your bios and any remaining fragments of the old EFI drivers from the native nvram.

 

The EFI I posted not long ago on the thread is not meant for you and incorrect for your setup pal hence why I put the users name on the EFI and addressed it to him. :hammer:

Edited by AudioGod
Link to comment
Share on other sites

8 minutes ago, hackinhacker said:

I've used the provided "FartPants EFI.zip". I'm not able to upload the EFI as the size is too big even after zip it.

 

.empty

vol_recovery.icns

vol_internal_ext3.icns

os_slackware.icns

os_vista.icns

vol_firewire.icns

os_ecomstation.icns

func_options.png

os_debian.icns


the fartpants Efi is not for you pal and incorrect for your setup.

 

if your EFI is to big to send then you have done something major time wrong my friend... what on earth is going on there? :hysterical:

 


@hackinhacker go into the EFIs themes folder and delete everything from it apart from the folder neon and then zip it up and send it to me. That should do it. :) 

Link to comment
Share on other sites

4 hours ago, AudioGod said:

@fart pants Your using SMBios 19,2 and this is incorrect. Use SMBios 19,1 or MacPro 1,1 with IGPU disabled but not 19,2

You don't need to over install clover like you have and if you do then DO NOT INSTALL RC Scripts as its not needed.

 

Try again and this time dont do anything other then create new details for 19,1 everything is setup correctly for your setup with my EFI.

 

Heres your EFI back cleaned up and changed to the correct smbios for you. Ive made some minor changes and put the GPU injection back to how it should be and reinserted WEG 1.3.6. make new details and try it as it is please and let me know how you get on?

 

FartPants EFI.zip

 

config.plist

CodeResources

CodeRequirements-1

Info.plist

platform.h

4 hours ago, AudioGod said:

@fart pants Your using SMBios 19,2 and this is incorrect. Use SMBios 19,1 or MacPro 1,1 with IGPU disabled but not 19,2

You don't need to over install clover like you have and if you do then DO NOT INSTALL RC Scripts as its not needed.

 

Try again and this time dont do anything other then create new details for 19,1 everything is setup correctly for your setup with my EFI.

 

Heres your EFI back cleaned up and changed to the correct smbios for you. Ive made some minor changes and put the GPU injection back to how it should be and reinserted WEG 1.3.6. make new details and try it as it is please and let me know how you get on?

 

FartPants EFI.zip

 

Link to comment
Share on other sites

5 minutes ago, hackinhacker said:


that’s not your EFI

 

:hysterical: @hackinhacker ok ok don’t worry I will create a new EFI for you to try now but just tell me this much please.

 

are you using smbios 1,1 and are you using the unlocked MSR bios profile?

Edited by AudioGod
Link to comment
Share on other sites

15 minutes ago, AudioGod said:


that’s not your EFI

 

:hysterical: @hackinhacker ok ok don’t worry I will create a new EFI for you to try now but just tell me this much please.

 

are you using smbios 1,1 and are you using the unlocked MSR bios profile?

 

It is showing SMBIOS set to iMacPro1,1, and I have not unlocked MSR bios profile.

 

Screen Shot 2020-01-03 at 10.08.57 AM.png

Edited by hackinhacker
Link to comment
Share on other sites

9 minutes ago, hackinhacker said:

 

It is showing SMBIOS set to iMacPro1,1, and I have not unlocked MSR bios profile.

 

Screen Shot 2020-01-03 at 10.08.57 AM.png

 

Here you go,

Put your serial number details back in and Replace your EFI with this one.

 

HackinHacker EFI.zip

 

@hackinhacker make sure you fill in your MLB under RT Variables, its the same serial as your board serial number. 

Don't remove or Add any boot arguments or additional kexts, use the EFI just as I sent it to you.

Edited by AudioGod
Link to comment
Share on other sites

×
×
  • Create New...