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

IntelMausiEthernet.kext for Intel onboard LAN

973 posts in this topic

Recommended Posts

@mieze - 

 

update 1

 

nothing much in the log until VMware is started.

i installed the kext last evening. let it idle/run all night.

today I started VMware around noon today.

then shut the VM down after about 1 hour.

 

Note: ethernet was and is still working even so.

 

log attached from this:

cat /var/log/system.log | grep kernel > kernel.log

 

 

$ grep -i mausi /var/log/system.log

Feb 28 01:08:06 Toms-Mac kernel[0]: Ethernet [intelMausi]: Check tx ring for progress. txNumFreeDesc=1021

Feb 28 04:03:33 Toms-Mac kernel[0]: Ethernet [intelMausi]: Check tx ring for progress. txNumFreeDesc=1020

Feb 28 09:29:55 Toms-Mac kernel[0]: Ethernet [intelMausi]: Check tx ring for progress. txNumFreeDesc=1022

Feb 28 11:04:35 Toms-Mac kernel[0]: Ethernet [intelMausi]: Promiscuous mode enabled.

Feb 28 11:10:35 Toms-Mac kernel[0]: Ethernet [intelMausi]: Check tx ring for progress. txNumFreeDesc=1020

Feb 28 12:10:01 Toms-Mac kernel[0]: Ethernet [intelMausi]: Check tx ring for progress. txNumFreeDesc=1023

Feb 28 12:44:01 Toms-Mac kernel[0]: Ethernet [intelMausi]: Not enough descriptors. Stalling.

Feb 28 12:44:01 Toms-Mac kernel[0]: Ethernet [intelMausi]: Restart stalled queue!

Feb 28 12:44:10 Toms-Mac kernel[0]: Ethernet [intelMausi]: Not enough descriptors. Stalling.

Feb 28 12:44:10 Toms-Mac kernel[0]: Ethernet [intelMausi]: Restart stalled queue!

Feb 28 12:44:10 Toms-Mac kernel[0]: Ethernet [intelMausi]: Not enough descriptors. Stalling.

....

Feb 28 12:47:26 Toms-Mac kernel[0]: Ethernet [intelMausi]: Restart stalled queue!

Feb 28 12:47:28 Toms-Mac kernel[0]: Ethernet [intelMausi]: Not enough descriptors. Stalling.

Feb 28 12:47:28 Toms-Mac kernel[0]: Ethernet [intelMausi]: Restart stalled queue!

Feb 28 13:01:05 Toms-Mac kernel[0]: Ethernet [intelMausi]: Check tx ring for progress. txNumFreeDesc=1022

Feb 28 13:12:46 Toms-Mac kernel[0]: Ethernet [intelMausi]: Promiscuous mode disabled.

 

---

Update 2.

i reinstalled an older (but reliable) ethernet kext 2.4.14 and saw problems with VMware with this kext too.

but only when set to bridge mode vs NAT. this snipped below is what I was seeing with the vmware bridge mode (and E1000e 2.4.14 kext). 

 

so far retests with your -d5 kext with VMware in NAT mode are working fine. (so i think vmware networking has some issues ?)

note: i am running 10.10.3 pre-release.

 

Feb 28 18:42:58 Toms-Mac kernel[0]: vmnet: Port 2

Feb 28 18:42:58 Toms-Mac kernel[0]: vmnet: VNetUserIfFree: freeing userif8.

Feb 28 18:44:51 Toms-Mac kernel[0]: considerRebuildOfPrelinkedKernel com.insanelymac.driver.AppleIntelE1000e triggered rebuild

Feb 28 18:44:57 Toms-Mac kernel[0]: process vmware-vmx[842] caught causing excessive wakeups. Observed wakeups rate (per sec): 368; Maximum permitted wakeups rate (per sec): 150; Observation period: 300 seconds; Task lifetime number of wakeups: 45006

Feb 28 18:45:53 Toms-Mac kernel[0]: vmnet: Failed to shallow copy mbuf: 12.

Feb 28 18:45:53 Toms-Mac kernel[0]: vmnet: mbuf_tag_allocate failed: 35.

Feb 28 18:45:53 Toms-Mac kernel[0]: vmnet: Failed to shallow copy mbuf: 12.

