veloha.blogg.se

1. #CODE 12 KILLER E2200 GIGABIT ETHERNET CONTROLLER INSTALL#
2. #CODE 12 KILLER E2200 GIGABIT ETHERNET CONTROLLER DRIVERS#
3. #CODE 12 KILLER E2200 GIGABIT ETHERNET CONTROLLER DRIVER#
4. #CODE 12 KILLER E2200 GIGABIT ETHERNET CONTROLLER PATCH#

Short of applying the appropriate patch and recompiling the affected kernel module, you may be able to register new PCI device IDs ( documentation) with existing device drivers:

Original post (still applicable to other Ubuntu releases before 16.04) More info: Ubuntu Wiki – LTS Enablement Stack The newly installed kernel should be the new default boot option for Grub.

#CODE 12 KILLER E2200 GIGABIT ETHERNET CONTROLLER INSTALL#

Install the kernel packages: sudo apt install linux-generic-lts-xenial Luckily one can upgrade to the same kernel in Ubuntu 14.04 via LTS/HWE upgrades: Your E2400 should now appear for your networking enjoyment!Īccording to chili555's comment on a similar question that device is supported by the kernel shipped with Ubuntu 16.04. extra/alx.ko If you do not, you may need to rename the alx.ko that it did find to alx.ko.bak or something of the sort, and run the last three commands again. Note: You after executing the last line, you should see the module load from. Sudo make -C /lib/modules/$(uname -r)/build M=$(pwd) modules_install

#CODE 12 KILLER E2200 GIGABIT ETHERNET CONTROLLER DRIVERS#

Now, all that's left is to make and install the drivers make -C /lib/modules/$(uname -r)/build M=$(pwd) modules

#CODE 12 KILLER E2200 GIGABIT ETHERNET CONTROLLER DRIVER#

Once that is finished, we'll modify the alx driver to include our E2400 (feel free to use your text editor of choice) cd ubuntu-vivid/drivers/net/ethernet/atheros/alx/įind the line defining ALX_DEV_ID_E2200 (you can just search for E2200), and add this below it #define ALX_DEV_ID_E2400 0xe0a1Īgain, find E2200, and after the lines , That last step can take a little while, so relax and bask in the knowledge that your E2400 will soon be working. You would replace vivid with your release codename. I tried to find a couple regedit values that I was advised to delete to fix code 10s and this device doesn't have those values.I am posting this from my Skylake MSI Z170A GAMING M5 build using my Killer E2400 on Ubuntu Gnome! Below are the (more or less) simple steps I used to get it working.įirst we'll follow some instructions from Ubuntu sudo apt-get build-dep linux-image-$(uname -r) I have already uninstalled a couple of the drivers that I installed, but the issue persists. Constantly my display driver gets a code 10 upon waking up from sleep and much of the time it won't let me disable and re-enable. This time, against my better judgement, I went through with installing all of the drivers supposed to come with my Gigabyte motherboard, and two new issues cropped up, one of them causing my display driver to turn off and me having to hard reboot the computer (but that's a story for another time).

I have refreshed all of my software on the computer a couple times, and this issue didn't occur until the last time I reset the computer. I have disallowed the computer from turning off the device to save power in case that was an issue. The driver is the Killer E2400 Gigabit Ethernet Controller. I can't roll it back, it's up to date, I've tried reinstalling it, and troubleshooter tells me nothing. Additionally, after every time I restart it seems that it can go a few wake-ups without having the issue, but once it has it once it has it almost every other time I wake it up until I reboot again. I end up having to reboot or put the computer back to sleep and wake it up again to fix it. I have to kill the task, and then trying again it does the same thing. Most of the time I can open the Device Manager and disable and re-enable it, but sometimes that doesn't work and Device Manager hangs upon trying to re-enable it. About 1/3 of the times I wake my computer up from sleep, the networking driver got a code 10.