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?
This is IMHO rather anaconda bug. From date I'm just guessing it is RHEL4.
anaconda is no longer an approved component for RHEL4.