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

IntelMausiEthernet.kext for Intel onboard LAN

975 posts in this topic

Recommended Posts

I have compiled IntelMausiEthernet.kext from Github Resources with XCODE version 11.2.1 with success in Catalina 10.15.2 Beta 2

My Intel I219V2 from Gigabyte Z170X Gaming 7 is working properly, sleep and wake without problem (with ethernet cable attached).

And just for the information, i always use Wifi for daily usage. i just tried new version and give feedback for dev.

Thanks very much

 

Edited by Andres ZeroCross

Share this post


Link to post
Share on other sites
Advertisement
On 11/16/2019 at 11:24 PM, Andres ZeroCross said:

I have compiled IntelMausiEthernet.kext from Github Resources with XCODE version 11.2.1 with success in Catalina 10.15.2 Beta 2

My Intel I219V2 from Gigabyte Z170X Gaming 7 is working properly, sleep and wake without problem (with ethernet cable attached).

And just for the information, i always use Wifi for daily usage. i just tried new version and give feedback for dev.

Thanks very much

Screen Shot 2019-11-17 at 11.18.18.png

 

HI, Can you please add support for I350 onboard lan?  (0x15218086 )

here is the key from AppleIGP.kext, as you may already now, It's unstable with kernal panics... but when it does not panic, it works well.

 

 

 

<key>i350</key>
        <dict>
            <key>CFBundleIdentifier</key>
            <string>com.insanelymac.driver.AppleIGB</string>
            <key>IOClass</key>
            <string>AppleIGB</string>
            <key>IOPCIMatch</key>
            <string>0x15218086 0x15228086 0x15238086 0x15248086 0x15468086</string>
            <key>IOProviderClass</key>
            <string>IOPCIDevice</string>
            <key>NETIF_F_TSO</key>
            <true/>
        </dict>

Share this post


Link to post
Share on other sites
On 10/2/2019 at 4:07 PM, Evgeny2256 said:

Hello!
Please, help
I have a motherboard X8DTH with ethernet controller INTEL 82576.  I downloaded the kext from the first page, but the network interface still does not work. Please tell me what to do. I used kext utility for installation 

Please, help

 

Hi. Smalltreexxxxx.kext will support your MB. On Mojave and Catalina. I know , I have the same Nic on my X8DTi

Share this post


Link to post
Share on other sites
On 4/8/2018 at 4:06 PM, liuhongxin1993 said:

Supported devices for SmallTreeIntel8254x.kext:

  • 8086:107c 82541PI Gigabit Ethernet Controller

 

unfortunately not true. i have that card and it doesn't work at all.

Share this post


Link to post
Share on other sites
14 minutes ago, Mieze said:

@maleorderbride I'm sorry but there is none. IntelMausiEthernet was designed exclusively for PCH's integrated LAN solution.

 

Mieze

Thanks for the quick response Mieze (and all of your work around here). Is your RTL8111 also only for integrated LAN's?

 

Or would it work with a card like this? https://www.newegg.com/syba-sd-pex24009/p/N82E16833328018?Description=RTL8111&cm_re=RTL8111-_-33-328-018-_-Product&quicklink=true

Edited by maleorderbride

Share this post


Link to post
Share on other sites
26 minutes ago, maleorderbride said:

Is your RTL8111 also only for integrated LAN's?

 

Or would it work with a card like this? https://www.newegg.com/syba-sd-pex24009/p/N82E16833328018?Description=RTL8111&cm_re=RTL8111-_-33-328-018-_-Product&quicklink=true

It works well with any RTL8111 add-on card but you should avoid cards based on the outdated RTL8111B as this chip doesn't support offload features for IPv6 and is junk silicon due to several hardware bugs. Personally I'm using an RTL8111E-based card for testing.

 

Unfortunately your product link doesn't mention the exact chip used on the card.

 

Mieze

Share this post


Link to post
Share on other sites
On 1/31/2020 at 9:49 PM, maleorderbride said:

See reviews

Quote

