Jump to content

[SUCCESS] HUANANZHI X79-ZD3 + Xeon E5-2689 [Mojave 10.14.6] [Big Sur 11.2.3] [Monterey 12.0.1] [Sonoma beta 7]

verdazil

By verdazil,
in Installation Guides

 Share
138 posts in this topic

Recommended Posts

BillDH2k
BillDH2k
Posted
Posted (edited)

Just want to report back that I've tried the similar DSDT editing on my Dell T5810, with Clover 5150 (per @Slice suggestion). Same result, "non-monotonic time" kernel panic under Monterey during booting. 

 

So I am convinced that the solution would need to be a BIOS level "fix". If some smart guy could figure out how HP Z440/840, also SuperMicro X99 boards, do differently to perform a TSC synch to the CPUS before proceeding to OS boot. These boards, as I pointed before, do not need CpuTscSync.kext/VoodooTscSync.kext to boot/run Monterey.

 

BTW, I like the new Clover, especially the ability to modify boot arg, as well as choosing different config.plist, on the fly. This makes it a lot easier to experiment different settings. Also, converting from OC to Clover is relative easy. The two appeared to work similarly under the hook. I could almost use the same aml/kext files.

Edited by BillDH2k
  • Like 1
Link to comment
Share on other sites
BillDH2k
BillDH2k
Posted
Posted (edited)

 @Zuja4701 @Slice @verdazil.  I have finally found a solution!  At least it worked for DELL T5810.

 

I used this efi tool to reset TSC before launching Monterey: 

          ResetTSCAdjust.efi, from here: https://github.com/denskop/VoodooTSCSync/issues/1#issuecomment-629837192

          ResetTSCAdjust.efi.zip

 

I tested in two different methods, and both worked.

 

Method 1 (manual): add this efi tool to the picker menu, and run it once before launching macOS.

  • Add this efi file to EFI/OC/Tools, and add it to Picker menu: Root->Misc->Tools.
  • When booting up to OC picker, select ResetTSCAdjust.efi to run once, and then select macOS to boot.

 

Method 2 (auto): add this efi tool as EFI driver, so it will run automatically during booting.

  • Add this efi file to EFI/OC/Drivers, then add it to Root->UEFI->Drivers

 

When I test the above for the 1st time, I found out that I need to perform a NVRAMReset at least once to clear previous settings.

 

Please try this method if you are unable to boot Monterey due to "non-monotonic time" panic.

 

Credit goes to original author of this tool. 

 

Edited by BillDH2k
  • Like 2
  • Thanks 2
Link to comment
Share on other sites
Zuja4701
Zuja4701
Posted
Posted
3 hours ago, BillDH2k said:

 @Zuja4701 @Slice @verdazil.  I have finally found a solution!  At least it worked for DELL T5810.

 

I used this efi tool to reset TSC before launching Monterey: 

          ResetTSCAdjust.efi, from here: https://github.com/denskop/VoodooTSCSync/issues/1#issuecomment-629837192

           ResetTSCAdjust.efi.zip 5.05 kB · 3 downloads

 

I tested in two different methods, and both worked.

 

Method 1 (manual): add this efi tool to the picker menu, and run it once before launching macOS.

  • Add this efi file to EFI/OC/Tools, and add it to Picker menu: Root->Misc->Tools.
  • When booting up to OC picker, select ResetTSCAdjust.efi to run once, and then select macOS to boot.

 

Method 2 (auto): add this efi tool as EFI driver, so it will run automatically during booting.

  • Add this efi file to EFI/OC/Drivers, then add it to Root->UEFI->Drivers

 

When I test the above for the 1st time, I found out that I need to perform a NVRAMReset at least once to clear previous settings.

 

Please try this method if you are unable to boot Monterey due to "non-monotonic time" panic.

 

Credit goes to original author. 

 

@BillDH2k Thank you very much Bill, I have also installed successfully Ventura on dell T7910 by using ResetTSCAdjust.efi.

Dell T7910 + Ventura.png

  • Like 2
  • Thanks 1
Link to comment
Share on other sites
Drovosek
Drovosek
Posted
Posted

There is a CpuTSCSync kext from a Chinese developer who made a fork of this kext from the acidanthera project.

