Jump to content

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

AudioGod

By AudioGod,
in Installation Guides

 Share
5539 posts in this topic

Recommended Posts

AudioGod
AudioGod
Posted
  • Author
Posted (edited)

@Tiem use the new EFI I posted yesterday. I think I have solved memory allocation failures at boot up and the need to battery reset the bios for once and for all.

also try raising your igpu memory if your using 19,1 from 64mb too 512mb for a nice kick in performance. :thumbsup_anim: 

Edited by AudioGod
AudioGod
AudioGod
Posted
  • Author
Posted (edited)

@WizeMan @pkdesign @Tiem @velopitex @tasc And anybody else reading this,

I have a test for anybody using the new EFI under 19,1 with igpu enabled.

using geekbench please run a gpu test and take a note of the score then restart the system and go into the bios and change the igpu memory from 64mb to 512mb 

Settings -> IO Ports -> DVMT Pre-Allocated -> 512m

Boot back into Catalina and once it’s fully loaded (after 2 or 3 mins) run the geekbench gpu test again and see if you get a nice kick in performance?

Be sure to let me know the result. :) 

 

if anybody gets a failure to allocate memory (stop sign at startup) using the new EFI ever then again please do let me know as thanks to the MemoryAllocation.efi and OcQuirks you should hopefully never see that or have to do a battery bios reset again. 

Edited by AudioGod
Sharkus
Sharkus
Posted
Posted (edited)
3 hours ago, AudioGod said:


that’s awesome buddy well done. :thumbsup_anim:

The Z390 Elite is not a mile away from the Z390 Pro so im not that surprised the dsdt is working with it but the power tables could very well be off..

have you tested things like sleep and wake and shut down after sleep and make sure that all works for you?

check the usb outputs all work for you too as the ssdt isn’t designed for your board but still might work as they are so close,

keep an eye on the motherboard when you shut down the system and make sure the board fully shuts down.


Sleep, restart, and shutdown all seem to be working fine.

 

My AIO (EVGA) seems to have the same problem as the Corsair (instantly wakes up from sleep if plugged into F_USB1).  I tried the patch mentioned on the first page, but that didn't seem to make any difference.  Not sure if I'm entering the patch properly into the clover configuration.  The screenshot shows a lot of checked fixes that are not in the default config, so not sure if I need all those or just the rename config.

 

Sidecar is giving me some trouble (my iPad is detected but gives a "The device timed out." error dialog after a few seconds).  I haven't spent much time debugging it yet.

Edited by Sharkus
AudioGod
AudioGod
Posted
  • Author
Posted (edited)
36 minutes ago, Sharkus said:


Sleep, restart, and shutdown all seem to be working fine.

 

My AIO (EVGA) seems to have the same problem as the Corsair (instantly wakes up from sleep if plugged into F_USB1).  I tried the patch mentioned on the first page, but that didn't seem to make any difference.  Not sure if I'm entering the patch properly into the clover configuration.  The screenshot shows a lot of checked fixes that are not in the default config, so not sure if I need all those or just the rename config.

 

Sidecar is giving me some trouble (my iPad is detected but gives a "The device timed out." error dialog after a few seconds).  I haven't spent much time debugging it yet.

 

try using sidecar wired instead of wireless and see if its the connection causing it?

if that works then go into your kexts folder within the EFI and delete airportfixup.kext, reboot and try Sidecar wireless again.

Edited by AudioGod
hackinhacker
hackinhacker
Posted
Posted
10 hours ago, AudioGod said:

That looks correct now at least.

great ok so like I said before it should just work. Can you confirm using windows that you have sound going though the HDMI line to your monitor all ok please bud?

 

I can confirm if HDMI sound works once I have to reformat the drive and install windows etc... I have only one HD and it's fully partiontioned, so I can't install windows on top of MacOS.  and it appears that vmware fusion doesn't work well on hackintosh according to my google search...  Any other option i can follow than reformat the drive?

 

Sharkus
Sharkus
Posted
Posted
2 hours ago, AudioGod said:

 

try using sidecar wired instead of wireless and see if its the connection causing it?

if that works then go into your kexts folder within the EFI and delete airportfixup.kext, reboot and try Sidecar wireless again.

 

