home | list info | list archive | date index | thread index

[OCLUG-Tech] Re: GCC: Request for help to get cluster booting!

  • Subject: [OCLUG-Tech] Re: GCC: Request for help to get cluster booting!
  • From: Richard Cook <rpcook [ at ] pobox [ dot ] com>
  • Date: Wed, 17 Sep 2008 23:46:53 -0400
Thanks Stephen, Bart and Peter!

I will keep your PXE suggestions (good readings) but alas, the damn motherboard only supports RPL network booting and it is broken!

By using the USB key with syslinux on it I can get it to try and download a file. It is the file I am getting messed up (probably because I am reading too much about PXE!) :)

The USB key contains four files:

dos.bss
ldlinux.sys
sis900.zli
syslinux.cfg


syslinux.cfg contains:
  default sis900.zli
  timeout 1

sis900 is my built in NIC chip.

I used ROM-o-matic to build the sis900.zli file.

/etc/dhcp3/dhcpd.config contains:
---------------------------------

subnet 192.168.1.0 netmask 255.255.255.0 {
  range 192.168.1.240 192.168.1.253;
}

filename "vmlinuz";

host gcc2 {
  hardware ethernet  00:0d:87:07:66:bd;
  fixed-address 192.168.1.2;
}

...



/etc/default/tftpd-hpa contains:
--------------------------------
RUN_DAEMON="yes"
OPTIONS="-l -s /tftpboot"


/etc/inet.d conatins:
---------------------
tftp    dgram   udp     wait    root    /usr/sbin/tcpd  in.tftpd


I am not sure that I need both of these as I just added tftpd-hpa and saw no difference in behaviour. :(

An initial attempt and running initramfs (I think) now has the following in /tftpboot :
-rw-r--r-- 1 root root     159 2008-09-15 23:59 default
-rw-r--r-- 2 root root 7070503 2008-09-11 15:24 initrd.img-2.6.22-14-server
-rw-r--r-- 1 root root 1787256 2008-09-11 15:19 vmlinuz-2.6.22-14-server

with default containing:
------------------------
LABEL linux
KERNEL vmlinuz-2.6.22-14-server
APPEND root=/dev/nfs initrd=initrd.img-2.6.22-14-server nfsroot=192.168.2.1:/nfs root ip=dhcp rw
PROMPT 1
TIMEOUT 0

I think that the default file is only required for PXE but am not sure.
Perhaps I will change the dhcpd.conf file to say:
  filename "default";

and see what happens?  :)

Tomorrow, perhaps.
Good night and thank you all!

Richard Cook