https://gitee.com/chenguangheiguo/cputscsync-chenguang-network-studio-master

 

Most of the commits in his repository are manipulations with markdown files (and as you understand, this does not affect the kext itself), but in this commit he made quite a few changes to the kext.

https://gitee.com/chenguangheiguo/cputscsync-chenguang-network-studio-master/commits/master

https://gitee.com/chenguangheiguo/cputscsync-chenguang-network-studio-master/commit/3fd4f61c07b4b03934bd8e293dc52f61ec843045

Try his kext version if someone has problems with acidanthera version CpuTscSync or problems with kext VoodooTSCSync

 

v1.5.3

https://gitee.com/chenguangheiguo/cputscsync-chenguang-network-studio-master/releases/tag/1.5.3

https://gitee.com/chenguangheiguo/cputscsync-chenguang-network-studio-master/releases/download/1.5.3/CpuTSCSync V5.3.kext.zip

CpuTSCSync V1.5.3.kext.zip

  • Like 1
Link to comment
Share on other sites
BillDH2k
BillDH2k
Posted
Posted (edited)

@Drovosek  Unless the TSC resync action is done significantly earlier in Monterey booting process, it would not address the root cause of the booting problem. It might help other situations.

 

Here is the comment by one of the OC developer, regarding the root cause (booting):

https://github.com/acidanthera/bugtracker/issues/1676#issuecomment-881884751

vit9696 commented on Jul 17, 2021

> Well, the situation unpleasant. The root cause of the issue is that on macOS 12 CPU registration comes in parallel with many other things,

> so SMP support (hardware multithreading) is initialised even before all the CPU cores are initialised.

>

> Normally the solution is to wait for all CPUs to register, then perform the TSC sync on them. Now it is no longer feasible,

> since whenever even just 2 CPUs register, we already have multithreading and potentially a kernel panic. I am not quite sure how to address it best.

 

 

I read their commit comments (in Chinese), no mentioning of addressing root cause for booting. But I will give this kext a try anyway.

 

Update: Tried and it does not work.

Edited by BillDH2k
  • Like 1
Link to comment
Share on other sites
vdv
vdv
Posted
Posted

Tested on Monterey ResetTSCAdjust.efi but no luck. A protocol i is missing. 

 

Looking for a solution, I read on the forum where you got this file that problem for 2697v2 should be related to APIC patching. Clover was doing it easily. OC not. 


In any case I did some progress. 
Using voodootscsyn I fixed Catalina. 
I had solution in front of my eyes…but looking elsewhere. 
Thanks for patience and suggestions
 

Also Monterey install has been a bit tricky, but worked. 
Still on the cpus=1 limit but able to boot it. 
 

I’ll try to delete unused cpu on the dsdt, use voodoo as recommended. 
 

Do you recommend to go with OC (and manually patch Apic) or to try with clover? 
 

Thanks

A6D01FDA-D715-4558-A731-F8C9E8A9883D.jpeg

Link to comment
Share on other sites
Slice
Slice
Posted
Posted
15 hours ago, Drovosek said:

There is a CpuTSCSync kext from a Chinese developer who made a fork of this kext from the acidanthera project.

https://gitee.com/chenguangheiguo/cputscsync-chenguang-network-studio-master

 

Most of the commits in his repository are manipulations with markdown files (and as you understand, this does not affect the kext itself), but in this commit he made quite a few changes to the kext.

https://gitee.com/chenguangheiguo/cputscsync-chenguang-network-studio-master/commits/master

https://gitee.com/chenguangheiguo/cputscsync-chenguang-network-studio-master/commit/3fd4f61c07b4b03934bd8e293dc52f61ec843045

Try his kext version if someone has problems with acidanthera version CpuTscSync or problems with kext VoodooTSCSync

 

v1.5.3

https://gitee.com/chenguangheiguo/cputscsync-chenguang-network-studio-master/releases/tag/1.5.3

https://gitee.com/chenguangheiguo/cputscsync-chenguang-network-studio-master/releases/download/1.5.3/CpuTSCSync V5.3.kext.zip

CpuTSCSync V1.5.3.kext.zip 7.51 kB · 4 downloads

These links are useless because of chinese language and absent registration.

 

See my signature. I successfully installed Monterey on X79 + Ivybridge-E5 by Clover 5150.

