Hi
I had the same problem.
Set environment varables in the console like is indicated in step 4.3.5 from getting started guide.
Be careful with Nfshost and rootpath
Regards
De: "Phil Quiney" <[EMAIL PROTECTED]>
Enviado: lunes, 03 de marzo de 2008 9:09
Para: [EMAIL PROTECTED]>, "davinci" <[email protected]
Asunto: RE: nfs boot problem
Hi,
Can you post the output of 'printenv' on your DM355?
Also the console output would be useful as would an ethereal packet capture of the DHCP transaction.
If the nfsroot value is valid then it is likely that the problem is with in the DHCP area. This failure could be a mis-configuration of the DHCP server, the packet capture would help diagnose this. You could try bypassing DHCP by setting the ip= value to set static addresses for ip address, gateway etc.
ip=<client-ip>:<server-ip>:<gw-ip>:<netmask>:<hostname>:<device>:<autoconf>
Example:
ip=172.18.1.222:172.18.1.49:172.18.0.254:255.255.0.0:::off
Obviously you will need to change the network values to suit your network & how you come up with an address to use is your problem ;-)
Regards
Phil Q
Phil Quiney, Senior Software Engineer
Trinity Convergence
Cambridge Business Park
Cowley Road
Cambridge CB4 0WZ, UK
T: +44(0)1223-435536
F: +44(0)1223-435560
|
Hi,
My DM355 EVM board was unable to boot through nfs mount.
It was struck in getting dhcp ip.
"DHCP/BOOTP reply not for us" message is coming repeatedly..
sometimes its also giving error like
VFS : cannot open root device "nfs"
Please append a correct "root=" boot option.
kerne panic.
Any one has got any idea with the error or am i doing any mistake?
thanks
regds
gopi k |
Get the freedom to save as many mails as you wish.
Click here to know how.