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

[nimrod]

I am running this build for quite some time now and I am absolutely happy with it.
Some things I noticed (currently running Ventura 13.1):
It crashes when Ethernet is connected. I tried pretty much all settings I could find without any luck.
WiFi sometimes does not work when it was used in Windows before. As I am switching a lot this was really annoying.
So I solved it by disabling Ethernet in this build and running Windows with only Ethernet. No problems with this since.

And the Bluetooth sometimes gets stuck or stops working when listening to audio over it. Seeing a "Hash mismatch" and suggestion to reinstall. This seems to be a common problem with bluetooth.

 

[trs96]

Some things I noticed (currently running Ventura 13.1):
It crashes when Ethernet is connected. I tried pretty much all settings I could find without any luck.

Have you seen this post about the Apple e1000 Ethernet driver in Ventura ?
The author says to try this boot argument:

e1000.fi0=0x15f3

Z790 Chipset & Raptor Lake

Of course. This is a very new motherboard, and few look at the corporate/server/workstation Qx70/C2x2/C2x6/Wx80 chipsets ('x' being the generation counter) for buying motherboards—although there's a sizeable community of happy users of 'Q' chipsets in Dell Optiplex and similar pre-builds. W680...

www.tonymacx86.com

 

[UtterDisbelief]

I am running this build for quite some time now and I am absolutely happy with it.
Some things I noticed (currently running Ventura 13.1):
It crashes when Ethernet is connected. I tried pretty much all settings I could find without any luck.
WiFi sometimes does not work when it was used in Windows before. As I am switching a lot this was really annoying.
So I solved it by disabling Ethernet in this build and running Windows with only Ethernet. No problems with this since.

And the Bluetooth sometimes gets stuck or stops working when listening to audio over it. Seeing a "Hash mismatch" and suggestion to reinstall. This seems to be a common problem with Bluetooth.

Hi there.

Follow-up on what @trs96 mentions above for Ethernet. If you decided to disable the Ethernet chip you have to ensure that the wireless IP is set as "en0" in the Network section of System Report, for the App Store to function. This is how MacBooks handle the lack of ethernet capability.

In my usage of the system, although I extensively ran and recommend Big Sur, I did test Monterey and Ventura. I had heard (via @CaseySJ IIRC) about the e1000 driver issues with Ventura, affecting a few boards with the same or similar chipsets.

Bluetooth has not been any problem for me using the latest OpenIntelWireless driver releases, though clearly the ones for Ventura are still at the beta stage. Make sure you use the correct one. I regularly streamed to my HomePod while using the mouse and Internet connection etc., with no issues.

I believe it is a known problem - and I can confirm it - that you may have problems with both wireless and bluetooth straight after running Windows. This is because the Windows drivers "flash", or try to, the wireless hardware. Usually a full power cycle will restore macOS reliability.

 

[rkwallace]

I've been trying to install Ventura to this new Hackintosh all day and cannot get past this error that crashes my install usb. Instead of just copying someone else's EFI I built mine from scratch. The only difference I'm using a Intel Core i7-11700KF CPU. Any assistance is appreciated.

 

[UtterDisbelief]

I've been trying to install Ventura to this new Hackintosh all day and cannot get past this error that crashes my install usb. Instead of just copying someone else's EFI I built mine from scratch. The only difference I'm using a Intel Core i7-11700KF CPU. Any assistance is appreciated.

Hi there.

Yours is actually quite a different build from the one in this thread with its 11th gen CPU and m.2 SSD etc.

First thing I notice that will cause a problem is that you are using the iMacPro1,1 system-definition, whereas the USBPorts.kext uses iMac18,3 which means the kext will not work.

The only other obvious thing is that maybe you could download the very latest AirportItlwm.kext. Although the kexts change little, the newest appears to have different release date to yours, despite having the same byte-count. We had to use the beta for quite a while.

 

[rkwallace]

Hi there.

Yours is actually quite a different build from the one in this thread with its 11th gen CPU and m.2 SSD etc.

First thing I notice that will cause a problem is that you are using the iMacPro1,1 system-definition, whereas the USBPorts.kext uses iMac18,3 which means the kext will not work.

The only other obvious thing is that maybe you could download the very latest AirportItlwm.kext. Although the kexts change little, the newest appears to have different release date to yours, despite having the same byte-count. We had to use the beta for quite a while.

First of all I would like to thank you for responding to my post. I followed you instructions and now my installation USB is stopping at the line listed below. Please note, the AirportItiwm.kext i was using is v2.2.0 (the latest version).
I went over the BIOS settings again to no avail, this got me stumped. I'm still researching and will respond if I cannot find a fix.

 

