Jump to content
Mieze

New Driver for Realtek RTL8111

1,389 posts in this topic

Recommended Posts

@Mieze

Im trying to compile my own and noticed it has a v2. Which one should i compile?

 

Thanks

Always V2! V1 is outdated and will be removed soon.

 

Mieze

Share this post


Link to post
Share on other sites
Advertisement

Hi,

if you let the macos settings on "manual" in the hardware tab of the ethernet device driven by this driver, it won't select 1000baseT, if it is available. So you have to switch to 1000baseT manually, else it stays in 100baseX mode. Using a CAT5e cable.

Share this post


Link to post
Share on other sites

Hi,

if you let the macos settings on "manual" in the hardware tab of the ethernet device driven by this driver, it won't select 1000baseT, if it is available. So you have to switch to 1000baseT manually, else it stays in 100baseX mode. Using a CAT5e cable.

"Manual" means manual configuration. So, what is the point?

 

Mieze

Share this post


Link to post
Share on other sites

Mieze,

 

I actually meant "automatically" :)

 

I switched my LAN from 100 to 1000, but in auto-mode, the driver does not seem to detect the 1000 mbit. Shouldn't it detect it automatically? 

 

 

EDIT: Hm, nvm. I checked now in another LAN, there it works. Seems to be a wrong CAT5e cable?

Share this post


Link to post
Share on other sites

Mieze,

 

I actually meant "automatically" :)

 

I switched my LAN from 100 to 1000, but in auto-mode, the driver does not seem to detect the 1000 mbit. Shouldn't it detect it automatically? 

Auto-configuration is a complex process in which both link partners negotiate the link parameters but the result isn't always the expected one and that's the reason why one might want to switch to manual mode.

 

Mieze

Share this post


Link to post
Share on other sites

Hey there.
My Ethernet doesn't work after sleep, but kext itself does - I can see a self-assigned IP address in my network settings.

Is that normal for this driver? Or how can I fix it if it's not?

Share this post


Link to post
Share on other sites

Hey there.

My Ethernet doesn't work after sleep, but kext itself does - I can see a self-assigned IP address in my network settings.

 

Is that normal for this driver? Or how can I fix it if it's not?

No, it's not normal and you should check other things like DHCP first as I haven't heard of any sleep/wake related problems for quite a long lime. In case you think that's a driver related problem, you should send me some kernel logs showing the problem.

 

Mieze

Share this post


Link to post
Share on other sites

Hello Mieze, can you delete these messages from the log?

Thank you.

2018-02-11 21:21:41.107117+0200 0x39e      Default     0x0                  0      kernel: (kernel) setOffset79() ===>

2018-02-11 21:21:41.110350+0200 0x39e      Default     0x0                  0      kernel: (kernel) setOffset79() <===

2018-02-11 21:21:41.135446+0200 0x39e      Default     0x0                  0      kernel: (kernel) setMulticastMode() ===>

2018-02-11 21:21:41.135888+0200 0x39e      Default     0x0                  0      kernel: (kernel) setMulticastMode() <===

2018-02-11 21:21:41.161713+0200 0x39e      Default     0x0                  0      kernel: (kernel) setMulticastMode() ===>

2018-02-11 21:21:41.167093+0200 0x39e      Default     0x0                  0      kernel: (kernel) setMulticastMode() <===

2018-02-11 21:21:41.230920+0200 0x39e      Default     0x0                  0      kernel: (kernel) setMulticastList() ===>

2018-02-11 21:21:41.236896+0200 0x39e      Default     0x0                  0      kernel: (kernel) setMulticastList() <===

2018-02-11 21:21:41.254538+0200 0x2d1      Default     0x0                  0      kernel: (kernel) setMulticastList() ===>

2018-02-11 21:21:41.260332+0200 0x2d1      Default     0x0                  0      kernel: (kernel) setMulticastList() <===

2018-02-11 21:21:41.283636+0200 0x2d1      Default     0x0                  0      kernel: (kernel) setMulticastList() ===>

