eth0 is moved to eth1

[Jean-Christophe Dubois]

My motherboard is an A8N-VM CSM from Asus.

On this board there is only one ethernet controller:

00:14.0 Bridge: nVidia Corporation MCP51 Ethernet Controller (rev a1)

This system used to run Fiesty Fawn (x86 server). I had no problem with it and the only ethernet port was referenced as eth0.

Then I decided to give Gusty Gibon (x86_64 server) a try. I wiped out my disks and installed it from scratch. Everything went fine.

But when I reboot I discovered that no ethernet port was configured.

looking at /etc/network/interfaces it sounded like the installation script detected and configured an eth0 port.

But running "ifconfig -a" I discovered that there was no eth0 port available but only one eth1.

So patching the /etc/network/interfaces, replacing eth0 with eth1 fixed the problem.

However it is still a strange behavior and this could certainly be puzzling for a beginner.

Here is a short extract form my dmesg:

jcd@ubuntuNAS:~$ dmesg | grep eth
[ 18.288834] forcedeth.c: Reverse Engineered nForce ethernet driver. Version 0.60.
[ 20.885103] forcedeth: using HIGHDMA
[ 21.409823] eth0: forcedeth.c: subsystem: 01043:8141 bound to 0000:00:14.0
[ 43.128645] eth1: no IPv6 routers present

I am not sure the fact that I went from an x86 to an x86_64 release does matter so much but ... there is still something strange on this AMD64 release (not sure is the same is true for the x86 release).

[Jean-Christophe Dubois (jcd)]

Just adding the "uname -a" output:

jcd@ubuntuNAS:~$ uname -a
Linux ubuntuNAS 2.6.22-12-server #1 SMP Sun Sep 23 20:27:14 GMT 2007 x86_64 GNU/Linux

and the linux kernels installed (the system is up to date):

jcd@ubuntuNAS:/etc$ dpkg -l linux-*
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Installed/Config-f/Unpacked/Failed-cfg/Half-inst/t-aWait/T-pend
|/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad)
||/ Name Version Description
+++-====================-====================-========================================================
un linux-boot-loader <none> (no description available)
un linux-doc-2.6.22 <none> (no description available)
un linux-image <none> (no description available)
un linux-image-2.6 <none> (no description available)
ii linux-image-2.6.22-1 2.6.22-12.39 Linux kernel image for version 2.6.22 on x86/x86_64
ii linux-image-server 2.6.22.12.17 Linux kernel image on Server Equipment.
un linux-initramfs-tool <none> (no description available)
un linux-kernel-log-dae <none> (no description available)
ii linux-server 2.6.22.12.17 Complete Linux kernel on Server Equipment.
ii linux-sound-base 1.0.14-1ubuntu1 base package for ALSA and OSS sound systems
un linux-source-2.6.22 <none> (no description available)
ii linux-ubuntu-modules 2.6.22-12.32 Ubuntu supplied Linux modules for version 2.6.22 on x86/

[Brian Murray (brian-murray)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. This seems to me to be a duplicate of bug 145382 which was mentioned as a part of the release announcement for the Beta CD. Could you look at that bug report and see if it is the same as yours? Thanks in advance.

[Jean-Christophe Dubois (jcd)]

You are right, my 70-persistent-net.rules was as follow:

SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="", NAME="eth0"

SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="", NAME="eth0"

SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="", NAME="eth0"

SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="", NAME="eth0"

SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="", NAME="eth0"

# PCI device 0x10de:0x0269 (forcedeth)
SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:13:d4:fe:07:4c", NAME="eth1"

After changing it to:

# PCI device 0x10de:0x0269 (forcedeth)
SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:13:d4:fe:07:4c", NAME="eth0"

The system was back to normal.

[Brian Murray (brian-murray)]

Okay, I'm going to mark this as a duplicate of 145382 then. Thanks again for taking the time to report it.