UtterDisbelief 20 ITX - Gigabyte Z590i, i5-10600K, 32GB, RX560

[UtterDisbelief]

Wow, thank you so much.
So what would be the best way to actually upgrade? Updating/Changing the EFI and then just installing the system upgrade?

Btw. is there a way to buy you a coffee?

Forget the upgrade question...i will figure it out

Well, I just created a new USB installer stick using the "createinstallmedia" Terminal command you can find on the Ventura beta Installation page. There's a command for the release version too.

Once done I installed the EFI folder attached above, into the USB EFI partition. Then booted the installer.

If you want a totally clean Ventura system just use a new destination drive, or reformat the old (backup first!) using the Disk Utility on the install screen.

Once done just copy the same EFI folder into place on the destination drive EFI partition.

So be aware I did a fresh installation, not an upgrade. In theory just running the installer on an already existing system should not damage data, but you will need the new EFI at some point or Ventura will lock up.

The main differences between the Monterey EFI and the Ventura one are that a newer OpenCore version and kexts are needed to achieve boot. For example using the older AirportItlwm.kext will freeze Ventura.

 

[nimrod]

top of every page has a "contribute" link

Actually had to search it haha.
Did a little contribution, not much, but should be enough for a coffee or two.

And @UtterDisbelief I just tried the new EFI with Monterey, but that unfortunately did not work.
Currently I am trying to upgrade directly and will swap out the EFI afterwards.

I noticed you set a specific ProcessorType (1541) in the new EFI. Is that important? Previously it was set to 0 which should be auto detect. And FullNvramAccess seems to be false now.

Will let you know if my upgrade attempt worked

Update:
Yep, just worked. I upgraded from Monterey, went through the setup.
It rebooted 3 times. After the 3rd time the installation crashed when it said "9 minutes remaining".
Then I changed to your new EFI and rebooted. Strangely it didnt install anymore, but now I am running 13.0.
So far everything seems to work.

Thanks again!

 

[UtterDisbelief]

Actually had to search it haha.
Did a little contribution, not much, but should be enough for a coffee or two.

And @UtterDisbelief I just tried the new EFI with Monterey, but that unfortunately did not work.
Currently I am trying to upgrade directly and will swap out the EFI afterwards.

I noticed you set a specific ProcessorType (1541) in the new EFI. Is that important? Previously it was set to 0 which should be auto detect. And FullNvramAccess seems to be false now.

Will let you know if my upgrade attempt worked

Update:
Yep, just worked. I upgraded from Monterey, went through the setup.
It rebooted 3 times. After the 3rd time the installation crashed when it said "9 minutes remaining".
Then I changed to your new EFI and rebooted. Strangely it didnt install anymore, but now I am running 13.0.
So far everything seems to work.

Thanks again!

Glad you figured it out.

Looks like you have almost identical hardware so only memory and drives might have an impact, though I doubt it.

Yes, the EFI was set up specifically for Ventura and not Monterey. Mainly because, as I mentioned, the Monterey version of AirportItlmw.kext would crash Ventura and vice-versa. I could have disabled the kext and left it at that but then the EFI folder wouldn't have been been fully operational.

One thing I didn't include in the EFI/Drivers folder was "ResetNvramEntry.efi" to enable the menu entry for clearing NVRAM. Add it if you need that facility for dual-booting etc.

OpenCore 0.8.5 is still beta and as such each new version offers new, or deprecates old, settings. So for this build I started from scratch with the sample.plist, then added or removed as required. New flags and toggles appear, others go. If you feel the need for a certain setting, change what you need to etc.

Yes, you are correct, I usually use the "wildcard" ProcessorType "0" but thought for this update I'd try the standard OpenCore uses. It worked so I saw no reason to alter it. It's a setting others often miss so removing the worry seemed logical.

Thanks for your support too.

 

[romarcin]

Do you have full igpu acceleration with this 500 mobo? I'm considering to buy Z590i or B560M but without discrete GPU.

 

[Metal]

Do you have full igpu acceleration with this 500 mobo? I'm considering to buy Z590i or B560M but without discrete GPU.

iGPU acceleration does not work on this board, see here for more information regarding Intel Z590 compatibility with macOS: https://dortania.github.io/hackintosh/updates/2021/04/24/rocket-lake.html

Yes, the EFI was set up specifically for Ventura and not Monterey. Mainly because, as I mentioned, the Monterey version of AirportItlmw.kext would crash Ventura and vice-versa. I could have disabled the kext and left it at that but then the EFI folder wouldn't have been been fully operational.

Seems like a great build! Having been a few months since your last revision, do you have any improvements/updates to share? Thanks!

 

[UtterDisbelief]

iGPU acceleration does not work on this board, see here for more information regarding Intel Z590 compatibility with macOS: https://dortania.github.io/hackintosh/updates/2021/04/24/rocket-lake.html


Seems like a great build! Having been a few months since your last revision, do you have any improvements/updates to share? Thanks!

Hi there. Thanks for your post.

This has been a rock-solid build. All I can add really is that Big Sur seems the best fit.

I've not had any problems with the later OSs particularly, but slightly older software and apps have been less reliable since Big Sur. YMMV.

We have to remember the latest Intel chipset Apple used was the 400-series.

 

[Superbogey]

