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

[AudioGod]

13 minutes ago, freakermonguer said:

 

 

I have a USB for testing. No problem on that

 

But the instructions I find on https://github.com/acidanthera/RTCMemoryFixup are minimal.

 

I don't see any kext only a plist file and also the cpp files, etc, so I guess I have to compile the kext - if it is one - 
Well... as a programmer myself I don't see it very well explained... 

 

Also, as you know the system very well, on question. I noticed that the OpenCore files from AudioGod include  AirportBrcmFixuo.kext. I didn't remove it for my build as it worked. But... could it be causing trouble with my system????

 

 

 

Any help or guidance is very welcome, thanks.

 

 

 

 

When I get home from work I can compile your Efi for you with the correct kexts if you like buddy?

As for AirportBrcmFixup.kext it might help with it disabled but I personally very much doubt it but saying that go into the config.plist and set the kext to disabled and see if it helps.  (Don’t just delete it from the kext folder as this will stop OpenCore from working if it’s still enabled in the plist)

 

Edited July 21, 2020 by AudioGod

[pkdesign]

FYI for Clover users: I updated to Clover 5120. Clover update is fine but the new included OcQuirks.plist via Clover config isn't working for me. See my post below:

Seems to be okay to simply update Clover though.

 

EDIT01:

According to Slice you have to use the OcQuirks.efi from the Clover installer. I will try this afternoon.

 

EDIT02:

I reinstalled and included OcQuirk.efi from Clover installer and I still can not boot.

Edited July 22, 2020 by pkdesign
New info

[pkdesign]

On 7/13/2020 at 3:06 PM, Tiem said:

KASLR. Stop using Clover if you want a 100% reliable boot process, failing that, calculate your slide value if you want an additional level of operability for the macOS kernel.

Do you have a good guide for how to do that? I've seen a few and they are all confusing.

[Tiem]

10 hours ago, pkdesign said:

Do you have a good guide for how to do that? I've seen a few and they are all confusing.

 

https://www.reddit.com/r/hackintosh/comments/d524ip/understanding_and_fixing_couldnt_allocate_runtime/

 

Probably the most thorough write-up on the topic. Note that this is not a 100% perfect cure. KASLR is deterministic to a point but your BIOS and other quirks may allocate the block of memory you end up using and you may need to find another free block.

 

It's always good form to reset everything before doing this (NVRAM but also your CMOS). Starting as clean as possible will greatly reduce the need to do it repeatedly and the value will have a far better chance of sticking.

 

You really shouldn't need to do this today. Especially with OC. But even Clover has now pretty much solved this problem.

 

Lastly, it is old even being 10 months young. While all still applicable, things with OC and even Clover have changed.

 

PS: If you're a giant nerd and want to know more about KASLR, read: https://lwn.net/Articles/569635/ (I think the reddit post may link to this as well)

Edited July 22, 2020 by Tiem
additional info

[freakermonguer]

14 hours ago, AudioGod said:

When I get home from work I can compile your Efi for you with the correct kexts if you like buddy?

As for AirportBrcmFixup.kext it might help with it disabled but I personally very much doubt it but saying that go into the config.plist and set the kext to disabled and see if it helps.  (Don’t just delete it from the kext folder as this will stop OpenCore from working if it’s still enabled in the plist)<<<<------

 

 

 

X-D I know, I know, that was exactly the FIRST thing I did when I copied the opencore files the first time and my system didn't boot at all... go figure....

 

Ok, when I end work today I can disable AirportBrcmFix and try to see what happens. You don't need to compile the Efi for me, man, thank you for offering your time. Just give me some guidance of what should I do, so I can learn a little bit about how this works. 

 

 

[Yayiin]

On 7/17/2020 at 1:54 PM, AudioGod said:

Yes keep it enabled in the bios and also in powersaving in settings.

wake on lan can behave erratically and be woken up by things like your iPhone or iPad screen waking or your Apple Watch when you look at it but AirportBRCMfixup.kext can Help with that and settle it down.

 

 

