[HELP] Intel I225-V Ethernet - DHCP works but no gateway/routing in Sequoia Recovery | ASUS ROG B650E-I

0xSkalitz

New member
AMD OS X Member
Mar 20, 2026
4
0
1
CPU:
Amd ryzen 7 7800x3d
Hi everyone,

I'm trying to install macOS Sequoia on my AMD Ryzen 7 7800X3D build and I'm stuck on a networking issue during installation. I've spent a lot of time troubleshooting and wanted to share everything I've found so far in case anyone can help.

---

My System Specs:
  • CPU: AMD Ryzen 7 7800X3D
  • Motherboard: ASUS ROG Strix B650E-I Gaming WiFi (Mini-ITX)
  • Ethernet: Intel I225-V (onboard, rev 03)
  • GPU: AMD Radeon RX 470/480/570/580
  • Storage: Samsung NVMe SSD
  • OpenCore version: 1.0.7

---

The Problem:
In macOS Sequoia recovery, the ethernet kext loads fine and DHCP assigns an IP address (192.168.x.x), but I cannot reach the gateway at all. Ping to the gateway returns "No route to host" every time. This means the recovery installer cannot contact Apple's servers.

---

What I've Tried:
  • AppleIGC.kext v1.4d1 — loads correctly, en0 shows up in ifconfig with a valid IP
  • DeviceProperties device-id spoof (F2150000) — tried multiple PCI paths:
- PciRoot(0x0)/Pci(0x1,0x1)/Pci(0x0,0x0)
- PciRoot(0x0)/Pci(0x1C,0x1)/Pci(0x0,0x0)
- PciRoot(0x0)/Pci(0x1C,0x4)/Pci(0x0,0x0)
- PciRoot(0x0)/Pci(0x2,0x1)/Pci(0x0,0x0)/Pci(0xa,0x0)/Pci(0x0,0x0) ← verified from lspci -tv on Linux
  • boot-arg e1000=0
  • DisableIoMapper → false
  • DisableIoMapperMapping → True
  • SecureBootModel → Disabled
  • Manually adding routes and DNS in recovery terminal — no effect
  • networksetup -setdnsservers Ethernet 8.8.8.8 8.8.4.4 — no effect

---

What I Found From Linux (lspci -tv):
The verified PCI path for the I225-V on this board is:
Code:
PciRoot(0x0)/Pci(0x2,0x1)/Pci(0x0,0x0)/Pci(0xa,0x0)/Pci(0x0,0x0)
Device ID: 8086:15f3, rev 03

---

Current Kexts loaded:
  • Lilu.kext
  • VirtualSMC.kext
  • AppleIGC.kext
  • AppleMCEReporterDisabler.kext
  • NVMeFix.kext
  • RestrictEvents.kext
  • USBToolBox.kext
  • UTBMap.kext
  • WhateverGreen.kext

---

Question:
Is the I225-V ARP/routing issue in Sequoia recovery a known unfixable bug, or is there something specific I'm missing? Has anyone successfully gotten internet working in Sequoia recovery with the I225-V on an AMD B650 board?

Any help is greatly appreciated — I've been at this for a long time!

Thanks
 
Issues with Intel i225-V Ethernet controllers are common on AMD hacks. Most of the fixes you see on the internet are for Intel Hacks that use the same Ethernet controller, the fixes often don’t work that well, if at all, on AMD hacks.

Usual fix is to use AppleIGC.kext and e=1000 boot argument.


You might need to use a USB to Ethernet adapter for the macOS installation process. MacOS will automatically recognise the USB to Ethernet adapter. Assuming you have created a working UTBMap.kext in Windows, before trying to install Sequoia. This was a work around that was used by a number of site members when Sequoia was first released.
 
Hi, thanks for the reply!

I've been trying to get this working for a while now and wanted to update you on where I'm at and ask a few follow-up questions.

I already have AppleIGC.kext v1.4d1 installed and e1000=0 in boot-args. The kext loads correctly — ifconfig shows en0 with a valid IP from DHCP, but I cannot reach the gateway at all. Ping returns 'No route to host' every time. I've also tried dk.e1000=0 boot arg with no improvement.

I then tried a USB to Ethernet adapter (Clas Ohlson 38-3732, Realtek USB 10/100 chipset). macOS recovery sees it at the USB level (shows up in ioreg as 'USB 10/100 LAN' / Realtek vendor) but it never creates a network interface — it doesn't show up in ifconfig at all.

I have UTBMap.kext and USBToolBox.kext disabled and XhciPortLimit enabled, so USB mapping shouldn't be the issue.

My questions:
1. Does the Realtek USB 10/100 adapter work in Sequoia recovery, or do I need a specific chipset like ASIX AX88179?
2. Is installing Sonoma first and then upgrading to Sequoia a viable path on AMD B650? Are there any known issues with that upgrade route?
3. Is there anything else I can try to get the onboard I225-V actually routing traffic in Sequoia recovery?


Thanks again for any help!
 
  1. In theory any USB to Ethernet adapter should work in macOS.
    1. Although a 10/100mb adapter would be a bit old and so slow to use in any modern macOS release.
    2. Apple may have removed support for older USB to Ethernet adapters of that age. Most are now a minimum of 1GB, with some really expensive adapters supporting up to 10GB.
    3. The adapter should work as long as the USB port it is connected through is enabled and set with the correct connector type for the physical USB port. So using XhciPortLimit isn't the best option.
    4. Have you tested the Realtek USB to Ethernet adapter on another system, to check that it works and isn't damaged?
  2. Yes, there are issues with the Sonoma to Sequoia upgrade path related to the flaky Intel i225-V controller, on both Intel and AMD Hacks. But you already know that. It doesn't get any better with an update to Tahoe.
  3. No.
Not sure where you live or the cost of hardware components but I would normally recommend that you look to install a PCIe Network card, Realtek RTL8125B or similar chipset. But as you have an ITX board that isn't viable for you.

So perhaps purchasing a new USB to Ethernet adapter that works with a recent macOS release would be a better option. They are not expensive in the UK, available for less than £10 on Amazon. The UGREEN adapter linked below is one I own and it works without any issue in macOS.


I would strongly recommend that you create a USBMap.kext and configure your USB ports correctly for macOS, as the lack of a working/correctly configured USB setup is the Number 1 cause of problems in an AMD Hack.
 
Best option is honestly either a supported PCI-E card or a USB adapter as Ed has said. I can also confirm the UGREEN adapter linked to work as I also have it and I also have this one that works without issues too, https://amzn.to/3PiJ76a
 
  AdBlock Detected
Sure, ad-blocking software does a great job at blocking ads, but it also blocks some useful and important features of our website. For the best possible site experience please take a moment to disable your AdBlocker.