Jump to content
Mieze

Driver for Realtek's RTL810x Fast Ethernet Series

169 posts in this topic

Recommended Posts

Newbie here. I had a hackintosh for two years, build from refurbished components, I used the Tonymacx86 method to install Yosemite, El Capitan and Sierra. The old motherboard crashed las month, and I replaced it with a similar one, slightly older. Ethernet refused to work. All attempts to get a working kext failed.

Specs are

Gigabyte fsb 1066 ga-945gzm-s2
Intel Core 2 Duo E8500
Nvidia GeForce 6200

Due to the Nvidia Graphics card I need to use npci=0x3000 flag to get it to boot. On the previous motherboard, this caused no issues with the lan connection.

I have aquired another lan card, RTL8139c, RehabMan on the Tonymacx86 board said to get the kext created by Mieze. I did, but it failed as well. I have downloaded the latest kext posted by Mieze, linked in this thread, found the kext file and pasted it into the installation pen drive. Failed. Reading this discussion, I see that she says that npci=0x3000 with cause issues with the lan kext. Perhaps this is why none of the lan cards do not work? In this case, I shall need a video card replacement. I am willing to cooperate and get logs and such, if I am showed where to find them, I have never face anything like this in the previous two hackintoshing years. I have only installed kexts using pkg files (the least mpkg) or copy/past into the Clover kext folder in the EFI partition, so I need to learn the other way to install them as well.

Share this post


Link to post
Share on other sites
Advertisement

Newbie here. I had a hackintosh for two years, build from refurbished components, I used the Tonymacx86 method to install Yosemite, El Capitan and Sierra. The old motherboard crashed las month, and I replaced it with a similar one, slightly older. Ethernet refused to work. All attempts to get a working kext failed.

Specs are

Gigabyte fsb 1066 ga-945gzm-s2

Intel Core 2 Duo E8500

Nvidia GeForce 6200

Due to the Nvidia Graphics card I need to use npci=0x3000 flag to get it to boot. On the previous motherboard, this caused no issues with the lan connection.

I have aquired another lan card, RTL8139c, RehabMan on the Tonymacx86 board said to get the kext created by Mieze. I did, but it failed as well. I have downloaded the latest kext posted by Mieze, linked in this thread, found the kext file and pasted it into the installation pen drive. Failed. Reading this discussion, I see that she says that npci=0x3000 with cause issues with the lan kext. Perhaps this is why none of the lan cards do not work? In this case, I shall need a video card replacement. I am willing to cooperate and get logs and such, if I am showed where to find them, I have never face anything like this in the previous two hackintoshing years. I have only installed kexts using pkg files (the least mpkg) or copy/past into the Clover kext folder in the EFI partition, so I need to learn the other way to install them as well.

My driver doesn't support the RTL8139 but there used to be a native driver for this chip in Snow Leopard. Even the source code is available and, in case the binary doesn't work out of box, it should be possible to build this driver for newer versions of OS X which still support 32bit kernels.

 

Mieze

Share this post


Link to post
Share on other sites

My driver doesn't support the RTL8139 but there used to be a native driver for this chip in Snow Leopard. Even the source code is available and, in case the binary doesn't work out of box, it should be possible to build this driver for newer versions of OS X which still support 32bit kernels.

 

Mieze

Well, I am not too advanced so that I would be able to build the kext from source into a new version, from Sierra. I was hoping that there was a way to bypass the npci=0x3000 and make your kext work in Sierra. If not, my Hackintosh is lost for good, I need to get a new system. If the npci=0x3000 is caused by an issue in the motherboard itself. Right now, I have an onboard lan rtl8110sc and another lan card rtl8139c. You say there are no kexts for this lans for Sierra.

Share this post


Link to post
Share on other sites

Hi,

I have a HP 625 notebook with a RTL8101E card.
I installed the kext, which loads fine but my internet won't come up. 
It's either "Cable is not plugged in" or "Cable is plugged in, but the computer has no IP-adress assigned to it".

When I manually assign a DNS and IP to the interface, the same happens only then it toggles from "Connected" to "Cable is not plugged in".
Funny thing is, it does not matter if the cable actually is plugged in or not... even if it is not it still toggles between "connected" and "cable is not plugged in".

I also notice that there's no MAC-adress assigned to it...

Any idea how I can get it working?

Thanks in advance





 

RTL8101E.txt

Share this post


Link to post
Share on other sites

Hi,

 

I have a HP 625 notebook with a RTL8101E card.

I installed the kext, which loads fine but my internet won't come up. 

It's either "Cable is not plugged in" or "Cable is plugged in, but the computer has no IP-adress assigned to it".

 

