Jump to content
InsanelyMac Forum
Mieze

Driver for Realtek's RTL810x Fast Ethernet Series

Recommended Posts

Zythyr and I, we managed to finish the next development release of the driver. I updated the source code and the binaries attached to the first post of this thread a few minutes ago. Everyone is encouraged to test the new release on her/his system.

 

Mieze 

Unfortunately, ethernet failed to work after wake. One thing I notice is that Hurt has ethernet card built-in in system info, but not for mine. Does it matter?

Share this post


Link to post
Share on other sites
Advertisement

Unfortunately, ethernet failed to work after wake. One thing I notice is that Hurt has ethernet card built-in in system info, but not for mine. Does it matter?

 

No, I don't think so. Check your BIOS settings. Do you have Network Boot or the UEFI network stack enabled? Please disable it. What happens when you enable/disable the network interface using ifconfig up/down in Terminal? I'm asking because this is almost the same as sleep/wakeup.

 

Mieze

Share this post


Link to post
Share on other sites

No, I don't think so. Check your BIOS settings. Do you have Network Boot or the UEFI network stack enabled? Please disable it. What happens when you enable/disable the network interface using ifconfig up/down in Terminal? I'm asking because this is almost the same as sleep/wakeup.

 

Mieze

My BIOS supports UEFI, but I cannot disable network boot since there is no option.

 

I tried ifconfig en0 up/down many times, but there seems no difference. Ethernet will continue work before sleep and fail after wake, and ifconfig up/down is not changing anything. So I guess something is different between ifconfig up/down and actual sleep/wake.

 

I also tried to compare ioreg before and after sleep. I found IOPCIPMCSState is different in these two cases. See attached picture, not sure if it helps though:

post-732552-0-87386600-1393456289_thumb.png

Share this post


Link to post
Share on other sites

I tried ifconfig en0 up/down many times, but there seems no difference. Ethernet will continue work before sleep and fail after wake, and ifconfig up/down is not changing anything. So I guess something is different between ifconfig up/down and actual sleep/wake.

 

Sorry, in case my post was inaccurate but this is not what I asked for. Call ifconfig down/up while network is functional and let me know if it resumes operation after ifconfig up.

 

Mieze

Share this post


Link to post
Share on other sites

Sorry, in case my post was inaccurate but this is not what I asked for. Call ifconfig down/up while network is functional and let me know if it resumes operation after ifconfig up.

 

Mieze

Mac:~ peter$ sudo ifconfig up
ifconfig: interface up does not exist
Mac:~ peter$ sudo ifconfig down
ifconfig: interface down does not exist
Mac:~ peter$ ifconfig up

I don't think it is the right syntax. Then I tried ifconfig en0 down which successfully disabled my ethernet, the LED in ethernet port also stopped blinking. After ifconfig en0 up, ethernet shows "Connected" and everything is normal.

Share this post


Link to post
Share on other sites

I don't think it is the right syntax. Then I tried ifconfig en0 down which successfully disabled my ethernet, the LED in ethernet port also stopped blinking. After ifconfig en0 up, ethernet shows "Connected" and everything is normal.

 

 

Ok, at least we know now that the enable() and disabled() routines are working properly.

 

Mieze

Share this post


Link to post
Share on other sites

Great work!Thank you~

Work perfectly on my RTL8103e Chipest 7(shown in kernel log)

My laptop is dell insprision 15R n5010

Work well afer wake up

Share this post


Link to post
Share on other sites

@lisai9093: I tried to find some background information about IOPCIPMCSState but found nothing. Therefore I checked this property of en0 on my 2011 iMac and it shows a similar behavior. IOPCIPMCSState changed from 0x0 before sleep to 0x2108 after wakeup.

 

Mieze

Share this post


Link to post
Share on other sites

@lisai9093: I tried to find some background information about IOPCIPMCSState but found nothing. Therefore I checked this property of en0 on my 2011 iMac and it shows a similar behavior. IOPCIPMCSState changed from 0x0 before sleep to 0x2108 after wakeup.

 

Mieze

uhmm that's strange. i also did some other test on ethernet setting that might be useful to you:

 

i tried to play with DHCP in ethernet setting. Test after wakeup, if DHCP is enabled, the ethernet card cannot get IP address from my router, there is only self-assigned IP instead. Then I double checked my router site (192.168.0.1), under "device table" section where all devices and their IP listed. My machine's ethernet port is not in the list.

 

