Jump to content
Mieze

IntelMausiEthernet.kext for Intel onboard LAN

896 posts in this topic

Recommended Posts

I compiled the kext using xcode 6.2 in Mavericks. I had a one compilation error that I solved quickly. The only doubt I have is, how can I have the Release version instead of the Debug one.

 

From the "Products" menu select "Archive". After that, select the built driver archive in the Organizer window which appears and click "Export" to save the release build somewhere, e.g. on the Desktop. In this folder you'll find a directory hierarchy with the release version of the driver in it.

 

Mieze

Share this post


Link to post
Share on other sites
Advertisement

From the "Products" menu select "Archive". After that, select the built driver archive in the Organizer window which appears and click "Export" to save the release build somewhere, e.g. on the Desktop. In this folder you'll find a directory hierarchy with the release version of the driver in it.

 

Mieze

Thanks!!!

 

EDIT:

 

Here is the V2.3.0d0 compatible with Mavericks.

IntelMausiEthernet-V2.3.0.d0.zip

 

Share this post


Link to post
Share on other sites

Hello
Just to say thanks, in the first place
Then some info
So to have the full bit rate in ethernet, it is necessary to choose in bios auto negociated
And in preference system, automatic

Result I move to just under 300MB / s fiber
Thank you Mieze
Long live the cat

 

170617173029.BMP

post-1181448-0-73799800-1497720814_thumb.png

post-1181448-0-45288900-1497720855_thumb.png

post-1181448-0-23342100-1497720868_thumb.png

post-1181448-0-12829800-1497721113_thumb.jpg

Share this post


Link to post
Share on other sites

Hello

Just to say thanks, in the first place

Then some info

So to have the full bit rate in ethernet, it is necessary to choose in bios auto negociated

And in preference system, automatic

Result I move to just under 300MB / s fiber

Thank you Mieze

Long live the cat

What kind of widget/app its that with blue specs, latency?

Thanks.

Share this post


Link to post
Share on other sites

I have PCI LAN card with ID=0x12298086.

Is it possible the kext will work with it?

Sorry, but PCI devices aren't supported at all because of the lack of support for 64bit DMA operations.

 

Mieze

Share this post


Link to post
Share on other sites

Hi Miezi, i have a problem with new High Sierra, DP2, because not work good internet, intermittent signal.

 

I have IntelMausiEthernet work very fine on 10.12.6, but in 10.13 DP2 not work good. First Beta is good, but now, im not sure what to do...

 

You can help me, please? 

 

EDIT: Artur-PT help me with this issue, in Portuguese forum, so im fixed that deleting the other folder on EFI Clover 4097 Partition.

 

http://www.insanelymac.com/forum/topic/324222-macos-1013-betas-dps-disponiveis/?p=2450603 

Share this post


Link to post
Share on other sites

Sorry, but PCI devices aren't supported at all because of the lack of support for 64bit DMA operations.

Aren't situations like that supposed to be handled by classes like IOMapper, IOMemoryDescriptor, IOBufferMemoryDescriptor, IODMACommand, etc. which can use an IOMMU or DART (if one exists) for DMA address translation?

https://developer.apple.com/library/content/documentation/DeviceDrivers/Conceptual/IOKitFundamentals/DataMgmt/DataMgmt.html#//apple_ref/doc/uid/TP0000019-SW3

Share this post


Link to post
Share on other sites

Aren't situations like that supposed to be handled by classes like IOMapper, IOMemoryDescriptor, IOBufferMemoryDescriptor, IODMACommand, etc. which can use an IOMMU or DART (if one exists) for DMA address translation?

https://developer.apple.com/library/content/documentation/DeviceDrivers/Conceptual/IOKitFundamentals/DataMgmt/DataMgmt.html#//apple_ref/doc/uid/TP0000019-SW3

Sure, it's possible to write a driver which supports 32bit-devices using these classes but it requires a different approach and adds another level of complexity to the driver which isn't required for PCIe at all and not to forget, the most important question: how many users are still using PCI cards as PCIe replacements are dirt cheap?

 

Mieze