When I manually assign a DNS and IP to the interface, the same happens only then it toggles from "Connected" to "Cable is not plugged in".

Funny thing is, it does not matter if the cable actually is plugged in or not... even if it is not it still toggles between "connected" and "cable is not plugged in".

 

I also notice that there's no MAC-adress assigned to it...

Looks like ASPM is causing the trouble. Either way you have messed with the settings in the driver's Info.plist or your BIOS forces it's activation. In case you played with the Info.plist, revert your changes, but if it's the BIOS you need to disable ASPM support for the driver to work properly.

 

Mieze

Share this post


Link to post
Share on other sites

Hm... I did not change anything within its info.plist, so I guess my BIOS is the culprit. 
I don't have any settings option related to ASPM... only the basic stuff like boot order, SATA mode, supervisor password, UEFI on/off et cetera. Nothing power management related anyway.


EDIT: Well, it does not matter anymore. The laptop had a broken screen and I was busy replacing it. While it was still in a 'test setup' (read: laptop and screen dismantled) my cats thought it was a good idea to pull everything from the dining table. Thus the replacing screen is also broken now.  :D R.I.P. 

Edited by ricoc90

Share this post


Link to post
Share on other sites

My driver doesn't support the RTL8139 but there used to be a native driver for this chip in Snow Leopard. Even the source code is available and, in case the binary doesn't work out of box, it should be possible to build this driver for newer versions of OS X which still support 32bit kernels.

 

Mieze

 

Please i request you to make the RTL8139 driver compatible with newer versions , i am currently on yosemite and i have tried every kext available but i can't make my ethernet to work. By using your driver ethernet shows as connected but i can't connect to internel also DHCP shows wrong ip address.

Share this post


Link to post
Share on other sites

Please i request you to make the RTL8139 driver compatible with newer versions , i am currently on yosemite and i have tried every kext available but i can't make my ethernet to work. By using your driver ethernet shows as connected but i can't connect to internel also DHCP shows wrong ip address.

Let's be real about one thing: Wasting serval hours of work in order to support 20 years old hardware is beyond all reason. Take my advice and upgrade your system!

 

Mieze

Share this post


Link to post
Share on other sites

@jalves: I've checked the driver's code again and found no evidence for a driver bug. I don't have hardware to test myself but as sleep/wake and link change detection are basic functions of a driver which have been thoroughly tested, it's hard to imagine a scenario in which a driver bug causing this behavior wouldn't have been found much earlier. That's why I'm not willing to believe in a driver bug until some user with the same chip confirms this issue.

 

Please check your BIOS settings and make sure that network boot, the UEFI network stack as well as any LAN related power management functions are disabled (in particular if there is any function to put the NIC into a low power state when the cable is disconnected). 

 

Mieze

Hello @Mieze

 

Just to write down, I decided to test version 1.0.0 and "voia-la", the problem I reported did not occur.

It works 100% after sleeping or unplug and plug the cable.

 

;)

 

 

Share this post


Link to post
Share on other sites

Hello @Mieze

 

Just to write down, I decided to test version 1.0.0 and "voia-la", the problem I reported did not occur.

It works 100% after sleeping or unplug and plug the cable.

Congratulations but it doesn't change my point of view because the RTL8106E is one of the most frequently used chips of this series and in case of a serious bug there would be more than just 1 error report. As the driver loads Realtek provided firmware into the chip, which may be different in 1.0.0 than 2.0.0, this could be the reason for the problem but that's beyond by scope.

 

Mieze

Share this post


Link to post
Share on other sites

Hi, I have this issue where the network will be "jammed" if I try to download 2 files at the same time, any idea why this happen?

I have Realtek rtl8139/810x on my laptop and using your kext.

Share this post


Link to post
Share on other sites
3 minutes ago, baddles said:

Hi, I have this issue where the network will be "jammed" if I try to download 2 files at the same time, any idea why this happen?

I have Realtek rtl8139/810x on my laptop and using your kext.

Sorry, but you are on a wrong track because this is not a driver issue. A driver handles packets, nothing more and nothing less. Anything else is located in higher levels.

 

Mieze

Share this post


Link to post
Share on other sites
On 2/19/2014 at 7:43 AM, Mieze said:

I put the driver into EFI/Clover/kexts, and the driver is already loaded, but the Mac address is wrong. I used the Debug driver, but I didn't find anything related to the Realtek RTL8100 in /var/log/system.log. ,Can you tell me what to do? Thank you!

 

Share this post


Link to post
Share on other sites
17 hours ago, LockyDeng said:

 

Follow the instructions in post#1 of the thread. They have been updated for Sierra and above a few moments ago.

 

Mieze

Share this post


