Popular Post Mieze Posted February 18, 2014 Popular Post Share Posted February 18, 2014 (edited) 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 Edited April 21, 2019 by Mieze 29 1 Link to comment Share on other sites More sharing options...
theconnactic Posted February 18, 2014 Share Posted February 18, 2014 Thank you, Mieze! Now I can stop doing the retail Realtek 8169 plus half-duplex trick to get my 8105 to work. Going to test and report back on my AMD machine ASAP. All the best! 1 Link to comment Share on other sites More sharing options...
Mieze Posted February 21, 2014 Author Share Posted February 21, 2014 As of now the feedback is far from overwhelming. In case there is someone who is willing to test but needs a prebuilt binary, please drop me a line. Mieze 2 Link to comment Share on other sites More sharing options...
theconnactic Posted February 21, 2014 Share Posted February 21, 2014 Sorry, I'm moving to a new home and so the tests I was intending to do will have to wait until the end of this month. But I did download the project and compiled it with Xcode. As soon as I have time to really test it, following your testing recommendations, I'll post here. All the best! Link to comment Share on other sites More sharing options...
Mieze Posted February 21, 2014 Author Share Posted February 21, 2014 Sorry, I'm moving to a new home and so the tests I was intending to do will have to wait until the end of this month. But I did download the project and compiled it with Xcode. As soon as I have time to really test it, following your testing recommendations, I'll post here. All the best! No problem! Mieze Link to comment Share on other sites More sharing options...
Dr. Hurt Posted February 21, 2014 Share Posted February 21, 2014 Mieze, Could you please add a precompiled binary to the opening post. That would help a lot of people test the driver. Thanks in advance Link to comment Share on other sites More sharing options...
Mieze Posted February 21, 2014 Author Share Posted February 21, 2014 Mieze, Could you please add a precompiled binary to the opening post. That would help a lot of people test the driver. Thanks in advance Done! 2 Link to comment Share on other sites More sharing options...
Dr. Hurt Posted February 21, 2014 Share Posted February 21, 2014 Done! Thanks. I'll test it as soon as I get the chance (probably tonight). Link to comment Share on other sites More sharing options...
Dr. Hurt Posted February 22, 2014 Share Posted February 22, 2014 @Mieze: I've just tested it and its working perfectly. The problem I had with the 8169 driver (where OS X always saw the cable as plugged in) seems to have been resolved No performance issues whatsoever so far. On a cosmetic side note though, system profiler says gigabit ethernet instead of fast ethernet. Once again, I cannot thank you enough for you efforts and contributions to this project 2 Link to comment Share on other sites More sharing options...
Mieze Posted February 22, 2014 Author Share Posted February 22, 2014 On a cosmetic side note though, system profiler says gigabit ethernet instead of fast ethernet. Hello Dr. Hurt, thanks for testing the driver. I'll fixed that cosmetic issue. Mieze Link to comment Share on other sites More sharing options...
lisai9093 Posted February 23, 2014 Share Posted February 23, 2014 Thanks Mieze!!! Great work! However, my ethernet failed to work after sleep. Network setting shows self-assigned IP, then indicate it is connected to the Internet but actually it is not. So should I tried the debug version to give u more information? btw my ethernet card is 8105E, device id is 0x8136 Link to comment Share on other sites More sharing options...
Zprood Posted February 23, 2014 Share Posted February 23, 2014 2/23/14 12:08:56.000 PM kernel[0]: Ethernet [RealtekRTL8100]: Warning: PCIe ASPM enabled. 2/23/14 12:08:56.000 PM kernel[0]: Ethernet [RealtekRTL8100]: EEE support enabled. 2/23/14 12:08:56.000 PM kernel[0]: Ethernet [RealtekRTL8100]: TCP/IPv4 segmentation offload enabled. 2/23/14 12:08:56.000 PM kernel[0]: Ethernet [RealtekRTL8100]: TCP/IPv6 checksum offload enabled. 2/23/14 12:08:56.000 PM kernel[0]: Ethernet [RealtekRTL8100]: Using interrupt mitigate value 0x0. 2/23/14 12:08:56.000 PM kernel[0]: Ethernet [RealtekRTL8100]: RTL8105E: (Chipset 11) at 0xffffff80f0cd5000, 84:8f:69:c4:b5:12 Good job, my chip is RTL8136, mavericks 10.9.2, test works well. Mail/DHCP/sleep&wakeup/AppStore/plug&unplug, WoL haven't test. But all play good. 1 Link to comment Share on other sites More sharing options...
Mieze Posted February 23, 2014 Author Share Posted February 23, 2014 However, my ethernet failed to work after sleep. Network setting shows self-assigned IP, then indicate it is connected to the Internet but actually it is not. So should I tried the debug version to give u more information? Yes, please use the debug build and send me the kernel logs. Mieze Link to comment Share on other sites More sharing options...
lisai9093 Posted February 23, 2014 Share Posted February 23, 2014 Yes, please use the debug build and send me the kernel logs. Mieze First connection is around Feb 22 21:55:09, which is before sleep, so it works fine. Then did sleep and wake, plug ethernet to computer, but did not have Internet. system.log.zip 1 Link to comment Share on other sites More sharing options...
Mieze Posted February 23, 2014 Author Share Posted February 23, 2014 First connection is around Feb 22 21:55:09, which is before sleep, so it works fine. Then did sleep and wake, plug ethernet to computer, but did not have Internet. According to your log file the connection gets established and the link is up after wakeup. Feb 22 21:57:55 Mac kernel[0]: Ethernet [RealtekRTL8100]: Link up on en0, 100-Megabit, Full-duplex, No flow-control Please repeat the test and after wakeup use netstat -i in Terminal to check the packet statistics several times with intervals of a few seconds. Does the number of transmitted/received packets increase (which of them?). This is important in order to track down what is wrong. Mieze Link to comment Share on other sites More sharing options...
lisai9093 Posted February 23, 2014 Share Posted February 23, 2014 Mac:~ peter$ netstat -i Name Mtu Network Address Ipkts Ierrs Opkts Oerrs Coll lo0 16384 <Link#1> 768 0 768 0 0 lo0 16384 localhost ::1 768 - 768 - - lo0 16384 127 localhost 768 - 768 - - lo0 16384 localhost fe80:1::1 768 - 768 - - gif0* 1280 <Link#2> 0 0 0 0 0 stf0* 1280 <Link#3> 0 0 0 0 0 en0 1500 <Link#4> 08:9e:01:2b:b4:25 1342 0 1307 0 0 en0 1500 mac.local fe80:4::a9e:1ff:f 1342 - 1307 - - en0 1500 169.254 mac.local 1342 - 1307 - - en0 1500 fd00::a9e:1 fd00::a9e:1ff:fe2 1342 - 1307 - - en0 1500 fd00::18c8: fd00::18c8:d09d:d 1342 - 1307 - - en1 1500 <Link#5> 44:6d:57:a3:50:fb 21180 0 22767 0 0 en1 1500 mac.local fe80:5::466d:57ff 21180 - 22767 - - en1 1500 192.168.0 192.168.0.2 21180 - 22767 - - en1 1500 fd00::466d: fd00::466d:57ff:f 21180 - 22767 - - en1 1500 fd00::d021: fd00::d021:8fa2:4 21180 - 22767 - - p2p0 2304 <Link#6> 06:6d:57:a3:50:fb 0 0 0 0 0 utun0 1380 <Link#7> 0 0 6 0 0 utun0 1380 fe80::c48d: fe80:7::c48d:2a75 0 - 6 - - utun0 1380 fd93:20a0:6 fd93:20a0:6edf:b3 0 - 6 - - Mac:~ peter$ en0 is ethernet and en1 is wifi. This is after wakeup, so ethernet is not working. I guess the number not changing? But my wifi is working normally. Network setting first show this: After few seconds: Link to comment Share on other sites More sharing options...
polyzargone Posted February 24, 2014 Share Posted February 24, 2014 Works great !!!! Finally I have Ethernet connection @ full speed Full duplex 10/100 BaseT and everything works fine so far ! Great, great job and thanks a lot for this ! I'll keep monitoring this but as I say, it works fine so far ! Link to comment Share on other sites More sharing options...
Mieze Posted February 25, 2014 Author Share Posted February 25, 2014 Anyone else here who has tested sleep/wake? Does the network connection work properly after wake? Together with Zythyr, I'm currently preparing a new development release and will post it here as soon as he confirms that it works for him. Mieze 2 Link to comment Share on other sites More sharing options...
polyzargone Posted February 25, 2014 Share Posted February 25, 2014 Don't know for sleep/wake as it never worked for me… BTW if you know how to make it works, It'wd be great ! Link to comment Share on other sites More sharing options...
Mieze Posted February 25, 2014 Author Share Posted February 25, 2014 Well, unfortunately I don't have any NIC of Realtek's Fast Ethernet series so that I can't test the driver myself. I have to rely on user feedback. Mieze Link to comment Share on other sites More sharing options...
Dr. Hurt Posted February 25, 2014 Share Posted February 25, 2014 Anyone else here who has tested sleep/wake? Does the network connection work properly after wake? Together with Zythyr, I'm currently preparing a new development release and will post it here as soon as he confirms that it works for him. Mieze The connection works perfectly fine after wake on my Inspiron with RTL8105 1 Link to comment Share on other sites More sharing options...
Mieze Posted February 25, 2014 Author Share Posted February 25, 2014 The connection works perfectly fine after wake on my Inspiron with RTL8105 Just one more question: which chipset is your RTL8105? You can find the chipset number in the kernel logs. Mieze 1 Link to comment Share on other sites More sharing options...
Dr. Hurt Posted February 25, 2014 Share Posted February 25, 2014 Just one more question: which chipset is your RTL8105? You can find the chipset number in the kernel logs. Mieze I'm not at home now. I'll check and tell you tomorrow. Link to comment Share on other sites More sharing options...
Dr. Hurt Posted February 26, 2014 Share Posted February 26, 2014 2/26/14 11:12:07.000 AM kernel[0]: Ethernet [RealtekRTL8100]: RTL8105E: (Chipset 11) at 0xffffff8082c85000, xx:xx:xx: .... Link to comment Share on other sites More sharing options...
Mieze Posted February 26, 2014 Author Share Posted February 26, 2014 Zythyr and I, we managed to finish the next development release of the driver. I updated the source code and the binaries attached to the first post of this thread a few minutes ago. Everyone is encouraged to test the new release on her/his system. Mieze Link to comment Share on other sites More sharing options...
Recommended Posts