Jump to content
Mieze

IntelMausiEthernet.kext for Intel onboard LAN

936 posts in this topic

Recommended Posts

 

Here is a short list of things to test:

1.) Boot

2.) IP address acquisition via DHCP.

3.) Cable unplug and replug. (Test several times!)

4.) Sleep/wake cycles (Test several times!).

 

 

 

Mieze

 

THANKS Mieze! As for now all the 4 points are working as expected here. Asus Z370 Prime A and i7-8700K. In case of malfunctioning I'll report back. 

 

Have a nice day  :)

Share this post


Link to post
Share on other sites
Advertisement

This is the first test build of version 2.4.0 of IntelMausiEthernet which updates the underlying Linux sources and adds official support for Coffee Lake. All users are encouraged to test it thoroughly. Although I tested it successfully on my I218V, you should keep in mind that this is work in progress which can't be expected to be 100% stable. In case things go wrong and you end up with a kernel panic, you should be prepared to recover your system from that situation.

 

Here is a short list of things to test:

1.) Boot

2.) IP address acquisition via DHCP.

3.) Cable unplug and replug. (Test several times!)

4.) Sleep/wake cycles (Test several times!).

 

In any case, please report back with attached kernel logs of the test run including the boot sequence. In case you need instructions how to retrieve them, please refer to post#1 of the driver's thread in the forum.

 

Good luck!

 

Mieze

     Yay! Well done! Really fulfilled my wish, accidentally solved my problem. 
    This version of the driver works fine on my laptop, and I tested it against the list you provided. every one passed. The attachment is a log of the startup process and the process of plug and unplug cable three times. There is a small detail, that is, plug the cable for the first time after boot, there will be a chance to Auto-negotiation in 10M full-duplex state.
    thanks again!

bootlog1.zip

Share this post


Link to post
Share on other sites

Hello Mieze and greetings from Austria :-) Thank you for developing your driver, I appreciate that I can just download drivers such as your kexts for free when you surely put quite some time into it.

 

Now I have a new mainboard with the new 300 coffee lake series, the Supero C7Z370-CG-L. It uses the i219 (v2) with device ID 0x15b8. Neither your 2.3.0 version nor your newest 2.4.0d0 works, unfortunately.

 

With both versions, the kext enables the NIC and recognizes when I plug in the network cable. But there is no actual connection, it does not receive an IP address via DHCP and when I configure the IP address settings manually, no connection can be established.

 

With Windows 10 on a second drive, the NIC works just fine. I tried unplugging and plugging in the cable several times. Furthermore I also tried the E1000 driver and the exact same behaviour occurs. Cable is recognized when connected, but no actual connection is established.

 

macOS autoconfigures to: 1000baseT, full-duplex, energy-efficient-ethernet, MTU Standard 1500. Playing around with those settings and reverting to 100Mbit/s does not change the behaviour.

 

Now I will try to figure out how to get the log files you asked for in your previous post about the 2.4.0d0 version and I'll write another post with the logs attached. I haven't checked them yet and I am not sure how to get them, yet.

 

Since the kext seems to respond to the device ID and macOS tries to use your kext for the NIC, I am afraid that maybe your driver just does not contain the code to run this NIC properly :( It's a very new mainboard and even though the i219v2 isn't such a new NIC, perhaps my mainboard has a new version of this NIC that isn't known yet?

 

I disabled the NIC in the UEFI, but the UEFI is a mess compared to Asus and Gigabyte, settings aren't explained at all (the user guide that comes with it does not contain them either, and that's supposed to be a professional supermicro product...) and so I am not sure if that is all done correctly. Perhaps I am missing a UEFI setting?

 

Thanks!

Share this post


Link to post
Share on other sites

Hello Mieze and greetings from Austria :-) Thank you for developing your driver, I appreciate that I can just download drivers such as your kexts for free when you surely put quite some time into it.

 

Now I have a new mainboard with the new 300 coffee lake series, the Supero C7Z370-CG-L. It uses the i219 (v2) with device ID 0x15b8. Neither your 2.3.0 version nor your newest 2.4.0d0 works, unfortunately.

 

