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

hansik
hansik
Posted
Posted

Hi. I use 1 screen 144 hz with DP, and one 60 hz hdmi. Like a lot of people on pc i have a problem during the boot. the system seems to give 144hz to the 60 screen 50 % time and the 60 screen start to blink. I tried to fix it with Switch screen x but it didnt work. if anyone have a solution. 

Olion
Olion
Posted
Posted (edited)

Hello everyone, today I updated clover to v.5104 and added:
- NTFS driver
- USBInjectAll.kext
- AirportBrcmFixup.kext
- RTCMemoryFixup.kext
Also updated for currenc macOS version:
- IntelMausi.kext

Right now all works correct, my problems resolved.

One moment: First minute after launch my graphics have some freezes, after that all is ok.
Any ideas?

 

Edited by Olion
  • Confused 1
AudioGod
AudioGod
Posted
  • Author
Posted (edited)
35 minutes ago, Olion said:

Hello everyone, today I updated clover to v.5104 and added:
- NTFS driver
- USBInjectAll.kext
- AirportBrcmFixup.kext
- RTCMemoryFixup.kext
Also updated for currenc macOS version:
- IntelMausi.kext

Right now all works correct, my problems resolved.

One moment: First minute after launch my graphics have some freezes, after that all is ok.
Any ideas?

 

Please don’t post an Efi of yours and mark it like it’s one of mine.

you have made many strange changes that are incorrect so I would be grateful if you could remove it please from your post.
thank you

Edited by AudioGod
  • Like 1
Tiem
Tiem
Posted
Posted
8 hours ago, Olion said:

Hello everyone, today I updated clover to v.5104 and added:
- NTFS driver
- USBInjectAll.kext
- AirportBrcmFixup.kext
- RTCMemoryFixup.kext
Also updated for currenc macOS version:
- IntelMausi.kext

Right now all works correct, my problems resolved.

Maybe useful to someone: HD630 Z390 Pro F12d EFI 260220.zip

One moment: First minute after launch my graphics have some freezes, after that all is ok.
Any ideas?

 

RTCMemoryFixup.kext is used for CMOS debugging. USBInjectAll.kext is a temporary extension used to aid in mapping USB ports.

WizeMan
WizeMan
Posted
Posted
On 2/24/2020 at 11:49 PM, pkdesign said:

I've been trying to do this as well.

 

So you find that dw=3 let's your system sleep properly AND external drives do not complain about being ejected?

 

Right now, I took out all arguments (so I assume dw=3 default) and sleep works ONCE, but not again. And drive still complain about being ejected.

 

Granted, I am on the Pro Wifi board.

 

So unfortunately after a week or so, my Time Machine USB drive started being force ejected again.

I have updated my initial message a couple of pages back. I did not have this issue for about a week using no darkwake value (thus the kernel setting the default 3) but the morning of the day before yesterday I came to my office, woke up my hack and saw several force eject messages. Then came back yesterday morning, the same. Last night I resorted back to darkwake = 0 and this morning no force eject messages. Will definitely further check it as it seems super random.

Pieroman
Pieroman
Posted
Posted (edited)
On 2/25/2020 at 12:29 AM, Cass67 said:

I gave up with iGPU on 19,1 and just disabled the thing.. OC was running solid with it enabled until i upgraded to 0.5.6 and at which point it stopped booting with the memory allocation errors.  Even then it seems to be on a hairline as to what can be enabled feature wise with this disabled or not.  Simply enabling the PollAppleHotKeys feature so i could boot with -v or whatever by using keys was enough to tip it over the edge and fail with memory allocation error.. No amount of wiping bios by removing battery would fix it ... It would boot 1 in 10 or 20 times or what seemed like never.  Still have to test removing all the stuff in the OC.plist that i have thats set to default values as per the config guide to see if this makes a difference to what features can be added.

 

Have you tried with the quirks DevirtualiseMmio set to true and ForceExitBootServices to false ? This made it working for me (so far !) with the iGPU and 19,1. But I'm on Clover (since we are using OCquirks the same options should be there in OC)...