Yes, I also had problems with TSC sync. Anyway all problems were resolved as said before multiple times.

  • Like 1
Link to comment
Share on other sites
anerik70
anerik70
Posted
Posted
18 hours ago, Drovosek said:

There is a CpuTSCSync kext from a Chinese developer who made a fork of this kext from the acidanthera project.

https://gitee.com/chenguangheiguo/cputscsync-chenguang-network-studio-master

 

Most of the commits in his repository are manipulations with markdown files (and as you understand, this does not affect the kext itself), but in this commit he made quite a few changes to the kext.

https://gitee.com/chenguangheiguo/cputscsync-chenguang-network-studio-master/commits/master

https://gitee.com/chenguangheiguo/cputscsync-chenguang-network-studio-master/commit/3fd4f61c07b4b03934bd8e293dc52f61ec843045

Try his kext version if someone has problems with acidanthera version CpuTscSync or problems with kext VoodooTSCSync

 

v1.5.3

https://gitee.com/chenguangheiguo/cputscsync-chenguang-network-studio-master/releases/tag/1.5.3

https://gitee.com/chenguangheiguo/cputscsync-chenguang-network-studio-master/releases/download/1.5.3/CpuTSCSync V5.3.kext.zip

CpuTSCSync V1.5.3.kext.zip 7.51 kB · 5 downloads

It works well here! 

Thank you guy!

image.thumb.png.0014ccd7d539ba7191b7bd4f00306ffb.png

Link to comment
Share on other sites
BillDH2k
BillDH2k
Posted
Posted

@vdv  I tried to run this efi tool on HP Z420 board (X79/2680V2), it gave the same error. But on HP Z440 [X99] it run properly. So It appears that X79 boards may not have up-to-date version of UEFI BIOS to support "EFI_MP_SERVICES_PROTOCOL" call. The solution could be an update of this efi tool to perform a TSC reset using method supported by the older BIOS. Or better, OC or Clover could do this easily, if the developers are made aware of this issue. 

  • Thanks 1
Link to comment
Share on other sites
Slice
Slice
Posted
Posted
On 11/6/2022 at 6:12 PM, vdv said:

Tested on Monterey ResetTSCAdjust.efi but no luck. A protocol i is missing. 

 

Looking for a solution, I read on the forum where you got this file that problem for 2697v2 should be related to APIC patching. Clover was doing it easily. OC not. 


In any case I did some progress. 
Using voodootscsyn I fixed Catalina. 
I had solution in front of my eyes…but looking elsewhere. 
Thanks for patience and suggestions
 

Also Monterey install has been a bit tricky, but worked. 
Still on the cpus=1 limit but able to boot it. 
 

I’ll try to delete unused cpu on the dsdt, use voodoo as recommended. 
 

Do you recommend to go with OC (and manually patch Apic) or to try with clover? 
 

Thanks

A6D01FDA-D715-4558-A731-F8C9E8A9883D.jpeg

Very bad!!!

If your BIOS doesn't contain EFI_MP_SERVICES_PROTOCOL then you can't use TscSyncTimeout quirk. Also ResetTSCAdjust.efi is impossible.

May be you will be happy with other pathes/quirks. (PatchAPIC in Clover, fix somehow DSDT, VoodooTscSync)

Link to comment
Share on other sites
vdv
vdv
Posted
Posted

Hi,

1 week of trials and fails.

It seems that DSDT with removed useless thread/CPU + VoodooTSC + current edit is going ahead but still no boot (no issues with CPUS=1 of coarse).

lapic_dont_panic=1 doesn't show benefit.

 

As you can see it try to "load" SCK2.C200 with is CPU I have erased from DSDT. 

It seems also the voodoo is not present if I check with IORegistryExplorer (I have modified the info to 47 - 12x2x2-1 cores)

Is there any place I should erase/modify?

 

I'm trying in 12.6.1. Should I downgrade to 12.0.1?

 

Can you please have a look to my folder and to address on the right direction?

 

I'm also try to work on the MRS unlock of firmware (or Region Unlock).

Unfortunately no big help (an no wish to have a bricked mobo).

 

Any help appreciated.

 

P.S.

Other road would be Clover but I'm afraid to loose all experience (even if extremely limited) I've done with OC.