With both versions, the kext enables the NIC and recognizes when I plug in the network cable. But there is no actual connection, it does not receive an IP address via DHCP and when I configure the IP address settings manually, no connection can be established.

 

With Windows 10 on a second drive, the NIC works just fine. I tried unplugging and plugging in the cable several times. Furthermore I also tried the E1000 driver and the exact same behaviour occurs. Cable is recognized when connected, but no actual connection is established.

 

macOS autoconfigures to: 1000baseT, full-duplex, energy-efficient-ethernet, MTU Standard 1500. Playing around with those settings and reverting to 100Mbit/s does not change the behaviour.

 

Now I will try to figure out how to get the log files you asked for in your previous post about the 2.4.0d0 version and I'll write another post with the logs attached. I haven't checked them yet and I am not sure how to get them, yet.

 

Since the kext seems to respond to the device ID and macOS tries to use your kext for the NIC, I am afraid that maybe your driver just does not contain the code to run this NIC properly :( It's a very new mainboard and even though the i219v2 isn't such a new NIC, perhaps my mainboard has a new version of this NIC that isn't known yet?

 

I disabled the NIC in the UEFI, but the UEFI is a mess compared to Asus and Gigabyte, settings aren't explained at all (the user guide that comes with it does not contain them either, and that's supposed to be a professional supermicro product...) and so I am not sure if that is all done correctly. Perhaps I am missing a UEFI setting?

 

Thanks!

According to the specs, there shouldn't be any problems with this chip. Get me the kernel logs with at least one complete boot sequence and we will se what's going on.

 

Mieze

Share this post


Link to post
Share on other sites

Thank you for the quick reply. Here is the log for "log show --predicate "processID == 0" --debug"

 

The ethernet cable was plugged in from the beginning, at around time 23:24:49 I unplugged it and at around 23:25:10 I plugged it in again.

 

I will look through the log now myself, but unless it's something trivial and especially if the driver itself needs a change, I'll surely need help. Thanks for your time!

logoneboot.txt

Share this post


Link to post
Share on other sites

Thank you for the quick reply. Here is the log for "log show --predicate "processID == 0" --debug"

 

The ethernet cable was plugged in from the beginning, at around time 23:24:49 I unplugged it and at around 23:25:10 I plugged it in again.

 

I will look through the log now myself, but unless it's something trivial and especially if the driver itself needs a change, I'll surely need help. Thanks for your time!

There is no indication for a driver problem in the kernel logs. The NIC seems to work fine. Please check the network configuration as it might be messed up causing such strange behavior.

 

By the way, your ACPI data needs some attention as there are several ACPI related errors in the log file.

 

Mieze

Share this post


Link to post
Share on other sites

Thank you - I will check on the ACPI errors, I saw those too. It might be due to me simply installing a fresh system with Clover and not installing any DSDT patches or what is sometimes done afterwards since the system works just fine as it is (except for the NIC). I just intalled vanilla High Sierra with nvidia web drivers and then made it bootable with Clover, that worked on my other (older) hackintosh just fine.

 

Unfortunately there isn't anything with the network config that I can check, I use good quality managed switches and have dozens of computers in the network including the other hackintosh and several real Macs, and all work well.

 

I just tried attaching another computer NIC <-> NIC with a static IPv4 address config and tried pings, but unsuccessfully. I can try to further check with Wireshark to see what happens, but I see no DHCP discovery packet received on my pfsense firewall/router, so not even the initial DHCP packet makes it out of the NIC.

 

I agree that there are no errors related to your driver visible in the log, so it should be working just fine. But since 0 packets make it across the wire, the NIC obviously isn't working properly, for whatever reason...

Share this post


Link to post
Share on other sites

I just tried attaching another computer NIC <-> NIC with a static IPv4 address config and tried pings, but unsuccessfully. I can try to further check with Wireshark to see what happens, but I see no DHCP discovery packet received on my pfsense firewall/router, so not even the initial DHCP packet makes it out of the NIC.

 

