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

IntelMausiEthernet.kext for Intel onboard LAN

975 posts in this topic

Recommended Posts

@xiyue: Please post kernel logs showing the incident which should include at least a full boot sequence. Use the debug version of the driver to create the logs.

 

Mieze

Share this post


Link to post
Share on other sites
Advertisement

@xiyue: Please post kernel logs showing the incident which should include at least a full boot sequence. Use the debug version of the driver to create the logs.

 

Mieze

@Mieze: Thanks for your reply. The attachment is the log files I collected. In the package, kernel-1.log is with cable plugged, and kernel-2.log is with cable unplugged.

kernellog.zip

Share this post


Link to post
Share on other sites

@xiyue: Please post kernel logs showing the incident which should include at least a full boot sequence. Use the debug version of the driver to create the logs.

 

Mieze

@Mieze: Thank you for your attention, May I ask what information can I provide in depth? Such as log or screenshots?

Share this post


Link to post
Share on other sites

I checked your kerne logs and they look good. There is no indication of an error. Honestly I have no idea why the link isn't established. Sorry!

 

Mieze

Share this post


Link to post
Share on other sites

I checked your kerne logs and they look good. There is no indication of an error. Honestly I have no idea why the link isn't established. Sorry!

 

Mieze

@Mieze

Oh, that's a bad news. I think the process of loading the driver should be normal. Could the NIC cable plug / unplug the trigger event that is not handled correctly? Is there a tool or method can be used for debugging and then to collect some useful data?

 

And, if I do not load the NIC driver, the NIC led light is always lit with cable plugged(after OS boot), rather than on for a while, off for a while.

Share this post


Link to post
Share on other sites

@Mieze,

 

I am running into a problem potential related to the drive. Here is the symptom: when computer boot up, the everything works fine, but when the computer wakes up from sleep, sometimes ( not always), the computer freezes: i.e. No KP, but screens just freezes, keyboard stops working as well. After removing IntelMausiEthernet.kext, there is no more freezes. The computer is HP EliteDesk 800 G1. The NIC is onboard Intel Corporation Ethernet Connection I217-LM (rev 04). I am running macOS 10.12.6. I tried IntelMausiEthernet version 2.2.0. And recompiled from latest codebase (2.3.0), both show the same symptom. Any hint to how can I debug this problem? I really hope that I could get your driver working on the computer. Thanks a lot!

Share this post


Link to post
Share on other sites

@Mieze,

 

I am running into a problem potential related to the drive. Here is the symptom: when computer boot up, the everything works fine, but when the computer wakes up from sleep, sometimes ( not always), the computer freezes: i.e. No KP, but screens just freezes, keyboard stops working as well. After removing IntelMausiEthernet.kext, there is no more freezes. The computer is HP EliteDesk 800 G1. The NIC is onboard Intel Corporation Ethernet Connection I217-LM (rev 04). I am running macOS 10.12.6. I tried IntelMausiEthernet version 2.2.0. And recompiled from latest codebase (2.3.0), both show the same symptom. Any hint to how can I debug this problem? I really hope that I could get your driver working on the computer. Thanks a lot!

First of all, as your system has a Q87 chipset and an I217LM, there is probably some remote management software built into the BIOS. Make sure that it's disabled completely. As you don't get a KP but a system freeze I assume that the ME is in control of the NIC which may explain the freeze. Also check other BIOS settings and take a look at the DSDT. Sleep wake problems often result form BIOS and/or DSDT problems and are hard to debug. Also try to disable WoL in System Preferences as it may help too. I had an instant reboot on wakeup with WoL enabled on my development machine too and was able so resolve it with a DSDT patch and a change in the BIOS settings. Good luck!

 

Mieze 

Share this post


Link to post
Share on other sites

First of all, as your system has a Q87 chipset and an I217LM, there is probably some remote management software built into the BIOS. Make sure that it's disabled completely. As you don't get a KP but a system freeze I assume that the ME is in control of the NIC which may explain the freeze. Also check other BIOS settings and take a look at the DSDT. Sleep wake problems often result form BIOS and/or DSDT problems and are hard to debug. Also try to disable WoL in System Preferences as it may help too. I had an instant reboot on wakeup with WoL enabled on my development machine too and was able so resolve it with a DSDT patch and a change in the BIOS settings. Good luck!

 

Mieze 

@Mieze, Thanks a lot for your tip. You are right, there is an AMT built into BIOS. I tried to disable it completely from BIOS. But, the computer couldn't boot up anymore, it seems waiting for something after loading ethernet driver.  The good news is that after I disabled the watchdog, (the watchdog is 5 seconds, and it is more or less matching the delay between computer wakes up and hang when watchdog is enabled), and disabled WOL, I didn't see hang problem(crossing fingers).  thanks for a lot for your great effort providing the driver, and your suggestion that fixed the hang problem!

