Jump to content
Mieze

Driver for Realtek's RTL810x Fast Ethernet Series

169 posts in this topic

Recommended Posts

Meize,

 

I really really want to thank you very much for taking the effort and building the FE driver for us! I really appreciate it. 

Share this post


Link to post
Share on other sites
Advertisement

I just update the binary and the source code in the first post of this thread with the release candidate. Changes since the last version are minimal, nevertheless I would like everyone to test it again. In case nobody finds a serious problem in this release candidate I will make it the official version 1.0.

 

Good luck!

 

Mieze 

Share this post


Link to post
Share on other sites

Hello Mieze,

 

great work so far. Looking a long time for a working driver.

It's a Lenovo Lappy Z560 from my daughter running 10.9.2.

The link is not coming up. See log.

Last three lines will const. repeated.

 

Ethernet [RealtekRTL8100]: Warning: PCIe ASPM enabled.

Ethernet [RealtekRTL8100]: EEE support enabled.

Ethernet [RealtekRTL8100]: TCP/IPv4 segmentation offload enabled.

Ethernet [RealtekRTL8100]: TCP/IPv6 checksum offload enabled.

Ethernet [RealtekRTL8100]: Using interrupt mitigate value 0x0.

Ethernet [RealtekRTL8100]: RTL8103E: (Chipset 7) at 0xffffff807b336000, xx:xx:xx:xx:xx:xx

Ethernet [RealtekRTL8100]: Link up on en0, 100-Megabit, Full-duplex, flow-control

Ethernet [RealtekRTL8100]: Tx timeout. Lost interrupt?

Ethernet [RealtekRTL8100]: Tx stalled? Resetting chipset. ISR=0xffff, IMR=0xffff.

Ethernet [RealtekRTL8100]: Link up on en0, 100-Megabit, Full-duplex, flow-control

Ethernet [RealtekRTL8100]: Tx timeout. Lost interrupt?

Ethernet [RealtekRTL8100]: Tx stalled? Resetting chipset. ISR=0xffff, IMR=0xffff.

post-52582-0-70846100-1396439588_thumb.png

Share this post


Link to post
Share on other sites

Hello Mieze,

 

great work so far. Looking a long time for a working driver.

It's a Lenovo Lappy Z560 from my daughter running 10.9.2.

The link is not coming up. See log.

Last three lines will const. repeated.

 

Ethernet [RealtekRTL8100]: Warning: PCIe ASPM enabled.

Ethernet [RealtekRTL8100]: EEE support enabled.

Ethernet [RealtekRTL8100]: TCP/IPv4 segmentation offload enabled.

Ethernet [RealtekRTL8100]: TCP/IPv6 checksum offload enabled.

Ethernet [RealtekRTL8100]: Using interrupt mitigate value 0x0.

Ethernet [RealtekRTL8100]: RTL8103E: (Chipset 7) at 0xffffff807b336000, xx:xx:xx:xx:xx:xx

Ethernet [RealtekRTL8100]: Link up on en0, 100-Megabit, Full-duplex, flow-control

Ethernet [RealtekRTL8100]: Tx timeout. Lost interrupt?

Ethernet [RealtekRTL8100]: Tx stalled? Resetting chipset. ISR=0xffff, IMR=0xffff.

Ethernet [RealtekRTL8100]: Link up on en0, 100-Megabit, Full-duplex, flow-control

Ethernet [RealtekRTL8100]: Tx timeout. Lost interrupt?

Ethernet [RealtekRTL8100]: Tx stalled? Resetting chipset. ISR=0xffff, IMR=0xffff.

 

The link is up but the transmitter hangs, but this doesn't seem to be the reason which is causing the trouble. Please take a look at the line in the logs identifying the chipset and compare it with System Profiler's screenshoot. It says RTL8103E while the screenshot shows an RTL8101E. There must be something which is interfering. Have you removed any other driver for the NIC which you installed previously?

 

Or have you modified the source in any way?

 

Mieze

Share this post


Link to post
Share on other sites

The link is up but the transmitter hangs, but this doesn't seem to be the reason which is causing the trouble. Please take a look at the line in the logs identifying the chipset and compare it with System Profiler's screenshoot. It says RTL8103E while the screenshot shows an RTL8101E. There must be something which is interfering. Have you removed any other driver for the NIC which you installed previously?

 

Or have you modified the source in any way?

 

Mieze

I had a not working kext installed to have an ethernet0.

Removed that and installed yours a second time and deleted network.plist.

Now it works! Great job!

 

Thanks

verleihnix

Share this post


Link to post
Share on other sites

I had a not working kext installed to have an ethernet0.

Removed that and installed yours a second time and deleted network.plist.

Now it works! Great job!

 

Thanks

verleihnix

 

Thanks for the information. Have fun!

 

Mieze

Share this post


Link to post
Share on other sites

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

Thanks, I finally solve the problem!

 

The key is getting MAC address. My computer seems having issue getting ethernet MAC address (maybe hardware related). It was happening on Mac OS only, but now on Win and Ubuntu as well for some unknown reasons. So I need to specify MAC address manually. On Mac OS, it is:

sudo ifconfig en0 ether xx:xx:xx:xx:xx:xx

Since en0 is my ethernet. Similar methods need to be performed in other OSes.

Share this post


Link to post
Share on other sites

@lisai9093: Thanks for sharing the information. It looks like your NIC's EEPROM, which stores the MAC address, is messed up so that getting the MAC address fails.

 

Mieze

Share this post


Link to post
Share on other sites

Can someone build the kext for me(Im using mavericks 10.9.0) I want try to build it with my own but my connection too slow to downloading xcode..realy appreciated if someone able to help me..

Share this post


Link to post
Share on other sites

Can someone build the kext for me(Im using mavericks 10.9.0) I want try to build it with my own but my connection too slow to downloading xcode..realy appreciated if someone able to help me..

 

Use the latest prebuilt version posted in this thread.

 

Mieze

Share this post


Link to post
Share on other sites

@lisai9093: There is a DOS diagnostic utility available for download at Realtek's website. It's name is RSET8136 and, although I haven't checked myself, it might have an option to rewrite the NIC's EEPROM in order to restore the original MAC address. Please see: http://www.realtek.com.tw/downloads/downloadsView.aspx?Langid=1&PNid=14&PFid=7&Level=5&Conn=4&DownTypeID=3&GetDown=false

 

Good luck!

 

Mieze

Share this post


Link to post
Share on other sites

@lisai9093: There is a DOS diagnostic utility available for download at Realtek's website. It's name is RSET8136 and, although I haven't checked myself, it might have an option to rewrite the NIC's EEPROM in order to restore the original MAC address. Please see: http://www.realtek.com.tw/downloads/downloadsView.aspx?Langid=1&PNid=14&PFid=7&Level=5&Conn=4&DownTypeID=3&GetDown=false

 

Good luck!

 

Mieze

Thanks man~

This RSET8136 is for diagnoses only. I found PG8136 tool that can write MAC into EEPROM. There is no problem getting MAC address anymore, even after sleep!

Share this post


Link to post
Share on other sites

Mieze,

Awesome work! I will report back after iperf testing on my RTL8105E: (Chipset 12).

7/10/14 4:04:09.000 PM kernel[0]: Ethernet [RealtekRTL8100]: PCI power management capabilities: 0xffc3.
7/10/14 4:04:09.000 PM kernel[0]: Ethernet [RealtekRTL8100]: PME# from D3 (cold) supported.
7/10/14 4:04:09.000 PM kernel[0]: Ethernet [RealtekRTL8100]: PCIe link capabilities: 0x00077c11, link control: 0x0141.
7/10/14 4:04:09.000 PM kernel[0]: Ethernet [RealtekRTL8100]: Warning: PCIe ASPM enabled.
7/10/14 4:04:09.000 PM kernel[0]: Ethernet [RealtekRTL8100]: EEE support enabled.
7/10/14 4:04:09.000 PM kernel[0]: Ethernet [RealtekRTL8100]: TCP/IPv4 segmentation offload enabled.
7/10/14 4:04:09.000 PM kernel[0]: Ethernet [RealtekRTL8100]: TCP/IPv6 checksum offload enabled.
7/10/14 4:04:09.000 PM kernel[0]: Ethernet [RealtekRTL8100]: Using interrupt mitigate value 0x0.
7/10/14 4:04:09.000 PM kernel[0]: Ethernet [RealtekRTL8100]: RTL8105E: (Chipset 12) at 0xffffff8103bb5000,  xx:xx:xx:xx:xx:xx <= MAC address identified correctly;  removed from here
7/10/14 4:04:09.000 PM kernel[0]: Ethernet [RealtekRTL8100]: MSI interrupt index: 1
7/10/14 4:04:09.000 PM kernel[0]: Ethernet [RealtekRTL8100]: kIOEthernetWakeOnMagicPacket added to filters.
7/10/14 4:04:09.000 PM kernel[0]: Ethernet [RealtekRTL8100]: Already in power state 1.
7/10/14 4:06:38.000 PM kernel[0]: Ethernet [RealtekRTL8100]: Link up on en0, 100-Megabit, Full-duplex, No flow-control

