AudioGod's Aorus Z390 Master Patched DSDT EFI for Catalina Mini Guide and Discussion

[AudioGod]

12 minutes ago, M0r1d1n said:

 

@AudioGod @WizeMan I just confirmed mine is in PCIEX3 (the small slot above). Will move it down after I'm done with this post. BTW I'm using one of the cards from here, maybe even this one: https://www.osxwifi.com/product/pc-hackintosh-apple-broadcom-bcm94360cd-802-11-a-b-g-n-ac-with-bluetooth-4-0/

 

Can you tell me if I need to use the AirportBrcmFixup.kext or if I can just drop it?

Yep what @WizeMan said. Also you might find the card works better using the BrcmPatch kexts.

instructions for what kexts to use can be found on the front page of the link. 

 

https://github.com/acidanthera/BrcmPatchRAM/releases

[M0r1d1n]

31 minutes ago, AudioGod said:

Yep what @WizeMan said. Also you might find the card works better using the BrcmPatch kexts.

instructions for what kexts to use can be found on the front page of the link. 

 

Thanks guys @AudioGod @WizeMan. I actually have no idea which model I have, since I bought it in 2013-2014 or so. I recall it had the chips from a 2013 iMac though.

 

Anyway, I just moved it from PCIEX3 to PCIEX4 and sadly nothing changed at all, so it looks like I'll be disconnecting everything and seeing if any of that helps. I'm still thinking it's a monitor thing though. Or something in NVRAM conflicting with the 2 displays, because of that one situation where I accidentally rebooted from Win10 to macOS, resetting NVRAM along the way, without turning off my Alienware, and it worked great. It went back to stuttering after another reboot and I couldn't get it back to working 100% unfortunately (have been disconnecting and reconnecting displays over the weekend in many various configurations).

 

Just noticed, while typing this message...

 

I can't turn my Wi-Fi on now. Bluetooth works fine, but Wi-Fi will not turn on. Any ideas why that would be?

 

Edit:

 

Card not showing up under System Information in the PCI section now. But Bluetooth is working. WTH.

 

Edited June 29, 2020 by M0r1d1n

[AudioGod]

11 minutes ago, M0r1d1n said:

 

Thanks guys @AudioGod @WizeMan. I actually have no idea which model I have, since I bought it in 2013-2014 or so. I recall it had the chips from a 2013 iMac though.

 

Anyway, I just moved it from PCIEX3 to PCIEX4 and sadly nothing changed at all, so it looks like I'll be disconnecting everything and seeing if any of that helps. I'm still thinking it's a monitor thing though. Or something in NVRAM conflicting with the 2 displays, because of that one situation where I accidentally rebooted from Win10 to macOS, resetting NVRAM along the way, without turning off my Alienware, and it worked great. It went back to stuttering after another reboot and I couldn't get it back to working 100% unfortunately (have been disconnecting and reconnecting displays over the weekend in many various configurations).

 

Just noticed, while typing this message...

 

I can't turn my Wi-Fi on now. Bluetooth works fine, but Wi-Fi will not turn on. Any ideas why that would be?

 

Edit:

 

Card not showing up under System Information in the PCI section now. But Bluetooth is working. WTH.

 

clear your nvram bud and rebuild your permissions.

how many antennas does your combo card have?

Edited June 29, 2020 by AudioGod

[M0r1d1n]

46 minutes ago, AudioGod said:

clear your nvram bud and rebuild your permissions.

how many antennas does your combo card have?

Will try. AFAIK rebuilding permissions in only possible in Recovery Mode now. Is that what you had in mind? If not, then how?

 

4 antennas. 

[M0r1d1n]

