Tru Huynh wrote: > Hi, > > On Fri, Aug 11, 2006 at 05:33:39PM -0700, Tracy R Reed wrote: > >> I have successfully set up a very nice kickstart install with the i386 >> version of CentOS 4.3 and it works great. I am using a custom kickstart >> > ... > >> 0.522788 192.168.0.201 -> 192.168.0.7 TFTP Read Request, File: >> linux-install/CentOS4.3/x86_64/vmlinuz, Transfer type: octet >> 2.487047 192.168.0.201 -> 192.168.0.7 TFTP Read Request, File: >> linux-install/CentOS4.3/x86_64/initrd.img, Transfer type: octet >> >> But then it never tries to get the ks.cfg. I am booting it with: >> >> label centos >> kernel CentOS4.3/x86_64/vmlinuz >> append initrd=CentOS4.3/x86_64/initrd.img ramdisk_size=7000 >> ksdevice=eth0 ks=http://192.168.0.7/network-install/ks.cfg.x86_64 >> >> (that last line should be all one line) >> >> > Are you sure your ksdevice is eth0? > could it be i386->eth0 and x86_64->eth1 > > /usr/share/doc/anaconda-10.1.1.37 > ... > ksdevice Takes one of 4 types of argument which tells install > what network device to use for kickstart from network: > ... > - An argument like 00:12:34:56:78:9a indicating the > MAC address of a specific interface > - The keyword `link' indicating that the first > interface with link up > ... > > ksdevice=00:0c:29:14:3a:c5 or ksdevice=link ? > > Cheers, > > Tru I have made a boot cdrom and in that one I use these switches for append (and it is working for both i386 and x86_64) : append initrd=initrd.img ramdisk_size=8192 ks=http://192.168.10.241/ks.cfg ksdevice=eth0 nofirewire nopcmcia skipddc noparport I tried the ksdevice=link but that didn't work. What is the output from the Alt+F3(or was it F4) when you boot your kickstart install ? /Mats --- "Those that sacrifice essential liberty to obtain a little temporary safety deserve neither liberty nor safety." -- Ben Franklin (1759)