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

thanks, working nicely on my intel dx58so2 board :P (i82567L and i82574L, 0x10cd/0x10d3 *feeding the search engine*)

 

oh, and 10.7 dp4, of course :unsure:

Share this post


Link to post
Share on other sites
1.3.17. don't work on intel 82579 id 0x1503 on Asus p8z68-v .. :o Any idea?

Thanks.

Mine is also 0x1503, and working naturally.

How NOT work ? - driver not loaded, crash, no carrier, no IP, 1.2.10a works but 1.3.17 not, etc.

Share this post


Link to post
Share on other sites
Mine is also 0x1503, and working naturally.

How NOT work ? - driver not loaded, crash, no carrier, no IP, 1.2.10a works but 1.3.17 not, etc.

Mine is Intel® 82579V Gigabit Network Connection PCI\VEN_8086&DEV_1503&SUBSYS_849C1043&REV_05 on Asus P8Z68-V and Core i7 2600K

i try 1.2.10a and now 1.3.17 on dp4 11A494A lan connect dhcp asign ip bad, manualy config not work. no internet connect in any mode.

I not tray sl.

Thanks.

Share this post


Link to post
Share on other sites
Mine is Intel® 82579V Gigabit Network Connection PCI\VEN_8086&DEV_1503&SUBSYS_849C1043&REV_05 on Asus P8Z68-V and Core i7 2600K

i try 1.2.10a and now 1.3.17 on dp4 11A494A lan connect dhcp asign ip bad, manualy config not work. no internet connect in any mode.

I not tray sl.

Thanks.

Neither of 1.2.10a and 1.3.17 works ?

 

--- edit

 

I have just installed Lion DP4 on the same hardware as Snow.

I just copied the Snow's working driver (1.3.17) into the new /S/L/E and it works as expected.

The MB is Intel DH67CF.

Share this post


Link to post
Share on other sites
Neither of 1.2.10a and 1.3.17 works ?

 

--- edit

 

I have just installed Lion DP4 on the same hardware as Snow.

I just copied the Snow's working driver (1.3.17) into the new /S/L/E and it works as expected.

The MB is Intel DH67CF.

 

Id try also sl 10.6.8 neither of 1.2.10a and 1.3.17 works, error is the same "Self-Assigned IP". so ip address is invalid.

 

Installation are cloning of my 1st pc changing extra folder.. and adding kext lan in s/l/e.

 

--- edit

 

My hardware with windows 7 64 and old xp work fine!

 

 

OT.

For Graphics you use cpu hd vga?

Work?

 

Thanks.

 

I remove dsdt and install chimera 1.5.3 and work fine .

Share this post


Link to post
Share on other sites
Id try also sl 10.6.8 neither of 1.2.10a and 1.3.17 works, error is the same "Self-Assigned IP". so ip address is invalid.

 

Installation are cloning of my 1st pc changing extra folder.. and adding kext lan in s/l/e.

 

--- edit

 

My hardware with windows 7 64 and old xp work fine!

 

 

OT.

For Graphics you use cpu hd vga?

Work?

 

Thanks.

If carrier is active and IP is self-assigned, it requires investigation using packet sniffers like WireShark.

Do you see transmit/receive errors with the Network Utility.app ?

 

My Graphics card is Radeon HD 5450 (MSI). I use an injector found in a ATI thread of the forum.

Share this post


Link to post
Share on other sites
Hey man, I too have an Alienware M15X but I use SL 10.6.3. So far everything works great but I cannot get the DVD Drive working although it's recognized in the Serial-ATA part of System Profiler. Does your DVD drive work under Leopard?

 

you probably need the IOATA panic fix in sat1 aka ide aka pata. to disable secondary chann.. or device id for controler is wrong.

Share this post


Link to post
Share on other sites
Thanks for the answer, other user also reported is working perfectly with 82579.

 

Hi hnak,

 

I'm having another issue causing kernel panics and I'm wondering if you are anyone else can replicate it.

 

If I enable Screen Sharing (VNC) on the host hackintosh, and connect from another mac and start doing a lot of network activity, I can cause a kernel panic. Has anyone seen this?

 

