Bug 116948 - eth0 becomes eth2 after motherboard replacement
Summary: eth0 becomes eth2 after motherboard replacement
Status: RESOLVED WONTFIX
Alias: None
Product: openSUSE 10.2
Classification: openSUSE
Component: Network (show other bugs)
Version: unspecified
Hardware: Other All
: P5 - None : Enhancement (vote)
Target Milestone: ---
Assignee: Michal Zugec
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-09-14 12:18 UTC by Bavo De Ridder
Modified: 2008-06-25 09:22 UTC (History)
2 users (show)

See Also:
Found By: Other
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Bavo De Ridder 2005-09-14 12:18:06 UTC 
I have RC3 installed on a Dell D800 laptop. The internal ethernet card was  
configured as eth0, an external wifi card as eth1. The motherboard was  
replaced because of a broken USB connector. The internal ethernet card now  
appears as eth2.  
  
I removed all devices from Yast2 and even rebooted. I configured the internal  
ethernet card again. It now always appears as eth2.  
  
When I stop the network and unload the module tg3 and then load the module  
again, dmesg shows me that an eth0 device was found, however when activating  
the network for this card (rcnetwork start eth0) I get a Interface eth0 is not  
available, rcnetwork start eth2 starts the network correctly.  
  
It seems that somewhere there are still references to the configuration of the  
internal card of the old motherboard?  
 
I have not yet attached configuration files or logs since I have no idea what 
the relevant files are for this problem.
Comment 1 Christian Zoz 2005-09-15 04:13:52 UTC 
This works as expected. Have a look in /etc/udev/rules.d/30-net* and remove the
lines for the non existent cards. There is also a pointer to a README that
explains why.

Martin, for the next release, YaST should be able to manage interface names.
Comment 2 Harald Mueller-Ney 2006-04-22 04:45:21 UTC 
Reducing to enhancement - it works as expected. The feature might added for next release, taking over to create a FATE feature
Comment 4 Andreas Jaeger 2006-06-01 07:03:51 UTC 
Stano, could you add this to fate?
Comment 6 Martin Vidner 2006-08-28 11:52:26 UTC 
Reassigning to the new maintainer of yast2-network.
Comment 7 Michal Zugec 2006-08-30 06:47:12 UTC 
move to later
Comment 8 Felix Miata 2006-09-13 21:54:25 UTC 
This bug was filed over a year ago. Why is it marked later instead of fixed? Nothing is resolved.
Comment 9 Felix Miata 2006-09-13 22:24:43 UTC 
BTW, same problem when the motherboard NIC dies and a  replacement is installed in a PCI slot.
Comment 10 Stephan Kulow 2008-06-25 09:18:50 UTC 
mass reopening all 10.2 LATER+REMIND bugs.
Comment 11 Stephan Kulow 2008-06-25 09:22:54 UTC 
close all 10.2 LATER/REMIND bugs as WONTFIX. Reopen yourself if you still plan to work on it.