replaced old linux box with msi z170a m5 motherboard thinking this may work well for a couple years and the lan component on the board, killer e2400 gigabyte ethernet controller, does not seem to be supported… and I couldn’t find help from google. can this be fixed without purchase of a lan card? if not what lan card would be suggested for my new linux box? Thank You
That is your conclusion, but we like to know the technical facts that let you jump to that conclusion.
Please you post the out of
/usr/sbin/hwinfo --netcard
Thank you for responding, after running the command:
27: PCI 300.0: 0200 Ethernet controller
[Created at pci.328]
Unique ID: svHJ.F3kDev1wJr7
Parent ID: hoOk.EE7OfURW6V3
SysFS ID: /devices/pci0000:00/0000:00:1c.2/0000:03:00.0
SysFS BusID: 0000:03:00.0
Hardware Class: network
Model: “Atheros Ethernet controller”
Vendor: pci 0x1969 “Atheros Communications Inc.”
Device: pci 0xe0a1
SubVendor: pci 0x1462 “Micro-Star International Co., Ltd.”
SubDevice: pci 0x7977
Revision: 0x10
Memory Range: 0xdf400000-0xdf43ffff (rw,non-prefetchable)
I/O Ports: 0xd000-0xdfff (rw)
IRQ: 11 (no events)
Module Alias: “pci:v00001969d0000E0A1sv00001462sd00007977bc02sc00i00”
Config Status: cfg=no, avail=yes, need=no, active=unknown
Attached to: #18 (PCI bridge)
First, you can not know because you are new here (Welcome!), but please use CODE tags around copied/pasted computer text in a post. It is the # button in the tool bar of the post editor. When applicable copy/paste complete, that is including the prompt, the command, the output and the next prompt.
Then, as you can see the system does detect your NIC. Again, please answer, why do you say “it does not seem to be supported”?
What, when you use YaST > Network Devices > Network settings? Isn’t the device in the list there?
Thank you for welcoming me and your prompt assistance:
YaST2 - lan @ linux-kbhn
Network Settings
┌Global Options──Overview──Hostname/DNS──Routing──────────────────────────────────────────┐
│┌───────────────────────────────────────────────────────────────────────────────────────┐│
││Name │IP Address │Device│Note ││
││Atheros Ethernet controller│Not configured│ │ ││
││ ││
││ ││
││ ││
││ ││
││ ││
││ ││
││ ││
││ ││
│└───────────────────────────────────────────────────────────────────────────────────────┘│
│┌───────────────────────────────────────────────────────────────────────────────────────┐│
││Atheros Ethernet controllerBusID : 0000:03:00.0 ┬│
││Unable to configure the network card because the kernel device (eth0, wlan0) is not ││
││present. This is mostly caused by missing firmware (for wlan devices). See dmesg output┴│
││for details. ││
│└───────────────────────────────────────────────────────────────────────────────────────┘│
│[Add][Edit][Delete] │
│ │
└─────────────────────────────────────────────────────────────────────────────────────────┘
[Help] [Cancel] OK ]
F1 Help F3 Add F4 Edit F5 Delete F9 Cancel F10 OK
hope this helps to solve my dilema and help with my ‘forum etiquette’ as well
You seem to use the ncurses interface of YaST (you do not use a GUI desktop?)
Does not matter, but as YaST also has the device, I stiill do not understand why you say “does not seem to be supported”> Plerase why do you say so???
Simply use YaST and configure the NIC. What is the problem?
What is the problem
Maybe the Chip is not supported by the Kernel:
Vendor: pci 0x1969 “Atheros Communications Inc.”
Device: pci 0xe0a1
modprobe -c | grep -i "1969.*e0a1"
No output on kernel 4.1.
therefore if the chip is not supported by the kernel
then is there a way to alleviate this or must i install
a new lan card that my kernel does support, if so any suggestions?
On 2015-08-23 18:36, hcvv wrote:
> Simply use YaST and configure the NIC. What is the problem?
Mmm. Perhaps you did not notice the message yast gives? :-?
«Unable to configure the network card because the kernel device (eth0,
wlan0) is not present. This is mostly caused by missing firmware (for
wlan devices). See dmesg output for details.»
Thus, the next step would be to look at dmesg.
–
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)
Indeed, I did. Sorry for that.
And that ncurses copy/paste is in fact a good replacement for the GUI when one wants to show what happens. That is if I had studied it better to not completely miss the message 
dmesg included a bit more text then this message can hold…
therefore i copy/paste a piece that may be interesting although
it may be referring to something altogether different:
0.000027] ACPI: Core revision 20140424
0.022062] ACPI Error: \_SB_.PCI0.XHC_.RHUB.HS11] Namespace lookup failure, AE_NOT_FOUND (20140424/dswload-210)
0.022065] ACPI Exception: AE_NOT_FOUND, During name lookup/catalog (20140424/psobject-224)
0.028928] ACPI: All ACPI Tables successfully acquired
On 2015-08-25 00:06, regmont wrote:
> dmesg included a bit more text then this message can hold…
Use susepaste.org. Upload for a limited time. Post here a link.
–
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 “Bottle” (Minas Tirith))
On 08/23/2015 12:36 PM, regmont wrote:
> Unable to configure the network card because the kernel device (eth0, wlan0) is not ││
> ││present. This is mostly caused by missing firmware(for wlan devices). See dmesg output┴│
> ││for details
What part of this is not understood? The OP needs further help
installing the firmware. If I could help with that I would.
Ken
The Lan-Card is named:
Killer™ E2400 Gigabit LAN controller
http://www.msi.com/product/mb/Z170A-GAMING-M5.html#hero-specification
And as I said, the Chip is not supported under Linux.
that being said does anyone have a suggestion for a least expensive great quality lan card for my motherboard/OS? guess i am really sore i wasted a lot of money on something that is not linux friendly and favors windows, what a bummer:’(
Hello,
I have the same problem.
No solution since August 2015 ?
Please help.
“ethernet/atheros/alx: add Killer E2400 device ID
This patch adds the PCI device ID (0xe0a1) and alx_pci_tbl entry for the Killer E2400 Ethernet controller, modeled after the Killer E2200 controller support (0xe091) already present in the alx driver.”
Supported in >= 4.4
Committed package “atheros-ethernet” to home:Akoellh:Kernelmodules for 13.1, 13.2 and 42.1 (also with “Update”-repos containing the modules built against latest respective distro kernels).
http://download.opensuse.org/repositories/home:/Akoellh:/Kernelmodules/
Thanx a lot.
I’ll try it.
Thank you my friend.
You are a lifesaver 
I have wired Ethernet connection.
BUT i don’t have Wireless (INTEL Dual Band wireless AC 3165)
Regards