Boot.png

1408440665_EFI2.zip

Link to comment
Share on other sites
BillDH2k
BillDH2k
Posted
Posted (edited)

@vdv I would advise that you stay at Big Sur for now, until the root cause for TSC out of sync is addressed under Monterey's booting. T5810/T7910 got lucky because ResetTSCAdjust.efi worked while your T5610 did not because of the older BIOS. Your best hope is someone could write a similar one-time TSC Reset tool compatible for the older BIOS (it surely could be done, but I am not an expert here). Editing DSDT is not addressing the root cause, not for these DELL boards (I've tried all the suggested DSDT methods mentioned here with my T5810, including using Clover, without success).

Edited by BillDH2k
  • Thanks 1
Link to comment
Share on other sites
vdv
vdv
Posted
Posted
11 hours ago, BillDH2k said:

@vdv I would advise that you stay at Big Sur for now, until the root cause for TSC out of sync is addressed under Monterey's booting. T5810/T7910 got lucky because ResetTSCAdjust.efi worked while your T5610 did not because of the older BIOS. Your best hope is someone could write a similar one-time TSC Reset tool compatible for the older BIOS (it surely could be done, but I am not an expert here). Editing DSDT is not addressing the root cause, not for these DELL boards (I've tried all the suggested DSDT methods mentioned here with my T5810, including using Clover, without success).

Many thanks. Really appreciated.

I was almost on the position to sell this machine and consider an easier project.

Sometime a good suggestion is what you need to continue testing.

 

Do you know where to address the request for TSC adjust? Maybe to Opencore group or to Clover group? Or some programmer with same knowledge of the writer of ResetTSCAdjust.efi 

I'll be very glad to buy someone a couple of beers, and be a tester.

Link to comment
Share on other sites
Slice
Slice
Posted
Posted
On 11/6/2022 at 6:12 PM, vdv said:

Tested on Monterey ResetTSCAdjust.efi but no luck. A protocol i is missing. 

 

Looking for a solution, I read on the forum where you got this file that problem for 2697v2 should be related to APIC patching. Clover was doing it easily. OC not. 


In any case I did some progress. 
Using voodootscsyn I fixed Catalina. 
I had solution in front of my eyes…but looking elsewhere. 
Thanks for patience and suggestions
 

Also Monterey install has been a bit tricky, but worked. 
Still on the cpus=1 limit but able to boot it. 
 

I’ll try to delete unused cpu on the dsdt, use voodoo as recommended. 
 

Do you recommend to go with OC (and manually patch Apic) or to try with clover? 
 

Thanks

A6D01FDA-D715-4558-A731-F8C9E8A9883D.jpeg

Hi,

I found a way to produce the protocol EFI_MP_SERVICE_PROTOCOL.

Try to put this driver into the bootloader.

In the case of Clover this is the folder

/EFI/CLOVER/drivers/UEFI

I need your tests and observations.

 

  • Thanks 1
Link to comment
Share on other sites
BillDH2k
BillDH2k
Posted
Posted (edited)
21 hours ago, Slice said:

Hi,

I found a way to produce the protocol EFI_MP_SERVICE_PROTOCOL.

Try to put this driver into the bootloader.

In the case of Clover this is the folder

/EFI/CLOVER/drivers/UEFI

I need your tests and observations.

CpuDxe.efi.zip 15.43 kB · 4 downloads

 

@Slice Tried this on HP Z420 (X79) with OC 0.8.4. With CpuDxe.efi loaded as driver, OpenCore boot would hang (no message to screen and did not reach picker). Without it, OC would boot up fine.

Edited by BillDH2k
  • Thanks 1
Link to comment
Share on other sites
verdazil
verdazil
Posted
  • Author
Posted (edited)
23 hours ago, vdv said:

Refreshed config.plist with properthree. 

Didn't the Propertрtree say that there are a lot of errors in the config? For example, "No schema for SyncTableIDS at 5 index, context <Quirks>! ?? And 17 more!!!

In the section, UEFI --> Drivers errors too. The parameter Arguments requires a string value, not a data.

You need to check the config with the ocvalidate utility

Edited by verdazil
Link to comment
Share on other sites
 Share
Go to topic listing
×
×
  • Create New...