View previous topic :: View next topic |
Author |
Message |
Fire Hazard n00b
Joined: 14 Jan 2005 Posts: 64 Location: The Ohio State University
|
Posted: Mon Jan 13, 2014 7:47 am Post subject: No eth0 using System Rescue CD [SOLVED] |
|
|
So I just built my new PC and figured I'd have another go at Gentoo since I really really miss it. But like any Gentoo install I got walls to get around. My first wall looks to be getting my NIC to work. So here's the rub.
Using the latest version of System Rescue CD (SystemRescueCd-x86-3.8.1) I'm attempting to install Gentoo.
In the boot up screen I caught (via video on my cell phone since it scrolls too quickly) this....
Code: | No Network device auto detected |
Which might help explain why my ifconfig -a shows only lo and not eth0....
Code: | ifconfig -a
lo: flags=73<UP,LOOPBACK,RUNNING> mtu 16436
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 0 (Local Loopback)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 |
Did some searching based on my lspci output dealing with my NIC....
Code: | lspci
00:16.0 Communication Controller: Intel Corporation Lynx Point MEI Controller #1 (rev 04)
00:19.0 Ethernet controller: Intel Corporation Ethernet Connection I217-V (rev 05) |
Seemed like the kernel module e1000e was linked with getting it to run so I modprobe it and tried to run net-setup...
I chose interface name of eth0, wired network (which it is), and DHCP to auto-detect my network settings. Afterwards I ran ifconfig -a again....
Code: | ifconfig -a
lo: flags=73<UP,LOOPBACK,RUNNING> mtu 16436
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 0 (Local Loopback)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 |
What really throws me off is how there is no Kernel driver in use with my Communication controller and Ethernet controller...
Code: | 00:16.0 Communication Controller: Intel Corporation Lynx Point MEI Controller #1 (rev 04)
Subsystem: ASUSTeK Computer Inc. Device 8534
00:19.0 Ethernet controller: Intel Corporation Ethernet Connection I217-V (rev 05)
subsystem: ASUSTeK Computer Inc Device 859f |
Any suggestions on what to do next?
For those interested and for future Google/Forum searches I'm running i7-4770K on a ASUS MAXIMUS VI Hero motherboard. _________________ "Linux is only free if your time is worthless."
"Here is your parachute and here is the manual.
Welcome to Linux."
Last edited by Fire Hazard on Tue Jan 14, 2014 5:15 am; edited 1 time in total |
|
Back to top |
|
|
depontius Advocate
Joined: 05 May 2004 Posts: 3509
|
Posted: Mon Jan 13, 2014 1:02 pm Post subject: |
|
|
What does "dmesg" say after you "modprobe e1000e"?
There has been some stuff going on in the past few years about refining the PHY support, and I would wonder what kind of PHY connects your e1000e to the physical port. Might that be uncommon, and need a modprobe, as well? _________________ .sigs waste space and bandwidth |
|
Back to top |
|
|
DONAHUE Watchman
Joined: 09 Dec 2006 Posts: 7651 Location: Goose Creek SC
|
Posted: Mon Jan 13, 2014 3:57 pm Post subject: |
|
|
if your sysresccd is not the very latest suggest update and use the altkernel to get the latest available kernel.
the ubuntu folks reported that your nic is not supported in version 12 but is in 13 suggesting a kernel change
an alternative would be to install from a most current ubuntu livecd with sudo -su and mkdir /mnt/gentoo having been run to establish an analog of the gentoo install environment
hopefully asus has not tweaked the chip support code
does running lspci -nn find a pciid of 8086:153b ? _________________ Defund the FCC. |
|
Back to top |
|
|
Fire Hazard n00b
Joined: 14 Jan 2005 Posts: 64 Location: The Ohio State University
|
Posted: Mon Jan 13, 2014 4:37 pm Post subject: |
|
|
Code: | modprobe e1000e
.....
e1000e: Intel(R) PRO/1000 Nework Driver - 1.9.5-k
e1000e: Copyright(c) 1999 - 2012 Intel Corporation.
|
Is 1.9.5-K the latest drive?
Code: | lspci -nn
00:16.0 Communication controller [0780]: Intel Corporation Lynx Point MEI Controller [8086:8c31] (rev 05)
00:19.0 Ethernet controller [0200]: Intel Corporation Ethernet Connection I217-V [8086:153b] (rev 05) |
I take it 8086:153b is what I want to find since it would mean ASUS hasn't fiddled with the chip support code right?
I made my sysresccd(on a USB) at work on a Windows machine. I'll double check that is the latest and greatest kernel after I get home from work. I'll also try and see if Ubuntu's liveCD works on getting it to work too. _________________ "Linux is only free if your time is worthless."
"Here is your parachute and here is the manual.
Welcome to Linux." |
|
Back to top |
|
|
depontius Advocate
Joined: 05 May 2004 Posts: 3509
|
Posted: Mon Jan 13, 2014 8:48 pm Post subject: |
|
|
Thinkpad W530
Code: | [root@localhost ~]# lsmod | grep e1000
e1000e 253849 0 |
Code: | [root@localhost ~]# dmesg | grep e1000
e1000e: Intel(R) PRO/1000 Network Driver - 2.1.4-k
e1000e: Copyright(c) 1999 - 2012 Intel Corporation.
e1000e 0000:00:19.0: PCI INT A -> GSI 20 (level, low) -> IRQ 20
e1000e 0000:00:19.0: setting latency timer to 64
e1000e 0000:00:19.0: Interrupt Throttling Rate (ints/sec) set to dynamic conservative mode
e1000e 0000:00:19.0: irq 33 for MSI/MSI-X
e1000e 0000:00:19.0: eth0: (PCI Express:2.5GT/s:Width x1) 3c:97:0e:58:72:52
e1000e 0000:00:19.0: eth0: Intel(R) PRO/1000 Network Connection
e1000e 0000:00:19.0: eth0: MAC: 10, PHY: 11, PBA No: 1000FF-0FF
e1000e 0000:00:19.0: irq 33 for MSI/MSI-X
e1000e 0000:00:19.0: irq 33 for MSI/MSI-X
e1000e: eth0 NIC Link is Up 100 Mbps Full Duplex, Flow Control: None
e1000e 0000:00:19.0: eth0: 10/100 speed: disabling TSO |
_________________ .sigs waste space and bandwidth |
|
Back to top |
|
|
DONAHUE Watchman
Joined: 09 Dec 2006 Posts: 7651 Location: Goose Creek SC
|
Posted: Tue Jan 14, 2014 12:09 am Post subject: |
|
|
sysresccd 3.8.1 provides a kernel version 3.4.66 as the standard kernel and 3.10.17 as the alternate kernel. Thus the choice of alternate kernel over standard kernel is much more likely to provide support for your nic than using the newest cd with the standard kernel. The versions are the same for uefi and legacy bios choices.
8086:153b would suggest minimal change by asus. _________________ Defund the FCC. |
|
Back to top |
|
|
Fire Hazard n00b
Joined: 14 Jan 2005 Posts: 64 Location: The Ohio State University
|
Posted: Tue Jan 14, 2014 5:15 am Post subject: |
|
|
Well it turns out using the sysresccd 3.8.1 with the alt kernel (3.10.17-alt381-amd64) does have my NIC up and running as I'm making my post with the ASUS MAXIMUS VI Hero motherboard. That was an awfully simple answer to my problem. I hope the rest of my install is this simple to fix when/if I have another problem.
FYI I tried the Ubuntu LiveDVD and it also got my NIC up and running and off the top of my memory the kernel was 3.10.11 I believe. But the kernal module e1000e is working on my I217-V (rev 05) chipset. _________________ "Linux is only free if your time is worthless."
"Here is your parachute and here is the manual.
Welcome to Linux." |
|
Back to top |
|
|
DONAHUE Watchman
Joined: 09 Dec 2006 Posts: 7651 Location: Goose Creek SC
|
Posted: Tue Jan 14, 2014 5:19 am Post subject: |
|
|
good news; good luck _________________ Defund the FCC. |
|
Back to top |
|
|
|