Yes I am sure about this. I wouldn’t say it if I wasn’t.

also it should indeed be set too internal not usb2 but that won’t cure the problem probbaly. (HS11=internal and HS13=USB2)

again it’s pcie adaptor dependent and yes it’s the bluetooth that causes the wake.

 

Side Note - I’m referring to OpenCore here as my clover EFI doesn’t work right with hackintool as Usb is being done via the ssdt and DSDT to give you native usb with no port limit. You can change this if you prefer to make it with a kext and 15 port limit.

Works! But I had to disable ERP in Bios to power on the hackintosh.

Thanks!

[matt-uk]

Hi @AudioGod

 

You posted a new bios which allows serial port to be disabled and profile to unlock MSR in the Z390 Aorus Master thread. Is there a similar new bios for the Pro?

 

I am using the Master at the moment but have a lot of coil whine from VRM same as many people so I’m thinking of RMAing to Amazon and switching to the pro, plus money back in my pocket.

 

 Thanks 

[panosru]

Is it possible to downgrade to 10.15.5? After 10.15.6 my USB microphone records the sound very distorted... :/ 

 

Thanks!

[freakermonguer]

15 minutes ago, panosru said:

Is it possible to downgrade to 10.15.5? After 10.15.6 my USB microphone records the sound very distorted... :/ 

 

Thanks!

 

Don't know, usually not. Always, MAKE A BACKUP OF YOUR SYSTEM in a spare drive. If ANYTHING GOES WRONG, you restore your system from that drive. 


 

[panosru]

Yeah, that's correct, I'm also giving the same advice, the issue is that I didn't follow that :/ I wonder though why no-one else complained about it, I'm not sure if it's just me... I tested a few USB mics, and none worked on my system, all worked on PC and my MacBook pro. The issue happened just right after the 10.15.6 upgrade, as I'm aware, 10.15.6 introduced some fixes to the USB interface, maybe those fixes interfere with the kexts we use in hackintosh world and I'll have to wait for an upgrade. Most likely I will switch to a 3.5 external mic before a kext update will be released.

[AudioGod]

1 hour ago, matt-uk said:

Hi @AudioGod

 

You posted a new bios which allows serial port to be disabled and profile to unlock MSR in the Z390 Aorus Master thread. Is there a similar new bios for the Pro?

 

I am using the Master at the moment but have a lot of coil whine from VRM same as many people so I’m thinking of RMAing to Amazon and switching to the pro, plus money back in my pocket.

 

 Thanks 

Yes indeed, goto Page one of this thread buddy and your find everything you need to do it. 

 

I wouldn’t get a Z390 Pro after owning the Master though, The chances are you will regret it and get buyers remorse if you do.  In my eyes it’s to big of a step down. I’m not knocking the pro board it just doesn’t compare to the Master.

 

Ive heard about the coil whine on the master but having done over 10 different builds using that board I have never come across it myself.

 

Nvidia GPU coil hum I hear that all the blooming time, More of them GPUS whine then don't.  

 

@matt-uk I Have a Z390 Designare going spare I could sell to you for a decent price if you like brother? PM me if your interested. 

Edited July 22, 2020 by AudioGod

[Tiem]

1 hour ago, panosru said:

Is it possible to downgrade to 10.15.5? After 10.15.6 my USB microphone records the sound very distorted... :/ 

 

Thanks!

Yes. The way we install macOS on hacks is to create a USB installer. Find someone to share their 10.15.5 installer or find one on the net. You can no longer pull it directly from Apple, however, as they have updated their servers to the new 10.15.6 and are no longer delivering any prior version.

 

Ask around. NOT IN THIS THREAD.

 

Obligator RTFM Notice: This is why you use TM or better yet, go grab a few USB sticks and keep a few iterations of old version on hand. If you can't be bothered to do that, then you have to live with the consequences.

 

A better alternative is to fix what is causing the issue. Apple fixed USB 2.0 device drops in 10.5.6 and that may have inadvertently borked the way Hackintoshes work with USB 2.0.

