Jump to content
About Just Joined group Read more... ×
Mieze

New Driver for Realtek RTL8111

1,517 posts in this topic

Recommended Posts

Advertisement

I've installed it in my hack (RTL8111E) and it loaded fine and detected the disconnected cable (I'm not using the LAN right now, just wifi). Recently I've been testing Slice's new kext but had some issues with the latest version so I'll try yours a couple of days and report here.

 

kernel[0]: Ethernet [RealtekRTL8111]: EEE support enabled
kernel[0]: Ethernet [RealtekRTL8111]: RTL8168E-VL/8111E-VL: (Chipset 16) at 0xffffff80f08e5000, xx:xx:xx:xx:xx:xx
kernel[0]: RTL8111: Ethernet address xx:xx:xx:xx:xx:xx

Share this post


Link to post
Share on other sites

Is it possible to add support for the 8105E? Could you include it in your driver?

Unfortunately it isn't because there is no documentation for the Realtek gigabit NICs publicly available so that I had to take the hardware initialization routines from their linux driver and this driver doesn't support the 8105E.

 

Mieze

Share this post


Link to post
Share on other sites

Thanks, Mieze, for the answer!

 

In fact, there is a Linux driver that includes support for the 8105, and Slice even included it in the sources for his driver. I even tried to do something with it, since i'm familiar to C programming, but i lack the necessary knowledge of how to port it to OSX, so i got stuck.

 

All the best!

 

P.S.: the 8105, btw, isn't exactly gigabit ethernet: it's a 10/100 mbs card which usually comes bundled with some cheaper motherboards.

Share this post


Link to post
Share on other sites

In fact, there is a Linux driver that includes support for the 8105, and Slice even included it in the sources for his driver. I even tried to do something with it, since i'm familiar to C programming, but i lack the necessary knowledge of how to port it to OSX, so i got stuck.

My driver has a clear cut separation between the OS X code and the linux code. There are only a few interconnections, mainly when the driver calls hardware initialization routines. Assuming that Realtek's linux driver for their Fast Ethernet NICs has a similar architecture it shouldn't be a big deal for you to take my OS X code as a starting point for your development. You would only have to rewrite the hardware dependent parts, like the outputPacket() function and the interrupt handling routines. Maybe you'll also find a leaked datasheet of the 8105E at www.realtek.cz helping you to implement the transmit and receive routines.

 

Mieze

Share this post


Link to post
Share on other sites

Hey Mieze!

 

Just checking in on the thread with a post so I can receive email updates. :wink2:

 

Keep up the great as always!

 

Mrengles (Robert)

Share this post


Link to post
Share on other sites

i would like to take part to this driver development and i think many users want.

As a proposal: could you please put you driver source code on GITHUB or other online versioning portal to be able to track changes between version more easily

Share this post


Link to post
Share on other sites

i would like to take part to this driver development and i think many users want.

As a proposal: could you please put you driver source code on GITHUB or other online versioning portal to be able to track changes between version more easily

I already thought about that but at the moment I'm very busy with an iOS project so that there is not much time left for the driver. But this is not a high priority because the project folder contains a git repository that you can use to track changes.

 

Mieze

Share this post


Link to post
Share on other sites

I already thought about that but at the moment I'm very busy with an iOS project so that there is not much time left for the driver. But this is not a high priority because the project folder contains a git repository that you can use to track changes.

 

I'd also like to get involved, having a central repro would be most helpful. That said, what needs to be done still for the 8111F chipset?

Share this post


Link to post
Share on other sites

I'd also like to get involved, having a central repro would be most helpful. That said, what needs to be done still for the 8111F chipset?

As far as I know nothing. Only the 8111B still has a long way to go.

 

Mieze

Share this post


Link to post
Share on other sites

Finally I can use WOL !!

My system have RTL8111E (GA X58A-UD3R motherboard) chip, it works perfectly now.

First time when I try this kext follow your guide in post #1.

It shows connected in system profiler and System Preference, but when I try to use internet it's not connect to internet.