Edited by Pieroman
AudioGod
AudioGod
Posted
  • Author
Posted (edited)
2 hours ago, WizeMan said:

 

So unfortunately after a week or so, my Time Machine USB drive started being force ejected again.

I have updated my initial message a couple of pages back. I did not have this issue for about a week using no darkwake value (thus the kernel setting the default 3) but the morning of the day before yesterday I came to my office, woke up my hack and saw several force eject messages. Then came back yesterday morning, the same. Last night I resorted back to darkwake = 0 and this morning no force eject messages. Will definitely further check it as it seems super random.


@WizeMan Give jettison a try bro,

https://www.stclairsoft.com/Jettison/


Or do what I did ages ago and forgot about it and it’s why my usb never ejects i believe.


To fix "disk did not eject properly" message use  fixUSB.sh  install open terminal:

1- Copy and paste :

// command will download the latest fixUSB.sh ( if link does not work, then follow alternative instructions at bottom) 

git clone https://github.com/syscl/Fix-usb-sleep

Enter

 

2- Copy and paste: 

chmod +x ~/Fix-usb-sleep/fixUSB.sh

Enter

 

3- Copy and paste: 


cd ./Fix-usb-sleep
./fixusb.sh  

Enter

Edited by AudioGod
  • Like 1
WizeMan
WizeMan
Posted
Posted
3 hours ago, AudioGod said:


@WizeMan Give jettison a try bro,

https://www.stclairsoft.com/Jettison/


Or do what I did ages ago and forgot about it and it’s why my usb never ejects i believe.


To fix "disk did not eject properly" message use  fixUSB.sh  install open terminal:

1- Copy and paste :

// command will download the latest fixUSB.sh ( if link does not work, then follow alternative instructions at bottom) 


git clone https://github.com/syscl/Fix-usb-sleep

Enter

 

2- Copy and paste: 


chmod +x ~/Fix-usb-sleep/fixUSB.sh

Enter

 

3- Copy and paste: 



cd ./Fix-usb-sleep
./fixusb.sh  

Enter

 

Thanks mate! I'll keep experimenting with darkwake=0 which doesn't seem to bring any force ejection issues up until now. In case I see that the problem persists I 'll use fixUSB script.

AudioGod
AudioGod
Posted
  • Author
Posted
4 minutes ago, WizeMan said:

 

Thanks mate! I'll keep experimenting with darkwake=0 which doesn't seem to bring any force ejection issues up until now. In case I see that the problem persists I 'll use fixUSB script.

 

I use darkwake=0 plus the fixUSb script and I haven’t had a single force eject problem ever and I just forgot about it. That was like 6 months ago or something like that. Used darkwake=8 for a while and moved back to zero but again I have never ever had the force eject issue so I would recommend it personally. :thumbsup_anim:

  • Thanks 1
texem
texem
Posted
Posted

@Wizeman 

The eject problem exists on some real Mac's as well . It's the power definition which can be done via USBX , the current level for sleep is the relevant part.

With my "SSDT only OC" version it should be fixed. Since then, I could remove Jettison.

 

AudioGod
AudioGod
Posted
  • Author
Posted (edited)
32 minutes ago, texem said:

@Wizeman 

The eject problem exists on some real Mac's as well . It's the power definition which can be done via USBX , the current level for sleep is the relevant part.

With my "SSDT only OC" version it should be fixed. Since then, I could remove Jettison.

 

Problem with USBX is it can leave your external usb rgb lights on once sleep hits as happens to me a lot with my Corsair keyboard or mouse but your right it does cure eject too. 

Edited by AudioGod
pkdesign
pkdesign
Posted
Posted
3 hours ago, WizeMan said:

 

Thanks mate! I'll keep experimenting with darkwake=0 which doesn't seem to bring any force ejection issues up until now. In case I see that the problem persists I 'll use fixUSB script.

Love to know if it works for you. It didn’t for me.

 

