Jump to content
Mieze

IntelMausiEthernet.kext for Intel onboard LAN

899 posts in this topic

Recommended Posts

Is there some reason to have two separate targets?

 

Yes, there are several reasons:

  • I don't want to give up support for Lion.
  • Version 2.x.x is an experimental fork of the driver.
  • Both forks will be maintained in parallel.

Mieze

Share this post


Link to post
Share on other sites
Advertisement

Yes, there are several reasons:

  • I don't want to give up support for Lion.
  • Version 2.x.x is an experimental fork of the driver.
  • Both forks will be maintained in parallel.
Mieze

 

Would you rather us test v2 or v1?

 

Any particular focus for testing of either?

Share this post


Link to post
Share on other sites

As version 1.0.0d6 is quite stable and close to a final release, I suggest to use it for productive systems while version 2.x.x will evolve during the next weeks and was made for testing.

 

Mieze 

Share this post


Link to post
Share on other sites

As version 1.0.0d6 is quite stable and close to a final release, I suggest to use it for productive systems while version 2.x.x will evolve during the next weeks and was made for testing.

 

Mieze

At the moment, using v2 without issue...

Share this post


Link to post
Share on other sites

hi...

 

can it be used at 10.10 folder when using clover..or only at s/l/e ?  intel1217v..

thanks 

c.frio

Share this post


Link to post
Share on other sites

hi...

 

can it be used at 10.10 folder when using clover..or only at s/l/e ?  intel1217v..

thanks 

c.frio

Yes!

Share this post


Link to post
Share on other sites

@mieze - reporting in

... v2 is working quite well on my Lenovo T420. i have updated to the latest/recent OS X 10.10.3 (14D105g) beta on march 16. 

Share this post


Link to post
Share on other sites

@ATIguy123: Please send me your kernel logs showing the issue. Maybe I'll find something that helps to track it down. By the way, which mainboard are you using?

 

Mieze

Share this post


Link to post
Share on other sites

Hallo Mieze (äh sorry, I mean hello :D  )

 

your driver (v2.0.0d2) runs perfect with Mavericks 10.9.5 and Intel i217 onboard on GA Z87MX-D3H. Here a screen shot of a 5GB test to a Synology DS1010+ NAS with SynologyRaid (similar Raid5 - with the "slow" WD green drives) over gigabit-ethernet.

post-657179-0-99125800-1428668907_thumb.jpg

Share this post


Link to post
Share on other sites

Is there some reason to have two separate targets?

 

Yes, there are several reasons:

  • I don't want to give up support for Lion.
  • Version 2.x.x is an experimental fork of the driver.
  • Both forks will be maintained in parallel.

Mieze

i have compiled v2.0.0d2 targeting sdk10.7 and driver still works in Lion. what feature would i miss if i do it this way?

Edited by calibre

Share this post


Link to post
Share on other sites

i have compiled v2.0.0d2 targeting sdk10.7 and driver still works in Lion. what feature would i miss if i do it this way?

 

Although the driver might show version 2.0, you actually built version 1.0.0d7 because 2.0 would fail to load on Lion.

 

Mieze

Share this post


Link to post
Share on other sites

I've now experienced two different kernel panics, on an otherwise stable machine, and this driver was the only one mentioned in the kernel backtrace of the crash report. (1 each kernel panic on 2.0.0d1 and 2.0.0d2)

 

Mieze, I've sent you a PM on the subject. Meanwhile, going back to 1.0.0d6, as I'm not able to tolerate random rebooting on this machine, even if it only happens every few days...

Share this post


Link to post
Share on other sites

Your driver working very good  :)

This is  the first time in Yosemite My Info About 

this Network is showing properly

Thanks for your great Work  :wink_anim:

Do you have Paypal account?

 

 

g10.png

Share this post


Link to post
Share on other sites

Just wanted to say thanks for this driver! OS X definitely seems to recognise my I217LM better compared to the AppleIntelE1000e.kext, though it's hard to tell if it's giving me better performance or not. However I can at least confirm that I've had no issues thus far, as everything seems to working perfectly, so that's definitely a big plus!

 

 

I also wanted to ask; what's the best way to verify that the new features are working or, if some of them aren't supported on all models, how would I go about finding out which features I'm currently benefiting from?

 

For example, one feature listed is offloaded checksums, however if I look under netstat -s under the IP section I see entries such as "3298032 headers (65961256 bytes) checksummed in software". Does this mean I'm not benefiting from this feature at all, or is that some messages can't have their checksums offloaded? The number isn't the same as total number of packets for that section, so it implies that not all packets required checksumming in software, but is this because the rest were offloaded, or because checksums had already been computed in advance somewhere?

 

Probably not really important, I'm curious to know which features I'm benefiting from :)

Share this post


Link to post
Share on other sites

I also wanted to ask; what's the best way to verify that the new features are working or, if some of them aren't supported on all models, how would I go about finding out which features I'm currently benefiting from?

 

In Terminal type "ifconfig -v" and you will see "TXSTART" under "eflags" and QFQ as the scheduler while using version 2.

I also wanted to ask; what's the best way to verify that the new features are working or, if some of them aren't supported on all models, how would I go about finding out which features I'm currently benefiting from?

 

The driver enables all offload features for all supported devices, but OS X doesn't support checksum offload of packets with complex IP headers, e.g. any packet with IPv4 header options or IPv6 extension headers will always be checksummed in software. 

 

Mieze

Share this post


Link to post
Share on other sites

FYI...

 

the 2.0.0d2 version has been rock solid for me on my Lenovo T420

 

Intel 82579LM PCI Express Gigabit Ethernet:

 

  Name: ethernet

  Type: Ethernet

  Bus: PCI

  Slot: PCI Slot 1638400

  Vendor ID: 0x8086

  Device ID: 0x1502

  Subsystem Vendor ID: 0x17aa

  Subsystem ID: 0x21ce

  Revision ID: 0x0004

  BSD name: en0

  Kext name: IntelMausiEthernet.kext

  Location: /System/Library/Extensions/IntelMausiEthernet.kext

  Version: 2.0.0d2

 

So today I included this kext in the T420 Guide thread so it should get a wider audience from that group. 

Thank you.

 

P.S. I also have been using your other recent kext v2.0.0d2 for RTL8111 (on my gigabyte systems with Realtek 8168) - and it has been working very well for me. 

Share this post


Link to post
Share on other sites

Congratulations to the first official release. This is amazing software. Thank you very much for your work for our community. All the best. 

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
       

×