Everyone,
There are two versions of the tulip card, the old and new. When I
built the network boot kernel, I supported the new version, since old and
new are mutually exclusive. Tom Naughton from Oak Ridge National Lab did
create a kernel that supported the older version, and posted it to this
newsgroup last week I think. Ken Schwartz said this new kernel did not work
for him. I suggested that he try the bzImage.242 that we ship and see if
that works any better. I would suggest that if anyone has a tulip card
they try the boot kernel we ship with oscar, and if that fails, the boot
kernel that Tom Naughton built and posted last week. If that fails, try the
bzImage.242 that ships with oscar.
A little tutorial on boot kernels follows.
The boot kernel is only used to network boot the node, it is not
necessarily the kernel you use to install on the local harddrive, and use
when the node is booted from harddrive. The netboot kernel comes in two
flavors, tagged and untagged. The untagged kernel is created during the
kernel build process and is named bzImage. The luikernel.config file that
we ship with oscar is the .config file that is used for this untagged
version. You use the untagged kernel when doing true network boot, PXE
method, without using the diskette. A tagged kernel is created by running
mknbi-linux against an untagged kernel. mknbi-linux used to be distributed
as part of etherboot, but has since become a separate project. You would
run mknbi-linux against an untagged kernel, and call the output vmlinuz by
convention. You then use etherboot to build the network boot diskette with
the device driver for the NIC on your node. You boot the etherboot
diskette on the node, and it will load the vmlinuz (tagged) file from the
server and configure the NIC.
One thing you should know about the network boot process is that the
NIC gets configured twice. In PXE, it's configured by the BIOS the first
time, then a second time by the network boot kernel, which configures it
for tcp/ip using the information passed by dhcp. In the case of etherboot,
the NIC gets configured by driver on the etherboot diskette, which then
requests a tagged kernel. The tagged kernel configures the NIC a second
time, also for tcp/ip using the information passed from dhcp.
So, regardless of whether you use pxe or etherboot, you pretty
quickly get to the same place in the boot process... I hope this helps with
some of the questions that I'm hearing out there.
best, Rich
Kaizaad Bilimorya <[EMAIL PROTECTED]>@lists.sourceforge.net on
12/19/2001 11:59:30 AM
Sent by: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
cc:
Subject: [Oscar-users] 3C905CX & OSCAR
HiYa,
Since all the nodes we have are configured with builtin 3C905CX cards I
can't "avoid this adapter completely if at all possible" like the notes
section says.
I get as far as the node gets an ip from the DHCP server and the
/tftp/vmlinuz is sent. But the node doesn't boot with it.
I read a post by Richard Ferri
(http://www.geocrawler.com/archives/3/13442/2001/12/0/7247985/)
and if I interperate what is going on correctly, the kernel that was
tftpd'ed over does not configure the ethernet device correctly. And
according to http://oscar.sourceforge.net/notes.php#item5 "the network
boot kernel provided with LUI contains a driver (3c59x) that does not
properly initialize this adapter, rendering it unable to receive data"
Is there anything I can do? I would still like to use OSCAR but if I
can't get this resolved, I guess I will have to drop it and do all the
package installs seperatly by hand.
Has anyone got OSCAR to work using a 3CO95 card? If so can you post the
steps on how you did it?
Any help/input/direction is greatly appreciated.
Regards
kaizaad
_______________________________________________
Oscar-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/oscar-users
_______________________________________________
Oscar-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/oscar-users