[Middleman]

First of all I would like to thank you for responding to my post. I followed you instructions and now my installation USB is stopping at the line listed below. Please note, the AirportItiwm.kext i was using is v2.2.0 (the latest version).
I went over the BIOS settings again to no avail, this got me stumped. I'm still researching and will respond if I cannot find a fix.

Hi @rkwallace,

As I too have a Gigabyte Z590I board, I thought to give a helping hand also, so I had a look at your EFI setup and made a number of observations and corrections.

1) First of all I noticed you did not have your Intel UHD 630 IGPU settings set properly. Not having npci=0x2000 in the boot-arg and no IGPU device properties in the PCI device list means the system will not detect your GPUs at all, so I've added those in for you to the config.

2) Incorrect pointer settings, your mouse pointer was set to ASUS under UEFI > Input > PointerSupportMode.
This was probably what gave you the invalid pointer error earlier. It should be empty.

3) Lack of required APCI settings and ACPI/kernel patches. You only had about 3 ACPI tables added when it requires about 14 tables to boot Ventura on the Z590I, so I've added those in for you also.

4) Empty ROM value under Platform Info > Generic ROM. Without a correct ROM value your system cannot boot.
I have temporarlly added 11 22 33 44 66 as the value, but it either needs to be generated.

5) Required drivers, tools and resources folder missing. OpenCanopy was installed but disabled meaning you couldn't use the boot selector properly, and your Tools selection only had CleanNVRAM.efi and no OpenShell.efi either. ResetNVRAM was also missing and is actually the tool you need for proper cache clearing for the EFI, not CleanNVRAM. The Reset function differs from the Clean one.

So anyways I've made all the corrections above for you. The platform is now set to use iMac20,2. Hopefully it should boot Ventura okay.

 

[UtterDisbelief]

First of all I would like to thank you for responding to my post. I followed you instructions and now my installation USB is stopping at the line listed below. Please note, the AirportItiwm.kext i was using is v2.2.0 (the latest version).
I went over the BIOS settings again to no avail, this got me stumped. I'm still researching and will respond if I cannot find a fix.

Hi there

*Before* you go much deeper, the first thing I would do with your own EFI is change the Misc/Security/SecureBootModel setting in your config.plist from "Default" to "Disabled".

That should make a difference.

 

[rkwallace]

Hi @rkwallace,

As I too have a Gigabyte Z590I board, I thought to give a helping hand also, so I had a look at your EFI setup and made a number of observations and corrections.

1) First of all I noticed you did not have your Intel UHD 630 IGPU settings set properly. Not having npci=0x2000 in the boot-arg and no IGPU device properties in the PCI device list means the system will not detect your GPUs at all, so I've added those in for you to the config.

2) Incorrect pointer settings, your mouse pointer was set to ASUS under UEFI > Input > PointerSupportMode.
This was probably what gave you the invalid pointer error earlier. It should be empty.

3) Lack of required APCI settings and ACPI/kernel patches. You only had about 3 ACPI tables added when it requires about 14 tables to boot Ventura on the Z590I, so I've added those in for you also.

4) Empty ROM value under Platform Info > Generic ROM. Without a correct ROM value your system cannot boot.
I have temporarlly added 11 22 33 44 66 as the value, but it either needs to be generated.

5) Required drivers, tools and resources folder missing. OpenCanopy was installed but disabled meaning you couldn't use the boot selector properly, and your Tools selection only had CleanNVRAM.efi and no OpenShell.efi either. ResetNVRAM was also missing and is actually the tool you need for proper cache clearing for the EFI, not CleanNVRAM. The Reset function differs from the Clean one.

So anyways I've made all the corrections above for you. The platform is now set to use iMac20,2. Hopefully it should boot Ventura okay.

I would like to thank you for your suggestions. I truly appreciate you explaining all the changes involved. It took me awhile to get back because I wanted to go through them all and understand what was taking place instead of just dropping in the corrected EFI.

Almost everything worked. I did get Ventura OS installed. However, I had one issue. If you look at the attached picsy you will notice the color is off. Actually its worst than the pics. I'm using a XFX Radeon RX580 (8gb) graphics card. I know its not a defect of the graphics card since this only occurs with this EFI and not others. Also, it works perfectly in Windows. Please note, this CPU does not have an iGPU. Any other suggestions is appreciated.

 

[rkwallace]

Hi there

*Before* you go much deeper, the first thing I would do with your own EFI is change the Misc/Security/SecureBootModel setting in your config.plist from "Default" to "Disabled".

That should make a difference.

Done, thanks for the suggestion.