Jump to content
Mieze

IntelMausiEthernet.kext for Intel onboard LAN

899 posts in this topic

Recommended Posts

On 8/8/2018 at 3:00 AM, Mieze said:

Once again, fix your system and everything will be fine! This kind of KPs keep popping up after every major update and it always turned out that the driver is innocent. :cat:

 

Mieze

How to understand where is the problem in system? In my case KP happens when OneDrive syncing lot of data  (50-100GB)....

Thanks

Share this post


Link to post
Share on other sites
Advertisement

Dumb question, can I inject this kext via EFI/Clover/Other or do I have to install it into S/L/E?

If I inject, do I still have to do the kext removals as listed above?

Share this post


Link to post
Share on other sites
19 hours ago, THE_Roen said:

Dumb question, can I inject this kext via EFI/Clover/Other or do I have to install it into S/L/E?

If I inject, do I still have to do the kext removals as listed above?

It's your call. Both methods work fine. Anyway you have to remove AppleIntelE1000e.kext in order to avoid conflicts.

 

Mieze

Share this post


Link to post
Share on other sites

Hey Mieze and haXors,

 

having problems with IntelMausi ethernet, currently running 10.11 but High Sierra was the same, random reboots.

im not sure but IntelMausi always shows up in Kernel extension backtrace.

i have tried different versions of IntelMausi and different locations. the kext used to be in Clover/Extensions but now testing in Library / Extensions, currently trying version 2.1.0d0, previously tried 2.4.0

 

Anonymous UUID:       52750D50-5CF2-E7A4-C18A-C64BA521EF42

Thu Sep 27 00:28:22 2018

*** Panic Report ***
panic(cpu 2 caller 0xffffff8016dcfc0b): Kernel trap at 0xffffff7f9765deea, type 14=page fault, registers:
CR0: 0x000000008001003b, CR2: 0xffffff8027615008, CR3: 0x000000001f72b000, CR4: 0x00000000001627e0
RAX: 0xffffff8125980000, RBX: 0x0000000000060084, RCX: 0x0000000000000000, RDX: 0x0000000000000001
RSP: 0xffffff81253ebe60, RBP: 0xffffff81253ebed0, RSI: 0xffffff802d6d8b00, RDI: 0xffffff80ebde9000
R8:  0x0000000000989243, R9:  0xffffff801742e018, R10: 0x0000000000000000, R11: 0x0000342d0ccea7fa
R12: 0xffffff802d6d8b00, R13: 0xffffff80ebde9000, R14: 0xffffff80ebde9000, R15: 0xffffff8027615000
RFL: 0x0000000000010246, RIP: 0xffffff7f9765deea, CS:  0x0000000000000008, SS:  0x0000000000000010
Fault CR2: 0xffffff8027615008, Error code: 0x0000000000000000, Fault CPU: 0x2, PL: 0

Backtrace (CPU 2), Frame : Return Address
0xffffff81253ebaf0 : 0xffffff8016cdab52
0xffffff81253ebb70 : 0xffffff8016dcfc0b
0xffffff81253ebd50 : 0xffffff8016deba63
0xffffff81253ebd70 : 0xffffff7f9765deea
0xffffff81253ebed0 : 0xffffff7f9765e65d
0xffffff81253ebef0 : 0xffffff80172b4cb6
0xffffff81253ebf40 : 0xffffff80172b2b21
0xffffff81253ebf80 : 0xffffff80172b2c16
0xffffff81253ebfb0 : 0xffffff8016dca257
      Kernel Extensions in backtrace:
         com.insanelymac.IntelMausiEthernet(2.1d0)[885CCFB0-868F-3864-B711-98998FB549E4]@0xffffff7f9765b000->0xffffff7f9766dfff
            dependency: com.apple.iokit.IONetworkingFamily(3.2)[848B398F-4D96-3024-8092-6CD3534D2CCA]@0xffffff7f97627000
            dependency: com.apple.iokit.IOPCIFamily(2.9)[3ED0A052-3347-39B8-AEA5-024E4BAC7886]@0xffffff7f9758e000

BSD process name corresponding to current thread: kernel_task
Boot args: -v dart=0 darkwake=no kext-dev-mode=1 -disablegfxfirmware

Mac OS version:
15G21013

Kernel version:
Darwin Kernel Version 15.6.0: Wed May  2 21:04:22 PDT 2018; root:xnu-3248.73.10~1/RELEASE_X86_64
Kernel UUID: 60551AC7-A949-357B-8B60-9825201AE9FB
Kernel slide:     0x0000000016a00000
Kernel text base: 0xffffff8016c00000
__HIB  text base: 0xffffff8016b00000
System model name: Macmini7,1 (Mac-35C5E08120C7EEAF)