Cons: not a realtek RTL8111 chipset (its an Agere ET-1310)
wont obtain IP via DHCP seems to work if I manually config IP (all other computers grab DHCP ip's fine)

 

Share this post


Link to post
Share on other sites
Posted (edited)
25 minutes ago, MacXZ said:

Can support intel X722 network(x710 series)?

https://downloadcenter.intel.com/product/139349/Intel-Ethernet-Network-Adapter-X722-Series

Only linux and windows driver be provided.

 

I try to learn driver development on mac os, but I think I need learn more about IOKit.

you have to learn i/o kit if you want to make a driver, i/o kit is the only way of comunicating with the os and having access to all the features you need to make driver, for example only using i/o kit you can have access to the allocation of dma buffers

Edited by ITzTravelInTime

Share this post


Link to post
Share on other sites
4 hours ago, ITzTravelInTime said:

you have to learn i/o kit if you want to make a driver, i/o kit is the only way of comunicating with the os and having access to all the features you need to make driver, for example only using i/o kit you can have access to the allocation of dma buffers

Thx for ur reply.

Can u recommend some books or site to learn I/O kit?

 

Would X722 series be supported by intelmausiethernet.kext in the future?

 

Thx again!

Share this post


Link to post
Share on other sites
5 hours ago, MacXZ said:

Would X722 series be supported by intelmausiethernet.kext in the future?

 

No, because it's a completely different architecture. Sorry!

 

Mieze :cat:

Share this post


Link to post
Share on other sites
On 4/18/2020 at 8:25 PM, Mieze said:

 

No, because it's a completely different architecture. Sorry!

 

Mieze :cat:

 

All right.

I have try to learn something from intelmausiethernet project, it beyond my head now.

 

Can u give me some advice to learn i/okit? 

Thx again.

Share this post


Link to post
Share on other sites
Posted (edited)
21 minutes ago, MacXZ said:

 

All right.

I have try to learn something from intelmausiethernet project, it beyond my head now.

 

Can u give me some advice to learn i/okit? 

Thx again.

 

I strongly reccommend you to have a strong c and c++ blackground as well as a good experience in working at low level and with the hardware (and also understand some machine architecture and machine language). There are some books i know of to leran the os architecture and i/o kit (but it's all old stuff and i didn't find the included explainations good enought in some instances, but they are better than nothing as a starting point) which are: OS X and IOS kernel programming and OS X internals.

 

I also reccomend you to check out the source code of some simple apple-made drivers (see some older source code from apple like the systems kexts from os x 10.6 or 10.5) and some simple open source drivers, for example for the sound drivers you can check out the cmi8738 driver.

 

Consider that a lof of stuff in those old books and source codes is outdated, for example you may need to be carefoul because of all the changes in how memory allocation works.

 

Final considerations are that you may want to work using an older version of xcode and an older version of mac os x since a lot of stuff reguarding the development of some kexts got deprecated or havely changed, and also consider giving your users some backwards compatibility like making the driver compatible with mountain lion or even snow leopard on 32 bit machines (people like owners of the older mac pros will appreciate that) and consider to make your projects open source, the hackintosh commiunity can be very untrusty of closed source projects and having your project to be open source is also a nice way to get help and feedback and have someone to keep the development of them after you abbandon them.

Edited by ITzTravelInTime

Share this post


Link to post
Share on other sites
10 hours ago, ITzTravelInTime said:

 

I strongly reccommend you to have a strong c and c++ blackground as well as a good experience in working at low level and with the hardware (and also understand some machine architecture and machine language). There are some books i know of to leran the os architecture and i/o kit (but it's all old stuff and i didn't find the included explainations good enought in some instances, but they are better than nothing as a starting point) which are: OS X and IOS kernel programming and OS X internals.

 

I also reccomend you to check out the source code of some simple apple-made drivers (see some older source code from apple like the systems kexts from os x 10.6 or 10.5) and some simple open source drivers, for example for the sound drivers you can check out the cmi8738 driver.

 

Consider that a lof of stuff in those old books and source codes is outdated, for example you may need to be carefoul because of all the changes in how memory allocation works.

 

Final considerations are that you may want to work using an older version of xcode and an older version of mac os x since a lot of stuff reguarding the development of some kexts got deprecated or havely changed, and also consider giving your users some backwards compatibility like making the driver compatible with mountain lion or even snow leopard on 32 bit machines (people like owners of the older mac pros will appreciate that) and consider to make your projects open source, the hackintosh commiunity can be very untrusty of closed source projects and having your project to be open source is also a nice way to get help and feedback and have someone to keep the development of them after you abbandon them.

I appreciate it.

I was a iOS developer, and a go developer now. But it seems that no help to develop a driver.

 

Thx for ur advice. I would follow ur advise and have a try.

Share this post


Link to post
Share on other sites
Posted (edited)

Issue: no ipv6 addresses on Nic after sleep/wake.

 

Hi,

I use this driver with OC 0.5.7/10.15.4 on a Gigabyte B360M D3H (i5-8400).

Currently, after sleep/wake, the NIC loses all its ipv6 addresses. Reboot or ifconfig down/up resolves this temporarily.

I added a Realtek NIC with RTL8111 Driver and compared the debug messages and code of both drivers. As I am no driver coder please do _not_  take the following as a fact...

 

It seems that both drivers behave differently during wake up. Both drivers run through their enable-function (intelEnable() , enableRTL8111()).

While the Realtek Driver always calls setLinkStatus(kIONetworkLinkValid)  in its enableRTL8111() func, the Intel driver has a condition wrapped around the call so that after wake, setLinkStatus() was not called during my tests.

 

Snippet from intelEnable() (including an additional DebugLog)

if (!linkOpts || !intelCheckLink(&adapterData)) {
        linkOpts = 0;
        setLinkStatus(kIONetworkLinkValid);
        DebugLog("intelmausi setLinkstatus=%d in intelEnable if-branch()  \n", kIONetworkLinkValid);

    }

the variable linkOpts holds the value 4 after wake.

 

I looked at the rest of the code where linkOpts is set. Before sleep, it gets set to value 4 (=kIONetworkLinkNoNetworkChange) in func intelDisable()

 linkOpts = kIONetworkLinkNoNetworkChange;
        linkStatus |= linkOpts;

I did not find any corresponding code in RTL8111 driver and I do not really understand its purpose ,why linkOpts is set to kIONetworkLinkNoNetworkChange.

For testing purposes I changed the code above to

linkOpts = kIONetworkLinkValid;
        linkStatus |= linkOpts;

linkOpts now gets value 1 (= kIONetworkLinkValid) and now the condition in intelEnable() is met and setLinkStatus(kIONetworkLinkValid) is called after wake and ipv6 addresses are bound to the NIC.

 

As said, I do not really understand the idea behind linkOpts value and its usage in enableIntel().

Perhaps some devs could have a look at the topic to get ipv6 assigned after sleep/wake.

 

Kind regards, T.

 

 

Edited by TalkingHead
I am _not_ a coder ;-)