So I disabled DHCP and assigned IP address myself in Setting. I put 192.168.0.14 as my IP because it is not used to prevent IP conflict. Then I saw this IP showing up in the "Device List". And the MAC address matches with my ethernet card's MAC address.

 

Here is some log lines for one plug-in and out cycle:

Feb 28 17:15:13 Mac kernel[0]: Ethernet [RealtekRTL8100]: Link up on en0, 100-Megabit, Full-duplex, No flow-control
Feb 28 17:15:16 Mac.local configd[19]: network changed: v4(en0+:192.168.0.14, en1) DNS! Proxy! SMB
Feb 28 17:15:18 Mac.local racoon[320]: failed to bind to address fd00::a9e:1ff:fe2b:b425[500] (Can't assign requested address).
Feb 28 17:15:18 Mac.local racoon[320]: failed to bind to address fd00::a9e:1ff:fe2b:b425[500]: because interface address is/was not ready (flags 42).
Feb 28 17:15:18 Mac.local racoon[320]: failed to bind to address fd00::a9e:1ff:fe2b:b425[4500] (Can't assign requested address).
Feb 28 17:15:18 Mac.local racoon[320]: failed to bind to address fd00::a9e:1ff:fe2b:b425[4500]: because interface address is/was not ready (flags 42).
Feb 28 17:15:18 Mac.local racoon[320]: failed to bind to address fd00::a9e:1ff:fe2b:b425[500] (Can't assign requested address).
Feb 28 17:15:18 Mac.local racoon[320]: failed to bind to address fd00::a9e:1ff:fe2b:b425[500]: because interface address is/was not ready (flags 42).
Feb 28 17:15:18 Mac.local racoon[320]: failed to bind to address fd00::a9e:1ff:fe2b:b425[4500] (Can't assign requested address).
Feb 28 17:15:18 Mac.local racoon[320]: failed to bind to address fd00::a9e:1ff:fe2b:b425[4500]: because interface address is/was not ready (flags 42).
Feb 28 17:15:18 Mac.local configd[19]: network changed: v4(en0:192.168.0.14, en1) DNS* Proxy SMB
Feb 28 17:15:18 Mac.local racoon[320]: failed to bind to address fd00::a9e:1ff:fe2b:b425[500] (Can't assign requested address).
Feb 28 17:15:18 Mac.local racoon[320]: failed to bind to address fd00::a9e:1ff:fe2b:b425[500]: because interface address is/was not ready (flags 42).
Feb 28 17:15:18 Mac.local racoon[320]: failed to bind to address fd00::a9e:1ff:fe2b:b425[4500] (Can't assign requested address).
Feb 28 17:15:18 Mac.local racoon[320]: failed to bind to address fd00::a9e:1ff:fe2b:b425[4500]: because interface address is/was not ready (flags 42).
Feb 28 17:15:19 Mac.local configd[19]: network changed.
Feb 28 17:15:23 Mac.local AirPlayUIAgent[876]: 2014-02-28 05:15:23.988534 PM [AirPlayUIAgent] Changed PIN pairing: no
Feb 28 17:15:24 Mac.local AirPlayUIAgent[876]: 2014-02-28 05:15:24.038392 PM [AirPlayUIAgent] Changed PIN pairing: no
Feb 28 17:15:24 Mac.local com.apple.WebKit.Networking[934]: tcp_connection_destination_prepare_complete 5769 connectx to 192.168.0.1#80 failed: 64 - Host is down
Feb 28 17:15:24 Mac.local com.apple.WebKit.Networking[934]: tcp_connection_handle_destination_prepare_complete 5769 failed to connect
Feb 28 17:15:24 Mac.local com.apple.WebKit.Networking[934]: tcp_connection_destination_prepare_complete 5769 connectx to 192.168.0.1#80 failed: 64 - Host is down
Feb 28 17:15:24 Mac.local com.apple.WebKit.Networking[934]: tcp_connection_handle_destination_prepare_complete 5769 failed to connect
Feb 28 17:15:40 Mac kernel[0]: Ethernet [RealtekRTL8100]: Link down on en0

Share this post


Link to post
Share on other sites

 

i tried to play with DHCP in ethernet setting. Test after wakeup, if DHCP is enabled, the ethernet card cannot get IP address from my router, there is only self-assigned IP instead. Then I double checked my router site (192.168.0.1), under "device table" section where all devices and their IP listed. My machine's ethernet port is not in the list.

 

So I disabled DHCP and assigned IP address myself in Setting. I put 192.168.0.14 as my IP because it is not used to prevent IP conflict. Then I saw this IP showing up in the "Device List". And the MAC address matches with my ethernet card's MAC address.

 

In the device table on the router? This would mean that after a wakeup packets are going out, i.e. the transmitter is working but the receiver isn't. Maybe I should check the receiver config for your chipset again. There might be a hidden error?

 

Mieze

Share this post


Link to post
Share on other sites

Just tested this kext on my U310 (with 8105E) and it work great.  

I did have to configure it manually tho.  Automatic did not work for me (it kept switching between connected and disconnected).
My settings were 
100baseTX
full duplex
standard (1500)

I've tested waking from sleep as well as unplugging and re-plugging the ethernet cable and using both methods, I was able to get an IP and internet access.

Share this post


Link to post
Share on other sites

Just tested this kext on my U310 (with 8105E) and it work great.  

 

I did have to configure it manually tho.  Automatic did not work for me (it kept switching between connected and disconnected).

My settings were 

100baseTX

full duplex

standard (1500)

 

I've tested waking from sleep as well as unplugging and re-plugging the ethernet cable and using both methods, I was able to get an IP and internet access.

 

Which chipset? Please see the kernel logs.

 

Mieze

Share this post


Link to post
Share on other sites

Just tested this kext on my U310 (with 8105E) and it work great.  

 

I did have to configure it manually tho.  Automatic did not work for me (it kept switching between connected and disconnected).

My settings were 

100baseTX

full duplex

standard (1500)

 

I've tested waking from sleep as well as unplugging and re-plugging the ethernet cable and using both methods, I was able to get an IP and internet access.

Can you upload ur DSDT? Just wanna check the ethernet part.

Share this post


Link to post
Share on other sites

Which chipset? Please see the kernel logs.

 

Mieze

 

do you mean this?

2/28/14 8:37:31.000 PM kernel[0]: Ethernet [RealtekRTL8100]: RTL8105E: (Chipset 12) at 0xffffff80dec3d000,  4:7d:7b:b8: 5:b8

Can you upload ur DSDT? Just wanna check the ethernet part.

 

how do I add attachments?

Share this post


Link to post
Share on other sites

do you mean this?

2/28/14 8:37:31.000 PM kernel[0]: Ethernet [RealtekRTL8100]: RTL8105E: (Chipset 12) at 0xffffff80dec3d000,  4:7d:7b:b8: 5:b8

 

how do I add attachments?

You can click "More Reply Option" at bottom right corner. Then attach your file. Thx in advance.

Share this post


Link to post
Share on other sites

I did another test: to unload and reload the rtl8100.kext.

 

After sleep, console shows:

Before unload/reload:
Ethernet [RealtekRTL8100]: RTL8105E: (Chipset 12) at 0xffffff80f124e000,  8:9e: 1:2b:b4:25

After:
Ethernet [RealtekRTL8100]: RTL8105E: (Chipset 12) at 0xffffff80e9aa5000,  0: 0: 0: 0: 0: 0

Shows MAC address is not properly initialized.

 

And I tried this procedure before sleep, no problem at all. Wish it is helpful info.

Share this post


Link to post
Share on other sites

I did another test: to unload and reload the rtl8100.kext.

 

After sleep, console shows:

Before unload/reload:
Ethernet [RealtekRTL8100]: RTL8105E: (Chipset 12) at 0xffffff80f124e000,  8:9e: 1:2b:b4:25

After:
Ethernet [RealtekRTL8100]: RTL8105E: (Chipset 12) at 0xffffff80e9aa5000,  0: 0: 0: 0: 0: 0

Shows MAC address is not properly initialized.

 

And I tried this procedure before sleep, no problem at all. Wish it is helpful info.

 

Yeah, got an idea! Are you able to build from source?

 

Mieze

Share this post


Link to post
Share on other sites

Yeah, got an idea! Are you able to build from source?

 

Mieze

Nice. No, I don't have Xcode installed. I could download it but need some time.

Share this post


Link to post
Share on other sites

 Just returned home. I'll send you a new version to test soon.

 

Mieze

Please try the attached version and report back.

 

Good luck!

 

Mieze

Thx. Unfortunately it is still not working. Unload/reload shows:

Before:
Ethernet [RealtekRTL8100]: RTL8105E: (Chipset 12) at 0xffffff80f136d000,  8:9e: 1:2b:b4:25

After:
Ethernet [RealtekRTL8100]: RTL8105E: (Chipset 12) at 0xffffff80f136d000,  0: 0: 0: 0: 0: 0

Share this post


Link to post
Share on other sites

@lisai9093: Can you please send me your DSDT. It might be as well something outside of thee driver which causes the failure after wakeup.

 

Mieze

Share this post


Link to post
Share on other sites

@lisai9093: Can you please send me your DSDT. It might be as well something outside of thee driver which causes the failure after wakeup.

 

Mieze

 

Here it is:dsdt.aml.zip

 

I've tried @ikkoku's DSDT without success.  :(

Share this post


Link to post
Share on other sites

Here it is:attachicon.gifdsdt.aml.zip

 

I've tried @ikkoku's DSDT without success.  :(

 

I've checked your DSDT and found no problem. It's really strange but it seems as if your NIC doesn't get powered on completely after wakeup.

 

As ikkoku has no problems with sleep/wakeup using the same chipset, I assume that the cause of the problem isn't located inside the driver. Have you verified that there is no other driver for your NIC installed. I recently had a user reporting a funny problem with the RTL8111 driver and finally it turned out that he had forgotten to remove Realtek's own driver before installing mine.

 

You should also review your BIOS settings very carefully. Is energy saving and suspension (sleep = S3 state) configured correctly? Are PCIe devices allowed to generate wakeup events? What entity is handling wakeup events: the BIOS or OS X?

 

Mieze

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 ITzTravelInTime
      KX AUDIO DRIVER MOD
       
      Hi guys i am a small developer, i really like to use my sound blaster cards on my machines and i love also coding, so when i find the source code for the kx audio driver on git hub and then Eugene, the creator of kx audio driver decided to no longer maintain the project, i decided to start working on a mod of this driver. 
       
      With my mod, created starting from the sources of the last version of kx audio driver, and also by using apple developer documentation for pci and audio drivers as reference, i am working to achieve 2 things mainly: get all the cards supported by the driver to work with all the recent versions os macOS and add support for other cards that are not officially supported by the driver that works or could, but needs to be more properly supported.
       
      This driver is made to support cards based on the E-mu 10k1, 10k2 and similars (like what is used by audigy rx and audigy 4 cards).
       
      Supported cards are:
       
       - most of the sound blaster live!, live! 5.1 and live! 5.1 digital series
       - sound blaster 512
       - sound blaster 256
       - other creative and e-mu sound cards based on the 10k1 chip (cards with the ES1370/ES1371/ES1372/ES1373 chips are not supported)
       - sound blaster Audigy series (1 st gen)
       - sound blaster Audigy 2  and audigy 2 zs series
       - E-MU cards based on the 10k2 sound chip
       - Some Audigy 4 cards (SB0610 only) and the audigy 4 pro
       - Sound blaster Audigy RX (sb0155)
       - other creative and e-mu cards based on the (10k2, 10k2,5 and CA10300 based cards)
       
      NOT supported cards:
       
       - Any ISA Sound card
       - ES1370/ES1371/ES1372/ES1373 based sound cards
       - CMI8738/CMI8788 based cards
       - Any CA0106 based card and cards with similar architectures (like sound blaster live! 24 bit, sound blaster audigy SE SB0570, audigy LS and similars, but audigy SA is supported)
       - Any sound blaster x-fi (some of them works on macOS using a modified version of voodoo hda)
       - Any sound blaster recon3D
       - Any sound blaster Z/ZS/ZX and similar series
       - Any sound blaster AE5 series
       
      In the time being the things i have modded or added with this mod are:
       
      - increased the simple buffer frames number with different values for emu10k1 based cards and emu10k2 based cards (including recent audigy 4 and rx) to reduce and all the audio cracking issues and possibly fixing all of them on a lot of cards
       
      - added a more proper support for the pci express sound blaster audigy rx (which basically is an audigy 4 with a pcie bridge chip) 
       
      - added more fancy names for the cards in the settings and other menus (so the name will be, for example, SB live! 5.1 SB0060 instead of kx SB0060 [e880] witch was shown in the original driver)
       
      - added support to sample rate chaning and added lots of sample rates (from 8 khz to 176,4 khz) to accomodate any possible usecase (note that 10k1 sound cards are limited up to 48khz sample rate, and 10k2 based cards for now are limited up to 176,4 khz and because of issues getting 192 khz to work, for now the driver goes up to 176,4 khz for supported cards) 
       
      - added boot args to manage the driver:
       
      Boot args to use with the kx audio driver mod: -kx_disable or -kxdisable or -kxoff This will prevent the driver from doing any initialization work, so the driver is basically disabled, use it to boot your ssytem in case the driver is giving you issues and kernel panics while you are trying to boot/using your system, so you are able to remove this driver or replace it with another version of it or to do some truble shooting. -kx_debug or -kxdebug or -kxspec Will show more debug info about the card, mainly the i/o port address and the kind of bus that it uses -kx_exp_deb or -kx_beta or -kxbeta Will enable experimental and probably not working or unstable features like showing inputs for the card or 192 khz sampling rate, use it only for testing and debug purposes, this may likely cause instability and problems in the everyday usage! Use it at your own risk! -kx_original or -kxoriginal This will basically turn off almost all the mods of this mod, so the driver will come to work as it was before modding it, this can be usefoul as a "safe mode" like feture to have a working driver in case of problems with features of the mod, so using this means no crsking issues improvements, only 48 khz sample rate and only features of the non-modded kx audio driver for mac os x  
      - created a script file to use with the driver for debug and also installer replacement, it can be also used to unload and reload, replacement of the driver without rebooting
       
      What i'd like to implement but i don't know how to do:
       
       - I'd like mainly to add a more proper support to the pci bridge chip of the audigy rx,
       
       - have audio inputs working,
       
       - fix the support when using more than one card, to get all the cards shown in the settings and other menus,
       
       - have the gameport/gameport midi port of older cards to be used in mac os as a midi in/out
       
      If other developers would like to join and help me, you can, and also an hand from other people with testing and feedback will be nice.
       
      link for the kext only (if you have clover put it in [your clover efi folder]/clover/kexts/[your macOS version]/ so it will not be deleted when updating macOS):
               - download from the downloads section:          kX Audio Driver Mod by ITzTravelInTime 1.01                                                                                    - external download:                                      https://dl.dropboxus...Driver.kext.zip   link for the installer pack (the best way to install it, but you have to reinstall it when you upgrade macOS, remeber to fix kext permitions and rebuild the kernelcache if you want to remove the kext from it's install directory without using the unistall feature of the provvided script):              - download:                                                   https://dl.dropboxus...aller pack.zip   Source code from Git Hub:          -  github repo:                                               https://github.com/ITzTravelInTime/kx-audio-driver   NOTE: Some system because of some problems with the HPET may need to use FixHPET in clover and to install the kext in /System/Library/Extensions  






    • By ITzTravelInTime
      This driver is a mod of the popular kx audio driver for mac os x, the project goal is to still maintaining it for the future releases of mac os and to include as much cards as possible and to get all the features of the cards to work.
       
      Currently the only features not supported are audio inputs and integrated midi and synth capabilitues of the cards, and some minor things like creative remote controllers or software controlled volume gears on creative external drives and bays)
       
      It supports most the sound blaster live! series cards, the sound blaster PCI 512, most of the audigy (emu 10k2 based) series, audigy 1, audigy 2, audigy 2 zs, audigy 4 (SB0610), audigy 4 pro, audigy 5 and audigy rx (sb1550) and some e-mu edsp audio cards with all the recent versions of mac os, tested to work with mac os yosemite, el capitan, sierra and high sierra on intel based machines from socket 775 to 1151 (including enthusiast platforms like x58, x79, x99, x299) and also confirmed to work on mac pros.
       
      reference topic:
       
      Kx audio driver mod [sound blaster live!, audigy 1/2/4/RX emu edsp]
    • By ivanagui2
      VMQemuVGA display adapter driver for OSx86 running as a VirtualBox guest. The binary should work on all OSs from Snow Leopard up to Yosemite 10.10. It allows to set different screen resolutions in VirtualBox from System Preferences.   The changes I've made to the fork have been minimal.
      GitHub project page Binary and source releases Special thanks:
      PureDarwin
      probonopd
      rafirafi
      Zenith432
      VMware, Inc


    • 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). 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 Yosemite. 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. 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.
    • By Mieze
      Driver for recent Intel onboard LAN controllers. 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
      I219LM I219V 200 and 300 Series
      I219LM I219V Please see the project's homepage at http://www.insanelymac.com/forum/topic/304235-intelmausiethernetkext-for-intel-onboard-lan/ for a detailed project description.
×