I agree that there are no errors related to your driver visible in the log, so it should be working just fine. But since 0 packets make it across the wire, the NIC obviously isn't working properly, for whatever reason...

No, but I doubt that any packet has ever made it too the NIC. In case of a transmitter hang, the driver resets the chip so that there would be log messages indicating a chip reset every few seconds but there isn't anything like that. Please check the network statistics of the NIC and report back.

 

Mieze

Share this post


Link to post
Share on other sites

That crossover cable hasn't been required anymore for years, NICs automatically switch it over nowadays. In any case, you are correct, Mieze, there are actually dhcp discover packets reaching the pfsense firewall/router, and it responds with a dhcp offer packet in return. Then this starts over, DHCP never completes. I was checking the wrong log before, sorry about that.

 

I see a curious behaviour with a static configuration: When I ping the static IP address, the received packets count in the statistics counts up for each ping that I send. So apparently the NIC receives packets. But on the host I send the pings from, I get a timeout, so the reply packet for my ping is not being sent out.

 

To sum this up: The NIC seems to be receiving packets but not sending out packets, other than that initial request for DHCP when it's enabled. At least that describes the problem enough for searching for it on google...

Share this post


Link to post
Share on other sites

To sum this up: The NIC seems to be receiving packets but not sending out packets, other than that initial request for DHCP when it's enabled. At least that describes the problem enough for searching for it on google...

In case of a transmitter hang, the driver would reset the NIC every few seconds and unless there are those messages there is no indication for a driver bug. Looks more like a DHCP or routing problem. You might also want to try to disable EEE (select medium manually) as it sometimes causes strange things

 

Mieze

Share this post


Link to post
Share on other sites

Oh. God. I just resolved it. You were right all along, it was my networking equipment. Reason was: I installed this new hardware, needed a longer ethernet cable and thus used a different switch port to plug it in, that switch port had the VLAN set to tagged instead of untagged. While Windows was able to handle this - or rather, Windows ignored it - macOS was obviously not happy.

 

...immediately after I set that switch port from tagged to untagged, DHCP received the address and it's resolved. So now I am one of those people "my stuff is fine, i know my stuff, it can't be my stuff... oh it was my stuff..."

 

Thanks for making the time. I might not have found the issue without your hint.

Share this post


Link to post
Share on other sites

Hi Mieze,

after several weeks of using I must say there is something unusual: after wakeup my rig (the one in signature) often freezes, it happens mainly in Safari and after that only mouse is working and nothing else. And that point I have the only chance to hard reboot the machine. 

So I reverted back to v. 2.3.0 that still works with my mobo and these behaviours have almost disappeared. 

But As I cannot be sure it depends on your ethernet kext, before sending you any log or other data I kindly ask you to point me to some tutorial where I can learn how to make a diagnostic report from the console and its log files. I really know nothing about them. 

After that if I find some evidence that the problem can be truly related with your kext, I'll send the proper data to you. In the meanwhile if you have new betas to test I'd glad to give it a try. 

Thank you! 

Share this post


Link to post
Share on other sites
3 hours ago, hackaro said:

Hi Mieze,

after several weeks of using I must say there is something unusual: after wakeup my rig (the one in signature) often freezes, it happens mainly in Safari and after that only mouse is working and nothing else. And that point I have the only chance to hard reboot the machine. 

So I reverted back to v. 2.3.0 that still works with my mobo and these behaviours have almost disappeared. 

But As I cannot be sure it depends on your ethernet kext, before sending you any log or other data I kindly ask you to point me to some tutorial where I can learn how to make a diagnostic report from the console and its log files. I really know nothing about them. 

After that if I find some evidence that the problem can be truly related with your kext, I'll send the proper data to you. In the meanwhile if you have new betas to test I'd glad to give it a try. 

Thank you! 