panic(cpu 4 caller 0xffffff801bd4153a): "thread_invoke: preemption_level 1, possible cause: blocking while holding a spinlock, or within interrupt context"@/AppleInternal/BuildRoot/Library/Caches/com.apple.xbs/Sources/xnu/xnu-6153.121.2/osfmk/kern/sched_prim.c:2205
Backtrace (CPU 4), Frame : Return Address
0xffffffa775a3b730 : 0xffffff801bd1f5cd 
0xffffffa775a3b780 : 0xffffff801be58b05 
0xffffffa775a3b7c0 : 0xffffff801be4a68e 
0xffffffa775a3b810 : 0xffffff801bcc5a40 
0xffffffa775a3b830 : 0xffffff801bd1ec97 
0xffffffa775a3b930 : 0xffffff801bd1f087 
0xffffffa775a3b980 : 0xffffff801c4c27cc 
0xffffffa775a3b9f0 : 0xffffff801bd4153a 
0xffffffa775a3ba60 : 0xffffff801bd3fc2f 
0xffffffa775a3bab0 : 0xffffff801bd30800 
0xffffffa775a3baf0 : 0xffffff801bd7717d 
0xffffffa775a3bc20 : 0xffffff801be39aef 
0xffffffa775a3bc70 : 0xffffff801bcc5a40 
0xffffffa775a3bc90 : 0xffffff7fa1401d01 
0xffffffa775a3bd80 : 0xffffff7fa140078e 
0xffffffa775a3bda0 : 0xffffff7fa13fe4be 
0xffffffa775a3bdf0 : 0xffffff7fa13fdb7f 
0xffffffa775a3be20 : 0xffffff801c4333e9 
0xffffffa775a3be90 : 0xffffff801c433309 
0xffffffa775a3bec0 : 0xffffff801bd61565 
0xffffffa775a3bf40 : 0xffffff801bd61091 
0xffffffa775a3bfa0 : 0xffffff801bcc513e 
      Kernel Extensions in backtrace:
         ru.joedm.SMCSuperIO(1.1.4)[3EBEC0A6-5D45-3034-A52E-8B63A6FABDA1]@0xffffff7fa13fc000->0xffffff7fa140bfff
            dependency: as.vit9696.Lilu(1.4.5)[E42CE60E-EC0B-33AE-A513-5383B81BF165]@0xffffff7fa1387000
            dependency: as.vit9696.VirtualSMC(1.1.4)[9DD28544-2B81-33EB-B3F1-488D0FBB0947]@0xffffff7fa13b0000
            dependency: com.apple.iokit.IOACPIFamily(1.4)[0A7D7382-66FE-391B-9F93-97A996256C25]@0xffffff7f9c9b0000

BSD process name corresponding to current thread: kernel_task
Boot args: -v shikigva=80 darkwake=0 

 

@AudioGod @WizeMan

 

1. I have had loss of all USB + Bluetooth functionality 3 times in the past 2 days. 3rd time happened just now.

 

2. OSXWiFi card will not work in PCIEX4. It's not even recognized in BIOS (assuming it should be). I just put it back into PCIEX3 and it's working again.

 

3. I had a kernel panic after rebooting. Maybe useful in the future (pasted above).

 

4. Apple Watch still won't unlock screen saver.

 

These are the details of my WiFi card from Sys Info:

 

BCM4360 802.11ac Wireless Network Adapter:

  Name:	pci14e4,43a0
  Type:	Network controller
  Driver Installed:	Yes
  MSI:	Yes
  Bus:	PCI
  Slot:	Slot 4
  Vendor ID:	0x14e4
  Device ID:	0x43a0
  Subsystem Vendor ID:	0x106b
  Subsystem ID:	0x0111
  Revision ID:	0x0003
  Link Width:	x1
  Link Speed:	2.5 GT/s

So frustrating. Will try unplugging everything next.

 

5. Bluetooth audio is choppy. Just connected my AirPods Pro and the sound crackles and pops from time to time.

Edited June 29, 2020 by M0r1d1n

[M0r1d1n]

Tried to reset BT and now Handoff doesn’t work.

 

Got it working by logging out and back in to iCloud.

 

Also noticed that I couldn't switch Wi-Fi networks (I have 3 at home: 2.4GHz + 2x 5GHz) so I removed the Airportfix.kext and that started working again.

 

Good news and bad news. I'm pretty certain it's BT that's causing the lag issues though... unless something else is causing BT lag. Bah so irritating.

Edited June 29, 2020 by M0r1d1n

