>Also, here are what the HEX files look like from the /tftboot/pxelinux.cfg directory. > >This is the one that will get to the text install before returning the "ks.cfg file could not be found" error: (I've replaced IP addresses with x) > ># Install >SERIAL 1 9600 >DEFAULT csm >LABEL csm >KERNEL csm/ks7.2z >APPEND root=/dev/ram mem=128M ks=nfs:xxx.xx.x.x:/csminstall/csm/1.2.0/kickstart.RedHat7.2/xxx.xx.x.x-kicks tart initrd=csm/ks7.2.gz Here's a couple things you can check On the nfs server (xxx.xx.x.x) check the following: - Does /csminstall/csm/1.2.0/kickstart.RedHat7.2/xxx.xx.x.x-kickstart? - Are you exporting /csminstall? (run 'exportfs' to check) ># Install >SERIAL 1 9600 >DEFAULT csm >LABEL csm >KERNEL csm/ks7.2z >APPEND root=/dev/ram mem=128M console=ttyS1,9600 ks=nfs:xxx.xx.x.x:/csminstall/csm/1.2.0/kickstart.RedHat7.2/xxx.xx.x.x-kicks tart >initrd=csm/ks7.2.gz >As you can see, the only change I've made is removing the console attribute in the APPEND statement. I'm fairly new to the linux/unix world, and I'm >running out of ideas quickly. Any other tips anyone could offer would be greatly appreciated!! removing the console attribute from the append line enables you to see the output on the screen(vga) rather then sending it through the console(ttyS1/COM A). both are unable to find the kickstart file you just can't see the output because you haven't hooked up the terminal equipment yet? (i'm guessing) it looks like you are using csm, so i would advise calling IBM support for the product. also check the xCat documentation from IBM. CSM and xCat are pretty similar. - mark
