I would agree with this. It seems that you are mounting the nfs directory successfully and kickstart has downloaded the ks.cfg. Check your ks.cfg for network lines. I have just added this to my ks.cfg for testing: network --device=eth0 network --device=eth1 on top of the entry network --device=eth2 --bootproto dhcp Kickstart is now sending DHCP requests for other network cards and failing - then prompting me for manual input. Try removing all network lines from your ks config except: network --device=eth0 --bootproto dhcp and give it another go. Harry On Thu, 25 Aug, Brian Long wrote: > On Thu, 2005-08-25 at 13:26 -0600, Lloyd T Brown wrote: > > Yes, the ks log shows the ip address being acquired correctly for > > eth0. There's this weird message about it waiting 15 seconds, though. > > I'm not sure what that means. The message about the eth0 getting a dhcp > > address is followed very shortly by a couple messages stating what the > > IP address for the NFS server is and what the path is to the ks.cfg > > file, so I'm pretty sure it's working correctly. After that, messages > > about it trying to acquire a dhcp address for eth1 come too, including a > > failure message. I'll see if I can get something more exact and post > > it, if that'd be helpful. > > Do you have "network --bootproto=dhcp --device=eth0" in ks.cfg? If you > have zero "network" lines, the docs say it's only supposed to use eth0, > but I wonder if this might be causing your problems. > > /Brian/ > -- Harry Mills Chief Technical Manager Opendium Ltd. http://www.opendium.com/