System uptime in nanoseconds: 57368190764967
last loaded kext at 40586986750804: com.apple.driver.IOBluetoothHIDDriver    4.4.6f3 (addr 0xffffff7f9907e000, size 73728)
last unloaded kext at 41760926918718: com.apple.driver.IOBluetoothHIDDriver    4.4.6f3 (addr 0xffffff7f9907e000, size 73728)
loaded kexts:
com.paragon-software.filesystems.ntfs    26.1.15
com.intel.driver.EnergyDriver    2.0
at.obdev.nke.LittleSnitch    4740
com.insanelymac.IntelMausiEthernet    2.1.0d0
org.hwsensors.driver.ACPISensors    1765
org.hwsensors.driver.CPUSensors    1765
as.vit9696.AppleALC    1.2.7
org.netkas.driver.FakeSMC    1765
as.lvs1974.IntelGraphicsFixup    1.2.7
as.vit9696.Lilu    1.2.3
com.rehabman.driver.USBInjectAll    0.5.17
com.apple.filesystems.smbfs    3.0.1
com.apple.filesystems.afpfs    11.0
com.apple.nke.asp-tcp    8.0.0
com.apple.driver.AudioAUUC    1.70
com.apple.filesystems.autofs    3.0
com.apple.driver.AppleGraphicsDevicePolicy    3.12.7
com.apple.driver.AppleUpstreamUserClient    3.6.1
com.apple.driver.AppleMCCSControl    1.2.13
com.apple.driver.AppleHDA    274.12
com.apple.driver.pmtelemetry    1
com.apple.iokit.IOUserEthernet    1.0.1
com.apple.driver.AppleIntelHD5000Graphics    10.1.4
com.apple.driver.AppleOSXWatchdog    1
com.apple.iokit.CSRBluetoothHostControllerUSBTransport    4.4.6f3
com.apple.iokit.IOBluetoothSerialManager    4.4.6f3
com.apple.Dont_Steal_Mac_OS_X    7.0.0
com.apple.driver.AppleHV    1
com.apple.driver.AppleIntelFramebufferAzul    10.1.4
com.apple.driver.ACPI_SMC_PlatformPlugin    1.0.0
com.apple.driver.AppleIntelSlowAdaptiveClocking    4.0.0
com.apple.AppleFSCompression.AppleFSCompressionTypeDataless    1.0.0d1
com.apple.AppleFSCompression.AppleFSCompressionTypeZlib    1.0.0
com.apple.BootCache    38
com.apple.iokit.IOAHCIBlockStorage    2.8.5
com.apple.driver.AppleAHCIPort    3.1.8
com.apple.driver.usb.AppleUSBEHCIPCI    1.0.1
com.apple.driver.AppleACPIButtons    4.0
com.apple.driver.AppleRTC    2.0
com.apple.driver.AppleHPET    1.8
com.apple.driver.AppleSMBIOS    2.1
com.apple.driver.AppleAPIC    1.7
com.apple.nke.applicationfirewall    163
com.apple.security.quarantine    3
com.apple.security.TMSafetyNet    8
com.apple.security.SecureRemotePassword    1.0
com.apple.kext.triggers    1.0
com.apple.driver.AppleGraphicsControl    3.12.9
com.apple.driver.AppleSMBusController    1.0.14d1
com.apple.iokit.IOSMBusFamily    1.1
com.apple.driver.DspFuncLib    274.12
com.apple.kext.OSvKernDSPLib    525
com.apple.driver.AppleHDAController    274.12
com.apple.iokit.IOHDAFamily    274.12
com.apple.iokit.IOAudioFamily    204.4
com.apple.vecLib.kext    1.2.0
com.apple.iokit.IOSurface    108.3.2
com.apple.iokit.IONDRVSupport    2.4.1
com.apple.iokit.IOBluetoothHostControllerUSBTransport    4.4.6f3
com.apple.iokit.IOSerialFamily    11
com.apple.iokit.IOBluetoothFamily    4.4.6f3
com.apple.driver.CoreCaptureResponder    1
com.apple.driver.corecapture    1.0.4
com.apple.AppleGraphicsDeviceControl    3.12.9
com.apple.iokit.IOAcceleratorFamily2    205.14
com.apple.iokit.IOGraphicsFamily    2.4.1
com.apple.driver.AppleSMC    3.1.9
com.apple.driver.IOPlatformPluginLegacy    1.0.0
com.apple.driver.IOPlatformPluginFamily    6.0.0d7
com.apple.iokit.IOSlowAdaptiveClockingFamily    1.0.0
com.apple.iokit.IOSCSIArchitectureModelFamily    3.7.7
com.apple.driver.usb.IOUSBHostHIDDevice    1.0.1
com.apple.driver.usb.cdc    5.0.0
com.apple.driver.usb.networking    5.0.0
com.apple.driver.usb.AppleUSBHostCompositeDevice    1.0.1
com.apple.driver.usb.AppleUSBHub    1.0.1
com.apple.driver.AppleEFINVRAM    2.0
com.apple.iokit.IOUSBFamily    900.4.1
com.apple.iokit.IONetworkingFamily    3.2
com.apple.driver.usb.AppleUSBXHCIPCI    1.0.1
com.apple.driver.usb.AppleUSBXHCI    1.0.1
com.apple.iokit.IOAHCIFamily    2.8.1
com.apple.driver.usb.AppleUSBEHCI    1.0.1
com.apple.iokit.IOUSBHostFamily    1.0.1
com.apple.driver.AppleUSBHostMergeProperties    1.0.1
com.apple.driver.AppleEFIRuntime    2.0
com.apple.iokit.IOHIDFamily    2.0.0
com.apple.security.sandbox    300.0
com.apple.kext.AppleMatch    1.0.0d1
com.apple.driver.AppleKeyStore    2
com.apple.driver.AppleMobileFileIntegrity    1.0.5
com.apple.driver.AppleCredentialManager    1.0
com.apple.driver.DiskImages    417.4
com.apple.iokit.IOStorageFamily    2.1
com.apple.iokit.IOReportFamily    31
com.apple.driver.AppleFDEKeyStore    28.30
com.apple.driver.AppleACPIPlatform    4.0
com.apple.iokit.IOPCIFamily    2.9
com.apple.iokit.IOACPIFamily    1.4
com.apple.kec.Libm    1
com.apple.kec.pthread    1
com.apple.kec.corecrypto    1.0
Model: Macmini7,1, BootROM MM71.0232.B00, 2 processors, Intel Core i5, 2.89 GHz, 8 GB, SMC 2.24f32
Graphics: Intel HD Graphics 4600, Intel HD Graphics 4600, Built-In
Memory Module: BANK 0/DIMM0, 4 GB, DDR3, 1600 MHz, SK Hynix, HMT351S6CFR8C-PBN0
Memory Module: BANK 1/DIMM0, 4 GB, DDR3, 1600 MHz, SK Hynix, HMT351S6CFR8C-PBN0
Bluetooth: Version 4.4.6f3, 3 services, 26 devices, 1 incoming serial ports
Network Service: Ethernet, Ethernet, en0
Serial ATA Device: Samsung SSD 850 EVO 250GB, 250.06 GB
USB Device: USB 2.0 Bus
USB Device: Hub
USB Device: USB 2.0 Bus
USB Device: Hub
USB Device: USB 3.0 Bus
USB Device: USB 2.0 Hub
USB Device: Microsoft® 2.4GHz Transceiver v8.0
USB Device: USB Receiver
USB Device: CSR8510 A10
Thunderbolt Bus:

 

 

