Ventura does not have that 210 kext anymore. Please read my post above (and try it yourself?). Also with id F3158086 it does not make a connection. But you will be able to find more about that in the forum.
Edit: Thank you
@Middleman! I have found the solution you was trying to tell me.
The link:
I225-V_FIX.md It's Option 1 for me.
Under Monterey, i225V worked for me with DeviceProperties F2158680 and no other LAN hacks. This charged in Ventura and no longer works. I lost i225V ethernet ports with upgrade to macOS 13 Ventura. No ethernet devices detected at all—Asus z590 Hero dual i225v Open Core 0.8.5:
OPTION 1 works for me
EDIT: Native Ventura i225V also works for me following CaseySJ config for AppleVTD. My i225V are RevisionID 3, per requirements.
BACKGROUND
There seems to be several parts to this story—I am just waving my hands here:
A) changes in how IONetworkingKit drivers are supplied in Monterey and Ventura which pertain to the use of boot args dk.e1000=0 and e1000=0. Ventura has i225V native, but the drivers are bundled differently which prevents previous hacks from working.
B) details on how vendor / device type information in coded into some controllers that doesn't play well for z490+ since Monterey. E.g., F2150000 vs F2158680 (and variants).
C) i225V firmware revision—not sure how this plays with (2) but it needs to be Revision ID 3+. You can look this up in System Information > Ethernet: Revision ID = 0x0003 or higher and to disable all other i225V hacks including SSDTs, kexts, bootargs (no dk.e1000=0, no e1000=0), no DeviceProperties, etc.
D) Lore related z690 Alder Lake option of enabling AppleVTD to assist with devices connected by Thunderbolt (inc. Ethernet). This prolly has to do with how v-TD supports DMA for fast device data transfers needed by 2500BT.
*** It turns out AppleVTD is also needed for native i225V support. CaseySJ describes how to get AppleVTD configured on his z690 thread.
The above link describes two options to work around. There's a "corrected header" SSDT and Monterey kext injection procedure (OPTION 1) and a firmware update procedure that can allow Ventura i225V kexts to attach (OPTION 2).
OPTION 1 just changes OC config to get the Monetery driver injected.
OPTION 2 describes a way to use Open Core to do the ethernet controller firmware update, but you still need the blob,
which has gone missing from its source at InsanelyMac.
[EDIT CaseySJ reposted the blob]
Hello I have tried to enable my i225-V Ethernet port and while I think Ive done everything stated in the above posting I cant get it to grab an IP address. Shows up good in my system profile but still no IP, it stays red. If someone could verify my setting Id really appreciate it. I have enabled...
www.tonymacx86.com
You might be able to get your i225V firmware updated using your board vendor's downloads for Windows. The ethernet driver update may include a firmware component. You'll need to investigate.
AppleVTD is the combination of config.plist DisableIOMapper option, a DMAR ACPI, and enabling v-TD in BIOS:
A little confused. I thought the idea was to find a SN that is legit but not registered to get iCloud working? Or am I wrong, you need to generate an incorrect none apple SN of a none existing mac? correct, do not use a valid serial number
www.tonymacx86.com
MY SITUATION
I have i225V Revision 3, so native should work. B
ut when I try Ventura native i225V, my i225V is detected but won't connect, and my system is unstable. (Maybe I made a mistake idk)
*** EDIT: SWITCHED TO OPTION-2 NATIVE
*** Corrected error in AppleVTD DMAR config per instructions above and i225V works with Ventura natively.
HERE'S THE RUNDOWN ON OPTION-1
When I inject the Monterey kext as described at above link OPTION 1, my ethernet works and my Ventura system is stable.
• You need a copy of
IONetworkingFamily.kext ->
AppleIntelI210Ethernet.kext from Monterey.
—This is something you'll have to find, hopefully from a backup. The link referenced in the write-up above no longer works.
• Add the
SSDT-I225V.aml from the links above to
EFI > OC > ACPI
• Add
AppleIntelI210Ethernet.kext to
EFI > OC > Kexts
• Update your config.plist accordingly under
ACPI > Add and
Kernel > Add
(See attached EFI, i225V Inject folder)
Also...
— Set kernel config entry
MinKernel field to
22.0.0, if multi-booting various macOS
— Set bootarg
e1000=0 (for Ventura/Monterey)
— Remove other
DeviceProperties pertaining to i225V ethernet
This was an easy config update and after these changes the system came right up with pre-upgrade Ethernet config working in System Settings...
DOUBLE CHECK your Network settings, as my custom DNS entries were reset. I cannot say if 2.5G works because I only have 1000BT.
Here's the above-quoted link again for all the gory details on the options:
OpenCore EFI for running macOS on Gigabyte Z490 Visison G with an Intel i9 10850K Processor. Supported macOS: Mojava, Catalina, Big Sur, Monterey and Ventura - 5T33Z0/Gigabyte-Z490-Vision-G-Hackint...
github.com
See CaseySJs posts starting with this one...
@P1LGRIM Well, that got me in! Thank you! No WiFi or Bluetooth, of course, but the problem is now that it’s not recognizing my wired connection, either. Is there a kext or something I can use to get the wired connection recognized? I can live without WiFi or Bluetooth until I can get those...
www.tonymacx86.com
And see his Alder Lake Golden Build post #1 for how to approach i225V native, if you have the right Revision ID.
@CaseySJ Thank you so much for the detailed instruction. It is super helpful. I was able to get my mod working (on OC0.8.2) but I am having problem getting my builtin Thunderbolt working. I have tried the RIDGE-RP05-V2.aml or download the compiled aml file from Hackindrom ("Gigabyte GC-Titan...
www.tonymacx86.com
Eternal thanks to 5T33Z0 on Github for the hacks, to
@Middleman for getting the word out here, and to
@CaseySJ for his explanations of how to run i225V natively in Monterey and Ventura.
.
