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] [Sequoia 15.0]

verdazil

By verdazil,
in Installation Guides

 Share
158 posts in this topic

Recommended Posts

BillDH2k
BillDH2k
Posted
Posted
3 hours ago, vdv said:

Hi,

I understand but before installing the driver I don’t have those errors. 

 

I would recommend using OCAT tool to check your config.plist (Here is good link for instruction). Those errors are typically from old formats not compatible with newer OC. 

Link to comment
Share on other sites
Slice
Slice
Posted
Posted
On 11/19/2022 at 11:23 PM, 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.

 

I may propose next iteration. Test please.

 

Link to comment
Share on other sites
BillDH2k
BillDH2k
Posted
Posted (edited)
20 hours ago, Slice said:

I may propose next iteration. Test please.

CpuMpDxe.efi.zip 8.36 kB · 1 download

 

@Slice  Tried this driver on a HP Z620 (X79, 1x 2650V2) with OC 0.8.4. OC boot up OK, no hang up, but when I tried to run ResetTSCAdjust.efi (as an EFI tool), it hanged on message "Looking up EFI_MP_SERVICES_PROTOCOL..." 

 

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

@Slice Also went a step further to test with the VerifyMP.efi tool (from the same source as ResetTSCAdjust.efi here). It checked the current TSC values, then perform a reset, and show new TSC after the reset. See screen capture below for results.

 

On HP Z620 with your CpuMpExe.efi loaded as EFI driver, it appeared to have passed "looking up EFI_MP_SERVICES_PROTOCOL" and then stuck on next step "MSR TSC Adjust" (could only speculate what the script was trying to do).  For comparison,  I also showed the screen capture when the script was working on a HP Z440 (BIOS has support for EFI_MP_SERVICES_PROTOCOL).

 

when running VerifyMP.efi on HP Z620 (with CpuMpExe.efi loaded as driver):

image.thumb.jpeg.be2663db4f5d59d44c5a9e89e7f52c94.jpeg

 

When running VerifyMP.efi on HP Z440 (no extra driver loaded):

image.thumb.jpeg.11929a49eb1e6f52e8b398274b2187ee.jpeg

 

Edited by BillDH2k
Link to comment
Share on other sites
verdazil
verdazil
Posted
  • Author
Posted (edited)

Ventura experimental installation

 

Brief description of the installation procedure:

1. Download the Ventura installer to the Applications directory

2. Patch the installer with OCLP app

3. Make an installation flash drive as always

4. Install the system in the usual way. For the first log on to the Ventura desktop at the final stage of installation, disable SIP, set the SecureBootModel parameter to Disabled, and add the -x bootarg

5. Complete Post Install Root Patch with OCLP app, delete -x bootarg and reboot

 

P.S. Having a second working macOS on this PC will greatly facilitate and speed up the work.

Edited by verdazil
  • Thanks 1
Link to comment
Share on other sites
vdv
vdv
Posted
Posted
On 11/27/2022 at 4:50 PM, verdazil said:

@vdv, you are using the debug version OC 0.8.6?

Check the config.plist settings using the ocvalidate utility. I see 43 errors!

Very bad update.

I tried to change CPU. Unfortunately bent 4 pins (CPU falled).

Bending them back in position...2 broken. Mobo not reparable.

My experience with T5610 stop here. Already sold the CPUS.

 

Reassembled back the T5600 and sold.

Thanks for the help.

 

Now I will work on a T5810.

Let see if I can handle 1 cpu :)

 

Link to comment
Share on other sites
  • 9 months later...
verdazil
verdazil
Posted
  • Author
Posted (edited)

Sonoma 14 beta7 experimental installation

 

1. Installation completed with OCLP

 

2. Some special settings and files (OpenCore):

- Native CpuPm.aml ACPI Table is deleted, a modified CpuPmMod.aml is used instead

- AppleIntelCPUPowerManagement.kext, AppleIntelCPUPowerManagementClient.kext from macOS Monterey, patched for compatibility with Sonoma and added to OpenCore

- For Turbo Boost operation used 3 patches in OC config section Kernel --> Patch

- To ensure synchronization of CPU cores, a modified CpuTSCSyncM.kext is used