Link to post
Share on other sites
9 hours ago, LockyDeng said:

Mieze please help me analyze the log. Thank you very much.

kernel_2.zip

The driver reports 40:28:36:42:80:ff which is not a valid address. In order to find out what is wrong I need to know the correct MAC address.

 

Mieze

Share this post


Link to post
Share on other sites
On 5/2/2018 at 11:51 AM, LockyDeng said:

Mieze, Do you need me to provide more information?

No, I didn't need more information, just a little bit of time which is a scarce resource at the moment. Please try this and report back. Good luck!

 

Mieze

RealtekRTL8100-V2.0.1d0.zip

Edited by Mieze

Share this post


Link to post
Share on other sites
18 hours ago, Mieze said:

No, I didn't need more information, just a little bit of time which is a scarce resource at the moment. Please try this and report back. Good luck!

 

Mieze

RealtekRTL8100-V2.0.1d0.zip

This driver works very well! When will you publish the final version? Thank you very much!

Share this post


Link to post
Share on other sites
On 5/7/2018 at 2:29 PM, LockyDeng said:

This driver works very well! When will you publish the final version? Thank you very much!

Already done a few moments ago. Have fun!

 

Mieze :cat:

Share this post


Link to post
Share on other sites

Hi Mieze,

 

I have tried your driver on Sierra but when I rebuild the kernel cache I get this error:

 

kxld[com.insanelymac.RealtekRTL8100]: The super class vtable 'vtable for IOEthernetController' for vtable 'vtable for RTL8100' is out of date. Make sure your kext has been built against the correct headers.

Link failed (error code 5).

Prelink failed for com.insanelymac.RealtekRTL8100; omitting from prelinked kernel.

 

Please help! :)

Share this post


Link to post
Share on other sites

The latest prebuilt version requires High Sierra. In order to use it with Sierra please compile it with Xcode 8 using the MacOS 10.12 SDK and 10.12 as the deployment target.

 

