Contribute
Register

Working Kext for Killer E2200

Status
Not open for further replies.
You can see all the parts in my rig in my signature. Click on the link in My PC. Sorry if I don’t link it directly, I’m on mobile. The only LAN adapter I have is the integrated Killer one anyway. And wait, am I not on Sierra? I thought all I installed (drivers and OS) was Sierra

I see. Thought that you might be using additional hardware such as a dedicated Ethernet adapter like I do, which I mentioned in my previous post. So if I understand correctly you're using everything that is on-board along with the GTX 750 Ti. Well, I'd first suggest to disable the on-board Killer chip due to the bandwidth problem that I mentioned in my previous post, and to use a dedicated card instead. Hopefully it will also solve the issue you're facing - I'm not sure about it but it's something worth checking. Either way you'd have better transfer and speed behavior experience on your home network with a dedicated Ethernet card over the Killer one.

As for the MacOS version that you're using, your logs indicates 16G1036, which is the build number of High Sierra (the newer build of MacOS Sierra). I'm using the previous version - never updated to High Sierra as I'm not a fan of updating to the latest builds of whatever's out there. I live with the principles of "if it ain't broke, don't fix it". :)

By the way, you don't have to replace the Ethernet card right away if you just wish to see if it solves the crash problem. Just go into the BIOS and disable it; that way the OS won't see it. And then check if the issue happens again when you shut down. If it doesn't happen then here's what causing the problem. So it could be or driver related which is incompatible, or the Killer chip itself which again, I'd recommend to disable and replace with a dedicated card anyway.
 
I see. Thought that you might be using additional hardware such as a dedicated Ethernet adapter like I do, which I mentioned in my previous post. So if I understand correctly you're using everything that is on-board along with the GTX 750 Ti. Well, I'd first suggest to disable the on-board Killer chip due to the bandwidth problem that I mentioned in my previous post, and to use a dedicated card instead. Hopefully it will also solve the issue you're facing - I'm not sure about it but it's something worth checking. Either way you'd have better transfer and speed behavior experience on your home network with a dedicated Ethernet card over the Killer one.

As for the MacOS version that you're using, your logs indicates 16G1036, which is the build number of High Sierra (the newer build of MacOS Sierra). I'm using the previous version - never updated to High Sierra as I'm not a fan of updating to the latest builds of whatever's out there. I live with the principles of "if it ain't broke, don't fix it". :)

By the way, you don't have to replace the Ethernet card right away if you just wish to see if it solves the crash problem. Just go into the BIOS and disable it; that way the OS won't see it. And then check if the issue happens again when you shut down. If it doesn't happen then here's what causing the problem. So it could be or driver related which is incompatible, or the Killer chip itself which again, I'd recommend to disable and replace with a dedicated card anyway.

Well now replacing the ethernet card when I'd have no need for it is not a solution is it hahaha
Anyway I'm pretty sure I have regular Sierra, don't I?
Screen Shot 2017-11-11 at 12.21.12.png


EDIT: I can confirm that the system doesn't kernel panic once the integrated LAN is disabled, so that definitely the issue.
 
Last edited:
Well now replacing the ethernet card when I'd have no need for it is not a solution is it hahaha
Anyway I'm pretty sure I have regular Sierra, don't I?View attachment 291672

EDIT: I can confirm that the system doesn't kernel panic once the integrated LAN is disabled, so that definitely the issue.

youre using alxethernet.kext, use mieze's atheros kext
http://www.insanelymac.com/forum/to...lcomm-atheros-ar816x-ar817x-and-killer-e220x/

delete alxethernet, try with the above
 
Hey guys. I've used your resources for a very long time, and now I finally have something to contribute in return. I recently purchased an MSI GT70-2OD laptop. Every PC and laptop I have all run Windows, OSX, and Linux, and I depend on that capability because I'm a computer repair guy, and I sometimes have to do work on exotic systems or do something that requires software exclusive to one platform or another. After quite a bit of work getting OSX installed on the laptop I remembered that it has killer doubleshot wireless and LAN (E2200), and that finding a driver for either of those was going to be nigh impossible. I started looking for a solution, and decided to install linux in the meantime. Lo and behold, the E2200 didn't work in Linux Mint 15 either. I was pretty disappointed, until I found a patch that someone developed to allow the E2200 to work in linux through the ALX driver.

Apparently the ALX driver already did support the E2200, it just didn't know it. At this point, I went back to OSX, downloaded the source for Shailua's ALX driver, manually added the patch, and compiled for mavericks. Unfortunately, that wasn't enough. It would see the hardware properly (PCI addresses and such), and even did load and associate (Which was a very good sign), but it would always fail halfway through the initialization. A couple days worth of digging later, I found out that I had to modify some low-level driver code to make it succeed.

A bit of explanation is in order, I think. With the normal AR8161s, and other ALX compatible chips, there is just the MII (Controller) and the PHY (Physical Link/Port). The PHY answers to the MII, and gives you your link. The MII talks to the PCI bus. (Normally) Only with the Killer, there is that fancy UDP offload engine in the way, and the MII always says that it's busy, because it's only expecting to get commands from the killer controller, and not the system. Part of what I did is, I disabled the check to see if the MII is busy, in order to override that. Accessing the MII will always succeed, even if it -really- is busy.

I AM NOT LIABLE IF THIS BREAKS YOUR SYSTEM OR FRIES YOUR NIC, and this is very important in this case because I -REMOVED- a FAILSAFE in the DRIVER CODE. That said, it works wonderfully for me, and while I didn't remove anything major, i would only recommend testing this driver on the KILLER E2200, and nothing else. The only killer I've used it on is the onboard E2200 on the MSI GT70-2OD. I'm using it on one of my gigabyte hacks' AR8161, and it does work, but I don't know how stable it is yet.

I don't know enough about Xcode to change the version number, and I'm too lazy to clean up the hardware descriptions (The E2200 shows up in System Information as an AR8172 Fast Ethernet. It still runs at gigabit speeds, so it's just a cosmetic thing.) and to be honest, I'm done working on it, because it works great, and I don't have the time to take it any farther. I'm including the modified source code, and the ALX Kext, compiled for Mavericks. If you need it for an older version of OSX, you can open the project in Xcode, change the build target to whichever version you need, and then hit build. it should require no editing for OSX versions 10.7 to 10.9.

EDIT: To install this kext, copy the DEBUG version of the kext to S/L/E, and also copy it into the plugins folder inside IONetworkingFamily.kext. Either use kext wizard, or simply repair permissions on the disk afterwards, then reboot. ^_^
 
Hey shakakoa, I just managed to get ethernet on my msi Z170A GAMING M5 which has a killerE2400
I used this kext and the kext wizard

Hi guys sorry for the noob question, but is this all I need to do to get my e2200 to work? Not sure if this post over simplified it or not? Is there anything I should read first as I know next to nothing about kexts or anything like that.

Thanks in advance! :)
 
Hi guys sorry for the noob question, but is this all I need to do to get my e2200 to work? Not sure if this post over simplified it or not? Is there anything I should read first as I know next to nothing about kexts or anything like that.

Thanks in advance! :)
In response to my own question, for anyone else that was wandering the same as me, yes that is all you need to do. I’m rubbish at all this computer stuff and managed to do it so yay me
 
Status
Not open for further replies.
Back
Top