@UtterDisbelief Ok, I've got to ask why you aren't using NVMe's. They are magnitudes faster than that 560 MB/s SSD you are using. Also, I don't believe one of the earlier poster's comments that one M.2 controller is disabled when using anything older than 11000 series CPUs. That is a function of the chipset, not the CPU Buuut, on mine, each NVMe WILL take away a SATA lane (I have both a Ventura bootable WD NVMe in one M.2 slot AND in the other, a WD booting Windows 11 on my somewhat ancient Z270).

Thirdly, it might be that I'm using a newer AX210 WiFi 6E PCIe add-in card in mine as opposed to your AX200, but I've tried both Itlwm.kext (which MUST HAVE the companion Heliport.app to function) and AiportItlwm.kext (pre-release V2.2.0) and each runs fine. I find the AirportItlwm.kext is smoother since it works with the native WiFi so have stuck with it (really hoping the devs get around to enabling 802.11ax in each of the kexts soon). Other than the issues noted, Bluetooth 5.2 runs fine with IntelBluetoothFirmware.kext, IntelBTPatcher.kext and BlueToolFixup.kext (V2.6.4).

 

[UtterDisbelief]

@UtterDisbelief Ok, I've got to ask why you aren't using NVMe's. They are magnitudes faster than that 560 MB/s SSD you are using. Also, I don't believe one of the earlier poster's comments that one M.2 controller is disabled when using anything older than 11000 series CPUs. That is a function of the chipset, not the CPU Buuut, on mine, each NVMe WILL take away a SATA lane (I have both a Ventura bootable WD NVMe in one M.2 slot AND in the other, a WD booting Windows 11 on my somewhat ancient Z270).

Thirdly, it might be that I'm using a newer AX210 WiFi 6E PCIe add-in card in mine as opposed to your AX200, but I've tried both Itlwm.kext (which MUST HAVE the companion Heliport.app to function) and AiportItlwm.kext (pre-release V2.2.0) and each runs fine. I find the AirportItlwm.kext is smoother since it works with the native WiFi so have stuck with it (really hoping the devs get around to enabling 802.11ax in each of the kexts soon). Other than the issues noted, Bluetooth 5.2 runs fine with IntelBluetoothFirmware.kext, IntelBTPatcher.kext and BlueToolFixup.kext (V2.6.4).

Hi there.

Well the reason I use SATA 2.5" SSDs is because I like swapping and experimenting. I've so far run El Capitan, High Sierra, Mojave, Catalina, Big Sur, Monterey and Ventura on this rig and it's easier to change SATA drives than dig around for the M.2 version. (I do have M.2 drives but rarely use them in a build.)

Next, yes it's true. The top-side M.2 socket *is* specced to work only with 11th gen CPUs. The back-side M.2 socket is fine for either. Having said that I don't use either (see above!).



As for wireless, I've used itlwm.kext in this build to cover all macOS versions I've tested. But AirportItlwm.kext works best for Big Sur onwards, I agree. Remember it is still Ethernet despite appearances!

And incidentally I don't use IntelBTPatcher.kext. No need so far.

(I also discovered that AppleALC.kext rarely works for High Sierra on this build and I have to use VoodooHDA.kext instead).

 

[Superbogey]

Hi there.

Well the reason I use SATA 2.5" SSDs is because I like swapping and experimenting. I've so far run El Capitan, High Sierra, Mojave, Catalina, Big Sur, Monterey and Ventura on this rig and it's easier to change SATA drives than dig around for the M.2 version. (I do have M.2 drives but rarely use them in a build.)

Next, yes it's true. The top-side M.2 socket *is* specced to work only with 11th gen CPUs. The back-side M.2 socket is fine for either. Having said that I don't use either (see above!).

View attachment 563133

As for wireless, I've used itlwm.kext in this build to cover all macOS versions I've tested. But AirportItlwm.kext works best for Big Sur onwards, I agree. Remember it is still Ethernet despite appearances!

And incidentally I don't use IntelBTPatcher.kext. No need so far.

(I also discovered that AppleALC.kext rarely works for High Sierra on this build and I have to use VoodooHDA.kext instead).

Hiya, @UtterDisbelief.

Well, that's a weird CPU "feature" - to say the least. Strange to think that a 7th gen Core CPU handles PCI lanes better than an 10th gen one does.

And not that I was trying to tell you what to do with your rig but I actually do the same with mine - as far as test builds with whatever the newest macOS beta is (or new Windows versions, too). Only I can still do so by booting from NVMe just using its OpenCore to then select the SATA drive in the picker. I've even got a rescue Ventura build and its own OC on an old M.2 mounted on a PCIe card that I'll use to boot from if I manage to bork something on my main NVMe.

With all that being said, it still comes down to whatever works for you. So if it ain't broke, don't fix it.

 

[UtterDisbelief]

Hiya, @UtterDisbelief.

Well, that's a weird CPU "feature" - to say the least. Strange to think that a 7th gen Core CPU handles PCI lanes better than an 10th gen one does.

And not that I was trying to tell you what to do with your rig but I actually do the same with mine - as far as test builds with whatever the newest macOS beta is (or new Windows versions, too). Only I can still do so by booting from NVMe just using its OpenCore to then select the SATA drive in the picker. I've even got a rescue Ventura build and its own OC on an old M.2 mounted on a PCIe card that I'll use to boot from if I manage to bork something on my main NVMe.

With all that being said, it still comes down to whatever works for you. So if it ain't broke, don't fix it.

Hey no worries. We all do things our own way. That's the beauty of Hackintoshing - we get to play around with something that was never designed to happen, and have fun doing it.

For this build if someone wants to improve on the basics, that's great.