Hi there,
I've posted something similar in the past but I am still stuck with this problem:
can't get a diskless
ebsa-285 (footbridge) to NFS boot with latest kernels. I would appreciate if someone
told me that they've
managed to accomplish that, so at least I know it is possible at all.
I've compiled 2.4.0-test5(rmk1, np1), 2.4.0(rmk3) and 2.4.1(rmk1), all with the same
results: the ebsa-285
(as host + network card) get's its IP address from the bootp server fine, and then
fails with:
Looking up port of RPC 100003/2 on <server IP address>
portmap: server not responding, timed out
and everything goes downhill from there (can't mount root-nfs etc ...). I've widely
researched the problem
in standard (not ARM) linux sources, and all the server-side possible solutions make
no difference at all.
I deeply believe the problem is in the diskless ARM workstation.
Interesting facts:
* the set-up worked flawlessly in the past when I compiled 2.2.13 into the diskless
workstation, with the
same server. I need features from 2.4.0, that's why I am upgrading.
* My bootp and NFS server throw exactly the same results whether running 2.2.12, 2.4.0
or 2.4.1. I've also
upgraded to latest nfs-utils and bootp, with same results - it is called desperation
:-)
* Another standard desktop R.H. linux machine, running the (arm unpatched) original
source kernels and with
the same (or the closest) compilation options in the kernel as the diskless machine
can mount the NFS directory
no problem (not as root-fs, but as a simple remote directory, so that might not be a
useful fact, but there you go)
* I get no kernel compilation errors or warnings. Using a precompiled xdev tool-chain
(bin-utils 2.10-1,
gcc-2.95.2-2, glibc-2.1.3-2).
* monitoring with tcpdump the traffic with the server on boot-up, I see an arp request
for an IP address,
served by bootpd, and acknowledged by the ebsa-285 in the booting-up screen. Also,
after the ebsa requests
its IP address, and entry in the host's ARP cache /proc/net/arp reads:
IP address HW type Flags HW address Mask Device
192.168.0.93 0x1 0x0 00:B0:86:00:0E:29 * eth0
<ebsa-285>
which seems ok. And then messages from server asking for the ebsa to respond:
18:49:58.635180 eth0 > arp who-has ebsa285.h2eye.com tell fishlaptop.h2eye.com
(0:60:8:24:76:dd)
repeated a number of times, but never answered.
Any ideas would be greatly appreciated, at least to know that someone has managed to
get somthing along this lines
successfully working would be very encouraging.
Regards,
Jaime
_______________________________________________
http://lists.arm.linux.org.uk/mailman/listinfo/linux-arm
Please visit the above address for information on this list.
