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

saCULar
saCULar
Posted
Posted
3 hours ago, panosru said:

@antuneddu Yassu!! :D What I noticed is that every time I'm applying a modification in SSDT-6, the length that is mentioned at the header of the file is changed, basically from what I understand it works like a hash of some sort, therefore it fluctuates upon alterations. After I disabled the ports I don't need by putting Return (GUPC (Zero, Zero)), I'm copying the new length and I paste it inside the OC config, but so far, Hackintool is showing all the ports of my machine, but as you can see from the screenshots I posted, half of my devices are not recognised (I notice that all my USB3 devices are not recognised).

 

I have the feeling that I'm messing up the oem acpi, I might need to get it via UEFI shell... If not, I'm attaching here my OC config and my SSDT-6.aml file, just in case I messed something up, maybe you or someone else could take a quick look and I would really prefer to be informed of what should I correct so I will do it myself instead of getting a fixed file :D

 

Thanks a lot!

 

UPDATE:

I dumped DSDT from UEFI shell, and I saw that the table length is set to 265165, I changed the value in OC config and I will reboot one last time before I go to bed because it is already 05:22 and I need some sleep. Also, why the fck it takes 6 minutes and 27 seconds to boot into Monterey? W T F ?! I kind of regret that I upgraded, I should've stayed with Bug Sur.

SSDT-6.aml 9.82 kB · 1 download config.plist 37.28 kB · 0 downloads

On my i9 the boot spends 20seconds sitting after the bootroot section, and then about 60 secs after complaining about a 60 sec timeout on the SMBIOS identity.  Way longer boot cycle than before, but once booted just as snappy as Big Sur

panosru
panosru
Posted
Posted

@saCULar, still, that is a lot 😕 I'm on i7 9700K, literally, it takes ~6.5 minutes to boot into OS (stopwatch starting counting from OpenCore screen). When is loaded, indeed it feels even snappier than Big Sur, but, damn, it takes too long to boot :( I guess that is a Hackintosh issue, from what I read that behaviour isn't happening  on a Apple hardware.

 

@antuneddu, it seems that midnight is only for movies and sex, doing complex stuff isn't great. I read the Italian forum again and I got it working. I was doing it wrong... I loaded the debug version of OC and enabled SysReport under Misc -> Debug, then I rebooted and I grabbed the SysReport folder, after checking it out, I found that for me, the usb ports were defined at SSDT-7.aml, I also copied the table length of the original SSDT-7.aml since we need it for OC config so it will be dropped, otherwise our custom SSDT-*.aml file won't be loaded (which was happening to me). Now that I got it right, it is a straight forward solution :D In terms of performance, of-course, nothing changed, but I'm not yet sure if the stability is affected, since from what I read, ACPI for that kind of stuff is the "native" way to go.

 