Feb 28 18:45:53 Toms-Mac kernel[0]: vmnet: mbuf_tag_allocate failed: 35.

Feb 28 18:54:03 Toms-Mac.local com.apple.kextcache[910]: Created prelinked kernel copy "/System/Library/PrelinkedKernels/prelinkedkernel"

Feb 28 18:54:03 Toms-Mac.local com.apple.kextcache[910]: Created prelinked kernel "/System/Library/Caches/com.apple.kext.caches/Startup/kernelcache"

Feb 28 18:54:03 Toms-Mac.local com.apple.kextcache[910]: Created prelinked kernel using "/System/Library/Kernels/kernel"

Feb 28 18:54:18 Toms-Mac kernel[0]: vmnet: Failed to deep copy mbuf: 12.

Feb 28 18:54:18 Toms-Mac kernel[0]: vmnet: bridge-en0: SendToVNet copy failed: 12.

Feb 28 18:54:18 Toms-Mac kernel[0]: vmnet: Failed to deep copy mbuf: 12.

Feb 28 18:54:18 Toms-Mac kernel[0]: vmnet: bridge-en0: SendToVNet copy failed: 12.

Feb 28 18:54:20 Toms-Mac kernel[0]: vmnet: Failed to deep copy mbuf: 12.

Feb 28 18:54:20 Toms-Mac kernel[0]: vmnet: bridge-en0: SendToVNet copy failed: 12.

Feb 28 19:05:18 Toms-Mac kernel[0]: vmnet: Failed to deep copy mbuf: 12.

Feb 28 19:05:18 Toms-Mac kernel[0]: vmnet: bridge-en0: SendToVNet copy failed: 12.

Feb 28 19:05:18 Toms-Mac kernel[0]: vmnet: Failed to deep copy mbuf: 12.

Feb 28 19:05:18 Toms-Mac kernel[0]: vmnet: bridge-en0: SendToVNet copy failed: 12.

Feb 28 19:10:43 Toms-Mac kernel[0]: vmnet: VMNetDisconnect: called for port userListener0.

Feb 28 19:10:43 Toms-Mac kernel[0]: vmnet: VMNetDisconnect: called for port userif7.

Feb 28 19:10:43 Toms-Mac kernel[0]: en0: promiscuous mode disable succeeded

Feb 28 19:10:43 Toms-Mac kernel[0]: vmnet: bridge-en0: disabled promiscuous mode

Feb 28 19:10:43 Toms-Mac kernel[0]: vmnet: VNetUserIfFree: freeing userif7.

kernel.log.zip

Share this post


Link to post
Share on other sites
Advertisement

-d5 installed. I attempted to reproduce my VMWare issue by completing the Windows Update that I couldn't get through last time. Unfortunately (!) the update proceeded normally, without any issues. No issues logged by IntelMausi either during that process.
 
So I started up a Linux VM that's also overdue updates and is still configured for bridged networking. I ran its updates, while on OSX copying a batch of files to a remote NFS server (as before) *and* had the Windows VM still up as well, while I updated firefox and chrome.
 
It won't break. :-)
 
I realise this may actually not be good news; as you seemed to be indicating you don't think the problem is fixed yet, after reverting the -d4 change; only that we should see more debug output from IntelMausi when it happens. Oh well. :-) I'll keep using it normally.
 
The logs show more interesting stuff going on, even though as a user I didn't encounter any visible problems. Lots and lots of:
 
Feb 28 12:09:41 spitfire kernel[0]: Ethernet [intelMausi]: Not enough descriptors. Stalling.
Feb 28 12:09:41 spitfire kernel[0]: Ethernet [intelMausi]: Restart stalled queue!

Which I think coincides with the update running on Linux. The full log, although you'll quickly see it gets very repetitive (attached; when I foolishly pasted it into a code block it broke the topic for a while!)
 
That's where it stops, even though the Linux VM is still running; that's about when the software update had finished downloading.
 
At the top, the "Promiscuous mode enabled." happens as the Linux VM is starting up and, is disabled when that VM is shut down. The activity in the Windows VM caused, I think, nothing to be logged. I think even the replaceOrCopyPacket() occurred before Windows was started. (I probably should have been tailing it while I was doing it to be sure.)
 