- USBPorts.kext used for correct operation of the USB ports

- Custom PowerPlay Tables for AMD Polaris Card RX 570 4G

- Custom memory OC settings

 

3. What works?

- Video: 4K x 60Hz on BENQ-BL2711U + Full HD x 60Hz on LG TV 42LF650V

- Sound: audio jack + HDMI audio on both monitors

- USB2 && USB3 ports

- LAN

- CPU SpeedStep and Turbo Boost

- VDA Decoder Fully Supported

 

4. EFI folder available: https://drive.google.com/file/d/1iWEZOT9ORBZcHv-Se_u500GEyfXDI61H/view?usp=sharing

 

5. Test work images

1.thumb.png.537f1098ed0fdc1e7378ae23d0a43889.png

 

2.thumb.png.273bdeeddbcf5454a7d1f0736611dea9.png

 

3.thumb.png.81c8b16eff85a813561a9c7688b5313e.png

Edited by verdazil
  • Like 1
Link to comment
Share on other sites
  • 4 months later...
  • 7 months later...
verdazil
verdazil
Posted
  • Author
Posted (edited)

Successfully installed macOS Sequoia 15.0

EFI folders available.

 

Updated hardware configuration

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
TV: LG TV 42LF650V
SSD: Lexar SSD NM620, 256 Gb
SSD: Samsung SSD 850 EVO, 250 Gb
SSD: Kingston SA400 S37120G, 120 Gb
SSD: Transcend TS120G SSD220S, 120 Gb
HDD: SAMSUNG HD154UI, 1.5 Tb
HDD: WDC WD20EZ13X, 2.0 Tb
WiFi: TP-LINK TL-WDN4800 Qualcomm Atheros AR938x Wireless Network Adapter [168c:0030]

 

What  work?

- Video: 4K x 60Hz on BENQ-BL2711U + Full HD x 60Hz on LG TV 42LF650V (OCLP v. 2.0.1)

- Sound: audio jack + HDMI audio on both monitors (AppleALC for OC and VoodooHDA for Clover)

- Wi-Fi TP-LINK TL-WDN4800 Qualcomm Atheros AR938x  (OCLP v. 2.0.1)

- USB2 && USB3 ports

- LAN

- Speed Step

- Turboboost

 

EFI Clover: https://drive.google.com/file/d/1Z_OEwU-FVIqe_lzCsy2nfkCMRSm0KCgZ/view?usp=sharing

EFI OC: https://drive.google.com/file/d/1cQjGUFx7Z78xs-ab-KEh4ZP1QJ8EqPbG/view?usp=sharing

Edited by verdazil
  • Like 3
Link to comment
Share on other sites
  • 1 month later...
kinhhoang161
kinhhoang161
Posted
Posted (edited)

@verdazil Hello. Sorry for bothering you. I also have a machine with quite similar configuration but i cant make it working with macOS Sonoma 14.4

 

That is:

CPU: E5-2689
Main: X79-8D
RAM: 32GB
SSD: 256GB NVME no brand
GPU: RX570

 

I tried to install Sonoma but got the error as shown below. I think it is related to the TSC Sync error of the CPU so I tried to do as you and everyone discussed above. However, even though I did it, I could not Boot into the macOS installation.

- I tried the VoodooTSCSync kext attached in this post + TscSyncTimeout = 525000
(also tried the kext in your latest EFI which is CPUTscSyncM + TscSyncTimeout = 525000

but all failed )

- I tried the DSDT Patch method but in the end I couldn't build it because it required Patching many other things. I don't have the ability so I had to leave it. Is it possible to build SSDT to spoof or drop SKC1,SKC2 or something.

- In the end. I used the ResetTSCAdjust.efi driver but it hangs when booting with the error loaded ResetTSCAdjust.efi.

 

 

My pictures about error:

 

Spoiler

z5979555358759_cc1fe033476831cb0d8ffccfa2de7ec5.thumb.jpg.1ac46e4438ba4633f6ea6e23b839ad4a.jpg

 

 

 

Spoiler