[WizeMan]

3 hours ago, M0r1d1n said:

panic(cpu 4 caller 0xffffff801bd4153a): "thread_invoke: preemption_level 1, possible cause: blocking while holding a spinlock, or within interrupt context"@/AppleInternal/BuildRoot/Library/Caches/com.apple.xbs/Sources/xnu/xnu-6153.121.2/osfmk/kern/sched_prim.c:2205
Backtrace (CPU 4), Frame : Return Address
0xffffffa775a3b730 : 0xffffff801bd1f5cd 
0xffffffa775a3b780 : 0xffffff801be58b05 
0xffffffa775a3b7c0 : 0xffffff801be4a68e 
0xffffffa775a3b810 : 0xffffff801bcc5a40 
0xffffffa775a3b830 : 0xffffff801bd1ec97 
0xffffffa775a3b930 : 0xffffff801bd1f087 
0xffffffa775a3b980 : 0xffffff801c4c27cc 
0xffffffa775a3b9f0 : 0xffffff801bd4153a 
0xffffffa775a3ba60 : 0xffffff801bd3fc2f 
0xffffffa775a3bab0 : 0xffffff801bd30800 
0xffffffa775a3baf0 : 0xffffff801bd7717d 
0xffffffa775a3bc20 : 0xffffff801be39aef 
0xffffffa775a3bc70 : 0xffffff801bcc5a40 
0xffffffa775a3bc90 : 0xffffff7fa1401d01 
0xffffffa775a3bd80 : 0xffffff7fa140078e 
0xffffffa775a3bda0 : 0xffffff7fa13fe4be 
0xffffffa775a3bdf0 : 0xffffff7fa13fdb7f 
0xffffffa775a3be20 : 0xffffff801c4333e9 
0xffffffa775a3be90 : 0xffffff801c433309 
0xffffffa775a3bec0 : 0xffffff801bd61565 
0xffffffa775a3bf40 : 0xffffff801bd61091 
0xffffffa775a3bfa0 : 0xffffff801bcc513e 
      Kernel Extensions in backtrace:
         ru.joedm.SMCSuperIO(1.1.4)[3EBEC0A6-5D45-3034-A52E-8B63A6FABDA1]@0xffffff7fa13fc000->0xffffff7fa140bfff
            dependency: as.vit9696.Lilu(1.4.5)[E42CE60E-EC0B-33AE-A513-5383B81BF165]@0xffffff7fa1387000
            dependency: as.vit9696.VirtualSMC(1.1.4)[9DD28544-2B81-33EB-B3F1-488D0FBB0947]@0xffffff7fa13b0000
            dependency: com.apple.iokit.IOACPIFamily(1.4)[0A7D7382-66FE-391B-9F93-97A996256C25]@0xffffff7f9c9b0000

BSD process name corresponding to current thread: kernel_task
Boot args: -v shikigva=80 darkwake=0 

 

@AudioGod @WizeMan

 

1. I have had loss of all USB + Bluetooth functionality 3 times in the past 2 days. 3rd time happened just now.

 

2. OSXWiFi card will not work in PCIEX4. It's not even recognized in BIOS (assuming it should be). I just put it back into PCIEX3 and it's working again.

 

3. I had a kernel panic after rebooting. Maybe useful in the future (pasted above).

 

4. Apple Watch still won't unlock screen saver.

 

These are the details of my WiFi card from Sys Info:

 

BCM4360 802.11ac Wireless Network Adapter:

  Name:	pci14e4,43a0
  Type:	Network controller
  Driver Installed:	Yes
  MSI:	Yes
  Bus:	PCI
  Slot:	Slot 4
  Vendor ID:	0x14e4
  Device ID:	0x43a0
  Subsystem Vendor ID:	0x106b
  Subsystem ID:	0x0111
  Revision ID:	0x0003
  Link Width:	x1
  Link Speed:	2.5 GT/s

So frustrating. Will try unplugging everything next.

 

5. Bluetooth audio is choppy. Just connected my AirPods Pro and the sound crackles and pops from time to time.