For my particular case I completely disabled the following ports: HS01, HS02, HS04, HS06, HS07, HS08, HS12, HS14, USR1, USR2 (I don't know what USR ports are, they were disabled by default anyways), SS01, SS02, SS06

 

The following ports are enabled (total: 13 ports): HS03, HS05, HS09, HS10, HS11, HS13, SS03, SS04, SS05, SS07, SS08, SS09, SS10

 

Basically, I disabled all the unnecessary ports and i left only the ones I use. In the SS05/HS05 port, I left the HS05 port enabled because I'm using DAS 4 Professional Keyboard for Mac and it has two USB3 ports available, one of the two is occupied by my ASUS BT400, and I noticed that because the bluetooth dongle is next to my mouse, since physically my mouse is always next to my keyboard, I neither have any interference by other 2.4GHz signals, nor any lagging. The dongle is a USB2 device, therefore I had to enable HS05 also.

 

Same principle applies for SS03, I have a TP-Link USB3 hub connected on that port that also has a couple of USB2 devices, therefore I also enabled the HS03 port.


I didn't enabled HS04/08/07 ports because I only have USB3 devices connected on them, and I also disabled completely the SS/HS06 ports since I'm not using the type-c port at all. I left HS/SS09 and 10 enabled so I can have two USB3 ports available at the front of my PC with backwards compatibility for USB2 devices.

 

Everything is working like a charm now (not that it didn't worked with USBMap.kext file).

SSDT-7.aml

  • Like 3
panosru
panosru
Posted
Posted (edited)

About the very slow boot, it seems that it is a known issue and affects a few disks, including Samsung 970 EVO Plus (disk6)... I guess there is nothing to do about it for the time being, maybe Acidanthera will push an update that will resolve the issue.

 

It seems to be an issue with trimming, I run log show --last boot | grep "trims took" and I got the following result:

  

2021-10-29 19:28:07.066689+0300 0x74       Default     0x0                  0      0    kernel: (apfs) spaceman_scan_free_blocks:3153: disk6 scan took 351.509650 s, trims took 351.074117 s
2021-10-29 19:28:25.106322+0300 0xb94      Default     0x0                  0      0    kernel: (apfs) spaceman_scan_free_blocks:3153: disk5 scan took 9.422977 s, trims took 9.280218 s

~6 minutes... 

 

Running sudo trimforce enable also isn't doing anything, after reboot:

  

$ log show --last boot | grep "trims took"
2021-10-29 21:12:12.044569+0300 0x3e6      Default     0x0                  0      0    kernel: (apfs) spaceman_scan_free_blocks:3153: disk6 scan took 346.191712 s, trims took 345.812004 s
2021-10-29 21:12:26.436360+0300 0xbb4      Default     0x0                  0      0    kernel: (apfs) spaceman_scan_free_blocks:3153: disk7 scan took 5.357154 s, trims took 4.866876 s
2021-10-29 21:12:30.249208+0300 0xbb0      Default     0x0                  0      0    kernel: (apfs) spaceman_scan_free_blocks:3153: disk5 scan took 9.456542 s, trims took 9.305414 s

 

 

PS: Sorry for the many and lengthy posts in the last couple of days...

Edited by panosru
pkdesign
pkdesign
Posted
Posted

Updated to Monterey yesterday and it went very, very smoothly. Took about 45 minutes. There were a bunch of apps that needed to be updated; most importantly Little Snitch and Carbon Copy Cloner. My boot time is faster than it was with Mojave, about 30-40 seconds. Found the same in my Dell laptop. WiFi and bluetooth just worked. I have the YOUBO WiFi card which uses the BCM94360CD chip.

 

The biggest surprise was just how much faster and snappier my whole system is. I couldn't be happier. 

  • Like 3
dsynos80
dsynos80
Posted
Posted
44 minutes ago, pkdesign said:

Updated to Monterey yesterday and it went very, very smoothly. Took about 45 minutes. There were a bunch of apps that needed to be updated; most importantly Little Snitch and Carbon Copy Cloner. My boot time is faster than it was with Mojave, about 30-40 seconds. Found the same in my Dell laptop. WiFi and bluetooth just worked. I have the YOUBO WiFi card which uses the BCM94360CD chip.

 

The biggest surprise was just how much faster and snappier my whole system is. I couldn't be happier. 

Still on Catalina, thinking about it. Any more details? You used OC 0.75? You have RBaR enabled?

rob1980
rob1980
Posted
Posted

Updated to 0.7.5 without issue.

 

For those of you who rely on others to update your EFI you might want to give OCAT a try

 https://github.com/ic005k/QtOpenCoreConfig/releases 

 

There's a great guide here on Insanely and I've been using it for the previous 3 or 4 releases without issue. 

 

In short, (copied from guide and I take no credit! ). 

 

1. Updating OpenCore, Drivers, Kexts  and config.plist with OCAT

  • Run OCAT and check for program updates if you haven't already (globe icon)!
  • Mount ESP (Hard Disk Icon)
  • BACKUP YOUR CURRENT EFI FOLDER ON A FAT32 FORMATTED USB STICK!
  • Open the config.plist
  • Next, hit "Save" (the Floppy Icon). This will automatically update the config.plist to the latest form with the latest feature-set.
  • Click "Synchronize OC main program" (aka the Recycle Button). This will update OpenCore, Drivers, Kexts and Resources (if selected) present in your EFI.

2. Validate and Test

  • Open the config again in OCAT and click on the green check mark icon to validate it. Everything should be fine. If it is not, compare your config.plist with the sample.plist in included in the OpenCore Package to fix the errors mentioned in the log.
  • Fix Errors if there any. Once they are fixed, save the config and reboot

DONE! Congratulations, you successfully updated your OpenCore EFI to the latest version!

 

 

 

  • Like 1
  • Thanks 1
pkdesign
pkdesign
Posted
Posted (edited)
3 hours ago, dsynos80 said:

Still on Catalina, thinking about it. Any more details? You used OC 0.75? You have RBaR enabled?

 

I always use the release version of OC. I always assume Monday. I used 0.7.4. Updates have been such a breeze lately. I will do that tomorrow.

 

Assume that a lot of your apps will need to be updated but that was it for me. Remember that I was coming from Mojave though. It was really as simple as allowing the update to happen. I only had to make one edit to my config.plist and that was the UEFI>APFS MinDate and MinVersion to 0. Mine was set to Mojave. That is the only change I made to my plist.

 

Still can’t set SecureBootModel to Default. I have to set it to Disabled in order to boot.

 

No settings for RBaR, I understand that is only for 5700XT cards. I have RX570.

 

EDIT:

I went ahead and used OCAT to update to 0.7.5. I normally do not like to use any tools because I want to see exactly what I am changing but this worked quite well.

 

Looks like the only two additions to config.plist:

 

Booter>Quirks>ResizeAppleGpuBars -1

UEFI>Quirks>ResizeGpuVars -1

 

(those values are for my setup)

 

All is well and no issues booting or anything. :thumbsup_anim:

Edited by pkdesign
  • Like 1
  • Thanks 1
saCULar
saCULar
Posted
Posted

pkdesign:  did you do a full install to monterey or software update from mojave?  I have a very similar system and updated via software update from Big Sur - but have much slower boot - Big Sur boots similar to your quoted time.

 

pkdesign
pkdesign
Posted
Posted
30 minutes ago, saCULar said:

pkdesign:  did you do a full install to monterey or software update from mojave?  I have a very similar system and updated via software update from Big Sur - but have much slower boot - Big Sur boots similar to your quoted time.

 

Software update from Mojave to Monterey. My SSD is an ADATA SX8200 Pro.

  • Like 1
rob1980
rob1980
Posted
Posted
5 hours ago, pkdesign said:

 

I always use the release version of OC. I always assume Monday. I used 0.7.4. Updates have been such a breeze lately. I will do that tomorrow.

 

Assume that a lot of your apps will need to be updated but that was it for me. Remember that I was coming from Mojave though. It was really as simple as allowing the update to happen. I only had to make one edit to my config.plist and that was the UEFI>APFS MinDate and MinVersion to 0. Mine was set to Mojave. That is the only change I made to my plist.

 

Still can’t set SecureBootModel to Default. I have to set it to Disabled in order to boot.

 

No settings for RBaR, I understand that is only for 5700XT cards. I have RX570.

 

EDIT:

I went ahead and used OCAT to update to 0.7.5. I normally do not like to use any tools because I want to see exactly what I am changing but this worked quite well.

 

Looks like the only two additions to config.plist:

 

Booter>Quirks>ResizeAppleGpuBars -1

UEFI>Quirks>ResizeGpuVars -1

 

(those values are for my setup)

 

All is well and no issues booting or anything. :thumbsup_anim:

I done the same some time ago, I used the tool to see what changes it made, and I used MELD for comparisons between that and one I changed manually as well as one provided by AG. OCAT I believe is the only tool suggested by OC in their guide )happy to be corrected if I'm wrong) 

 

Interested to hear the benefits of RBaR if any using the 5700XT as I have that card, and what is involved / where I can read up on it if you know?

 

Thanks

  • Like 1
panosru
panosru
Posted
Posted (edited)

Yeap, Samsung SSD has an issue so far, it takes me about 7 minutes to boot, once booted everything is fine, but that boot time is very annoying... Also, for my particular case, I had to set ResizeAppleGpuBars to 0, otherwise I can't boot to my system, it stuck on Apple logo.

Edited by panosru
DoYouBelieveInMiracles
DoYouBelieveInMiracles
Posted
Posted (edited)

@panosru I read your post about fixing Bluetooth on Monterrey and everything went well. Unfortunately though, while BT works again and since I rely on USB dongles for both BT & Wifi, my wifi dongle is acting up. Slow speeds, losing connection etc.

Did this happen to you as well? I might revert to the previous configuration. [TP-LINK Archer T2U Plus]

 

Also, since I've had it with this piece of malakia antenna, can someone suggest a relatively cheap USB wifi dongle that works well with Hackintosh?

Edited by unknownharris
panosru
panosru
Posted
Posted

@unknownharris For me, after putting the v2.6.1 BlueToolFixup kext, my dongle is working fine again. I'm not using a USB dongle for WiFi, only BT.

saCULar
saCULar
Posted
Posted (edited)
21 hours ago, panosru said:

Yeap, Samsung SSD has an issue so far, it takes me about 7 minutes to boot, once booted everything is fine, but that boot time is very annoying... Also, for my particular case, I had to set ResizeAppleGpuBars to 0, otherwise I can't boot to my system, it stuck on Apple logo.

I installed Monterey onto my HP x360 elitebook - long install but now it boots up in approx 40secs.... however bluetooth is lost - even with BlueToolFixup 2.6.1 😞

 

Always something!   Ahem, now I have re-checked by config.plist with OCAT its seems there were a few errors...  Now bluetooth works properly again (internal Intel bluetooth)

 

Yassou

Edited by saCULar
Corrections
  • Like 2
Blesh
Blesh
Posted
Posted

 

Do you know guys, why my Bluetooth is greyed out and how to fix that? Everything works and I can connect to new devices. There is no issue besides the greyed-out part.

What I have done so far:

  • NVME reset
  • bluetoothaudio reset (via script, via terminal and another lot of commands)

 

1572703006_Screenshot2021-11-02at13_49_52.png.fcb2b86a6fced8b147e216f6e9789a0c.png

 

panosru
panosru
Posted
Posted

@Blesh, for me it seems to be working fine:

 

image.thumb.png.f7a6b4bca68456e7ac19f0c47ad5c02b.png

 

My bluetooth is also enabled:

 

image.png.82c7a88c0e3764a2fcf575c947a00539.png

 

Is your bluetooth device available?

 

image.thumb.png.50ef668d12608f561c98fde0bbd48c24.png

pkdesign
pkdesign
Posted
Posted
11 hours ago, saCULar said:

Always something!   Ahem, now I have re-checked by config.plist with OCAT its seems there were a few errors...  Now bluetooth works properly again (internal Intel bluetooth)

 

Did you spell it in config BlueToothFixup a hundred times like I did? :hysterical:

  • Like 1
  • Haha 1
map002
map002
Posted
Posted

Quick Question...

 

I seem to remember that Sidecar only worked if you used the 19,1 system ID.  Is this correct?  Any answers and corrections appreciated. 🙂

hackinhacker
hackinhacker
Posted
Posted (edited)

My Catalina hackintosh went into never-ending boot loop after I applied Security Update 2021-005 or 2021-06 about a month ago.  As I can see, it's at the final stage of update then it just keeps on rebooting.

 

I do not remember the OC version which I believe it to be 0.6.x. What steps should I follow to make it alive again?

 

Your help would be much appreciated.  thank you

 

 

Intel i5 9600K 
Gigabyte AORUS Z390 PRO with F12k BIOS
iGPU Intel UHD 630
Samsung 970 EVO 1TB NVMe SSD / macOS Catalina

 

 

 

1.jpg

2.jpg

3.jpg

4.jpg

5.jpg

Edited by hackinhacker
hackinhacker
hackinhacker
Posted
Posted
2 hours ago, panosru said:

@hackinhacker try looking here. 

thanks for the link but my OC is believed to be later than the 0.5.8.  Are you suggesting that I should downgrade?  is there a way I can poke around at the DISK PICKER screen to troubleshoot?  Is there a way I can figure out which OC I'm on and is there a way I can check the boot load log?  I also see reset NVRAM option when I pushed SPACE button, is it safe to try and see?  Would it make my security patch update go corrupted?

 Share
Go to topic listing
×
×
  • Create New...