I'm still digging on this one guys, and it may be out of the hands of the kickstart list at this point. I have just one question for the group, and it's this: Has anyone been successful kickstarting a Redhat psyche (8.0) installation using the 8139too.o driver? It looks like there is a difference between the 7.3 release of this driver and the 8.0, and while the copy of the 8139too.o driver works with the distribution as installed off the CD's. I cannot reproduce this working binary when building the kernel for 8.0 - even using the default config-2.4.18-14 configuration parameters for the kernel. It stands to reason then, that the version of the 8130too.o driver in the bootnet.img file is equally as broken. Any advise on how to track this one down? -Ace > -----Original Message----- > From: kickstart-list-admin@xxxxxxxxxx > [mailto:kickstart-list-admin@xxxxxxxxxx] On Behalf Of > knights-of-ni@xxxxxxxxxxxxxxxx > Sent: Thursday, October 10, 2002 9:32 AM > To: kickstart-list@xxxxxxxxxx > Subject: RE: Hassles with 8.0 - renegotiating the DHCP?!? > > > The description you give below Kelley, makes all kind of > sense. The client just isn't listening to the responses from > the DHCP server, and indeed it seems to be Pump that is > controlling this. > > Did you notice this change when migrating to 8.0 as well, or > was it earlier? I am confused, because 7.3 worked with this > both versions of PXELINUX here, and 8.0 did not. It is my > impression that something is wrong with Psyche... > > I'll try back-revving to 1.65, and see what that gives me... > > > > -Ace > > > > > -----Original Message----- > > From: kickstart-list-admin@xxxxxxxxxx > > [mailto:kickstart-list-admin@xxxxxxxxxx] On Behalf Of K . Spoon > > Sent: Wednesday, October 09, 2002 9:35 PM > > To: kickstart-list@xxxxxxxxxx > > Subject: Re: Hassles with 8.0 - renegotiating the DHCP?!? > > > > > > On Wed, Oct 09, 2002 at 06:56:32PM -0400, > > knights-of-ni@xxxxxxxxxxxxxxxx wrote: > > > Thanks Kelley, I'll have a look at the bug report. I > thought along > > > the same lines as you when this error started happening, > > and updated > > > my pxelinux.0, but found the same problem. The release of > > pxelinux.0 > > > that I am using is out of the latest syslinux package > > (1.76), though I > > > am unsure what rev. this is. Should I be using a > different version? > > > > > > The client *does* try a DHCPDISCOVER 4 times before giving up > > > though... > > > > Yeah, but those are kind of a red herring (or at least they > > were for me). The discovers weren't what was failing as much > > as it was that pump was failing to see the reply. > > > > Here's the relevant line from loader.c: > > > > if (kickstartNetwork(&devName, &netDev, "dhcp", flags)) { > > logMessage("no dhcp response received"); > > return 1; > > } > > > > In my case, pxelinux was doing something funky that left > > something (driver, kernel, or whatever) in a state that > > prevented the kickstartNetwork() from seeing the dhcp > > server's reply. Calling kickstartNetwork() a second time > > seemed to reset whatever was hanging, and the first discover in the > > second instance of kickstartNetwork() finally saw the reply. > > > > My suggestion though, rather than trying to patch loader and > > rebuild boot images, is to try another version of pxelinux > > first. 1.65 is working like a champ for 6.2 to 8.0 for me, > > so you might want to give that version a shot and see what happens. > > > > -- > > Kelley Spoon Main: > 210-892-4000 > > Rackspace Managed Hosting Fax: > 210-892-4329 > > 112 East Pecan, Suite 600 Email: > kspoon@xxxxxxxxxxxxx > > San Antonio, TX 78205 > <http://www.rackspace.com> > > > > > > > > > _______________________________________________ > > Kickstart-list mailing list > > Kickstart-list@xxxxxxxxxx > > https://listman.redhat.com/mailman/listinfo/ki> ckstart-list > > > > > > _______________________________________________ > Kickstart-list mailing list > Kickstart-list@xxxxxxxxxx > https://listman.redhat.com/mailman/listinfo/kickstart-list >
