I am also seeing this bug, however I am specifically able to turn it on
and off, so I may be able to shed a little more light on the situation.

I have a built-in Intel NIC, and two PCI-pluggable Realtek NICs.
When I installed lucid, my udev rules were:

# PCI device 0x10ec:0x8169 (r8169)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", 
ATTR{address}=="00:0a:cd:17:f6:2b", ATTR{dev_id}=="0x0", ATTR{type}=="1", 
KERNEL=="eth*", NAME="eth0"

# PCI device 0x10ec:0x8169 (r8169)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", 
ATTR{address}=="00:0a:cd:17:f6:3e", ATTR{dev_id}=="0x0", ATTR{type}=="1", 
KERNEL=="eth*", NAME="eth1"

# PCI device 0x8086:0x10c0 (e1000e)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", 
ATTR{address}=="00:21:9b:05:a3:8f", ATTR{dev_id}=="0x0", ATTR{type}=="1", 
KERNEL=="eth*", NAME="eth2"

Udev assigns the eth* names in order by MAC address (I think).
At this point, network-manager works fine.

After installation, I renamed and reordered the interfaces so that they
are indexed in the order the ports actually physically are on the PC
(I'm a stickler for order that way :D). My udev rules are now:

# PCI device 0x8086:0x10c0 (e1000e)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", 
ATTR{address}=="00:21:9b:05:a3:8f", ATTR{dev_id}=="0x0", ATTR{type}=="1", 
KERNEL=="eth*", NAME="eth0"

# PCI device 0x10ec:0x8169 (r8169)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", 
ATTR{address}=="00:0a:cd:17:f6:3e", ATTR{dev_id}=="0x0", ATTR{type}=="1", 
KERNEL=="eth*", NAME="eth1"

# PCI device 0x10ec:0x8169 (r8169)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", 
ATTR{address}=="00:0a:cd:17:f6:2b", ATTR{dev_id}=="0x0", ATTR{type}=="1", 
KERNEL=="eth*", NAME="eth2"

Network-manager now picks up eth0 as a Realtek card, and lists eth2
without any hardware information. Changing the file back to its original
state, however, fixes the problem: I just end up with a naming order I
don't particularly like.

My tentative conclusion is that when the order and names of the devices
in the udev rules file are not what udev expects, then it gets confused.

TJ, could you try reordering and renaming your net rules and see if that
helps or changes the situation?

-- 
Network Manager applet shows wrong wired interface name
https://bugs.launchpad.net/bugs/536826
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to