Jump to content
  • Announcements

    • Allan

      Forum Rules   04/13/2018

      Hello folks! As some things are being fixed, we'll keep you updated. Per hour the Forum Rules don't have a dedicated "Tab", so here is the place that we have our Rules back. New Users Lounge > [READ] - InsanelyMac Forum Rules - The InsanelyMac Staff Team. 
hnak

AppleIntelE1000e.kext for 10.8/10.7/10.6/10.5

767 posts in this topic

Recommended Posts

Updated to 3.0.4.1 according to the minor changes in the original e1000 driver project.

 

I was informed of some mbuf leaks - it may cause system errors in heavy traffic (failed getPhysicalSegment call.), but I have not figured it out .

Share this post


Link to post
Share on other sites

@hnak any idea why Lnx2Mac's RealtekRTL81xx.kext would be able to wake up a B75 on OSX 10.9.0 gigabyte board via WOL by just installing the kext and using tony's installer to install OSX, but your AppleIntelE1000e.kext v2.5.4d would not wake up a 10.9.2 Gigabyte Z87 via WOL using your kext and just tony's installer to install OSX?

Share this post


Link to post
Share on other sites

@hnak any idea why Lnx2Mac's RealtekRTL81xx.kext would be able to wake up a B75 on OSX 10.9.0 gigabyte board via WOL by just installing the kext and using tony's installer to install OSX, but your AppleIntelE1000e.kext v2.5.4d would not wake up a 10.9.2 Gigabyte Z87 via WOL using your kext and just tony's installer to install OSX?

RealtekRTL81xx (Realtek chipset)IS NOT AppleIntelE1000e (Intel chipset) thats why :D

Share this post


Link to post
Share on other sites

RealtekRTL81xx (Realtek chipset)IS NOT AppleIntelE1000e (Intel chipset) thats why :D

Really? If you don't have any idea please refrain from stating the obvious, come on now lol :P

 

@HNAK <------------ any idea why Lnx2Mac's RealtekRTL81xx.kext would be able to wake up a B75 on OSX 10.9.0 gigabyte board via WOL by just installing the kext and using tony's installer to install OSX, but your AppleIntelE1000e.kext v2.5.4d would not wake up a 10.9.2 Gigabyte Z87 via WOL using your kext and just tony's installer to install OSX?

Share this post


Link to post
Share on other sites

Really? If you don't have any idea please refrain from stating the obvious, come on now lol :P

 

@HNAK <------------ any idea why Lnx2Mac's RealtekRTL81xx.kext would be able to wake up a B75 on OSX 10.9.0 gigabyte board via WOL by just installing the kext and using tony's installer to install OSX, but your AppleIntelE1000e.kext v2.5.4d would not wake up a 10.9.2 Gigabyte Z87 via WOL using your kext and just tony's installer to install OSX?

Thats clearer than water :D

Share this post


Link to post
Share on other sites

@hnak any idea why Lnx2Mac's RealtekRTL81xx.kext would be able to wake up a B75 on OSX 10.9.0 gigabyte board via WOL by just installing the kext and using tony's installer to install OSX, but your AppleIntelE1000e.kext v2.5.4d would not wake up a 10.9.2 Gigabyte Z87 via WOL using your kext and just tony's installer to install OSX?

 

I fixed WOL for the AppleIntelE1000e.kext in a patched 2.5.4f, see #1988601 and #1993817

@hnak, could you have a look at this and maybe add it to the next 3.x update?

Share this post


Link to post
Share on other sites

Updated to 3.0.4.1 according to the minor changes in the original e1000 driver project.

 

I was informed of some mbuf leaks - it may cause system errors in heavy traffic (failed getPhysicalSegment call.), but I have not figured it out .

 

Increase the maximum number of segments for the getPhysicalSegment call to 40 in order to avoid this error. I had the same issue with my Realtek driver and was able to resolve the problem this way.

 

Mieze

Share this post


Link to post
Share on other sites

I fixed WOL for the AppleIntelE1000e.kext in a patched 2.5.4f, see #1988601 and #1993817

@hnak, could you have a look at this and maybe add it to the next 3.x update?

I have added your code into source.

Increase the maximum number of segments for the getPhysicalSegment call to 40 in order to avoid this error. I had the same issue with my Realtek driver and was able to resolve the problem this way.

 

Mieze

I increased the number to 40.

 

Thank you for suggestions.

Share this post


Link to post
Share on other sites

WOL SUCCESS! http://wikisend.com/....1000e.kext.zip once I used this in place of the original it worked perfectly. Also port 5900 was open on my router causing constant wakes but that was after I had installed the new kext into the IONetworkingFamily.kext contents/plugins folder due to constant hackers trying to VNC into my hack. I used kext utility after the kext was installed, closed that port, rebooted then everything worked perfect. THANKYOU @diddl14!

 

Also @rals2007 thanks for providing absolutely nothing of importance go drink some clear water you need it  :D

Share this post


Link to post
Share on other sites

Updated to 3.0.4.1 according to the minor changes in the original e1000 driver project.

 

I was informed of some mbuf leaks - it may cause system errors in heavy traffic (failed getPhysicalSegment call.), but I have not figured it out .

Good job!

3.0.4.1 Works great for me! Today i was running twitch on source quality and make large data transfer in home network and all ok.

 

Edit:

I just tried run the torrent, and after five minutes +/- it dropped again. :-/

