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

IntelMausiEthernet.kext for Intel onboard LAN

973 posts in this topic

Recommended Posts

I must say, I'm impressed. Smaller, has not given me a single glitch so far, extremely fast, first driver to allow me to reach 106MB/s on a Gb ethernet card, from hack 1 to hack 2, both with Mausi.

 

Mieze, I've been following the idea of this driver for a very long time, and now that it is here, I can't thank you enough!

 

Super Kudos!

Share this post


Link to post
Share on other sites
Advertisement

Followed first page instructions, but add me to the +1 who got instant KP unless I deleted these files first:

 

/Library/Preferences/SystemConfiguration/NetworkInterfaces.plist

/Library/Preferences/SystemConfiguration/preferences.plist

 

Without that, kept asking for ionetworking iopci dependancies.

 

Probably should add to the first page. would have saved me a day troubleshooting, as even though I read through the topic here. It doesn't explicitly say this until now.

 

Thanks for this awesome work BTW.

Share this post


Link to post
Share on other sites

Followed first page instructions, but add me to the +1 who got instant KP unless I deleted these files first:

 

/Library/Preferences/SystemConfiguration/NetworkInterfaces.plist

/Library/Preferences/SystemConfiguration/preferences.plist

 

Without that, kept asking for ionetworking iopci dependancies.

 

Probably should add to the first page. would have saved me a day troubleshooting, as even though I read through the topic here. It doesn't explicitly say this until now.

 

Done!

Share this post


Link to post
Share on other sites

Working fine here too

Asus Maximus VI Gene ( Z87 ) + Intel I217V

 

PS: Does anybody know why my System Profiler doesn't show the Kext loaded and it's version like anybody else? :blush:

post-202089-0-51627500-1431002405_thumb.png

post-202089-0-21376500-1431002416_thumb.png

Share this post


Link to post
Share on other sites

Working fine here too

Asus Maximus VI Gene ( Z87 ) + Intel I217V

 

PS: Does anybody know why my System Profiler doesn't show the Kext loaded and it's version like anybody else? :blush:

I'll check next time I boot under OSX, but it seems to have seen the same thing on my setup...

Share this post


Link to post
Share on other sites

PS: Does anybody know why my System Profiler doesn't show the Kext loaded and it's version like anybody else? :blush:

 

Are you injecting the kext with Clover?

 

Mieze

Share this post


Link to post
Share on other sites
 
 

 

Are you injecting the kext with Clover?

 

Mieze

Yup, with Clover.

 

It won't show if you're injecting it from EFI or BIOS. Only if it's in /S/L/E.

Ahhh, OK, didn't knew that.

Share this post


Link to post
Share on other sites

It won't show if you're injecting it from EFI or BIOS. Only if it's in /S/L/E.

Thanks for the info.

 

I have the kext in /S/L/E/ and indeed I've got this :

5fc1a5f7753ed99da15ee89d4c7c7ba65277451a

Share this post


Link to post
Share on other sites

If you want to know why, check the system log. You'll find this line:

 

"Kext com.insanelymac.IntelMausiEthernet not found for client path request."

 

Basically it can't find the kext post-boot because it was injected by the bootloader. So it can't read the path or version number.

Share this post


Link to post
Share on other sites
 
 

 

If you want to know why, check the system log. You'll find this line:

 

"Kext com.insanelymac.IntelMausiEthernet not found for client path request."

 

Basically it can't find the kext post-boot because it was injected by the bootloader. So it can't read the path or version number.

 

Thanks for the detailed information.

Share this post


Link to post
Share on other sites

Mieze - thanks for all the work on the driver. Was having issues with intel ethernet stalling out during large file transfers or file sharing. Installed v2.0.0. and so far seems to be working well with the I217V I have on board

Share this post


Link to post
Share on other sites

Please, can anybody do a 10.8+ build of this driver and upload it? I have issues downloading Xcode from AppStore... Would be nice, thank you!

 

 

And Mieze, big big thanks for this slim and fast driver so far!  Keep on doing your great projects!

Share this post


Link to post
Share on other sites

Please, can anybody do a 10.8+ build of this driver and upload it? I have issues downloading Xcode from AppStore... Would be nice, thank you!

 

Please see post #1 of this thread. I added instructions to built the driver for 10.8 at the end of the post. This should resolve your issue.

 

Mieze

Share this post


Link to post
Share on other sites

Please see post #1 of this thread. I added instructions to built the driver for 10.8 at the end of the post. This should resolve your issue.

 

Mieze

 

How to build it to be compatible with 10.8 and 10.9 at the same time?

Share this post


Link to post
Share on other sites

How to build it to be compatible with 10.8 and 10.9 at the same time?

 

Following the instructions you will produce a binary which is compatible with 10.8 and above.

 

Mieze

Share this post


Link to post
Share on other sites

Hi,

 

First off, great work, and sorry to nag about what is probably a niche use case. I'm having problems with bonding the interface driven by the Mausi driver and that of the other Intel NIC on my board.

 

OS X 10.10.3

Clover EFI-only

Motherboard: Asus Z97-WS

 

NICs and drivers in use:

I218-LM: IntelMausiEthernet 2.0.0

I210-AT: AppleIntelI210 (Vanilla, 2.2.0b1)

 

The driver works perfectly until I try and create a bond (link aggregation) with the two NICs. There's almost no connectivity at all. I can ping things, but web pages fail to even begin loading 90% of the time. Some connections succeed so I'm going to make the assumption that those which are made over the I218 are failing whilst the few which go out on the I210 succeed.

 

I had a spare Intel Gigabit CT card (82574L chipset) so I put this in and created the bond with this and the I210 and it worked flawlessly, so I guess I've narrowed the problem down to the Mausi driver.

 

It's probably also worth noting that I had no problem bonding these two NICs under Windows.

 

Find a copy of the kernel messages with the debug kext and bonding turned on here: http://pastebin.com/tcGZ1tDp

Share this post


Link to post
Share on other sites

The driver works perfectly until I try and create a bond (link aggregation) with the two NICs. There's almost no connectivity at all. I can ping things, but web pages fail to even begin loading 90% of the time. Some connections succeed so I'm going to make the assumption that those which are made over the I218 are failing whilst the few which go out on the I210 succeed.

 

Link aggregation works fine with the driver as long as all drivers in the bond support the same hardware offload features which is not the case in your configuration because the Apple provided drivers don't support TSO but Audio Video Bridging.

/var/log/system.log:Jun 10 11:33:12 Beast kernel[0]: bond_add_interface(bond0, en0)  hwassist values don't match 0x710067 != 0x10006, using 0x10006 instead

You might want to combine it with an Atheros NIC using AtherosE2200Ethernet or a Realtek RTL8111E based card (avoid the old RTL8111B) with my RealtekRTL8111 driver which support the same offload features as IntelMausiEthernet.

 

Mieze

Share this post


Link to post
Share on other sites

Does WOL work with this kext by any chance? Thanks!

 

Yes, it works. In case you are having trouble check your BIOS settings over and over again until the issue is resolved.

 

Mieze

Share this post


Link to post
Share on other sites

So we met again lol ok so the issue is your kext in 10.11 beta 2 has a huge issue where the net slows from 100 download 90 upload to 36/kb's download and 1 kb/s upload speed after 32 hours so can you maybe update your kext for 10.11 please thanks and all hail the cat gods!!!!

 

 

update: when i turn off itunes 12.2 the net speed goes back to normal seems to be a issues with your kext and the new itunes 12.2 with apple music 

Share this post


Link to post
Share on other sites

So we met again lol ok so the issue is your kext in 10.11 beta 2 has a huge issue where the net slows from 100 download 90 upload to 36/kb's download and 1 kb/s upload speed after 32 hours so can you maybe update your kext for 10.11 please thanks and all hail the cat gods!!!!

 

 

update: when i turn off itunes 12.2 the net speed goes back to normal seems to be a issues with your kext and the new itunes 12.2 with apple music 

 

There is no need for an update because this is not a driver issue. A driver handles packets on behalf of the network stack, nothing more and nothing less. It doesn't care where they are coming from or where they are going to and it never gets in touch with an application directly. If there is a problem with a specific service or application, search somewhere else because a driver error can be ruled out.

 

Mieze

Share this post


Link to post
Share on other sites

Following the instructions you will produce a binary which is compatible with 10.8 and above.

 

Mieze

Hi Mieze

 

can you help me please, i build your kext for 10.8 following yours instructions in the first page but neither v1 nor v2 loads.

 