Sorry for being vague, but I'm assuming this is related to the NIC driver. I'll see if I can capture a screen shot of the kernel panic (usually when this happens, I can't see it as Screen Sharing just stops responding).

Share this post


Link to post
Share on other sites
Though I don't have the answer, I am using this kext myself regularly on DH67CF and DZ68DB.

 

Hnak,

 

Have you built a hackintosh with the Intel DZ68DB? If so, how did you install?

 

I've just bought this motherboard to build an HTPC using Ubuntu but I'd like to use it as a hackintosh if possible.

Share this post


Link to post
Share on other sites
Where did you put it ?

 

Well, Lion can recognize it in the system, but cannot connect to the internet.

I get the problem of self-assign IP address, no matter what I do (renew DHCP, reset router, etc.)

Share this post


Link to post
Share on other sites

Hi all, totally new to the scene, so please forgive my noobishness.

I've spent all my time over at the Windows side and have finally decided to jump over to OS X.

 

I've just built my working Mac, but for some reason I can't get my ethernet to work.

My current setup is at 10.6.7 with full graphics, and sound working with [url="http://www.insanelymac.com/forum/topic/279450-why-insanelymac-does-not-support-tonymacx86/"]#####[/url].

I've tried installing the kext myself using Kext Utility (from hnak's AppleIntelE1000e.kext) as well as installing the P8P67 Pro Package.

The problem is, I can't seem to get anything to show up in the network application for me to connect to.

 

Any insight is greatly appreciated!

Share this post


Link to post
Share on other sites

Hello I use your kext since long time and you once fixed the MTU 9000 issue when I told you. Many thanks!

Sometimes I had kernel panics when the device was detected at boot, now it's happening more often, I updated the kext to the last version you released.

 

I haven't the log, I can't find it in /var/log/kernel.log when it panics, but you can see from the picture below, it writes partially panic and freezes like that:

 

IMG_0026.jpg

 

 

This is a normal successful boot:

Jul 26 13:42:40 localhost kernel[0]: Kernel is LP64
Jul 26 13:42:42 localhost kernel[0]: systemShutdown false
Jul 26 13:42:49 localhost kernel[0]: Previous Shutdown Cause: 3
Jul 26 13:42:50 localhost kernel[0]: vendor:device: 0x8086:0x10d3.
Jul 26 13:42:50 localhost kernel[0]: AppleIntelE1000e(Info): changing MTU from 0 to 1500
Jul 26 13:42:52 localhost kernel[0]: AppleTyMCEDriver::start coreVIDPID = 0x2c418086 Number of packages = 1 Number of cpus = 8 memory monitor trough MCA
Jul 26 13:42:52 localhost kernel[0]: RadeonMonitor: found 6898 Radeon chip
Jul 26 13:42:52 localhost kernel[0]: DSMOS has arrived
Jul 26 13:42:52 localhost kernel[0]: Found ATI Radeon 6898AppleIntelE1000e: Ethernet address 00:1b:21:44:1d:e8
Jul 26 13:42:52 localhost kernel[0]: ** Device in slot: SLOT--1 **
Jul 26 13:42:54 localhost kernel[0]: AppleIntelE1000e(Info): changing MTU from 1500 to 9018
Jul 26 13:42:56 localhost kernel[0]: AppleIntelE1000e(Info): Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx

 

If you need to know more let me know. Thanks.

The card is 82574L PCI-E, device id 0x10d3.

Share this post


Link to post
Share on other sites
Hnak,

 

Have you built a hackintosh with the Intel DZ68DB? If so, how did you install?

 

I've just bought this motherboard to build an HTPC using Ubuntu but I'd like to use it as a hackintosh if possible.

Sorry for not responding, I have not checked this topic recently.

I just installed system using from another working system ( actually, old mac-mini ) via USB-SATA converter, installed Chimera 1.4.1 + stage0/stage1 bootloader of chameleon, and put fakesmc and nullcpupowermanagement in /E/E.

I also edited DSDT using DSDT editor for shutdown, USB, HPET, etc.

 

 

 

If you need to know more let me know. Thanks.

The card is 82574L PCI-E, device id 0x10d3.

KP occurs only if MTU > 1500 ?

Share this post


