Sorry for all of the questions, but now when I try to program the FPGA with katcp is complains about a read-only file system. /etc/exports declares it rw, so I seem to be stuck again.
Thanks, Dale On Thu, Jun 6, 2013 at 5:02 PM, Gary, Dale E. <dale.e.g...@njit.edu> wrote: > > Good luck! I don't have any further ideas other than verifying that the > root file system is mountable by > > computers on the ROACH2 subnet. > > You are a genius! I hadn't updated exportfs... It is now booted! > > > Thanks, > Dale > > > On Thu, Jun 6, 2013 at 4:39 PM, David MacMahon > <dav...@astro.berkeley.edu>wrote: > >> Hi, Gary, >> >> On Jun 6, 2013, at 9:20 AM, Gary, Dale E. wrote: >> >> > Hmm, I was just trying to follow the instructions in the roach nfs >> guide, which says to create a directory named etch to put the root file >> system. I probably renamed the directory to etch. Will that matter? It >> is the correct file system--just a different directory name. >> >> It won't matter for the computer (a rose by any other name...), but it >> might confuse humans! :-) >> >> > However, I fixed the problem with loading the wrong uImage, and it now >> boots to the point where I get this output: >> > >> > Sending DHCP requests ., OK >> > IP-Config: Got DHCP answer from 192.100.16.206, my address is >> 192.168.24.121 >> > IP-Config: Complete: >> > device=eth0, addr=192.168.24.121, mask=255.255.255.0, >> gw=192.168.24.1 >> > host=roach1.solar.pvt, domain=solar.pvt solar.ovro.caltech.edu, >> nis-domain=(none) >> > bootserver=192.100.16.206, rootserver=192.100.16.206, >> rootpath=/srv/roach2_boot/etch >> > nameserver0=192.100.16.2, nameserver1=192.168.9.15 >> > VFS: Unable to mount root fs via NFS, trying floppy. >> > VFS: Cannot open root device "nfs" or unknown-block(2,0): error -6 >> > Please append a correct "root=" boot option; here are the available >> partitions: >> > 1f00 4096 mtdblock0 (driver?) >> > 1f01 65536 mtdblock1 (driver?) >> > 1f02 49152 mtdblock2 (driver?) >> > 1f03 11264 mtdblock3 (driver?) >> > 1f04 256 mtdblock4 (driver?) >> > 1f05 512 mtdblock5 (driver?) >> > Kernel panic - not syncing: VFS: Unable to mount root fs on >> unknown-block(2,0) >> > Rebooting in 180 seconds.. >> > >> > So indeed the file system may not be right. Still working on it... >> >> Good luck! I don't have any further ideas other than verifying that the >> root file system is mountable by computers on the ROACH2 subnet. >> >> Dave >> >> >