Share this post


Link to post
Share on other sites

@Mieze

 

love this kext, but... is there any feature to "hide" the whole bootlog messages while using this kext during verbose boot?

Any bootvariable to set "silent boot" w/o any printouts in the bootlog while verbose booting?

 

Just a question and please don't worry, if this is not a feature yet, neither planned for a common release. Thanx in advance. Regards.

Share this post


Link to post
Share on other sites

@Mieze

 

love this kext, but... is there any feature to "hide" the whole bootlog messages while using this kext during verbose boot?

Any bootvariable to set "silent boot" w/o any printouts in the bootlog while verbose booting?

 

Just a question and please don't worry, if this is not a feature yet, neither planned for a common release. Thanx in advance. RegardsWhat.

Personally I wonder why anybody wants to have this feature?  :wacko:

 

By the way, it's an open source driver any everybody is free to modify it according to his/her needs.

 

Mieze

Share this post


Link to post
Share on other sites

 

Hi,

 

I am running an AsRock H170M-ITX-ac with an Intel I219V interface under 10.12.1 with version 2.2.0d4, injected by Clover. When I boot the system with the cable connected, everything works fine. If I pull the cable and then reinsert, the status of the interface starts to toggle between 'Cable Unplugged' and 'Not Connected' and I have to reboot to get ethernet working again.

 

This board also has an extra Realtek 8111H interface. At first I had not installed the Realtek driver and the problems described above already appeared. I installed the Realtek driver and if then I pull and reinsert the cable on the Realtek 8111h interface, ethernet comes back up again with no problems.

 

Anyone any ideas what could be going wrong with the I219V port?

 

Rgds,

Tom

The problem I encountered is the same as yours, the difference is my laptop is HP820G4, and the driver is v2.3.0

Mieze also helpless...

Share this post


Link to post
Share on other sites

  The problem I encountered is the same as yours, the difference is my laptop is HP820G4, and the driver is v2.3.0

Mieze also helpless...

These kind of problem results from something else being in control of the NIC. Check your BIOS settings and make sure that any kind of remote management software and the UEFI network stack are disabled.

 

Mieze

Share this post


Link to post
Share on other sites

@Mieze

These kind of problem results from something else being in control of the NIC. Check your BIOS settings and make sure that any kind of remote management software and the UEFI network stack are disabled.

 

Mieze

Thank you for your attention. I have checked the BIOS settings, the relevant options only "wake on lan" and "lan/wan switch", and are disabled. I installed windows 10, kali linux, centos linux, freebsd with this laptop, the NIC works fine. I guess the problem is handle of the cable plug state, Can you make a tool to debug and log data? I will be a dedicated tester.

 

I hope my poor English can express my wishes correctly.

Share this post


Link to post
Share on other sites

I guess the problem is handle of the cable plug state, Can you make a tool to debug and log data? I will be a dedicated tester.

There is no need to make anything because you can use the debug version of the driver as it logs such events in detail. If there was a problem with link state detection, you should find some related log messages in the kernel logs when you plug/unplug the cable.

 

Mieze

Share this post


Link to post
Share on other sites

@ACIDSkyRU: Use the debug version of the driver to collect more detailed logs and report back with log data containing at least one complete boot sequence. Please don't upload the complete file as it's no fun to search for log messages in a > 500MB file.

 

Mieze

Share this post


Link to post
Share on other sites

The management engine is in control of the NIC so that the driver is unable to take control. Make sure that the UEFI network stack and any remote management function is disabled in UEFI setup.

 

Mieze

Share this post


Link to post
Share on other sites

Hi Mieze,

Ok it's off topic and maybe not! I was sensitized with your topic and the dedication made in memory of your cat. You are certainly a good person! I also have and love my Pipo and Gui. A hug ?

post-1313347-0-60554500-1511369830_thumb.jpg

post-1313347-0-62775900-1511369861_thumb.jpg

post-1313347-0-59596300-1511369878_thumb.jpg

Share this post


Link to post
Share on other sites

Nothing helped. Rolled back BIOS to older versions. On the website Tony, there are reports on the plant of my Board (ASUS Z170i gaming pro) and it works. There is a possibility of conflict with Lilu.kext and plugins?

Share this post


Link to post
Share on other sites

Nothing helped. Rolled back BIOS to older versions. On the website Tony, there are reports on the plant of my Board (ASUS Z170i gaming pro) and it works. There is a possibility of conflict with Lilu.kext and plugins?

Provided the BIOS updates also contain a ME firmware update, have you chosen to update the ME firmware too while installing the BIOS update?

 

I don't think that a Lilu plugin is causing the driver failure, at least I have no reason to assume it might be but, as not all of them are open source, it's hard to rule out completely.

 

Please post an IOReg dump. Use version 3.0.2 of IORegistryExplorer to create the dump.

 

Mieze

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