12.3.1 WindowServer Crash

D

DarkSilentSC

Active member
AMD OS X Member
Jun 4, 2021
132
60
28
CPU:
Ryzen 9 5900X
Currently macOS locks up almost immediately after successfully booting up to GUI, and then auto-reboots.
I tried removing BAR support / Removing Whatevergreen as well- WindowServer crashes and then reboots back to BIOS.

Zero clue where to begin troubleshooting this...
 
Sort by date Sort by votes
DarkSilentSC said:
Currently macOS locks up almost immediately after successfully booting up to GUI, and then auto-reboots.
I tried removing BAR support / Removing Whatevergreen as well- WindowServer crashes and then reboots back to BIOS.

Zero clue where to begin troubleshooting this...
Click to expand...
Have you included AppleMCEReporterDisabler.kext in your build? Try that first because that is needed for 12.3.
If that doesn't work, add swd_panic=1 to your boot-arg to see what's gone wrong.
 
Upvote 0 Downvote
I did have the AppleMCEReporterDisabler kext included and enabled. That's why I was able to get MacOS GUI and log in, but it just reboots on its own after short period of time.
adding swd_panic=1 gave me no log dumps of any sort...
 
Upvote 0 Downvote
DarkSilentSC said:
I did have the AppleMCEReporterDisabler kext included and enabled. That's why I was able to get MacOS GUI and log in, but it just reboots on its own after short period of time.
adding swd_panic=1 gave me no log dumps of any sort...
Click to expand...
Okay. What's your build spec? And which version of Opencore are you using?
 
Upvote 0 Downvote

R9 5900X on Gigabyte Aorus X570 Xtreme with RX 6900XT - Sonoma 14.0 - OC 0.9.5 EFI

Build Spec CPU: Ryzen R9 5900X Motherboard: Gigabyte AORUS X570 Xtreme - BIOS F37e RAM: G-Skill Trident Z Neo 4x16GB DDR4 3600Mhz C16 (XMP) Graphics: AsRock RX 6900 XT (Reference Board) Case : NZXT 710i NVMe: Samsung 970 EVO 1TB PSU: Corsair RM1000i WiFi-Bluetooth: BCM94360NG M.2 WiFi -...
forum.amd-osx.com forum.amd-osx.com

I juuust updated to 0.7.9 but that didn’t help either.
 
Upvote 0 Downvote
DarkSilentSC said:

R9 5900X on Gigabyte Aorus X570 Xtreme with RX 6900XT - Sonoma 14.0 - OC 0.9.5 EFI

Build Spec CPU: Ryzen R9 5900X Motherboard: Gigabyte AORUS X570 Xtreme - BIOS F37e RAM: G-Skill Trident Z Neo 4x16GB DDR4 3600Mhz C16 (XMP) Graphics: AsRock RX 6900 XT (Reference Board) Case : NZXT 710i NVMe: Samsung 970 EVO 1TB PSU: Corsair RM1000i WiFi-Bluetooth: BCM94360NG M.2 WiFi -...
forum.amd-osx.com forum.amd-osx.com

I juuust updated to 0.7.9 but that didn’t help either.
Click to expand...
Okay. I can see you are missing a number of things. SSDT-EC for starters. Also SSDT-CPUR & SSDT-HPET & SSDT-USB-W. SSDT-CPUR is slightly different to SSDT-PLUG. I've enabled both on my B550 Vision D. Also missing SMCAMDProcessor.kext & SMCSuperIO.kext.
 
Upvote 0 Downvote
I have SSDT-EC actually. SSDT-CPUR I believe this is specifically for B550 and A520. SSDT-HPET is for X79 and X99 and high-end desktops and laptops. What is SSDT-USB-W?
I have SMCAMDProcessor.kext and AMDRyzenCPUPowerManagement.kext. Do I still need SMCSuperIO.kext?

I also updated to OC 0.8.0 with no success. I have attached my config.plist below. Have at it!
 

Attachments

Last edited:
Upvote 0 Downvote
DarkSilentSC said:
I have SSDT-EC actually. SSDT-CPUR I believe this is specifically for B550 and A520. SSDT-HPET is for X79 and X99 and high-end desktops and laptops. What is SSDT-USB-W?
I have SMCAMDProcessor.kext and AMDRyzenCPUPowerManagement.kext. Do I still need SMCSuperIO.kext?
Click to expand...
Yes. It’s part of USBWakeFixup.