2018-02-11 21:21:41.289017+0200 0x2d1      Default     0x0                  0      kernel: (kernel) setMulticastList() <===

2018-02-11 21:21:41.294344+0200 0x2d1      Default     0x0                  0      kernel: (kernel) setMulticastList() ===>

2018-02-11 21:21:41.299477+0200 0x2d1      Default     0x0                  0      kernel: (kernel) setMulticastList() <===

///

2018-02-11 21:21:44.841041+0200 0x104      Default     0x0                  0      kernel: (kernel) getFeatures() ===>

2018-02-11 21:21:44.851499+0200 0x104      Default     0x0                  0      kernel: (kernel) getFeatures() <===

2018-02-11 21:21:41.242840+0200 0x39e      Default     0x0                  0      kernel: (kernel) getPacketFilters() ===>

2018-02-11 21:21:41.248731+0200 0x39e      Default     0x0                  0      kernel: (kernel) getPacketFilters() <===

2018-02-11 21:21:41.265920+0200 0x1bf      Default     0x0                  0      kernel: (kernel) getPacketFilters() ===>

2018-02-11 21:21:41.271323+0200 0x1bf      Default     0x0                  0      kernel: (kernel) getPacketFilters() <===

Share this post


Link to post
Share on other sites

Hello Mieze, can you delete these messages from the log?

Thank you.

2018-02-11 21:21:41.107117+0200 0x39e      Default     0x0                  0      kernel: (kernel) setOffset79() ===>

2018-02-11 21:21:41.110350+0200 0x39e      Default     0x0                  0      kernel: (kernel) setOffset79() <===

2018-02-11 21:21:41.135446+0200 0x39e      Default     0x0                  0      kernel: (kernel) setMulticastMode() ===>

2018-02-11 21:21:41.135888+0200 0x39e      Default     0x0                  0      kernel: (kernel) setMulticastMode() <===

2018-02-11 21:21:41.161713+0200 0x39e      Default     0x0                  0      kernel: (kernel) setMulticastMode() ===>

2018-02-11 21:21:41.167093+0200 0x39e      Default     0x0                  0      kernel: (kernel) setMulticastMode() <===

2018-02-11 21:21:41.230920+0200 0x39e      Default     0x0                  0      kernel: (kernel) setMulticastList() ===>

2018-02-11 21:21:41.236896+0200 0x39e      Default     0x0                  0      kernel: (kernel) setMulticastList() <===

2018-02-11 21:21:41.254538+0200 0x2d1      Default     0x0                  0      kernel: (kernel) setMulticastList() ===>

2018-02-11 21:21:41.260332+0200 0x2d1      Default     0x0                  0      kernel: (kernel) setMulticastList() <===

2018-02-11 21:21:41.283636+0200 0x2d1      Default     0x0                  0      kernel: (kernel) setMulticastList() ===>

2018-02-11 21:21:41.289017+0200 0x2d1      Default     0x0                  0      kernel: (kernel) setMulticastList() <===

2018-02-11 21:21:41.294344+0200 0x2d1      Default     0x0                  0      kernel: (kernel) setMulticastList() ===>

2018-02-11 21:21:41.299477+0200 0x2d1      Default     0x0                  0      kernel: (kernel) setMulticastList() <===

///

2018-02-11 21:21:44.841041+0200 0x104      Default     0x0                  0      kernel: (kernel) getFeatures() ===>

2018-02-11 21:21:44.851499+0200 0x104      Default     0x0                  0      kernel: (kernel) getFeatures() <===

2018-02-11 21:21:41.242840+0200 0x39e      Default     0x0                  0      kernel: (kernel) getPacketFilters() ===>

2018-02-11 21:21:41.248731+0200 0x39e      Default     0x0                  0      kernel: (kernel) getPacketFilters() <===

2018-02-11 21:21:41.265920+0200 0x1bf      Default     0x0                  0      kernel: (kernel) getPacketFilters() ===>

2018-02-11 21:21:41.271323+0200 0x1bf      Default     0x0                  0      kernel: (kernel) getPacketFilters() <===

 