I tried Jettison and it was nice, but I think you have to eject the drive manually and sleep. I didn’t see it work automatically. Maybe I'll try again. It might be darkwake depend as well.

2 hours ago, texem said:

@Wizeman 

The eject problem exists on some real Mac's as well . It's the power definition which can be done via USBX , the current level for sleep is the relevant part.

With my "SSDT only OC" version it should be fixed. Since then, I could remove Jettison.

 

What and/or where is this "SSDT only OC" I'm a bit confused about USBX?

AudioGod
AudioGod
Posted
  • Author
Posted (edited)
17 minutes ago, pkdesign said:

What and/or where is this "SSDT only OC" I'm a bit confused about USBX?

 

Its not posted or released by any of us yet and is a work in progress so too speak.

It might go live when 0.5.6 is officially released and if it can pass the @larabee test under 19,1. ATM its only reliable on a Z390 Pro with the igpu disabled.

You can request a copy from @texem as I only have a working copy for the Z390 Master that works perfectly under 19,1 with igpu enabled but that's a whole different bios and story and thread. :hysterical:

 

 

Edited by AudioGod
texem
texem
Posted
Posted
39 minutes ago, pkdesign said:

I tried Jettison and it was nice, but I think you have to eject the drive manually and sleep. I didn’t see it work automatically.

 

it's fully automatic, you can configure what to eject and remount on sleep/wake.

 

pkdesign
pkdesign
Posted
Posted
2 hours ago, AudioGod said:

CLOVER DRIVER UPDATE 26/02/20

 

OcQuirks Revision 16 & FwRunTimeServices Latest Versions.

 

OcQuirks R16.zip

Are we using the plist file with our setup? Or do we just delete it.

Olion
Olion
Posted
Posted (edited)
20 hours ago, AudioGod said:

Please don’t post an Efi of yours and mark it like it’s one of mine.

you have made many strange changes that are incorrect so I would be grateful if you could remove it please from your post.
thank you

No problems, done.

Thanks anyway.

 

Edited by Olion
  • Thanks 1
AudioGod
AudioGod
Posted
  • Author
Posted (edited)
36 minutes ago, pkdesign said:

Are we using the plist file with our setup? Or do we just delete it.

I don’t use it with the master or the pro setups but it’s been reported on here that it helps so I left it in there. If your having troubles now and again using 19,1 then add the plist and see if it helps.

if it does then just let me know. :thumbsup_anim:
 

50 minutes ago, Tiem said:

1725746116_ScreenShot2020-02-26at11_06_37AM.thumb.png.2097a4abae0153edc23169381561d443.png

Latest beta running on Clover. All good.

Any sign of any performance improvements with your 5700xt using the latest beta?  

Edited by AudioGod
Olion
Olion
Posted
Posted
13 hours ago, Tiem said:

RTCMemoryFixup.kext is used for CMOS debugging. USBInjectAll.kext is a temporary extension used to aid in mapping USB ports.

But, without USBInjectAll.kext my USB ports don't work.

AudioGod
AudioGod
Posted
  • Author
Posted (edited)
14 minutes ago, Olion said:

But, without USBInjectAll.kext my USB ports don't work.

Did you remove the dsdt and or ssdt from my original Efi when you tried to use it?
or did you add any additional usb info in any way shape or form when you first tried to use it?
 

34 minutes ago, Tiem said:

@AudioGod Nope. They are definitely working on the drivers but it's still falling well short of what the card is capable of doing.

I hope so, the only reason it doesn’t crash for us is because we use smbios 19,1.. Try using a 5700xt under macpro1,1 or better yet with a real Mac of any description and put the gpu under heavy load for a prolonged amount of time and watch what happens...lol...it’s not good at all.

on a hack under 19,1 with the igpu enabled fixes it but it’s not really fixed it’s just hiding the problem.

oh well at least it works for us I guess.

fingers crossed they sort it out soon as I would like to go back to smbios 1,1 for myself and disable my igpu. (Maybe one day) :) 

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