This kernel works! It brings the interfaces up correctly! It's crashing for other reasons now, but I can work on those (I think I've got an error in my partitioning file).
Thank you SO much. You've made my day very bright indeed!
And thanks to everyone who helped me diagnose and fix the problem. It's not working perfectly yet, but I hope to get things going by tomorrow!
Jason
On Dec 9, 2003, at 2:22 PM, Bernard Li wrote:
Hey Jason:--------------
Try these files from Frank Crawford, it might work with your bcm5704.
Cheers,
Bernard
From: Frank Crawford <[EMAIL PROTECTED]>
Date: September 25, 2003 5:33:54 PM GMT-06:00
To: Bernard Li <[EMAIL PROTECTED]>
Subject: Re: [Oscar-users] SystemImager and Broadcom Tigon3 NIC
Bernard,
The files I sent to Jess are attached.
Frank
On Fri, 2003-09-26 at 03:23, Bernard Li wrote:
Hey Frank:--
I wouldn't mind getting a copy of those files. We also got some
Opterons though we haven't put OSCAR on them yet. But I anticipate they
may have the same problem.
Thanks in advance,
Bernard
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.
ac3
Suite G16, Bay 7, Locomotive Workshop Phone: 02 9209 4600
Australian Technology Park Fax: 02 9209 4611
Eveleigh NSW 1430
<newPXEboot.tgz>
Jason Hlady, B. Sc., M. Sc. (Chem), Adv. Cert. (Comp. Sci.)
Programmer/Analyst (Bioinformatics Specialist)
U of Saskatchewan, Bioinformatics Research Laboratory (BIRL)
[EMAIL PROTECTED] (306) 966-2075
