Contribute
Register

Stork's MyHero II Build: ASUS ROG MAXIMUS Z370 HERO X - i7-8700K - AMD RX 580 - Thunderbolt 3

Hi,

I just did a massive upgrade;
I upgraded from Catalina / Clover to Ventura / OpenCore. I also updated the motherboard BIOS to version 2701. OCAT made it all so easy; Based on the 'Desktop_8th-9thGen_Coffee_Lake_iMac19,1.plist' configuration file in OCAT's database, I made a new EFI, OC 0.8.9.
My old custom SSDT files are working fine in the new build.
Things I had to change to make things work: I now use BlueToolFixup.kext instead of BrcmBluetoothInjector.kext (is causing OC to tilt :))
I also had to switch from Samsung to WD Blue NVMe drives. Ventura does not like Samsung's NVMe drives. Even the separate Windows NVMe drive was causing Ventura to crash. For the XFX RX 6800XT MERC319, I had to add the boot argument agdpmod=pikera.

All is working zippy and graphics are much better in Ventura (they seem sharper, also using the RX580)

I think it's good to go for another four years :)
 

Attachments

  • Screenshot 2023-02-19 at 12.10.40.png
    Screenshot 2023-02-19 at 12.10.40.png
    75.5 KB · Views: 60
  • Screenshot 2023-02-19 at 12.10.47.png
    Screenshot 2023-02-19 at 12.10.47.png
    115.6 KB · Views: 64
  • Screenshot 2023-02-19 at 12.17.20.png
    Screenshot 2023-02-19 at 12.17.20.png
    286.4 KB · Views: 54
  • Screenshot 2023-02-19 at 12.17.29.png
    Screenshot 2023-02-19 at 12.17.29.png
    281.6 KB · Views: 48
  • Screenshot 2023-02-19 at 12.17.39.png
    Screenshot 2023-02-19 at 12.17.39.png
    310.7 KB · Views: 58
I updated first from 12.6.1 to 12.6.6 and then to 13.4. There were no problems. I should note that I had upgraded my graphics card to a RX 6600 XT, so I am not using the RX 580. I have my macOS running for a few days now and everything works nicely as before. I have to say that I like Stage Manager and the way it removes visual clutter. I even hide my menu bar these days. Using Stage Manager with Mission Control seems sensible if you can't find a window.

I took some time consuming precautions before updating. I updated to the newest version of Open Core, and I updated the kexts, drivers and aml-files where possible. I compared my old and the new OpenCore sample config.plist line by line and made changes in the new config.plist where I had also made changes in the old file. I also updated to the combined SSDT-EC-USBX-DESKTOP.aml as I had separate files for EC and USBX before. Of course I also made a copy of my old EFI-folder and I made a backup of the whole drive using SuperDuper to an internal spinning disk.

That said, this disk which I installed for the update seems to never spin down for some reason. :confused:
 
I updated first from 12.6.1 to 12.6.6 and then to 13.4. There were no problems. I should note that I had upgraded my graphics card to a RX 6600 XT, so I am not using the RX 580. I have my macOS running for a few days now and everything works nicely as before. I have to say that I like Stage Manager and the way it removes visual clutter. I even hide my menu bar these days. Using Stage Manager with Mission Control seems sensible if you can't find a window.

I took some time consuming precautions before updating. I updated to the newest version of Open Core, and I updated the kexts, drivers and aml-files where possible. I compared my old and the new OpenCore sample config.plist line by line and made changes in the new config.plist where I had also made changes in the old file. I also updated to the combined SSDT-EC-USBX-DESKTOP.aml as I had separate files for EC and USBX before. Of course I also made a copy of my old EFI-folder and I made a backup of the whole drive using SuperDuper to an internal spinning disk.

That said, this disk which I installed for the update seems to never spin down for some reason. :confused:
I have no idea on what to do for drive that doesn't spin down. I take it that the drive is HDD (spinner)?

Let's get @CaseySJ and @pastrychef to put their Mk1 eyeballs on this problem. Thanks guys.
 
I have no idea on what to do for drive that doesn't spin down. I take it that the drive is HDD (spinner)?
Yes, it is a spinning hard drive. I exempted it from Time Machine. It seems some task accesses it sometimes. I tried figuring out what accesses it with FSMonitor, but it is either not useful or I don't know how to use it.
 
Thanks @Stork for your engagement.

I noticed that Spotlight accesses my spinning backup drive, so I excluded it from Spotlight. That didn't solve the problem. It seems macOS treats my backup drive like it is a system drive.


I forgot to mention two little snags and one boon after updating to Ventura 13.4:

- Private Relay does not work for me anymore: I get the message "Software installed on this Mac is incompatible with Private Relay." That software might be Little Snitch or AdGuard.

- A message warned me about mismatched memory modules. For some reason macOS thinks that I have only one module out of four installed. I have in fact two memory modules installed. I use MacPro7,1 as the hardware model, which probably enables this kind of warning.

- Searching in Apple Mail works again for me and quickly at that. When it didn't work I used macOS 12.6.1.
 
Using RestrictEvents.kext should fix the incorrect memory issue, when using the MacPro7,1 SMBIOS.
 
