x79, OC 0.7.6 - Monterey does not work

[NEOSoftWare]

Please help me figure out why you can't start Monterey

I made an assembly according to the instructions from dortania for the x79 platform for the Sandy Bridge EP processor

And with this assembly, I can run big sur without any problems, but when loading Monterey I get this error (after which the computer restarts)

 

Tell me how to fix it?

EFI.zip

[Hangten]

Is not the cut off for Monterey Ivybridge from what I read RDRAND Example is needed. My X79 works but its a i7-4820K . 

 E5 2697v2 should work but not the Sandy E5 1660 

 

Remove VoodooTSCSync.kext it caused immediate panic in Monterey but not in Big Sur for my X79 see if that might work   

Edited November 14, 2021 by Hangten
EFI look over

[NEOSoftWare]

11 hours ago, Hangten said:

Remove VoodooTSCSync.kext

I disabled it and boot arg : cpus = 1 in the arguments and I was able to boot Monterey, but how can I make all the processor cores work?

Edited November 14, 2021 by NEOSoftWare

[Hangten]

E5 2697v2    <key>SystemProductName</key>
                         <string>MacPro6,1</string>
For this cpu you should change the SMBIOS (yes all the info pertaining to it also) 

Considering it is Natively supported on MacPro6,1

Try ACPI attached 

ACPI.zip

[Guest 5T33Z0]

Incorporate these patches and it should work. Use the SMBIOS which is for your CPU.

 

 

 

[NEOSoftWare]

14 hours ago, Hangten said:

Try ACPI attached 

Changed SMBIOS to iMacPro1,1 and added ACPI, it didn't help, everything still stops at the same place and freezes

 

13 hours ago, 5T33Z0 said:

Incorporate these patches and it should work. Use the SMBIOS which is for your CPU.

As I understand it, for my situation, it was only necessary to add kernel patches?

If so, I added them, but that gave no results :(

 

Do you have any other ideas?

[Guest 5T33Z0]

13 minutes ago, NEOSoftWare said:

As I understand it, for my situation, it was only necessary to add kernel patches?

If so, I added them, but that gave no results :(

 

Do you have any other ideas?

 

As I wrote in the Guide: the patch consists of 2 Parts: Booter AND Kernel patches. Then you can use the n correct SMBIOS for your CPU family and not the one suited for Monterey! The whole idea is to spoof a valid board ID via VM but for the hardware you use the correct SMBIOS suited for your CPU. So you need to add Booter patches as welll. Otherwise the whole patch is useless.

[NEOSoftWare]

2 hours ago, 5T33Z0 said:

As I wrote in the Guide: the patch consists of 2 Parts: Booter AND Kernel patches. Then you can use the n correct SMBIOS for your CPU family and not the one suited for Monterey! The whole idea is to spoof a valid board ID via VM but for the hardware you use the correct SMBIOS suited for your CPU. So you need to add Booter patches as welll. Otherwise the whole patch is useless.

Installed SMBIOS for MacPro6,1

added all the patches in the post, except
- Patch AppleSMC
- Disable Library Validation Enforcement
But without success, everything stops at the same place, please see my config.plist, maybe I was wrong about something?

 

config.plist.zip

[Guest 5T33Z0]

@NEOSoftWare Okay, I changed the Min and MaxKernel settings for the relevant kernel patches. I hope that fixes it. If not you have to recheck everything. The ACPI Section doesn't look good, the DeviceProperty section doesn't look good either

 

config.plist

[NEOSoftWare]

16 hours ago, 5T33Z0 said:

The ACPI Section doesn't look good, the DeviceProperty section doesn't look good either

Everything is the same, stops at the same moment from the first post and reboots,

ACPI is specified only SSDT-EC.aml the rest are disabled, and in DeviceProperty network devices are made internal, nothing else is there

[Guest 5T33Z0]

@NEOSoftWare Looked through the EFI and updated files etc. If this doesn't work, I can't help you. Is there a particular reason why you are using fakesmc?

 

EFI.zip

[NEOSoftWare]

2 hours ago, 5T33Z0 said:

Is there a particular reason why you are using fakesmc?

for HWMonitor to work normally

 

2 hours ago, 5T33Z0 said:

Looked through the EFI and updated files etc. If this doesn't work, I can't help you.

Yes, everything has been updated. I can boot Monterey operating system on this EFI assembly only if boot-args: cpus=1 🙁

 

and there is no VoodooTSCSync or CpuTscSync for Monterey?

[Guest 5T33Z0]

You can use HWMonitorSMC2 with VirtualSMC without Problems.

 

You should use either VoodooTSCSync or CpuTscSync. I'd choose the latter since it's newer.

[NEOSoftWare]

5 hours ago, 5T33Z0 said:

CpuTscSync. I'd choose the latter since it's newer.

Using this kext leads to panic (without it in Big Sur I can load and use all cpu kernels)

[Guest 5T33Z0]

Please remove fakesmc and sensor plugins and try virtualsmc

[NEOSoftWare]

9 hours ago, 5T33Z0 said:

try virtualsmc

I removed fakesmc and added virtualsmc - the problem persists

[Rocky12]

This is not my work

x79- e5_2670_v1_c2 OpenCore-0.7.5 Monterey.ZIP

[NEOSoftWare]

12 hours ago, Rocky12 said:

This is not my work

unfortunately it didn't work for me either (

[Guest 5T33Z0]

Then I suggest to stay on Big Sur since the RDRAND and Race to condition fixes for Sandy Bridge are experimental. I don't know how to resolve this issue .

Edited November 18, 2021 by 5T33Z0