Thank you so very much. This worked perfectly, and now I understand how this process works. I didn't understand that you used the normal kernel coupled with the systeimager config file to make this specialized kernel.
You are awesome!
Jess
Frank Crawford wrote:
Jess, I've attached the files below, but the basic steps are:
1) Get a very recent kernel source (I used the latest Red Hat 9, but 2.4.22 should be fine - check the tg3.c driver version), 2) copy /usr/share/systemimager/boot/i386/standard/config to /usr/src/linux-2.4/.config, run make oldconfig, make new kernel and modules, etc. Note, here you may want to make an even more specialised kernel, with all the drivers needed compiled in. This kernel will only be used for the PXE boot, so can be dumb and small. Also, you need to ensure cramfs is compiled in, as the initrd image is in cramfs format. 3) copy the new kernel to /tftpboot, 4) create a new boel_binaries.tar.gz file (in /usr/share/systemimager/boot/i386/standard directory) with the new modules (including the correct path). Easiest way is to extract it all, replace the /lib/modules directory and then tar it up again.
You should then be okay to go. With this build list you don't need to change initrd.img as no modules are in there to change. If you do have to add modules, it is a bit trickier. Again, that involves mounting the initrd.img file on a loopback device, copying everything out, and then creating a new cramfs file, but isn't needed here.
I'm sending you the three files separately, as I don't think the whole list wants them.
Frank
On Fri, 2003-09-26 at 00:08, Jess Cannata wrote:
Frank,
Thanks for the help. If you could send me instructions, and/or the files, or whatever, I would appreciate it. I just haven't seen how to actually create a new initrd and boel_binaries.tar.gz. I would really like to know how to build these images myself, but the SystemImager documentation leaves a lot to be desired.
Thanks.
Jess
Frank Crawford wrote:
Jess, You can do this, but not too easily. Put simply, you have to make a new kernel, with the options you require, in particular 'cramfs' and then put the new kernel, initrd and /usr/share/systemimager/boot/i386/standard/boel_binaries.tar.gz file (as it includes some modules) into appropriate places.
If you want, I can send you all of these, since I've been through the same issue for a Dell 1750 installation.
Frank
On Thu, 2003-09-25 at 23:35, Jess Cannata wrote:
I have two Opteron test computers with RedHat 9.0 (32-bit mode) on them and I am trying to install Oscar 2.3. I can create the images, but when I network boot the node to load the image, the node networks boots but when it loads the small boot image passed to it by PXE it can't load the network drivers (the motherboard has Broadcom Tigon3 Gigabit NICs). When it tries to load tg3.o version 1.2, Nov 14, 2002 (the Broadcom drivers) it says:
tg3: Problem fetching invariants of chip; aborting.
I know that there is a newer tg3.o driver because I have it installed--and working--on the master node. What I haven't been able to figure out is how to create an new initrd.img that resides in /tftpboot that has the new tg3 driver included. I've also created a boot floppy, but the the initrd.img appears to tbe the exact same as the image in /tftpboot and it gives the same error. Is it possible to make a new initrd.img with support for new NIC drivers? I've searched the Systemimager documentation, but I haven't found my answer. Does anyone know how to "easily" do this?
Thanks.
------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Oscar-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/oscar-users