Share this post


Link to post
Share on other sites

Mieze,

You did it again! Outstanding work!

iperf from Linux to OS X (10.9.4)

[ ID] Interval       Transfer     Bandwidth
[  3]  0.0- 1.0 sec  12.6 MBytes   106 Mbits/sec
[  3]  1.0- 2.0 sec  11.2 MBytes  94.4 Mbits/sec
[  3]  2.0- 3.0 sec  11.1 MBytes  93.3 Mbits/sec
[  3]  3.0- 4.0 sec  11.2 MBytes  94.4 Mbits/sec
[  3]  4.0- 5.0 sec  11.1 MBytes  93.3 Mbits/sec
[  3]  5.0- 6.0 sec  11.9 MBytes  99.6 Mbits/sec
[  3]  6.0- 7.0 sec  11.1 MBytes  93.3 Mbits/sec
[  3]  7.0- 8.0 sec  11.2 MBytes  94.4 Mbits/sec
[  3]  8.0- 9.0 sec  11.1 MBytes  93.3 Mbits/sec
[  3]  9.0-10.0 sec  11.2 MBytes  94.4 Mbits/sec
[  3] 10.0-11.0 sec  11.1 MBytes  93.3 Mbits/sec
[  3] 11.0-12.0 sec  11.2 MBytes  94.4 Mbits/sec
[  3] 12.0-13.0 sec  11.4 MBytes  95.4 Mbits/sec
[  3] 13.0-14.0 sec  11.2 MBytes  94.4 Mbits/sec
[  3] 14.0-15.0 sec  10.8 MBytes  90.2 Mbits/sec
[  3] 15.0-16.0 sec  11.2 MBytes  94.4 Mbits/sec
[  3] 16.0-17.0 sec  11.4 MBytes  95.4 Mbits/sec
[  3] 17.0-18.0 sec  11.4 MBytes  95.4 Mbits/sec
[  3] 18.0-19.0 sec  11.4 MBytes  95.4 Mbits/sec
[  3] 19.0-20.0 sec  10.8 MBytes  90.2 Mbits/sec
[  3] 20.0-21.0 sec  11.4 MBytes  95.4 Mbits/sec
[  3] 21.0-22.0 sec  11.2 MBytes  94.4 Mbits/sec
[  3] 22.0-23.0 sec  11.4 MBytes  95.4 Mbits/sec
[  3] 23.0-24.0 sec  11.2 MBytes  94.4 Mbits/sec
[  3] 24.0-25.0 sec  11.2 MBytes  94.4 Mbits/sec
[  3] 25.0-26.0 sec  10.8 MBytes  90.2 Mbits/sec
[  3] 26.0-27.0 sec  11.2 MBytes  94.4 Mbits/sec
[  3] 27.0-28.0 sec  11.2 MBytes  94.4 Mbits/sec
[  3] 28.0-29.0 sec  11.2 MBytes  94.4 Mbits/sec
[  3] 29.0-30.0 sec  11.2 MBytes  94.4 Mbits/sec
[  3] 30.0-31.0 sec  11.4 MBytes  95.4 Mbits/sec
[  3] 31.0-32.0 sec  11.2 MBytes  94.4 Mbits/sec
[  3] 32.0-33.0 sec  11.4 MBytes  95.4 Mbits/sec
[  3] 33.0-34.0 sec  11.2 MBytes  94.4 Mbits/sec
[  3] 34.0-35.0 sec  10.8 MBytes  90.2 Mbits/sec
[  3] 35.0-36.0 sec  11.2 MBytes  94.4 Mbits/sec
[  3] 36.0-37.0 sec  11.4 MBytes  95.4 Mbits/sec
[  3] 37.0-38.0 sec  11.4 MBytes  95.4 Mbits/sec
[  3] 38.0-39.0 sec  11.4 MBytes  95.4 Mbits/sec
[  3] 39.0-40.0 sec  11.2 MBytes  94.4 Mbits/sec
[  3] 40.0-41.0 sec  10.8 MBytes  90.2 Mbits/sec
[  3] 41.0-42.0 sec  11.2 MBytes  94.4 Mbits/sec
[  3] 42.0-43.0 sec  11.2 MBytes  94.4 Mbits/sec
[  3] 43.0-44.0 sec  11.2 MBytes  94.4 Mbits/sec
[  3] 44.0-45.0 sec  11.4 MBytes  95.4 Mbits/sec
[  3] 45.0-46.0 sec  11.4 MBytes  95.4 Mbits/sec
[  3] 46.0-47.0 sec  10.8 MBytes  90.2 Mbits/sec
[  3] 47.0-48.0 sec  11.2 MBytes  94.4 Mbits/sec
[  3] 48.0-49.0 sec  11.2 MBytes  94.4 Mbits/sec
[  3] 49.0-50.0 sec  11.4 MBytes  95.4 Mbits/sec
[  3] 50.0-51.0 sec  11.2 MBytes  94.4 Mbits/sec
[  3] 51.0-52.0 sec  11.4 MBytes  95.4 Mbits/sec
[  3] 52.0-53.0 sec  11.2 MBytes  94.4 Mbits/sec
[  3] 53.0-54.0 sec  11.2 MBytes  94.4 Mbits/sec
[  3] 54.0-55.0 sec  11.2 MBytes  94.4 Mbits/sec
[  3] 55.0-56.0 sec  10.8 MBytes  90.2 Mbits/sec
[  3] 56.0-57.0 sec  11.2 MBytes  94.4 Mbits/sec
[  3] 57.0-58.0 sec  11.4 MBytes  95.4 Mbits/sec
[  3] 58.0-59.0 sec  11.2 MBytes  94.4 Mbits/sec
[  3] 59.0-60.0 sec  11.2 MBytes  94.4 Mbits/sec
[  3]  0.0-60.0 sec   675 MBytes  94.3 Mbits/sec

