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 script and the kernel and initrd from disc1/images. But when I try to duplicate this for a 64 bit setup (changing paths in my tftp server, ks.cfg, etc to point to the 64 bit stuff) it successfully tftp's everything just as it should (tethereal output follows): 0.000000 192.168.0.201 -> 192.168.0.7 TFTP Read Request, File: linux-install/pxelinux.0, Transfer type: octet 0.002503 192.168.0.201 -> 192.168.0.7 TFTP Read Request, File: linux-install/pxelinux.0, Transfer type: octet 0.039763 192.168.0.201 -> 192.168.0.7 TFTP Read Request, File: linux-install/pxelinux.cfg/01-00-0c-29-14-3a-c5, Transfer type: octet 0.045674 192.168.0.201 -> 192.168.0.7 TFTP Read Request, File: linux-install/msgs/boot.msg, Transfer type: octet 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) in the /tftpboot/linux-install/pxelinux.cfg/01-00-0c-29-14-3a-c5 config file which it tftp's so it should know that it needs to get the ks.cfg.x86_64 file. I have this same setup working for i386 and it seems to work fine. I would guess there might be some difference in the initrd's but for some reason /linuxrc is a symlink to sbin/init which is a binary executable instead of a shell script. Anyone know why it isn't a shell? And why would my x86_64 kickstart be behaving different from my i386? Any help is very much appreciated! -- Tracy R Reed http://ultraviolet.org A: Because we read from top to bottom, left to right Q: Why should I start my reply below the quoted text
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 -- Tru Huynh (CentOS-3 i386/x86_64 Package Maintenance) http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xBEFA581B -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: <http://lists.centos.org/pipermail/centos/attachments/20060812/7a76ac8d/attachment-0002.sig>
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, > > TruI 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)
Tru Huynh wrote:> Are you sure your ksdevice is eth0? > could it be i386->eth0 and x86_64->eth1I have other x86_64 boxes and they have always made the first ethernet device eth0. I have never heard of it being any other way. But just in case I tried it with ksdevice=link and it did not work any better. -- Tracy R Reed http://ultraviolet.org A: Because we read from top to bottom, left to right Q: Why should I start my reply below the quoted text