FIXED IT!

i downloaded [url="http://www.insanelymac.com/forum/topic/279450-why-insanelymac-does-not-support-tonymacx86/"]#####[/url] El Capitan version and had a look at what version it has inside it, extracted it, and presto! no more daily reboots!

it was some old version 2.0 or something. working well from /EFI/C/K/O with WOL :)

 

 

 

Edited by millusions

Share this post


Link to post
Share on other sites
On 1/31/2015 at 8:51 AM, malek_bh said:

tested on Dell Latitude E6320 with Intel® 82579LM Gigabit Network ,work ok ,

thank you

Can I ask you how do you fix? I have the same board but having also some troubles and can't solve them...

What steps did you do?

 

Thank you so much

Edited by Fedeanzaf

Share this post


Link to post
Share on other sites

In the past there have always been reports of kernel panics after every major update of macOS and I also received some of them from users which upgraded to Mojave. It always turned out that the driver is innocent and I have no reason to assume that it's different this time. 

 

Anyway, I ran some tests with 10.14.1 this afternoon using the prebuilt binary from the download section and there haven't been any issues. Version 2.4.0 of IntelMausiEthernet works perfectly with Mojave. In case you are experiencing any problems, it's most likely because something went wrong during the update and you should try to fix your system.

 

1062282619_Bildschirmfoto2018-11-02um21_09_44.thumb.png.5c2611772994f20d128a05406c71807a.png

 

Mieze

Edited by Mieze

Share this post


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

Hi Mieze,

 

just wondering... is there any link aggregation support with this kext under High Sierra/Mojave? TIA!

Yes, the driver supports LACP. I successfully tested it in combination with a Realtek RTL8111E using my Realtek driver.

 

Mieze

Share this post


Link to post
Share on other sites

I've had an annoying problem for quite some time now, but it only happens when downloading so I've lived with it. Everytime I downloaded large files with Ethernet for example 20gb game from GOG and left the download running and came back the computer had restarted. I noticed that when Safari is downloading for a long time the computer goes to sleep and reboots. I haven't had any problems with sleep previously, only when downloading.

 

So I noticed today you had updated the driver and gave it a try and it seems to have fixed this problem with Z270N WiFi board. I just wrote this to say thank you Mieze and maybe someone is googling the same problem and finds this helpful.

Share this post


Link to post
Share on other sites
19 hours ago, Amble said:

I've had an annoying problem for quite some time now, but it only happens when downloading so I've lived with it. Everytime I downloaded large files with Ethernet for example 20gb game from GOG and left the download running and came back the computer had restarted. I noticed that when Safari is downloading for a long time the computer goes to sleep and reboots. I haven't had any problems with sleep previously, only when downloading.

 

So I noticed today you had updated the driver and gave it a try and it seems to have fixed this problem with Z270N WiFi board. I just wrote this to say thank you Mieze and maybe someone is googling the same problem and finds this helpful.

Thank you for the feedback. I received a similar problem report form from vit9696 but I neither can reproduce the issue on my test system, nor do I have a conclusive explanation for it. 

 

Instead of that I noticed a strange behavior of the power LED during sleep on my test machine. Although the system seems to sleep and wake properly, the power LED stays on in sleep state which indicates, that the machine doesn't manage to complete the transition to sleep state (S3) completely. This never happened before updating to Mojave and it indicates that there is a general power management issue, which may also be related to the crash.

 

Anyway, it would be helpful if you could provide me a kernel panic report of the machine showing the incident? Are you using Gigabit Ethernet for your LAN? How fast is your internet connection?

 

I also attach the prebuilt binary (requires Mojave) to this post so that anybody interested in testing version 2.5.0d0 of the driver or having the same problem can try it too. It should also fix the no network after wakeup issue that some users with LM-versions of the NIC reported in the past, as it doesn't release control of the chip during sleep anymore

 

Mieze

IntelMausiEthernet-V2.5.0d0.zip

Edited by Mieze

Share this post


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

Thank you for the feedback. I received a similar problem report form from vit9696 but I neither can reproduce the issue on my test system, nor do I have a conclusive explanation for it. 

 

Instead of that I noticed a strange behavior of the power LED during sleep on my test machine. Although the system seems to sleep and wake properly, the power LED stays on in sleep state which indicates, that the machine doesn't manage to complete the transition to sleep state (S3) completely. This never happened before updating to Mojave and it indicates that there is a general power management issue, which may also be related to the crash.

 

Anyway, it would be helpful if you could provide me a kernel panic report of the machine showing the incident? Are you using Gigabit Ethernet for your LAN? How fast is your internet connection?

 

I also attach the prebuilt binary (requires Mojave) to this post so that anybody interested in testing version 2.5.0d0 of the driver or having the same problem can try it too. It should also fix the no network after wakeup issue that some users with LM-versions of the NIC reported in the past, as it doesn't release control of the chip during sleep anymore

 

Mieze

IntelMausiEthernet-V2.5.0d0.zip

 

I'll try this weekend.

Share this post


Link to post
Share on other sites
On 12/2/2018 at 10:58 PM, Mieze said:

Thank you for the feedback. I received a similar problem report form from vit9696 but I neither can reproduce the issue on my test system, nor do I have a conclusive explanation for it. 

 