One of my friend informed me to shutdown the system instead of restart after install this kext.

I shutdown system couple minutes after install new kext and boot again, now it works perfectly.

New kext makes my system use WOL. I couldn't use WOL when I use old kext.

Thanks, Mieze !!

Share this post


Link to post
Share on other sites

I own a EP45-extreme (two 8111C) , my question is , if i boot chameleon with kernel patcher plugin (to use /E/E) , does the network work with the driver placed in the Extra/Extensions ? the lynx2mac does not work , only if i place it in the S/L/E folder.

Share this post


Link to post
Share on other sites

I own a EP45-extreme (two 8111C) , my question is , if i boot chameleon with kernel patcher plugin (to use /E/E) , does the network work with the driver placed in the Extra/Extensions ? the lynx2mac does not work , only if i place it in the S/L/E folder.

This could be a problem with the kernel cache, because /Extra/Extensions is usually not taken into account when the kernel cache is recreated by Apple provided tools. Better install it in /S/L/E to avoid trouble!

 

Mieze

 

One of my friend informed me to shutdown the system instead of restart after install this kext.

I shutdown system couple minutes after install new kext and boot again, now it works perfectly.

Thanks for posting this. I just added the information to the troubleshooting section.

 

Mieze

Share this post


Link to post
Share on other sites

Would it be possible to add support for RTL8188XX (e.g RTL8188CE)?

No, because these are wireless NICs. They are completely different.

 

Mieze

Share this post


Link to post
Share on other sites

I've installed your driver to both hacks to see how it goes. Had problem installing it at first: driver was loaded and connected to device, but net was not working, said that cable is not connected. Somehow got resolved by few shutdowns/restarts/reinstalls/deleting and adding ethernet - not sure what helped. But works very nice now.

 

Thank you for your work!

Share this post


Link to post
Share on other sites

This could be a problem with the kernel cache, because /Extra/Extensions is usually not taken into account when the kernel cache is recreated by Apple provided tools. Better install it in /S/L/E to avoid trouble!

 

Mieze

 

 

Thanks for posting this. I just added the information to the troubleshooting section.

 

Mieze

 

On my installer USB, i have the kexts in /extra , with the kernel patcher module.

My problem is that on the first boot, osx uses the audio kext, fakesmc, sata (all inside /extra) only realtek kexts does not load, only after i copy it to s/l/e. My wish was to have the internet on first boot, to configure osx from the initial wizard.

 

I've tried your driver, the download is perfect, but i have around 20kb/s upload if i try to put a file on a server or on my network, something is wrong with the upload.

Share this post


Link to post
Share on other sites

On my installer USB, i have the kexts in /extra , with the kernel patcher module.

My problem is that on the first boot, osx uses the audio kext, fakesmc, sata (all inside /extra) only realtek kexts does not load, only after i copy it to s/l/e. My wish was to have the internet on first boot, to configure osx from the initial wizard.

To copy the driver anywhere is not enough. You'll have to repair it's permissions or it will never be used.

I've tried your driver, the download is perfect, but i have around 20kb/s upload if i try to put a file on a server or on my network, something is wrong with the upload.

Please follow the instructions in the troubleshooting section. If the problem persists report back with debug data from /var/log/system.log (all driver related messages), netstat -s output and your OS X version, CPU and mainboard.

 

Mieze

Share this post


Link to post
Share on other sites

Thanks for your work. I have replaced the Lnx2 Realtek driver i have been using with yours. I have had rare problems with the Lnx2 driver where out of the blue the whole network was just gone. The transition went smooth (just followed your instructions). Using a 8111F on a P8H77-I. Will see how it performs long term! So far - all looking good.

Thanks! :)

Share this post


Link to post
Share on other sites

  • 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 Mojave and above. 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!  
      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 "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.0 (2020-08-14) Changed version number to make this the first official release. 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 in the download section: https://www.insanelymac.com/forum/files/file/1004-lucyrtl8125ethernet/  
       
    • By Mieze
      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 Mojave and above. 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.
    • 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.
×