Wired gave the same error.  I was able to get things working by logging out of my iCloud account in Catalina, then back in.  It probably had something to do with me originally logging in with the default serial number from Clover, then changing it after. 

  • Like 1
AudioGod
AudioGod
Posted
  • Author
Posted (edited)

NEW Clover EFI UPDATE 3rd January 2020


The EFI has now been updated to the my latest version.

Changes made include,

OcQuirks & FwRuntimeServices Latest Revisions

MemoryAllocation.efi now added to the UEFI driver folder to fix failure to boot due to memory allocation failure at start up 

Whatevergreen 1.3.6 latest Beta

Clover Updated too Revision 5102

Plus other minor tweaks to the clover config

 

EFI Update - 03/01/2020 - Use with Bios revision F11 Only

19,1 Aorus Z390 Pro Navi Vega EFI.zip - Vega, Navi (5700, 5700xt), Radeon VII DSDT EFI

19,1 Aorus Z390 Pro RX Polaris EFI.zip - RX5XX Polaris DSDT EFI

 

If you are having trouble to boot up using smbios 19,1 with iGPU enabled then make the following change to the bios

 

• Settings -> IO Ports -> DVMT Pre-Allocated -> 512M

 

You will need to reset the bios by Removing the power cable and then pulling the battery on the motherboard for a few minutes to totally clear the nvram before loading into Catalina with the new EFI for the first time.

Use the unlocked MSR Bios profile if you can and untick kernelPM in the clover config if you do use it.

 

If you prefer using SMBios 1,1 then by all means switch to it but all the old problems of using 19,1 are corrected now with this EFI plus DRM is fully working unless you have a  Polaris gpu. Just to add, SMBios 19,1 is the correct one to be using for our chipset and cpu, if you check the spec of a real macpro it is not a using a CoffeeLake CPU or Z3xx chipset. It does work perfectlyl but correct is correct so 19,1 it is. :) 

 


TESTING AND FEEDBACK NEEDED SO PLEASE TRY THE FOLLOWING.

 

I have a test for anybody using the new EFI under 19,1 with igpu enabled.

using geekbench please run a gpu test and take a note of the score then restart the system and go into the bios and change the igpu memory from 64mb to 512mb 

Settings -> IO Ports -> DVMT Pre-Allocated -> 512m

Boot back into Catalina and once it’s fully loaded (after 2 or 3 mins) run the geekbench gpu test again and see if you get a nice kick in performance?

Be sure to let me know the result. :) 

 

if anybody gets a failure to allocate memory (stop sign at startup) using the new EFI ever then again please do let me know as thanks to the MemoryAllocation.efi and OcQuirks you should hopefully never see that or have to do a battery bios reset again

Edited by AudioGod
jmcm
jmcm
Posted
Posted

Hi, I update to latest EFI and with RX580 the score in Geekbench 5 OpenCL was 43403 with 64m and now is 43657 with 512m.

64m: https://browser.geekbench.com/v5/compute/403156

512m: https://browser.geekbench.com/v5/compute/403197

 

I know the result is just ok, but I think that is what's expected with RX580...

 

No problems detected.

 

Thanks

  • Like 1
AudioGod
AudioGod
Posted
  • Author
Posted (edited)
19 minutes ago, jmcm said:

Hi, I update to latest EFI and with RX580 the score in Geekbench 5 OpenCL was 43403 with 64m and now is 43657 with 512m.

64m: https://browser.geekbench.com/v5/compute/403156

512m: https://browser.geekbench.com/v5/compute/403197

 

I know the result is just ok, but I think that is what's expected with RX580...

 

No problems detected.

 

Thanks

 

with a RX580 you have a slight increase. ok thank you for that.

on the 5700xt im getting a score bump of around 1000 with the igpu set at 512m. im trying to figure out if its universal or unique to the 5700xt or its just me.

 

@jmcm your getting a small bump up at in performance at 512m. it could be margin of error though so I need more results to know more. was the higher score consistent or did you only run the test once? 

Edited by AudioGod
Ralle
Ralle
Posted
Posted
3 hours ago, AudioGod said:

NEW Clover EFI UPDATE 3rd January 2020


The EFI has now been updated to the my latest version.

Changes made include,

OcQuirks & FwRuntimeServices Latest Revisions

MemoryAllocation.efi now added to the UEFI driver folder to fix failure to boot due to memory allocation failure at start up 