Share this post


Link to post
Share on other sites

@TalkingHead There is no bug, the driver is working as specified. The root of the problem is located in your DHCPv6 configuration. The option kIONetworkLinkNoNetworkChange tells the network stack to skip renewal of the DHCP leases after wakeup because the has been no change. This speeds up wakeup and has been designed to work that way. It's only used when WoL is enabled, a valid link was established while the machine went to sleep and the link is still up when it wakes up.

 

I tested this option intensively years ago when I implemented this feature and I use it in my network without any problems since then. In case you are experiencing problems, best option would be to fix DHCPv6, in case you can't do that, disable WoL on your machine and everything will be fine.

 

Mieze :cat:

Share this post


Link to post
Share on other sites
19 minutes ago, Mieze said:

@TalkingHead [...big snip...]

 

I tested this option intensively years ago when I implemented this feature and I use it in my network without any problems since then. In case you are experiencing problems, best option would be to fix DHCPv6, in case you can't do that, disable WoL on your machine and everything will be fine.

 

Mieze :cat:

Hello Mieze,

thank you very much for the details and clarification.

And thnx for the drivers :-)

 

Kind regards, T.

Share this post


Link to post
Share on other sites
Posted (edited)

Hi everybody!
Great work Mieze!!!
Using a compiled Kext of previous version and wondering if a compiled version of version 2.5.1d1 can be found somewere or if someone could be so kind to compile it and attach it here (MacOS 10.15 Catalina).

TIA

K.

   
Edited by KvL
typo fix

Share this post


Link to post
Share on other sites

  • Recently Browsing   0 members

    No registered users viewing this page.

Announcements

  • Similar Content

    • By Del
      I have been trying to get my Lenovo G570 i5 2430M with HD3000 (id: 116) to work for almost 2 months. Mountain Lion works flawlessly but Mavericks onwards, display stays off with the exact same setup (Chameleon: Extra folder with smbios mbp8,1 included in attachment)
       
      I'm able to boot and see the screen with remote desktop but internal display stays off.
       
      found an old post which fixed issue for few users
       
      I understand HD3000 is natively supported till High Sierra, which is why I'm totally baffled and out of ideas to proceed with.
       
      Any help is greatly appreciated
      Thanks
       
      @jl4c
      Alex.zip
    • By tapochek2004
      Hello. I have recently installed a "Hackintosh Sierra Zone" 10.12.3 distro (yes, I know they are unstable and might contain malware) on my Dell Inspiron 7567. I am now experiencing trouble with the integrated GPU, Intel HD (not UHD!) Graphics 630: there is no acceleration, I can observe noticeable screen flickering and the displayed amount of VRAM is 7MB.
       
      Here's what I've tried so far:
       
      1. Enabling InjectIntel and disablegfxfirmware and setting Fake ID = 0x59120000.
      2. Changing SMBIOS to iMac 18,1 (still displayed as a 21,5 in About This Mac).
      3. The last thing I tried was installing Lilu and WhateverGreen as per this manual, which required me to disable the first workaround completely.
       
      I have included my Clover's config.plist and the output of kextstat.
       
      Thanks in advance!
       
      Best regards, Luka
       
      P. S. Is it possible to move this topic into 'Intel Graphics'?
      config.plist
      kextstat.rtf
      report.tiff
    • By tosziro
      Hello,
       
      I successfully installed MacOS Catalina on this machine it booted after it. Keyboard, ethernet, touchpad, battery status was working. Only that was broken was wifi...
       
      Sadly after reboot out of the blue it stop to work completly. Displays kernel panic. I didnt change anything.
      panic 2cpu 2 caller userspace watchdog timeout no successful checkins from com.apple.logd in 120 seconds
       
      This is my first Hackintosh.  I have complety no idea what should I do now. :-(
      Maybe you could help me, Im attaching my EFI config... I used OpenCore to install.
       
      Intel Core i7-4702MQ Intel HD Graphics 4600 / Nvidia 760M  
      Thank you.
      EFI.zip
    • 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/H 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 unsupported up to version 2.3.x. Version 2.4.0 might come with experimental jumbo frame support depending on test results of the development versions. No support for 32bit kernels.  
      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 or OC injection). It's your call! 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.  
      The same procedure should be applied when you are experiencing erratic behavior after an update! Please keep in mind that you have to disable SIP temporarily when you are using OC.
       
      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
      I want to disable Energy Efficient Ethernet (EEE) but I don't know how? Select a medium without EEE manually. 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, G and H versions of the RTL8111/8168 and is known to work stable on these devices.  
      Changelog
      Version 2.4.0d4 (2020-10-10) Experimental jumbo frame support up to 9k for chipset 16 and above Requires 10.14 or newer. Version 2.3.0 (2020-08-14) Reworked medium section and EEE support to resolve problems with connection establishment and stability. Added option to supply a fallback MAC. Updated Linux sources to 8.047.04 and added support for new family members Requires 10.14 or newer.
      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 above: https://www.insanelymac.com/forum/files/file/88-realtekrtl8111-binary/  
      Building from Source
      I'm always using the latest version of XCode 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.
×