View previous topic :: View next topic |
Author |
Message |
JonathanVP n00b


Joined: 21 Oct 2002 Posts: 51 Location: Ashtabula, OH
|
Posted: Tue Nov 30, 2010 7:28 am Post subject: nterface eth0 does not exist |
|
|
I executed the lspci command and my ethernet controller is a Intel Corp 82545EM Gigabyte Ethernet Controller (rev 01). Dmesg states that it exists but when Gentoo boots up, I get the eth0 does not exist error even when I added the INtel network support in the kernel (not as a module). Has anyone experienced this? |
|
Back to top |
|
 |
Goverp Advocate


Joined: 07 Mar 2007 Posts: 2206
|
Posted: Tue Nov 30, 2010 9:34 am Post subject: Re: nterface eth0 does not exist |
|
|
JonathanVP wrote: | I executed the lspci command and my ethernet controller is a Intel Corp 82545EM Gigabyte Ethernet Controller (rev 01). Dmesg states that it exists but when Gentoo boots up, I get the eth0 does not exist error even when I added the INtel network support in the kernel (not as a module). Has anyone experienced this? |
Which "eth0 does not exist error"? A little more detail would help. _________________ Greybeard |
|
Back to top |
|
 |
JonathanVP n00b


Joined: 21 Oct 2002 Posts: 51 Location: Ashtabula, OH
|
Posted: Tue Nov 30, 2010 2:00 pm Post subject: |
|
|
It appears that eth1 was created which is now the default network setting (and not eth0). I had to make it activated at boot which fixes the problem. Thanks for your help! |
|
Back to top |
|
 |
Ph0eniX Guru


Joined: 24 Sep 2004 Posts: 502 Location: New York, U.S.
|
Posted: Tue Nov 30, 2010 5:39 pm Post subject: |
|
|
JonathanVP wrote: | It appears that eth1 was created which is now the default network setting (and not eth0). I had to make it activated at boot which fixes the problem. Thanks for your help! |
I've had silly issues like this in the past. The NIC would change from eth0 to eth1 and the other way around randomly. To correct the issue permanently, I had to bind the NIC's MAC address to the interface name in udev config. |
|
Back to top |
|
 |
|