Instead of that I noticed a strange behavior of the power LED during sleep on my test machine. Although the system seems to sleep and wake properly, the power LED stays on in sleep state which indicates, that the machine doesn't manage to complete the transition to sleep state (S3) completely. This never happened before updating to Mojave and it indicates that there is a general power management issue, which may also be related to the crash.

 

Anyway, it would be helpful if you could provide me a kernel panic report of the machine showing the incident? Are you using Gigabit Ethernet for your LAN? How fast is your internet connection?

 

I also attach the prebuilt binary (requires Mojave) to this post so that anybody interested in testing version 2.5.0d0 of the driver or having the same problem can try it too. It should also fix the no network after wakeup issue that some users with LM-versions of the NIC reported in the past, as it doesn't release control of the chip during sleep anymore

 

Mieze

IntelMausiEthernet-V2.5.0d0.zip

 

I had time do this today. Can you PM me email address where I could send these files? On the Zip I added kernel log (2.4.0 debug version), KP file and screenshot of Ethernet.

 

On the kernel log 4.12.2018:

 

17:04 Restart

17:06 Sleep/Wake

17:07 Started the download

17:25 Monitor shuts down when computer goes or tries to go to sleep and then restarts.

 

I haven't had that sort of problems with power led. Connection is 250Mbit/s. File was about 23Gb and download speed about 11Mb/s. Don't know if it was just GOG having a temporary hiccup but with the 2.5.0 I compiled I got around 20Mb/s about an hour ago.

Edited by Amble

Share this post


Link to post
Share on other sites

hey Mieze,

 

 

there is a problem with this driver and static IP.

it seems to kernel panic once a day around 00:20 every day if the IP is static, works perfectly with DHCP

 

thanks

Share this post


Link to post
Share on other sites
22 minutes ago, millusions said:

hey Mieze,

 

 

there is a problem with this driver and static IP.

it seems to kernel panic once a day around 00:20 every day if the IP is static, works perfectly with DHCP

 

thanks

Please delete system caches and see if it resolves the issue.

 

Mieze

Share this post


Link to post
Share on other sites

hi. thanks for reply.

 

is clean my Mac clean caches ok?

or manual /Library/Caches?

 

i did the Clean My Mac 3 way,

it's 10.11.6, InelMausi v.2.1.0 loaded from EFI/Clover/kexts/other

 

i've set it back to static IP - see what happens at midnight.

 

it's working very nicely but few days ago i went back to static IP for Plex and it started KP's daily again.  changed it to DHCP and it's perfect again.

IP is mac addressed assigned by time capsule

Share this post


Link to post
Share on other sites

