Monterey on X79G v1.3 + E5-1650 v2 panic

[AwSomeSiz]

Yoo
After many attempts to install Big Sur on X79G motherboard, I finally managed to do it!

However, when running the Monterey 12.3 installer, I ran into a problem that I can’t solve for more than a day, namely, writing on the lines:
• Kernel trap at 0xffffff8007484f3b
• panic(cpu 0 caller 0xffffff8007484f3b)
• Fault CR2: 0xffffff800b6792b1

DSDT is used by me, cleaned of all warnings and removed entries in _SB about extra processors and threads, leaving only 12 threads.
So far, googling does not help, so I turn to you for help and at the same time try to fix it

What I tried:
• played with quirks
• changed CpuTscSync to VoodooTscSync and back it
• changed VirtualSMC to FakeSMC and back it
• added "cpus=1" to the arguments and deleted
• deleted CpuTscSync and back it (because without TSC Sync Kext i can't to boot into any MacOS)
• played with DSDT patches and with the creation of SSDT
• and a lot of other things

P.S. I'm using OpenCore 0.8.0 with latest version of kexts&drivers

 

[EliteMacx86]

Yoo
After many attempts to install Big Sur on X79G motherboard, I finally managed to do it!

However, when running the Monterey 12.3 installer, I ran into a problem that I can’t solve for more than a day, namely, writing on the lines:
• Kernel trap at 0xffffff8007484f3b
• panic(cpu 0 caller 0xffffff8007484f3b)
• Fault CR2: 0xffffff800b6792b1

DSDT is used by me, cleaned of all warnings and removed entries in _SB about extra processors and threads, leaving only 12 threads.
So far, googling does not help, so I turn to you for help and at the same time try to fix it

What I tried:
• played with quirks
• changed CpuTscSync to VoodooTscSync and back it
• changed VirtualSMC to FakeSMC and back it
• added "cpus=1" to the arguments and deleted
• deleted CpuTscSync and back it (because without TSC Sync Kext i can't to boot into any MacOS)
• played with DSDT patches and with the creation of SSDT
• and a lot of other things

P.S. I'm using OpenCore 0.8.0 with latest version of kexts&drivers

View attachment 4236

The Kernel panic is due to CPUTscSync and Lilu.

Your configuration is not as per the guide. Here are the issues.

- You should not use USBMap and USBToolBox together. Use one, not both. It's better to remove USBToolBox
- Kexts loading order is not correct. Use the guide to fix the sorting order.
- DisableIoMapper must be enabled.
- Update your version of CPUTscSync.
- You should generate an SSDT for CPU PM using Piker's script.

 

[AwSomeSiz]

The Kernel panic is due to CPUTscSync and Lilu.

Your configuration is not as per the guide. Here are the issues.

- You should not use USBMap and USBToolBox together. Use one, not both. It's better to remove USBToolBox
- Kexts loading order is not correct. Use the guide to fix the sorting order.
- DisableIoMapper must be enabled.
- Update your version of CPUTscSync.
- You should generate an SSDT for CPU PM using Piker's script.

Thanks for ur reply, bro.
I did all what u said, and deleted some more SSDT's from my EFI, not only PLUG.
And creater new PM SSDT with ssdtPRGen.
All's good, all USB ports work without USBTool, but now my PC have a lot of lags and long boot time.
I ll fix it and after this will post results.

P.S. SSDT EC and HPET I created on windows with SSDTTime.

 

[EliteMacx86]

Thanks for ur reply, bro.
I did all what u said, and deleted some more SSDT's from my EFI, not only PLUG.
And creater new PM SSDT with ssdtPRGen.
All's good, all USB ports work without USBTool, but now my PC have a lot of lags and long boot time.
I ll fix it and after this will post results.

P.S. SSDT EC and HPET I created on windows with SSDTTime.

No PR files attached.

 

[AwSomeSiz]

No PR files attached.

I made changes to my EFI:
• Indeed, I shouldn't have generated an SSDT-PLUG for my Ivy Bridge E since it's need for Haswell and newer. I generated SDST-PM via ssdtPRGen and everything works great.
• Should I enable DisableIoMapper if I disabled VT-d in the BIOS?
• Put kexts in the right order, but didn't understand if SMCProcessor and SMCSuperIO should be placed before VirtualSMC or not.
• The version of CpuTscSync, like all other kexts, uses the latest version.

Big Sur works perfectly (I'll fix the sound later), the Monterey installer stucks.

 

[AwSomeSiz]

No PR files attached.

What does mean PR file?

Is it?

 

[AwSomeSiz]

Tried to use CpuTscSync by wy414012 and catch another panic and immediate reboot, when loading Monterey installer. With Big Sur I'm loading successfully.

 

[AwSomeSiz]

Tried to use CpuTscSync by wy414012 and catch another panic and immediate reboot

I recorded video and saved moment. A moment after that, the reboot starts.

 

[EliteMacx86]

I made changes to my EFI:
• Indeed, I shouldn't have generated an SSDT-PLUG for my Ivy Bridge E since it's need for Haswell and newer. I generated SDST-PM via ssdtPRGen and everything works great.
• Should I enable DisableIoMapper if I disabled VT-d in the BIOS?
• Put kexts in the right order, but didn't understand if SMCProcessor and SMCSuperIO should be placed before VirtualSMC or not.
• The version of CpuTscSync, like all other kexts, uses the latest version.

Big Sur works perfectly (I'll fix the sound later), the Monterey installer stucks.

What does mean PR file?

Is it?

Tried to use CpuTscSync by wy414012 and catch another panic and immediate reboot, when loading Monterey installer. With Big Sur I'm loading successfully.

I recorded video and saved moment. A moment after that, the reboot starts.

Still not proper. Use VoodooTscSync instead of CPUTscSync. If that doesn't work, use TSCAdjustReset

 

[AwSomeSiz]

Good morning.
I collected detailed statistics with logs (which, as I understand it, do not make much sense) and a description of the behavior of the system at boot.

Here is the results:
• Without any TscSync kexts - Monterey unsuccess (panic and reboot), Big Sur unsuccess(panic and stuck)
• Without any TscSync kexts with cpus=1 - Monterey unsuccess (panic and stuck), Big Sur unsuccess (panic and stuck)
• Using VoodooTscSync = Monterey unsuccess (panic and reboot), Big Sur success
• Using TscAdjustReset = Monterey unsuccess (panic and reboot), Big Sur unsuccess(panic and stuck)
• Using CpuTscSync = Monterey unsuccess (panic and stuck), Big Sur success


Should I try to do something else or just stay on Big Sur? Before this, I experienced a few days of bad luck with Big Sur, but I was still able to get it to work.