Hi Jason: I find another thing interesting. If I modify the /etc/network/interfaces file at other PC, and then replace the file with the modified file, the problem does not appear.
Any idea? Thanks Wan -----Original Message----- From: Jason Manley [mailto:[email protected]] Sent: Friday, 22 May 2009 4:12 PM To: Cheng, Wan (ATNF, Marsfield) Cc: [email protected] Subject: Re: [casper] Roach issue: Stale NFS file handle error is reported If your problem is with the filesystem, then this has nothing to do with your flash (which hosts uboot, the kernel and busybox). You will need to reformat your USB stick and put a fresh copy of the "roach" file on there. This will erase all your customised settings though. I suspect you've managed to corrupt your filesystem and it's now mounting RO or something. I am concerned about your statement of the OS crashing. Why did it crash? Linux is pretty stable and doesn't usually crash easily. Is this a problem with the ROACH, or was it due to a user-action? FWIW, if you want to update your flash, see the step-by-step guide here: http://casper.berkeley.edu/wiki/ROACH_kernel_uboot_update Note that we are working on a new uBoot image as I write this email and there will be an update released later today or on monday. The primary change is to optimise the clock speeds around the PPC. Jason On 22 May 2009, at 08:01, <[email protected]> wrote: > Hi Jason: > > Thanks for your great help. But even auot eth0 is added, the network > still could not come up automatically. > > And my USB file system is FAT32 R/W. I am not sure what the file > system is for the on board flash. > > I agree with you that this should be a filesystem problem. > > I think this problem is popped up only when the OS is crashed for a > few times. But this problem could not be fixed even I update the > Uboot and the image on the Roach board. Is there anyway I can erase > all the on board flash and reprogram them again? > > Thanks > > Wan > > -----Original Message----- > From: Jason Manley [mailto:[email protected]] > Sent: Friday, 22 May 2009 3:52 PM > To: Cheng, Wan (ATNF, Marsfield) > Cc: [email protected] > Subject: Re: [casper] Roach issue: Stale NFS file handle error is > reported > > This is complaining about the statefile (ifstate) not being writeable. > This is probably a problem with your filesystem. Are you using an NFS > filesystem? is it mounted R/W, or Read-only? > > BTW, now that I've seen your interfaces file, I suspect the reason > your interface is not coming up automatically is because you've left > out the "auto eth0" line... > > auto eth0 > iface eth0 inet static > address 192.168.1.36 > netmask 255.255.255.0 > gateway 192.168.1.1 > > Jason > > On 22 May 2009, at 07:40, <[email protected]> <[email protected]> > wrote: > >> Hi: >> >> In order to set a static IP address to roach Ethernet port, I insert >> the following configuration to the /etc/network/interfaces: >> >> iface eth0 inet static >> address 130.155.199.211 >> netmask 255.255.240.0 >> gateway 130.155.192.2 >> dns-nameservers 130.155.194.32 130.155.192.40 >> >> Then I >> >> ifdown eth0 >> ifup eth0 >> >> So the Ethernet port works properly. >> >> But when I restart the Roach, I could not run ifdown and ifup >> command anymore. A failure is reported: >> ifdown: failed to open statefile /etc/network/run/ifstate: Stale NFS >> file handl >> >> Then I run ls /etc/network/run/ifstate, similar error is reported: >> >> ls: /etc/network/run/ifstate: Stale NFS file handle >> >> This is repeatable. >> >> Anybody has any idea? >> >> Thanks >> >> Wan > >