:(

 

 

Tue Dec 18 04:10:37 2018

*** Panic Report ***
panic(cpu 2 caller 0xffffff801e1cfc0b): Kernel trap at 0xffffff7fa0444975, type 14=page fault, registers:
CR0: 0x000000008001003b, CR2: 0xffffff802ea85008, CR3: 0x0000000026b99000, CR4: 0x00000000001627e0
RAX: 0x0000000000000000, RBX: 0x0000000000060084, RCX: 0x0000000000000000, RDX: 0x0000000000000001
RSP: 0xffffff812c093e60, RBP: 0xffffff812c093ed0, RSI: 0xffffff8034e24280, RDI: 0xffffff80f3354000
R8:  0x0000000000989240, R9:  0xffffff801e82e018, R10: 0x0000000000000000, R11: 0x00007b938cb7b44a
R12: 0xffffff8034e24280, R13: 0xffffff80f3354000, R14: 0xffffff80f3354000, R15: 0xffffff802ea85000
RFL: 0x0000000000010246, RIP: 0xffffff7fa0444975, CS:  0x0000000000000008, SS:  0x0000000000000010
Fault CR2: 0xffffff802ea85008, Error code: 0x0000000000000000, Fault CPU: 0x2, PL: 0

Backtrace (CPU 2), Frame : Return Address
0xffffff812c093af0 : 0xffffff801e0dab52
0xffffff812c093b70 : 0xffffff801e1cfc0b
0xffffff812c093d50 : 0xffffff801e1eba63
0xffffff812c093d70 : 0xffffff7fa0444975
0xffffff812c093ed0 : 0xffffff7fa044511f
0xffffff812c093ef0 : 0xffffff801e6b4cb6
0xffffff812c093f40 : 0xffffff801e6b2b21
0xffffff812c093f80 : 0xffffff801e6b2c16
0xffffff812c093fb0 : 0xffffff801e1ca257
      Kernel Extensions in backtrace:
         com.insanelymac.IntelMausiEthernet(2.1)[0615B7F7-B3E2-3EBF-9D09-24897BADC66E]@0xffffff7fa0441000->0xffffff7fa0454fff
            dependency: com.apple.iokit.IONetworkingFamily(3.2)[848B398F-4D96-3024-8092-6CD3534D2CCA]@0xffffff7f9eee5000
            dependency: com.apple.iokit.IOPCIFamily(2.9)[3ED0A052-3347-39B8-AEA5-024E4BAC7886]@0xffffff7f9e98e000

 

Share this post


Link to post
Share on other sites

First of all, if you don't know how to clean the system caches of your Mac OS version, ask Google.

 

Second, there is no driver problem with static IP addresses because address handling is far beyond the scope of a driver. The driver handles packets, nothing more and nothing less. In case it continues to crash, fix your system.

 

Mieze

Share this post


Link to post
Share on other sites

can you tell me how to clean it? it's quite easy to say fix your system.  i'm not a genius but im pretty sure an ethernet driver also handles IP address of self etc.

if the computer works perfectly with a dynamic IP then it's probably not a system issue.

 

check it out. now it kp's at 04:10: exactly the same time as yesterday. and i know why, because computer is set to go to sleep at 4am, it used to be 1200 so kp's were at 12:10

 

Anonymous UUID:       52750D50-5CF2-E7A4-C18A-C64BA521EF42

Wed Dec 19 04:10:37 2018

*** Panic Report ***
panic(cpu 0 caller 0xffffff801abcfc0b): Kernel trap at 0xffffff7f9ce51975, type 14=page fault, registers:
CR0: 0x000000008001003b, CR2: 0xffffff802b484008, CR3: 0x0000000023599000, CR4: 0x00000000001627e0
RAX: 0x0000000000000000, RBX: 0x0000000000060084, RCX: 0x0000000000000000, RDX: 0x0000000000000001
RSP: 0xffffff812a383e60, RBP: 0xffffff812a383ed0, RSI: 0xffffff8031662400, RDI: 0xffffff80efc74000
R8:  0x00000000009892f3, R9:  0xffffff8032e77688, R10: 0x0000000000000000, R11: 0x000029419e119be4
R12: 0xffffff8031662400, R13: 0xffffff80efc74000, R14: 0xffffff80efc74000, R15: 0xffffff802b484000
RFL: 0x0000000000010246, RIP: 0xffffff7f9ce51975, CS:  0x0000000000000008, SS:  0x0000000000000010
Fault CR2: 0xffffff802b484008, Error code: 0x0000000000000000, Fault CPU: 0x0, PL: 0

Backtrace (CPU 0), Frame : Return Address
0xffffff812a383af0 : 0xffffff801aadab52
0xffffff812a383b70 : 0xffffff801abcfc0b
0xffffff812a383d50 : 0xffffff801abeba63
0xffffff812a383d70 : 0xffffff7f9ce51975
0xffffff812a383ed0 : 0xffffff7f9ce5211f
0xffffff812a383ef0 : 0xffffff801b0b4cb6
0xffffff812a383f40 : 0xffffff801b0b2b21
0xffffff812a383f80 : 0xffffff801b0b2c16
0xffffff812a383fb0 : 0xffffff801abca257
      Kernel Extensions in backtrace:
         com.insanelymac.IntelMausiEthernet(2.1)[0615B7F7-B3E2-3EBF-9D09-24897BADC66E]@0xffffff7f9ce4e000->0xffffff7f9ce61fff
            dependency: com.apple.iokit.IONetworkingFamily(3.2)[848B398F-4D96-3024-8092-6CD3534D2CCA]@0xffffff7f9b8e5000
            dependency: com.apple.iokit.IOPCIFamily(2.9)[3ED0A052-3347-39B8-AEA5-024E4BAC7886]@0xffffff7f9b38e000

BSD process name corresponding to current thread: kernel_task
Boot args: -v dart=0 darkwake=8 -disablegfxfirmware kext-dev-mode=1

Mac OS version:
15G21013

Kernel version:
Darwin Kernel Version 15.6.0: Wed May  2 21:04:22 PDT 2018; root:xnu-3248.73.10~1/RELEASE_X86_64
Kernel UUID: 60551AC7-A949-357B-8B60-9825201AE9FB
Kernel slide:     0x000000001a800000
Kernel text base: 0xffffff801aa00000
__HIB  text base: 0xffffff801a900000
System model name: Macmini7,1 (Mac-35C5E08120C7EEAF)

 

Share this post


Link to post
Share on other sites

First booting into osx, open terminal and enter the following command.

 sudo kextcache -i /

press enter then enter your password if required. That should clean your cache.

Edited by p.H

Share this post


Link to post
Share on other sites

thanks p.H

 

i went back to IntelMausi project page and followed instruction to install there.

i used KCPM Utility Pro to recreate cache. to be honest i've never had to do that before.

then i created a schedule to go to sleep in 5 minutes and everything went without a hitch, im pretty sure by now that it was 'schedule to sleep' that was causing the kp's.

i was just trying to keep system 100% vanilla.

 

anyway, thanks for help mate. i hope tomorrow morning no kp :)

Share this post


Link to post
Share on other sites

Anonymous UUID:       52750D50-5CF2-E7A4-C18A-C64BA521EF42

Fri Dec 21 03:10:43 2018

*** Panic Report ***
panic(cpu 0 caller 0xffffff80017cfc0b): Kernel trap at 0xffffff7f82d377d5, type 14=page fault, registers:
CR0: 0x000000008001003b, CR2: 0xffffff801201d008, CR3: 0x000000000a12c000, CR4: 0x00000000001627e0
RAX: 0x0000000000000000, RBX: 0xffffff80d683c000, RCX: 0x0000000000000000, RDX: 0x0000000000000200
RSP: 0xffffff801205be50, RBP: 0xffffff801205bed0, RSI: 0xffffff8017bc0000, RDI: 0xffffff80d683c000
R8:  0x000000000098915d, R9:  0xffffff8001ec37c0, R10: 0x0000000000000000, R11: 0x0000466d09ecfda1
R12: 0xffffff80d683c000, R13: 0x000000ff5f0ed0c6, R14: 0xffffff801201d000, R15: 0x0000000000000001
RFL: 0x0000000000010246, RIP: 0xffffff7f82d377d5, CS:  0x0000000000000008, SS:  0x0000000000000010
Fault CR2: 0xffffff801201d008, Error code: 0x0000000000000000, Fault CPU: 0x0, PL: 0