iperf from OS X (10.9.4) to Linux

[ ID] Interval       Transfer     Bandwidth
[  5]  0.0- 1.0 sec  11.5 MBytes  96.5 Mbits/sec
[  5]  1.0- 2.0 sec  11.1 MBytes  93.3 Mbits/sec
[  5]  2.0- 3.0 sec  11.1 MBytes  93.3 Mbits/sec
[  5]  3.0- 4.0 sec  11.1 MBytes  93.3 Mbits/sec
[  5]  4.0- 5.0 sec  11.1 MBytes  93.3 Mbits/sec
[  5]  5.0- 6.0 sec  11.2 MBytes  94.4 Mbits/sec
[  5]  6.0- 7.0 sec  11.1 MBytes  93.3 Mbits/sec
[  5]  7.0- 8.0 sec  11.1 MBytes  93.3 Mbits/sec
[  5]  8.0- 9.0 sec  11.1 MBytes  93.3 Mbits/sec
[  5]  9.0-10.0 sec  11.2 MBytes  94.4 Mbits/sec
[  5] 10.0-11.0 sec  11.1 MBytes  93.3 Mbits/sec
[  5] 11.0-12.0 sec  11.1 MBytes  93.3 Mbits/sec
[  5] 12.0-13.0 sec  11.1 MBytes  93.3 Mbits/sec
[  5] 13.0-14.0 sec  11.2 MBytes  94.4 Mbits/sec
[  5] 14.0-15.0 sec  11.1 MBytes  93.3 Mbits/sec
[  5] 15.0-16.0 sec  11.1 MBytes  93.3 Mbits/sec
[  5] 16.0-17.0 sec  11.2 MBytes  94.4 Mbits/sec
[  5] 17.0-18.0 sec  11.1 MBytes  93.3 Mbits/sec
[  5] 18.0-19.0 sec  11.1 MBytes  93.3 Mbits/sec
[  5] 19.0-20.0 sec  11.1 MBytes  93.3 Mbits/sec
[  5] 20.0-21.0 sec  11.2 MBytes  94.4 Mbits/sec
[  5] 21.0-22.0 sec  11.1 MBytes  93.3 Mbits/sec
[  5] 22.0-23.0 sec  11.1 MBytes  93.3 Mbits/sec
[  5] 23.0-24.0 sec  11.1 MBytes  93.3 Mbits/sec
[  5] 24.0-25.0 sec  11.2 MBytes  94.4 Mbits/sec
[  5] 25.0-26.0 sec  11.1 MBytes  93.3 Mbits/sec
[  5] 26.0-27.0 sec  11.1 MBytes  93.3 Mbits/sec
[  5] 27.0-28.0 sec  11.2 MBytes  94.4 Mbits/sec
[  5] 28.0-29.0 sec  11.1 MBytes  93.3 Mbits/sec
[  5] 29.0-30.0 sec  11.1 MBytes  93.3 Mbits/sec
[  5] 30.0-31.0 sec  11.1 MBytes  93.3 Mbits/sec
[  5] 31.0-32.0 sec  11.2 MBytes  94.4 Mbits/sec
[  5] 32.0-33.0 sec  11.1 MBytes  93.3 Mbits/sec
[  5] 33.0-34.0 sec  11.1 MBytes  93.3 Mbits/sec
[  5] 34.0-35.0 sec  11.2 MBytes  94.4 Mbits/sec
[  5] 35.0-36.0 sec  11.1 MBytes  93.3 Mbits/sec
[  5] 36.0-37.0 sec  11.1 MBytes  93.3 Mbits/sec
[  5] 37.0-38.0 sec  11.1 MBytes  93.3 Mbits/sec
[  5] 38.0-39.0 sec  11.2 MBytes  94.4 Mbits/sec
[  5] 39.0-40.0 sec  11.2 MBytes  94.4 Mbits/sec
[  5] 40.0-41.0 sec  11.1 MBytes  93.3 Mbits/sec
[  5] 41.0-42.0 sec  11.2 MBytes  94.4 Mbits/sec
[  5] 42.0-43.0 sec  11.2 MBytes  94.4 Mbits/sec
[  5] 43.0-44.0 sec  11.1 MBytes  93.3 Mbits/sec
[  5] 44.0-45.0 sec  11.2 MBytes  94.4 Mbits/sec
[  5] 45.0-46.0 sec  11.2 MBytes  94.4 Mbits/sec
[  5] 46.0-47.0 sec  11.1 MBytes  93.3 Mbits/sec
[  5] 47.0-48.0 sec  11.2 MBytes  94.4 Mbits/sec
[  5] 48.0-49.0 sec  11.2 MBytes  94.4 Mbits/sec
[  5] 49.0-50.0 sec  11.1 MBytes  93.3 Mbits/sec
[  5] 50.0-51.0 sec  11.2 MBytes  94.4 Mbits/sec
[  5] 51.0-52.0 sec  11.1 MBytes  93.3 Mbits/sec
[  5] 52.0-53.0 sec  11.2 MBytes  94.4 Mbits/sec
[  5] 53.0-54.0 sec  11.2 MBytes  94.4 Mbits/sec
[  5] 54.0-55.0 sec  11.1 MBytes  93.3 Mbits/sec
[  5] 55.0-56.0 sec  11.2 MBytes  94.4 Mbits/sec
[  5] 56.0-57.0 sec  11.2 MBytes  94.4 Mbits/sec
[  5] 57.0-58.0 sec  11.1 MBytes  93.3 Mbits/sec
[  5] 58.0-59.0 sec  11.2 MBytes  94.4 Mbits/sec
[  5] 59.0-60.0 sec  11.1 MBytes  93.3 Mbits/sec
[  5]  0.0-60.0 sec   671 MBytes  93.8 Mbits/sec

