Jump to content

IntelMausiEthernet.kext for Intel onboard LAN


Mieze
1,015 posts in this topic

Recommended Posts

I decided to make version 2.2.0d4 the official version 2.2.0 and updated the prebuilt binary in the download section. As always, source code can be found on GitHub.

 

Have fun!

 

Mieze  :cat:

  • Like 9
Link to comment
Share on other sites

I decided to make version 2.2.0d4 the official version 2.2.0 and updated the prebuilt binary in the download section. As always, source code can be found on GitHub.

 

Have fun!

 

Mieze  :cat:

 

Thanks great works on this and your Realtek8111 both are rock solid and if the drives being copied too support the writing speed just about fully saturate the link when copying. This over a period of about a day it took me to copy 7TB of data between two system my main data storage system and new second backup system I setup both running raidz on zfs filesystem. Anytime I looked at it it was doing 95-105 MB/s the smaller files going the lowest speed for the couple of seconds it was taking for them, the larger getting the highest as the link could get up to full speed then, I was using rsync to copy between the machines. 

Link to comment
Share on other sites

WoL seems not to work. I'm using the Intel I219V (ASUS z170 pro gaming). 2.2.0d4 on Sierra

In most cases this is due to a:

  • Wrong BIOS setting.
  • DSDT error.

Anyway, please post kernel logs showing a sleep/wake cycle.

 

Mieze

Link to comment
Share on other sites

In most cases this is due to a:

  • Wrong BIOS setting.
  • DSDT error.

Anyway, please post kernel logs showing a sleep/wake cycle.

 

Mieze

I'm not using DSDT and I think my BIOS settings are correct. WoL is working when i shutdown the PC in Windows and also in Clover. WoL is working on macOS in sleep mode but not after a shutdown.

 

EDIT: I did just read about WoL after a full shutdown on Mac and I think the problem is the missing S5 support. Thank you Mieze ^_^

 

sleep/wake

