Jump to content
hnak

AppleIntelE1000e.kext for 10.8/10.7/10.6/10.5

768 posts in this topic

Recommended Posts

If you care to test, you can easily prove that swapping the buried kext does not trigger a proper rebuild of the cache,

Of course it doesn't, and I never claimed it did. You have to trigger a cache rebuild the way documented by Apple ('touch /System/Library/Extensions')

 

As to the location of the kext, I put it where Apple puts it, also as recommended at the beginning of this discussion. Enough said.

Apple does not put AppleIntelE1000e.kext anywhere. I prefer not to bury hackintosh kexts in native kext PlugIn directories. You can have a difference of opinion. We will agree to disagree.

 

The discussion that I replied to was regarding how to make Ethernet kexts work when installed to EFI/Clover/kexts.

Share this post


Link to post
Share on other sites
Advertisement

I would suggest to open up a new thread in order to discuss the best way to install a kext as this might be of interest to all users, not only those using AppleIntelE1000e.kext, and it would help to stick on the subject.

 

:cat:

Share this post


Link to post
Share on other sites

I would suggest to open up a new thread in order to discuss the best way to install a kext as this might be of interest to all users, not only those using AppleIntelE1000e.kext, and it would help to stick on the subject.

 

:cat:

In my mind, the discussion is over. No need to open a thread. If the mods want to move the posts, so be it.

Share this post


Link to post
Share on other sites

Can somebody have a look on the AppleIntelE1000e.kext.

Because since 10.9.5 and 10.10 sometimes the network gets broken after some time fast afp transfer.

The OS Versions before had no problem with it.

Share this post


Link to post
Share on other sites

Can somebody have a look on the AppleIntelE1000e.kext.

Because since 10.9.5 and 10.10 sometimes the network gets broken after some time fast afp transfer.

The OS Versions before had no problem with it.

FWIW I don't use AFP on my network (any more) so if it was the change that fixed my issue that's causing this, I won't have encountered it.

 

(That said, I'm not sure that change is in the general release yet, is it? I'm still running the quickly-fixed version mieze made for me :) )

Share this post


Link to post
Share on other sites

Can somebody have a look on the AppleIntelE1000e.kext.

Because since 10.9.5 and 10.10 sometimes the network gets broken after some time fast afp transfer.

The OS Versions before had no problem with it.

 

Please provide us with a log file showing the problem so that we have a starting point to track down the issue.

:cat:

Share this post


Link to post
Share on other sites

In Wireshark this is the only thing what i get (but really often, the hole log is full with it):  Reasmmebly Error, protocol TCP: New fragment overlaps old data (retransmission?)

 

But also had to say that i didn´t get the error until now. (whats totaly typical)

Share this post


Link to post
Share on other sites

In Wireshark this is the only thing what i get:  Reasmmebly Error, protocol TCP: New fragment overlaps old data (retransmission?)

 

But also had to say that i didn´t get the error until now. (whats totaly typical)

 

Looks more like a bug in Yosemite's network stack than in the driver? Anyway, it doesn't shed a good light on Apple's new OS.

 

:cat:

Share this post


Link to post
Share on other sites

Hey, I'm currently working on a Nuc with I218V Lan card. My Problem occurs only after wake from sleep. WOL or USB Wake works fine, but with every wake the ethernet connection is lost until a reboot. I tried the 3.1.0 as well as the 2.5.4 neither of them is solving the problem. With my other build on a i217 i had none of these problems.

 

Someone has an idea of the cause?

Share this post


Link to post
Share on other sites

Hey, I'm currently working on a Nuc with I218V Lan card. My Problem occurs only after wake from sleep. WOL or USB Wake works fine, but with every wake the ethernet connection is lost until a reboot. I tried the 3.1.0 as well as the 2.5.4 neither of them is solving the problem. With my other build on a i217 i had none of these problems.

 

Someone has an idea of the cause?

My H97M Pro4 (i218v2) works after waking up, though it may depend on how deep your sleep setting is.

Share this post


Link to post
Share on other sites

I now tried to disable NETIF_F_TSO.

Now the e1000_tx_map: failed to getphysicalsegment errors are gone.

Also the transferspeed over afp (writing on server) increases from 30 - 60 MB/s to 60 - 100 MB/s which is very good.

 

The strange thing is that iperf (tx) shows just between 450 - 550 Mbit/s instead of 850 - 900 Mbit/s.

iperf (rx) is the same value. (about 940 Mbit/s)

 

Can somebody help me with it?

 

@ Mieze 

Do you know if TSO4 is working as it should on the last version of this driver?

 

 

If i enable TSO and try to transfer over smb it is limited to 2 - 5 MB/s tx, which is incredible slow.

 

Wireshare shows a lot of retransmissions and out of order errors.

 

Edit:

Nobody is able to help here?

Edited by wastez

Share this post


Link to post
Share on other sites

My question might sound stupid, but does the AppleIntelE1000e.kext v.3.0.1 in the very first post will run and recognise i218v (0x15a18086) in 10.10 (Yosemite)?

Share this post


Link to post
Share on other sites

Yosemite:

VER 3.1.0 stopped work after huge transfere data from network (doing fist time machine backup)

After transfere 200 of 600GB the driver stopped work. Only restart fixed.

Back to 2.4.14 - by far the most stable driver for my intel network until now, could transfer the remaining 400 gb to time capsule without any driver crash

Share this post