Backtrace (CPU 0), Frame : Return Address
0xffffff801205bae0 : 0xffffff80016dab52
0xffffff801205bb60 : 0xffffff80017cfc0b
0xffffff801205bd40 : 0xffffff80017eba63
0xffffff801205bd60 : 0xffffff7f82d377d5
0xffffff801205bed0 : 0xffffff7f82d380ac
0xffffff801205bef0 : 0xffffff8001cb4cb6
0xffffff801205bf40 : 0xffffff8001cb2b21
0xffffff801205bf80 : 0xffffff8001cb2c16
0xffffff801205bfb0 : 0xffffff80017ca257
      Kernel Extensions in backtrace:
         com.insanelymac.IntelMausiEthernet(2.4d0)[6FDD7FE8-3965-3DAC-8997-8F76D32D99E5]@0xffffff7f82d34000->0xffffff7f82d47fff
            dependency: com.apple.iokit.IONetworkingFamily(3.2)[848B398F-4D96-3024-8092-6CD3534D2CCA]@0xffffff7f8247b000
            dependency: com.apple.iokit.IOPCIFamily(2.9)[3ED0A052-3347-39B8-AEA5-024E4BAC7886]@0xffffff7f81f8e000

BSD process name corresponding to current thread: kernel_task
Boot args: -v dart=0 darkwake=8 -disablegfxfirmware kext-dev-mode=1

Mac OS version:
15G21013

Kernel version:
Darwin Kernel Version 15.6.0: Wed May  2 21:04:22 PDT 2018; root:xnu-3248.73.10~1/RELEASE_X86_64
Kernel UUID: 60551AC7-A949-357B-8B60-9825201AE9FB
Kernel slide:     0x0000000001400000
Kernel text base: 0xffffff8001600000
__HIB  text base: 0xffffff8001500000
System model name: Macmini7,1 (Mac-35C5E08120C7EEAF)

 

Share this post


Link to post
Share on other sites

@millusions i experience the same problems. Crash reports looks identical.  Not nearly as often as you. It can go weeks without a problem. 

But I use dchp, and still get the problem, so like @Mieze says; Its not a problem of static ip vs dchp. 

However i also use a schedule to sleep. So that we do have in common. 

I could think it is somehow related to power management. 

 

Kext version: 2.4.1d1

OS: Mojave 10.14.2

motherboard: asus rog strix z370-g

 

Hope you have some suggestions @Mieze ? 

I can obviously supply crash reports, if needed, but they look identical to those of @millusions

Share this post


Link to post
Share on other sites

OS X has become more and more picky about the ACPI data structures starting with El Capitan. When I set up my test machine with an Asrock H97M-Pro4 under Yosemite, the board was almost hassle-free. After upgrading to El Capitan, I got an instant kernel panic on boot with a discrete GPU installed due to broken interrupt routing functions in the DSDT and even after resolving that problem, I had random kernel panics on sleep/wake with WoL enabled in OS X. In order to solve this problem, I had to keep Thunderbolt support enabled in BIOS (who knows why???), although there is no thunderbolt hardware installed in the system, and had to rewrite about 10% of the DSDT's code in order to get it stable with WoL enabled in OS X. The Sierra upgrade resulted in a bunch of new ACPI errors in the kernel logs too so that I had to rework the DSDT again. Look for ACPI errors in the kernel logs as a starting point and try to disable WoL in System Preferences when possible.

With regard to the UEFI setup, consult your board's manual and check all options which may affect the NIC's operation, in particular the UEFI network stack, network boot and power management. I even had a case where a user needed to to enable the network stack temporarily in order to get access to an option which had to be disabled for stable operation. Some things are straightforward while others need trial and error to find out like my Thunderbolt issue. ;-)

Messed up systems usually result from things going wrong while installing new drivers and require a reinstall in order to recover from that situation. During development I had a case where any version of the driver, even older versions which used to work fine, caused the machine to crash on boot. After a reinstall, the system work fine with the driver. I even watched this happen with Apple provided drivers.

 
Edited by millusions

Share this post


Link to post
Share on other sites

I219V doesn't have such joy :(

 