1. I’ve been facing this issue and the problem seems to be with the motherboard. @AudioGod has reported this to Gigabyte, maybe they’ll release some update for the UEFI BIOS that fixes it.

 

2. Weird. My Fenvi works best on that port.

 

4. You might need to logout and in from iCloud on the hack, you can also try to restore and re-pair the watch. My unlock with watch works.

 

5. I had some choppy audio issues but since I starting using the 5Ghz WiFi network instead of 2.4Ghz and also unlocked the MSR it was fixed.

[M0r1d1n]

@AudioGod @WizeMan @MattUK Guys, assuming you have a dGPU as your main display and iGPU used headless (iMac19,1), do you see both GPUs under Activity Monitor in the GPU History graph (Windows → GPU History) or just your dGPU?

 

At this point I'm even wondering if my iGPU is working properly, though Geekbench 5 says it is. I have currently allocated 32/128MB for it (was running some tests) but I'll return to 64/256MB tomorrow.

[M0r1d1n]

@AudioGod I just disconnected everything apart from 1 keyboard and 1 mouse. Wi-Fi card is removed.

 

No change.

 

I'm currently running 64/256MB of RAM for the iGPU. Do you think I could try to increase that? It seemed to get better when I went from 32/128 → 64/256.

 

At this point, not really sure what else I can try, apart from turning each and every option in the config.plist on/off.

[matt-uk]

@M0r1d1n

Whilst there are differences i still think we are experiencing the same issue and I am increasingly thinking it is iGPU related.

 

@AudioGod - some more info for troubleshooting - is there anyone else you can suggest that may have thoughts on this and be able to help as well?

 

I am not using Bluetooth mouse or keyboard - both of mine are connected with a Logitech Unifying Receiver so i don't think that is the issue.

 

I have been doing more testing myself. The issue (for me) doesn't seem to be Power Nap related as i thought but rather monitor related and Power Naps were turning off the monitor to create the issue.

 

Here is a troubleshooting workflow:

 

• Restart machine - energy saving settings turned off, screensaver turned on after 1 minute.
• Screen saver starts - everything is responsive, i can click in the password box to log on and the screensaver animation continues smoothy in the background.
• If i turn the monitors over to another input (my laptop is plugged in) then back to my main computer, the logon screen is laggy, when i click in the password box the screensaver animation stutters and the password characters take a few seconds to show up

 

The only thing that is different is that the monitors have turned off and on again - or more precisely changed inputs back and forth.

 

Is the screen saver animation handled buy the iGPU? Is there any reason why monitors turning off and on would impact the iGPU?

 

I currently have two monitors attached to a Vega 64 (for testing) with the relevant boot argument added as per direction on page 1.

 

This is literally the only issue i have with my hack. I am desperately hoping someone can come up with a clever diagnosis and solution.

 

Thanks all!

Edited June 30, 2020 by matt-uk

[M0r1d1n]

1 hour ago, matt-uk said:

Whilst there are differences i still think we are experiencing the same issue and I am increasingly thinking it is iGPU related.

 

Me too, especially since all the UI animations are handled by Metal and the iGPU, which is what is causing my problems. While the screen saver itself probably isn't, the password box is.

 

Any suggestions if I could increase RAM for iGPU for testing @AudioGod?

[M0r1d1n]

Coffee Lake iGPU users may also need igfxonln=1 in 10.15.4 and newer

Found in: https://dortania.github.io/OpenCore-Desktop-Guide/troubleshooting/troubleshooting.html#stuck-on-or-near-ioconsoleusers-gioscreenlockgiolockstate-3

[M0r1d1n]

Found another suggestion @matt-uk.

 

Delete /Library/Preferences/com.apple.windowserver.plist
Delete ~/Library/Preferences/ByHost/com.apple.windowserver*.plist

 

These files seem to contain the data of all the screens I have ever had connected to my Mac. But I doubt it will work, since I already tried a clean install of Catalina, which exhibits the same problems.

 

So this is either a Catalina issue, perhaps additionally only pertaining to some GPUs, or an Open Core config problem on our hardware.

 

@AudioGod Can you share which exact make and model of the 5700 XT you are currently using? I'll be upgrading soon and will consider getting the exact same one.

[matt-uk]

@M0r1d1n

 

In system monitor under the CPU tab i have a process called "loginwindow (Not Responding)"

Perhaps this is a process that is crashing that is leading to some of the issues on the login screen? Have you the same?

 

EDIT: No - doesn't seem to be related, process is responding again but still having issue.

 

Ref the GFX, i have tried with both a RX580 and a Vega 64 and it made no difference.

 

 

 

Edited June 30, 2020 by matt-uk

[M0r1d1n]

I'm also getting choppy normal audio — something's making everything lag slightly and I'm not sure how to diagnose it properly.

 

Edit:

 

Console is spamming this:

Jun 30 21:38:52 Jedha com.apple.xpc.launchd[1] (com.apple.mdworker.shared.09000000-0100-0000-0000-000000000000[14862]): Service exited due to SIGKILL | sent by mds[114]
Jun 30 21:39:02 Jedha com.apple.xpc.launchd[1] (com.apple.mdworker.shared.1D000000-0300-0000-0000-000000000000[14724]): Service exited due to SIGKILL | sent by mds[114]
Jun 30 21:39:03 Jedha com.apple.xpc.launchd[1] (com.apple.mdworker.shared.02000000-0300-0000-0000-000000000000[14487]): Service exited due to SIGKILL | sent by mds[114]
Jun 30 21:39:03 Jedha com.apple.xpc.launchd[1] (com.apple.mdworker.shared.15000000-0600-0000-0000-000000000000[14889]): Service exited due to SIGKILL | sent by mds[114]
Jun 30 21:39:03 Jedha com.apple.xpc.launchd[1] (com.apple.mdworker.shared.07000000-0200-0000-0000-000000000000[14888]): Service exited due to SIGKILL | sent by mds[114]
Jun 30 21:39:03 Jedha com.apple.xpc.launchd[1] (com.apple.mdworker.shared.0D000000-0200-0000-0000-000000000000[14681]): Service exited due to SIGKILL | sent by mds[114]
Jun 30 21:39:03 Jedha com.apple.xpc.launchd[1] (com.apple.mdworker.shared.1E000000-0100-0000-0000-000000000000[14881]): Service exited due to SIGKILL | sent by mds[114]
Jun 30 21:39:05 Jedha com.apple.xpc.launchd[1] (com.apple.mdworker.shared.1B000000-0100-0000-0000-000000000000[14890]): Service exited due to SIGKILL | sent by mds[114]
Jun 30 21:39:05 Jedha com.apple.xpc.launchd[1] (com.apple.mdworker.shared.0B000000-0500-0000-0000-000000000000[14892]): Service exited due to SIGKILL | sent by mds[114]
Jun 30 21:39:05 Jedha com.apple.xpc.launchd[1] (com.apple.mdworker.shared.0C000000-0600-0000-0000-000000000000[14893]): Service exited due to SIGKILL | sent by mds[114]
Jun 30 21:39:05 Jedha com.apple.xpc.launchd[1] (com.apple.mdworker.shared.0F000000-0600-0000-0000-000000000000[14891]): Service exited due to SIGKILL | sent by mds[114]
Jun 30 21:39:11 Jedha com.apple.xpc.launchd[1] (com.apple.mdworker.shared.04000000-0400-0000-0000-000000000000[14894]): Service exited due to SIGKILL | sent by mds[114]
Jun 30 21:39:42 Jedha com.apple.xpc.launchd[1] (com.apple.mdworker.shared.1A000000-0400-0000-0000-000000000000[14919]): Service exited due to SIGKILL | sent by mds[114]
Jun 30 21:40:29 Jedha com.apple.xpc.launchd[1] (com.apple.mdworker.shared.17000000-0100-0000-0000-000000000000[14923]): Service exited due to SIGKILL | sent by mds[114]
Jun 30 21:40:30 Jedha com.apple.xpc.launchd[1] (com.apple.mdworker.shared.11000000-0400-0000-0000-000000000000[14926]): Service exited due to SIGKILL | sent by mds[114]