But i think it is better than before, but torrent cant stand.

Share this post


Link to post
Share on other sites

just tested this latest with copying some large stuff over afp @ another machine in my lan, after a while i get the kernel[0]: failed to getphysicalsegment in outputPacket. And then it stalls

are there any workarounds for this? Cause the driver works fine otherwise..

Share this post


Link to post
Share on other sites

Hey guys,

 

i trie to get WoL working with Mavericks 10.9.2 on my Gigabyte Z87mx. 

 

With the appleintele1000.kext from page 28 i got it working ONE time but the second, third, fourth and so on... time it doesn't work any more.

 

Maybe someone have an idea or a pre patched working .kext for me.

 

greets

 

p.s. wol in bios is activated, rep is deactivated and wol is activated in energy saver settings

Share this post


Link to post
Share on other sites

I have the same board and it's working fine so the issue is probably either with the configuration or the network, not the driver.

 

Some suggestions on what you could check:

 

What driver version is current installed?

 

Are the lights on the ethernet port blinking?

 

How do you wake the system up?

 

When it is sleeping, check the the ip and arp table on your router - it might be an issue with a sleep proxy http://en.wikipedia.org/wiki/Bonjour_Sleep_Proxy

 

Anything in the console log after you wake it up manually?

 

Hope this helps..

Share this post


Link to post
Share on other sites

I have tried 2.5.x f and the new Version 3

 

I wake my System through fritzbox, MacBook (ssh), iphone (ishutdown) or on demand with ATV.

 

If the pc is sleeping i See it in the Finder on my MacBook and in the fritzbox it is connected.

 

I dont Check the console. I try it tomorrow.

 

Thx and greets

Share this post


Link to post
Share on other sites

 

just tested this latest with copying some large stuff over afp @ another machine in my lan, after a while i get the kernel[0]: failed to getphysicalsegment in outputPacket. And then it stalls

are there any workarounds for this? Cause the driver works fine otherwise..

 

I have the same problem as above. This is when copying files TO the server. Copying files from the server doesn't output these messages. After a while of copying to the server, say 15GB the AppleIntelEthernet device hangs and the network goes down. Would be happy if someone knew a workaround!

 

Edit:

I'm using an Asus Z87 MAXIMUS VI GENE board with the internal NIC Intel i217

Share this post


Link to post
Share on other sites

I have added your code into source.

I increased the number to 40.

 

Thank you for suggestions.

Any updates on when this new version will be available?

Share this post


Link to post
Share on other sites

I compiled the latest version on Mavericks. It's 64-bit only.

 

Hopefully it works ok. I haven't checked as I'm still on 2.4.14 here.

I can confirm that this works with 10.9.2 & a Gigabyte UD7-TH Motherboard. No more issues with large file transfers.

 

If you are running a iSCSI based SAN, this is the driver to use. Very smooth & reliable transfers.

Share this post


Link to post
Share on other sites

I compiled the latest version on Mavericks. It's 64-bit only.

 

Hopefully it works ok. I haven't checked as I'm still on 2.4.14 here.

 

 

I can confirm that this works with 10.9.2 & a Gigabyte UD7-TH Motherboard. No more issues with large file transfers.

 

If you are running a iSCSI based SAN, this is the driver to use. Very smooth & reliable transfers.

 

 

I can also confirm that on 10.9.2 and an Asus P8P67 Pro, that I also have no more issues with large file transfers using Riley Freeman's compiled version.  Thanks!

 

EDIT:  Ends up that it still crashes, more stable than the 2.5.4 option, but alas no go. Back to 2.4.14 here.

Share this post


Link to post
Share on other sites

I compiled the latest version on Mavericks. It's 64-bit only.

 

Hopefully it works ok. I haven't checked as I'm still on 2.4.14 here.

 

I'm still experiencing hang errors while transferring 200GB or bigger directories to other (OSX) computers.

 

My mobo is a GA-X79-UP4, I'm on OSX 10.9.2

 

I have repaired permissions, tried to install the kext into the plugin directory and also directly into the extensions directory, tried to boot with -f, nothing seems to work, it also hang randomly, some times after transferring 20gb other when just transferring a few MB.

Share this post


Link to post
Share on other sites

looks like disabling TSO might help in the errors when doing large transfers, it can be done with a sysctl switch but i guess that would turn it off on all interfaces, so I'm trying to do this via ifconfig and the -mediaopts switch, i messed around with this before for turning on/off functions like avb and eee (energy efficient ethernet) now it seems it won't let me set any options or I'm using the wrong syntax. If anyone cares the sysctl switch i mentioned is net.inet.tcp.tso (defaults to 1) 

Share this post


Link to post
Share on other sites

Hello, i'm sorry for my newbish question, but is this driver supposed to enable the intel i218v ? Because every time i enable the Lan in bios it just hangs at the line "changing mtu from 0 to 1500", if i disable the ethernet port in bios it works just fine, very weird...

 

Thank you!

Share this post


Link to post
Share on other sites

Hello, i'm sorry for my newbish question, but is this driver supposed to enable the intel i218v ? Because every time i enable the Lan in bios it just hangs at the line "changing mtu from 0 to 1500", if i disable the ethernet port in bios it works just fine, very weird...

 

Thank you!

I forgot to add those new ID values in my last change. I uploaded the new build.

I hope mbuf leak problem is alleviated, too.

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.

×