Are you sending the kickstart file via DHCP or retrieving via NFS? I've never had much luck retrieving it via DHCP. My system writes the pxelinux.cfg files on the fly and uses syntax like: label ks kernel images/rhel/3.0/as/qu1/vmlinuz append ksdevice=link initrd=images/rhel/3.0/as/qu1/initrd.img ks=nfs:156.132.110.110:/data/linux_build/kickstart/seahawk.imd.lab/ks.cfg lang= lowres devfs=nomount ramdisk_size=8192 James S. Martin, RHCE Contractor Administrative Office of the United States Courts Washington, DC (202) 502-2394 kickstart-list-bounces@xxxxxxxxxx wrote on 05/27/2004 05:04:46 AM: > 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
