I have seen this before. GigE adapters have been troublesome with DHCP and kickstart. If kickstart gave it a little more time it would work. Check your dhcp server logs for requests. The most common issue is that spanning tree is not disabled on the port of your switch for that node. When the NIC goes active, spanning tree takes too much time and then DHCP times out. GigE ports on switches almost always have spanning tree enabled. So do all Cisco switches. You do not need it on ports with nodes. Another problem I have seen is that if the def gateway is not sent as part of the DHCP reply manual works, but unattended does not. > -----Original Message----- > From: kickstart-list-admin@xxxxxxxxxx > [mailto:kickstart-list-admin@xxxxxxxxxx] On Behalf Of > Staniforth, Paul [IES] > Sent: Monday, August 11, 2003 8:41 AM > To: 'redhat kickstart list' > Subject: RE: Manual NFS install works but fails for kickstart > with added network driver > > > This is actually a Redhat 9 > > Paul R. Staniforth > Leeds Metropolitan University. > > > -----Original Message----- > > From: Staniforth, Paul [IES] > > Sent: Monday, August 11, 2003 10:06 AM > > To: 'redhat kickstart list' > > Subject: Manual NFS install works but fails for > kickstart with added > > network driver > > > > We have created a boot cd with an added driver for the > Broadcom BCM5700 > > NIC. This works fine with a manual NFS install but fails > when trying to do > > a DHCP based kickstart install, from the messages it gets it correct > > information from the DHCP server but says it can't NFS > mount the directory > > with the kickstart file in it. > > The same boot CD will work OK with with machines with > RH supported > > NIC's, any help appreciated. > > > > Thanks, > > Paul R. Staniforth. > > > _______________________________________________ > Kickstart-list mailing list > Kickstart-list@xxxxxxxxxx > https://www.redhat.com/mailman/listinfo/kickstart-list >
