Jump to content

IntelMausiEthernet.kext for Intel onboard LAN

Intel Driver LAN I217 I218 82579

  • Please log in to reply
733 replies to this topic

#1
Mieze

Mieze

    Giant Cat

  • Developers
  • 1,190 posts
  • Gender:Female
  • Location:Germany
  • Interests:Cats

*
POPULAR

This project is dedicated to the memory of Mausi, the cat I loved more than anybody else.

 

Attached File  Mausi.jpeg   33.14KB   125 downloads

 

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

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

  1. Goto /S/L/E and delete AppleIntelE1000e.kext.
  2. Recreate the kernel cache.
  3. Open System Preferences and delete the corresponding network interface, e. g. en0.
  4. Reboot.
  5. Install the new driver and recreate the kernel cache. I recommend to use Kext Wizard or a similar utility for the installation.
  6. Reboot
  7. Open System Preferences again, select Network and check if the new network interface has been created automatically or create it manually now.
  8. 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.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)
    1. First development release.

Getting the Driver

Build from Source for 10.8

  1. ​Register as a developer on Apple's developer website. A free membership is sufficient.
  2. Download a copy of Xcode 5.1.1 and install it on your machine.
  3. In the project select 10.8 as the "Base SDK" and the "Deployment Target".
  4. 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.

Edited by Mieze, 19 June 2017 - 11:01 PM.


#2
anonymousnbs

anonymousnbs

    InsanelyMac Sage

  • Members
  • PipPipPipPipPip
  • 277 posts
  • Gender:Male
  • Location:Ho Chi Minh Viet Nam
  • Interests:MAC OS X

i try it and report if have bug :D thank you mieze



#3
malek_bh

malek_bh

    InsanelyMac Protégé

  • Members
  • Pip
  • 2 posts
  • Gender:Male

tested on Dell Latitude E6320 with Intel® 82579LM Gigabit Network ,work ok ,

thank you



#4
buoo

buoo

    The Prodigal Son

  • Moderators
  • 4,748 posts
  • Gender:Male
  • Location:Italy

Pinned!

Thank you :)



#5
AllenRoss

AllenRoss

    InsanelyMac Protégé

  • Banned
  • PipPip
  • 57 posts

Great Job Mieze :D



#6
kilian

kilian

    InsanelyMac Protégé

  • Members
  • Pip
  • 45 posts
  • Gender:Male
  • Location:Milano

Great job!!! Working perfect on my GB. Z87-D3HP :D

One question my ethernet MAC address is 88:88:88:88:87:88, there is some way to change it? 

 

Thanks in advance

Federico



#7
Mieze

Mieze

    Giant Cat

  • Developers
  • 1,190 posts
  • Gender:Female
  • Location:Germany
  • Interests:Cats

One question my ethernet MAC address is 88:88:88:88:87:88, there is some way to change it? 

 

Yes, use ifconfig (see the man page) in Terminal to change the MAC address.

 

Mieze



#8
tarasis

tarasis

    InsanelyMac Protégé

  • Members
  • PipPip
  • 82 posts
  • Gender:Male
  • Location:Near Hamburg, Germany
Wonderful news. I will try it out tomorrow morning.

Thank you for your work Mieze!

#9
Mac Hosehead

Mac Hosehead

    InsanelyMac Protégé

  • Members
  • PipPip
  • 69 posts

It's working on the Intel skull motherboard & Yosemite - 82578DC

 

skull_zpsld0tnrqk.png

 

-MH



#10
genzai

genzai

    InsanelyMac Geek

  • Members
  • PipPipPipPip
  • 201 posts
  • Gender:Male
  • Location:San Francisco

so far so good with 82579V on UP5 TH. If this works well for a few days i will roll it out to the rest of the systems in my care that have supported chips. thanks for all you do Mieze!

 

Whats the driver name stand for?

g\



#11
Mieze

Mieze

    Giant Cat

  • Developers
  • 1,190 posts
  • Gender:Female
  • Location:Germany
  • Interests:Cats

Whats the driver name stand for?

 

