<< Solved >> Monterey Update 12.3.1 => 12.4 Kernel Panic

[dalaranunion]

Final Update (for those who might experience such thing)
The Kernel Panics was USB related. Specifically a result of two, port limit, kernel patches: IOUSBHostFamily / AppleUSBXHCI. These were patches I transfered over from MacMan's Build with Clover.

Removing these allowed the update to boot and install just fine. I then simply had to re-map my USB ports via USBMap.

Another important note: Using XhciPortLimit caused issues. All my back (motherboard) usb panel was dead, apart from the internal USBs. I used a wireless Mouse / Keyboard to help with using my Hackintosh and map my USBs

---

Update1: I tried to look for different pointers but after reading this:

00:449 00:005 AAPL: #[EB.H.LV|!] Err(0xE) <- RT.GV boot-image 7C436110-AB2A-4BBB-A880-FE41995C9F82
00:456 00:007 AAPL: #[EB.H.LV|!] Err(0xE) <- RT.SV- boot-signature 7C436110-AB2A-4BBB-A880-FE41995C9F82
00:462 00:006 AAPL: #[EB.H.LV|!] Err(0xE) <- RT.SV- boot-image-key 7C436110-AB2A-4BBB-A880-FE41995C9F82
00:469 00:006 AAPL: #[EB.H.LV|!] Err(0xE) <- RT.SV- boot-image 7C436110-AB2A-4BBB-A880-FE41995C9F82

Could it be that the update partition is corrupt?

If OpenCore would have any issues then it would stop from booting all together, right? Therefore this means that the Kernel Panic is something from MacOs Side...

--

So I have used the Software Update, as I usually do to update my Hackintosh. But this time, when restarting to boot into the update volume. The installation would kernel panic.

My specs are classic build:
Mobo - ASUS TUF Z390-Pro Gaming
CPU - i7-9700K
GPU - RX Vega 56

At first I thought it was my Open Core Version, updated to the latest but still the same.

I have attached the Open Core Debug file here along with the Panic. Does anyone have any clues what this might cause it? I must notice that I have updated my Hackintosh from Catalina => Monterey Fine, and then after till 12.3.1. So I really wonder what could trigger a kernel panic.

Also Open Core 8.1 no longer has the "Reset NVRAM" option. Pressed space but the option didn't show up anyone has experience with that?

Thanks,

 

[jywuo]

same problem here...

 

[elgipsy]

Try to download the full MacOS 12.4 from the App Store and install that instead of the update.
As for reset NVRAM, check here, basically starting with OC 0.8.1 you need to add ResetNvramEntry.efi to the Drivers folder of your EFI and add it to your plist

 

[dalaranunion]

Try to download the full MacOS 12.4 from the App Store and install that instead of the update.
As for reset NVRAM, check here, basically starting with OC 0.8.1 you need to add ResetNvramEntry.efi to the Drivers folder of your EFI and add it to your plist

Oh I see many thanks for that, I reckon they made lots of code improvements and that had to live in a separate "space" as a boot option that is a tool.

I could do a fresh install indeed, but I work on this system. Mostly I am curious as to what could trigger it. I reckon I would have to get on with OC debug version. I am a bit new to this, I would think there are two parts of the debugging/logging. One is the OpenCore's and second is the MacOS. Seeing other people installing latest update with OpenCore it is not open core rather my set-up/settings. Is there any way to save the KernelPanic of the MacOS?

Do you suggest turning off kernel patches I had from clover? Minding that OC is better and more improved?

Any pointers from anyone or keywords let me know

Thanks

 

[elgipsy]

I didn't tell you to do a fresh install, rather download the full MacOS 12.4 from the App Store and let it install straight from desktop, no need to create a bootable USB and if successful 12.4 will be installed and you won't loose any data an update might fail if for some reason bits of it were not properly downloaded. It's rare but it can happen, bad luck I guess.

As for OC, yeah they did some changes, you can always check the bootloaders forums for differences between updates.

You can save kernel panics.... if a report is made when macOS boots. If it's the case you can open the report and copy/paste the content. If it happens before MacOS loads then I think you can only take screenshots with another device.

Sometimes you can also find traces of panics using the console app

 

[jywuo]

I didn't tell you to do a fresh install, rather download the full MacOS 12.4 from the App Store and let it install straight from desktop, no need to create a bootable USB and if successful 12.4 will be installed and you won't loose any data an update might fail if for some reason bits of it were not properly downloaded. It's rare but it can happen, bad luck I guess.

As for OC, yeah they did some changes, you can always check the bootloaders forums for differences between updates.

You can save kernel panics.... if a report is made when macOS boots. If it's the case you can open the report and copy/paste the content. If it happens before MacOS loads then I think you can only take screenshots with another device.

Sometimes you can also find traces of panics using the console app

Still same situation and kernel panic on same place than dalaranunion first message picture.

 

[nhonguyen.80]

Still same situation and kernel panic on same place than dalaranunion first message picture.

You can try to add the cpus=1 boot flag. I have had the same problem, it was KP without this boot flag.

 

[Middleman]

To boot Monterey 12.4 you could try to enable AdviseFeatures. Z390 systems will need the following enabled:
ACPI: SSDT-AWAC, SSDT-EC, SSDT-GPRW, SSDT-HPET, SSDT-PLUG, SSDT-SBUS-MCHC, SSDT-XOSI plus _OSI to XOSI rename patch
Booter: AvoidRuntimeDefrag, EnableSafeModeSlide, EnableWriteUnprotector, ProvideCustomSlide, and SetupVirtualMap.
Kernel: DisableIOMapper, DisableLinkedItJettison, PanicNoKextDump., PowerTimeoutKernel, ThirdPartyDrives & a custom USBMap or USBPorts kext plus usual Lilu/Whatevergreen/AppleALC/VirtualSMC.
Use of OC 0.7.8+, CPUFriend & NVMEFix is also recommended.

 

[jywuo]

To boot Monterey 12.4 you could try to enable AdviseFeatures. Z390 systems will need the following enabled:
ACPI: SSDT-AWAC, SSDT-EC, SSDT-GPRW, SSDT-HPET, SSDT-PLUG, SSDT-SBUS-MCHC, SSDT-XOSI plus _OSI to XOSI rename patch
Booter: AvoidRuntimeDefrag, EnableSafeModeSlide, EnableWriteUnprotector, ProvideCustomSlide, and SetupVirtualMap.
Kernel: DisableIOMapper, DisableLinkedItJettison, PanicNoKextDump., PowerTimeoutKernel, ThirdPartyDrives & a custom USBMap or USBPorts kext plus usual Lilu/Whatevergreen/AppleALC/VirtualSMC.
Use of OC 0.7.8+, CPUFriend & NVMEFix is also recommended.

Hi Middleman,

dalaranunion have Z390 mobo, I have a Z370.
I think that problem is my USB mapping also. I used until now the USBinjectAll.kext and never made proper USB mapping.

 

[Middleman]

Hi Middleman,

dalaranunion have Z390 mobo, I have a Z370.
I think that problem is my USB mapping also. I used until now the USBinjectAll.kext and never made proper USB mapping.

Right. Well they are same thing anyways (300 series) so my settings should work for you.
If you are going to boot Monterey 12.4 I suggest to turn off XHCIPortLimit and enable XHCI-unsupported.kext
and the other kexts I mentioned - and then turn off USBInjectall once you have your USB map. Also make sure device-id and AAPL,ig-platform-id is Coffee Lake (from the Dortania guide). Your Vega64 dGPU is natively supported so you shouldn't need anything else in the boot-arg.