z5979555370306_08a4363badfeb8260ccd7ba32e4035c6.thumb.jpg.95fd0690314bafb0d47f8711f0cfb79f.jpg

 

 

If you can. please help me or give me some suggestions

Here is my EFI and my original DSDT. Thank you very much

 

DSDT.aml EFI.zip opencore-2024-10-28-232119.txt

Edited by kinhhoang161
Link to comment
Share on other sites
verdazil
verdazil
Posted
  • Author
Posted (edited)

Hi, @kinhhoang161

1. I have corrected the errors in the DSDT ACPI table.

But one more table needs correction: SSDT-0-CpuPm.aml. With its loading instead of the native one.

2. "Not used SCK delete"ACPI patch not needed

3. Driver HfsPlus.efi not needed

4. The correct order of kexts: 1 - Lilu, 2- VirtualSMC...

5. Need kext CpuTscSyncM.kext

DSDT.zip

Edited by verdazil
Link to comment
Share on other sites
kinhhoang161
kinhhoang161
Posted
Posted
On 10/29/2024 at 9:03 PM, verdazil said:

Hi, @kinhhoang161

1. I have corrected the errors in the DSDT ACPI table.

But one more table needs correction: SSDT-0-CpuPm.aml. With its loading instead of the native one.

2. "Not used SCK delete"ACPI patch not needed

3. Driver HfsPlus.efi not needed

4. The correct order of kexts: 1 - Lilu, 2- VirtualSMC...

5. Need kext CpuTscSyncM.kext

DSDT.zip 31.76 kB · 0 downloads

 

Sorry for my late reply. The past few days I've been quite busy with my work. Only now can we continue to perform hackintosh. I will try them and will respond as soon as possible. Thank you very much

Link to comment
Share on other sites
verdazil
verdazil
Posted
  • Author
Posted
On 10/29/2024 at 4:03 PM, verdazil said:

But one more table needs correction: SSDT-0-CpuPm.aml. With its loading instead of the native one.

2. "Not used SCK delete"ACPI patch not needed

3. Driver HfsPlus.efi not needed

4. The correct order of kexts: 1 - Lilu, 2- VirtualSMC...

 

Link to comment
Share on other sites
kinhhoang161
kinhhoang161
Posted
Posted

 

1. But one more table needs correction: SSDT-0-CpuPm.aml. With its loading instead of the native one. 

 

- i checked and see that it only have one CPU file which is SSDT ( CpuPm ). So i need to patch it right ?

SSDT.aml 

 

2. "Not used SCK delete"ACPI patch not needed DONE - REMOVED

3. Driver HfsPlus.efi not needed DONE 

4. The correct order of kexts: 1 - Lilu, 2- VirtualSMC... DONE

5. Need kext CpuTscSyncM.kext DONE

Link to comment
Share on other sites
verdazil
verdazil
Posted
  • Author
Posted

1. XHCI-unsupported.kext && USBMap.kext
Need one of these kexts. If done correctly, only USBMap.kext.
2. UEFU --> APFS —> MinDate && MinVersion "-1"

3. Bootargs: -crypt_force_avx npci=0x3000 ipc_control_port_options=0 amfi=0x80 -cputsbeta

4. Disable NVMeFix.kext (may interfere)

5. Delete all MmioWhitelist (Doesn't make sense if DevirtualiseMmio set to YES)
 

Link to comment
Share on other sites
kinhhoang161
kinhhoang161
Posted
Posted
6 minutes ago, verdazil said:

1. XHCI-unsupported.kext && USBMap.kext
Need one of these kexts. If done correctly, only USBMap.kext.
2. UEFU --> APFS —> MinDate && MinVersion "-1"

3. Bootargs: -crypt_force_avx npci=0x3000 ipc_control_port_options=0 amfi=0x80 -cputsbeta

4. Disable NVMeFix.kext (may interfere)

5. Delete all MmioWhitelist (Doesn't make sense if DevirtualiseMmio set to YES)
 

1. DONE
2. DONE
3. DONE
4. DONE
5. DONE

i still cant boot. i see the verbose has one line is 32 threads but 16 registered from MADT. can it be problem ?image.thumb.png.aa9da6eb0c464854d7aa7ccce0320bc9.png

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