Jump to content
Mieze

New Driver for Realtek RTL8111

1,386 posts in this topic

Recommended Posts

Posted (edited)

@toperloid According to the logs the driver is working fine but it fails to pick up the MAC address. This is the reason why it doesn't work as expected on your machine because DHCP fails to acquire an IP address due to the broken MAC address. I'll try to find a solution for it and will publish a new test build ASAP.

 

EDIT: What happens if you enable the UEFI network stack in BIOS?

 

Mieze

Edited by Mieze

Share this post


Link to post
Share on other sites
Advertisement
On 4/9/2019 at 5:05 PM, macky1 said:

Thank you for your suggestion will try it out. I've got a feeling it is the network stack and thus possibly Mojave bug.

So far in testing of beta RealtekRTL8111-V2.3.0d5 it works good. Whatever the issue was with the driver v2.2.2 using RTL8111H on Mojave it has disappeared in this version. Internet starts up every time now.

Thanks Mieze for the updated driver.

On 8/5/2019 at 7:52 PM, Roran90 said:

I have the same issue, how did you solve the issue? I tried a clear cmos, I changed the cable but still have the problem and it is very annoying 

Try beta version RealtekRTL8111-V2.3.0d5 and see how it goes. So far for me it works good.

Share this post


Link to post
Share on other sites
Posted (edited)

@Mieze sorry for late reply. My BIOS does not have that option, unfortunately. 

 

My device is this using coreboot (mrchromebox) bios running in High Sierra if that info helps

Edited by toperloid

Share this post


Link to post
Share on other sites
3 hours ago, toperloid said:

@Mieze sorry for late reply. My BIOS does not have that option, unfortunately. 

 

My device is this using coreboot (mrchromebox) bios running in High Sierra if that info helps

No problem! I'm currently investigating possible solutions to resolve situations when retrieving the MAC address fails. Either way I could use a random MAC address or add an option to supply a fallback address and I'm not quite sure which way to go because both methods have drawbacks.

Share this post


Link to post
Share on other sites
2 minutes ago, Mieze said:

No problem! I'm currently investigating possible solutions to resolve situations when retrieving the MAC address fails. Either way I could use a random MAC address or add an option to supply a fallback address and I'm not quite sure which way to go because both methods have drawbacks.

What would be the drawback of manually supplying one? it requires more user work, but seems the solid route. a random one could change and that could cause all sorts of havoc (software license tied to MAC for instance). This issue is probably rare to begin with, I think a plist edit is a good solution for a fallback address. just make sure its disabled by default so it requires user interaction (adding a valid address and enabling the fallback).

g\

Share this post


Link to post
Share on other sites
4 hours ago, genzai said:

What would be the drawback of manually supplying one? it requires more user work, but seems the solid route. a random one could change and that could cause all sorts of havoc (software license tied to MAC for instance). This issue is probably rare to begin with, I think a plist edit is a good solution for a fallback address. just make sure its disabled by default so it requires user interaction (adding a valid address and enabling the fallback).

Problems arise when the fallback isn't properly configured, e.g. when multiple machines are using he same MAC address or there is no valid fallback address supplied. On the other hand using a random address also might cause trouble as it will change on each and every boot. I'm still not sure what to do but will have to make a decision tomorrow.

 

Mieze :cat:

Share this post


Link to post
Share on other sites
Posted (edited)

@toperloid This one is especially for you but all users are encouraged to test it! 

 

Here is version 2.3.0d7 in which I added an option to supply a fallback MAC being used in situations when retrieving a valid MAC address fails.

 

In the driver's Info.plist I added the option "fallbackMAC" to "Driver Parameters". "fallbackMAC" is a string which may be used to supply your original MAC address. It is used only if retrieving a valid MAC address fails. In the default configuration, the string is empty. In case you need it, please fill in your MAC with the following syntax "xx:xx:xx:xx:xx:xx" in which every x represents exactly one hexadecimal digit.

 

Warning: This is not an option for MAC address customization and I won't add such an option because it would be stupid to do so. Use with care because MAC addresses have to be unique. Using another machine's MAC address may produce unexpected results!

 

PS: Could anybody be so nice to test test WoL with this built because it doesn't work on my test machine and I have reasons to beliefe that it's not the driver's responsibility.

 

RealtekRTL8111-V2.3.0d7.kext.zip

Edited by Mieze

Share this post


Link to post
Share on other sites

@Mieze Thank you. I won't be able to test this until tomorrow when I get home.

I managed to get the actual MAC address from an Ubuntu live boot the previous day and will be using it to test. 

Share this post


Link to post
Share on other sites

@Mieze It works! I'm able to test the connection using Speedtest. It works perfectly. 

Many thanks to you :)

 

Here's the log showing that it was able to use the MAC address that I've supplemented.

 

 

KL.txt

Network Utility.png

Share this post


Link to post
Share on other sites

Driver works perfectly on my signature rig. WoL works...but not reliably. It seems to loop back on its own. From 3 tests, the first one was ok, the following two, bounced back almost immediately after going to sleep.

 

I'll test a bit more and update if anything interesting comes up.

 

WoL from shutdown works with no hiccups (so far).

 

Update:

 

Batch test nr 2 from sleep:


[Attempt nr. | result]

01 | ok
02 | nok 
03 | ok
04 | nok
05 | ok
06 | nok
07 | ok
08 | nok
09 | ok
10 | nok

 

Ok = went to sleep ok, woke up by network trigger
Nok = sleep not ok, woke up on its own

First attempt made after a complete shutdown and reboot (just to have clear results).

 

Batch test nr 2 from shutdown:

 

[Attempt nr. | result]

01 | ok
02 | ok
03 | ok
04 | ok
05 | ok
06 | ok
07 | ok
08 | ok
09 | ok
10 | ok

 

Ok = shutdown ok, rebooted by network trigger

 

 

Edited by arsradu

Share this post


Link to post
Share on other sites

Thanks for Great Work ...

Realtek 8118 Gaming LAN Bandwidth Control Error is Gone !!!

B360M-D3V Board with Realtek 8118 Gaming LAN "work Perfect  Now !!!"

Thanks Again !!!

 

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.
×