RHEL 3 or 4? RHEL 4 enumerates the bus in a different
order than RHEL 3, so if there are any NIC's on expansion cards, this could
cause problems.
What happens if you pass the IP information at the boot:
prompt?
Chip
From: kickstart-list-bounces@xxxxxxxxxx [mailto:kickstart-list-bounces@xxxxxxxxxx] On Behalf Of anthony parackel
Sent: Thursday, November 23, 2006 1:21 PM
To: kickstart-list@xxxxxxxxxx
Subject: pump told us: No DHCP reply received
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.
Any suggestions would be VERY helpful. I can’t find
any useful info about this error message on google.
Thanks in advance,
anthony
Everyone is raving about the all-new Yahoo! Mail beta.
