Jump to content

IntelMausiEthernet.kext for Intel onboard LAN


981 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

-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

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.

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

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!!!

 

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

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!!!

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. 

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 ?

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!

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:

@ 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.

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.

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

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:

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

×
×
  • Create New...