Well, Mausi was the name of my mother's cat who died a few weeks ago and I decided to dedicate the driver to Mausi because she was a brilliant cat.

 

:cat:



#12
tarasis

tarasis

    InsanelyMac Protégé

  • Members
  • PipPip
  • 82 posts
  • Gender:Male
  • Location:Near Hamburg, Germany

Installed and working on my Asus Z97-A with Intel218V ethernet.

 

Will keep an eye on Netstats, so far the only things that stand out

 

kctl: 5 send failures

icmp6: 7 bad neighbor advertisement messages (not using ip6 anyway)

arp: 2 ARP entries timed out

 

 

Thank you.



#13
StrangeNoises

StrangeNoises

    InsanelyMac Protégé

  • Members
  • PipPip
  • 66 posts
  • Gender:Female

Mausi installed on my Asus Z87I-PRO (Intel 217V) with Yosemite. All seems to be working so far. (Haven't tried big transfers yet.)



#14
StrangeNoises

StrangeNoises

    InsanelyMac Protégé

  • Members
  • PipPip
  • 66 posts
  • Gender:Female

Mausi installed on my Asus Z87I-PRO (Intel 217V) with Yosemite. All seems to be working so far. (Haven't tried big transfers yet.)

ok, 107GB transferred over rsync over ssh over ipv6 no problems at all. That's a good start. I'll just leave it in use until and unless I have a problem...



#15
avian

avian

    InsanelyMac Protégé

  • Members
  • PipPip
  • 65 posts

Mausi installed on a Gigabyte z97x-ud7th with Intel 217V on Mavericks 10.9.5.  So far so good, a few large-ish transfer to check for issues, no problems yet. 

 

Out of interest is jumbo frame support something planned for the future?



#16
Mieze

Mieze

    Giant Cat

  • Developers
  • 1,190 posts
  • Gender:Female
  • Location:Germany
  • Interests:Cats

Out of interest is jumbo frame support something planned for the future?

 

I thought about implementing support for jumbo frames but I don't know if it's worth the effort as there is almost no gain in throughput in real world scenarios.

 

Mieze



#17
rednous

rednous

    InsanelyMac Sage

  • Members
  • PipPipPipPipPipPip
  • 420 posts
  • Gender:Male
  • Location:Galaxy: Milky Way
  • Interests:graphic design, mac, progressive and house

Mieze, thank you for your massive (imho) work. Thumbs up  :thumbsup_anim:

 

So far the driver's working nice (also having correct report of the NIC model / version). Will report if any issues or strange behaviour occur:

 

28thvno.png



#18
buoo

buoo

    The Prodigal Son

  • Moderators
  • 4,748 posts
  • Gender:Male
  • Location:Italy

Mieze, thank you for your massive (imho) work. Thumbs up  :thumbsup_anim:
 
So far the driver's working nice (also having correct report of the NIC model / version). Will report if any issues or strange behaviour occur:
 
28thvno.png

 
Does it work better than hank's E1000e with Yos ?

#19
rednous

rednous

    InsanelyMac Sage

  • Members
  • PipPipPipPipPipPip
  • 420 posts
  • Gender:Male
  • Location:Galaxy: Milky Way
  • Interests:graphic design, mac, progressive and house

 Does it work better than hank's E1000e with Yos ?

 

Can't tell yet it's better than hnak's (guess it is, cause Mieze says he dropped pretty old models / respective code in his fork), but Mieze's driver's displaying the model of my NIC at least so far. Will test / investigate further.



#20
buoo

buoo

    The Prodigal Son

  • Moderators
  • 4,748 posts
  • Gender:Male
  • Location:Italy
Do you know a good way to test the transfer rate of an ethernet/wifi chip?
I'd like to make a comparison between two different chips.





Also tagged with one or more of these keywords: Intel, Driver, LAN, I217, I218, 82579


0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

© 2017 InsanelyMac  |   News  |   Forum  |   Downloads  |   OSx86 Wiki  |   Designed by Ed Gain  |   Logo by irfan  |   Privacy Policy