The "Check tx ring for progress." messages at the very top are the last output from -d4 before the driver upgrade.

IntelMausi.log.zip

Share this post


Link to post
Share on other sites

I've been running D5 for the last 3 days and its been fine other than the occasional

01/03/2015 17:51:40.000 kernel[0]: Ethernet [IntelMausi]: Check tx ring for progress. txNumFreeDesc=1016

(where desc is a number between 1016 and 1023). However I haven't run VMWare at all.

Share this post


Link to post
Share on other sites

Hi Mieze,

 

With d5 version, I can't connect to iMessage nor FaceTime.

Revert to d3 and all is good anew.

 

Thanks for all your work.

Share this post


Link to post
Share on other sites

I've been running D5 for the last 3 days and its been fine other than the occasional

01/03/2015 17:51:40.000 kernel[0]: Ethernet [IntelMausi]: Check tx ring for progress. txNumFreeDesc=1016

(where desc is a number between 1016 and 1023). However I haven't run VMWare at all.

 

These occasional messages are lost interrupts and nothing to worry about. Under load the next interrupt will clear the condition and in idle mode the watchdog will do the job.

With d5 version, I can't connect to iMessage nor FaceTime.

Revert to d3 and all is good anew.

 

I can assure you that this is not a driver issue because I haven't changed anything which might affect iMessage or FaceTime. Strange things like this happen sometimes but they are usually a side effect caused by the installation process itself.

 

After all it seems that we are making progress. I will rework TSO6 too in order to prevent problems which may arise with VMware just to be on the save side.

 

Mieze

Share this post


Link to post
Share on other sites

Hi Mieze,

 

With d5 version, I can't connect to iMessage nor FaceTime.

Revert to d3 and all is good anew.

 

Thanks for all your work.

 

Same problem, here with d5 version.
And beside it, I also can't update apps on App Store.
I can't find d3 version here... would you mind to send it to me, please?
Thanks!!!

Share this post


Link to post
Share on other sites

 

Same problem, here with d5 version.
And beside it, I also can't update apps on App Store.
I can't find d3 version here... would you mind to send it to me, please?
Thanks!!!

 

 

Once again. This is not a driver issue. A driver handles packets and doesn't care where they come from or where they are going. It doesn't know anything about specific services which means that if specific services don't work, while others are working fine, search somewhere else because you are on a completely wrong track.

 

Mieze

Share this post


Link to post
Share on other sites

Once again. This is not a driver issue. A driver handles packets and doesn't care where they come from or where they are going. It doesn't know anything about specific services which means that if specific services don't work, while others are working fine, search somewhere else because you are on a completely wrong track.

 

Mieze

Mieze,
 
I just found it strange because I tried to install version d5 3 times and did not get iMessage, FaceTime and AppStore ... So I installed the version d4 and an old AppleIntelE1000e and everything worked the first time.
Version d3 gave me better speed and stability... well, at least was what I felt.
Anyway, I'll keep an eye on this new kext.
 
Thanks for your work!!!

Share this post


Link to post
Share on other sites