Hi all, I just created a new EFI for my Maximus Hero X for sonoma, I was able to install it, but the system keeps rebooting. Can someone help me figure out what the problem is?
Or maybe you can share your EFI folder that works with Sonoma. That would be great...

EDJMQozWwAAaUPT.jpg



Thanx A LOT!!!
 

Attachments

  • EFI.zip
    9.9 MB · Views: 19
First thing of note in your EFI is the contents of your /EFI/OC/ACPI folder. You have two SSDT's in the folder that you don't need with a Z370 Coffee Lake system - SSDT-PMC.aml and SSDT-PNLF.aml.

SSDT-PMC.aml is only required on Z390 and other real Coffee Lake (CFL) systems. It is not required on the Z370 system because it a cross between a Kaby Lake and a Coffee Lake system, that uses the Intel 200-series chipset, not the CFL 300-series chipset.

SSDT-PNLF.aml is only required for laptops, enabling of the non-Apple display.

Your /EFI/OC/Drivers folder is lacking a pair of entries that I consider essential. These are the OpenCanopy.efi and ResetNvramEntry.efi drivers.

OpenCanopy.efi is essential when you want to use the OC GUI boot screen.
ResetNvramEntry.efi is essential when you need to clear the old Nvram entries from the system, before booting with a revised or updated OC setup.

I would also swap OpenHfsPlus.efi for HfsPlus.efi as the latter is a faster and more accomplished HFS+ driver.

Your /EFI/OC/Kexts folder is set at the bare minimum for booting macOS, but is missing the Ethernet kext and contains a kext that is only required for a laptop (theme going on here!).

Your ROG MAXIMUS X HERO Z370 motherboard contains the Intel I219V Ethernet controller. So you should add IntelMausi.kext to your OC setup.

VoodooPS2Controller.kext is a laptop driver for built-in laptop keyboards and trackpads. It is not meant for use on a desktop system.

Your Resources folder is empty, bar 4 x empty sub-folders. If you like the Text picker list that is fine. If you want your Hack to boot more inline with a real Mac then you need to use a populated Resources folder, which can be obtained from the Acidanthera Github repository linked below.


The Resources folder is contained within the OCBinaryData-Master folder.

I have attached a revised EFI, based on my Asus Z370 system for you to try. See if this improves how your Hack works.

The two screenshots below show your current EFI folder contents and the contents of the revised EFI I would recommend you use with your system.

Screenshot 2023-10-24 at 19.30.21.png Your Current EFI folder contents

Screenshot 2023-10-24 at 19.30.35.png Revised EFI folder contents.

Along with these changes I have made a number of other edits to your config.plist, to better match with the Coffee Lake OC guide. Including adding the DeviceProperties for your system IGPU to run in headless mode, with the Polaris dGPU doing all the graphics processing.

Test revised EFI:
I would recommend you do the following:
  1. Get hold of a spare USB pen drive.
  2. Erase the drive as HFS+ & GUID partition map in Disk Utility.
  3. Mount the EFI partition on the USB pen drive and copy the attached EFI folder to the EFI partition.
  4. Reboot your system.
  5. Boot your system from the USB pen drive, use F8 key when system boots to access the Bios boot menu and select the USB drive.
  6. When you arrive on the OC GUI boot screen, press the 'Spacebar' to unhide the Tools and Drivers present in your OC setup.
  7. Select the ResetNvramEntry.efi icon. This will automatically reboot your system and remove the current NVRAM entries. Allowing the NVRAM entries present in the revised EFI to be used.
  8. Reboot via the USB pen drive and boot macOS.
See what happens. Post a photo of the Verbose text if the system kernel panics.

Bios:
All this assumes you have set your Bios correctly to work with macOS. I have pasted the Bios settings you should be using with an Intel system below.

Intel BIOS settings​

  • Note: Most of these options may not be present in your firmware, we recommend matching up as closely as possible but don't be too concerned if many of these options are not available in your BIOS

Disable​

  • Fast Boot
  • Secure Boot
  • Serial/COM Port
  • Parallel Port
  • VT-d (can be enabled if you set DisableIoMapper to YES)
  • Compatibility Support Module (CSM) (Must be off in most cases, GPU errors/stalls like gIO are common when this option is enabled)
  • Thunderbolt (For initial install, as Thunderbolt can cause issues if not setup correctly)
  • Intel SGX
  • Intel Platform Trust
  • CFG Lock (MSR 0xE2 write protection)(This must be off, if you can't find the option then enable AppleXcpmCfgLock under Kernel -> Quirks. Your hack will not boot with CFG-Lock enabled)

Enable​

  • VT-x
  • Above 4G Decoding
  • Hyper-Threading
  • Execute Disable Bit
  • EHCI/XHCI Hand-off
  • OS type: Windows 8.1/10 UEFI Mode (some motherboards may require "Other OS" instead)
  • DVMT Pre-Allocated(iGPU Memory): 64MB or higher
  • SATA Mode: AHCI
USB configuration:
You don't have one! You need to follow the USB configuration guide linked below as a matter of urgency, as you may have issues with Sleep/Wake/Shutdown etc. if you don't have a custom configuration for your USB ports.

 

Attachments

  • EFI.zip
    10.7 MB · Views: 26
Back
Top