here is the kernel log output concerning the kext. I can send you full kernel log if you want.

Jul 10 15:57:27 localhost kernel[0]: kxld[com.insanelymac.IntelMausiEthernet]: The super class vtable '__ZTV20IOEthernetController' for vtable '__ZTV10IntelMausi' is out of date. Make sure your kext has been built against the correct headers.
Jul 10 15:57:27 localhost kernel[0]: Can't load kext com.insanelymac.IntelMausiEthernet - link failed.
Jul 10 15:57:27 localhost kernel[0]: Failed to load executable for kext com.insanelymac.IntelMausiEthernet.
Jul 10 15:57:27 localhost kernel[0]: Kext com.insanelymac.IntelMausiEthernet failed to load (0xdc008016).
Jul 10 15:57:27 localhost kernel[0]: Failed to load kext com.insanelymac.IntelMausiEthernet (error 0xdc008016).
Jul 10 15:57:27 localhost kernel[0]: Couldn't alloc class "IntelMausi"
Jul 10 15:57:27 localhost kernel[0]: mbinit: done [96 MB total pool size, (64/32) split]
Jul 10 15:57:27 localhost kernel[0]: Pthread support ABORTS when sync kernel primitives misused

I am trying to make it work since yesterday. My machine is running the latest release of Mountain Lion.

 

Thank You

Share this post


Link to post
Share on other sites

Hi Mieze

 

can you help me please, i build your kext for 10.8 following yours instructions in the first page but neither v1 nor v2 loads.

 

I'm aware of the fact that building version 2.0.0 for ML results in a broken executable. I assume that the header files I took from the IONetworking.kext's source code of Yosemite are responsible for this error but I haven't found time to resolve it.

 

Nevertheless I verified that it is possible to built version 1.0.0 for ML provided you use Xcode 5.1.1 and set both the Base SDK and the Deployment Target to 10.8. Most likely you failed to select the correct Base SDK and/or Deployment Target. Please see my results:

mausi:Desktop laura$ kextstat
Index Refs Address            Size       Wired      Name (Version) <Linked Against>
    1   69 0xffffff7f80757000 0x686c     0x686c     com.apple.kpi.bsd (12.6.0)
    2    6 0xffffff7f80742000 0x46c      0x46c      com.apple.kpi.dsep (12.6.0)
    3   97 0xffffff7f80761000 0x1b7ec    0x1b7ec    com.apple.kpi.iokit (12.6.0)
    4  102 0xffffff7f8074d000 0x99f8     0x99f8     com.apple.kpi.libkern (12.6.0)
    5   88 0xffffff7f80743000 0x88c      0x88c      com.apple.kpi.mach (12.6.0)
    6   38 0xffffff7f80744000 0x502c     0x502c     com.apple.kpi.private (12.6.0)
    7   55 0xffffff7f8074a000 0x23cc     0x23cc     com.apple.kpi.unsupported (12.6.0)
    8    0 0xffffff7f81450000 0x41000    0x41000    com.apple.kec.corecrypto (1.0) <7 6 5 4 3 1>
    9   24 0xffffff7f80d0e000 0x9000     0x9000     com.apple.iokit.IOACPIFamily (1.4) <7 6 4 3>
   10   32 0xffffff7f80851000 0x29000    0x29000    com.apple.iokit.IOPCIFamily (2.8) <7 6 5 4 3>
   11    2 0xffffff7f81de6000 0x5a000    0x5a000    com.apple.driver.AppleACPIPlatform (1.8) <10 9 7 6 5 4 3 1>
   12    1 0xffffff7f80a6e000 0xe000     0xe000     com.apple.driver.AppleKeyStore (28.21) <7 6 5 4 3 1>
   13    4 0xffffff7f8077d000 0x25000    0x25000    com.apple.iokit.IOStorageFamily (1.8) <7 6 5 4 3 1>
   14    0 0xffffff7f80dfb000 0x19000    0x19000    com.apple.driver.DiskImages (346) <13 7 6 5 4 3 1>
   15    0 0xffffff7f81ae0000 0x2e000    0x2e000    com.apple.driver.AppleIntelCPUPowerManagement (214.0.0) <7 6 5 4 3 1>
   16    0 0xffffff7f8075e000 0x3000     0x3000     com.apple.security.TMSafetyNet (7) <7 6 5 4 2 1>
   17    2 0xffffff7f807f3000 0x4000     0x4000     com.apple.kext.AppleMatch (1.0.0d1) <4 1>
   18    1 0xffffff7f807f7000 0x11000    0x11000    com.apple.security.sandbox (220.4) <17 7 6 5 4 3 2 1>
   19    0 0xffffff7f80808000 0x6000     0x6000     com.apple.security.quarantine (2.1) <18 17 7 6 5 4 2 1>
   20    0 0xffffff7f81e57000 0x8000     0x8000     com.apple.nke.applicationfirewall (4.0.39) <7 6 5 4 3 1>
   21    0 0xffffff7f81adb000 0x3000     0x3000     com.apple.driver.AppleIntelCPUPowerManagementClient (214.0.0) <7 6 5 4 3 1>
   22    0 0xffffff7f81dba000 0x3000     0x3000     com.apple.driver.AppleAPIC (1.7) <4 3>
   23    2 0xffffff7f80c9f000 0x4000     0x4000     com.apple.iokit.IOSMBusFamily (1.1) <5 4 3>
   24    0 0xffffff7f81e46000 0x7000     0x7000     com.apple.driver.AppleACPIEC (1.8) <23 11 9 5 4 3>
   25    0 0xffffff7f81911000 0x4000     0x4000     com.apple.driver.AppleSMBIOS (1.9) <7 4 3>
   26    0 0xffffff7f81b39000 0x3000     0x3000     com.apple.driver.AppleHPET (1.8) <9 7 5 4 3>
   27    9 0xffffff7f80a7c000 0x6d000    0x6d000    com.apple.iokit.IOHIDFamily (1.8.1) <12 7 6 5 4 3 2 1>
   28    0 0xffffff7f81e50000 0x4000     0x4000     com.apple.driver.AppleACPIButtons (1.8) <27 11 9 7 6 5 4 3 1>
   29    0 0xffffff7f8193d000 0x8000     0x8000     com.apple.driver.AppleRTC (1.5) <9 5 4 3 1>
   30    1 0xffffff7f81d95000 0x5000     0x5000     com.apple.driver.AppleEFIRuntime (2.0) <7 6 5 4 3>
   31    0 0xffffff7f81d9a000 0xa000     0xa000     com.apple.driver.AppleEFINVRAM (2.0) <30 7 6 5 4 3>
   32   10 0xffffff7f809ed000 0x5e000    0x5e000    com.apple.iokit.IOUSBFamily (635.4.0) <10 7 5 4 3 1>
   33    0 0xffffff7f80b86000 0x18000    0x18000    com.apple.driver.AppleUSBEHCI (621.4.6) <32 10 7 5 4 3 1>
   35    2 0xffffff7f80fe0000 0x16000    0x16000    com.apple.iokit.IOAHCIFamily (2.5.1) <5 4 3 1>
   36    0 0xffffff7f81dbf000 0x1a000    0x1a000    com.apple.driver.AppleAHCIPort (2.6.6) <35 10 5 4 3 1>
   37    7 0xffffff7f809ae000 0x2b000    0x2b000    com.apple.iokit.IONetworkingFamily (3.0) <7 6 5 4 3 1>
   38    1 0xffffff7f8102a000 0x68000    0x68000    com.apple.iokit.IO80211Family (530.5) <37 7 6 5 4 3 1>
   39    0 0xffffff7f81099000 0x1f9000   0x1f9000   com.apple.driver.AirPort.Brcm4331 (615.20.17) <38 37 10 7 5 4 3 1>
   40    0 0xffffff7f81924000 0x12000    0x12000    com.apple.driver.AppleSDXC (1.4.3) <13 10 5 4 3 1>
   41    1 0xffffff7f80d62000 0x7000     0x7000     com.apple.iokit.IOEthernetAVBController (1.0.2b1) <37 5 4 3 1>
   42    0 0xffffff7f80d69000 0x38000    0x38000    com.apple.iokit.AppleBCM5701Ethernet (3.6.2b4) <41 37 10 9 5 4 3 1>
   43    5 0xffffff7f80bb6000 0xbb000    0xbb000    com.apple.iokit.IOThunderboltFamily (2.7.7) <5 4 3 1>
   44    0 0xffffff7f81857000 0x16000    0x16000    com.apple.driver.AppleThunderboltNHI (1.9.2) <43 10 9 5 4 3 1>
   45    2 0xffffff7f808ef000 0x73000    0x73000    com.apple.iokit.IOFireWireFamily (4.5.5) <5 4 3 1>
   46    0 0xffffff7f80e56000 0x27000    0x27000    com.apple.driver.AppleFWOHCI (4.9.9) <45 10 7 6 5 4 3 1>
   47    0 0xffffff7f80a6b000 0x3000     0x3000     com.apple.iokit.IOUSBUserClient (630.4.4) <32 7 5 4 3 1>
   48    0 0xffffff7f81006000 0x17000    0x17000    com.apple.iokit.IOAHCIBlockStorage (2.3.5) <35 13 6 5 4 3 1>
   49    0 0xffffff7f80b6a000 0x15000    0x15000    com.apple.driver.AppleUSBHub (635.4.0) <32 5 4 3 1>
   50    0 0xffffff7f8178e000 0x3000     0x3000     com.apple.driver.XsanFilter (404) <13 5 4 3 1>
   51    0 0xffffff7f814a0000 0x9000     0x9000     com.apple.BootCache (34) <7 6 5 4 3 1>
   52    0 0xffffff7f81d86000 0x4000     0x4000     com.apple.AppleFSCompression.AppleFSCompressionTypeZlib (1.0.0d1) <6 4 3 2 1>
   53    0 0xffffff7f81d8c000 0x3000     0x3000     com.apple.AppleFSCompression.AppleFSCompressionTypeDataless (1.0.0d1) <7 6 4 3 2 1>
   55    1 0xffffff7f80b05000 0x7000     0x7000     com.apple.driver.AppleUSBComposite (621.4.0) <32 4 3 1>
   56    1 0xffffff7f80afc000 0x9000     0x9000     com.apple.iokit.IOUSBHIDDriver (623.4.0) <32 27 5 4 3 1>
   57    0 0xffffff7f819e6000 0x4000     0x4000     com.apple.driver.AppleIRController (320.15) <56 32 27 5 4 3>
   58    0 0xffffff7f80b63000 0x7000     0x7000     com.apple.driver.AppleUSBMergeNub (621.4.6) <55 32 4 3 1>
   59    0 0xffffff7f81849000 0x5000     0x5000     com.apple.driver.AppleThunderboltPCIDownAdapter (1.3.2) <43 10 5 4 3>
   60    2 0xffffff7f81871000 0x9000     0x9000     com.apple.driver.AppleThunderboltDPAdapterFamily (2.5.0) <43 10 9 5 4 3>
   61    1 0xffffff7f8187a000 0x6000     0x6000     com.apple.driver.AppleThunderboltDPInAdapter (2.5.0) <60 43 10 9 5 4 3>
   62    0 0xffffff7f81880000 0xb000     0xb000     com.apple.driver.AppleThunderboltDPOutAdapter (2.5.0) <61 60 43 10 9 5 4 3>
   63   11 0xffffff7f80da4000 0x38000    0x38000    com.apple.iokit.IOGraphicsFamily (2.3.7) <10 7 5 4 3>
   64    0 0xffffff7f819ed000 0x2e000    0x2e000    com.apple.driver.AppleIntelSNBGraphicsFB (8.1.6) <63 10 9 7 6 5 4 3 1>
   65    5 0xffffff7f80de7000 0x12000    0x12000    com.apple.iokit.IONDRVSupport (2.3.7) <63 10 7 5 4 3>
   66    0 0xffffff7f81a53000 0x62000    0x62000    com.apple.driver.AppleIntelHD3000Graphics (8.1.6) <65 63 10 7 5 4 3 1>
   67    5 0xffffff7f80d17000 0xa000     0xa000     com.apple.driver.IOPlatformPluginFamily (5.4.1d13) <9 7 6 5 4 3>
   68    1 0xffffff7f80d26000 0x12000    0x12000    com.apple.driver.IOPlatformPluginLegacy (1.0.0) <67 9 7 6 5 4 3>
   69    2 0xffffff7f80d3a000 0xf000     0xf000     com.apple.driver.AppleSMC (3.1.5d4) <9 7 5 4 3>
   70    0 0xffffff7f80d4b000 0x10000    0x10000    com.apple.driver.ACPI_SMC_PlatformPlugin (1.0.0) <69 68 67 10 9 7 6 5 4 3>
   71    0 0xffffff7f818fd000 0x2000     0x2000     com.apple.driver.AppleSMBusPCI (1.0.11d1) <10 5 4 3>
   72    2 0xffffff7f81b56000 0xc000     0xc000     com.apple.iokit.IOHDAFamily (2.4.7fc4) <5 4 3 1>
   73    1 0xffffff7f81b8d000 0x19000    0x19000    com.apple.driver.AppleHDAController (2.4.7fc4) <72 63 10 7 6 5 4 3 1>
   74    2 0xffffff7f81900000 0xe000     0xe000     com.apple.driver.AppleSMBusController (1.0.11d1) <23 10 9 5 4 3>
   75    0 0xffffff7f819a7000 0xd000     0xd000     com.apple.driver.AppleMCCSControl (1.1.11) <74 63 10 9 7 5 4 3 1>
   76    0 0xffffff7f817e3000 0x5000     0x5000     com.apple.driver.AppleUpstreamUserClient (3.5.12) <63 10 9 7 5 4 3 1>
   77    0 0xffffff7f80d21000 0x3000     0x3000     com.apple.driver.AppleSMCPDRC (1.0.0) <67 10 6 4 3>
   78    1 0xffffff7f80f86000 0x1b000    0x1b000    com.apple.iokit.IOBluetoothHostControllerUSBTransport (4.1.7f6) <32 10 9 7 5 4 3 1>
   79    0 0xffffff7f80fa1000 0x8000     0x8000     com.apple.iokit.BroadcomBluetoothHostControllerUSBTransport (4.1.7f6) <78 32 10 9 7 5 4 3>
   82    0 0xffffff7f819de000 0x3000     0x3000     com.apple.driver.AppleLPC (1.6.3) <67 10 5 4 3>
   83    1 0xffffff7f81d52000 0x3000     0x3000     com.apple.driver.AppleGraphicsControl (3.4.5) <65 63 10 9 7 5 4 3 1>
   84    0 0xffffff7f81d55000 0xc000     0xc000     com.apple.driver.ApplePolicyControl (3.4.5) <83 65 63 10 9 7 5 4 3 1>
   85    0 0xffffff7f81367000 0x5000     0x5000     com.apple.Dont_Steal_Mac_OS_X (7.0.0) <69 7 4 3 1>
   86    2 0xffffff7f80eb1000 0x9b000    0x9b000    com.apple.iokit.IOBluetoothFamily (4.1.7f6) <32 7 5 4 3 1>
   87    0 0xffffff7f80c8b000 0x12000    0x12000    com.apple.iokit.IOSurface (86.0.5) <7 5 4 3 1>
   88    0 0xffffff7f809e0000 0x7000     0x7000     com.apple.iokit.IOUserEthernet (1.0.0d1) <37 6 5 4 3 1>
   91    0 0xffffff7f80e46000 0xe000     0xe000     com.apple.iokit.IOFireWireIP (2.2.5) <45 37 5 4 3 1>
   92    0 0xffffff7f81b65000 0x16000    0x16000    com.apple.driver.AppleMikeyDriver (2.4.7fc4) <74 9 5 4 3 1>
   93    2 0xffffff7f814bb000 0xe000     0xe000     com.apple.kext.OSvKernDSPLib (1.12) <5 4>
   94    3 0xffffff7f814c9000 0x2f000    0x2f000    com.apple.iokit.IOAudioFamily (1.9.2fc7) <93 5 4 3 1>
   95    1 0xffffff7f81ba6000 0xba000    0xba000    com.apple.driver.DspFuncLib (2.4.7fc4) <94 93 6 5 4 3 1>
   96    0 0xffffff7f81c69000 0x8b000    0x8b000    com.apple.driver.AppleHDA (2.4.7fc4) <95 94 73 72 65 63 6 5 4 3 1>
   98    0 0xffffff7f8199c000 0x3000     0x3000     com.apple.driver.AppleMikeyHIDDriver (124) <27 7 4 3 1>
  100    0 0xffffff7f81995000 0x4000     0x4000     com.apple.driver.ApplePlatformEnabler (2.0.7d2) <7 5 4 3>
  101    0 0xffffff7f81d38000 0x12000    0x12000    com.apple.driver.AGPM (100.13.14) <67 65 63 10 5 4 3>
  102    0 0xffffff7f8080f000 0x2b000    0x2b000    com.apple.iokit.IOSCSIArchitectureModelFamily (3.5.6) <5 4 3 1>
  103    1 0xffffff7f814ab000 0x5000     0x5000     com.apple.kext.triggers (1.0) <7 6 5 4 3 1>
  104    0 0xffffff7f814b0000 0x9000     0x9000     com.apple.filesystems.autofs (3.0) <103 7 6 5 4 3 1>
  105    0 0xffffff7f81500000 0x5000     0x5000     com.apple.driver.AudioAUUC (1.60) <94 63 10 9 7 5 4 3 1>
  106    1 0xffffff7f80ca8000 0xe000     0xe000     com.apple.iokit.IOSerialFamily (10.0.6) <7 6 5 4 3 1>
  107    0 0xffffff7f80f72000 0xa000     0xa000     com.apple.iokit.IOBluetoothSerialManager (4.1.7f6) <106 7 5 4 3 1>
  108    0 0xffffff7f81b11000 0x5000     0x5000     com.apple.driver.AppleHWSensor (1.9.5d0) <5 4 3>
  109    1 0xffffff7f817f8000 0x17000    0x17000    com.apple.driver.AppleMultitouchDriver (237.4) <27 5 4 3 1>
  110    2 0xffffff7f80f5b000 0x12000    0x12000    com.apple.driver.IOBluetoothHIDDriver (4.1.7f6) <86 27 5 4 3>
  111    0 0xffffff7f81da4000 0xe000     0xe000     com.apple.driver.AppleBluetoothMultitouch (75.19) <110 109 86 27 5 4 3>
  112    1 0xffffff7f81813000 0x7000     0x7000     com.apple.driver.AppleHIDKeyboard (170.2.4) <27 4 3>
  113    0 0xffffff7f81b50000 0x6000     0x6000     com.apple.driver.AppleBluetoothHIDKeyboard (170.2.4) <112 110 27 4 3>
  114    0 0xffffff7f81e74000 0xd000     0xd000     com.apple.nke.asp_tcp (7.1.0) <7 6 5 4 3 1>
  115    1 0xffffff7f81e81000 0x11000    0x11000    com.apple.security.SecureRemotePassword (1.0) <4 1>
  116    0 0xffffff7f81e92000 0x4f000    0x4f000    com.apple.filesystems.afpfs (10.0) <115 7 6 5 4 3 1>
  118    0 0xffffff7f81eef000 0x24000    0x24000    com.insanelymac.IntelMausiEthernet (1.0.0) <37 10 5 4 3 1>