Link to post
Share on other sites
Hi hnak,

Any chance for 82599 driver (e.g Intel Ethernet Server Adapter X520-T2)?

The linux driver for the chip is hosted on the same sourceforge site ( e1000.sf.net ), but the project (ixgbe) is different from the one I ported (e1000e). The site hosts some more projects ( e1000, igb, igbvf, etc. )

If I had the environment, I would be able to port, but I don't.

Share this post


Link to post
Share on other sites
KP occurs only if MTU > 1500 ?
I'll try that tonight and let you know.

 

No panic yet at 1500. Had the chance to try about 3/4 times.

Share this post


Link to post
Share on other sites
No panic yet at 1500. Had the chance to try about 3/4 times.

I'll start checking the code this weekend.

As I am not using jumbo frame, I have to set up the testing environment at first, so it may take some time to figure out the problem.

Share this post


Link to post
Share on other sites
I'll start checking the code this weekend.

As I am not using jumbo frame, I have to set up the testing environment at first, so it may take some time to figure out the problem.

I talked too soon, had 2 consecutive panics today at the first bootup of my computer also with mtu 1500.

But for the first time it showed me the trace of the first panic, but that's all I have on the log:

 

Jul 28 13:25:28 localhost kernel[0]: Kernel is LP64
Jul 28 13:25:28 localhost kernel[0]: FireWire (OHCI) TI ID 8024 PCI now active, GUID 00ec0c25006cf049; max speed s400.
Jul 28 13:25:28 localhost kernel[0]: USBMSC Identifier (non-unique): 100803100039 0x424 0x4063 0x191
Jul 28 13:25:28 localhost kernel[0]: hfs: Removed 1 orphaned / unlinked files and 0 directories 
Jul 28 13:25:28 localhost kernel[0]: systemShutdown false

 

picture shows more:

panic.jpg

 

 

2nd panic didn't show any trace again just froze after device detect "vendor:device: 0x8086:0x10d3."

Thanks for your help!

Share this post


Link to post
Share on other sites

I gathered some info from your screen shot.

It appears the driver crashed at offset 0x443b and you are using x86_64.

 

I executed a command:

dwarfdump --lookup=0x443b [dsymfile]

and the answer is AppleIntelE1000e.cpp line 2351.

The corresponding line is :

count = rxMbufCursor->getPhysicalSegmentsWithCoalesce(skb, &vector, 1);

It appears to have failed in allocating ( collecting ) contiguous memory in mbuf.

It is a very fundamental API call and used everywhere.

I don't know why it caused a page fault even if mtu=1500.

Share this post


Link to post
Share on other sites
I gathered some info from your screen shot.

It appears the driver crashed at offset 0x443b and you are using x86_64.

 

I executed a command:

dwarfdump --lookup=0x443b [dsymfile]

and the answer is AppleIntelE1000e.cpp line 2351.

The corresponding line is :

count = rxMbufCursor->getPhysicalSegmentsWithCoalesce(skb, &vector, 1);

It appears to have failed in allocating ( collecting ) contiguous memory in mbuf.

It is a very fundamental API call and used everywhere.

I don't know why it caused a page fault even if mtu=1500.

 

I can actually see the error only when mtu is set at 1500, if I set it to 9000 it just freezes like the second try before.

Had couple panics today too :/ Thanks for looking into this and glad the screenshot helped you to track the line. Do you think it's possibile to fix or it's something else causing the panic?

Share this post


Link to post
Share on other sites
I can actually see the error only when mtu is set at 1500, if I set it to 9000 it just freezes like the second try before.

Had couple panics today too :/ Thanks for looking into this and glad the screenshot helped you to track the line. Do you think it's possibile to fix or it's something else causing the panic?

The bigger mtu gets, the more memory allocated, and it may cause panic more frequently.

Does the same system work fine with NICs other than 82574 ? I am wondering about the sanity of the system components, as I never had the kind of problem with none of my NICs/systems.

 

 

I tested the jumbo frame between Apple's driver and mine, and I successfully transferred files.

The problem might be 82574 specific. I will read the model specific flow of the source, though I cannot do any testing.

Are there any 82574 users having ( or not having ) the same problem ?

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.

×