Zuja4701 Posted August 3, 2022 Share Posted August 3, 2022 20 hours ago, verdazil said: MB: Huananzhi X79-ZD3 CPU: Intel® Xeon E5-2689, 1.2-3.6 GHz Chipset: Sandy Bridge-E Q65 (C600/C200) Memory: Samsung 32 Gb (4 x 8 Gb) ECC/REG, 1866 MHz, DDR3 Video: Sapphire Pulse Radeon RX 570 (4 Gb) Monitor: BENQ-BL2711U + LG TV 42LF650V SSD: 2.5" SATA SSD 250 Gb Samsung 850 EVO HDD: Seagate 2.0 Tb I don't know the algorithm how to choose value TscSyncTimeout correctly. Yes, I tried, it doesn't work for me. Thank you. I tried to use the value TscSyncTimeout = 525000, but it doesn't work for my specs. 1 Link to comment Share on other sites More sharing options...
verdazil Posted October 10, 2022 Author Share Posted October 10, 2022 A guaranteed solution has been found to resolve CPU core synchronization error when booting macOS 12 and newer. (Credits to @Slice) The solution is to edit DSDT.aml like this: 1. Remove "redundant" entries for non-existent CPUs 2. Remove "redundant" entries for non-existent CPUs threads 3. For all real CPU threads, do the following edit: Notes: - use attached VoodooTSCSync.kext version and DSDT sample. - use OpenCore parameter UEFI --> Quirks --> TscSyncTimeout (number) 500000 VoodooTSCSync.kext.zip DSDT.aml.zip Link to comment Share on other sites More sharing options...
anerik70 Posted October 10, 2022 Share Posted October 10, 2022 I just use this patch under ACPI config.plist Link to comment Share on other sites More sharing options...
Zuja4701 Posted October 11, 2022 Share Posted October 11, 2022 6 hours ago, anerik70 said: I just use this patch under ACPI config.plist 113.97 kB · 3 downloads hello @anerik70, which software did you use to patch ACPI? Is it work for intel xeon E5v4 in macOS 12 and newer? Thank you Link to comment Share on other sites More sharing options...
Slice Posted October 11, 2022 Share Posted October 11, 2022 Hi, @verdazil Have you ever a problem with audio? Sound is present as startup due to AudioDxe.efi. But when the macOS started I have no working audio device. Neither with AppleALC nor with VoodooHDA. Neither in Monterey nor in Mojave. What I am doing wrong? May be npci=0x3000 is a culprit? Link to comment Share on other sites More sharing options...
verdazil Posted October 11, 2022 Author Share Posted October 11, 2022 (edited) 24 minutes ago, Slice said: Hi, @verdazil Have you ever a problem with audio? Sound is present as startup due to AudioDxe.efi. But when the macOS started I have no working audio device. Neither with AppleALC nor with VoodooHDA. Neither in Monterey nor in Mojave. What I am doing wrong? May be npci=0x3000 is a culprit? Hi, @Slice Audio works perfectly fine in all Mojave - Monterey with AppleALC. Now I looked into my config and saw that there are conflicting audio settings there, apparently the boot-arg has a higher priority and works. Now there is no access to the computer to check that is redundant. Edited October 11, 2022 by verdazil Link to comment Share on other sites More sharing options...
Slice Posted October 11, 2022 Share Posted October 11, 2022 Is the chip ALC887? Link to comment Share on other sites More sharing options...
verdazil Posted October 11, 2022 Author Share Posted October 11, 2022 1 hour ago, Slice said: Is the chip ALC887? Yes, 5.1 ALC 887 Link to comment Share on other sites More sharing options...
Zuja4701 Posted October 11, 2022 Share Posted October 11, 2022 20 hours ago, verdazil said: A guaranteed solution has been found to resolve CPU core synchronization error when booting macOS 12 and newer. (Credits to @Slice) The solution is to edit DSDT.aml like this: 1. Remove "redundant" entries for non-existent CPUs 2. Remove "redundant" entries for non-existent CPUs threads 3. For all real CPU threads, do the following edit: Notes: - use attached VoodooTSCSync.kext version and DSDT sample. - use OpenCore parameter UEFI --> Quirks --> TscSyncTimeout (number) 500000 VoodooTSCSync.kext.zip 9.97 kB · 3 downloads DSDT.aml.zip 9.37 kB · 4 downloads hello @verdazil , I have followed your hints, but I could not remove 'redundant' as you mentioned above from DSDT file. I am appreciate if you could take a look my DSDT file, and please let me know how could I modify it. Thanks a lot. DSDT.aml Link to comment Share on other sites More sharing options...
verdazil Posted October 11, 2022 Author Share Posted October 11, 2022 @Zuja4701, your CPU Intel XEON E5-2699v4 doesn't need this method. It should normally work with CpuTscSync.kext. See https://www.insanelymac.com/forum/topic/341600-success-huananzhi-x79-zd3-xeon-e5-2689-mojave-10146-big-sur-1123-monterey-1201/?do=findComment&comment=2782711 Link to comment Share on other sites More sharing options...
Zuja4701 Posted October 11, 2022 Share Posted October 11, 2022 14 minutes ago, verdazil said: @Zuja4701, your CPU Intel XEON E5-2699v4 doesn't need this method. It should normally work with CpuTscSync.kext. See https://www.insanelymac.com/forum/topic/341600-success-huananzhi-x79-zd3-xeon-e5-2689-mojave-10146-big-sur-1123-monterey-1201/?do=findComment&comment=2782711 @verdazil, thank you. I have checked my CPUID that has "MSR_IA32_TSC_ADJUST". I can not install Monterey and Ventura without cpus=1. But there is no problem with Big Sur. I am really appreciate if you could give me some advice. Link to comment Share on other sites More sharing options...
BillDH2k Posted October 23, 2022 Share Posted October 23, 2022 I have a DELL T5810 (X99, with 2666V3) having the same booting problem under Monterey, due to "Non-Monotonic Time". Per @Slice's suggestion, I've tried to modify the DSDT for attempting a "similar" fix. It wasn't successful. Here is the trail of what I did: Link to comment Share on other sites More sharing options...
Zuja4701 Posted October 24, 2022 Share Posted October 24, 2022 5 hours ago, BillDH2k said: I have a DELL T5810 (X99, with 2666V3) having the same booting problem under Monterey, due to "Non-Monotonic Time". Per @Slice's suggestion, I've tried to modify the DSDT for attempting a "similar" fix. It wasn't successful. Here is the trail of what I did: Hello @BillDH2k and @Slice, I have the same problem with Dell T7910 ( E5-2699v4), it works well on Big Sur. But I can't boot without cpus=1 (kernel panic) on Monterey/Ventura. I do not know how to solve that problem. Any suggestions would be greatly appreciated. Link to comment Share on other sites More sharing options...
BillDH2k Posted October 24, 2022 Share Posted October 24, 2022 @Zuja4701 Unfortunately, no solution yet. My understanding, based on OC developer's comment, is that the Dell's BIOS failed to initialize the TSC synch properly, and cause the kernel to panic under Monterey. With a proper BIOS code, this could be avoided, like the cases of HP Z440/840 machines, where no TSC kext is needed to run Monterey. May be a smart guy could figure out a BIOS mod to fix this. I also tried an EFI tool that supposed to perform a TSC Reset, from a UEFI shell, before starting the macOS from the OC picker. But it wasn't successful. Link to comment Share on other sites More sharing options...
Slice Posted October 24, 2022 Share Posted October 24, 2022 On 10/11/2022 at 6:49 PM, Zuja4701 said: @verdazil, thank you. I have checked my CPUID that has "MSR_IA32_TSC_ADJUST". I can not install Monterey and Ventura without cpus=1. But there is no problem with Big Sur. I am really appreciate if you could give me some advice. On the screen I see AppleACPICPU: ProcessorID =120. It meas you make no DSDT patch to restrict the number of CPUs. Link to comment Share on other sites More sharing options...
Zuja4701 Posted October 24, 2022 Share Posted October 24, 2022 3 hours ago, Slice said: On the screen I see AppleACPICPU: ProcessorID =120. It meas you make no DSDT patch to restrict the number of CPUs. @Slice, thank you for your hints. I tried to add DSDT and generate SSDT with ssdtPRgen, but it is still not work. Please take a look my EFI if you have time. Thanks in advance! EFI.zip 5 hours ago, BillDH2k said: @Zuja4701 Unfortunately, no solution yet. My understanding, based on OC developer's comment, is that the Dell's BIOS failed to initialize the TSC synch properly, and cause the kernel to panic under Monterey. With a proper BIOS code, this could be avoided, like the cases of HP Z440/840 machines, where no TSC kext is needed to run Monterey. May be a smart guy could figure out a BIOS mod to fix this. I also tried an EFI tool that supposed to perform a TSC Reset, from a UEFI shell, before starting the macOS from the OC picker. But it wasn't successful. @BillDH2kYes, I tried many methods, but it does not work with my PC. Please let me know if you can solve this problem. Have a nice day! Link to comment Share on other sites More sharing options...
Slice Posted October 24, 2022 Share Posted October 24, 2022 2 hours ago, Zuja4701 said: @Slice, thank you for your hints. I tried to add DSDT and generate SSDT with ssdtPRgen, but it is still not work. Please take a look my EFI if you have time. Thanks in advance! EFI.zip 3.95 MB · 0 downloads @BillDH2kYes, I tried many methods, but it does not work with my PC. Please let me know if you can solve this problem. Have a nice day! You are using CpuTscSunc.kext which is paniced in Monterey. I tell about VoodooTSCSync.kext. Link to comment Share on other sites More sharing options...
Zuja4701 Posted October 24, 2022 Share Posted October 24, 2022 2 hours ago, Slice said: You are using CpuTscSunc.kext which is paniced in Monterey. I tell about VoodooTSCSync.kext. Yes, I have checked with VoodooTSCSync.kext, but it is the same kernel panic. Link to comment Share on other sites More sharing options...
Slice Posted October 24, 2022 Share Posted October 24, 2022 DSDT edit for CPUs number + the quirk TscSyncTimeout + VoodooTscSync.kext Yes? Link to comment Share on other sites More sharing options...
Zuja4701 Posted October 24, 2022 Share Posted October 24, 2022 35 minutes ago, Slice said: DSDT edit for CPUs number + the quirk TscSyncTimeout + VoodooTscSync.kext Yes? Yes, I used VoodooTSCSync.kext + the quirk TscSyncTimeout = 500000 as mentioned by @verdazil Link to comment Share on other sites More sharing options...
Zuja4701 Posted October 24, 2022 Share Posted October 24, 2022 1 hour ago, Zuja4701 said: Yes, I used VoodooTSCSync.kext + the quirk TscSyncTimeout = 500000 as mentioned by @verdazil Hello @Slice, please help me take a look at this EFI which included the VoodooTSCSync.kext + the quirk TscSyncTimeout. It is still the kernel panic, but I can not boot with cpus=1. EFI.zip Link to comment Share on other sites More sharing options...
Slice Posted October 24, 2022 Share Posted October 24, 2022 It looks like I have a success with another kext VoodooTSCSync.kext.zip Moreover, I am using Clover and FakeSMC. Link to comment Share on other sites More sharing options...
Zuja4701 Posted October 25, 2022 Share Posted October 25, 2022 8 hours ago, Slice said: It looks like I have a success with another kext VoodooTSCSync.kext.zip 8.16 kB · 3 downloads Moreover, I am using Clover and FakeSMC. Hi @Slice, I have tried to use your VoodooTSCSync.kext and FakeSMC, but it is the same KP. Please let me know of you have some new idea to solve this problem. Thanks a lot. Link to comment Share on other sites More sharing options...
verdazil Posted October 25, 2022 Author Share Posted October 25, 2022 2 hours ago, Zuja4701 said: t is the same KP. Please let me know of you have some new idea to solve this problem. I think the solution is right DSDT edit for CPUs number and threads as mentioned above. Link to comment Share on other sites More sharing options...
Slice Posted October 25, 2022 Share Posted October 25, 2022 15 hours ago, Zuja4701 said: Yes, I used VoodooTSCSync.kext + the quirk TscSyncTimeout = 500000 as mentioned by @verdazil In my case timeout is 750000. Link to comment Share on other sites More sharing options...
Recommended Posts