IntelMausiEthernet.kext for Intel onboard LAN

[Henties]

@Mieze Thanks for joining, and I hear what your sentiments are concerning proper bios settings and ACPI data structures, and I agree entirely. In my case however I have a situation where an add on NIC - DGE-560T - works exceptionally well WOL wise, in an identical bios and  ACPI data environment in which any version of the IntelMausi.kext which I can lay my hands on, just does not, you figure ?

From my vantage point I  believe it to be a kext problem and would not want to change anything in any of my systems to make, what I believe a flawed driver, work in my environment the way it should.

 

My sentiments are reinforced by the age old adage "if it ain't broken don't fix it"

 

In my 10 machine environment, comprising any macOS from Big Sur, Monterey as well as Ventura, in multi-boot OC 0.8.3 configurations, WOL/VNC work exceptionally well from anywhere to anywhere.

The attached pictures are examples of a machine that was woken with a standard WOL packet followed by a proper VNC construct and voila 12 seconds after issuing the WOL/VNC construct, the login screen appears. That is what I wish the IntelMausi.kext would also be able to do. Incidentally in Windows 10 environments the onboard Intel i219-V onboard NIC works quite well with WOL/VNC, obviously using the windows driver with the same bios setting that macOS is operating under.

 

14 hours ago, jpz4085 said:

I assume WOL from sleep has never worked with the i219-V on your Gigabyte GA-Z170X-UD3. Is that correct?

 

Yes that is correct, however it also applies to another, Haswell based macOS, hack using  an Intel i217-V onboard NIC instead.  The cure in this case once again was using an add-on DGE-560T NIC. On this particular machine I am however not short of spare PCIe slots. Incidentally in this case Windows is using the same "personality" that it is using for the i219-V NIC on the Skylake mobo.

 

"If so are you using any ACPI patches that would power down the network controller during sleep to prevent instant wake issues?"

 

No not at all. On non of my machines, in my particular environment, did I need to action anything to prevent this phenomena, because I have not experienced that yet. 

 

"You could test whether the kext is even able to set the power mode and Magic Packet filter required for WOL by temporarily enabling wake from S5. That would at least tell us it's really sleep specific."

 

Done that, but it makes no difference, and this "setting" is also not available in most of the iterations of this kext floating around.

 

Greetings Henties.

[jpz4085]

13 hours ago, Henties said:

From my vantage point I  believe it to be a kext problem and would not want to change anything in any of my systems to make, what I believe a flawed driver, work in my environment the way it should.

We'll need to look more closely at your configuration to determine what is causing the issue.

13 hours ago, Henties said:

My sentiments are reinforced by the age old adage "if it ain't broken don't fix it"

At this point that only applies to the DGE-560T which is different hardware and different driver but WOL doesn't work on the integrated NIC so clearly that's broken and needs fixed.

13 hours ago, Henties said:

Yes that is correct, however it also applies to another, Haswell based macOS, hack using  an Intel i217-V onboard NIC instead.

WOL is working on my Haswell GA-Z97X-UD3H-BK with an i217-V. Again we need to look more closely at your configuration considering it's never worked for you.

 

I'd suggest opening a separate thread to address these issues and attach the EFI folder for your machine(s) and mention me in the post. System specific troubleshooting is outside the scope of this driver support thread.

Edited August 13, 2022 by jpz4085

[Henties]

@jpz4085 Thks for your response, will open a new thread as you suggested and as soon as I am back home.

 

That the DGE-560T uses a different driver is clear, being @Mieze 's version 2.4.2 RealtekRTL8111 kext.

 

What makes me wandering is that for @Mieze's IntelMausi.kext certain bios settings and ACPI data structures need to be in place for it to function properly, but  these same conditions seem to be irrelevant, as far as her RealtekRTL8111 kext is concerned. To me this just does not make sense, considering my lifelong experience in the telecommunication industry and particular R&D, developing IP based system management software and more.

 