Hi Miezi, i have a problem with new High Sierra, DP2, because not work good internet, intermittent signal.

 

I have IntelMausiEthernet work very fine on 10.12.6, but in 10.13 DP2 not work good. First Beta is good, but now, im not sure what to do...

 

You can help me, please? 

 

EDIT: Artur-PT help me with this issue, in Portuguese forum, so im fixed that deleting the other folder on EFI Clover 4097 Partition.

 

http://www.insanelymac.com/forum/topic/324222-macos-1013-betas-dps-disponiveis/?p=2450603 

First of all you should solve the problem which exists between keyboard and chair! Where is a detailed problem description because "intermittent signal" could be anything, for example a cat playing with the cable? :lol: 

 

Where are the kernel logs showing the issue? In case there are connection drops, there must be some driver messages in the kernel logs.

 

Mieze

Share this post


Link to post
Share on other sites

Sorry Miezi, im not know how do it (log), but im solved with delete folder other and caches are normal now!!

 

The cables is fine, because another systems like Sierra, 10 and Beta its very normal. 

 

Tks!!

Share this post


Link to post
Share on other sites

... because "intermittent signal" could be anything, for example a cat playing with the cable? 

 

Mieze

 

Do you really like cats, huh? ;)

Share this post


Link to post
Share on other sites

Hi,

 

installed latest version on 10.12.6 in my system but the transfer is too bad, about 30m (on windows is about 100).

What could be the problem?

Share this post


Link to post
Share on other sites

Hi,

 

installed latest version on 10.12.6 in my system but the transfer is too bad, about 30m (on windows is about 100).

What could be the problem?

It's most likely a protocol issue (packet signing) or a power management related problem.

 

Mieze

Share this post


Link to post
Share on other sites

Saludos amigos


He intentado ver como soluciono lo de la red lan en mi Mobo Dp55wg y nada, tengo que reiniciar la maquina luego que la prendo para que reconozca la Lan

Me lanza este error :

Ethernet IntelMausi : Failed to get adapter data with error -3


Luego si la reinicio :

 

Ethernet IntelMausi : 82578DC (Rev. 5), 

Me sugirieron esto

The UEFI network stack or some kind of remote management software is still in control of the NIC preventing the driver from taking control. Check you UEFI settings and disable it.


 

Pero lo tengo desabilitado en el Bios

Lei esto por ahi, no lo he hecho

 

