OK, thanks to Marcel, I have it successfully pulling the pxelinux.0 where its failing now, is at the following: Jun 16 13:54:40 yum1 dhcpd: DHCPDISCOVER from 00:03:47:11:3c:6b via eth0 Jun 16 13:54:41 yum1 dhcpd: DHCPOFFER on 10.10.232.80 to 00:03:47:11:3c:6b via eth0 Jun 16 13:54:41 yum1 dhcpd: DHCPREQUEST for 10.10.232.80 (10.10.232.54) from 00:03:47:11:3c:6b via eth0 Jun 16 13:54:41 yum1 dhcpd: DHCPACK on 10.10.232.80 to 00:03:47:11:3c:6b via eth0 Jun 16 17:54:41 yum1 in.tftpd[9505]: tftp: client does not accept options Jun 16 13:54:41 yum1 dhcpd: DHCPINFORM from 10.10.232.231 via eth0: not authoritative for subnet 10.10.232.0 Jun 16 13:54:41 yum1 dhcpd: If this DHCP server is authoritative for that subnet, Jun 16 13:54:41 yum1 dhcpd: please write an `authoritative;' directive either in the Jun 16 13:54:41 yum1 dhcpd: subnet declaration or in some scope that encloses the Jun 16 13:54:41 yum1 dhcpd: subnet declaration - for example, write it at the top Jun 16 13:54:41 yum1 dhcpd: of the dhcpd.conf file. Jun 16 13:54:44 yum1 dhcpd: DHCPINFORM from 10.10.232.231 via eth0: not authoritative for subnet 10.10.232.0 Jun 16 13:55:47 yum1 dhcpd: DHCPDISCOVER from 00:03:47:11:3c:6b via eth0 Jun 16 13:55:47 yum1 dhcpd: DHCPREQUEST for 10.10.232.55 (10.10.1.13) from 00:03:47:11:3c:6b via eth0: unknown lease 10.10.232.55. Jun 16 13:55:48 yum1 dhcpd: DHCPOFFER on 10.10.232.80 to 00:03:47:11:3c:6b via eth0 I can see the server actually loading the bootloader and I can see this in the messages log now: Jun 16 14:11:48 yum1 rpc.mountd: authenticated mount request from 10.10.232.80:750 for /repo/fedora/linux/core/2/i386/os (/repo) Actually I am unsure if it is able to find my kickstart config file. The /repo above is of course the install base (Fedora/images/etc under the OS tree). Here is my current ks-cf2.cfg file for completeness: # Kickstart file automatically generated by anaconda. install nfs --server=10.10.232.54 --dir=/repo/fedora/linux/core/2/i386/os lang en_US.UTF-8 langsupport --default en_US.UTF-8 en_US.UTF-8 keyboard us skipx network --device eth0 --bootproto dhcp --hostname ag800 network --device eth1 --bootproto dhcp --hostname ag800 rootpw --iscrypted $1$.pio2FpF$qdZBN7oU0oOG6R3oV6y5X. firewall --disabled selinux --disabled authconfig --enableshadow --enablemd5 timezone America/New_York bootloader --location=mbr --append rhgb quiet # The following is the partition information you requested # Note that any partitions you deleted are not expressed # here so unless you clear all partitions first, this is # not guaranteed to work clearpart --linux part /boot --fstype ext3 --size=101 part /disk2 --fstype ext3 --size=12289 part / --fstype ext3 --size=12289 part swap --size=2048 part /weblog --fstype ext3 --size=1 --grow %packages --resolvedeps @ web-server @ mail-server @ dns-server @ dialup @ network-server @ sql-server @ editors @ admin-tools @ system-tools @ news-server @ smb-server @ authoring-and-publishing @ sound-and-video @ server-cfg @ graphics @ ftp-server @ development-tools @ engineering-and-scientific @ text-internet kernel-smp grub e2fsprogs %post # The Last Thing happening in Kickstart: # get a file via TFTP which indicates we are done. echo "get Kickstart_end" | /usr/bin/tftp 10.10.232.54 Now, when I rebooted this test box this morning, it grabs an IP from the dhcp server, is able to receive and load the pxelinux bootloader, but in the virtual console 3 I see the following after it runs through and loads the kernel: * NFS install method detected will use Rhupdates/ * Running anaconda script /usr/bin/anaconda * Display mode=t * Method = nfs://mnt/source/ . * ddcprobe returned bogus values: ID Name HorizSync VertSync * anaconda floppy devices is fd0 * Running kickstart %pre scripts * All kickstart %pre scripts have been run Which confuses me a little bit as I don't quite understand where its getting the nfs methof pointing to Rhupdates and some of the other stuff. As the pxelinux.cfg default file reads as follows: DEFAULT linux SERIAL 0,38400n8 LABEL linux KERNEL vmlinuz-fc2 APPEND ksdevice=eth0 console=tty0 console=ttyS0,38400 load_ramdisk=1 initrd=initrd-fc2.img network ip=dhcp ks=nfs:10.10.232.54:/tftp/ks-fc2.cfg Any one have any ideas? Thanks for all your help, again, and responses - very helpful. Michael Weiner -- fedora-list mailing list fedora-list@xxxxxxxxxx To unsubscribe: http://www.redhat.com/mailman/listinfo/fedora-list