Mieze

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 Mieze
      A New Driver for Realtek RTL8111
       
      Due to the lack of an OS X driver that makes use of the advanced features of the Realtek RTL81111/8168 series I started a new project with the aim to create a state of the art driver that gets the most out of those NICs which can be found on virtually any cheap board on the market today. Based on Realtek's Linux driver (version 8.035.0) I have written a driver that is optimized for performance while making efficient use of system resources and keeping the CPU usage down under heavy load.

      Key Features of the Driver
      Supports Realtek RTL8111/8168 B/C/D/E/F/G 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 under IPv4. Support for TCP/IPv6 and UDP/IPv6 checksum offload. Fully optimized for Mountain Lion (64bit architecture) but should work with Lion too. As of now there is no support for Snow Leopard but it can be added if someone will create the necessary patches. 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.  
      Limitations
      As checksum offload doesn't work with jumbo frames they are currently unsupported and will definitely never be. No support for 32bit kernels.  
      Installation
      Before you install the driver you have to remove any installed driver for RTL8111/8168.
      Goto /S/L/E and delete the old driver (Lnx2mac, AppleRealtekRTL8169, etc.). 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. 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 found in /var/log/system.log. For Sierra and above 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. 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. 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.  
      FAQ
      How can I retrieve the kernel logs? In Terminal type "grep kernel /var/log/system.log". I want to disable Energy Efficient Ethernet (EEE) but I don't know how? Take a look at the driver's Info.plist file. There you will find an option named <key>enableEEE</key>. Change its value from <true/> to <false/>. Don't forget to recreate the kernel cache after changing the value. 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.  
      Current status
      The driver has been successfully tested under 10.8.x and 10.9 with the B, C, D, E, F and G versions of the RTL8111/8168 and is known to work stable on these devices.  
      Changelog
      Version 2.2.2 (2018-01-21) Force ASPM state to disabled/enabled according to the config parameter setting. Requires 10.12 or newer. Version 2.2.1 (2016-03-12): Updated underlying linux sources from Realtek to 8.041.00. Added support for RTL8111H. Implemented Apple’s polled receive driver model (RXPOLL). Requires 10.11 or newer. Support for older versions of OS X has been dropped. Version 2.0.0 (2015-06-21): Uses Apple's private driver interface introduced with 10.8. Supports packet scheduling with QFQ. Please note that 2.0.0 is identical to 2.0.0d2. Only the version number has changed. Version 1.2.3 (2014-08-23): Reworked TSO4 and added support for TSO6. Version 1.2.2 (2014-08-44): Added an option to disable Active State Power Management (ASPM, default disabled) as ASPM seems to result in unstable operation of some chipsets. Resolved a problem with Link Aggregation after reboot. Added a workaround for the multicast filter bug of chipset 17 (RTL8111F) which prevented Bonjour from working properly Version 1.2.0 (2014-04-24): Updated underlying linux sources from Realtek to 8.037.00. Improved interrupt mitigate to use a less aggressive value for 10/100 MBit connections. Version 1.1.3 (2013-11-29): Improved transmit queue handling made it possible to reduce CPU load during packet transmission. Improved deadlock detection logic in order to avoid false positives due to lost interrupts. Version 1.1.2 (2013-08-03): Improved SMB performance in certain configurations. Faster browsing of large shares. Version 1.1.0 (2013-06-08): Support for TCP/IPv6 and UDP/IPv6 checksum offload added (can be disabled in Info.plist). Maximum size of the scatter-gather-list has been increased from 24 to 40 segments to resolve performance issues with TSO4 when offloading large packets which are highly fragmented. TSO4 can be disabled in Info.plist without rebuild. Statistics gathering has been improved to deliver more detailed information (resource shortages, transmitter resets, transmitter interrupt count). The interrupt mitigate settings has been changed to improve performance with SMB and to reduce CPU load. Configuration option added to allow for user defined interrupt mitigate settings without rebuild. Version 1.0.4 (2013-05-04): Moved setLinkStatus(kIONetworkLinkValid) from start() to enable(). Cleaned up getDescCommand(). Version 1.0.3 (2013-04-25): The issue after a reboot from Windows has been eliminated. Version 1.0.2 (2013-04-22): Added support for rx checksum offload of TCP and UDP over IPv6. Version 1.0.1 (2013-03-31): Improved behavior when rx checksum offload isn't working properly. Adds the chipset's model name to IORegistry so that it will show up in System Profiler.  
      Known Issues
      There are still performance problems with regard to SMB in certain configurations. My tests indicate that Apple's Broadcom driver shows the same behavior with those configurations. Obviously it's a more general problem that is not limited to my driver. WoL does not work in certain configurations. Old systems with 3 and 4 series chipsets exhibit performance issues in recent versions of macOS because there is no optimized power management for these systems in macOS anymore as Apple dropped support for the underlying hardware a long time ago. In case you are affected, please upgrade your hardware or find an alternative solution because I have no plans for a workaround. Sorry, but I don't think that it's worth the effort.  
      Getting the driver
      The source code can be found here: https://github.com/M...driver_for_OS_X There is also a pre-build binary for Mavericks and Yosemite: http://www.insanelym...n-and-wireless/  
      Building from Source
      I'm using XCode 4.6.3 for development. You can get a free copy of XCode after becoming a member of the Apple developer program. The free membership is sufficient in order to get access to development tools and documentation.
    • 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.
    • By grisno
      Hi people,
       
      Installer to activate the sound card REALTEK ALC282-v2 (10ec:0282) with LayoutID 1 or 3 in MacOS. This installer does not contain AppleHDA patched Kext. To work properly, it must be installed over vanilla AppleHDA.kext.
       
      I want to thank the whole community for their efforts and content provided, because without these it would not be possible to create this installer.
       
      I would appreciate comments and suggestions!!
       
      Status:
      Speakers : OK Headphones : OK HDMI Audio : OK (Intel HD4K Tested) LineIn : N/A (Model Without LineIn) MicInt : OK MicIntNoiseReduction : OK MicExt : N/A (Model Without MicExt) AutoDetectLineIn : N/A (Model Without LineIn) Sleep : OK WakeUp : OK AutoSleep : OK Hibernate : OK Siri : OK   Tested Laptops:
       
      - HP Pavillion 15-D002SS
       
      Coming Soon:
       
      - Unified installer for the different supported operating systems.
      - Support model with LineIn jack.
       
      Modified Verbs:
      01271C20 01271D00 01271EA0 01271F90 01471C10 01471D00 01471E17 01471F90 01871CF0 01871D00 01871E00 01871F40 01E71CF0 01E71D00 01E71E00 01E71F40 02171C30 02171D10 02171E21 02171F00 01470C02   DSDT:
       
      Patch to apply with MaciASL in your DSDT
      ######################################### HDEF v1.00######################################## into method label _DSM parent_label HDEF remove_entry;into device label HDEF insertbeginMethod (_DSM, 4, NotSerialized)\n{\n If (LEqual (Arg2, Zero)) { Return (Buffer() { 0x03 } ) }\n Return (Package()\n {\n "layout-id", Buffer() { 0x01, 0x00, 0x00, 0x00 },\n //"layout-id", Buffer() { 0x03, 0x00, 0x00, 0x00 },\n "hda-gfx", Buffer() { "onboard-1" },\n "PinConfigurations", Buffer() { },\n })\n}\nend;  
×