The "IP stack" that Apple provides is certainly the same for both of @Mieze's kexts, therefore both should work in one and the same environment if coded accordingly.

 

Environmental rules (API's) for software to function properly, in controlling similar categories of hardware, are universal, it therefore depends on the coder to take that into account when producing software.

 

I do however acknowledge that our macOS hacking world is far from ideal because API's are generally not published and need to be discovered by trial and error. Also the IntelMausi.kext has been in circulation for many years during which Apple introduced changes requiring the kext to be frequently "patched" to continue to be of use to the community. The IntelMausi.kext presently supports a total of 51 hardware personalities (variations) which is a big ask to make it work properly in conjunction with any NIC of that class one happens to throw at it.

 

Just my 2 cents, acknowledging that @Mieze 's service to the hacking community has been outstanding, without which basic networking would not have been possible as effortless as we have gotten used to with her kexts.

 

Greetings Henties

 

[Consistency]

Just to confirm. There's no support for "Automatic MDI/MDIX crossover at all speeds of operation" in this I219V driver? Therefore a crossover cable is required if I'd like to share the internet connection from a hackintosh?

 

[Creo2005]

Hi, i have ASUS PRIME Z790m-PLUS with Intel i219-V id 8086:0DC8

00:1f.6 8086:0dc8 /PC00@0/GLAN@1F,6 = PciRoot(0x0)/Pci(0x1F,0x6)

There is no such id in the IntelMausi.

Changing the id did not help, it is not in the system settings.

[Creo2005]

19 hours ago, Creo2005 said:

Hi, i have ASUS PRIME Z790m-PLUS with Intel i219-V id 8086:0DC8

00:1f.6 8086:0dc8 /PC00@0/GLAN@1F,6 = PciRoot(0x0)/Pci(0x1F,0x6)

There is no such id in the IntelMausi.

Changing the id did not help, it is not in the system settings.

With new V2.5.3d4 kext from @Slice all work!

IntelMausiEthernet.kext V2.5.3d4.zip

[Slice]

On 4/30/2023 at 12:20 PM, Creo2005 said:

With new V2.5.3d4 kext from @Slice all work!

 

Thanks for the test!

 

Welcome to my fork where I included new 16 Intel chips. Now the version is 2.5.4.

 https://github.com/CloverHackyColor/IntelMausiEthernet

The release kext was compiled under Ventura 13.4 with Xcode 14.3 and tested in Mojave 10.14.6 and in the Ventura. It works with my Intel V219 chip.

[Creo2005]

1 hour ago, Slice said:

Thanks for the test!

 

Welcome to my fork where I included new 16 Intel chips. Now the version is 2.5.4.

 https://github.com/CloverHackyColor/IntelMausiEthernet

The release kext was compiled under Ventura 13.4 with Xcode 14.3 and tested in Mojave 10.14.6 and in the Ventura. It works with my Intel V219 chip.

Thank's. Add your repository to OCAT config for update.

[MattsCreative]

On 5/20/2023 at 6:26 AM, Slice said:

Thanks for the test!

 

Welcome to my fork where I included new 16 Intel chips. Now the version is 2.5.4.

 https://github.com/CloverHackyColor/IntelMausiEthernet

The release kext was compiled under Ventura 13.4 with Xcode 14.3 and tested in Mojave 10.14.6 and in the Ventura. It works with my Intel V219 chip.

could you add support for intel 82574L please none of the old kexts work or the patches to make it run native.

[kocoman]

are there plans to support i225 (2.5Gig 4 port) (the default intel driverkit ibxe )one just "reboots" when network under load and 82599ES (10Gig SFP+ dual)?

 

thx

[Slice]

On 6/7/2023 at 1:39 AM, MattsCreative said:

could you add support for intel 82574L please none of the old kexts work or the patches to make it run native.

Did you test such driver? May be it works?

 

502797_AppleIntel8255x.kext.zip

[Henry2010]

Is it possibly a bug?

I cannot change Duplex in Sonoma 23A5301H using version 2.5.4. It's locked to full-duplex only.

In System Info "There was an error while gathering Ethernet device information."

😊

 

EDIT

Using the same kext, Clover version and config.plist, everything works as expected in Monterey.

(The NIC is I219-V.)

Edited August 5, 2023 by Henry2010

[xenophon]

Greetings.

 

I've used Mieze's kexts for ages, and have been very happy (and grateful).

 

Tried Slice's version (thank you, master) from https://github.com/CloverHackyColor/IntelMausiEthernet on a ThinkCentre M70q (Intel I219V, Device 0x0D4D) and it restored WOL from sleep.

 

Hope this helps.

 

Huge thanks to all.

Xen

[bhuether]

Hi, is this kext needed in Asus z790 creator (has built in i225) under Sonoma?

 

Thanks!

Edited May 23, 2024 by bhuether

[kocoman]

I getting choppy mouse/shuttering and audio also if I enable the driver and drop to 100mbps (with 5mbps DL and fast UL

how to debug this thx

 

Edited July 14, 2024 by kocoman

[Mieze]

Here is a prebuilt binary of IntelMausiEthernet V2.5.5d0 which comes with the following enhancements:

• Support for AppleVTD (please see the comments about AppleVTD for IntelLucy / RealtekRTL8111 / AtherosE2200Ethternet to learn about the limitations).
• Support for I219 chips found on Rocket Lake boards (maybe Alder Lake boards too?)
• Requires macOS 10.13 or newer.

Edit: Source code can be found on GitHub.

 

Mieze

IntelMausiEthernet-V2.5.5d0.zip

Edited June 16, 2025 by Mieze
Note about source code

[deeveedee]

@Mieze Thank you for the quick response!!! With v2.5.5d0, I still need to set Kernel > Quirks > DisableIoMapper = true when VT-d is enabled in BIOS on my hack (background here).  Note my hack does not require / use a modified DMAR.

 

I did confirm that IntelMausi is loading correctly

Spoiler

 

I'll review your comments about AppleVTD for IntelLucy / RealtekRTL8111 / AtherosE2200Ethternet in the other threads to see if I can learn more.  

 

Thank you!

 

EDIT: @Mieze Not sure if this helps, but I re-tested 2.5.5d0 with "Kernel > Quirks > DisableIoMapper = false" after dropping all ReservedRegions from DMAR.  After booting Tahoe Beta 1, I confirmed the injection of the revised DMAR, but the modified DMAR did not change Ethernet behavior (still no network connection).  To recap, IntelMausi / Ethernet works well for me through Sequoia when DisableIoMapper = false and VT-d is enabled in BIOS (without modifying DMAR).   It's not until Tahoe that I need to set DisableIoMapper = true when VT-d is enabled in BIOS.  Thank you again for your attention to this.  "Kernel > Quirks > DisableIoMapper = true" is a perfectly acceptable solution for me, so I'm just letting you know about this issue in case it is something you want to address or something that is required by others.  Thank you.

 

EDIT2: Could it be that this is an Apple bug in Tahoe Beta 1... a bug that may be resolved in a subsequent Tahoe Beta or Release?

Edited June 16, 2025 by deeveedee

[Mieze]

@deeveedee I don't know if it a bug or only a change in the kernel's memory layout which conflicts with the boards UEFI. Keep in mind that the board manufacturer had a reason to add these regions to the DMAR. Therefore it's always a dangerous step to remove these reserved memory regions. The patched DMAR might work but in case it doesn't there is no other solution than disabling AppleVTD.

[deeveedee]

@Mieze I'm perfectly content to operate with DisableIoMapper=true (without revising DMAR).  Thank you for your effort!

 

I do see one improvement with Tahoe Beta 1 after upgrading from Acidanthera's IntelMausi.kext 1.0.8 to your IntelMausiEthernet.kext 2.5.5d0.  With Acidanthera's IntelMausi.kext 1.0.8, I experienced a network connectivity issue with Windows App (MS Remote Desktop).  With your IntelMausiEthernet.kext 2.5.5.d0, I do not experience the network connectivity issue.  Specifically, with Acidanthera's IntelMausi.kext 1.0.8 injected in Tahoe Beta 1, I would occasionally have to toggle Ethernet (deactivate/activate using the attached script) in order to be able to establish a Remote Desktop session.  With your IntelMausiEthernet.kext 2.5.5d0, I do not have this problem.  I experienced the same Remote Desktop network connectivity problem with Acidanthera's IntelMausi.kext in early versions of Sequoia, but the problem was resolved with later Sequoia releases.  I never investigated to find the cause.

 

Thanks again!

toggleEth.zip

[Andres ZeroCross]

On 6/16/2025 at 4:27 AM, Mieze said:

Here is a prebuilt binary of IntelMausiEthernet V2.5.5d0 which comes with the following enhancements:

• Support for AppleVTD (please see the comments about AppleVTD for IntelLucy / RealtekRTL8111 / AtherosE2200Ethternet to learn about the limitations).
• Support for I219 chips found on Rocket Lake boards (maybe Alder Lake boards too?)
• Requires macOS 10.13 or newer.

Edit: Source code can be found on GitHub.

 

Mieze

IntelMausiEthernet-V2.5.5d0.zip 130.73 kB · 103 downloads

Thanks for this version, it works fine it's still problem in macos tahoe 26.0 with VT-D Enabled in my board Gigabyte Z170X Gaming 7. I just confuse for making new thread or not. You're creator of "AtherosE2200Ethernet.kext" and my board has 2 ethernet. AtherosE2200Ethernet.kext can't get connection too when Apple VT-D Enable in macos Tahoe.

Edited October 22, 2025 by Andres ZeroCross

[Mieze]

@Andres ZeroCross What is happening on your system? Which driver works or doesn't work with Tahoe and AppleVTD? In case IntelMausiEthernet really works in this configuration (check twice because you would be the first to report success!!!), please send me a dump of IOReg, and, in case you are using a patched DMAR, the original and the patched one.

 

Mieze 😺

[Andres ZeroCross]

2 hours ago, Mieze said:

@Andres ZeroCross What is happening on your system? Which driver works or doesn't work with Tahoe and AppleVTD? In case IntelMausiEthernet really works in this configuration (check twice because you would be the first to report success!!!), please send me a dump of IOReg, and, in case you are using a patched DMAR, the original and the patched one.

 

Mieze 😺

 

1. I was wrong, i though ethernet works but it doesn't. Internet come from my BCM943602CS2. I am using "AppleBCMWLANCompanion.kext" and this kext need Apple VT-D : enabled in BIOS.

2. IntelMausiEthernet-V2.5.5d0 is loaded in macOS Tahoe but in network preferences show "not connected" but if i reboot to macOS Sequoia then ethernet is working fine with same settings (VT-D Enable and DisableIoMapper = False)

 

3. I didn't use Patched DMAR because my original DMAR table doesn't contain reserved memory regions

 

Andres’s Mac Pro.zip

Edited October 22, 2025 by Andres ZeroCross

[amiga5]

IntelMausiEthernet-V2.5.5d0  works very well on Gigabyte Z390 Designare  . Latest  Tahoe and VT-D enabled.

Also I use AppleBCMWLANCompanion.kext.  No other drivers worked under these conditions only IntelMausiEthernet.

Edited November 19, 2025 by amiga5

[Mieze]

As already announced this week, here is version 3.0.0 (build 3.0.2) of IntelMausiEthernet, which supports AppleVTD under Tahoe, but also works fine without it. Have fun and good luck testing!

 

Mieze 😺

IntelMausiEthernet-V3.0.0-build-3.0.2.zip

[pico joe]

confirmed 

 

Big Thanks 🙏

Edited December 6, 2025 by pico joe