PMRD: prevent idle sleep list: IODisplayWrangler- (0)
prevent idle sleep list: IODisplayWrangler- (0)
PM response took 146 ms (52, logd)
kern_direct_file(/var/log/SleepWakeStacks.bin): vp size 172032, alloc 172032, mp free 721066917888, keep free 34359738368
max io 0x2000000 bytes
kern_open_file_for_direct_io(0)
kern_open_file_for_direct_io took 0 ms
kern_open_file_for_direct_io took 0 ms
Opened file /var/log/SleepWakeStacks.bin, size 172032, extents 1, maxio 2000000 ssd 0
Opened file /var/log/SleepWakeStacks.bin, size 172032, extents 1, maxio 2000000 ssd 0
polled file major 1, minor 0, blocksize 4096, pollers 5
polled file major 1, minor 0, blocksize 4096, pollers 5
IOOpenDebugDataFile: opened debugdata file
IOHibernateSystemPostWake: Closing debugdata file
kern_close_file_for_direct_io
vnode_close(0)
PM response took 3119 ms (47, powerd)
kern_direct_file(/var/log/SleepWakeStacks.bin): vp size 172032, alloc 172032, mp free 721066917888, keep free 34359738368
max io 0x2000000 bytes
kern_open_file_for_direct_io(0)
kern_open_file_for_direct_io took 0 ms
kern_open_file_for_direct_io took 0 ms
Opened file /var/log/SleepWakeStacks.bin, size 172032, extents 1, maxio 2000000 ssd 0
Opened file /var/log/SleepWakeStacks.bin, size 172032, extents 1, maxio 2000000 ssd 0
polled file major 1, minor 0, blocksize 4096, pollers 5
polled file major 1, minor 0, blocksize 4096, pollers 5
IOOpenDebugDataFile: opened debugdata file
setWakeOnMagicPacket() ===>
Ethernet [IntelMausi]: Wake on magic packet enabled.
setWakeOnMagicPacket() <===
disable() ===>
Ethernet [IntelMausi]: LPIC=0x11000011.
clearDescriptors() ===>
clearDescriptors() <===
Ethernet [IntelMausi]: WUFC=0x00000002.
Ethernet [IntelMausi]: Link down on en0
disable() <===
setPowerState() ===>
Ethernet [IntelMausi]: switching to power state 0.
setPowerState() <===
         0 [Time 1474900674] [Message PMRD: System Sleep
IOCPUSleepKernel
ACPI SLEEP
ACPI S3 WAKE
Wake reason: PWRB XDCI GLAN (User)
Wake reason: PWRB XDCI GLAN (User)
IOPlatformWakeAction -> AppleRTC
IOPlatformWakeAction -> AppleKeyStore
Started cpu 2 (lapic id 00000002)
Started cpu 4 (lapic id 00000004)
Started cpu 6 (lapic id 00000006)
Started cpu 1 (lapic id 00000001)
Started cpu 3 (lapic id 00000003)
Started cpu 5 (lapic id 00000005)
Started cpu 7 (lapic id 00000007)
gIOLastWakeAbsTime: 135131997503
PMRD: System Wake
RTC: PowerByCalendarDate setting ignored
RTC: PowerByCalendarDate setting ignored
****[IOBluetoothHIDDriver][handleWake] -- sending EXIT HID SUSPEND returned 0xe00002be ****

**** [IOBluetoothHIDDriver][handleWake] -- acknowledgeSetPowerState() returned 0x0000 ****
RTC: PowerByCalendarDate setting ignored
RTC: PowerByCalendarDate setting ignored
****[IOBluetoothHIDDriver][setPowerStateWL] -- Wake -- return 10 seconds -- powerStateOrdinal = 1 ****
Previous sleep cause: 5
PMRD: prevent idle sleep list: IODisplayWrangler+ (1)
prevent idle sleep list: IODisplayWrangler+ (1)
setPowerState() ===>
Ethernet [IntelMausi]: switching to power state 1.
setPowerState() <===
enable() ===>
[IOBluetoothHostControllerUSBTransport][SetRemoteWakeUp] -- deviceRequest() failed: 0xE0005000 (0xe0005000 -- Unknown)
setMulticastMode() ===>
setMulticastMode() <===
enable() <===
setWakeOnMagicPacket() ===>
Ethernet [IntelMausi]: Wake on magic packet disabled.
setWakeOnMagicPacket() <===
setMulticastMode() ===>
setMulticastMode() <===
setMulticastList() ===>
setMulticastList() <===
getPacketFilters() ===>
getPacketFilters() <===
kPEDisableScreen 1
kPEEnableScreen 1
kPEEnableScreen 1
kPEDisableScreen 1
kPEEnableScreen 1
Ethernet [IntelMausi]: checkLinkStatus() returned 1.
Ethernet [IntelMausi]: EEE mode = 0x6000, adv=0x0006, lpa=0x0006
Ethernet [IntelMausi]: pollIntervalTime: 170us
Ethernet [IntelMausi]: Link up on en0, 1-Gigabit, Full-duplex, Rx/Tx flow-control, energy-efficient-ethernet
Ethernet [IntelMausi]: requireMaxBusStall(75000ns).
Ethernet [IntelMausi]: CTRL=0x58180240
Ethernet [IntelMausi]: CTRL_EXT=0x995a1027
Ethernet [IntelMausi]: STATUS=0x40080083
Ethernet [IntelMausi]: RCTL=0x04008002
Ethernet [IntelMausi]: PSRCTL=0x00040402
Ethernet [IntelMausi]: FCRTL=0x80005048
Ethernet [IntelMausi]: FCRTH=0x00005c20
Ethernet [IntelMausi]: RDLEN(0)=0x00002000
Ethernet [IntelMausi]: RDTR=0x00000000
Ethernet [IntelMausi]: RADV=0x00000000
Ethernet [IntelMausi]: RXCSUM=0x00002300
Ethernet [IntelMausi]: RFCTL=0x000380c0
Ethernet [IntelMausi]: RXDCTL(0)=0x00010000
Ethernet [IntelMausi]: RAL(0)=0xd5dc562c
Ethernet [IntelMausi]: RAH(0)=0x80007d42
Ethernet [IntelMausi]: MRQC=0x00370001
Ethernet [IntelMausi]: TARC(0)=0x0d800403
Ethernet [IntelMausi]: TARC(1)=0x45000403
Ethernet [IntelMausi]: TCTL=0x3103f0fa
Ethernet [IntelMausi]: TXDCTL(0)=0x01410000
Ethernet [IntelMausi]: TXDCTL(1)=0x01410000
Ethernet [IntelMausi]: TADV=0x0000001c
Ethernet [IntelMausi]: TIDV=0x0000001c
Ethernet [IntelMausi]: MANC=0x00000000
Ethernet [IntelMausi]: MANC2H=0x00000000
Ethernet [IntelMausi]: LTRV=0x88b988b9
Ethernet [IntelMausi]: PBA=0x0006001a
getPacketFilters() ===>
getPacketFilters() <===
setMulticastList() ===>
setMulticastList() <===
setMulticastList() ===>
setMulticastList() <===
setMulticastList() ===>
setMulticastList() <===
setMulticastList() ===>
setMulticastList() <===
setMulticastList() ===>
setMulticastList() <===
setMulticastList() ===>
setMulticastList() <===
SandboxViolation: fontd(273) deny(1) file-issue-extension /Network/Library
SandboxViolation: fontd(273) deny(1) file-issue-extension /Network/Library
setMulticastList() ===>
setMulticastList() <===
setMulticastList() ===>
setMulticastList() <===
BNBMouseDevice::setPowerState(0xf0be5ab5025d14e3, 0 -> 1) timed out after 10202 ms
BNBMouseDevice::setPowerState(0xf0be5ab5025d14e3, 0 -> 1) timed out after 10202 ms
IOHibernateSystemPostWake: Closing debugdata file
kern_close_file_for_direct_io
vnode_close(0)
****[IOBluetoothHIDDriver][handleWake] -- sending EXIT HID SUSPEND returned 0x0000 ****

**** [IOBluetoothHIDDriver][handleWake] -- acknowledgeSetPowerState() returned 0x0000 ****
Link to comment
Share on other sites

I knew this question would be posted here one day because Apple reworked logging in Sierra completely. In Terminal type

log show --predicate "processID == 0" --debug

in order to retrieve kernel logs. See "man log" for further information.

 

Mieze

 

Cheers Mieze, I will keep an eye on that. Shame Apple made it so awkward to see whats going on. (esp as my logs are apparently being spammed with "kernel: (Sandbox) SandboxViolation: com.apple.PhotoI(756) deny(1) mach-lookup com.apple.photoanalysisd" warnings). Amongst others.

Link to comment
Share on other sites

  • 2 weeks later...

I am jumping on this topic as I am still investigating my unstable Yosemite Hackintosh. The main suspect for hundreds of error messages in the logs ..

 

(from Windows_Server: surface testing not allowed, from iconserviceagent: crashes, from spinball-daemon: numerous messages indicating freezing of several apps for seconds)

 

... was always my frame buffer patches for my ATI RX290 graphics card. However I am observing a particular unstable system when I have mounted one or several disk shares (AFS) from my NAS or other network sources.

Thus I wonder whether the LAN driver AppleIntelE1000e.kext might be the culprit?  To be clear, booting is fine, OSX 10.10.5 works but from time to time it gets very laggy for no apparent reason.

Link to comment
Share on other sites

Thus I wonder whether the LAN driver AppleIntelE1000e.kext might be the culprit?  To be clear, booting is fine, OSX 10.10.5 works but from time to time it gets very laggy for no apparent reason.

Honestly, I don't understand how you relate the problems to IntelMausiEthernet.kext anyway?

 

Mieze

  • Like 1
Link to comment
Share on other sites

Honestly, I don't understand how you relate the problems to IntelMausiEthernet.kext anyway?

 

Mieze

 

And I would add most times I see these laggy networking post made it is always a GUI problem. Using a GUI method of transferring here when I see useless transfer speed killing it off and doing a rsync or scp most times results in better network transfer speed and no lagging in the Desktop GUI at all. Either that or they are expecting to saturate the network connection (usually gigabit) with hard drives in the system that will at best most times only do half that network connection speed when written too. And if running the OS on that same drive at the time of transfer then good luck on it not being laggy with all the drive I/O going on.

  • Like 1
Link to comment
Share on other sites

So do you use IntelMausiEthernet or AppleIntelE1000e?

AppleIntelE1000e is buggy while IntelMausiEthernet is really working fast and stable.

So if you still using AppleIntelE1000e i suggest to change it.

 

To your graphicsbug:

The HD4600 is a little bit tricky to configure, as special the framebuffer which need to be configured correctly (also a binpatch is suggested from my side) if you want it working 100%.

So i think there could be your problem.

Here is a old link which shows how the framebuffer is assembled: https://pikeralpha.wordpress.com/2014/08/20/yosemite-dp6-with-hd4600/

Link to comment
Share on other sites

Thanks @wastez but I am using the ATI R290X graphics card. I cannot enable the internal HD4600 graphics as I always get "memory allocation" errors during the Clover boot. I spend millions of hours searching the boards for the best Framebuffer patch. I now have one which is reasonable stable (with 2 monitors) but still shaky as described above.

 

Anyway, I replaced the AppleIntelE1000 with the IntelMaus Kext. It works but no difference to my problem. The search goes on... :unsure:

 

@Mieze: Because I see more freezes when connected to my LAN..

 

@MacUser: Even if it would be a "GUI Problem" I have to search for the cause. I am not building a Hackintosh for working from the command line.

Link to comment
Share on other sites

Thanks @wastez but I am using the ATI R290X graphics card. I cannot enable the internal HD4600 graphics as I always get "memory allocation" errors during the Clover boot. I spend millions of hours searching the boards for the best Framebuffer patch. I now have one which is reasonable stable (with 2 monitors) but still shaky as described above.

 

@MacUser: Even if it would be a "GUI Problem" I have to search for the cause. I am not building a Hackintosh for working from the command line.

 

I use two monitors connected to a HD4600 (for the hell of it tried three for testing all ports at once except vga all three worked fine) with only the inject Intel set in the clover config.plist with iMac14,2 system definition. I think it is the setting to 64mb for size for the graphics in the BIOS that is the key to it working correctly. You can search all you want it is the way the protocols are implemented in the operating system that is the problem something you will never be able to change. When I see junk 25-30MB/s transfer using gui killing it off and doing a rync or scp I get full speed 100+MB/s leaves no doubt in my mind that it is gui/protocol used in that gui operation at the time that is the problem, your loss if you want to spend that extra time waiting because your scared of the command line.

Link to comment
Share on other sites

  • 1 month later...

@arjanv

 

on the command line is easy - here is a simple example - pretty much what kextutil does:

sudo cp -r ~/Downloads/IntelMausiEthernet.kext /Library/Extensions
sudo chown -R 0:0 /Library/Extensions/IntelMausiEthernet.kext
sudo chmod -R g-w  /Library/Extensions/IntelMausiEthernet.kext
sudo kextcache -i /
Link to comment
Share on other sites

Hi,

 

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

 

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

 

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

 

Rgds,

Tom

Link to comment
Share on other sites

×
×
  • Create New...