If it’s not working for you you are welcome to check out my 5900X B550 Vision D build here for comparison which is fully working with Monterey 12.3 > https://www.tonymacx86.com/threads/...-5900x-rx550-samsung-1tb-970-evo-plus.319781/
 
Upvote 0 Downvote
Any additional help or responses would be greatly appreciated-- I have looked at few other people's configuration files and tried matching them with no success..

Also I wanted to enable Aquantia Support but it wants DisableIOMapper to be false and enable Vt-d (AMD-V) in BIOS - This resulted in black screen.
Any ideas?
 
Upvote 0 Downvote
DarkSilentSC said:
Any additional help or responses would be greatly appreciated-- I have looked at few other people's configuration files and tried matching them with no success..

Also I wanted to enable Aquantia Support but it wants DisableIOMapper to be false and enable Vt-d (AMD-V) in BIOS - This resulted in black screen.
Any ideas?
Click to expand...
Yes.

To boot 12.3.1:

Remove just the device-id in your Aquantia PCIRoot device properties and disable DisableIOMapper and any existing AQC patches. Enable VT-d in BIOS.
Your system should have this kernel patch enabled in config.plist as well:

Identifier: com.apple.driver.AppleEthernetAquantiaAqtion
Comment: AQC 107 10 Gbe v3
Find: 0F844503 0000
Replace: 660F1F44 0000
MinKernel: 21.4.0
Count: 1
Enabled: YES

If you are still having blackouts after this, it may be because you are using Monterey 12.2., in which case the solution will be slightly different from above.
I won't post it just yet in case it gets too confusing for you, but it involves a) another set of kernel patches plus b) the enabling of AQC 107 properties in Device Properties plus disabling of VT-d in BIOS and DisableIOMapper. :)
 
Upvote 0 Downvote
I’m seeing growing number of success cases with SMBIOS of iMac rather than Mac7,1… Will give this a try.
 
Upvote 0 Downvote
Okay. Finally found out the problem. It had to do with BAR Size settings. Has anyone got config.plist param that works for BAR Sizing for 6900XT?
 
Upvote 0 Downvote
Disabling and re-enabling BAR size seems to be doing the trick, yet it's somewhat unstable. I'll continue normally using 12.4 for now. Thanks.
 
Upvote 0 Downvote
Middleman said:
Yes.

To boot 12.3.1:

Remove just the device-id in your Aquantia PCIRoot device properties and disable DisableIOMapper and any existing AQC patches. Enable VT-d in BIOS.
Your system should have this kernel patch enabled in config.plist as well:

Identifier: com.apple.driver.AppleEthernetAquantiaAqtion
Comment: AQC 107 10 Gbe v3
Find: 0F844503 0000
Replace: 660F1F44 0000
MinKernel: 21.4.0
Count: 1
Enabled: YES

If you are still having blackouts after this, it may be because you are using Monterey 12.2., in which case the solution will be slightly different from above.
I won't post it just yet in case it gets too confusing for you, but it involves a) another set of kernel patches plus b) the enabling of AQC 107 properties in Device Properties plus disabling of VT-d in BIOS and DisableIOMapper. :)
Click to expand...
Okay, I'm now narrowing down to a point that the crashes are caused by Aquantia Settings done in config.plist.
I can boot it to Monterey 12.4 by using the following settings:
1. DeviceProperties - Removed the PCIe address that is for Aquantia device
2. Enabled ForceAquantiaEthernet Quirk in Kernel
3. Applied kernel patch as per above, except the Find parameter is 0F84C002 0000
4. DisableIOMapper is 'false'
5. Enabled SVM support in BIOS (Basically Vt-d support in Gigabyte's terms)

However this setting still end up with Network status as Self Assigned IP. I guess ForceAquantiaEthernet is still to be further developed?
 
  • Like
Reactions: Middleman
Upvote 0 Downvote
You must log in or register to reply here.
Top Bottom
✖
  AdBlock Detected
Sure, ad-blocking software does a great job at blocking ads, but it also blocks some useful and important features of our website. For the best possible site experience please take a moment to disable your AdBlocker.