Safari is working, but vst plugins couldn't reach to the ethernet card for some reason in Sierra.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By Mieze
      Being asked to add support for Realtek's Fast Ethernet PCIe NICs to my RTL8111 driver I got tired of answering the same old question again and again so that I finally decided to write a separate driver for these chips and to make a few of you guys and gals happy.
       
      As of now the driver supports the following members the RTL810X Fast Ethernet family:
      RTL8101E RTL8102E RTL8103E RTL8401E RTL8105E RTL8402 RTL8106E RTL8106EUS RTL8107E   Here is a list of the driver's basic features:
      Supports Sierra (maybe El Capitan). 64 bit architecture only. 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. 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. Built using Xcode 4.6.3.  
      Changelog Version 2.0.1 (2018-05-10): Fixes a problem with retrieval of the permanent MAC address on some chips. Version 2.0.0 (2017-04-04): Uses Apple's private driver interface introduced with 10.8. Adds support for the RTL8107E. Supports packet scheduling with QFQ. Adds support for flow control and EEE. Version 1.0.0 (2014-05-24): First offical release.     Installation   Before you install the driver you have to remove any installed driver for RTL810X. Goto /S/L/E and delete the old driver. 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. Install the new driver and recreate the kernel cache. Reboot Open System Preferences again, select Network and check if the new network interface has been created automatically or create it manually now. Configure the interface.   Help - I'm getting kernel panics!
      Well, before you start complaining about bugs after you upgraded macOS and ask me to publish a driver update, you should first try to resolve the issue on your own by cleaning the system caches.
      As the driver uses macOS's private network driver interface, which is supposed to be used by Apple provided drivers only, you might run into problems after an OS update because the linker may fail to recognize that IONetworking.kext has been updated and that the driver needs to be linked against the new version (Apple provided drivers avoid this problem because they are always updated together with IONetworking.kext). As a result, the linking process produces garbage and the driver may call arbitrary code when trying to call functions from IONetworking.kext. This usually results in unpredicted behavior or a kernel panic. In order to recover from such a situation, you should clean the System Caches forcing the linker to recreate it's caches:
      Delete all the files in /System/Library/Caches and it's subdirectories but leave the directories and the symbolic links intact. This is very important! Reboot. Recreate the kernel cache. Reboot again.  
      Troubleshooting Make sure you have followed the installation instructions especially when you have issues with certain domains while the others are working fine. Use the debug version to collect log data when trying to track down problems. The kernel log messages can be retrieved with "grep kernel /var/log/system.log" in Terminal. Starting from Sierra use "log show --predicate "processID == 0" --debug" in order to retrieve kernel logs. Include the log data when asking for support or giving feedback. I'm an engineer, not a clairvoyant. Don't copy and paste large amounts of log data to your post. Create an archive with the log data and attach it to your post. In case you don't want to make your log data publicly accessible, contact me via PM and I will provide you a mail address to send it directly to me.  Check your BIOS settings. You might want to disable Network Boot and the UEFI Network Stack as these can interfere with the driver. Double check that you have removed any other Realtek kext from your system because they could prevent the driver from working properly. Delete the following files: /Library/Preferences/SystemConfiguration/NetworkInterfaces.plist /Library/Preferences/SystemConfiguration/preferences.plist Verify your bootloader configuration, in particular the kernel flags. Avoid using npci=0x2000 or npci=0x3000.  In Terminal run netstat -s in order to display network statistics. Carefully examine the data for any unusual activity like a high number of packets with bad IP header checksums, etc. In case auto-configuration of the link layer connection doesn't work it might be necessary to select the medium manually in System Preferences under Network for the interface. Use Wireshark to create a packet dump in order to collect diagnostic information. Keep in mind that there are many manufacturers of network equipment. Although Ethernet is an IEEE standard, different implementations may show different behavior causing incompatibilities. In case you are having trouble try a different switch or a different cable.  
      Getting the driver
      There is a prebuilt binary in the Download section of this site: http://www.insanelymac.com/forum/files/file/259-realtekrtl8100-binary/ The source code can be found on Github: https://github.com/Mieze/RealtekRTL8100   Mieze
    • By Mieze
      A New Driver for Realtek RTL8111
       
      Due to the lack of an OS X driver that makes use of the advanced features of the Realtek RTL81111/8168 series I started a new project with the aim to create a state of the art driver that gets the most out of those NICs which can be found on virtually any cheap board on the market today. Based on Realtek's Linux driver (version 8.035.0) I have written a driver that is optimized for performance while making efficient use of system resources and keeping the CPU usage down under heavy load.

      Key Features of the Driver
      Supports Realtek RTL8111/8168 B/C/D/E/F/G found on recent boards. Support for multisegment packets relieving the network stack of unnecessary copy operations when assembling packets for transmission. No-copy receive and transmit. Only small packets are copied on reception because creating a copy is more efficient than allocating a new buffer. TCP, UDP and IPv4 checksum offload (receive and transmit). TCP segmentation offload under IPv4. Support for TCP/IPv6 and UDP/IPv6 checksum offload. Fully optimized for Mountain Lion (64bit architecture) but should work with Lion too. As of now there is no support for Snow Leopard but it can be added if someone will create the necessary patches. Supports Wake on LAN. Support for Energy Efficient Ethernet (EEE) which can be disabled by setting enableEEE to NO in the drivers Info.plist without rebuild. The default is YES. The driver is published under GPLv2.  
      Limitations
      As checksum offload doesn't work with jumbo frames they are currently unsupported and will definitely never be. No support for 32bit kernels.  
      Installation
      Before you install the driver you have to remove any installed driver for RTL8111/8168.
      Goto /S/L/E and delete the old driver (Lnx2mac, AppleRealtekRTL8169, etc.). Recreate the kernel cache. Open System Preferences and delete the corresponding network interface, e. g. en0. If you forget this step you might experience strange problems with certain Apple domains, iTunes and iCloud later. Reboot. Install the new driver and recreate the kernel cache. I recommend to use Kext Wizard or a similar utility for the installation. Reboot Open System Preferences again, select Network and check if the new network interface has been created automatically or create it manually now. Configure the interface.  
      Help - I'm getting kernel panics!
      Well, before you start complaining about bugs after you upgraded macOS and ask me to publish a driver update, you should first try to resolve the issue on your own by cleaning the system caches.
      As the driver uses macOS's private network driver interface, which is supposed to be used by Apple provided drivers only, you might run into problems after an OS update because the linker may fail to recognize that IONetworking.kext has been updated and that the driver needs to be linked against the new version (Apple provided drivers avoid this problem because they are always updated together with IONetworking.kext). As a result, the linking process produces garbage and the driver may call arbitrary code when trying to call functions from IONetworking.kext. This usually results in unpredicted behavior or a kernel panic. In order to recover from such a situation, you should clean the System Caches forcing the linker to recreate it's caches:
      Delete all the files in /System/Library/Caches and it's subdirectories but leave the directories and the symbolic links intact. This is very important! Reboot. Recreate the kernel cache. Reboot again.  
      Troubleshooting
      Make sure you have followed the installation instructions especially when you have issues with certain domains while the others are working fine. Use the debug version to collect log data when trying to track down problems. The kernel log messages can be found in /var/log/system.log. For Sierra and above use "log show --predicate "processID == 0" --debug" in order to retrieve kernel logs. Include the log data when asking for support or giving feedback. I'm an engineer, not a clairvoyant. Check your BIOS settings. You might want to disable Network Boot and the UEFI Network Stack as these can interfere with the driver. Double check that you have removed any other Realtek kext from your system because they could prevent the driver from working properly. Verify your bootloader configuration, in particular the kernel flags. Avoid using npci=0x2000 or npci=0x3000.  In Terminal run netstat -s in order to display network statistics. Carefully examine the data for any unusual activity like a high number of packets with bad IP header checksums, etc. In case auto-configuration of the link layer connection doesn't work it might be necessary to select the medium manually in System Preferences under Network for the interface. Use Wireshark to create a packet dump in order to collect diagnostic information. Keep in mind that there are many manufacturers of network equipment. Although Ethernet is an IEEE standard different implementations may show different behavior causing incompatibilities. In case you are having trouble try a different switch or a different cable.  
      FAQ
      How can I retrieve the kernel logs? In Terminal type "grep kernel /var/log/system.log". I want to disable Energy Efficient Ethernet (EEE) but I don't know how? Take a look at the driver's Info.plist file. There you will find an option named <key>enableEEE</key>. Change its value from <true/> to <false/>. Don't forget to recreate the kernel cache after changing the value. WoL from S5 doesn't work with this driver but under Windows it's working. Is this a driver bug? No it isn't, the driver is working as it should because OS X doesn't support WoL from S5.  
      Current status
      The driver has been successfully tested under 10.8.x and 10.9 with the B, C, D, E, F and G versions of the RTL8111/8168 and is known to work stable on these devices.  
      Changelog
      Version 2.2.2 (2018-01-21) Force ASPM state to disabled/enabled according to the config parameter setting. Requires 10.12 or newer. Version 2.2.1 (2016-03-12): Updated underlying linux sources from Realtek to 8.041.00. Added support for RTL8111H. Implemented Apple’s polled receive driver model (RXPOLL). Requires 10.11 or newer. Support for older versions of OS X has been dropped. Version 2.0.0 (2015-06-21): Uses Apple's private driver interface introduced with 10.8. Supports packet scheduling with QFQ. Please note that 2.0.0 is identical to 2.0.0d2. Only the version number has changed. Version 1.2.3 (2014-08-23): Reworked TSO4 and added support for TSO6. Version 1.2.2 (2014-08-44): Added an option to disable Active State Power Management (ASPM, default disabled) as ASPM seems to result in unstable operation of some chipsets. Resolved a problem with Link Aggregation after reboot. Added a workaround for the multicast filter bug of chipset 17 (RTL8111F) which prevented Bonjour from working properly Version 1.2.0 (2014-04-24): Updated underlying linux sources from Realtek to 8.037.00. Improved interrupt mitigate to use a less aggressive value for 10/100 MBit connections. Version 1.1.3 (2013-11-29): Improved transmit queue handling made it possible to reduce CPU load during packet transmission. Improved deadlock detection logic in order to avoid false positives due to lost interrupts. Version 1.1.2 (2013-08-03): Improved SMB performance in certain configurations. Faster browsing of large shares. Version 1.1.0 (2013-06-08): Support for TCP/IPv6 and UDP/IPv6 checksum offload added (can be disabled in Info.plist). Maximum size of the scatter-gather-list has been increased from 24 to 40 segments to resolve performance issues with TSO4 when offloading large packets which are highly fragmented. TSO4 can be disabled in Info.plist without rebuild. Statistics gathering has been improved to deliver more detailed information (resource shortages, transmitter resets, transmitter interrupt count). The interrupt mitigate settings has been changed to improve performance with SMB and to reduce CPU load. Configuration option added to allow for user defined interrupt mitigate settings without rebuild. Version 1.0.4 (2013-05-04): Moved setLinkStatus(kIONetworkLinkValid) from start() to enable(). Cleaned up getDescCommand(). Version 1.0.3 (2013-04-25): The issue after a reboot from Windows has been eliminated. Version 1.0.2 (2013-04-22): Added support for rx checksum offload of TCP and UDP over IPv6. Version 1.0.1 (2013-03-31): Improved behavior when rx checksum offload isn't working properly. Adds the chipset's model name to IORegistry so that it will show up in System Profiler.  
      Known Issues
      There are still performance problems with regard to SMB in certain configurations. My tests indicate that Apple's Broadcom driver shows the same behavior with those configurations. Obviously it's a more general problem that is not limited to my driver. WoL does not work in certain configurations. Old systems with 3 and 4 series chipsets exhibit performance issues in recent versions of macOS because there is no optimized power management for these systems in macOS anymore as Apple dropped support for the underlying hardware a long time ago. In case you are affected, please upgrade your hardware or find an alternative solution because I have no plans for a workaround. Sorry, but I don't think that it's worth the effort.  
      Getting the driver
      The source code can be found here: https://github.com/M...driver_for_OS_X There is also a pre-build binary for Mavericks and Yosemite: http://www.insanelym...n-and-wireless/  
      Building from Source
      I'm using XCode 4.6.3 for development. You can get a free copy of XCode after becoming a member of the Apple developer program. The free membership is sufficient in order to get access to development tools and documentation.
    • By End3rPower50
      Hi, i've installed on my pc MacOS Mojave but after installation my pc, sometimes, crash giving kernel panic.
      I came to the conclusion that it is a random kernel panic because sometimes it starting up and other times it isn't starting up
       
      My PC:
      CPU: Intel i7 6500U
      LAN: RTL8100
      Wi-Fi & Bluetooth: Dell DW1820A
      USB 3.1
       
      CLOVER.zip
    • By Angelo_
      Hi, I followed the rehabman guide (linked in the vanilla guide on the side of r/Hackintosh, not sure if I can link it) for laptops for my yoga 730ILW13 with an 8265u, Conexant 11870, 8gb of ram, 13.3" fhd and I found that upon booting the installer usb I get this weird issue where the screen displays what it should but the screen is incredibly dim (though it was off before using a flashlight on it) and it flashes every few seconds for a few milliseconds to the correct brightness, I used the plist for hd615-650 (including my 620), not quite sure what could be the culprit, first time hackintoshing a laptop so it might be a stupid brightness kext I forgot but didn't find any in that post or in this forum :c 
      Attached the clover zip so that anyone with more experience than me might give an idea in what could be a way to fix this.
      Thank you in advance 
       
       
       
      CLOVER.zip
    • By Bahaa
      Need help here
      My graphic card is detached 7mb
      and I try a lot of solution and no one work 
      can any one help
       

×