i too believe there may be a driver issue (even though you say there is not one) with regard to Message/FaceTime etc. i get a different response (network error can't connect) when logging in to Message with -d5 vs other drivers or interfaces. 

Share this post


Link to post
Share on other sites

Not had any app store apps get updates for ages. (so boring). However, with -d5, I seem to have no trouble downloading apps from the app store that I got in the past but didn't already have installed here.

Share this post


Link to post
Share on other sites

Not had any app store apps get updates for ages. (so boring). However, with -d5, I seem to have no trouble downloading apps from the app store that I got in the past but didn't already have installed here.

 

StrangeNoises,

 

Do you have iMessage and FaceTime working with -d5 ?

Share this post


Link to post
Share on other sites

Well, I also can't connect with Messages (no camera so facetime out anyway).

 

All I see is this sort of thing, which I agree doesn't look driver-ish:

Mar  4 18:13:28 spitfire.strangenoises.org identityservicesd[337]: [Warning] ====== IDS Traffic Usage:
Mar  4 18:13:28 spitfire.strangenoises.org identityservicesd[337]: [Warning] ====== Done
Mar  4 18:13:46 spitfire.strangenoises.org identityservicesd[337]: [Warning] FTMessageDelivery failed! (HTTP Status Code: 0) Error (NSURLErrorDomain:-1001): The request timed out. https://profile.ess.apple.com/WebObjects/VCProfileService.woa/wa/idsGetHandles
Mar  4 18:14:16 --- last message repeated 3 times ---

And also vaguely relevant?

Mar  4 18:16:27 spitfire com.apple.xpc.launchd[1] (com.apple.imfoundation.IMRemoteURLConnectionAgent): The _DirtyJetsamMemoryLimit key is not available on this platform.

Then right after quitting the Messages app:

Mar  4 18:18:31 spitfire.strangenoises.org CoreServicesUIAgent[30065]: unexpected message <OS_xpc_error: <error: 0x7fff76423c60> { count = 1, contents =
        "XPCErrorDescription" => <string: 0x7fff76423f70> { length = 18, contents = "Connection invalid" }
    }>
Mar  4 18:18:36 spitfire.strangenoises.org identityservicesd[337]: <IMMacNotificationCenterManager: 0x7fb84ca0f9e0>:    NC Disabled: NO
Mar  4 18:18:36 spitfire.strangenoises.org identityservicesd[337]: <IMMacNotificationCenterManager: 0x7fb84ca0f9e0>:   DND Enabled: NO
Mar  4 18:18:36 spitfire.strangenoises.org identityservicesd[337]: <IMMacNotificationCenterManager: 0x7fb84ca0f9e0>: Updating enabled: YES   (Topics: (
        "com.apple.private.alloy.icloudpairing",
        "com.apple.private.alloy.continuity.encryption",
        "com.apple.private.alloy.continuity.activity",
        "com.apple.madrid",
        "com.apple.private.ids",
        "com.apple.private.alloy.phonecontinuity",
        "com.apple.private.alloy.continuity.activity.public",
        "com.apple.private.alloy.continuity.auth",
        "com.apple.private.alloy.idsremoteurlconnection",
        "com.apple.private.alloy.sms",
        "com.apple.private.alloy.screensharing",
        "com.apple.private.alloy.maps",
        "com.apple.private.alloy.callhistorysync",
        "com.apple.private.alloy.continuity.tethering"
    ))
Mar  4 18:18:36 spitfire kernel[0]: setMulticastList() ===>
Mar  4 18:18:36 spitfire kernel[0]: setMulticastList() <===
Mar  4 18:18:37 spitfire.strangenoises.org identityservicesd[337]: [Warning] Broadcasting no devices for account IDSDAccount: 0x7fb84c929210 [Service: IDSDService: 0x7fb849d15a30 [Identifier: com.apple.private.alloy.sms Display Name: SMSRelay Topic: com.apple.private.alloy.sms   Service: com.apple.private.alloy.sms   Protocol: com.apple.private.alloy] Login: rachel@strangenoises.org UniqueID: 3CEB67DB-B342-4CB4-BF94-7FC7DF18A3F7 Account Type: Apple ID Registration: (null)  Registered: YES  Linked Accounts: (null)] even though we have some
Mar  4 18:18:37 --- last message repeated 1 time ---
Mar  4 18:18:37 spitfire.strangenoises.org identityservicesd[337]: [Warning] Broadcasting no devices for account IDSDAccount: 0x7fb84c92aa90 [Service: IDSDService: 0x7fb849d15a30 [Identifier: com.apple.private.alloy.sms Display Name: SMSRelay Topic: com.apple.private.alloy.sms   Service: com.apple.private.alloy.sms   Protocol: com.apple.private.alloy] Login: rachel@strangenoises.org UniqueID: 5925C0DF-277D-45B3-8BD9-C8FC8C51EDBB Account Type: Apple ID Registration: (null)  Registered: YES  Linked Accounts: (null)] even though we have some
Mar  4 18:18:37 --- last message repeated 1 time ---
Mar  4 18:18:37 spitfire.strangenoises.org identityservicesd[337]: [Warning] Broadcasting no devices for account IDSDAccount: 0x7fb84c92ba70 [Service: IDSDService: 0x7fb849d15a30 [Identifier: com.apple.private.alloy.sms Display Name: SMSRelay Topic: com.apple.private.alloy.sms   Service: com.apple.private.alloy.sms   Protocol: com.apple.private.alloy] Login: rachel@strangenoises.org UniqueID: C05007DD-E367-46D3-A3D5-10158BC8487D Account Type: Apple ID Registration: (null)  Registered: YES  Linked Accounts: (null)] even though we have some
Mar  4 18:18:37 --- last message repeated 1 time ---
Mar  4 18:18:37 spitfire.strangenoises.org identityservicesd[337]: [Warning] Broadcasting no devices for account IDSDAccount: 0x7fb84c92cc30 [Service: IDSDService: 0x7fb849d15a30 [Identifier: com.apple.private.alloy.sms Display Name: SMSRelay Topic: com.apple.private.alloy.sms   Service: com.apple.private.alloy.sms   Protocol: com.apple.private.alloy] Login: rachel@strangenoises.org UniqueID: C377B76F-22C0-471E-924E-444C9602B7BF Account Type: Apple ID Registration: (null)  Registered: YES  Linked Accounts: (null)] even though we have some
Mar  4 18:18:37 --- last message repeated 1 time ---
Mar  4 18:18:37 spitfire.strangenoises.org identityservicesd[337]: [Warning] Broadcasting no devices for account IDSDAccount: 0x7fb84c92ebf0 [Service: IDSDService: 0x7fb849d15a30 [Identifier: com.apple.private.alloy.sms Display Name: SMSRelay Topic: com.apple.private.alloy.sms   Service: com.apple.private.alloy.sms   Protocol: com.apple.private.alloy] Login: rachel@strangenoises.org UniqueID: C7839CB8-5EA2-45B9-B65F-BC0A9AABBF92 Account Type: Apple ID Registration: (null)  Registered: YES  Linked Accounts: (null)] even though we have some
Mar  4 18:18:37 --- last message repeated 1 time ---
Mar  4 18:18:37 spitfire.strangenoises.org identityservicesd[337]: [Warning] Broadcasting no devices for account IDSDAccount: 0x7fb84c92f620 [Service: IDSDService: 0x7fb849d15a30 [Identifier: com.apple.private.alloy.sms Display Name: SMSRelay Topic: com.apple.private.alloy.sms   Service: com.apple.private.alloy.sms   Protocol: com.apple.private.alloy] Login: rachel@strangenoises.org UniqueID: 0875E127-4749-422B-86F2-11595AAB8A9C Account Type: Apple ID Registration: (null)  Registered: YES  Linked Accounts: (null)] even though we have some
Mar  4 18:18:37 --- last message repeated 1 time ---
Mar  4 18:18:37 spitfire imagent[22277]: notify name "ids-device-nearby-51AE1C49-D96B-4F94-AF08-299E174C4457" has been registered 20 times - this may be a leak
Mar  4 18:18:37 spitfire.strangenoises.org identityservicesd[337]: [Warning] Broadcasting no devices for account IDSDAccount: 0x7fb84c92fce0 [Service: IDSDService: 0x7fb849d15a30 [Identifier: com.apple.private.alloy.sms Display Name: SMSRelay Topic: com.apple.private.alloy.sms   Service: com.apple.private.alloy.sms   Protocol: com.apple.private.alloy] Login: rachel@strangenoises.org UniqueID: B849585E-ADED-4C57-90F0-D6234968C56E Account Type: Apple ID Registration: (null)  Registered: YES  Linked Accounts: (null)] even though we have some
Mar  4 18:18:37 spitfire imagent[22277]: notify name "ids-device-nearby-07EE8147-AC14-48C4-9D50-FC509EB9B1C5" has been registered 20 times - this may be a leak
Mar  4 18:18:37 spitfire.strangenoises.org identityservicesd[337]: [Warning] Broadcasting no devices for account IDSDAccount: 0x7fb84c92fce0 [Service: IDSDService: 0x7fb849d15a30 [Identifier: com.apple.private.alloy.sms Display Name: SMSRelay Topic: com.apple.private.alloy.sms   Service: com.apple.private.alloy.sms   Protocol: com.apple.private.alloy] Login: rachel@strangenoises.org UniqueID: B849585E-ADED-4C57-90F0-D6234968C56E Account Type: Apple ID Registration: (null)  Registered: YES  Linked Accounts: (null)] even though we have some
Mar  4 18:18:37 spitfire.strangenoises.org identityservicesd[337]: [Warning] Broadcasting no devices for account IDSDAccount: 0x7fb84c930760 [Service: IDSDService: 0x7fb849d15a30 [Identifier: com.apple.private.alloy.sms Display Name: SMSRelay Topic: com.apple.private.alloy.sms   Service: com.apple.private.alloy.sms   Protocol: com.apple.private.alloy] Login: rachel@strangenoises.org UniqueID: 5F92E2AB-79A3-4437-B9C2-A89220D86C70 Account Type: Apple ID Registration: (null)  Registered: YES  Linked Accounts: (null)] even though we have some
Mar  4 18:18:37 --- last message repeated 1 time ---
Mar  4 18:18:37 spitfire.strangenoises.org identityservicesd[337]: [Warning] Broadcasting no devices for account IDSDAccount: 0x7fb84c930c20 [Service: IDSDService: 0x7fb849d15a30 [Identifier: com.apple.private.alloy.sms Display Name: SMSRelay Topic: com.apple.private.alloy.sms   Service: com.apple.private.alloy.sms   Protocol: com.apple.private.alloy] Login: rachel@strangenoises.org UniqueID: 0C44FE94-3C9C-4352-A40F-4C9E2C0CB4C1 Account Type: Apple ID Registration: (null)  Registered: YES  Linked Accounts: (null)] even though we have some
Mar  4 18:18:37 --- last message repeated 1 time ---
Mar  4 18:18:37 spitfire.strangenoises.org identityservicesd[337]: [Warning] Broadcasting no devices for account IDSDAccount: 0x7fb84c92aec0 [Service: IDSDService: 0x7fb849d15a30 [Identifier: com.apple.private.alloy.sms Display Name: SMSRelay Topic: com.apple.private.alloy.sms   Service: com.apple.private.alloy.sms   Protocol: com.apple.private.alloy] Login: rachel@strangenoises.org UniqueID: 5915D3F1-267A-4850-A4A4-0316F29D639D Account Type: Apple ID Registration: (null)  Registered: YES  Linked Accounts: (null)] even though we have some
Mar  4 18:18:37 --- last message repeated 1 time ---
Mar  4 18:18:37 spitfire.strangenoises.org identityservicesd[337]: [Warning] Broadcasting no devices for account IDSDAccount: 0x7fb84c92e120 [Service: IDSDService: 0x7fb849d15a30 [Identifier: com.apple.private.alloy.sms Display Name: SMSRelay Topic: com.apple.private.alloy.sms   Service: com.apple.private.alloy.sms   Protocol: com.apple.private.alloy] Login: rachel@strangenoises.org UniqueID: 07E25836-ECFF-414D-9E16-A3E3886B832A Account Type: Apple ID Registration: (null)  Registered: YES  Linked Accounts: (null)] even though we have some
Mar  4 18:18:37 --- last message repeated 1 time ---
Mar  4 18:18:37 spitfire.strangenoises.org identityservicesd[337]: [Warning] Broadcasting no devices for account IDSDAccount: 0x7fb84c932650 [Service: IDSDService: 0x7fb849d15a30 [Identifier: com.apple.private.alloy.sms Display Name: SMSRelay Topic: com.apple.private.alloy.sms   Service: com.apple.private.alloy.sms   Protocol: com.apple.private.alloy] Login: rachel@strangenoises.org UniqueID: D2AE1C71-62E4-44B6-889B-AF6E4CF250C8 Account Type: Apple ID Registration: (null)  Registered: YES  Linked Accounts: (null)] even though we have some
Mar  4 18:18:37 --- last message repeated 1 time ---
Mar  4 18:18:37 spitfire.strangenoises.org identityservicesd[337]: [Warning] Broadcasting no devices for account IDSDAccount: 0x7fb84c934480 [Service: IDSDService: 0x7fb849d15a30 [Identifier: com.apple.private.alloy.sms Display Name: SMSRelay Topic: com.apple.private.alloy.sms   Service: com.apple.private.alloy.sms   Protocol: com.apple.private.alloy] Login: rachel@strangenoises.org UniqueID: 52BE9B18-E0D0-4B96-B0B8-C752663B0AF2 Account Type: Apple ID Registration: (null)  Registered: YES  Linked Accounts: (null)] even though we have some
Mar  4 18:18:37 --- last message repeated 1 time ---
Mar  4 18:18:37 spitfire imagent[22277]: notify name "ids-device-nearby-51AE1C49-D96B-4F94-AF08-299E174C4457" has been registered 40 times - this may be a leak
Mar  4 18:18:37 spitfire imagent[22277]: notify name "ids-device-nearby-07EE8147-AC14-48C4-9D50-FC509EB9B1C5" has been registered 40 times - this may be a leak

I still don't know how this can be driver-based - AFAICT it's happening at HTTP level - but maybe they have some kind of device id thing going on for security that it's falling afoul of?


Interestingly perhaps, despite my apparent failure to log in, I just got the notification from Apple that "Your Apple ID (...) was used to sign into iMessage on an iMac 27" named "spitfire".

 

So it *was* talking, but not completing for some reason. But *some* communication was going on.

 

... and now I launch Messages again and it all seems to be working. though i don't have anyone to try actually talking to (because I never use this! whenever i used messages/ichat in the past it was just as a jabber client for google,which i'm guessing won't prove anything) but it seems to be started up and communicating to the server OK now.

 

Whatever's going on here, I have to concur it really doesn't look like a driver issue!

Share this post


Link to post
Share on other sites

I ran some additional tests this evening without finding evidence for a driver issue. Everything was working as expected. Nevertheless I used this opportunity to complete the missing lines of code needed for WoL support which is now working (1.0.0d6) on my test machine too.

 

You can find version 1.0.0d6 attached to post #1 of this thread.

 

Good luck!

 

Mieze  :cat:

Share this post


Link to post
Share on other sites

@ mieze

I also had problems with imessage (but not with login), sometimes after sleep it takes some time to send the first message on d5, i´ve to test this with the newest driver.

Maybe a Broad/Multicast Problem combined with the sms option? I can´t imagine what it else could be because like you said it just send/receives packages.

Maybe it was a unhappy coincidence.

 

I will test this, check the logs and will inform you if i know some more details.

 

PS: WOL is working great.

Share this post


Link to post
Share on other sites

This is some kind of nice to have but i prefer using AppleIntelE1000.kext

 

@Mietze 

soll deine Katze in Frieden ruhen  :bye:

 

happy hacking

 

OSBeast

Share this post


Link to post
Share on other sites

This is some kind of nice to have but i prefer using AppleIntelE1000.kext

 

@Mietze 

soll deine Katze in Frieden ruhen  :bye:

 

happy hacking

 

OSBeast

This one is much faster the the old one.

Share this post


Link to post
Share on other sites

I pushed the source code to GitHub last weekend. It can be found here: http://github.com/Mieze/IntelMausiEthernet

 

Mieze

Yep, fetched it from there yesterday and built it, as the forum was down. My build may be slightly different though as (when prompted by xcode) i selected options to make it build yosemite-only. All seems to be happy and working though.

Share this post


Link to post
Share on other sites

Oh excellent we're back and thanks for putting this on Github. I came looking for the driver at the weekend and was thrown by the site being down.

Share this post


Link to post
Share on other sites

Can't seem to find the kext on the link from the top message, it says it's not there.  I found the source code at github, but am not sure how to complie it.  Can you check on the link from the top message?

 

Thanks

Mark

Share this post


Link to post
Share on other sites

Can't seem to find the kext on the link from the top message, it says it's not there.  I found the source code at github, but am not sure how to complie it.  Can you check on the link from the top message?

 

Yeah, I was already wondering why the number of downloads didn't increase after the site was restored. I removed the old archive and uploaded the latest version of the driver again. I hope the issue is resolved now.

 

Mieze  :cat:

Share this post


Link to post
Share on other sites

Yeah, I was already wondering why the number of downloads didn't increase after the site was restored. I removed the old archive and uploaded the latest version of the driver again. I hope the issue is resolved now.

 

Mieze  :cat:

 

Got it.  Will drop it in tonight and see if I can get my network card working.

 

Thanks for all the work on this.

 

Mark

Share this post


Link to post
Share on other sites

  • Recently Browsing   0 members

    No registered users viewing this page.

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