On Jan 29, 2010, at 8:32 AM, Matt Iavarone wrote: > On Fri, Jan 29, 2010 at 9:18 AM, Arvind Navale <[email protected]> wrote: >> Thanks for the helpful pointers. >> >> I have tried using ksdevice=bootif and it did not help. When it comes to >> configuring network it brings me to following screen, >> >> +--------------------------+ Networking Device >> +---------------------------+ >> | >> | >> | You have multiple network devices on this system. Which would >> | >> | you like to install through? >> | >> | >> | >> | eth0 - nVidia Corporation MCP55 Ethernet ^ >> | >> | eth1 - nVidia Corporation MCP55 Ethernet # >> | >> | eth2 - nVidia Corporation MCP55 Ethernet : >> | >> | eth3 - nVidia Corporation MCP55 Ethernet : >> | >> | eth4 - Intel Corporation 82571EB Gigabit Ethernet Controller (Copper) : >> | >> | eth5 - Intel Corporation 82571EB Gigabit Ethernet Controller (Copper) v >> | >> | >> | >> | +----+ +----------+ +------+ >> | >> | | OK | | Identify | | Back | >> | >> | +----+ +----------+ +------+ >> | >> | >> | >> | >> | >> >> +--------------------------------------------------------------------------+ >> >> I haven't tried ksdevice=link and will try it out and see if it helps. >> >> Regarding adding 'bfsort' to the kernel command line I believe you are >> referring to add (basically append) it to the file which is created in >> /tftpboot/linux-install/pxelinux.cfg/<hex file> correct? >> >> For example >> >> default RHEL-4.4 >> >> label RHEL-4.4 >> kernel RHEL-4.4/vmlinuz >> append initrd=RHEL-4.4/initrd.img console=ttyS0,9600n8 ramdisk_size=8192 >> ks=nfs:192.168.91.14:/appl/kickstart/ks/bth3lab18-rhel-4.4-lvm-omg-kickstart.cfg >> ksdevice=eth0 bfsort >> >> I am installing RHEL-5.3 which has v2.6 kernel but I will still try it out. >> >> Thank you, >> AN >> >> >> >> >>> From: [email protected] >>> Subject: rhelv5-list Digest, Vol 35, Issue 28 >>> To: [email protected] >>> Date: Thu, 28 Jan 2010 12:00:04 -0500 >>> >>> Send rhelv5-list mailing list submissions to >>> [email protected] >>> >>> To subscribe or unsubscribe via the World Wide Web, visit >>> https://www.redhat.com/mailman/listinfo/rhelv5-list >>> or, via email, send a message with subject or body 'help' to >>> [email protected] >>> >>> You can reach the person managing the list at >>> [email protected] >>> >>> When replying, please edit your Subject line so it is more specific >>> than "Re: Contents of rhelv5-list digest..." >>> >>> >>> Today's Topics: >>> >>> 1. RHEL-5.3 Network Install on Sun Fire x4240 (Arvind Navale) >>> 2. Re: RHEL-5.3 Network Install on Sun Fire x4240 (Sam Sharpe) >>> 3. Re: RHEL-5.3 Network Install on Sun Fire x4240 (Colin Coe) >>> 4. Re: recent install trashes refit (Eugene Vilensky) >>> >>> >>> ---------------------------------------------------------------------- >>> >>> Message: 1 >>> Date: Wed, 27 Jan 2010 17:40:48 -0500 >>> From: Arvind Navale <[email protected]> >>> To: RHEL-v5 OS Group <[email protected]> >>> Subject: [rhelv5-list] RHEL-5.3 Network Install on Sun Fire x4240 >>> Message-ID: <[email protected]> >>> Content-Type: text/plain; charset="iso-8859-1" >>> >>> >>> 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. I go ahead and perform manual >>> configuration but it errors out at next step where I has to access >>> kickstart.cfg file form the NFS server (install server). I have tried >>> mentioning different network instance in the configuration but all the time >>> it shows only configuring eth0 instance not sure why it does like that. Have >>> anybody come across this issue, if so please provide pointers to resolve it. >>> >>> Thanks in advance for your time regarding this. >>> >>> Thank you, >>> AN >>> >>> >>> >>> _________________________________________________________________ >>> Hotmail: Trusted email with powerful SPAM protection. >>> http://clk.atdmt.com/GBL/go/196390707/direct/01/ >>> -------------- next part -------------- >>> An HTML attachment was scrubbed... >>> URL: >>> <https://www.redhat.com/archives/rhelv5-list/attachments/20100127/b6ccca35/attachment.html> >>> >>> ------------------------------ >>> >>> Message: 2 >>> Date: Wed, 27 Jan 2010 22:55:17 +0000 >>> From: Sam Sharpe <[email protected]> >>> To: "Red Hat Enterprise Linux 5 (Tikanga) discussion mailing-list" >>> <[email protected]> >>> Subject: Re: [rhelv5-list] RHEL-5.3 Network Install on Sun Fire x4240 >>> Message-ID: >>> <[email protected]> >>> Content-Type: text/plain; charset=ISO-8859-1 >>> >>> 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 >>> >>> >>> >>> ------------------------------ >>> >>> Message: 3 >>> Date: Thu, 28 Jan 2010 07:54:28 +0800 >>> From: Colin Coe <[email protected]> >>> To: "Red Hat Enterprise Linux 5 (Tikanga) discussion mailing-list" >>> <[email protected]> >>> Subject: Re: [rhelv5-list] RHEL-5.3 Network Install on Sun Fire x4240 >>> Message-ID: >>> <[email protected]> >>> Content-Type: text/plain; charset=ISO-8859-1 >>> >>> 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 >>> >>> >>> >>> ------------------------------ >>> >>> Message: 4 >>> Date: Wed, 27 Jan 2010 19:05:12 -0600 >>> From: Eugene Vilensky <[email protected]> >>> To: "Red Hat Enterprise Linux 5 (Tikanga) discussion mailing-list" >>> <[email protected]> >>> Subject: Re: [rhelv5-list] recent install trashes refit >>> Message-ID: >>> <[email protected]> >>> Content-Type: text/plain; charset=ISO-8859-1 >>> >>>> When I list the partitions in the >>>> refit shell, the Linux partitions are listed as 'basic data', is it >>>> possible >>>> this is the problem? >>>> >>>> Any insights would be greatly appreciated. >>> >>> Do the last two entries here help at all? >>> >>> http://refit.sourceforge.net/doc/ >>> >>> >>> >>> ------------------------------ >>> >>> _______________________________________________ >>> rhelv5-list mailing list >>> [email protected] >>> https://www.redhat.com/mailman/listinfo/rhelv5-list >>> >>> >>> End of rhelv5-list Digest, Vol 35, Issue 28 >>> ******************************************* >> >> ________________________________ >> Hotmail: Trusted email with powerful SPAM protection. Sign up now. >> _______________________________________________ >> rhelv5-list mailing list >> [email protected] >> https://www.redhat.com/mailman/listinfo/rhelv5-list >> >> > > That should be pci=bfsort, but I don't think that is a valid kernel > param for 5.3, at least on the newer updates. It worked on OEL 5.3 > though. ksdevice=link may not work for you either, depending on how > many NICs you have active. > > The two Intel's are probably your on-boards. Plug in only one of > these and try again. If you are using DHCP, then you shouldn't have > to specify a port anyway. Or you can just do ksdevice=ethX until you > hit the correct one.
ksdevice=00:00:00:00:00:00 (MAC address of the nic to use) is the only method that has reliably worked for us on RHEL5. -darren _______________________________________________ rhelv5-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/rhelv5-list
