You could try adding 'bfsort' to the kernel command line. This helps keeps the Ethernet device list the same for the kernel as for the BIOS. This is the v2.4 and below behavior.
CC On 1/28/10, Sam Sharpe <[email protected]> wrote: > 2010/1/27 Arvind Navale <[email protected]>: > > Hi Folks, > > > > I am doing network install of RHEL-5.3 OS on Sun hardware, model info is > > x4240 AMD 6 core system. Network install I have is a install server, tftp > > and dhcp server. It successfully does pxeboot over network and goes through > > probing the hardware on the system and when it comes to configuring network, > > it picks up eth0 for configuring the network and doesn't complete, instead > > shows manual configuration window. > > The x4240 has multiple network interfaces. The behaviour you describe > roughly matches my observations when what I have plugged into PXE is > not what anaconda considers eth0. Have you tried passing > ksdevice=bootif as a boot parameter as per this: > > http://www.redhat.com/archives/anaconda-devel-list/2005-August/msg00019.html > > Other options are ksdevice=link which will use the first device that > anaconda detects has a link. > > -- > Sam > > _______________________________________________ > rhelv5-list mailing list > [email protected] > https://www.redhat.com/mailman/listinfo/rhelv5-list > -- RHCE#805007969328369 _______________________________________________ rhelv5-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/rhelv5-list
