Gigabyte Z490 Vision D (Thunderbolt 3) + i5-10400 + AMD RX 580

[CaseySJ]

** Ventura Public Beta Users **​

UPDATE:
It is not necessary to use SSDT-I225V.aml or SSDT-I225V-NO-DTGP.aml.

To enable the Intel i225-V Ethernet port, please follow this procedure curated by @NCMacGuy -- but it's okay to skip the SSDT mentioned in the procedure:

Gigabyte Z690 Aero G + i5-12600K + AMD RX 6800 XT

Wow! That was last May! I have a hard time remembering what I did yesterday! Unfortunately, since I'm on OC 0.8.2, I don't know what I/we did. Sorry. So you were able to fix it?

www.tonymacx86.com

 

[HenryM]

Are you sure you really need the SSDT? have you tried it without? We must also necessarily distinguish between Revision 2 and 3 of the i225-v.

 

[Feartech]

** Ventura Public Beta Users **​

To enable the Intel i225-V Ethernet port, please follow this procedure curated by @NCMacGuy:

Gigabyte Z690 Aero G + i5-12600K + AMD RX 6800 XT

Wow! That was last May! I have a hard time remembering what I did yesterday! Unfortunately, since I'm on OC 0.8.2, I don't know what I/we did. Sorry. So you were able to fix it?

www.tonymacx86.com

And grab the modified SSDT from my post that appears immediately after the procedure.

quick question in regards to the SSDT, there are two instances of:

 If ((Arg0 == ToUUID ("a0b5b7c6-1318-441c-b0c9-fe695eaf949b") /* Unknown UUID */))

would the end user need to replace that with their UUID? or does it not matter?

 

[CaseySJ]

quick question in regards to the SSDT, there are two instances of:

 If ((Arg0 == ToUUID ("a0b5b7c6-1318-441c-b0c9-fe695eaf949b") /* Unknown UUID */))

would the end user need to replace that with their UUID? or does it not matter?

Fortunately this UUID is fixed -- it's an ID known to macOS -- so it applies to all users.

 

[Feartech]

Fortunately this UUID is fixed -- it's an ID known to macOS -- so it applies to all users.

ahh ok, good to know as I have also seen a lot of users using SSDT-SBUS-MCHC.aml which some have the same line of code

 

[CaseySJ]

Are you sure you really need the SSDT? have you tried it without? We must also necessarily distinguish between Revision 2 and 3 of the i225-v.

Good suggestion! Just booted my Asus ROG Strip Z690-i (mini-ITX) system without the SSDT and the i225-V port is still functioning. I've updated the previous post.

 

[HenryM]

In relation to the i225-v and AppleVTD, a lot of confusion is created by some at the insanelymac forums.

 

[MacArthur]

Hi all and @CaseySJ
I did a lot of home work since my previous posts saying that my Ethernet port was not working properly.
he is the situation now:
Monterey and Ventura are now working on Ethernet with OpenCore 0.8.3. this is fine !
I am trying to enable Wifi (working perfectly on Monterey with this EFI) on Ventura.
So far it's not working.
as @CaseySJ recommended I downloaded the alpha version of the AirportItlwm-Ventura.kext
here is my Kernel set up. did I miss something?
Thanks again for your input.
Cheers

 

[m4rk0]

[..]

• Then look below to see if this driver (kext) is attached:
  • AppleIntel210Ethernet.kext
• If this driver is attached then there's nothing more to do -- everything is correct.
• If a different driver is attached then we need to configure DeviceProperties, specifically device-id should be changed to F3158680.

Thanks a lot, I believe I fixed it

 

[CaseySJ]

Hi all and @CaseySJ
I did a lot of home work since my previous posts saying that my Ethernet port was not working properly.
he is the situation now:
Monterey and Ventura are now working on Ethernet with OpenCore 0.8.3. this is fine !
I am trying to enable Wifi (working perfectly on Monterey with this EFI) on Ventura.
So far it's not working.
as @CaseySJ recommended I downloaded the alpha version of the AirportItlwm-Ventura.kext
here is my Kernel set up. did I miss something?
Thanks again for your input.
Cheers

The screenshot looks correct, but I would not recommend using the Intel Bluetooth drivers from OpenIntelWireless. They're not functioning properly in Monterey and Ventura. I would also suggest disabling BlueToolFixup.kext. Then let's see if Intel WiFi is affected in any way...