Link to post
Share on other sites

Yosemite:

VER 3.1.0 stopped work after huge transfere data from network (doing fist time machine backup)

After transfere 200 of 600GB the driver stopped work. Only restart fixed.

Back to 2.4.14 - by far the most stable driver for my intel network until now, could transfer the remaining 400 gb to time capsule without any driver crash

Have you set TSO to off ?

Share this post


Link to post
Share on other sites

Trying to install Intel I218-V (0x15a18086) under Yosemite with AppleIntelE1000e.kext (v.3.0.1) and this is my experience so far:

 

1. AppleIntelE1000e.kext in /S/L/E/IONetworkingFamily.kext/Plugins/, repaired permissions and rebuilt cache

if NETIF_F_TSO=false then Yosemite boots, but there's no Ethernet adapter recognised...

 

2. AppleIntelE1000e.kext in /S/L/E/IONetworkingFamily.kext/Plugins/, repaired permissions and rebuilt cache

if NETIF_F_TSO=true then Yosemite hangs on this screen:

21eyes4.jpg

 

 

Suggestions and advices are appreciated and welcome :)

Share this post


Link to post
Share on other sites

Trying to install Intel I218-V (0x15a18086) under Yosemite with AppleIntelE1000e.kext (v.3.0.1) and this is my experience so far:

 

1. AppleIntelE1000e.kext in /S/L/E/IONetworkingFamily.kext/Plugins/, repaired permissions and rebuilt cache

if NETIF_F_TSO=false then Yosemite boots, but there's no Ethernet adapter recognised...

 

2. AppleIntelE1000e.kext in /S/L/E/IONetworkingFamily.kext/Plugins/, repaired permissions and rebuilt cache

if NETIF_F_TSO=true then Yosemite hangs on this screen:

...

As NETIF_F_TSO flag is read after the driver is loaded, it has nothing to do with adapter recognition.

Share this post


Link to post
Share on other sites

Trying to install Intel I218-V (0x15a18086) under Yosemite with AppleIntelE1000e.kext (v.3.0.1) and this is my experience so far:

 

1. AppleIntelE1000e.kext in /S/L/E/IONetworkingFamily.kext/Plugins/, repaired permissions and rebuilt cache

if NETIF_F_TSO=false then Yosemite boots, but there's no Ethernet adapter recognised...

 

2. AppleIntelE1000e.kext in /S/L/E/IONetworkingFamily.kext/Plugins/, repaired permissions and rebuilt cache

if NETIF_F_TSO=true then Yosemite hangs on this screen:

 

Yes, hnak is right. As TSO is used only for large outbound TCP packets, it doesn't affect adapter recognition or basic functionality like DHCP or DNS at all. You might even be able to browse the web with a broken TSO implementation.

 

Mieze

Share this post


Link to post
Share on other sites

As NETIF_F_TSO flag is read after the driver is loaded, it has nothing to do with adapter recognition.

 

 

Yes, hnak is right. As TSO is used only for large outbound TCP packets, it doesn't affect adapter recognition or basic functionality like DHCP or DNS at all. You might even be able to browse the web with a broken TSO implementation.

 

Mieze

 

Guys, thank you for the clarifications :)

 

 

My H97M Pro4 (i218v2) works after waking up, though it may depend on how deep your sleep setting is.

hnak, we're having the same motherboards -- form factor is different (mATX & ATX). Could you be so kind to tell / advice me how to get my I218-V recognised and utilised in Yosemite? Should I use the FixLAN=true in Clover? I guess Im doing something stupid & wrong...

 

Thanks again

Share this post


Link to post
Share on other sites

 

hnak, we're having the same motherboards -- form factor is different (mATX & ATX). Could you be so kind to tell / advice me how to get my I218-V recognised and utilised in Yosemite? Should I use the FixLAN=true in Clover? I guess Im doing something stupid & wrong...

 

Thanks again

I have never had recognition problems with my motherboard. I have used various version of Clover ( 2953 now ) and set FixLAN_2000=true.

The only things I do after Clover installation are setting kext-dev-mode=1 and  copying boot/bootx64.efi as Suse/elilo.efi so that I can choose "SuSe" in setup, otherwise I cannot boot in UEFI mode.

You should try booting without the kext and manually loading by kextutil. Before booting, removal of Library/Preferences/SystemConfiguration/NetworkInterfaces.plist is recommended.

Share this post


Link to post
Share on other sites

I also have v-i218(2) on my asus h97m-plus and never had recognition problems @ yosemite or mavericks unless i forget to add kext-dev-mode=1

Share this post


Link to post
Share on other sites

Back on Yosemite with the same symptoms I reported earlier in the thread, a few pages back: sending large amounts of data over ipv6 crowbars the ethernet interface under this driver.

 

I checked but there doesn't seem to be a newer one than 3.1.0. I tried installing mieze's fixed version that worked for me on Mavericks, but afraid it's no longer making a difference. Currently my fix is to run VMWare (which for other reasons I no longer have to do all the time for other reasons).

 

Also slightly annoyed with myself: Decided sod it and bought a Realtek RTL8111E-based PCIe card, from a supplier who always dispatches very quickly - too quickly, they'd dispatched it before I remembered I didn't have a spare slot for it in my (mini-itx) hackintosh machine. Daft me...

 

(Mind you I would if the displayport-crash-on-wake problem on my HD4600 was fixed, but that's another story... :-} )

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.

Announcements

×