According to the problem description I can almost rule out a driver bug. Sounds more like a messed up system (system caches, in particular as 2.3.0. doesn't exhibit this behavior) or a general wakeup issue (DSDT, etc.). Anyways, see post#1 of this thread for instructions how to collect kernel logs in case you find something contradicting my thesis.

Mieze

Share this post


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

I'm sorry but the X550 is a device with a completely different architecture. :(

Mieze

Is it possible to use the " dsdt " method. Seeking guidance:blush:

Share this post


Link to post
Share on other sites
Just now, liuhongxin1993 said:

Is it possible to use the " dsdt " method. Seeking guidance:blush:

As already stated, the X550 has a completely different architecture and can't be supported by IntelMausiEthernet. Sorry!

Mieze

Share this post


Link to post
Share on other sites
On ‎2018‎年‎4‎月‎7‎日 at 8:04 PM, Mieze said:

As already stated, the X550 has a completely different architecture and can't be supported by IntelMausiEthernet. Sorry!

Mieze

x540 driver ,Can modify it?Seek guidance。。。。。:blush::blush:

 SmallTreeIntel8259x.kext.zip

Linux:ixgbe-5.3.6.tar.zip

https://www.small-tree.com/support/download_category?cat_id=6

Adding 10 gigabit ethernet networking to your hackintosh is now extremely easy. You simply need to add these three kexts to your EFI/CLOVER/KEXTS/OTHER folder and you will have a working card! This method works so far on the following cards:

Supported devices for SmallTreeIntel8254x.kext:

  • 8086:1010 82546EB Gigabit Ethernet Controller (Copper)
  • 8086:1011 82545EM Gigabit Ethernet Controller (Fiber)
  • 8086:1012 82546EB Gigabit Ethernet Controller (Fiber)
  • 8086:101d 82546EB Gigabit Ethernet Controller
  • 8086:1026 82545GM Gigabit Ethernet Controller
  • 8086:1027 82545GM Gigabit Ethernet Controller
  • 8086:1028 82545GM Gigabit Ethernet Controller
  • 8086:105e 82571EB Gigabit Ethernet Controller (Also covered by AppleIntel8254XEthernet.kext)
  • 8086:105f 82571EB Gigabit Ethernet Controller
  • 8086:1079 82546GB Gigabit Ethernet Controller
  • 8086:107a 82546GB Gigabit Ethernet Controller
  • 8086:107b 82546GB Gigabit Ethernet Controller
  • 8086:107c 82541PI Gigabit Ethernet Controller
  • 8086:107d 82572EI Gigabit Ethernet Controller (Copper)
  • 8086:107e 82572EI Gigabit Ethernet Controller (Fiber)
  • 8086:10a4 82571EB Gigabit Ethernet Controller
  • 8086:10b5 82546GB Gigabit Ethernet Controller (Copper)
  • 8086:10b9 82572EI Gigabit Ethernet Controller (Copper)
  • 8086:10bc 82571EB Gigabit Ethernet Controller (Copper)

SmallTreeIntel82576.kext:

  • 8086:1521 I350 Gigabit Network Connection
  • 8086:1522 I350 Gigabit Fiber Network Connection
  • 8086:1533 I210 Gigabit Network Connection (Also covered by AppleIntelI210Ethernet.kext)

SmallTreeIntel8259x.kext:

  • 8086:10c6 82598EB 10-Gigabit AF Dual Port Network Connection
  • 8086:10c7 82598EB 10-Gigabit AF Network Connection
  • 8086:10c8 82598EB 10-Gigabit AT Network Connection
  • 8086:10ec 82598EB 10-Gigabit AT CX4 Network Connection
  • 8086:10d8 82599EB 10 Gigabit Network Connection
  • 8086:10fb 82599ES 10-Gigabit SFI/SFP+ Network Connection
  • 8086:10f1 82598EB 10-Gigabit AF Dual Port Network Connection
  • 8086:151c 82599 10 Gigabit TN Network Connection
  • 8086:150b 82598EB 10-Gigabit AT2 Server Adapter
  • 8086:1528 Ethernet Controller 10-Gigabit X540-AT2
  • 8086:10fc 82599 10 Gigabit Dual Port Network Connection
  • 8086:1560 Ethernet Controller X540

Share this post


Link to post
Share on other sites

@liuhongxin1993: This is off-topic. Please create a new thread in order to keep this one focused on IntelMausiEthernet.

Share this post


Link to post
Share on other sites

Hello,

The new B360 motherboard now uses the new Intel I219-V with Device ID 8086_15BC. I tried adding the Device ID to the current 2.3.0 release but as expected, it wouldn't work. Would you mind take a look at it ?

Edited by vusun123

Share this post


Link to post
Share on other sites
2 hours ago, vusun123 said:

Hello,

The new B360 motherboard now uses the new Intel I219-V with Device ID 8086_15BC. I tried adding the Device ID to the current 2.3.0 release but as expected, it wouldn't work. Would you mind take a look at it ?

Try version 2.4.0d0 which can be found here in this thread because it already supports this chip.

Mieze

Share this post


Link to post
Share on other sites

Here is a new development version of the driver (2.4.0d2) which changes interaction with the ME during sleep/wake and cable plug cycles in order to resolve problems with LM chips which support AMT. All users are encouraged to test it thoroughly, in particular those with LM versions of the supported NICs. Tests should focus on sleep/wake and cable plug/unplug events.

Good luck!

Mieze :cat:

IntelMausiEthernet-V2.4.0d2.zip

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

  • Similar Content

    • By sierra2600
      The laptop in question: Acer TravelMate 8472 TM8472 (Model: ZQ3) (refer to the "Spoiler" at the end if you want the machine specs)
       
      "So what are you bugging us for?" Good question, because I am usually an introvert and usually just keep looking for answers but I could not find some. Jumping to it...
      What does not work and I would like thoughts on:
      Bluetooth does not register, used to on previous installs (sorry, I did not pay attention to see if this was caused by me updating to 10.8.5 but that was necessary for the below functions) (It does not work in Debian either - Ignore) LAN and WLAN  - I have found Kexts (somewhere, I think I just lost them... dang it...) for the WLAN but I have yet to try them, nothing for the LAN I know this is cheating but I read that The NDISulator for FreeBSD (HINT HINT) is a port of NDISwrapper for Linux that runs Windows XP network drivers in Linux or BSD Brightness controls work from the middle down on the "Sun" brightness overlay, I got this far from following this: https://www.insanelymac.com/forum/topic/287133-guide-backlight-brightness-for-intel-80860046-1st-gen-hd-gma-5700mhd/ but I am kind of thinking of trying: https://www.insanelymac.com/forum/topic/287133-guide-backlight-brightness-for-intel-80860046-1st-gen-hd-gma-5700mhd/?do=findComment&comment=2214344 . My "magic number" is: 0xF        I used DSDTEditor in Windows, since I figured all the drivers are loaded, to extract the DSDT and compile something that somewhat works... Wake from sleep issue - I tried the above guide for that but I get a no backlit display and I can see that the cursor in the password field is not flashing when I use an external light source, but it will reboot when I press Ctrl + Alt + Power "button" (it is actually a slider) and then also clear my freaking CMOS right down to the clock... yeah I have the ACPI fix implmented and it usually works... DVD Player.app reports that no viable video device was found (personally I don't care about the DVD Player.app problem, just wanted to put that out there for the heck of it) The microphone port always sounds like it is going through a [dirty] guitar effects petal no matter what sliders are adjusted  
      Likely causes of:
      Bluetooth (BCM92046), WIFI (BCM943225HM) - So, I USED TO be able to turn on the WIFI from within Windows then reboot into Mac OS and have it work but I noticed recently that the indicator light for them turns off BEFORE it reboots now. When Windows or Android load, it lights up- "No... really, captain obvious?!"... anyways... working "No really Sherlock!" so OBVIOUSLY, the OS has to activate them... and preferably ignore the wireless switching button For the WIFI module, if you omit the 9 and HM in a search, results appear! Brightness - Will get reset to full "Bright light! Bright light!" when a "Load System Defaults" is applied from within the BIOS settings but like the WIFI and Bluetooth the OS will forcefully take control of it Microphone In sounding dirty - me being lazy with the audio drivers LAN (BCM57760) - I dunno...  when I search it, nothing comes up...  
      "How did you get this far?"
      Update the BIOS, this is oh so very important (refer to the battery section of the "Spoiler" for the reson) PLEASE BACKUP YOUR BIOS FIRST! PLUG THE MACHINE INTO THE AC ADAPTER/CHARGER! DO NOT FORCE THE COMPUTER TO SHUTDOWN NOR REMOVE THE BATTERY NOR UNPLUG IT FROM THE AC ADAPTER/CHARGER WHILE IT IS UPDATING! I WILL NOT BE HELD LIABLE FOR BRICKED MACHINES! So it will boot off of the (Niresh) Mac OS X 10.8 with no changes to anything "Awesome" but you may still need at least a USB mouse "Aww" If you have the option to remove the display drivers/kexts otherwise it will not to boot or not display If you forgot this, breathe "You think that's air your breathing?"... anyways... during the bootloader, go into single user mode [ -s ] and follow the on screen instructions to allow for modifying the files. You will want to PREFERABLY create a folder where Mac OS cannot read them and move the IntelHDGraphics Kexts into it You are likely going to need an external USB keyboard as well now that it is installed Now install the described Kexts in the "Spoiler" associated with the hardware to get more functionality and loose the USB HICs  
      Any help pertaining to the Bluetooth, WIFI, LAN, bizarre brightness and wake after sleep backlit display issue would be wonderful... Thank you for your time and I hope that I helped anyone else out with some of their own issues pertaining to the Acer TravelMate 8472 TM8472 ZQ3 no nVidia with i5 laptop...
      (Attached are non-modified extracted DSDT DSL and AML files "with errors according to DSDTEditor" for reference of the machine with a Phoenix BIOS version of 1.28 (07/20/2011))
      dsdt.aml
      dsdt.dsl
       
       
    • By MaLd0n
      --Donations via PayPal--
      https://tinyurl.com/r2bvzm7
       
      --Original Topic--
      https://www.olarila.com/topic/6874-olarila-hackbook-lenovo-ideapad-s145-mojave-catalina-full-dsdt-patches/
       

       
      -Perfect HackBook, HDMI Audio/Video, Bluetooth, AirPlay, Sleep, Lid Sleep, Auto Sleep, Audio, etc!
      -Wifi card has been replaced with Dell DW1560!
      -I'm using a S145-15IWL Model with Intel Core i5 8265u / Intel UHD Graphics 620
      -Update bios/uefi to last version
       
      --Installation--
      https://www.olarila.com/topic/5794-guide-install-macos-with-olarila-image-step-by-step-install-and-post-install-windows-or-mac/
       
      --Clover Folder--
      Just paste EFI folder inside EFI partition
      https://www.olarila.com/files/Clover.Folder/Lenovo IdeaPad S145.zip
      Notebooks with ELAN trackpad use it with my folder above
      IdeaPad S145 ELAN.zip
       
      Bluetooth Broadcom
      Bluetooth Broadcom.zip
       
      CPUFriend for i5-8265U
      CPUFriend i5-8265U.zip
       
      --Full DSDT Patches--
      -My DSDT
      DSDT Lenovo IdeaPad S145.zip
       
      This DSDT work on S145-14IWL, S145-15IWL, V14-IWL, V15-IWL models
      -Patches
      -FIX ERRORS AND WARNINGS -REMOVE UNUSED SCOPES / DEVICES -HIGH PRECISION EVENT TIMER -SATA SERIE 11 ID -DMAC -REMOVE LINES, PROBLEMATIC and UNUSED -SLPB -DARWIN / WINDOWS 2015 -XHCI -PLUGIN TYPE -HDAS to HDEF -HDEF -REAL TIME CLOCK -ARTC -IRQs -SBUS -BUS1 -MCHC -ALS0 -SHUTDOWN -FWHD -USBX -PMCR -PPMC -XSPI -GMM -IMEI -EC -PRWs -_DSMs -PNLF -BRIGHTNESS KEYS -I2C -NATIVE USB -ARPT -GFX0 -DTGP -kUSBCompanionIndex -io-device-location -FULL RENAMED DEVICES   --IGPU Patch--
      Video solution with HDMI Audio and Video
      <key>PciRoot(0x0)/Pci(0x2,0x0)</key> <dict> <key>AAPL,GfxYTile</key> <data> AQAAAA== </data> <key>AAPL,ig-platform-id</key> <data> CQClPg== </data> <key>device-id</key> <data> pT4AAA== </data> <key>enable-hdmi20</key> <data> AQAAAA== </data> <key>framebuffer-con0-alldata</key> <data> AAAIAAIAAACYAAAA </data> <key>framebuffer-con0-enable</key> <integer>1</integer> <key>framebuffer-con1-alldata</key> <data> AQEJAAAIAADHAQAA </data> <key>framebuffer-con1-enable</key> <integer>1</integer> <key>framebuffer-con2-alldata</key> <data> AgYKAAAEAADHAQAA </data> <key>framebuffer-con2-enable</key> <integer>1</integer> <key>framebuffer-fbmem</key> <data> AACQAA== </data> <key>framebuffer-patch-enable</key> <data> AQAAAA== </data> <key>framebuffer-stolenmem</key> <data> AAAwAQ== </data> <key>framebuffer-unifiedmem</key> <data> AAAAgA== </data> <key>hda-gfx</key> <string>onboard-1</string> <key>model</key> <string>Intel Corporation, Cannon Point-LP Iris Plus Graphics 655</string> </dict>   --Native USB Fix for Notebooks - No Injector/Kext Required--
      https://www.olarila.com/topic/6878-guide-native-usb-fix-for-notebooks-no-injectorkext-required/
      https://www.olarila.com/topic/6181-guide-native-usb-fix-for-desktops-no-injectorkext-required-skylake/
       
       
      -ScreenShots

































      -Links
       
       
      Clover https://github.com/CloverHackyColor/CloverBootloader
      AirportBrcmFixup.kext https://github.com/acidanthera/AirportBrcmFixup
      AppleALC.kext https://github.com/acidanthera/AppleALC
      Brcm Bluetooth https://github.com/acidanthera/BrcmPatchRAM
      Lilu.kext https://github.com/acidanthera/Lilu
      SystemProfilerMemoryFixup.kext https://github.com/Goldfish64/SystemProfilerMemoryFixup
      VirtualSMC.kext https://github.com/acidanthera/VirtualSMC
      VoodooI2C.kext https://github.com/alexandred/VoodooI2C
      VoodooPS2Controller.kext https://github.com/acidanthera/VoodooPS2
      WhateverGreen.kext https://github.com/acidanthera/WhateverGreen
      MaciASL - https://github.com/acidanthera/MaciASL
      acpica - https://github.com/acpica/acpica
      AptioMemoryFix.efi https://github.com/acidanthera/AptioFixPkg
      ApfsDriverLoader.efi https://github.com/acidanthera/AppleSupportPkg
      HFSPlus.efi https://github.com/JrCs/CloverGrowerPro/blob/master/Files/HFSPlus/X64/HFSPlus.efi?raw=true
      Hackintool https://github.com/headkaze/Hackintool
       
      -Credits and thanks to the old and new people in the community who developed patches, kexts and bootloaders!
       
      Slice, Kabyl, usr-sse2, jadran, Blackosx, dmazar, STLVNUB, pcj, apianti, JrCs, pene, FrodoKenny, skoczy, ycr.ru, Oscar09, xsmile, SoThOr, RehabMan, Download-Fritz, Zenit432, cecekpawon, Intel, Apple, Oracle, Chameleon Team, crazybirdy, Mieze, Mirone, Oldnapalm, netkas, Elconiglio, artut-pt, ErmaC, Pavo, Toleda, Master Chief and family, bcc9, The King, PMheart, Sherlocks, Micky1979, vit9696, vandroiy2013, Voodoo Team, Pike R. Alpha, lvs1974, Austere.J, CVad, Sampath007, onemanosx, erroruser, Jenny David, Olarila Facebook Community, Hackintosh Facebook Community and many others!
       
      We're all here to have fun and learn from each other!
    • 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: https://www.insanelymac.com/forum/files/file/88-realtekrtl8111-binary/  
      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 MaLd0n
      Now have a Olarila app, just download app and clover folder for your Chipset! https://www.olarila.com/topic/5165-olarila-app-images-and-folders/   Install MacOS with Olarila Image, Step by Step, Install and Post Install
      https://www.olarila.com/topic/5794-guide-install-macos-with-olarila-image-step-by-step-install-and-post-install-windows-or-mac/
        First... If you need DSDT edits... -Extract tables with F4 key in Clover boot screen! -Run it and send me files! RunMe.app   Installation --Create a bootable copy of El Capitan /  Sierra / High Sierra / Mojave https://github.com/chris1111/Create-Install-Media/releases   --Install Clover in USB stick https://github.com/CloverHackyColor/CloverBootloader/releases   --Replace with my Clover folder https://www.olarila.com/topic/5676-clover-folder-for-all-chipsets/   --Install EL Capitan / Sierra / High Sierra and boot into system!     Post Installation   --Install Clover and replace with my folder   https://www.olarila.com/topic/5676-clover-folder-for-all-chipsets/     --Reboot and activate video!   Bingo! Now you need a fine tune! DSDT Time!   My DSDT GA P35-DS3   DSDT.MaLd0n.zip     Patches -FIX ERRORS AND WARNINGS -HPET -SATA -SLPB -DARWIN -LPC -HDEF -RTC -EHCI -UHCI -IRQs -SBUS -BUS1 -MCHC -ALS0 -SHUTDOWN -LAN -EC -PNLF --Native Power Management
       
      Use Clover, check Generate P and C States
       
      --Brightness
      Install .app, select the required permission and reboot. Work in F1 / F2 keys!
      NativeDisplayBrightness.app.zip


      https://github.com/Bensge/NativeDisplayBrightness/releases
      *in some cases .app don't work, check patches in config.plist inside Clover folder Post Install
       
      --AUDIO
       
      Device HDEF + AppleAlc + Lilu
       
      --install Lan driver by Mieze
        -Atheros   http://www.insanelymac.com/forum/files/file/313-atherose2200ethernet/   -Intel   http://www.insanelymac.com/forum/files/file/396-intelmausiethernet/   -Realtek   http://www.insanelymac.com/forum/files/file/88-realtekrtl8111-binary/   --Links   -FakeSMC   https://bitbucket.org/RehabMan/os-x-fakesmc-kozlek   -Audio   https://github.com/vit9696/AppleALC http://www.insanelymac.com/forum/topic/293863-applehda-patch-requests/   -Credits and thanks to the old and new people in the community who developed patches, kexts and bootloaders!   Slice, Kabyl, usr-sse2, jadran, Blackosx, dmazar, STLVNUB, pcj, apianti, JrCs, pene, FrodoKenny, skoczy, ycr.ru, Oscar09, xsmile, SoThOr, RehabMan, Download-Fritz, Zenit432, cecekpawon, Intel, Apple, Oracle, Chameleon Team, crazybirdy, Mieze, Mirone, Oldnapalm, netkas, Elconiglio, artut-pt, ErmaC, Pavo, Toleda, Master Chief and family, bcc9, The King, PMheart, Sherlocks, Micky1979, vit9696, vandroiy2013, Voodoo Team, Pike R. Alpha, lvs1974, Austere.J, CVad and many, many, many others!   We're all here to have fun and learn from each other!   ENJOY!  
×