
The problem that remains is that when I reboot, the NIC doesn't wake up so I have to issue the command (simple, yes, but.) every time I boot up. Once that is issued, the NIC wakes up, I can connect, and I've verified the wired connection works (checked MAC addresses for connected devices through my router).

Then I found this:Įcho 1969 e0a1 > /sys/bus/pci/drivers/alx/new_id The device is detected, but I cannot seem to find a driver to recognize it. This page contains the driver installation download for Killer E2400 Gigabit Ethernet Controller in supported models (H170-Gaming 3) that are running a. Have tried different cables, redownloading drivers and bios and flushing dns. Linux localhost.localdomain #1 SMP Tue Jan 5 23:31: x8664 x8664 x8664 GNU/Linuxģb:00.0 Ethernet controller: Qualcomm Atheros Killer E2400 Gigabit Ethernet Controller (rev 10)ĭevice: Killer E2400 Gigabit Ethernet Controller All devices in the house receive 400mbps, whereas my PC with killer e2400 and ethernet caps out at 200mbps. Uninstalled device (Killer E2400 Gigabit Ethernet Controller) and manually installed latest driver Ran Update Driver (Windows indicated best / most recent driver already installed) Reset the Network Stack using the following Commands: ipconfig /release -> ipconfig /flushdns -> ipconfig /renew -> netsh int ip reset -> netsh winsock reset. A little Google mining led me to the following set of commands and responses:
