I had the same problem until I switched to using DNS names for the server both at the syslinux boot prompt, that is, for example, linux ks=nfs:fcserver.mynet:/disks/fc2/ks/bugs where bugs is the ks.cfg for the bugs installee. And, for the 'nfs' statement in the kickstart file itself, that is, nfs --server=fcserver.mynet --dir=/disks/fc2/cdrom The symptoms were exactly as you described. The DCHP part goes off without problems, but the installee never contacts the NFS server. Hope this helps. I'm guessing they changed anaconda. Live and learn. Ken On Thu, 27 May 2004 paul@xxxxxxxxxxxxx wrote: > Hi, > > I've configured DHCP and PXE for a network kickstart install. DHCP > works, pxe works, the kernel (from images/pxeboot) and initrd.img > load, I've passed the ks option as a boot parameter, the machine > sends a DHCP request, gets a response, but then makes no attempt > to contact the NFS server for a ks.cfg file. Any idea what's > missing? I'm not passing any argument to ks, therefore I believe > it should be passing default parameters to the NFS server (192.168.8.2 > below). > > Here's the response from my DHCP server for the anaconda DHCP > request: > > 08:30:26.893575 0:0:39:89:be:15 0:6:1b:da:fe:b9 ip 342: 192.168.8.1.bootps > 192.168.8.10.bootpc: [udp sum ok] xid:0xee401bda secs:768 Y:192.168.8.10 S:192.168.8.2 sname "hut2" file "/kickstart/" vend-rfc1048 DHCP:ACK SID:81.2.102.1 LT:0 SM:255.255.255.0 NS:192.168.8.1 DN:"sbrk.co.uk" BR:192.168.8.255 HN:"pxetest" [tos 0x10] (ttl 16, id 0, len 328) > > After this no network traffic is seen and anaconda goes into an > interactive install. > > Paul > > > _______________________________________________ > Kickstart-list mailing list > Kickstart-list@xxxxxxxxxx > https://www.redhat.com/mailman/listinfo/kickstart-list >