A user over on MacRumors sorted this error by...

 

After reading your post, I opened the Console and found the same message repeated multiple times.
As I have SIP disabled, I unloaded /System/Library/LaunchAgents/com.apple.mdworker.shared.plist,
moved the plist in a backup folder and rebooted. The message is gone now. I have no idea what
mdworker.shared is supposed to do, but Spotlight seems to be working just fine.

Will read up more on the topic.

Edited June 30, 2020 by M0r1d1n

[M0r1d1n]

I have a few questions to @AudioGod and possible @WizeMan.

 

1. Please see attached screenshot — is this correct?

 

2. I would like to switch from iMac19,1 to iMacPro1,1 to test if the iGPU is causing issues in my setup. Do I just need to delete the relevant iGPU section from my config.plist or should I do something else? Disable iGPU in BIOS or is that not needed? Anything else? Will something break because my serial number is generated for an iMac19,1, not an iMacPro1,1?

 

3. Does anything change in the SSDTs between iMac19,1 and iMacPro1,1?

 

Any info greatly appreciated!

Edited July 1, 2020 by M0r1d1n

[M0r1d1n]

Just switched over to `iMacPro1,1` from `iMac19,1` and it's a little better, but still not 100% as good as on Mojave. Maybe I'm just really anal about the animations and them being perfect at 60 fps and others aren't noticing this problem, but it really sucks...

 

Also, Apple Watch working for everything — authorisations, Apple Pay, etc. — except unlocking the screen.

[M0r1d1n]

I'm starting to wonder if I should try to go back to an older version of WhateverGreen...

[M0r1d1n]

Setting the Mac model to iMacPro1,1 caused some USB ports not to work. Not sure if this indicates a general problem with the config or if it's something else.

[M0r1d1n]

OK so I'm back to the iMac19,1 setup and it's OK-ish again.

 

UI animations and screen saver password prompt are still laggy / choppy / slow (added for SEO) and nowhere near as smooth as on Mojave with the exact same hardware setup.

 

At this point I'm starting to suspect that something's wrong with the USB or Bluetooth setup of either OpenCore or Catalina. Perhaps @AudioGod has some more ideas what could be causing these issues.

 

Now, before you all go and say I'm crazy and your setup is perfect... My friend has almost the exact same setup as mine (5700 XT instead of an RX 580) and he has the exact same issues. He just didn't notice them and he never had Mojave on this machine. So perhaps I'm just super anal about having perfect animations at 60 fps without frame drops.

 

Anyway, I'll try to boot from a clone of my Mojave installation to show you the difference on video.

 

If anyone has any good ideas, please do chime in. This is driving me nuts!

 

Edit:

 

2nd kernel panic today...

 

