Jump to content
Mieze

Driver for Realtek's RTL810x Fast Ethernet Series

178 posts in this topic

Recommended Posts

open a terminal window and type :

 

sudo touch /System/Library/Extensions

 

or

 

sudo kextcache -prelinked-kernel

 

then reboot

for both step 2 and step 4?? if so thanks

Share this post


Link to post
Share on other sites
Advertisement

sudo touch /System/Library/Extensions & sudo kextcache -prelinked-kernel do the same thing.

 

The first one is fast and simple, the second one is a little bit longer but you'll see onscreen what's happening.

 

You can do both one after the other if you want to see the difference but it's useless ;) and the result will be the same : it rebuilds kernel cache.

Note that it does NOT repair permissions !

 

Choose one of them then reboot

Share this post


Link to post
Share on other sites

sudo touch /System/Library/Extensions & sudo kextcache -prelinked-kernel do the same thing.

 

The first one is fast and simple, the second one is a little bit longer but you'll see onscreen what's happening.

 

You can do both one after the other if you want to see the difference but it's useless ;) and the result will be the same : it rebuilds kernel cache.

Note that it does NOT repair permissions !

 

Choose one of them then reboot

thanks again :)

Share this post


Link to post
Share on other sites

Mieze..Thanks for your outstanding contribution here. With the help of RehabMan directing my query to this post, I now have full ethernet functionality on my Lenovo U310, even after sleep. Smiles and chuckles after weeks of struggles. Thank you.  ssprod

Share this post


Link to post
Share on other sites

Mieze..Thanks charmed works for my 

(from lilnux )

01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8101E/RTL8102E PCI Express Fast Ethernet controller (rev 07)

    Subsystem: Realtek Semiconductor Co., Ltd. Device 0123
    Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
    Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
    Latency: 0, Cache Line Size: 64 bytes
    Interrupt: pin A routed to IRQ 43
    Region 0: I/O ports at 3000
    Region 2: Memory at b0600000 (64-bit, non-prefetchable)
    Region 4: Memory at b0400000 (64-bit, prefetchable)
    Capabilities: <access denied>
    Kernel driver in use: r8169

Share this post


Link to post
Share on other sites

Thank you for this wonderful contribution Mieze. I have just compiled and installed it on Mavericks. It has been working like a charm. :)

Finally, I no longer have to manually configure speed, duplex and MTU.

Share this post


Link to post
Share on other sites

please help ..idk why i'm the only one in this world still can't make my ethernet card works at all...

check out my screen shot...

 

also idk what to delete before i setup it and i use Kext Wizard tool to install it

 

please help me

post-1496184-0-22112400-1425075599_thumb.png

Share this post


Link to post
Share on other sites

What's your bootloader ?

Where is installed the kext ?

Check you don't have duplicate kexts in different places (ie. in S/L/E and E/E or EFI/Clover/kexts/10.10)

 

To make sure the kext is correctly loaded, move it in S/L/E and delete all others instances in your setup. Make sure you use kext-dev-mode=1 boot-flag, rebuild kernelcache and reboot.

Share this post


Link to post
Share on other sites

my bootloader is Clover Configurator as it shows at the 1st picture

and i setup the .kext file by Kext Wizard as it at the 2nd picture

and i only delete the file which at S/ L/ E/ selected and reinstall it as it shown at the 3rd picture ...idk if there is anything else i should delete or not

and i do repair permissions and Rebuild cache after i finish seting up the driver....or i have to do this before i setup it?

 

sry if i'm talking too much because that's my 1st time ever with Mac system so idk ALOT about how to configure it.

post-1496184-0-73024100-1425114588_thumb.png

post-1496184-0-22083800-1425114679_thumb.png

post-1496184-0-23158600-1425114776_thumb.png

post-1496184-0-05997200-1425114864_thumb.png

Share this post


Link to post
Share on other sites

Hi Mieze

The driver works and no sign of interruption. But i have something in my log:

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]: RTL8105E: (Chipset 11) at 0x35a62000, 44:8a:7d:b8:86:2a
RTL8100: Ethernet address 44:8a:7d:b8:86:2a
Ethernet [RealtekRTL8100]: Link up on en0, 100-Megabit, Full-duplex, No flow-control
Ethernet [RealtekRTL8100]: Tx timeout. Lost interrupt?
Ethernet [RealtekRTL8100]: Tx timeout. Lost interrupt?
Ethernet [RealtekRTL8100]: Tx timeout. Lost interrupt?
Ethernet [RealtekRTL8100]: Tx timeout. Lost interrupt?
Ethernet [RealtekRTL8100]: Tx timeout. Lost interrupt?
Ethernet [RealtekRTL8100]: Tx timeout. Lost interrupt?
Ethernet [RealtekRTL8100]: Tx timeout. Lost interrupt?
Ethernet [RealtekRTL8100]: Tx timeout. Lost interrupt?
Ethernet [RealtekRTL8100]: Tx timeout. Lost interrupt?
Ethernet [RealtekRTL8100]: Tx timeout. Lost interrupt?
Ethernet [RealtekRTL8100]: Tx timeout. Lost interrupt?
Ethernet [RealtekRTL8100]: Tx timeout. Lost interrupt?
Ethernet [RealtekRTL8100]: Tx timeout. Lost interrupt?
Ethernet [RealtekRTL8100]: Tx timeout. Lost interrupt?
Ethernet [RealtekRTL8100]: Tx timeout. Lost interrupt?
Ethernet [RealtekRTL8100]: Tx timeout. Lost interrupt?
Ethernet [RealtekRTL8100]: Tx timeout. Lost interrupt?
Ethernet [RealtekRTL8100]: Tx timeout. Lost interrupt?
Ethernet [RealtekRTL8100]: Tx timeout. Lost interrupt?
Ethernet [RealtekRTL8100]: Tx timeout. Lost interrupt?
Ethernet [RealtekRTL8100]: Tx timeout. Lost interrupt?
Ethernet [RealtekRTL8100]: Tx timeout. Lost interrupt?
Ethernet [RealtekRTL8100]: Tx timeout. Lost interrupt?
Ethernet [RealtekRTL8100]: Tx timeout. Lost interrupt?
Ethernet [RealtekRTL8100]: Tx timeout. Lost interrupt?
Ethernet [RealtekRTL8100]: Tx timeout. Lost interrupt?
Ethernet [RealtekRTL8100]: Tx timeout. Lost interrupt?
Ethernet [RealtekRTL8100]: Tx timeout. Lost interrupt?

Any idea?

Share this post


Link to post
Share on other sites

Any idea?

 

There is no need for further explanations because the log messages are self explanatory. These are lost interrupts, nothing less and nothing more.

 

Mieze

Share this post


Link to post
Share on other sites

Mieze,

 

Could you please update this driver to the new driver interface?

 

Thanks in advance :)

Share this post


Link to post
Share on other sites

Mieze,

 

Could you please update this driver to the new driver interface?

 

Thanks in advance :)

 

Sure, but I need a volunteer who is able to build from source in order to run some tests because I don't have any appropriate hardware to test the driver myself.

 

Mieze

Share this post


Link to post
Share on other sites

Sure, but I need a volunteer who is able to build from source in order to run some tests because I don't have any appropriate hardware to test the driver myself.

 

Mieze

 

I could help with testing but not building  :blush:

 

Thanks

Share this post


Link to post
Share on other sites

@Mieze Just curious, I was reading this code and noticed this:

 

https://github.com/Mieze/RealtekRTL8100/blob/master/RealtekRTL8100/RealtekRTL8100.cpp#L2621

 

data32 is not used after this point. Should there be:

mdio_write(tp, 0x10, data32);

After that line?

Please ask the Realtek developers because I took these lines from their linux driver and due to the lack of documentation I have no idea what it does.

 

Mieze

Share this post


Link to post
Share on other sites

Ok. Would you mind telling me which version linux you took this code from? That way I can cross-reference the changes that have been made.

Share this post


Link to post
Share on other sites

Ok. Would you mind telling me which version linux you took this code from? That way I can cross-reference the changes that have been made.

Take a look at the Linux source files inside the project. At the top of these files you'll find the answer on the header.

 

Mieze

Share this post


Link to post
Share on other sites

Not working on my laptop. HP Pavilion 15-ab205ns Skylake (Device id: 10ec:8136). Ethernet detected in system preferences. It gets ip, submask, router and dns correctly, but no internet.

Tried manual configuration, same result.

Share this post


Link to post
Share on other sites

Not working on my laptop. HP Pavilion 15-ab205ns Skylake (Device id: 10ec:8136). Ethernet detected in system preferences. It gets ip, submask, router and dns correctly, but no internet.

Tried manual configuration, same result.

If the interface successfully manages to acquire an IP address via DHCP the driver is working properly. In case you still haven't internet access, search somewhere else but a driver issue can be ruled out almost certainly.

 

Mieze

Share this post


Link to post
Share on other sites

Good afternoon, Mieze... Thanks for your answer...

This is the log when is detected by your kext...

 

