Tried to update to 12.3, now have kernel panic

[BillG66]

I finally got my machine restored and ports mapped, and everything running smoothly, then tried to update to 12.3. At first, all seemed to be going well, but after the first restart, the progress bar stopped, there was no hard disk activity for about 10 minutes, so I restarted. When I did, the install disk was gone, and it seemed to boot from my old disk just fine. But when I got to the log in page, the login froze. The wheel stopped spinning, and, again, no HD activity. So, I restarted, and now I get a kernel panic. What can I do?


Update: Now it will boot to the login screen, but freezes after I input my password.

 

[BillG66]

Sorry, getting desperate... is there anywhere I can download the macOS installer .dmg for 12.3? I found a way to create an installer in Windows, but all I've been able to find is the .pkg file...not the .dmg.

 

[marcohua]

No matter updated to 12.3 or a clean 12.3 installation, the panic is still going on. I have the almost same config, z490-i aorus, i9-10900 and igpu.

 

[BillG66]

No matter updated to 12.3 or a clean 12.3 installation, the panic is still going on. I have the almost same config, z490-i aorus, i9-10900 and igpu.

Any progress? I tried to reinstall 12.2, but it says the volume could not be downgraded.

 

[charlescai]

I believe I'm having similar issue (can't boot into MacOS 12.3 after upgrade) OC 0.7.6

 

[marcohua]

Any progress? I tried to reinstall 12.2, but it says the volume could not be downgraded.

I rolled back to 12.2.1 with a clean installing, which was working fine. Better stick to 12.2.1 until someone figures it out.

 

[danunahui]

If you have i225-v and dk.e1000=0 in bootargs, try to replace it with e1000=0.

 

[BillG66]

If you have i225-v and dk.e1000=0 in bootargs, try to replace it with e1000=0.

I don't have i225-v, but I do have dk.e1000=0. The question is, all I have access to is Windows at this point. How can I write to the EFI folder in Windows? I've figured out how to mount it, just not write to it.

 

[bmoag]

I rolled back to 12.2.1 with a clean installing, which was working fine. Better stick to 12.2.1 until someone figures it out.

I finally got my machine restored and ports mapped, and everything running smoothly, then tried to update to 12.3. At first, all seemed to be going well, but after the first restart, the progress bar stopped, there was no hard disk activity for about 10 minutes, so I restarted. When I did, the install disk was gone, and it seemed to boot from my old disk just fine. But when I got to the log in page, the login froze. The wheel stopped spinning, and, again, no HD activity. So, I restarted, and now I get a kernel panic. What can I do?


Update: Now it will boot to the login screen, but freezes after I input my password.

View attachment 544008

I ran into this exact problem with the update to 12.2.1 using what had been a successful OC 7.8. I didn't keep my screen shots but I think it was the same hard stop.
The fix was a bit laborious but worked as I was then able to go to 12.2.1 and yesterday 12.3.
I hope you have a bootable clone because the first step is restoring what worked.
I assumed the problem was with the custom USB kext I had made back in Catalina before converting from Clover to OC, the version of which was 6.8 I think. The kext worked but did not seem optimal.
In my not unlimited experienceIOPlatform etc often refers to USB problems.
If already in Monterey it is less problematic at that point to craft a new USB kext in Windows. Not hard to find the instructions.
I plugged that kext into my reverted 12.2 and it worked better than the one I had been using.
Updates as noted have been problem free since, so two cycles and now typing this in 12.3, whatever that is worth.
Might not work for you but nothing to lose. If it works don't forget to update the EFI on the clone.
If not using the latest version of OC and the kexts it might be worth slogging through the guide again, it doesn't take much more than an hour or so if you've done it before and you're using the same hardware.

 

[BillG66]

If you have i225-v and dk.e1000=0 in bootargs, try to replace it with e1000=0.

Holy Mackasmolie! That worked (mostly). It was a lot of hoops through which to jump, but I figured out how to edit the config.plist in Windows, removed the "dk." and rebooted right into my desktop! My problem now is Bluetooth. My trackpad and keyboard aren't connecting, although the trackpad keeps showing up in the devices window as "Not Connected." The keyboard isn't showing up at all. Maybe one of the Bluetooth kexts needs an update? Well, that's the next problem. At least I'm back in!