panic(cpu 0 caller 0xffffff801d14153a): "thread_invoke: preemption_level 1, possible cause: blocking while holding a spinlock, or within interrupt context"@/AppleInternal/BuildRoot/Library/Caches/com.apple.xbs/Sources/xnu/xnu-6153.121.2/osfmk/kern/sched_prim.c:2205
Backtrace (CPU 0), Frame : Return Address
0xffffff875c8bb640 : 0xffffff801d11f5cd 
0xffffff875c8bb690 : 0xffffff801d258b05 
0xffffff875c8bb6d0 : 0xffffff801d24a68e 
0xffffff875c8bb720 : 0xffffff801d0c5a40 
0xffffff875c8bb740 : 0xffffff801d11ec97 
0xffffff875c8bb840 : 0xffffff801d11f087 
0xffffff875c8bb890 : 0xffffff801d8c27cc 
0xffffff875c8bb900 : 0xffffff801d14153a 
0xffffff875c8bb970 : 0xffffff801d13fc2f 
0xffffff875c8bb9c0 : 0xffffff801d2407c0 
0xffffff875c8bba20 : 0xffffff801d1b26fd 
0xffffff875c8bbaf0 : 0xffffff801d176e01 
0xffffff875c8bbc20 : 0xffffff801d239aef 
0xffffff875c8bbc70 : 0xffffff801d0c5a40 
0xffffff875c8bbc90 : 0xffffff7fa269ed01 
0xffffff875c8bbd80 : 0xffffff7fa269d78e 
0xffffff875c8bbda0 : 0xffffff7fa269b4be 
0xffffff875c8bbdf0 : 0xffffff7fa269ab7f 
0xffffff875c8bbe20 : 0xffffff801d8333e9 
0xffffff875c8bbe90 : 0xffffff801d833309 
0xffffff875c8bbec0 : 0xffffff801d161565 
0xffffff875c8bbf40 : 0xffffff801d161091 
0xffffff875c8bbfa0 : 0xffffff801d0c513e 
      Kernel Extensions in backtrace:
         ru.joedm.SMCSuperIO(1.1.4)[3EBEC0A6-5D45-3034-A52E-8B63A6FABDA1]@0xffffff7fa2699000->0xffffff7fa26a8fff
            dependency: as.vit9696.Lilu(1.4.5)[E42CE60E-EC0B-33AE-A513-5383B81BF165]@0xffffff7fa24d6000
            dependency: as.vit9696.VirtualSMC(1.1.4)[9DD28544-2B81-33EB-B3F1-488D0FBB0947]@0xffffff7fa24ff000
            dependency: com.apple.iokit.IOACPIFamily(1.4)[0A7D7382-66FE-391B-9F93-97A996256C25]@0xffffff7f9e245000

BSD process name corresponding to current thread: kernel_task
Boot args: -v shikigva=80 darkwake=0 alcid=16 igfxmetal=1 

Mac OS version:
19F101

Kernel version:
Darwin Kernel Version 19.5.0: Tue May 26 20:41:44 PDT 2020; root:xnu-6153.121.2~2/RELEASE_X86_64
Kernel UUID: 54F1A78D-6F41-32BD-BFED-4381F9F6E2EF
Kernel slide:     0x000000001ce00000
Kernel text base: 0xffffff801d000000
__HIB  text base: 0xffffff801cf00000
System model name: iMac19,1 (Mac-AA95B1DDAB278B95)
System shutdown begun: NO
Panic diags file available: YES (0x0)

System uptime in nanoseconds: 30937228304

 

Edited July 2, 2020 by M0r1d1n
Typos and added KP.

[kapelan6]

Quietly with myself, I have a conversation.

[eSaF]

39 minutes ago, kapelan6 said:

Quietly with myself, I have a conversation.

At least you won't lose an argument   

[M0r1d1n]

OK so here's where I've gotten so far:

 

1. I changed one of the quirks (can't recall which one off the top of my head — would have to compare files) and all kernel panics which occurred right after logging in are now gone.

 

2. Generated SSDT-USBX.aml and replaced USBPorts.kext with USBMap.kext with a generated USB Map. USB now works much better and there is no audio drops on external USB speakers anymore.

 

3. Generated new SSDT-PLUG.aml according to the Dortania Vanilla Guide. Its contents differ from @AudioGod's implementation and I would love to know why.

 

4. Wi-Fi/Bluetooth + UI lag + similar issues are still present. Not sure why at this point. It could just be a Catalina bug for all I know.

[M0r1d1n]

Status update:

 

I removed SMCSuperIO.kext and SMCProcessor.kext from the config.plist and Bluetooth Audio is now flawless.

 

Still having laggy UI issues and the Apple Watch doesn't want to unlock the screen saver.

[Locked Down]

On 7/3/2020 at 2:51 PM, M0r1d1n said:

OK so here's where I've gotten so far:

 

3. Generated new SSDT-PLUG.aml according to the Dortania Vanilla Guide. Its contents differ from @AudioGod's implementation and I would love to know why.

 

 

@AudioGod's one is probably a generic one that covers loads of different systems. The one you created is probably specific to your motherboard, so will not have all the bloatware needed to cover multiple systems.

It is usually best to create SSDT's specific to your own system (MB) rather than use generic ones if possible, as they will be a lot smaller and load quicker. If you are unsure in what you are doing at any point then just sticking with the generic ones will be fine most of the time.