Matt,
Let's keep the discussion on list, maybe someone is listening that is
an ethernet guru.
First, if your server is nearly the same as your client, can you do
an lspci on the server and post the output to the mailing list? that will
tell us exactly what kind of ethernet NIC you have. From there we can
figure out the appropriate device driver.
You should not have to build a vmlinuz (a network boot kernel) except
in very rare circumstances. When I built the original kernel, I built in
support for all the ethernet devices that would compile cleanly (via-rhine
failed and I had to take it out, for example). I also had to choose between
the new tulip and the old tulip support since they were mutally exclusive
-- I chose the new support. Since there is support for just about all the
ethernet devices out there, you should not have to build a kernel.
My guess from the pxe output is that the firmware on the motherboard
and integrated adapter do not support PXE booting. Did you see the tftp
exchange take place in the pxe instance? If the kernel did get loaded,
then the kernel could not configure the ethernet NIC for some reason, and
the node crashed. On some nodes, this forces a reboot, on yours the node
just hung.
In the etherboot case, I suspect we just don't have the right
etherboot diskette yet; doing an lspci will tell us what NIC we're looking
at and from there we should be able to build a diskette easily.
regards, Rich
Matt Tucker <[EMAIL PROTECTED]> on 12/18/2001 10:29:45 AM
To: Richard C Ferri/Poughkeepsie/IBM@IBMUS
cc:
Subject: Re: [Oscar-users] Another network booting question sorry
Richard,
I'm back at the booting the client stage.
If I use the etherboot floppy I get :-
0 3c515 cards found
cs89x0: no cs8900 or cs8920 detected. Be sure to DISABLE PnP with SETUP
IP-Config:No Network devices available
Partition Check:
hda: hda1 hda2 hda3
Root-NFS:No NFS server available, giving up.
VFS: Unable to mount root fs via NFS, trying floppy.
VFS: insert root floppy and press enter.
I've check the nfs server by mounting /usr /tftpboot and /home, they all
work fine.
The only difference between the client and the server is that the server
has an extra network card/ cdrom and a graphics card.
Do need to make a new ramdisk or can I use the default ramdisk (this is
what I have done and I guess this could well be my problem, is it getting
that far or is it a vmlinuz problem?).
If I use pxe I get:-
.......
enabling EXTINT on CPU#0
ESR value before enabling vector:00000000
ESR value after enabling vector:00000000
calibrating APIC timer....
..... CPU clock speed is 1694.5609 MHz
..... host bus clock speed is 0.0000 MHz
cpu: 0 clocks: 0, slice: 0
Does this help you since it doesn't mean much to me?
I can see that with etherboot there is a network card problem so do I have
to make a new vmlinuz, if so how do I do this?
Thank you,
Matt
At 09:24 18/12/2001 -0500, you wrote:
>Matt,
> Yes of course we can help anyway studying the Earth... and no need
to
>apologize -- getting pxe, tftp, and nfs to cooperate all at the same time
>is problematic.
>
> In the PXE case, what are the last few messages you see before the
>node fails? Does the node reboot all by itself after a time? I assume you
>have just one ethernet adapter, an eepro100, and no integrated adapter, is
>this correct?
>
> In the etherboot case, I assume it got all the way to the end, said
>it could not moot root, and asked for a root file system on diskette, is
>that correct?
>
> In both of these cases, failing NFS could be the answer. Are you
>certain NFS is happy? Despite the fact that nfsd is running, I find that
>NFS is sometimes unhappy and not mounting file systems properly. You
could
>check this with a little test:
>
>mkdir /matt
>add /matt to /etc/exports, as in: /matt *()
>restart NFS: service nfs restart
>mount localhost:/matt /mnt
>
>
>If the mount works, than NFS is probably working ok and we can ignore it
>for now. If the mount fails, then NFS is not working and that would
>explain why both the pxe and etherboot cases fail.
>
>It's early here in the States, we'll be here all day, keep posting with
>more info...
>
>regards, Rich
>
>Richard Ferri
>IBM Linux Technology Center
>[EMAIL PROTECTED]
>845.433.7920
>
>Matt Tucker <[EMAIL PROTECTED]>@lists.sourceforge.net on 12/18/2001
>09:01:20 AM
>
>Sent by: [EMAIL PROTECTED]
>
>
>To: [EMAIL PROTECTED]
>cc:
>Subject: [Oscar-users] Another network booting question sorry
>
>
>
>
>
>I'm running through the OSCAR installation for the first time everything
>seems fine until I try to boot the client.
>It finds the server via tftp, gets an ip etc, but if I use pxe it loads
the
>bzImage produces lots of output that looks okay (I think) but then just
>sits there. So I tried using a boot floppy created using etherboot with
>the eepro100 driver, this seem to work fine but while booting vmlinuz this
>time it fails to set up the network device, so fails and asks for a boot
>floppy. Please can someone help.
>
>Thanks,
>Matt
>
>
>
>------------------------------------------------------------------------
>Matt Tucker
>Department of Earth Sciences
>Downing Street,
>Cambridge,
>CB2 3EQ
>Tel:01223 333408
>Fax: +44 1223 333450
>------------------------------------------------------------------------
>
>
>_______________________________________________
>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
