Hi, Gary,
Exactly where and when is it complaining (and what's the exact message)? We do
not re-mount /boffiles as read/write (we leave it as read-only) and it works OK
for us.
Dave
P.S. Thanks for the kind words! :-)
On Jun 6, 2013, at 10:25 AM, Gary, Dale E. wrote:
> You are a genius!
> 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.
The root filesystem is probably mounted read-only. We got around this by
mounting the /boffiles direct
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. wrote:
> > Good luck! I don't have any further
> 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 wrote:
> Hi, Gary,
>
> O
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
>
Hi Dave,
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.
However, I fix
Hi, Dale and Nimish,
In addition to running an older kernel as others have pointed out, I think you
might also be using an older root file system:
On Jun 5, 2013, at 5:59 PM, Nimish Sane wrote:
> Kernel command line: console=ttyS0,115200 root=/dev/nfs
> rootpath=192.100.16.206:/srv/roach2_boot
Ah, now I see. I also have the ROACH-1 uImage on the system, and our tftp
server used to point to it. I changed the tftp server-args to point to the
new directory, but I'll bet the server did not restart and is still
pointing to the old one. I will track that down.
Thanks!
Dale
On Thu, Jun 6,
I think John has the right idea: it looks like your server is serving
a ROACH 1 uimage to your ROACH 2. We ran into this at NRAO once before
as well, but perhaps the other way around.
On Thu, Jun 6, 2013 at 9:51 AM, John Ford wrote:
>> Hi John,
>>
>> Thanks for the reply. My uImage checksum for
> Hi John,
>
> Thanks for the reply. My uImage checksum for uImage-r2borph3 agrees with
> yours. I do not have any uImage-current, and do not understand why there
> would be two uImages. I will assume you are running two different ROACH2
> versions and that I should be using only the uImage-r2bo
Hi John,
Thanks for the reply. My uImage checksum for uImage-r2borph3 agrees with
yours. I do not have any uImage-current, and do not understand why there
would be two uImages. I will assume you are running two different ROACH2
versions and that I should be using only the uImage-r2borph3 one, b
In our R2 systems, we have the following kernel:
root@vegasr2-2:~# uname -a
Linux vegasr2-2 3.7.0-rc2+ #20 Fri Jan 4 18:04:26 SAST 2013 ppc GNU/Linux
I'm pretty sure the Roach-2 kernels are all 3.x.
Can you get a checksum (md5sum) of the uimage? I think you have the right
one, but it may be too
Posting on behalf of Dale. Please see the message below.
Thanks,
Nimish
-- Forwarded message --
From: "Gary, Dale E."
To: casper list
Cc:
Date: Thu, 6 Jun 2013 00:40:25 +
Subject: netbooting ROACH2
Hi Casperites,
I am setting up a ROACH2 rev2 for netbooting, and I think I
13 matches
Mail list logo