I had weird artefacts at boot whether Legacy ROM was activated or not. Mieze (IntelMausi's author) recommended to disable all ROM which could interfere with the LAN chip when you get the "Failed to get adapter data" error in the kext logs.

 

He conectado el USB en diferentes puertos mi Mobo solo posee USB 2.0

A ver que pudieran sugerir

 

 

Greetings friends

I tried to see how I solved the network lan in my Mobo Dp55wg and nothing, I have to reboot the machine after the attachment to recognize the Lan

I throw this error:
Ethernet IntelMausi: Failed to get adapter data with error -3

Then if the reboot:

Ethernet IntelMausi: 82578DC (Rev. 5),

I was suggested this
The UEFI network stack or some kind of remote management software is still in control of the NIC preventing the driver from taking control. Check UEFI settings and disable it.
But I have it disabled in the Bios
I read this out there, I have not done it
I had weird artefacts at boot whether Legacy ROM was activated or not. Mieze (IntelMausi's author) recommended to disable all ROM which could interfere with the LAN chip when you get the "Failed to get adapter data" error in the kext logs.
I have connected the USB in different ports my Mobo only owns USB 2.0

To see what they could suggest

Share this post


Link to post
Share on other sites

i am currently using intel e1000e kext for my 8th series sabertooth z87, will this driver work better than intel e1000 kext for my onboard intel controller?

 

For the other guys, you can get to work many of the controllers not supported by this driver using intel e1000 and intel e1000e ethernet drivers, but because they are kind of universal driver, you will miss some optimization and also support for newer controllers (for newer controller maybe some developer just created updated versions, i don't know), but this driver is focused on optimization for newer chips as i have read to get better performance, if you need support for controller no longer supported, just recompile from source code the older versions of the driver and set as target the mac os version you want to use

Share this post


Link to post
Share on other sites

Pity about WoL. Using it with I219LM on Lenovo Thinkcentre M800 & sadly onboard network goes black when Sierra powers off

 

Was using previously Thinkcentre M73 with Realtek driver under Yosemite, which did works great with WoL

 

So I am not convinced it is OS

Share this post


Link to post
Share on other sites

Pity about WoL. Using it with I219LM on Lenovo Thinkcentre M800 & sadly onboard network goes black when Sierra powers off

 

That's the specified behavior as WoL from S5 isn't supported by MacOS.

 

Mieze

Share this post


Link to post
Share on other sites

Still would like to understand how Thinkcentre M73 with Realtek driver does NOT behave this way...

Share this post


Link to post
Share on other sites

Still would like to understand how Thinkcentre M73 with Realtek driver does NOT behave this way...

First of all, when the system is going to reboot or shutdown the driver releases control of the NIC. What happens after that, is beyond control of the driver. Second, Intel onboard NICs are different than other NICs because they are tightly coupled with the chipset's management engine (ME) which means that the ME takes control of the NIC when the driver releases it.

 

Mieze

Share this post


Link to post
Share on other sites

Hello:

 

    I was having some problems when I used this driver for my laptop. When I plug in the network cable, the network state has been "not connected" and "cable unplugged" cycle switch, but if I plugged cable first, then boot into the OS will not have this problem. NIC in Windows10 environment everything is normal. Will change how to solve? laptop model is HP Elitebook 820 G4, and the NIC is i219v2. The OS is 10.12.6, the NIC driver is the latest version.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By Mieze
      Being asked to add support for Realtek's Fast Ethernet PCIe NICs to my RTL8111 driver I got tired of answering the same old question again and again so that I finally decided to write a separate driver for these chips and to make a few of you guys and gals happy.
       
      As of now the driver supports the following members the RTL810X Fast Ethernet family:
      RTL8101E RTL8102E RTL8103E RTL8401E RTL8105E RTL8402 RTL8106E RTL8106EUS RTL8107E   Here is a list of the driver's basic features:
      Supports Sierra (maybe El Capitan). 64 bit architecture only. Support for multisegment packets relieving the network stack of unnecessary copy operations when assembling packets for transmission. No-copy receive and transmit. Only small packets are copied on reception because creating a copy is more efficient than allocating a new buffer. TCP, UDP and IPv4 checksum offload (receive and transmit). TCP segmentation offload under IPv4. Support for TCP/IPv6 and UDP/IPv6 checksum offload. Supports Wake on LAN. Support for Energy Efficient Ethernet (EEE) which can be disabled by setting enableEEE to NO in the drivers Info.plist without rebuild. The default is YES. The driver is published under GPLv2. Built using Xcode 4.6.3.  
      Changelog Version 2.0.1 (2018-05-10): Fixes a problem with retrieval of the permanent MAC address on some chips. Version 2.0.0 (2017-04-04): Uses Apple's private driver interface introduced with 10.8. Adds support for the RTL8107E. Supports packet scheduling with QFQ. Adds support for flow control and EEE. Version 1.0.0 (2014-05-24): First offical release.     Installation   Before you install the driver you have to remove any installed driver for RTL810X. Goto /S/L/E and delete the old driver. Recreate the kernel cache. Open System Preferences and delete the corresponding network interface, e. g. en0. If you forget this step you might experience strange problems with certain Apple domains, iTunes and iCloud later. Install the new driver and recreate the kernel cache. Reboot Open System Preferences again, select Network and check if the new network interface has been created automatically or create it manually now. Configure the interface.   Help - I'm getting kernel panics!
      Well, before you start complaining about bugs after you upgraded macOS and ask me to publish a driver update, you should first try to resolve the issue on your own by cleaning the system caches.
      As the driver uses macOS's private network driver interface, which is supposed to be used by Apple provided drivers only, you might run into problems after an OS update because the linker may fail to recognize that IONetworking.kext has been updated and that the driver needs to be linked against the new version (Apple provided drivers avoid this problem because they are always updated together with IONetworking.kext). As a result, the linking process produces garbage and the driver may call arbitrary code when trying to call functions from IONetworking.kext. This usually results in unpredicted behavior or a kernel panic. In order to recover from such a situation, you should clean the System Caches forcing the linker to recreate it's caches:
      Delete all the files in /System/Library/Caches and it's subdirectories but leave the directories and the symbolic links intact. This is very important! Reboot. Recreate the kernel cache. Reboot again.  
      Troubleshooting Make sure you have followed the installation instructions especially when you have issues with certain domains while the others are working fine. Use the debug version to collect log data when trying to track down problems. The kernel log messages can be retrieved with "grep kernel /var/log/system.log" in Terminal. Starting from Sierra use "log show --predicate "processID == 0" --debug" in order to retrieve kernel logs. Include the log data when asking for support or giving feedback. I'm an engineer, not a clairvoyant. Don't copy and paste large amounts of log data to your post. Create an archive with the log data and attach it to your post. In case you don't want to make your log data publicly accessible, contact me via PM and I will provide you a mail address to send it directly to me.  Check your BIOS settings. You might want to disable Network Boot and the UEFI Network Stack as these can interfere with the driver. Double check that you have removed any other Realtek kext from your system because they could prevent the driver from working properly. Delete the following files: /Library/Preferences/SystemConfiguration/NetworkInterfaces.plist /Library/Preferences/SystemConfiguration/preferences.plist Verify your bootloader configuration, in particular the kernel flags. Avoid using npci=0x2000 or npci=0x3000.  In Terminal run netstat -s in order to display network statistics. Carefully examine the data for any unusual activity like a high number of packets with bad IP header checksums, etc. In case auto-configuration of the link layer connection doesn't work it might be necessary to select the medium manually in System Preferences under Network for the interface. Use Wireshark to create a packet dump in order to collect diagnostic information. Keep in mind that there are many manufacturers of network equipment. Although Ethernet is an IEEE standard, different implementations may show different behavior causing incompatibilities. In case you are having trouble try a different switch or a different cable.  
      Getting the driver
      There is a prebuilt binary in the Download section of this site: http://www.insanelymac.com/forum/files/file/259-realtekrtl8100-binary/ The source code can be found on Github: https://github.com/Mieze/RealtekRTL8100   Mieze
    • By Mieze
      A New Driver for Realtek RTL8111
       
      Due to the lack of an OS X driver that makes use of the advanced features of the Realtek RTL81111/8168 series I started a new project with the aim to create a state of the art driver that gets the most out of those NICs which can be found on virtually any cheap board on the market today. Based on Realtek's Linux driver (version 8.035.0) I have written a driver that is optimized for performance while making efficient use of system resources and keeping the CPU usage down under heavy load.

      Key Features of the Driver
      Supports Realtek RTL8111/8168 B/C/D/E/F/G found on recent boards. Support for multisegment packets relieving the network stack of unnecessary copy operations when assembling packets for transmission. No-copy receive and transmit. Only small packets are copied on reception because creating a copy is more efficient than allocating a new buffer. TCP, UDP and IPv4 checksum offload (receive and transmit). TCP segmentation offload under IPv4. Support for TCP/IPv6 and UDP/IPv6 checksum offload. Fully optimized for Mountain Lion (64bit architecture) but should work with Lion too. As of now there is no support for Snow Leopard but it can be added if someone will create the necessary patches. Supports Wake on LAN. Support for Energy Efficient Ethernet (EEE) which can be disabled by setting enableEEE to NO in the drivers Info.plist without rebuild. The default is YES. The driver is published under GPLv2.  
      Limitations
      As checksum offload doesn't work with jumbo frames they are currently unsupported and will definitely never be. No support for 32bit kernels.  
      Installation
      Before you install the driver you have to remove any installed driver for RTL8111/8168.
      Goto /S/L/E and delete the old driver (Lnx2mac, AppleRealtekRTL8169, etc.). Recreate the kernel cache. Open System Preferences and delete the corresponding network interface, e. g. en0. If you forget this step you might experience strange problems with certain Apple domains, iTunes and iCloud later. Reboot. Install the new driver and recreate the kernel cache. I recommend to use Kext Wizard or a similar utility for the installation. Reboot Open System Preferences again, select Network and check if the new network interface has been created automatically or create it manually now. Configure the interface.  
      Help - I'm getting kernel panics!
      Well, before you start complaining about bugs after you upgraded macOS and ask me to publish a driver update, you should first try to resolve the issue on your own by cleaning the system caches.
      As the driver uses macOS's private network driver interface, which is supposed to be used by Apple provided drivers only, you might run into problems after an OS update because the linker may fail to recognize that IONetworking.kext has been updated and that the driver needs to be linked against the new version (Apple provided drivers avoid this problem because they are always updated together with IONetworking.kext). As a result, the linking process produces garbage and the driver may call arbitrary code when trying to call functions from IONetworking.kext. This usually results in unpredicted behavior or a kernel panic. In order to recover from such a situation, you should clean the System Caches forcing the linker to recreate it's caches:
      Delete all the files in /System/Library/Caches and it's subdirectories but leave the directories and the symbolic links intact. This is very important! Reboot. Recreate the kernel cache. Reboot again.  
      Troubleshooting
      Make sure you have followed the installation instructions especially when you have issues with certain domains while the others are working fine. Use the debug version to collect log data when trying to track down problems. The kernel log messages can be found in /var/log/system.log. For Sierra and above use "log show --predicate "processID == 0" --debug" in order to retrieve kernel logs. Include the log data when asking for support or giving feedback. I'm an engineer, not a clairvoyant. Check your BIOS settings. You might want to disable Network Boot and the UEFI Network Stack as these can interfere with the driver. Double check that you have removed any other Realtek kext from your system because they could prevent the driver from working properly. Verify your bootloader configuration, in particular the kernel flags. Avoid using npci=0x2000 or npci=0x3000.  In Terminal run netstat -s in order to display network statistics. Carefully examine the data for any unusual activity like a high number of packets with bad IP header checksums, etc. In case auto-configuration of the link layer connection doesn't work it might be necessary to select the medium manually in System Preferences under Network for the interface. Use Wireshark to create a packet dump in order to collect diagnostic information. Keep in mind that there are many manufacturers of network equipment. Although Ethernet is an IEEE standard different implementations may show different behavior causing incompatibilities. In case you are having trouble try a different switch or a different cable.  
      FAQ
      How can I retrieve the kernel logs? In Terminal type "grep kernel /var/log/system.log". I want to disable Energy Efficient Ethernet (EEE) but I don't know how? Take a look at the driver's Info.plist file. There you will find an option named <key>enableEEE</key>. Change its value from <true/> to <false/>. Don't forget to recreate the kernel cache after changing the value. WoL from S5 doesn't work with this driver but under Windows it's working. Is this a driver bug? No it isn't, the driver is working as it should because OS X doesn't support WoL from S5.  
      Current status
      The driver has been successfully tested under 10.8.x and 10.9 with the B, C, D, E, F and G versions of the RTL8111/8168 and is known to work stable on these devices.  
      Changelog
      Version 2.2.2 (2018-01-21) Force ASPM state to disabled/enabled according to the config parameter setting. Requires 10.12 or newer. Version 2.2.1 (2016-03-12): Updated underlying linux sources from Realtek to 8.041.00. Added support for RTL8111H. Implemented Apple’s polled receive driver model (RXPOLL). Requires 10.11 or newer. Support for older versions of OS X has been dropped. Version 2.0.0 (2015-06-21): Uses Apple's private driver interface introduced with 10.8. Supports packet scheduling with QFQ. Please note that 2.0.0 is identical to 2.0.0d2. Only the version number has changed. Version 1.2.3 (2014-08-23): Reworked TSO4 and added support for TSO6. Version 1.2.2 (2014-08-44): Added an option to disable Active State Power Management (ASPM, default disabled) as ASPM seems to result in unstable operation of some chipsets. Resolved a problem with Link Aggregation after reboot. Added a workaround for the multicast filter bug of chipset 17 (RTL8111F) which prevented Bonjour from working properly Version 1.2.0 (2014-04-24): Updated underlying linux sources from Realtek to 8.037.00. Improved interrupt mitigate to use a less aggressive value for 10/100 MBit connections. Version 1.1.3 (2013-11-29): Improved transmit queue handling made it possible to reduce CPU load during packet transmission. Improved deadlock detection logic in order to avoid false positives due to lost interrupts. Version 1.1.2 (2013-08-03): Improved SMB performance in certain configurations. Faster browsing of large shares. Version 1.1.0 (2013-06-08): Support for TCP/IPv6 and UDP/IPv6 checksum offload added (can be disabled in Info.plist). Maximum size of the scatter-gather-list has been increased from 24 to 40 segments to resolve performance issues with TSO4 when offloading large packets which are highly fragmented. TSO4 can be disabled in Info.plist without rebuild. Statistics gathering has been improved to deliver more detailed information (resource shortages, transmitter resets, transmitter interrupt count). The interrupt mitigate settings has been changed to improve performance with SMB and to reduce CPU load. Configuration option added to allow for user defined interrupt mitigate settings without rebuild. Version 1.0.4 (2013-05-04): Moved setLinkStatus(kIONetworkLinkValid) from start() to enable(). Cleaned up getDescCommand(). Version 1.0.3 (2013-04-25): The issue after a reboot from Windows has been eliminated. Version 1.0.2 (2013-04-22): Added support for rx checksum offload of TCP and UDP over IPv6. Version 1.0.1 (2013-03-31): Improved behavior when rx checksum offload isn't working properly. Adds the chipset's model name to IORegistry so that it will show up in System Profiler.  
      Known Issues
      There are still performance problems with regard to SMB in certain configurations. My tests indicate that Apple's Broadcom driver shows the same behavior with those configurations. Obviously it's a more general problem that is not limited to my driver. WoL does not work in certain configurations. Old systems with 3 and 4 series chipsets exhibit performance issues in recent versions of macOS because there is no optimized power management for these systems in macOS anymore as Apple dropped support for the underlying hardware a long time ago. In case you are affected, please upgrade your hardware or find an alternative solution because I have no plans for a workaround. Sorry, but I don't think that it's worth the effort.  
      Getting the driver
      The source code can be found here: https://github.com/M...driver_for_OS_X There is also a pre-build binary for Mavericks and Yosemite: http://www.insanelym...n-and-wireless/  
      Building from Source
      I'm using XCode 4.6.3 for development. You can get a free copy of XCode after becoming a member of the Apple developer program. The free membership is sufficient in order to get access to development tools and documentation.
    • By End3rPower50
      Hi, i've installed on my pc MacOS Mojave but after installation my pc, sometimes, crash giving kernel panic.
      I came to the conclusion that it is a random kernel panic because sometimes it starting up and other times it isn't starting up
       
      My PC:
      CPU: Intel i7 6500U
      LAN: RTL8100
      Wi-Fi & Bluetooth: Dell DW1820A
      USB 3.1
       
      CLOVER.zip
    • By Angelo_
      Hi, I followed the rehabman guide (linked in the vanilla guide on the side of r/Hackintosh, not sure if I can link it) for laptops for my yoga 730ILW13 with an 8265u, Conexant 11870, 8gb of ram, 13.3" fhd and I found that upon booting the installer usb I get this weird issue where the screen displays what it should but the screen is incredibly dim (though it was off before using a flashlight on it) and it flashes every few seconds for a few milliseconds to the correct brightness, I used the plist for hd615-650 (including my 620), not quite sure what could be the culprit, first time hackintoshing a laptop so it might be a stupid brightness kext I forgot but didn't find any in that post or in this forum :c 
      Attached the clover zip so that anyone with more experience than me might give an idea in what could be a way to fix this.
      Thank you in advance 
       
       
       
      CLOVER.zip
    • By Bahaa
      Need help here
      My graphic card is detached 7mb
      and I try a lot of solution and no one work 
      can any one help
       

×