May 31 20:47:43 iMac com.apple.kextd[43]: kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext "/System/Library/Extensions/RealtekRTL8100.kext"
May 31 20:47:43 iMac com.apple.kextd[43]: kext signature failure override allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext "/System/Library/Extensions/RealtekRTL8100.kext"
May 31 20:47:43 iMac kernel[0]: Ethernet [RealtekRTL8100]: Warning: PCIe ASPM enabled.
May 31 20:47:43 iMac kernel[0]: Ethernet [RealtekRTL8100]: EEE support enabled.
May 31 20:47:43 iMac kernel[0]: Ethernet [RealtekRTL8100]: TCP/IPv4 segmentation offload enabled.
May 31 20:47:43 iMac kernel[0]: Ethernet [RealtekRTL8100]: TCP/IPv6 checksum offload enabled.
May 31 20:47:43 iMac kernel[0]: Ethernet [RealtekRTL8100]: Using interrupt mitigate value 0x0.
May 31 20:47:43 iMac kernel[0]: Ethernet [RealtekRTL8100]: RTL8101E: (Chipset 0) at 0x<ptr>, 70:5a: f:19:94:5c
May 31 20:48:16 iMac kernel[0]: Ethernet [RealtekRTL8100]: Link up on en0, 100-Megabit, Full-duplex, flow-control

 

It's correct? Or something fails?
 

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.

Announcements

  • Similar Content

    • By Mieze
      This project is dedicated to Lucy, my lovely little Tyrannofelis Rex. 
       

       
      LucyRTL8125Ethernet is an open source driver for the Realtek RTL8125 family of 2.5GBit Ethernet controllers.
       
      Key Features of the Driver
      Supports all versions of Realtek's RTL8125 2.5GBit Ethernet Controllers 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 over IPv4 and IPv6. Support for TCP/IPv4, UDP/IPv4, TCP/IPv6 and UDP/IPv6 checksum offload. Supports jumbo frames up to 9000 bytes (strongly recommended for 2.5GBit operation). Fully optimized for Catalina (doesn't work with Mojave and below). Note that older versions of macOS might not support 2.5GB Ethernet. Supports Wake on LAN (untested). Supports VLAN (untested). 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.  
      Current Status
      The driver has been tested successfully under Catalina (10.15.4 and above) and, according to first tests, is working stable. I haven't experienced any Kernel Panics during my tests and is working stable on my primary work machine. The driver has been designed to work with Catalina but might also work with Mojave, provided you build from source with Xcode 10.. Please keep in mind that support for 2.5GBit Ethernet was introduced in Mojave (or maybe High Sierra?) so that there is no way to make it work with Sierra or below.  
      Known Issues
      Using autoselect medium it seems to prefer negotiating a connection speed of 1Gbit with my switch so that I had to select 2.5GBit/s manually in order to achieve this speed but it might be different with other switches.   Installation
      You might want to install the driver to /L/E as usual but it's also ok to use Clover's injection function (installation in the EFI folder). Use your favorite kext installation tool for installation or perform the installation manually (for Clover injection). It's your call!  
      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 "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.  Delete the following files: /Library/Preferences/SystemConfiguration/NetworkInterfaces.plist /Library/Preferences/SystemConfiguration/preferences.plist 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 1.0.0d6 (2020-06-14) Fixed chip recognition. Version 1.0.0d3 (2020-04-20) First working development release.  
      Getting the driver
      Source code can be found on GitHub: https://github.com/Mieze/LucyRTL8125Ethernet You'll find the lastest prebuilt binary here in this thread (see below).  
       
    • By Yosa Tristian
      Can someone help me?
      When I turn on the USB Wireless Adapter (Wifi Dongle), my mouse is lagging (like quick ejecting & rejecting).
      When I turn off the Wifi Dongle, my mouse runs smooth again.
       
      Mouse: Fantech G13 Rhasta II
      Wifi Dongle: TPLink TL-WN725N
      Wifi Dongle Driver : https://github.com/chris1111/Wireless-USB-Adapter
       
      And if you don't mind, can you check my hackintosh configuration? maybe something isn't right yet
      Send me Yosas-MacBook-Pro.zip
    • By Mieze
      Key Features of the Driver
      Supports Qualcomm Atheros AR816x, AR817x, Killer E220x, Killer E2400 and Killer E2500. 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. Fully optimized for Mountain Lion, Mavericks and Yosemite (64bit architecture) but should work with Lion (only 64bit) too, provided you build from source with the 10.7 SDK. Wake on LAN support. VLAN support used to be broken in older versions but is working since version 2.3.2. The driver is published under GPLv2.
    • 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 400 Series (since V2.5.1d1)
      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, I219V 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.5.0 (2019-10-15) Reworked interrupt throttling code and added new configuration parameters. 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.
×