Jump to content

IntelMausiEthernet.kext for Intel onboard LAN


Mieze
988 posts in this topic

Recommended Posts

On 1/5/2021 at 11:20 PM, noah977 said:

I'm expereincing some very strange behavior with the physical onboard LAN.

 

Auros Z370 Motherboard

OpenCore (lastest Dec update)

Catalina (latest update)

Machine boots fine, LAN connects normally.  Speed test is great.  (I have 1GB Internet and see about 800MB speed)
However, after about 2-3 minutes, the LAN starts connecting and disconnecting.  It constantly cycles.  Additionally, I see that the hadware sometimes auto-sets itself to 10M.  The only entries in the logs just show connection up and connectoion down.

I have tested this LAN connetdion with a Linux laptop and it works perfect.  So, no problems with router or cable.

Any idea why this would happen? 

Thanks!

Bump
@Mieze

Link to comment
Share on other sites

  • 2 weeks later...

@CoBrA2168 There is absolutely no connection between IntelMausiEthernet and Wifi. Both driver's operate independently and in case there is a Wifi performance issue after wakeup, it's up to Apple to fix it. With regard to WoL, the OS calls the driver to enable WoL before going to sleep and calls it to disable it after wakeup. The driver's responsibility is to program the hardware according to this setting.

 

@noah977 Sounds like a hardware issue. Try to select the medium manually. Try one without flow control and EEE as those options sometimes cause trouble. Also consider that there might be dust on the connector?

 

Mieze :cat:

Link to comment
Share on other sites

On 1/26/2021 at 6:52 PM, Mieze said:

@CoBrA2168 There is absolutely no connection between IntelMausiEthernet and Wifi. Both driver's operate independently and in case there is a Wifi performance issue after wakeup, it's up to Apple to fix it. With regard to WoL, the OS calls the driver to enable WoL before going to sleep and calls it to disable it after wakeup. The driver's responsibility is to program the hardware according to this setting.

 

@noah977 Sounds like a hardware issue. Try to select the medium manually. Try one without flow control and EEE as those options sometimes cause trouble. Also consider that there might be dust on the connector?

 

Mieze :cat:

@Mieze thank you for the reply.  Not sure if you saw the "EDIT" in my post, but I realized that this particular WiFi issue has been solved already via AirportBrcmFixup.kext (a Lilu extension).  Basically this driver, by default, will disable WOL for any matching WiFi adapters.  This allows me to keep WOL enabled so I can use it over Ethernet with your kext, but without the nasty side affect of having broken WiFi after sleep.

 

I figured I'd keep my initial question/post here just in case someone else stumbles upon this very issue in the future :)  Also thanks again for your continued work on this kext.  I use it on both of my hackintosh machines and it works beautifully on both!

Link to comment
Share on other sites

  • 2 months later...

Hello -

 

I am building a hack using ASUS Z490 Gaming TUF Plus which has Intel i219-v chipset for Ethernet. I am unable to get the Mac to see the Ethernet port using either IntelMausi or IntelMausiEthernet kexts. I can confirm that the extension is loaded. I see an error that "IOACPIPlatformDevice is not serializable" in IOReg. I've used IntelMausi 1.0.5 and IntelMausiEthernet 2.5.3d1. 


What am I doing wrong? Thanks in advance!

Screen Shot 2021-03-31 at 4.13.52 PM.png

Screen Shot 2021-03-31 at 4.25.23 PM.png

config-mod.plist

iMac.ioreg

Edited by nagha
added IOReg dump
Link to comment
Share on other sites

  • 1 month later...

Here is a new development version (2.5.3d3) of the driver which supports some new configuration options which can be changed in the kext's Info.plist:

  • enableWakeOnAddrMatch: Enables wakeup on any packet with an address matching one of the machine's addresses (default off). Used on a server, it might be helpful to cause a wakeup when a client connects but prevents the machine from sleeping when there is network activity. It allows your server to go to sleep while all clients are off or sleeping. When a client wakes up and tries to reconnect to the server, enabling this option will cause the server to wakeup automatically in such a situation. Keep disabled unless you need it, in particular on client machines.
  • enableWakeS5: Enables WoL from S5 (default off). Keep disabled unless you need it.

The attached archive contains a debug and release build. Good luck and have fun!

 

Mieze :cat:

IntelMausiEthernet-V2.5.d3.zip

  • Like 3
  • Thanks 3
Link to comment
Share on other sites

  • 1 month later...
On 6/21/2021 at 7:43 PM, WeBeRiO said:

 

InMonterey no work correcty i219-V, only 100mb/s :(


 

No, all is good

Screenshot 2021-06-25 at 05.39.58.png

 

% sudo kextstat | grep -v pple
Password:
Executing: /usr/bin/kmutil showloaded
No variant specified, falling back to release
Index Refs Address            Size       Wired      Name (Version) UUID <Linked Against>
   19    3 0                  0x18000    0x18000    org.netkas.FakeSMC (3.5.3) 503675DF-E091-38F2-AE0C-5A1F93D84E15 <15 9 7 6 3>
   20    0 0                  0x10000    0x10000    org.slice.RadeonMonitor (1.3.5) 09B20CAE-4A50-34F9-BA72-5996FB7F2386 <19 16 9 6 3>
   52    0 0                  0x11000    0x11000    org.slice.IntelCPUMonitor (1.2.5) 5601DBF8-2C70-364B-9359-816108A00582 <19 9 7 6 3>
   53    0 0                  0x11000    0x11000    org.mozodojo.ITEIT87x (1.0.7) C1AEA9CC-79B7-32A6-AF30-CF9F2F5ADA2E <19 9 7 6 3>
   74    0 0                  0x2e000    0x2e000    com.insanelymac.IntelMausiEthernet (2.5.1d1) 624E285C-5E23-3941-B23C-980E71F7227E <50 16 7 6 3 1>
  118    0 0xffffff7f9a2eb000 0x25000    0x25000    org.voodoo.driver.VoodooHDA (2.9.7) 224E762A-1DFE-3C36-988D-9D7371A39434 <110 16 9 7 6 3>
  121    0 0xffffff7f9a20e000 0x2000     0x2000     com.intel.driver.EnergyDriver (3.7.0) 35E739F9-BF6C-3024-A67C-750711B3FB64 <9 7 6 3>

 

  • Like 1
Link to comment
Share on other sites

The kext from acidanthera is a copy of original with debugging ability (so why 100baseT?).

See their Readme

Quote

Do use the original version when uncertain. No support or troubleshooting provided.

 

Link to comment
Share on other sites

3 hours ago, WeBeRiO said:

Same error with your kext :(
 

image.thumb.png.b27a7cd740459869e36c79b0e8bfeded.png

May be your router doesn't allow to use 1000?

I don't know. There is also an observation that I used Clover while you used OC. FakeSMC vs VirtualSMC.

  • Thanks 1
Link to comment
Share on other sites

×
×
  • Create New...