[SUCCESS] Gigabyte Designare Z390 (Thunderbolt 3) + i7-9700K + AMD RX 580

[CaseySJ]

@CaseySJ

I copied your EFI to a USB flash, added my serial numbers, and changed ProcessorType to 3841.

I don't have an Aquantia card. Leaving the SSDT for the card active and the ForceAquantiaEthernet selected booting stalled.

Disabling the Aquantia SSDT and unchecking the ForceAquantiaEthernet, but using the balance of your EFI, Ventura boots fully, but the WiFi and ethernet are both disabled.

Apparently there is something in the Aquantia code that provides your success with WiFi and ethernet with Ventura 13.3.

That’s an interesting theory. I can remove the card and see what happens.

Another user posted above that changing System Product Name to MacPro7,1 resolved the issue. This should be done carefully — log out of AppleID before doing so. It can also cause lingering computer name issues in iCloud even when previous system product name is restored.

 

[CaseySJ]

Update:

• Unchecking the Aquantia SSDT and “ForceAquantiaEthernet” quirk disabled the card, but WiFi and Ethernet continue to work normally with AppleVTD in Ventura 13.3
• Physically removing the Aquantia 113C also has no effect — WiFi and other Ethernet ports continue to function properly

My Z490 Vision D, however, has the problem. Its WiFi does not work, but its Ethernet ports continue to work.

I will troubleshoot on the Z490 Vision D. I have already extracted all the kexts from 13.2 and 13.3. Next, I need to compare the right files.

 

[tedyun]

Attached is my OpenCore 0.9.0 EFI for Z390 Designare. Nothing has changed except I've removed my serial numbers from PlatformInfo -> DataHub.

Would be best to copy this to EFI partition of a USB flash drive, boot from USB, then launch Ventura. Of course, copy your serial numbers first into PlatformInfo -> DataHub.

If you have an 8-core or larger CPU, please change ProcessorType in PlatformInfo -> DataHub to 3841 (it is currently 1537 for my 6-core CPU).

Your EFI got me back up and running! Thanks again!

 

[CaseySJ]

Your EFI got me back up and running! Thanks again!

If you're running Ventura 13.3, does WiFi and Ethernet work with AppleVTD enabled?

 

[tedyun]

If you're running Ventura 13.3, does WiFi and Ethernet work with AppleVTD enabled?

Yes, it appears that my rig broke at some point during the 13.3 update process. After I used your EFI to boot my system, it restarted a couple of times, then I landed successfully in Ventura 13.3. I did replace my DeviceProperties and my serials etc. I didn't change these parameters in your EFI, so I believe AppleVTD is enabled. WiFi (Fenvi 919) and Ethernet (on board) are working.

 

[NCMacGuy]

Update:

• Unchecking the Aquantia SSDT and “ForceAquantiaEthernet” quirk disabled the card, but WiFi and Ethernet continue to work normally with AppleVTD in Ventura 13.3
• Physically removing the Aquantia 113C also has no effect — WiFi and other Ethernet ports continue to function properly

My Z490 Vision D, however, has the problem. Its WiFi does not work, but its Ethernet ports continue to work.

I will troubleshoot on the Z490 Vision D. I have already extracted all the kexts from 13.2 and 13.3. Next, I need to compare the right files.

@CaseySJ

I'm using BIOS F9i, i9-9900K, VT-d is enabled. I cleared CMOS and reset the BIOS based on Post 1 instructions to be sure I hadn't changed anything there. I did a full re-install of Ventura 13.3 since I had done the delta update.

I booted from a thumb drive using the CaseySJ EFI folder less the Aquantia-related SSDT and Kernel checkbox. Still no WiFi or Ethernet, which is illogical -- but that's hackintoshing!

I will just use the other workaround that works for me to get WiFi and Ethernet:

Kernel --> Quirks --> DisableIoMapper --> Check ON
ACPI --> Add --> SSDT-DMAR.aml --> Check OFF
ACPI --> Delete --> DMAR --> Check OFF
BIOS Setup --> VT-d --> this can be left ENABLED at all times

 

[CaseySJ]

@CaseySJ

I'm using BIOS F9i, i9-9900K, VT-d is enabled. I cleared CMOS and reset the BIOS based on Post 1 instructions to be sure I hadn't changed anything there. I did a full re-install of Ventura 13.3 since I had done the delta update.

I booted from a thumb drive using the CaseySJ EFI folder less the Aquantia-related SSDT and Kernel checkbox. Still no WiFi or Ethernet, which is illogical -- but that's hackintoshing!

I will just use the other workaround that works for me to get WiFi and Ethernet:

Kernel --> Quirks --> DisableIoMapper --> Check ON
ACPI --> Add --> SSDT-DMAR.aml --> Check OFF
ACPI --> Delete --> DMAR --> Check OFF
BIOS Setup --> VT-d --> this can be left ENABLED at all times

I should mention that on my Z390 Designare I have two 8GB DIMMs at 3200MHz. Not sure if that matters, but it is another difference.

 

[f10]

no success so far:
I tried with a new install of Ventura 13.3 with a macpro7,1 SMBIOS = still no Wifi, no lower ethernet port.
Booted with OC 090 that Casey provided = lower ethernet port does not work, wifi I could not check quickly (I use intel wifi) but I doubt it would work.
I do have my RAM overclocked to 3600 - will try lowering that. EDIT: No change with 2666mhz

 

[SmackAttack]

If you have an 8-core or larger CPU, please change ProcessorType in PlatformInfo -> DataHub to 3841 (it is currently 1537 for my 6-core CPU).

Hey @CaseySJ;
I’m curious, this is not something I’ve ever changed (from 0), and yet my systems all report correctly for my i9-9900k. I did a dive into dortania’s explanation and I’m not sure I’m understanding if it’s necessary or not — perhaps only if using a processor that doesn’t conform to the Apple SMBIOS for the one you’re using? Which is strange, cuz I’m on iMacPro on all, which, of course is Xeon.
Thanks!
J

 

[CaseySJ]

Hey @CaseySJ;
I’m curious, this is not something I’ve ever changed (from 0), and yet my systems all report correctly for my i9-9900k. I did a dive into dortania’s explanation and I’m not sure I’m understanding if it’s necessary or not — perhaps only if using a processor that doesn’t conform to the Apple SMBIOS for the one you’re using? Which is strange, cuz I’m on iMacPro on all, which, of course is Xeon.
Thanks!
J

You're right -- this is not a crucial parameter. For the most part we can ignore it, but if we use RestrictEvents.kext then it matters.