I can't see anything wrong with your settings assuming the network IP address are correct. I would be tempted to remove the 'nolock' option from the 'nfsroot' variable & run the 'portmap' service on the NFS server. That doesn't explain the DHCP issue though. Have you tried a static IP address (using ip=........ as discussed) ? 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 www.trinityconvergence.com <http://www.trinityconvergence.com/>
________________________________ From: kaja gopi [mailto:[EMAIL PROTECTED] Sent: 03 March 2008 09:14 To: Phil Quiney; [email protected]; [EMAIL PROTECTED] Subject: RE: nfs boot problem Hi, here is the printenv output bootdelay=3 baudrate=115200 bootfile="uImage" bootcmd=nboot 0x80700000 0 0x400000;bootm rootpath=/home/confident/workdir/filesys nfshost=192.168.100.1 bootargs=console=ttyS0,115200n8 noinitrd rw ip=dhcp root=/dev/nfs nfsroot=$(nfshost):$(rootpath),nolock mem=116M stdin=serial stdout=serial stderr=serial videostd=pal Environment size: 318/16380 bytes thanks regds gopi k --- On Mon, 3/3/08, Santiago Lanzuela Benedicto <[EMAIL PROTECTED]> wrote: From: Santiago Lanzuela Benedicto <[EMAIL PROTECTED]> Subject: RE: nfs boot problem To: [EMAIL PROTECTED], [EMAIL PROTECTED], [email protected] Date: Monday, 3 March, 2008, 1:44 PM 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 www.trinityconvergence.com <http://www.trinityconvergence.com/> ________________________________ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of kaja gopi Sent: 01 March 2008 07:13 To: davinci Subject: nfs boot problem 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. <http://in.rd.yahoo.com/tagline_mail_5/*http://help.yahoo.com/l/in/yahoo/mail/yahoomail/tools/tools-08.html/> ________________________________ Explore your hobbies and interests. Click here to begin. <http://in.rd.yahoo.com/tagline_groups_6/*http://in.promos.yahoo.com/groups>
_______________________________________________ Davinci-linux-open-source mailing list [email protected] http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
