Bruce,
First off, are you sure you are dealing with the right kernel? The
boel kernel is only used for the PXE booting and install, after that a
different kernel is used on the compute nodes themselves.
The boel kernel, ramdisk and also boel_binaries.tar.gz (which contain
other kernel modules) are in
/usr/share/systemimager/boot/i386/standard/ From here the kernel and
ramdisk are copied to /tftpboot during the OSCAR install process. You
may need to make sure that both of these locations are the same.
If you are talking about the kernel that is used on the compute node
itself, it is copied from /var/lib/systemimager/images/XXX/boot, which
is copied to the node during the install.
BTW, when you say that you had no luck with the other kernels, did it
not boot, or was it just that it didn't load the correct network
driver? If you have a monitor and keyboard plugged into one of the
compute nodes during the initial node you may be able to track down
additional details. Once it works for one node it almost always will
roll out to all the others.
If you have a look through the list archives from around September, I
sent in some details about how to replace the PXE boot kernel with one
of your own (RH 9 in my case) and what other files needed to be updated.
Frank
On Sat, 2004-01-24 at 01:27, Bruce Becker wrote:
> Hello all
>
> I've just set up a new OSCAR cluster (RH9, OSCAR-3.0 from CVS). Almost
> everything went well, until I tried to re-image my nodes. The standard
> kernel that gets booted does not have the driver for my network card built
> into it (sundance.o, for the D-LINK card), so the network boot fails. I've
> tried to edit the ramdisk, to load the module using the INSMOD_COMMANDS
> script under my_modules on the ramdisk. I inserted the line insmod
> sundance.o and copied the module to that directory. Of course, this didn't
> work, because I was running a different kernel (2.4.24smp, instead of
> boel).
>
> I found out that boel is 2.4.20 with patches, so i found that source,
> applied the patches, and selected the driver to be compiled into the
> kernel - no luck. I tried the stock kernel, with the driver compiled in as
> a module, with the insmod command - no luck.
>
> What am i doing wrong, and how do I get my nodes to network boot ?
>
> Thanks,
> Bruce
>
> --
> Bruce Becker
> UCT-CERN Research Center - University of Cape Town
> Room 405, R.W. James Building, University Avenue North
> Private Bag RONDEBOSCH 7700
>
> tel :(w) +27 21 650 3356 | (m) +27 82 537 9425 | (f) +27 21 650 3342
> WEB :http://hep.phy.uct.ac.za/~becker | AIM : brucellino
>
>
>
>
> -------------------------------------------------------
> The SF.Net email is sponsored by EclipseCon 2004
> Premiere Conference on Open Tools Development and Integration
> See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
> http://www.eclipsecon.org/osdn
> _______________________________________________
> Oscar-users mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/oscar-users
--
ac3
Suite G16, Bay 7, Locomotive Workshop Phone: 02 9209 4600
Australian Technology Park Fax: 02 9209 4611
Eveleigh NSW 1430
-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
_______________________________________________
Oscar-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/oscar-users