Whatevergreen 1.3.6 latest Beta

Clover Updated too Revision 5102

Plus other minor tweaks to the clover config

 

EFI Update - 03/01/2020 - Use with Bios revision F11 Only

19,1 Aorus Z390 Pro Navi Vega EFI.zip - Vega, Navi (5700, 5700xt), Radeon VII DSDT EFI

19,1 Aorus Z390 Pro RX Polaris EFI.zip - RX5XX Polaris DSDT EFI

 

If you are having trouble to boot up using smbios 19,1 with iGPU enabled then make the following change to the bios

 

• Settings -> IO Ports -> DVMT Pre-Allocated -> 512M

 

You will need to reset the bios by Removing the power cable and then pulling the battery on the motherboard for a few minutes to totally clear the nvram before loading into Catalina with the new EFI for the first time.

Use the unlocked MSR Bios profile if you can and untick kernelPM in the clover config if you do use it.

 

If you prefer using SMBios 1,1 then by all means switch to it but all the old problems of using 19,1 are corrected now with this EFI plus DRM is fully working unless you have a  Polaris gpu. Just to add, SMBios 19,1 is the correct one to be using for our chipset and cpu, if you check the spec of a real macpro it is not a using a CoffeeLake CPU or Z3xx chipset. It does work perfectlyl but correct is correct so 19,1 it is. :) 

 


TESTING AND FEEDBACK NEEDED SO PLEASE TRY THE FOLLOWING.

 

I have a test for anybody using the new EFI under 19,1 with igpu enabled.

using geekbench please run a gpu test and take a note of the score then restart the system and go into the bios and change the igpu memory from 64mb to 512mb 

Settings -> IO Ports -> DVMT Pre-Allocated -> 512m

Boot back into Catalina and once it’s fully loaded (after 2 or 3 mins) run the geekbench gpu test again and see if you get a nice kick in performance?

Be sure to let me know the result. :) 

 

if anybody gets a failure to allocate memory (stop sign at startup) using the new EFI ever then again please do let me know as thanks to the MemoryAllocation.efi and OcQuirks you should hopefully never see that or have to do a battery bios reset again

 

@AudioGod again I am stunned about your excellent work on this. First I was a little worried about updating to your latest EFI because my hack already was running great. Except Apple TV+. But I just update my EFI now and voila.. my hack is even better now. Will try to change my DVMT to 512 and see if there is a bump in Geekbench. I will report. Apropos my VSTs are all running flawlessly, just like you said buddy. Thanks again for your great work :thumbsup_anim: 

  • Thanks 1
AudioGod
AudioGod
Posted
  • Author
Posted (edited)
3 minutes ago, jmcm said:

@AudioGod I only run the test once. Now, after boot, I've got 43857, but on repeat it's getting worse: 43579, 43122...

That’s margin or error nothing more then. (As well as Processes running in the background changing the score)

 

if you get the same results at 64m then stay there.

 

1 minute ago, Neblogas said:

Does the new EFI folder work with F11 and Mojave? not Catalina?


yes buddy no problems with Mojave go for it. :thumbsup_anim:

Edited by AudioGod
Ralle
Ralle
Posted
Posted (edited)

Here are my results with the new EFI 19,1 from Audiogod (2020/01/03)

 

CPU Benchmark:

400351324_Bildschirmfoto2020-01-05um15_34_20.thumb.png.76c45f34a6448694682085c7a3cc027b.png

 

Compute Metal:

333073945_Bildschirmfoto2020-01-05um15_30_31.thumb.png.069de0078cb5bd9b4ecc0fe202ddc7f5.png

 

Compute OpenCL

1175963163_Bildschirmfoto2020-01-05um15_31_34.thumb.png.1e1968ba757e88cc07d3c707d02ecc38.png

 

Everything looking good... :D:yes:

 

Edited by Ralle
AudioGod
AudioGod
Posted
  • Author
Posted

@Ralle can you clean that post up please buddy it’s huge and has the same post pasted 4 times on one message? :hysterical:

 

Can you do the OpenCL gpu test only at 64m and then again at 512m and compare results Please. LoL :thumbsup_anim:

Ralle
Ralle
Posted
Posted
Just now, AudioGod said:

@Ralle can you clean that post up please buddy it’s huge and has the same post pasted 4 times on one message? :hysterical:

 

Can you do the OpenCL gpu test only at 64m and then again at 512m and compare results Please. LoL :thumbsup_anim:

Just saw it :whistle:

Neblogas
Neblogas
Posted
Posted

Hmm

 

Well,

system does not boot anymore...

 

Before I had an older version of the EFI folder and it was working ok till today.

 

System stops booting at loading nvme(see attachement)

 

Same problem with the new EFI folder.

 

System boots only with install USB.

 

IMG_20200105_153858.jpg

AudioGod
AudioGod
Posted
  • Author
Posted (edited)
4 minutes ago, Neblogas said:

Hmm

 

Well,

system does not boot anymore...

 

Before I had an older version of the EFI folder and it was working ok till today.

 

System stops booting at loading nvme(see attachement)

 

Same problem with the new EFI folder.

 

System boots only with install USB.

 

IMG_20200105_153858.jpg

What’s your setup please?

 

i don’t think that’s got anything to do with my EFI if it just stopped working on it’s own

Edited by AudioGod
Ralle
Ralle
Posted
Posted (edited)
18 minutes ago, AudioGod said:

@Ralle can you clean that post up please buddy it’s huge and has the same post pasted 4 times on one message? :hysterical:

 

Can you do the OpenCL gpu test only at 64m and then again at 512m and compare results Please. LoL :thumbsup_anim:

 

Here you go buddy  64MB

1080455524_Bildschirmfoto2020-01-05um16_01_22.thumb.png.a54309ed89c29e0a335400ddc2d1e409.png

 

2053268097_Bildschirmfoto2020-01-05um16_02_25.thumb.png.20228904b21a7e8e81d23f19364c98d1.png

 

Looks like 64 MB works better...

 

 

 

 

Edited by Ralle
AudioGod
AudioGod
Posted
  • Author
Posted (edited)
10 minutes ago, Ralle said:

 

Here you go buddy  64MB

1080455524_Bildschirmfoto2020-01-05um16_01_22.thumb.png.a54309ed89c29e0a335400ddc2d1e409.png

 

2053268097_Bildschirmfoto2020-01-05um16_02_25.thumb.png.20228904b21a7e8e81d23f19364c98d1.png

 

Looks like 64 MB works better...

 

Bildschirmfoto 2020-01-05 um 15.57.13.png

Bildschirmfoto 2020-01-05 um 15.58.16.png


you know what, that’s the exact opposite to my results using the same gpu...lolol

That now just shows me it’s the 5700xt and the rubbish OSX drivers.

im betting them results will sway if you keep doing them. 
I think that solves it but a few more 5700xt user results would be the icing on the cake. 
 

8 minutes ago, Neblogas said:

i7 9700k

Aorus z390 Pro F11

Gigabyte RX580

32GB RAM

WD Black SN750 nvme Mojave

WD Black SN750 nvme Arch Linux

Windows 10 SSD


When did this start happening exactly, was it random?

 

How come your still using fakesmc? How old is your EFI bro? 

Edited by AudioGod
Neblogas
Neblogas
Posted
Posted
3 minutes ago, AudioGod said:

When did this start happening exactly, was it random?

 

Today. I have tried to update some kexts through Hackintool. after that did not boot anymore. Deleted the new kexts, rebuild kextcache and permissions.

 

Also, my arch install was not booting anymore with clover, just directly from bios boot menu.

AudioGod
AudioGod
Posted
  • Author
Posted (edited)

 

8 minutes ago, Neblogas said:

 

Today. I have tried to update some kexts through Hackintool. after that did not boot anymore. Deleted the new kexts, rebuild kextcache and permissions.

 

Also, my arch install was not booting anymore with clover, just directly from bios boot menu.


yikes, that sounds like a bit of a mess.

you should consider starting again maybe and doing a fresh boot,

1st thing I would try before that is reflash your bios using F11 and then load in my bios MSR unlocked profile and using the new EFI and adding your details try and boot up. If that don’t work you might very well need to reinstall it. Lesson here is don’t use hackintool to install kexts. Do it yourself and just reboot for the kexts to take effect, there’s no need to be rebuilding the cache bud. Ops! 

Edited by AudioGod
 Share
Go to topic listing
×
×
  • Create New...