1 hour ago, AudioGod said:

Ive heard about the coil whine

 

This is unfortunately pretty normal. My Pro Wifi has some and so did my Mac mini and even my Mac Pro (2013). The MP was pretty bad AFAIR. If you hear it it's likely because your environment is really quiet. If you don't it's likely that your hearing misses it or it's drowned out by other noise. IMO every board I've had in a desktop class Mac or PC has had it to some degree. Notebooks and mobile devices I have never heard them (not saying they don't also have it, but it could be their chassis construction hides it.

 

Totally normal and if you manage to get an RTM over that, I would be impressed. More impressed if you could show me the new one doesn't also have it.

 

You can search on the net for remedies, but it's just how transistors work TBH.

[AudioGod]

9 minutes ago, Tiem said:

Yes. The way we install macOS on hacks is to create a USB installer. Find someone to share their 10.15.5 installer or find one on the net. You can no longer pull it directly from Apple, however, as they have updated their servers to the new 10.15.6 and are no longer delivering any prior version.

 

Ask around. NOT IN THIS THREAD.

 

Obligator RTFM Notice: This is why you use TM or better yet, go grab a few USB sticks and keep a few iterations of old version on hand. If you can't be bothered to do that, then you have to live with the consequences.

 

A better alternative is to fix what is causing the issue. Apple fixed USB 2.0 device drops in 10.5.6 and that may have inadvertently borked the way Hackintoshes work with USB 2.0.

 

This is unfortunately pretty normal. My Pro Wifi has some and so did my Mac mini and even my Mac Pro (2013). The MP was pretty bad AFAIR. If you hear it it's likely because your environment is really quiet. If you don't it's likely that your hearing misses it or it's drowned out by other noise. IMO every board I've had in a desktop class Mac or PC has had it to some degree. Notebooks and mobile devices I have never heard them (not saying they don't also have it, but it could be their chassis construction hides it.

 

Totally normal and if you manage to get an RTM over that, I would be impressed. More impressed if you could show me the new one doesn't also have it.

 

You can search on the net for remedies, but it's just how transistors work TBH.

 

like I said in my last post bro I have done many a master build and none have had coil whine at all. nor did my z390 pro, nor does my Z490 and x570 master and nor does my Z390 Designare.

 

I always hear that ugly whine sound via Nvidia GPUs though. yuck

 

Edited July 22, 2020 by AudioGod

[Tiem]

Just turn your music up 

[AudioGod]

14 minutes ago, Tiem said:

This is unfortunately pretty normal. My Pro Wifi has some and so did my Mac mini and even my Mac Pro (2013). The MP was pretty bad AFAIR. If you hear it it's likely because your environment is really quiet. If you don't it's likely that your hearing misses it

 

You do know I'm a full on Audio Engineer right? (hence the name AudioGod)

I would hear a Fly fart in a sand storm my friend. I have super ears don't you know.... 

Edited July 22, 2020 by AudioGod

[pkdesign]

15 hours ago, Tiem said:

You really shouldn't need to do this today. Especially with OC. But even Clover has now pretty much solved this problem.

That is what I thought. I thought this KASLR mess was sorted out with OcQuirks. Ugh.

[jpphd]

Hi there!

May I upgrade from 10.15.5 to 10.15.6 without issues or there´s gonna be a 10.15.6 ready EFI release?

[AudioGod]

1 minute ago, jpphd said:

Hi there!

May I upgrade from 10.15.5 to 10.15.6 without issues or there´s gonna be a 10.15.6 ready EFI release?

It should be fine, I have new EFIs but they are not ready yet as both OC and Clover are trying to get it all sorted for BIG SUR, the day OC 0.6.0 releases I will also post new EFIs at the same time.

This is why there hasn’t been a July EFI release from me yet. Soon come on that front.

[Tiem]

2 hours ago, pkdesign said:

That is what I thought. I thought this KASLR mess was sorted out with OcQuirks. Ugh.