Why?  :wacko:

 

These are debug messages output by the debug version of the driver, which is for debugging only. Production systems should use the release version of the driver which doesn't output these lines.

 

Mieze

Share this post


Link to post
Share on other sites

Why?  :wacko:

 

These are debug messages output by the debug version of the driver, which is for debugging only. Production systems should use the release version of the driver which doesn't output these lines.

 

Mieze

I'm sorry, I have a debug version installed.  :blush:

Share this post


Link to post
Share on other sites

I can't believe there have been almost 5 YEARS since this thread started... 5 years!

I think I've been using this kext since 3 years ago. Never had an issue. Not even once. It's been incredibly reliable for me.

So I just wanted to extend my gratitude to the developer. Congrats! And thank you very, very much for you work.

Edited by arsradu

Share this post


Link to post
Share on other sites
On 01.05.2017 at 2:39 AM, FFForever said:

 


panic(cpu 0 caller 0xffffff80004011bd): Kernel trap at 0xffffff7f838951a2, type 14=page fault, registers:
CR0: 0x000000008001003b, CR2: 0xffffff81ec657000, CR3: 0x0000000009b62000, CR4: 0x00000000001627e0
RAX: 0x0000000000000000, RBX: 0x0000000000000000, RCX: 0xffffff81ec657000, RDX: 0xffffff81c2469088
RSP: 0xffffff81ed40be40, RBP: 0xffffff81ed40be50, RSI: 0x0000000000000000, RDI: 0xffffff81a1b97000
R8: 0x00000591bb32903c, R9: 0xffffff80296b6d98, R10: 0x0000000000000000, R11: 0xffffff8000a8a810
R12: 0x00000591ba46549d, R13: 0x000000008df5a1c1, R14: 0xffffff81a1b97000, R15: 0xffffff81a1b972a0
RFL: 0x0000000000010246, RIP: 0xffffff7f838951a2, CS: 0x0000000000000008, SS: 0x0000000000000010
Fault CR2: 0xffffff81ec657000, Error code: 0x0000000000000002, Fault CPU: 0x0, PL: 0, VF: 1

Backtrace (CPU 0), Frame : Return Address
0xffffff81ed40bad0 : 0xffffff80002ec3ec
0xffffff81ed40bb50 : 0xffffff80004011bd
0xffffff81ed40bd30 : 0xffffff800029d543
0xffffff81ed40bd50 : 0xffffff7f838951a2
0xffffff81ed40be50 : 0xffffff7f83896e39
0xffffff81ed40be70 : 0xffffff7f838967ea
0xffffff81ed40bea0 : 0xffffff7f8389609f
0xffffff81ed40bee0 : 0xffffff80008bcfaf
0xffffff81ed40bf30 : 0xffffff80008bb811
0xffffff81ed40bf80 : 0xffffff80008badf6
0xffffff81ed40bfb0 : 0xffffff800029a8f7
Kernel Extensions in backtrace:
com.insanelymac.RealtekRTL8111(2.2.1)[8BA5E6A6-5DCA-3102-B71B-CE613147F452]@0xffffff7f83835000->0xffffff7f8389bfff
dependency: com.apple.iokit.IONetworkingFamily(3.2)[6326DB88-5330-3F0C-91F6-D478AB5E7503]@0xffffff7f812fd000
dependency: com.apple.iokit.IOPCIFamily(2.9)[C6E3195E-A0D7-3B71-B5F4-9EE9E182D4FC]@0xffffff7f80b32000

Hi! I often have same panic on version 2.2.2 when i try to go to sleep. My LAN - RTL8168G. OS X Sierra 10.12.6. I disable ASPM, Network boot etc...

Besides, if i fall asleep, then after waking up, the network speed drops to a minimum.

At the moment I returned to version 2.2.1 and there are no such problems.
Maybe you need to fix something in the new version?

Share this post


Link to post
Share on other sites
3 minutes ago, X-Tropic said:

Hi! I often have same panic on version 2.2.2 when i try to go to sleep. My LAN - RTL8168G. OS X Sierra 10.12.6. I disable ASPM, Network boot etc...

Besides, if i fall asleep, then after waking up, the network speed drops to a minimum.

At the moment I returned to version 2.2.1 and there are no such problems.
Maybe you need to fix something in the new version?

The driver is working fine, there is no indication for a driver problem in 2.2.2 in particular no reason for a kernel panic. It's your system which is broken (DSDT, system caches, etc.). Please fix your system in order to resolve the problem.

Mieze

Share this post


Link to post
Share on other sites

is this really a bug or somthing in high sierra an sierra when using the kext file the internet works fine after a reboot an then after a few mins it stops an says self assign ip an internet dont work until i reboot the laptop

Share this post


Link to post
Share on other sites
4 minutes ago, kendok said:

is this really a bug or somthing in high sierra an sierra when using the kext file the internet works fine after a reboot an then after a few mins it stops an says self assign ip an internet dont work until i reboot the laptop

It could be almost anything (DHCP issue, hardware problem, BIOS setting, etc.) but there is one thing I can almost certainly rule out: a driver bug! Fix your system in order get it working.

Share this post


Link to post
Share on other sites

such as reinstalling the OS X High Sierra cause i tried it in the installer it does the same thing when downloading the installer for High Sierra in Mac Os Utilites dhcp has no issue cause it works fine on my windows bios an hardware works fine

Share this post


Link to post
Share on other sites
7 minutes ago, kendok said:

such as reinstalling the OS X High Sierra cause i tried it in the installer it does the same thing when downloading the installer for High Sierra in Mac Os Utilites dhcp has no issue cause it works fine on my windows bios an hardware works fine

The fact that it works under Windows rules out a hardware issue but it doesn't rule out a DHCP related problem. Frankly I have no idea what went wrong on your system. Have you checked the BIOS settings? Is the the UEFI network stack and network boot disabled?

Mieze

Share this post


Link to post
Share on other sites

Not sure I have a dell inspiron 15 3567 also looking for WiFi next for qca 9565 I install the is this week soo... Don't blame me

Share this post


Link to post
Share on other sites

Is there any chance that  "Realtek 8822BE Wirelss LAN 802.11ac PCI-E NIC" will work?

Thanks.

Share this post


Link to post
Share on other sites
4 minutes ago, zy94 said:

Is there any chance that  "Realtek 8822BE Wirelss LAN 802.11ac PCI-E NIC" will work?

Thanks.

No! Please check Realtek's website for a macOS driver.

Mieze

Share this post


Link to post
Share on other sites

Hi, I'm running OS X 10.9.5 on my 1st gen Intel laptop.

Currently I'm having this issue, which causes the kext not to load, any fix for this?

Apr  7 07:14:46 Baddless-MacBook-Pro kernel[0]: kxld[com.insanelymac.RealtekRTL8111]: The following symbols are unresolved for this kext:

Apr  7 07:14:46 Baddless-MacBook-Pro kernel[0]: kxld[com.insanelymac.RealtekRTL8111]:     __ZN11IOPCIDevice12setASPMStateEP9IOServicej

Apr  7 07:14:46 Baddless-MacBook-Pro kernel[0]: Can't load kext com.insanelymac.RealtekRTL8111 - link failed.

Apr  7 07:14:46 Baddless-MacBook-Pro kernel[0]: Failed to load executable for kext com.insanelymac.RealtekRTL8111.

Apr  7 07:14:46 Baddless-MacBook-Pro kernel[0]: Kext com.insanelymac.RealtekRTL8111 failed to load (0xdc008016).

Apr  7 07:14:46 Baddless-MacBook-Pro kernel[0]: Failed to load kext com.insanelymac.RealtekRTL8111 (error 0xdc008016).

Apr  7 07:14:46 Baddless-MacBook-Pro.local com.apple.kextd[12]: Load com.insanelymac.RealtekRTL8111 failed; removing personalities from kernel.

Share this post


