kickstart seems not to process: ks.cfg

Philip Rowlands phr at doc.ic.ac.uk
Tue Jun 28 14:06:15 UTC 2005


On Tue, 28 Jun 2005 extern.Tobias.Kronwitter at AUDI.DE wrote:

>The following steps are performed:
>
>1. dhcp / pxeboot
>2. load ks.cfg via nfs
>3. install OS via nfs
>
>Step 1 works fine.
>However there are complaints about missing parameters:
[snip]

>PXE entry point found (we hope) at 9C19:0106
>
>My IP address seems to be 0AC78395 10.199.131.149
>ip=10.199.131.149:10.199.131.150:10.199.131.129:255.255.255.224
>
>TFTP prefix: /el-3.0/sun/
>Trying to load: pxelinux.cfg/01-00-0e-0c-30-b5-e0
>Trying to load: pxelinux.cfg/0AC78395
>Missing parameter in config file.
>Missing parameter in config file.
>Missing parameter in config file.
>0AC78395: PXE installing Enterprise Linux 3.0 in 10 seconds
>boot:
>+---------------------------------------------------------------------------
>
>This is the corresponding pxeboot - config file (0AC78395):
>
>serial 1 9600
>default do_inst
>display pxelinux.cfg/bootinfo_0AC78395.txt
>prompt 1
>timeout 100
>
>label do_inst
>  kernel ../images/pxeboot/vmlinuz
>  append ksdevice=eth1 console=ttyS1,9600n8 load_ramdisk=1
>initrd=install/initrd_rdh-es-v3.img
>ks=nfs:10.199.131.150:/tftpboot/ks_0AC78395.cfg network
>#

Is that "append" line actually wrapped? If so, try un-wrapping. Those
"Missing parameter" errors mean that your pxelinux.cfg files is probably
not being parsed as intended. Do relative paths works for the "kernel"
arg? (Remember these files are being retreived by PXElinux via TFTP.)


Cheers,
Phil




More information about the Kickstart-list mailing list