Same performance before and after sleep in both 10.9.4 and 10.10 dp2. Wake-On-Lan also works in both. I also noticed that Wake-On-Lan works only when connected to the power supply. This could be regular OS X behavior since there is no "Wake for network access" when on battery. Can someone confirm please.

 

Thank you for this great kext! 

post-506273-0-51139000-1405091794_thumb.png

post-506273-0-94713900-1405091803_thumb.png

post-506273-0-45027000-1405091823_thumb.png

post-506273-0-80454900-1405091831_thumb.png

post-506273-0-60295600-1405091868_thumb.png

post-506273-0-84646500-1405091926_thumb.png

post-506273-0-45000000-1405091937_thumb.png

Share this post


Link to post
Share on other sites

Hi Mieze,

 

thanks for your effort. My RTL8105E is running better with your kext 1.0 instead of AppleRTL8169Ethernet 2.0.6.

 

But when I use lan cable, system fan runs crazy and HWsensor report CPU temp > 70C. 

 

Using wifi is just fine.

 

Don't know if these relate to your kext. 

(also I have warning in console, kernel: apple80211Request Unsupported ioctl 181)

 

Just want to report that, do you have a clue? thanks!

 

-------------

Hereby the log from "grep -i realtek /var/log/system.log"

 

localhost kernel[0]: Ethernet [RealtekRTL8100]: Warning: PCIe ASPM enabled.

