• Become a Premium Member for $25/year with no ads to improve your community experience. Upgrade to Pro Account for faster response and no wait times!

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

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.
Can you attach your BIOS Settings?
 
Can you attach your BIOS Settings?
Sure,
BIOS - X79GA00E
Disabled:
• Above 4G Decoding
• ACPI Auto Configuration
• Hibernation
• USB 3.0 Support (because my MB haven't USB3 ports)
• XHCI Hand-off (because my MB haven't USB3 ports)
• Serial Port
• VT-d
• ME Subsystem
• Lauch CSM
• Fast Boot
• Secure Boot

Enabled:
• Hyper-Threading
• Virtualization Technology
• EHCI Hand-off

With latest CpuTscSync I tried to reset setting to default (Enabled VTd, SCM, Serial Port etc) and still get this panic (kernel trap...)

P.S. Just in case, I attached an archive with a photo of the BIOS settings.
 

Attachments

But I think, with VoodooTscSync I have more chances to install Monterey, because I get more lines when I try to boot it. But catch reboot :)
 

Attachments

  • 1st photo.jpg
    1st photo.jpg
    1.6 MB · Views: 24
  • 2nd photo.jpg
    2nd photo.jpg
    1.7 MB · Views: 24
Using VoodooTscSync and set "cpus=1" in boot-args allowed me to move on.
Now I'm stuck here.
 

Attachments

  • IMG_20220424_141004143.jpg
    IMG_20220424_141004143.jpg
    10.7 MB · Views: 23
Extract your DSDT via SSDTTime in Windows and upload it here... Thanks!

SSDTTime
 
  • Like
Reactions: AwSomeSiz
Sure,
BIOS - X79GA00E
Disabled:
• Above 4G Decoding
• ACPI Auto Configuration
• Hibernation
• USB 3.0 Support (because my MB haven't USB3 ports)
• XHCI Hand-off (because my MB haven't USB3 ports)
• Serial Port
• VT-d
• ME Subsystem
• Lauch CSM
• Fast Boot
• Secure Boot

Enabled:
• Hyper-Threading
• Virtualization Technology
• EHCI Hand-off

With latest CpuTscSync I tried to reset setting to default (Enabled VTd, SCM, Serial Port etc) and still get this panic (kernel trap...)

P.S. Just in case, I attached an archive with a photo of the BIOS settings.
Your BIOS settings are wrong.
 
  • Like
Reactions: AwSomeSiz
Extract your DSDT via SSDTTime in Windows and upload it here
Yoo, here is my dumped via SSDTTime DSDT.aml
Reset BIOS to Defaults and set up your BIOS again
I understand it.
I played a lot with the BIOS settings, but it did not lead to any effect.
Now I will set the settings according to one of your guides and update my post.

P.S. Thanks for ur answer, guys!!!

UPD:
• Hyper-threading - Enabled
• Virtualization - Enabled
• Legacy USB Support - Enabled
• USB3.0 Support - Enabled
• XHCI Hand-off - Enabled
• EHCI Hand-off - Enabled


• Sata mode - AHCI

• Serial Port - Disabled
• Network Stack - Disabled
• Intel VT-d - Disabled
• Secure Boot - Disabled
• Fast Boot - Disabled
• Launch CSM - Disabled

Current results:
without cpus = 1: Monterey - panic and reboot, Big Sur - successful boot
with cpus = 1: Monterey - the process goes on and stucks, Big Sur - stucks too on same lines

I'll attach my latest EFI, config and photos with system log.
It seems to me that there is no point in attaching the OpenCore logs, since there is information only about its launch and initialization.
 

Attachments

  • EFI.zip
    EFI.zip
    10.2 MB · Views: 30
  • monterey without cpus=1.png
    monterey without cpus=1.png
    9.6 MB · Views: 19
Last edited:
Yoo, here is my dumped via SSDTTime DSDT.aml

I understand it.
I played a lot with the BIOS settings, but it did not lead to any effect.
Now I will set the settings according to one of your guides and update my post.

P.S. Thanks for ur answer, guys!!!

UPD:
• Hyper-threading - Enabled
• Virtualization - Enabled
• Legacy USB Support - Enabled
• USB3.0 Support - Enabled
• XHCI Hand-off - Enabled
• EHCI Hand-off - Enabled


• Sata mode - AHCI

• Serial Port - Disabled
• Network Stack - Disabled
• Intel VT-d - Disabled
• Secure Boot - Disabled
• Fast Boot - Disabled
• Launch CSM - Disabled

Current results:
without cpus = 1: Monterey - panic and reboot, Big Sur - successful boot
with cpus = 1: Monterey - the process goes on and stucks, Big Sur - stucks too on same lines

I'll attach my latest EFI, config and photos with system log.
It seems to me that there is no point in attaching the OpenCore logs, since there is information only about its launch and initialization.
No DSDT and SSDTs attached. Use Clover to extract.
 
  • Like
Reactions: AwSomeSiz
No DSDT and SSDTs attached. Use Clover to extract.
Ops, DSDT file disappeared because his extension isn't allowed at this forum.
I'll attach my DSDT from SSDTTime now and ll attach origin tables from Clover some later(now 01:20 AM, at 5:30 I have to go to work, sry
 

Attachments

Forum statistics

Threads
1,937
Messages
18,124
Members
27,844
Latest member
moraWooChang