Link to post
Share on other sites
50 minutes ago, baddles said:

Hi, I'm running OS X 10.9.5 on my 1st gen Intel laptop.

Currently I'm having this issue, which causes the kext not to load, any fix for this?

 

  Hide contents

 

Apr  7 07:14:46 Baddless-MacBook-Pro kernel[0]: kxld[com.insanelymac.RealtekRTL8111]: The following symbols are unresolved for this kext:

Apr  7 07:14:46 Baddless-MacBook-Pro kernel[0]: kxld[com.insanelymac.RealtekRTL8111]:     __ZN11IOPCIDevice12setASPMStateEP9IOServicej

Apr  7 07:14:46 Baddless-MacBook-Pro kernel[0]: Can't load kext com.insanelymac.RealtekRTL8111 - link failed.

Apr  7 07:14:46 Baddless-MacBook-Pro kernel[0]: Failed to load executable for kext com.insanelymac.RealtekRTL8111.

Apr  7 07:14:46 Baddless-MacBook-Pro kernel[0]: Kext com.insanelymac.RealtekRTL8111 failed to load (0xdc008016).

Apr  7 07:14:46 Baddless-MacBook-Pro kernel[0]: Failed to load kext com.insanelymac.RealtekRTL8111 (error 0xdc008016).

Apr  7 07:14:46 Baddless-MacBook-Pro.local com.apple.kextd[12]: Load com.insanelymac.RealtekRTL8111 failed; removing personalities from kernel.

 

The lastest binary requires Sierra or newer. For 10.9.5 try an older version, preferably one which was released while 10.9 was the most recent version of macOS.

Mieze

Share this post


Link to post
Share on other sites
1 hour ago, Mieze said:

The lastest binary requires Sierra or newer. For 10.9.5 try an older version, preferably one which was released while 10.9 was the most recent version of macOS.

Mieze

Ah I see, I'll try it when my computer can be turned on.