mausi:Desktop laura$ system_profiler SPSoftwareDataType
Software:

    System Software Overview:

      System Version: OS X 10.8.5 (12F2542)
      Kernel Version: Darwin 12.6.0
      Boot Volume: Macintosh HD
      Boot Mode: Normal
      Computer Name: Mausi
      User Name: Laura Müller (laura)
      Secure Virtual Memory: Enabled
      Time since boot: 8 minutes

Mieze

Edited by Mieze

Share this post


Link to post
Share on other sites

Announcements

  • Similar Content

    • 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.
    • By autantpourmoi
      I'm an happy user of a x99 built hackintosch since 6/7 years using it mainly for photoshop and fcpx ... Using new camera with better resolution and video in ProResRaw , my built start to struggle a bit 
      I'm thinking of making a new built and seeking for advices for this new built that I want evolutive and last at least as long as my previous built 
      I'll use a SSD M2 forth Generation so I need at least 2 to 3 SSD M2 PCI x4 slots
      then which proc to use , I was thinking about the AMD Ryzen 9 3900xt or the Intel I9 10900k ( don't have the money for AMD threadripper ) if you have better idea I'm really open to it as long as you explain it to me 
      then which chipset should I use:
      for Intel  , should I go to Z490 or X299 or W480
      For AMD , I think I have only the choice of X570
      I always used Gigabyte motherboard so it will be naturally my first choice but again I'm open to any suggestion
      I need at least usb 3,1 Gen 2 and TB3 is not necessary but an option and can be add later on with a PCI Card I think
      So I'll be pleased o read your opinion and the choices that you'll do for the purpose of this built 
      thanks in advance 
       
       
    • By Mieze
      This project is dedicated to Lucy, my lovely little Tyrannofelis Rex. 
       

       
      LucyRTL8125Ethernet is an open source driver for the Realtek RTL8125 family of 2.5GBit Ethernet controllers.
       
      Key Features of the Driver
      Supports all versions of Realtek's RTL8125 2.5GBit Ethernet Controllers 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 over IPv4 and IPv6. Support for TCP/IPv4, UDP/IPv4, TCP/IPv6 and UDP/IPv6 checksum offload. Supports jumbo frames up to 9000 bytes (strongly recommended for 2.5GBit operation). Fully optimized for Mojave and above. Note that older versions of macOS might not support 2.5GB Ethernet. Supports Wake on LAN (untested). Supports VLAN (untested). 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.  
      Current Status
      The driver has been tested successfully under Catalina (10.15.4 and above) and, according to first tests, is working stable. I haven't experienced any Kernel Panics during my tests and is working stable on my primary work machine. The driver has been designed to work with Catalina but might also work with Mojave, provided you build from source with Xcode 10.. Please keep in mind that support for 2.5GBit Ethernet was introduced in Mojave (or maybe High Sierra?) so that there is no way to make it work with Sierra or below.  
      Known Issues
      Using autoselect medium it seems to prefer negotiating a connection speed of 1Gbit with my switch so that I had to select 2.5GBit/s manually in order to achieve this speed but it might be different with other switches.   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 injection). It's your call!  
      Help - I'm getting kernel panics!
      Well, before you start complaining about bugs after you upgraded macOS and ask me to publish a driver update, you should first try to resolve the issue on your own by cleaning the system caches.
      As the driver uses macOS's private network driver interface, which is supposed to be used by Apple provided drivers only, you might run into problems after an OS update because the linker may fail to recognize that IONetworking.kext has been updated and that the driver needs to be linked against the new version (Apple provided drivers avoid this problem because they are always updated together with IONetworking.kext). As a result, the linking process produces garbage and the driver may call arbitrary code when trying to call functions from IONetworking.kext. This usually results in unpredicted behavior or a kernel panic. In order to recover from such a situation, you should clean the System Caches forcing the linker to recreate it's caches:
      Delete all the files in /System/Library/Caches and it's subdirectories but leave the directories and the symbolic links intact. This is very important! Reboot. Recreate the kernel cache. Reboot again.  
      Troubleshooting
      Make sure you have followed the installation instructions especially when you have issues with certain domains while the others are working fine. Use the debug version to collect log data when trying to track down problems. The kernel log messages can be retrieved with "log show --predicate "processID == 0" --debug" in order to retrieve kernel logs. Include the log data when asking for support or giving feedback. I'm an engineer, not a clairvoyant. Don't copy and paste large amounts of log data to your post. Create an archive with the log data and attach it to your post. In case you don't want to make your log data publicly accessible, contact me via PM and I will provide you a mail address to send it directly to me.  Delete the following files: /Library/Preferences/SystemConfiguration/NetworkInterfaces.plist /Library/Preferences/SystemConfiguration/preferences.plist In Terminal run netstat -s in order to display network statistics. Carefully examine the data for any unusual activity like a high number of packets with bad IP header checksums, etc. In case auto-configuration of the link layer connection doesn't work it might be necessary to select the medium manually in System Preferences under Network for the interface. Use Wireshark to create a packet dump in order to collect diagnostic information. Keep in mind that there are many manufacturers of network equipment. Although Ethernet is an IEEE standard, different implementations may show different behavior causing incompatibilities. In case you are having trouble try a different switch or a different cable.  
      Changelog
      Version 1.0.0 (2020-08-14) Changed version number to make this the first official release. Version 1.0.0d6 (2020-06-14) Fixed chip recognition. Version 1.0.0d3 (2020-04-20) First working development release.  
      Getting the driver
      Source code can be found on GitHub: https://github.com/Mieze/LucyRTL8125Ethernet You'll find the lastest prebuilt binary in the download section: https://www.insanelymac.com/forum/files/file/1004-lucyrtl8125ethernet/  
       
×