I built mine around Oct 2019. Back then, I remembering rebooting was a {censored} shoot. 50 reboots no problemo. Then on the 51st, fail. Even with slide=0. It was a nightmare.

 

But since OC and even with OcQuirks I never really had issues. With that said, Clover was still twitchy. I have never had a single issue with OC with KASLR addressing.

 

Then again I’ve see lots of misinformation around this to this day. I saw someone post on Reddit a success running OC where they had slide in their boot args. I asked why and lots responded that some boards need it. Especially ours (z390). So yeah, lots of ignorance. Makes things hard to solve.

[pkdesign]

I think I may have found the issue with the boot crashing.

 

According to the OcQuicks guide on GitHub, the SetupVirtualMap needs to be set to <true>. Currently in @AudioGod EFI (both Clover and OpenCore) it is set to <false>. Since I have set this to <true>, I have not had any boot crashes. It's only been a day and a few boots but it seems more stable now.

 

EDIT 2020-07-27

Well, I was wrong. Still getting boot crashes.

Edited July 27, 2020 by pkdesign

[AudioGod]

9 minutes ago, pkdesign said:

I think I may have found the issue with the boot crashing.

 

According to the OcQuicks guide on GitHub, the SetupVirtualMap needs to be set to <true>. Currently in @AudioGod EFI (both Clover and OpenCore) it is set to <false>. Since I have set this to <true>, I have not had any boot crashes. It's only been a day and a few boots but it seems more stable now.

non nononononono its set to false for a reason and was instructed to do it the way I did by VIT of all people. I think you might find its a coincidence buddy. 

 

My BOOTER Quirks are set up like they are for continuity from os too os again specifically done like that while I was helping VIT test a while ago. I promise you its right,

Whats the problem anyway?

you getting the odd boot failure?

if so that could be due to one of two reasons.

1. bouncing from windows to macOS using windows 1909 with the recovery partition infront of the EFI Partition or

2. 19,1, the igpu and the nvram not playing happy.

 

Edited July 24, 2020 by AudioGod

[AudioGod]

@pkdesign I moved back to smbios 1,1 around a month ago now and haven't seen a single boot failure since, plus I fresh booted windows 10 v2004 and they have sorted out the partitions and put the recovery and EFI partitions in the correct order at long last. Im sick of 19,1 its a pain in the behind.

[rob1980]

39 minutes ago, AudioGod said:

@pkdesign I moved back to smbios 1,1 around a month ago now and haven't seen a single boot failure since, plus I fresh booted windows 10 v2004 and they have sorted out the partitions and put the recovery and EFI partitions in the correct order at long last. Im sick of 19,1 its a pain in the behind.

Potential silly question @AudioGod

 

Whats the advantage of using 1,1 over 19,1? 

Thanks

[AudioGod]

Just now, rob1980 said:

Potential silly question @AudioGod

 

Whats the advantage of using 1,1 over 19,1? 

Thanks

It’s a lot more stable and mean a lot more stable, drm works with no shiki value, the igpu is disabled in the bios freeing up a massive load of space in the nvram so you get no boot failures on start up. All gpus bar the lower end Polaris preform better.

 

Only real downside to 1,1 is Sidecar does not work but I personally don’t use Sidecar anyway so it’s no biggie to me on that front.

[Tiem]

23 minutes ago, rob1980 said:

Whats the advantage of using 1,1 over 19,1? 

From my experience and based mostly on testing in FCPX, I have found performance to be the following: MP7,1 > iMP1,1 > iM19,1.

 

7,1 is the fastest and cleanest, especially when it comes to scrubbing. 1,1 is close but stutters more scrubbing. Both generate the same speed on export using x264. But both do not support Sidecar. 19,1 does but is the slowest of the bunch. And I mean noticeably slower. I run a skeleton system (don't even have SATA enabled) so YMMV. These are my own tests results. If you have a Polaris GPU you may not see this. All these tests were done using the equipment in my sig.