Jump to content
Mieze

New Driver for Realtek RTL8111

1,430 posts in this topic

Recommended Posts

Advertisement

I really have nothing to add to the discussion except to say thank you so much for this driver.  I installed v1.2.2 after having (different) issues with both the realtek and lnx2mac versions.  So far yours seems the most superior in terms of speed, compatibility and stability.   An (initial) 400gb time machine backup occurs substantially faster and more reliably now than it did before.  Thanks Mieze!

Share this post


Link to post
Share on other sites

Mieze

hello! How about changing the Kernel socket buffer size to kick off my problems with system freezing in an hour after starting torrent clients with thousands of torrents?

post-609887-0-22878600-1410256414_thumb.png

Share this post


Link to post
Share on other sites

Mieze

I'm using your kext (RTL8111- V1.2.3-dev2 installed in system/library/extensions/ionetworkingfamily.kext/contents/plugins/

works to perfection but leaving the stop sometimes I get this screen, I'm using chameleon-2.2svn-r2395 last fakesmc vers. 6.9.315 by netkas 

also use ethernetbuiltin = yes in o.c.B.p. 
after several openings-closings safari everything works
*yosemite build DP8 + dsdt untouched + hd 3000 patch + hdef alc887 + applehda (bios 4003 modified rom http://biosrepo.wordpress.com/asus/z68/ )
 
*thanks for any response* 

post-332936-0-47991900-1411392744_thumb.png

Share this post


Link to post
Share on other sites

@copil: Take a look at the kernel logs because it is essential to find out what is wrong. Looks like the connection is unstable sometimes. Try to select the connection speed manually or try to disable EEE.

 

Mieze

Share this post


Link to post
Share on other sites

@copil: I described how to retrieve kernel logs sereral times in this thread. Please use the search function. Same with disabling EEE.

 

Mieze

Share this post


Link to post
Share on other sites

Mieze 

pardon 
now i read back in the thread
really helpful
 
 
in therminal i have this (attached)
 
grep kernel /var/log/system.log 
 
in the kext realtekrtl8111.kextcontents/info.plist i have this 
 
i put on false
*from now in test*

Terminal Saved Output.zip

post-332936-0-00430600-1411397847_thumb.png

Share this post


Link to post
Share on other sites

Mieze, you are amazing. When I first built this hack a couple years ago, I installed a PCI-E ethernet card because the only available kext for RTL8111 at the time was incredibly slow. I just tried your kext and the ping, download, and upload speeds are the same as my Marvell ethernet card. Guess I have a free PCI-E slot now!

Share this post


Link to post
Share on other sites

Just wanted to thank you Mieze for the great kext! The latest Dev-Drivers are running completely stable here!

:wub:

Share this post


Link to post
Share on other sites

I updated the prebuilt binary to 1.2.3 which is identical to 1.2.3-dev2 and pushed the source to GitHub. Please note that the prebuilt binary no longer includes a version for Lion. In case you want to install it on 10.7.x, please build from source with Xcode 4.6.3 using the 10.7 SDK as the Base SDK.

 

Mieze  :cat:

Share this post


Link to post
Share on other sites

Thank you for the driver!

 

Installed 1.2.3 after the driver I was using (that is at version 0.0.2) bombed out on me again (couldn't stay working, required that I cold boot the machine to get connectivity up again), and so far it's passed the 24 hour time machine backup test, and seems to recover from sleep correctly as well.

 

Please, keep on mataining and improving this one!

Share this post


Link to post
Share on other sites

Dear Mieze,

 

I tested the  last dev version of the kext, and it is working with the 10.10.

 

Thank you again,

 

Dioclecio

Share this post


Link to post
Share on other sites

Dear Mieze,

 

Hi! I meet a strange problem.Two OS was installed on my PC(Windows 8 and Yosemite).1.2.3 works fine on Yosemite,but every time i restart from Windows 8,my LAN is lost.I have to replug the power.Here is my log:

14/10/29 上午5:14:29.000 kernel[0]: Ethernet [RealtekRTL8111]: PCIe ASPM support disabled.
14/10/29 上午5:14:29.000 kernel[0]: Ethernet [RealtekRTL8111]: PCI power management capabilities: 0xffc3.
14/10/29 上午5:14:29.000 kernel[0]: Ethernet [RealtekRTL8111]: PME# from D3 (cold) supported.
14/10/29 上午5:14:29.000 kernel[0]: Ethernet [RealtekRTL8111]: PCIe link capabilities: 0x00477c11, link control: 0x0140.
14/10/29 上午5:14:29.000 kernel[0]: Ethernet [RealtekRTL8111]: Disable PCIe ASPM.
14/10/29 上午5:14:29.000 kernel[0]: Ethernet [RealtekRTL8111]: EEE support enabled.
14/10/29 上午5:14:29.000 kernel[0]: Ethernet [RealtekRTL8111]: TCP/IPv4 segmentation offload enabled.
14/10/29 上午5:14:29.000 kernel[0]: Ethernet [RealtekRTL8111]: TCP/IPv6 segmentation offload enabled.
14/10/29 上午5:14:29.000 kernel[0]: Ethernet [RealtekRTL8111]: TCP/IPv6 checksum offload enabled.
14/10/29 上午5:14:29.000 kernel[0]: Ethernet [RealtekRTL8111]: Version 1.2.3 using interrupt mitigate value 0xcf58.
14/10/29 上午5:14:29.000 kernel[0]: Ethernet [RealtekRTL8111]: RTL8168G/8111G: (Chipset 20) at 0xffffff8106f8a000, 54:a0:50:57:70:15
14/10/29 上午5:14:29.000 kernel[0]: Ethernet [RealtekRTL8111]: Device is WoL capable.
14/10/29 上午5:14:29.000 kernel[0]: Ethernet [RealtekRTL8111]: MSI interrupt index: 1
14/10/29 上午5:14:29.000 kernel[0]: Ethernet [RealtekRTL8111]: kIOEthernetWakeOnMagicPacket added to filters.
14/10/29 上午5:14:29.000 kernel[0]: Ethernet [RealtekRTL8111]: Already in power state 1.
14/10/28 下午9:14:30.000 kernel[0]: Ethernet [RealtekRTL8111]: No medium selected. Falling back to autonegotiation.

After I replug , one more line appears:

14/10/28 下午9:16:45.000 kernel[0]: Ethernet [RealtekRTL8111]: Link up on en0, 1-Gigabit, Full-duplex, flow-control

Sorry for my bad English, but I truly need your help.Thank you!

Share this post


Link to post
Share on other sites

Dear Mieze,

 

Hi! I meet a strange problem.Two OS was installed on my PC(Windows 8 and Yosemite).1.2.3 works fine on Yosemite,but every time i restart from Windows 8,my LAN is lost.I have to replug the power.

 

As dual booting with Win 8 is not an unusual configuration and you are the only user to report this issue, I assume that it is a bug that is caused by the configuration of the Win 8 driver or the BIOS so that it has to be resolved on the Windows side. Sorry, but there is nothing I can do for you.

 

Mieze

Share this post


Link to post
Share on other sites

As dual booting with Win 8 is not an unusual configuration and you are the only user to report this issue, I assume that it is a bug that is caused by the configuration of the Win 8 driver or the BIOS so that it has to be resolved on the Windows side. Sorry, but there is nothing I can do for you.

 

Mieze

I have the same problem as him: whenever I reboot or power off/on the system from yosemite to windows xp, the LAN is gone. I have to unplug cable of power supply. Not sure the problem comes from the LAN kext or other. I'm new in osx86, so i'm still searching the bug and fix.

Share this post


Link to post
Share on other sites

As dual booting with Win 8 is not an unusual configuration and you are the only user to report this issue, I assume that it is a bug that is caused by the configuration of the Win 8 driver or the BIOS so that it has to be resolved on the Windows side. Sorry, but there is nothing I can do for you.

 

Mieze

I have found that it is the windows 8 driver that caused it.Your driver is working stable and efficient on OS X.

 

Thank you very much for your patience!

I have the same problem as him: whenever I reboot or power off/on the system from yosemite to windows xp, the LAN is gone. I have to unplug cable of power supply. Not sure the problem comes from the LAN kext or other. I'm new in osx86, so i'm still searching the bug and fix.

You can try reinstalling a new driver on Windows.

Share this post


Link to post
Share on other sites

I have found that it is the windows 8 driver that caused it.Your driver is working stable and efficient on OS X.

 

Thank you very much for your patience!

 

You can try reinstalling a new driver on Windows.

Asus hasn't updated the xp driver from 2006 :(. Any other solution?

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 ITzTravelInTime
      KX AUDIO DRIVER MOD
       
      Hi guys i am a small developer, i really like to use my sound blaster cards on my machines and i love also coding, so when i find the source code for the kx audio driver on git hub and then Eugene, the creator of kx audio driver decided to no longer maintain the project, i decided to start working on a mod of this driver and maintain it. 
       
      With my mod, created starting from the sources of the last official version of kx audio driver and all the small commiunity updates, i am working to keep the driver compatible with the latest mac os versions and to improove the driver over time.
       
      Supported cards are:
       
       - most of the Sound Blaster live!, live! 5.1 and live! 5.1 digital series (except for the cards not using the 10k1 architecture)
       - sound blaster pci 512 and pci 256
       - Sound Blaster Audigy, Audigy 2 and Audigy 2 zs series
       - E-MU cards based on the 10k2 sound chip (like the EMU8852 aka 0404m, including the pcie version)
       - Sound Blaster Audigy 4 (SB0610 only) and the Audigy 4 pro
       - Sound Blaster Audigy RX (SB0155)
       - other creative and e-mu cards based on the (10k1,10k2, 10k2.5 and CA10300 based cards)
       
      The NOT supported cards includes (but are not limited to):
       
       - ES1370/ES1371/ES1372/ES1373 based sound cards
       - Any CA0106 based card and cards with similar architectures (like sound blaster live! 24 bit, sound blaster audigy SE SB0570, audigy LS and similars, but audigy SA is supported)
       - Any sound blaster x-fi (some of them works on macOS using a modified version of voodoo hda)
       - Any sound blaster recon3D
       - Sound blaster Audigy FX
       - Any sound blaster Z/ZS/ZX and similar series
       - Any sound blaster AE5/AE7/AE9 series
       - Any sound card without an emu sound chip
      - Any ISA Sound card
       
      In the time being the things i have modded or added with this mod are:
       
      - cracking and stability fixes
       
      - added a more proper support for the pci express Sound Blaster audigy rx SB0155 (which basically is an audigy 4 with a pcie bridge chip) 
       
      - more user-frienly names for the cards in the settings and other system menus (so the name will be, for example, SB live! 5.1 SB0060 instead of kx SB0060 [e880] witch was shown in the original driver)
       
      - added support to sample rate changing and bit resolution change (the absolte worst supported quality is 7 khz at 8 bit dept while the absolute best is 192 khz at 32 bit depth)
       
      - inputs support
       
      - added boot args to manage the driver (more info on those soon)
       
      What i'd like to implement but i don't know how to do:
       
       - fix the support when using more than one card, to get all the cards shown in the settings and other menus,
       
       - have the gameport/midi port of older cards to be used in mac os as a midi in/out
       
      If other developers would like to join and help they are free to do so, this is a free open source project afterall, and also an hand from other people with testing and feedback will be nice.
       
      LINKS and downloads:
               -  github repo:                                               https://github.com/ITzTravelInTime/kx-audio-driver   (kext download coming soon, since an update is coming)  
       





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