Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

For bugs related to Red Hat Enterprise Linux 4 product line. The current stable release is 4.9. For Red Hat Enterprise Linux 6 and above, please visit Red Hat JIRA https://issues.redhat.com/secure/CreateIssue!default.jspa?pid=12332745 to report new issues.

Bug 252374

Summary:	ethernet cards are being detected in the wrong order.
Product:	Red Hat Enterprise Linux 4	Reporter:	Allen Berg <aberg>
Component:	anaconda	Assignee:	Anaconda Maintenance Team <anaconda-maint-list>
Status:	CLOSED WONTFIX	QA Contact:	Release Test Team <release-test-team-automation>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	4.9	CC:	cperry, msuchy
Target Milestone:	---
Target Release:	---
Hardware:	ia64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2011-01-24 15:01:45 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	462714

Description Allen Berg 2007-08-15 17:32:04 UTC

Description of problem:
We have created a kickstart for our Sun Fire x4100 servers.  When we boot them 
up and look at the network config eth2 says that its eth0 eth0 says that its 
eth2, eth3 says its eth1 and eth3 says that its eth1.  eth2 and eth1 are Intel 
and eth0 and eth3 are NVIDIA cards.  What has likely happened is that the 
broadcom and nvidia drivers have been loaded in the wrong order.  


Version-Release number of selected component (if applicable): 5.0


How reproducible: auto detect using kickstart


Steps to Reproduce:
1.  run kickstart 
2. run network configuration
3.
  
Actual results:
eht0 is detected as eth2
Eth2 is detected as eth0
eth1 is detected as eth3
eth3 is detected as eth1


Expected results:

eth0 = eth0
eth2 = eth2
eth1 = eth1
eth3 = eth3

Additional info:  We can manually set them up using the network configuration 
tool but that does not allow us to automate the deployment and build of the 
kickstart.  How can we get the nvidia and broadcom drivers to load in the 
proper order?

Comment 1 Miroslav Suchý 2011-01-23 11:59:34 UTC

This is IMHO rather anaconda bug. From date I'm just guessing it is RHEL4.

Comment 2 Chris Lumens 2011-01-24 15:01:45 UTC

anaconda is no longer an approved component for RHEL4.