-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 anthony parackel wrote: > Hi, > > First off, I?d like to thank Chip, Mike and Colin for > their help earlier. > > I was asked to postpone this project for about a week > but eventually I experimented with different setups > > and managed to create a kickstart environment that > utilizes PXE boot. > > > Well, now I?m getting this strange error message after > the client boots off the PXE/DHCP server: > > > > * running dhcp for eth0 > > * pump told us: No DHCP reply received > > * eth0 isn?t a wireless adapter > > > > It looks like the DHCP server can?t assign an ip. > > > > This error is a little confusing because the kickstart > client is definitely getting an IP from the DHCP > server which allows > > it to boot into PXE. After initially getting an IP > to boot into PXE, anaconda begins to install the > driver modules. > > What I then see is various drivers loading like the > megaraid SCSI, megaraid SAS and NIC drivers. > > > > The installation just halts when it asks me for the > networking info. Here?s what I tried: > > > > I tried to do a kick off of a Dell 1950 and 2950. I > tried to boot off of both NICs to no avail > I connected a crossover cable from the kickstart > client directly to the DHCP/PXE server. > I get the same results. An initial ip is assigned the > first time for a PXE boot but doesn?t subsequently > > get one during the anaconda install phase. Anthony, The first two links below provide you with a check list of things to look at. The second link provides a new spin on the problem. Was your ks file created with an MS Windows editor? If so you need to use a cross-platform editor like vim and :set ff=unix and save the file. The open source notepad2 Ms Windows editor can also correctly format the ks.cfg file as a linux/unix formatted txt file. You haven't told us the release of anaconda or which version of the anaconda related product that you are using: Red Hat, Fedora Core, CentOS. Kernel bugs could be a factor. Since you mention multiple nics being involved, then you may need to supply the desired nic for installation on the boot line. There's notes below on this too. This error appears to be maddening problem because of lack of search results. Please post back with progress or a final resolution. Regards, Greg http://info.ccone.at/INFO/Mail-Archives/redhat/Feb-2004/msg01049.html http://www.themightywizard.com/weblog/archives/000153.html http://www.redhat.com/archives/kickstart-list/2002-July/msg00141.html http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=960683 http://bugzilla.redhat.com/bugzilla/114092 This is from the anaconda 11.0.5 docs/command-line.txt file. ksdevice Takes one of 4 types of argument which tells install what network device to use for kickstart from network: - An argument like 'eth0' naming a specific interface - An argument like 00:12:34:56:78:9a indicating the MAC address of a specific interface - The keyword `link' indicating that the first interface with link up - The keyword `bootif' indicating that the MAC address indicated by the BOOTIF command line option will be used to locate the boot interface. BOOTIF is automagically supplied by pxelinux when you include the option `IPAPPEND 2' in your pxelinux.cfg file -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iD8DBQFFaSOxxyxe5L6mr7IRAhgKAJ9TUJ5DI2qVqjs0VS8im3b3E/uxhQCfREkB 11zwaITHXVeI8boOLqX/IfM= =rQC6 -----END PGP SIGNATURE-----
