[Guide 2018] Z820 - HIGH SIERRA, The great guide (Sucess)

[kubes]

hi @BillDH2k

i have a HP z420
bios :3.96
intel xeon e5-2670 v2
nvidia quadro K2200
32GB ddram

I followed your thread trying to install catalina, 
but it happens to me that 3 minutes after the end of the OS installation, 
the machine reboots, how is this possible? 
could you please help me?

[BillDH2k]

@kubes There would be several reboots, as part of the OS installation. So not sure what you meant. Did the install complete its entire process? Normally, when the installation reboot, as part of its OS install process, it should pick the right partition automatically (can't recall the temporary partition name, "Install macOS"???), and no manual intervention is required.

 

[mexico78]

Hello BillDH2K,

I Have a Z840 and I tried to install Monterey and Ventura using your repo on Github, but it never worked, would you mind to share your EFI of that one please. I'm totally stuck

[BillDH2k]

OpenCore EFI for HP Z420-Z620-Z820 (0.9.1/0.7.1)

**(4/29/2023) Release 3.1 - Updated to OC 0.9.1. **

Details under the Release History section below.

About this EFI

OpenCore loader (0.9.1 & 0.7.1) for HP workstations Z420/Z620/Z820. Support macOS Catalina (10.15.7) to Monterey (12.6 tested).

Supported Hardware

• HP Z420/Z620/Z820 (BIOS 3.96, all motherboard revisions)
• CPUs: E5-1600/2600 V1 Xeon's (Sandy-Bridge) or V2 Xeon's (Ivy-Bridge)
• Required BIOS Settings: Enable UEFI boot, set SATA to AHCI mode, Disable Vt-d, and enable "Legacy ACPI Tables".

 

EFI Folders (Two Versions):

• EFI with OC 0.9.1

  • Support Big Sur and Monterey. Fresh install or update.

• EFI with OC 0.7.1

  • Mainly for supporting Catalina OS
  • Support Catalina/Big Sur (fresh install or update), Monterey (boot to existing install only)
  • Monterey install/update must use the newer EFI (0.9.1). Update from Catalina to Monterey must be done by booting up an USB Monterey installation stick.

• Choose the Correct config.plist

  • For Sandy-bridge CPUs (V1 Xeon's), use config_SandyCPUs.plist (rename it to config.plist)
  • For Ivy-bridge CPUs (V2 Xeon's), use config_IvyCPUs.plist (rename it to config.plist)
  • If you have 2643V2, 2667V2, or 2687w V2 CPUs, use the corresponding customized config_26XXV2.plist.

• Other Installation Note

  • Network LAN driver choice: For Z420 (Single LAN port), use IntelMausi.kext. For Z620/Z820 (Dual LAN ports), use AppleIntelE1000e.kext. Otherwise, you may experience random system lock up, especially true if NvMe SSD (via PCI-E adapter) is used.
  • Currently AppleIntelE1000e.kext is enabled by default in the config.list.

 

• What Works:

  • CPU Power Management (all processor models)
  • On-board Audio via AppleALC (Front/Back Jacks, internal speaker)
  • USB2 ports, Ethernet, On-Board SAS (Z820 only)
  • USB3 (Catalina only)

• What Not Work:

  • Sleep/Wake (Must disable from macOS, System Preference->Energy Saver->Prevent computer from sleeping)
  • USB3 ports not working under Big Sur or higher (no driver support for the TI chip). Recommend compatible USB3 PCIe add-on card, e.g. Inateck KT4006.

 

Pre/Post-Install:

• You must generate and add your own Serial # & Board ID to config.plist

• For full CPU power management, replace "SSDT-CPUPM.aml" (in ACPI folder) with one matching your CPU model. I have provided a few in the ACPI folder. Simply overwrite "SSDT-CPUPM.aml" with an appropriate file. If you have a different CPU not listed, you need to run ssdtPRGen (link) to create a new SSDT file. Additional instruction can be found here: bilbo's "Z820 - High Sierra, the Great Guide" (step #29) (link). If you have a mismatched CPU, you might experience booting issue. In this case, simply disable SSDT-CPUPM.aml from config.plist. macOs will run without CPU power management. Once up running, you can generate a correct SSDT file specific to your CPU.

• For 2643V2/2667V2/2687w V2 CPUs, use one of the pre-made config_xxx.plist, which include special patched CpuDef table. Without it, macOS won't boot.

Credits:

• bilbo's "Z820 - High Sierra, the Great Guide" (here). Also many of the follow-up posts in the same forum. My build wouldn't possible without these guy's work.
• Dortania's OpenCore Install Guide (Here)

 

*************

Due to attachment size limit, here is the EFI with OC0.9.1 only. The full repository can be found at Github.

1596839621_Zx20-OpenCore(0.9.1).zip

[oliveg]

Hi Guys!

Did someone try to install Ventura or Sonoma on his Zx20?

Which could be hardware limitations?

Thank you 😀

Olivier

Edited November 28, 2023 by oliveg

[BillDH2k]

OpenCore EFI for HP Z420-Z620-Z820 (0.9.7)

1. macOS support:

• Catalina/Big Sur/Monterey:

  • Native support (Recommended)

• Ventura/Sonoma:

  • Root patching with OCLP is required to enable graphic hardware acceleration. Check OCLP page for other limitations.
  • Follow the step-by-step instruction below.

2. Supported Hardware:

• HP Z420/Z620/Z820 (BIOS 3.96, all motherboard revisions)
• CPUs: E5-1600/2600 V1 Xeon's (Sandy-Bridge) or V2 Xeon's (Ivy-Bridge)
• Required BIOS Settings: Enable UEFI boot, set SATA to AHCI mode, Disable Vt-d, and enable "Legacy ACPI Tables".

 

3. What Works:

• CPU Power Management (all processor models)
• On-board Audio (Front/Back Jacks, internal speaker)
• USB2 ports, Ethernet, On-Board SAS (Z820 only)
• USB3 (Catalina only)

 

What Not Work:

• Sleep/Wake (Must disable from macOS, System Preference->Energy Saver->Prevent computer from sleeping)
• USB3 ports not working under Big Sur or higher (no driver support).
• Z820 DUAL CPU setup: boot issue (random lockup) under Sonoma/Ventura. Solution: stay with Monterey. No issue with single CPU.
• Z620 DUAL CPU setup: occationally locks up during booting under Sonamoa/Ventura. Reboot again normally works. Recommend temporarily remove the 2nd CPU card during Sonoma/Ventura installation.

 

4. EFI Folder

4.1 EFI with OC 0.9.7:

• Support Catalina - Sonoma (14.3.1 tested).
• SUMBIOS: MacPro7,1 (default) or iMacPro1,1. MacPro6,1 is supported up to Monterey.

4.2. Choose the correct config.plist:

• For Sandy-bridge CPUs (V1 Xeon's), use config_SandyCPUs.plist (rename it to config.plist).
• For Ivy-bridge CPUs (V2 Xeon's), use config_IvyCPUs.plist
• For 2643V2, 2667V2, or 2687w V2 CPUs, use the corresponding config_26XXV2.plist
• Choose the correct CPU PM file that matches your CPU model:
  • You may over-written SSDT_CPUPM.aml with the correct PM file (default PM), or
  • modify config.plist (ACPI->Add section) to pick the specific PM file
  • If your CPU is not listed, pick the one with closest match, disable use of any PM file (ACPI->Add section). Once install is completed, generate your own (see Post-Install) to enable optimal CPU power management.

4.3 For Catalina/Big Sur/Monterey:

• Just use the renamed config.plist, with the correct CPU PM file.

4.4 For Sonoma/Ventura:

• Follow Sonoma/Ventura step-by-step instruction below.

 

5. Other Installation Note:

• Network LAN driver choice: For Z420 (Single LAN port), use IntelMausi.kext. For Z620/Z820 (Dual LAN ports), use AppleIntelE1000e.kext. Otherwise, you might experience random system lock up, especially true if NvMe SSD (via PCI-E adapter) is used.
• Currently AppleIntelE1000e.kext is enabled by default in the config.list.

 

6. Pre/Post-Install

• You must generate and add your own Serial # & Board ID to config.plist

• For full CPU power management, replace "SSDT-CPUPM.aml" (in ACPI folder) with one matching your CPU model. I have provided a few in the ACPI folder. Simply overwrite "SSDT-CPUPM.aml" with an appropriate file. If you have a different CPU not listed, you need to run ssdtPRGen (link) to create a new SSDT file. Additional instruction can be found here: bilbo's "Z820 - High Sierra, the Great Guide" (step #29) (link). If you have a mismatched CPU, you might experience booting issue. In this case, simply disable SSDT-CPUPM.aml from config.plist. macOs will run without CPU power management. Once up running, you can generate a correct SSDT file specific to your CPU.

7. Sonoma/Ventura step-by-step instruction

The steps outlined below were tailored from the excellent instruction guide written by 5T33Z0.

 

Step 1. Start with the appropriate config.plist template (Section 4.2)

• Verify that this EFI works with your current Monterey/Big Sur setup (if you have one installed), with full CPU power management (use Intel Power Gadget tool to verify. Note: this tool can only be installed with single CPU configuration. But once installed, it runs fine under dual CPU configuration.).

 

Step 2. Modify the boot-args (to disable the video card hardware acceleration)

• Add the following flags to the boot-args:
  • "-amd_no_dgpu_accel"      if you have an AMD/Radeon card
  • “nv_disable=1”                     if you have an nVidia Kepler card
• optional:
  • "revpatch=sbvmm"          for Sonoma 14.3 only. Not needed for 14.2, or 14.3.1 (my own testing). Otherwise, you may encounter "Software Update Error” after 1st reboot. If you encounter this error, just do a restart (i.e. reboot) and the install would complete succesfully, except that the boot partition would end up as “Sonoma - Data” (which can be renamed later).

 

Step 3. Install Sonoma/ventura (latest version recommended)

• Reboot with the modified boot-args from Step 2. Make sure to perform a NVRAM reset (Important!)
• Start Sonoma/Ventura installation:
  • by booting from an USB installer stick (recommended), or
  • for updating from existing Ventura/Sonoma only, directly from a downloaded full installer copied to the Application folder (Note: for NVME disk, you must boot from USB Installer).
• Once Sonoma is installed successfully, proceed to Step 4.

 

Step 4: Apply OCLP patcher (to enable graphics card acceleration).

• Modify config.plist again:
  • csr-active-config to 03080000
  • Add “amfi=0x80” to boot-args
• Reboot. Perform NVRAM reset (Important). Reboot again.
• Download the latest OCLP patcher (OpenCore-Patcher-GUI.app )
• Launch the OCLP patcher and choose “Post-Install Root Patch”.

 

Step 5: Post OCLP change

• If OCLP root patching is successfully (Step 4), remove the following boot-args , if they were added from the previous steps:
  • "-amd_no_dgpu_accel"
  • "nv_disable=1"
  • "amfi=0x80"
  • "revpatch=sbvmm"
• Leave csr-active-config as <03080000>
• Reboot. Perform NVRAM reset. Reboot again.

 

Note:

• If you properly followed the steps above, the final EFI should be able to boot existing Big Sur, Monterey, and Ventura/Sonoma.

 

Credits:

• bilbo's "Z820 - High Sierra, the Great Guide" (here). Also many of the follow-up posts in the same forum. My build wouldn't possible without these guy's work.
• Dortania's OpenCore Install Guide (Here)
• "Installing macOS Ventura or newer on Ivy Bridge systems" (Here )

Hackintosh-HP-Z420-Z620-Z820-OpenCore-V3.4-Insanely.zip

Edited June 7 by BillDH2k

[bilbo]

thanks !! 😜

[antonio.clb]

Hello to everybody, hope everything well for you and your beloved ones! Long time no see here...

Just a quick post to show you my progress on Sonoma on my Z620 (see attached picture).

Thanks to @BillDH2k, @bilbo and 5T33Z0 for their precious work, my Z620 workstation is now perfectly working with Sonoma 14.5!

I've made a mix of these various tutorials and spent a couple of hours optimizing my previous EFI (0.9.7 with Monterey) and now latest version of Sonoma works!

Time to update my signature again!

 

Have a lot of fun and thanks again to everyone involved in this awesome project!

 

AC

P.S.: sorry for cross-posting...

[antonio.clb]

Just updated to Sonoma 14.6 folks!

Have a lot of fun!

 

AC

[Harry Hard]

Hello everyone,

 

unfortunately I haven't had much luck so far, I can't install Sonoma (or Ventura) with 'OpenCore EFI for HP Z420-Z620-Z820 (0.9.7)'. Also tried 1.0.0 with the folders from bilbo's package,

 

The system freezes during the first boot process (before the hard drive is formatted). I'm attaching a screenshot. Maybe someone can do something with it.

 

My system: z820 with 2x E5-2680v2 CPUs.

 

Thanks

 

This is the logfile:

 

00:000 00:000 AAPL: #[EB.H.IS|!] Err(0xE) <- RT.GV boot-signature 7C436110-AB2A-4BBB-A880-FE41995C9F82
00:112 00:112 AAPL: #[EB.H.IS|!] Err(0xE) <- RT.GV boot-image-key 7C436110-AB2A-4BBB-A880-FE41995C9F82
00:171 00:058 AAPL: #[EB|H:IS] 0
00:228 00:057 AAPL: #[EB|LOG:INIT] 2024-08-27T16:51:53
00:280 00:051 AAPL: #[EB|VERSION] <"bootbase.efi 580.140.1~8 (Official), built 2024-06-29T04:01:27-0700">
00:335 00:054 AAPL: #[EB|BUILD] <"BUILD-INFO[406]:{"DisplayName":"bootbase.efi","DisplayVersion":"580.140.1~8","RecordUuid":"CE64F4BE-AE76-4EAD-9193-9B193BB7A7CF","BuildTime":"2024-06-29T04:01:27-0700","ProjectName":"efiboot","ProductName":"bootbase.efi","SourceVersion":"580.140.1","BuildVersion":"8","BuildConfiguration":"Release","BuildType":"Official","Compiler":"clang-1500.3.9.1","SdkVersion":"14.6","SdkBuild":"23G65","TargetArchitectures":"x86_64"}">
00:392 00:057 AAPL: #[EB.CFG.DEV|!] Err(0xE) <- RT.GV booter-strict-xmlparser 7C436110-AB2A-4BBB-A880-FE41995C9F82
00:451 00:059 AAPL: #[EB|CFG:DEV] r5 0x0 0x0
00:510 00:059 AAPL: #[EB|H:IS] 0
00:623 00:113 AAPL: #[EB|WL:MODE] 0
00:688 00:064 AAPL: #[EB|CFG:ARG] boot-save-log 0x0000000000000002 (0x0000000000000002 < 0xFFFFFFFFFFFFFFFF) default
00:747 00:058 AAPL: #[EB|CFG:ARG] wake-save-log 0x0000000000000002 (0x0000000000000002 < 0x0000000000000002) default
00:805 00:058 AAPL: #[EB|CFG:ARG] console       0x0000000000000001 (0x0000000000000001 < 0x0000000000000001) default
00:862 00:056 AAPL: #[EB|CFG:ARG] serial        0x0000000000000001 (0x0000000000000001 < 0x0000000000000000) default
00:921 00:058 AAPL: #[EB|CFG:ARG] preoslog      0x0000000000000001 (0x0000000000000001 < 0xFFFFFFFFFFFFFFFF) default
00:980 00:058 AAPL: #[EB|CFG:ARG] timestamps    0x0000000000000000 (0x0000000000000000 < 0xFFFFFFFFFFFFFFFF) default
01:036 00:056 AAPL: #[EB|CFG:ARG] log-level     0x0000000000000001 (0x0000000000000001 & 0x0000000000000021) default
01:095 00:058 AAPL: #[EB|CFG:ARG] breakpoint    0x0000000000000000 (0x0000000000000000 & 0x0000000000000000) default
01:155 00:059 AAPL: #[EB|CFG:ARG] kc-read-size  0x0000000000100000 (0x0000000000100000 < 0xFFFFFFFFFFFFFFFF) default
01:219 00:063 AAPL: #[EB|CFG:ARG] force-error   0x0000000000000000 (0x0000000000000000 & 0x0000000000000000) default
01:276 00:056 AAPL: #[EB|H:IS] 0
01:335 00:059 AAPL: #[EB|WL] 0 0 0x01 0x01   0 0x00
01:394 00:059 AAPL: #[EB|BRD:NV] Mac-27AD2F918AE68F61
01:452 00:057 AAPL: #[EB|B:VAw]
01:513 00:061 AAPL: #[EB|B:IAw]
01:572 00:059 AAPL: #[EB|WL] 0 0 0x01 0x01   2 0x00
01:633 00:060 AAPL: #[EB.BST.IDT|+]
01:695 00:061 AAPL: #[EB.BST.IDT|-]
01:754 00:059 AAPL: #[EB|WL] 0 0 0x01 0x01   3 0x00
01:813 00:058 AAPL: #[EB|WL] 0 0 0x01 0x01   4 0x00
01:870 00:056 AAPL: #[EB|BRD:NV] Mac-27AD2F918AE68F61
01:928 00:058 AAPL: #[EB|WL] 0 0 0x01 0x01   5 0x00
01:987 00:058 AAPL: #[EB.H.CHK|BM] 0x0000000000000000
02:046 00:058 AAPL: #[EB.H.LV|!] Err(0xE) <- RT.GV boot-signature 7C436110-AB2A-4BBB-A880-FE41995C9F82
02:104 00:058 AAPL: #[EB|WL] 0 0 0x01 0x01  23 0x0E
02:164 00:059 AAPL: #[EB.H.LV|!] Err(0xE) <- RT.GV boot-image-key 7C436110-AB2A-4BBB-A880-FE41995C9F82
02:228 00:063 AAPL: #[EB|WL] 0 0 0x01 0x01  24 0x0E
02:285 00:057 AAPL: #[EB.H.LV|!] Err(0xE) <- RT.GV boot-image 7C436110-AB2A-4BBB-A880-FE41995C9F82
02:343 00:058 AAPL: #[EB.H.LV|!] Err(0xE) <- RT.SV- boot-signature 7C436110-AB2A-4BBB-A880-FE41995C9F82
02:404 00:061 AAPL: #[EB.H.LV|!] Err(0xE) <- RT.SV- boot-image-key 7C436110-AB2A-4BBB-A880-FE41995C9F82
02:461 00:057 AAPL: #[EB.H.LV|!] Err(0xE) <- RT.SV- boot-image 7C436110-AB2A-4BBB-A880-FE41995C9F82
02:521 00:059 AAPL: #[EB|H:NOT]
02:580 00:059 AAPL: #[EB|SB:P] 0x0
02:635 00:054 AAPL: #[EB|LIMG:DP] Acpi(PNP0A03,0)/Pci(1A|0)/Usb(1, 0)/Usb(3, 0)/HD(Part2,SigE899DDB1-85DA-4706-97E5-B09E0F883C9F)
02:680 00:045 AAPL: #[EB|LIMG:FP] \System\Library\CoreServices\boot.efi
02:741 00:061 AAPL: #[EB|LIMG:OPT] 
02:801 00:059 AAPL: #[EB|RPS] 0 0 0
02:861 00:059 AAPL: #[EB.OPT.LXF|F] <"\\System\\Library\\CoreServices\\com.apple.Boot.plist">
02:919 00:058 AAPL: #[EB.LD.LF|IN] 0 1 <"\\System\\Library\\CoreServices\\com.apple.Boot.plist"> <"0">
02:978 00:058 AAPL: #[EB.LD.OFS|OPEN!] Err(0xE) <"\\System\\Library\\CoreServices\\com.apple.Boot.plist">
03:037 00:058 AAPL: #[EB.OPT.LXF|LF!] Err(0xE)
03:094 00:056 AAPL: #[EB.OPT.LXF|F] <"Library\\Preferences\\SystemConfiguration\\com.apple.Boot.plist">
03:154 00:060 AAPL: #[EB.LD.LF|IN] 0 1 <"Library\\Preferences\\SystemConfiguration\\com.apple.Boot.plist"> <"0">
03:217 00:062 AAPL: #[EB|KF] <"root-dmg=file:///BaseSystem/BaseSystem.dmg">
03:279 00:061 AAPL: #[EB|MBA:CL] <"">
03:340 00:061 AAPL: #[EB|MBA:NV] <"-v keepsyms=1 debug=0x100 npci=0x2000 alcid=28 -amd_no_dgpu_accel slide=103">
03:399 00:058 AAPL: #[EB|MBA:KF] <"root-dmg=file:///BaseSystem/BaseSystem.dmg">
03:459 00:059 AAPL: #[EB|MBA:OUT] <"-v keepsyms=1 debug=0x100 npci=0x2000 alcid=28 -amd_no_dgpu_accel slide=103 root-dmg=file:///BaseSystem/BaseSystem.dmg">
03:515 00:056 AAPL: #[EB|LOG:VERBOSE] 2024-08-27T16:51:56
03:574 00:059 AAPL: #[EB.CSR.S|VAR] 0x00000040
03:633 00:058 AAPL: #[EB|OPT:BM] 0x82
03:742 00:109 AAPL: #[EB.OPT.LXF|F] <"\\System\\Library\\CoreServices\\PlatformSupport.plist">
03:802 00:060 AAPL: #[EB.LD.LF|IN] 0 1 <"\\System\\Library\\CoreServices\\PlatformSupport.plist"> <"0">
03:864 00:061 AAPL: #[EB|P:CPR] N
03:921 00:056 AAPL: #[EB|P:MPI] N
03:980 00:058 AAPL: #[EB|P:BPI] N
04:039 00:058 AAPL: #[EB.OPT.RKS|!] Err(0xE) <- BS.LocP EDB4A040-6D8A-11EC-8FAD-3E22FB93ADCF
04:097 00:058 AAPL: #[EB|KMR] 354680832
04:154 00:056 AAPL: #[EB.CS.CSKSD|+]
04:215 00:060 AAPL: #[EB.CS.CSKSD|!] Err(0xE) <- RT.GV boot-info-payload 8D63D4FE-BD3C-4AAD-881D-86FD974BC1DF
04:282 00:066 AAPL: #[EB.G.CS|-?] Ok(0)
04:341 00:059 AAPL: #[EB.LD.LF|IN] 0 1 <"<null string>"> <"1">
04:458 00:116 AAPL: #[EB.B.SBS|SZ] 723512
04:535 00:077 AAPL: #[EB|B:SHA] <cda59506357e6af41c4bdd82f73d008e3b7a1932>
04:602 00:066 AAPL: #[EB.WL.PWLFNV|!] Err(0xE) <- RT.GV wake-failure 7C436110-AB2A-4BBB-A880-FE41995C9F82
04:663 00:061 AAPL: #[EB.WL.DT|!] Err(0xE) <- EB.WL.PWLFNV
04:723 00:060 AAPL: #[EB.WL.PWLFRTC|NONE]
04:785 00:061 AAPL: #[EB.WL.DT|!] Err(0xE) <- EB.WL.PWLFRTC
04:848 00:063 AAPL: #[EB.LD.LKC|D] <"System\Library\KernelCollections\BootKernelExtensions.kc.development">
04:924 00:075 AAPL: #[EB.LD.OFS|OPEN!] Err(0xE) <"System\\Library\\KernelCollections\\BootKernelExtensions.kc.development">
04:986 00:061 AAPL: #[EB.LD.LKC|R.2] <"System\Library\KernelCollections\BootKernelExtensions.kc">
11:855 06:869 AAPL: #[EB.LD.LKFS|-?] Ok(0)
11:928 00:072 AAPL: #[EB.LD.LKC|-?] Ok(0)
11:990 00:061 AAPL: #[EB|BST:REV1]
12:052 00:062 AAPL: #[EB|CSR:OUT] 0x00000040
12:113 00:061 AAPL: #[EB.BST.FBS|+]
12:179 00:066 AAPL: #[EB.BST.FBS|ADSZ] 0
12:243 00:063 AAPL: #[EB.BST.FBS|KSSZ] 0
12:309 00:066 AAPL: #[EB|SB:SBGMFNS] x86legacyap.im4m
12:373 00:063 AAPL: #[EB|RH:PF] usr\standalone\OS.dmg.root_hash
12:438 00:064 AAPL: #[EB|RH:MF] <"usr\\standalone\\OS.dmg.root_hash.x86legacyap.im4m">
12:502 00:064 AAPL: #[EB.LD.LF|IN] 0 1 <"usr\\standalone\\OS.dmg.root_hash"> <"0">
12:564 00:062 AAPL: #[EB.LD.OFS|OPEN!] Err(0xE) <"usr\\standalone\\OS.dmg.root_hash">
12:627 00:062 AAPL: #[EB.RH.LRH|P!] Err(0xE) <- EB.LD.LF
12:690 00:063 AAPL: #[EB.BST.FBS|!] Err(0xE) <- EB.RH.LRH
12:752 00:061 AAPL: #[EB|LOG:DT] 2024-08-27T16:52:06
12:816 00:063 AAPL: #[EB|LOG:EXITBS:START] 2024-08-27T16:52:06

 

 

 

 

EFI only working with Big Sur.

EFI.zip

Edited August 27 by Harry Hard

[BillDH2k]

@Harry Hard.  Not being able to pay attention to the forum lately, so sorry for my late response. Dual CPUs configuration with Z820 will have trouble booting properly under Ventura/Sonoma (I never succeeded myself, except single CPU. Random lockup during booting).  I'd suggest that you either stay with Monterey or working with single CPU. 

 

Your EFI is missing the version control settings for loading the proper kext. I'd suggest that you start with my EFI only, and make sure it can run/boot, at the minimum, Monterey. Once working with Monterey, then you can consider moving up to Ventura/Sonoma, but you have to downgrade to single CPU.

Edited September 25 by BillDH2k

[antonio.clb]

10 hours ago, BillDH2k said:

@Harry Hard.  Not being able to pay attention to the forum lately, so sorry for my late response. Dual CPUs configuration with Z820 will have trouble booting properly under Ventura/Sonoma (I never succeeded myself, except single CPU. Random lockup during booting).  I'd suggest that you either stay with Monterey or working with single CPU. 

 

Your EFI is missing the version control settings for loading the proper kext. I'd suggest that you start with my EFI only, and make sure it can run/boot, at the minimum, Monterey. Once working with Monterey, then you can consider moving up to Ventura/Sonoma, but you have to downgrade to single CPU.

 

My Z620 works well with dual CPU in Sonoma 14.6. During installation (and maybe updates), in addition to disabling GPU acceleration, I have to physically disconnect the second CPU. Unfortunately, CPU physical disconnection cannot be done on Z820.