localhost kernel[0]: Ethernet [RealtekRTL8100]: EEE support enabled.

localhost kernel[0]: Ethernet [RealtekRTL8100]: TCP/IPv4 segmentation offload enabled.

localhost kernel[0]: Ethernet [RealtekRTL8100]: TCP/IPv6 checksum offload enabled.

localhost kernel[0]: Ethernet [RealtekRTL8100]: Using interrupt mitigate value 0x0.

localhost kernel[0]: Ethernet [RealtekRTL8100]: RTL8105E: (Chipset 12) at 0xffffff807aaa5000,  8:9e: 1:35:d5:5c

myMachine kernel[0]: Ethernet [RealtekRTL8100]: Link up on en0, 100-Megabit, Full-duplex, No flow-control

myMachine kernel[0]: Ethernet [RealtekRTL8100]: Link down on en0

Share this post


Link to post
Share on other sites

@Ravenstein: Have you used Activity Monitor in order to find out what is causing the high CPU load while you are connected via LAN?

 

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 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 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.
    • By grisno
      Hi people,
       
      Installer to activate the sound card REALTEK ALC282-v2 (10ec:0282) with LayoutID 1 or 3 in MacOS. This installer does not contain AppleHDA patched Kext. To work properly, it must be installed over vanilla AppleHDA.kext.
       
      I want to thank the whole community for their efforts and content provided, because without these it would not be possible to create this installer.
       
      I would appreciate comments and suggestions!!
       
      Status:
      Speakers : OK Headphones : OK HDMI Audio : OK (Intel HD4K Tested) LineIn : N/A (Model Without LineIn) MicInt : OK MicIntNoiseReduction : OK MicExt : N/A (Model Without MicExt) AutoDetectLineIn : N/A (Model Without LineIn) Sleep : OK WakeUp : OK AutoSleep : OK Hibernate : OK Siri : OK   Tested Laptops:
       
      - HP Pavillion 15-D002SS
       
      Coming Soon:
       
      - Unified installer for the different supported operating systems.
      - Support model with LineIn jack.
       
      Modified Verbs:
      01271C20 01271D00 01271EA0 01271F90 01471C10 01471D00 01471E17 01471F90 01871CF0 01871D00 01871E00 01871F40 01E71CF0 01E71D00 01E71E00 01E71F40 02171C30 02171D10 02171E21 02171F00 01470C02   DSDT:
       
      Patch to apply with MaciASL in your DSDT
      ######################################### HDEF v1.00######################################## into method label _DSM parent_label HDEF remove_entry;into device label HDEF insertbeginMethod (_DSM, 4, NotSerialized)\n{\n If (LEqual (Arg2, Zero)) { Return (Buffer() { 0x03 } ) }\n Return (Package()\n {\n "layout-id", Buffer() { 0x01, 0x00, 0x00, 0x00 },\n //"layout-id", Buffer() { 0x03, 0x00, 0x00, 0x00 },\n "hda-gfx", Buffer() { "onboard-1" },\n "PinConfigurations", Buffer() { },\n })\n}\nend;  
×