(I think it died on me 15 mins ago as of this post....)

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 Teerachat
      Hi every body, I am a new user of mac os. I use IMaC late 2017 mac os high sierra 10.13.6(17G65). I want to use Titan V as an external eGPU for molecular dynamic simulation. First I download 
      Webdriver-387.10.10.15.15.108.pkg. And it cannot detect my eGPU (I use sonnet breakaway box 350 watts). My question are : i) what driver NVIDIA is suitable for this mac os version  and it should be compatible with Titan V ii) what procedures should I follow to complete installation and make it working?.
       
      Thank you so much
       
      Teerachat
    • By eliot6001
      I don't know whether my LAN device will work on MAC and Which version of mac but i still want to run MAC on my PC, Also i checked my CPU-GPU and it turned out that i can Run MAX High sierra but i realized that some people have trouble with Sound and Internet connection so Here's the NAME of my LAN device:
       
      PCI\VEN_10EC&DEV_8136&SUBSYS_012310EC&REV_05\4&45F2A70&0&00E1 as (LAN DEVICE took the name from device manager in  windows). 
      also from compatibleIds i got this:
      PCI\VEN_10EC&DEV_8136&REV_05
       
      Is it Supported on any version of macOS ?
    • 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
      This project is dedicated to the memory of Mausi, the cat I loved more than anybody else.
       

       
      A few days before Christmas I started my latest project, a new driver for recent Intel onboard LAN controllers. My intention was not to replace hnak's AppleIntelE1000e.kext completely but to deliver best performance and stability on recent hardware. That's why I dropped support for a number of older NICs. Currently the driver supports:
       
      5 Series
      82578LM 82578LC 82578DM 82578DC 6 and 7 Series
      82579LM 82579V 8 and 9 Series
      I217LM I217V I218LM I218V I218LM2 I218V2 I218LM3 100 Series (since V2.1.0d0)
      I219LM I219V 200 Series (since V2.3.0d0)
      I219LM I219V 300 Series (since V2.4.0d0)
      I219LM I219V  
      Key Features of the Driver
      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). Support for TCP/IPv6 and UDP/IPv6 checksum offload. Makes use of the chip's TCP Segmentation Offload (TSO) feature with IPv4 and IPv6 in order to reduce CPU load while sending large amounts of data (disabled due to hardware bugs). Fully optimized for Sierra (64bit architecture) but should work with older 64bit versions of macOS too, provided you build from source with the appropriate SDK for the target OS. Support for Energy Efficient Ethernet (EEE). VLAN support is implemented but untested as I have no need for it. The driver is published under GPLv2.  
      Current Status
      The driver has been tested successfully with I217V, I218V and 82579V under 10.9.5 and above. The attached archive includes source code as well as a prebuilt binary (debug version) for Mavericks and newer versions of macOS.   Known Issues
      There seem to be problems while using VMware with version 1.x.x of the driver. In case you are affected use version 2.0.0 or newer.  
      FAQ
      Could you add support of for...? Well, you are probably asking me to add support for one of the older NICs like the 82571/2/3/4L or 82583 and the answer will be no as I dropped support for these chips intentionally. They are broken and I lost more than 2 weeks trying to make it work on the 82574L without success. I was asked to add support for I210, I211 and I350 but as these chips have a completely different architecture, which isn't supported by the underlying Linux driver, this is impossible, sorry. Does it work with Snow Leopard or 32 bit kernels? No and I have no plans to make a version for 32 bit kernels or anything older than Lion. 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.  
      Installation
      Goto /S/L/E and delete AppleIntelE1000e.kext. Recreate the kernel cache. Open System Preferences and delete the corresponding network interface, e. g. en0. 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 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 AppleIntelE1000e.kext from your system because it 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. Changelog
      Version 2.4.0 (2018-04-14) Added support for 300 series versions of I219LM and I219V. Updated underlying Linux source code. Version 2.3.0 (2017-06-20) Added support for 200 series versions of I219LM and I219V. Version 2.2.0 (2016-09-23) Disabled TSO to work around a hardware bug. Version 2.1.0 (2016-05-24) Added support for I219LM and I219V Version 2.0.0 (2015-04-22) First official release which is identical to 2.0.0d2 (only the version number has been changed). Version 2.0.0d2 (2015-04-04) Changed the tx descriptor write back policy for 82579, I217 and I218 to prevent random tx deadlocks. Version 2.0.0d1 (2015-03-14) Uses Apple's private driver interface introduced with 10.8. Supports packet scheduling with QFQ Solves the VMware issue. Version 1.0.0d6 (2015-03-04) Reworked TSO6 support to avoid problems with VMware. Wake-on-LAN now working. Version 1.0.0d5 (2015-02-27) Reworked TSO4 support to eliminate the bug of 1.0.0d4. Added some debug code in order to collect information about the VMware related issue. Version 1.0.0d4 (2015-02-25) Set total length field of the IP-header to zero for TSO4 operations. Report EEE activation state in kernel log message when the link has been established. Version 1.0.0d3 (2015-02-11) Reworked media selection and EEE support (EEE is now activated when both link partners support it. It can be disabled selecting the medium manually). Duplex setting for 10/100 MBit connections is now reported correctly. The number of tx descriptors has been reduced from 2048 to 1024. The code has been cleaned up and obsolete files have been removed. Version 1.0.0d2 (2015-01-31) First development release. Getting the Driver
      The source code can be found on GitHub: https://github.com/Mieze/IntelMausiEthernet There is also a prebuilt binary for 10.11 and above in the download section: http://www.insanelymac.com/forum/files/file/396-intelmausiethernet/ Build from Source for 10.8
      Register as a developer on Apple's developer website. A free membership is sufficient. Download a copy of Xcode 5.1.1 and install it on your machine. In the project select 10.8 as the "Base SDK" and the "Deployment Target". Call "Archive" from the menu "Product" and save the built driver. Credits
      Thanks to RehabMan and Yung Raj for running tests and pointing me in the right direction while I was trying to fix TSO. Special thanks to Yung Raj for motivating me when I was about to give up.
×