Re: [casper] Matlab 2013a and ISE 14.4/5

[Ryan Monroe]

Try just system generator before worrying about Casper libraries.  I'm out
of town right now but I'll help you or in a week ;-)
On Jun 6, 2013 8:06 PM, "Ross Williamson" 
wrote:

> Tried that - no luck. I think it might be some kind of mismatch in
> stdlibc++ between matlab, ISE and the native ubuntu damn it - time
> to start hacking libraries again.
>
>
>
> On Thu, Jun 6, 2013 at 2:35 PM, Ryan Monroe 
> wrote:
> > Try calling the ise system64.sh and then run the command "sysgen".  This
> is
> > the official way to call system generator.  You should not be calling
> matlab
> > directly to use system generator
> >
> > On Jun 6, 2013 4:44 PM, "Ross Williamson"  >
> > wrote:
> >>
> >> Anybody managed to get Matla 2013a and ISE 14.5 working?
> >>
> >> When I run  xlAddSysgen([getenv('XILINX_PATH'), '/ISE']) matlab
> >> segfaults. I can post the gory details but the summary is below.
> >>
> >>
> >> 
> >>Segmentation violation detected at Thu Jun  6 13:40:17 2013
> >> 
> >>
> >> Configuration:
> >>   Crash Decoding : Disabled
> >>   Current Visual : 0x21 (class 4, depth 24)
> >>   Default Encoding   : UTF-8
> >>   GNU C Library  : 2.17 stable
> >>   MATLAB Architecture: glnxa64
> >>   MATLAB Root: /opt/MATLAB/R2013a
> >>   MATLAB Version : 8.1.0.604 (R2013a)
> >>   Operating System   : Linux 3.8.0-23-generic #34-Ubuntu SMP Wed May
> >> 29 20:22:58 UTC 2013 x86_64
> >>   Processor ID   : x86 Family 6 Model 58 Stepping 9, GenuineIntel
> >>   Virtual Machine: Java 1.6.0_17-b04 with Sun Microsystems Inc.
> >> Java HotSpot(TM) 64-Bit Server VM mixed mode
> >>   Window System  : The X.Org Foundation (11303000), display :0.0
> >>
> >> Fault Count: 1
> >>
> >> ...
> >>
> >> This error was detected while a MEX-file was running. If the MEX-file
> >> is not an official MathWorks function, please examine its source code
> >> for errors. Please consult the External Interfaces Guide for information
> >> on debugging MEX-files.
> >>
> >>
> >>
> >> --
> >> Ross Williamson
> >> Research Scientist - Sub-mm Group
> >> California Institute of Technology
> >> 626-395-2647 (office)
> >> 312-504-3051 (Cell)
> >>
> >
>
>
>
> --
> Ross Williamson
> Research Scientist - Sub-mm Group
> California Institute of Technology
> 626-395-2647 (office)
> 312-504-3051 (Cell)
>

Re: [casper] Matlab 2013a and ISE 14.4/5

[Ross Williamson]

Tried that - no luck. I think it might be some kind of mismatch in
stdlibc++ between matlab, ISE and the native ubuntu damn it - time
to start hacking libraries again.



On Thu, Jun 6, 2013 at 2:35 PM, Ryan Monroe  wrote:
> Try calling the ise system64.sh and then run the command "sysgen".  This is
> the official way to call system generator.  You should not be calling matlab
> directly to use system generator
>
> On Jun 6, 2013 4:44 PM, "Ross Williamson" 
> wrote:
>>
>> Anybody managed to get Matla 2013a and ISE 14.5 working?
>>
>> When I run  xlAddSysgen([getenv('XILINX_PATH'), '/ISE']) matlab
>> segfaults. I can post the gory details but the summary is below.
>>
>>
>> 
>>Segmentation violation detected at Thu Jun  6 13:40:17 2013
>> 
>>
>> Configuration:
>>   Crash Decoding : Disabled
>>   Current Visual : 0x21 (class 4, depth 24)
>>   Default Encoding   : UTF-8
>>   GNU C Library  : 2.17 stable
>>   MATLAB Architecture: glnxa64
>>   MATLAB Root: /opt/MATLAB/R2013a
>>   MATLAB Version : 8.1.0.604 (R2013a)
>>   Operating System   : Linux 3.8.0-23-generic #34-Ubuntu SMP Wed May
>> 29 20:22:58 UTC 2013 x86_64
>>   Processor ID   : x86 Family 6 Model 58 Stepping 9, GenuineIntel
>>   Virtual Machine: Java 1.6.0_17-b04 with Sun Microsystems Inc.
>> Java HotSpot(TM) 64-Bit Server VM mixed mode
>>   Window System  : The X.Org Foundation (11303000), display :0.0
>>
>> Fault Count: 1
>>
>> ...
>>
>> This error was detected while a MEX-file was running. If the MEX-file
>> is not an official MathWorks function, please examine its source code
>> for errors. Please consult the External Interfaces Guide for information
>> on debugging MEX-files.
>>
>>
>>
>> --
>> Ross Williamson
>> Research Scientist - Sub-mm Group
>> California Institute of Technology
>> 626-395-2647 (office)
>> 312-504-3051 (Cell)
>>
>



-- 
Ross Williamson
Research Scientist - Sub-mm Group
California Institute of Technology
626-395-2647 (office)
312-504-3051 (Cell)

[casper] ADCx64-12 on a roach1

[David Saroff]

Who has the ADCx64-12 on a roach1? Could I see your .mdl please?

Re: [casper] Matlab 2013a and ISE 14.4/5

[Ryan Monroe]

Try calling the ise system64.sh and then run the command "sysgen".  This is
the official way to call system generator.  You should not be calling
matlab directly to use system generator
On Jun 6, 2013 4:44 PM, "Ross Williamson" 
wrote:

> Anybody managed to get Matla 2013a and ISE 14.5 working?
>
> When I run  xlAddSysgen([getenv('XILINX_PATH'), '/ISE']) matlab
> segfaults. I can post the gory details but the summary is below.
>
>
> 
>Segmentation violation detected at Thu Jun  6 13:40:17 2013
> 
>
> Configuration:
>   Crash Decoding : Disabled
>   Current Visual : 0x21 (class 4, depth 24)
>   Default Encoding   : UTF-8
>   GNU C Library  : 2.17 stable
>   MATLAB Architecture: glnxa64
>   MATLAB Root: /opt/MATLAB/R2013a
>   MATLAB Version : 8.1.0.604 (R2013a)
>   Operating System   : Linux 3.8.0-23-generic #34-Ubuntu SMP Wed May
> 29 20:22:58 UTC 2013 x86_64
>   Processor ID   : x86 Family 6 Model 58 Stepping 9, GenuineIntel
>   Virtual Machine: Java 1.6.0_17-b04 with Sun Microsystems Inc.
> Java HotSpot(TM) 64-Bit Server VM mixed mode
>   Window System  : The X.Org Foundation (11303000), display :0.0
>
> Fault Count: 1
>
> ...
>
> This error was detected while a MEX-file was running. If the MEX-file
> is not an official MathWorks function, please examine its source code
> for errors. Please consult the External Interfaces Guide for information
> on debugging MEX-files.
>
>
>
> --
> Ross Williamson
> Research Scientist - Sub-mm Group
> California Institute of Technology
> 626-395-2647 (office)
> 312-504-3051 (Cell)
>
>

[casper] Matlab 2013a and ISE 14.4/5

[Ross Williamson]

Anybody managed to get Matla 2013a and ISE 14.5 working?

When I run  xlAddSysgen([getenv('XILINX_PATH'), '/ISE']) matlab
segfaults. I can post the gory details but the summary is below.



   Segmentation violation detected at Thu Jun  6 13:40:17 2013


Configuration:
  Crash Decoding : Disabled
  Current Visual : 0x21 (class 4, depth 24)
  Default Encoding   : UTF-8
  GNU C Library  : 2.17 stable
  MATLAB Architecture: glnxa64
  MATLAB Root: /opt/MATLAB/R2013a
  MATLAB Version : 8.1.0.604 (R2013a)
  Operating System   : Linux 3.8.0-23-generic #34-Ubuntu SMP Wed May
29 20:22:58 UTC 2013 x86_64
  Processor ID   : x86 Family 6 Model 58 Stepping 9, GenuineIntel
  Virtual Machine: Java 1.6.0_17-b04 with Sun Microsystems Inc.
Java HotSpot(TM) 64-Bit Server VM mixed mode
  Window System  : The X.Org Foundation (11303000), display :0.0

Fault Count: 1

...

This error was detected while a MEX-file was running. If the MEX-file
is not an official MathWorks function, please examine its source code
for errors. Please consult the External Interfaces Guide for information
on debugging MEX-files.



--
Ross Williamson
Research Scientist - Sub-mm Group
California Institute of Technology
626-395-2647 (office)
312-504-3051 (Cell)

Re: [casper] netbooting ROACH2

[David MacMahon]

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!

Re: [casper] ROACH2 change password

[Rich Lacasse]

It works!

Thanks

On 6/6/2013 2:37 PM, Primiani, Rurik wrote:

Hi Rich,

I believe you're running Busybox (i.e. through soloboot), try the 
following:


$ busybox passwd

To change the root password.

Best,
Rurik

On Thu, Jun 6, 2013 at 2:06 PM, Rich Lacasse > wrote:


Hi All,

It's been requested that I change the password on our ROACH2's to
something a little more complex than carriage return.  I tried
passwd and chpasswd and password; none are recognized.  Is there a
way to change the password?

Thanks,
Rich

[casper] ROACH2 change password

[Rich Lacasse]

Hi All,

It's been requested that I change the password on our ROACH2's to 
something a little more complex than carriage return.  I tried passwd 
and chpasswd and password; none are recognized.  Is there a way to 
change the password?


Thanks,
Rich

Re: [casper] netbooting ROACH2

[John Ford]

> 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 directory with a separate entry in rc.local that is
found in /etc.  There might be a more elegant way...

Yes, Master<1009> more rc.local

#!/bin/sh -e
#
# rc.local
#
# This script is executed at the end of each multiuser runlevel.
# Make sure that the script will "exit 0" on success or any other
# value on error.
#
# In order to enable or disable this script just change the execution
# bits.
#
# By default this script does nothing.
mount -o nolock -t nfs 10.16.96.203:/export/home/tofu/cicadaroots/vegasbof
/boffiles

exit 0
Yes, Master<1010>

John

 >
> Thanks,
> Dale
>
>
>
>
> On Thu, Jun 6, 2013 at 5:02 PM, Gary, Dale E. 
> 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
>> 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:
>>> > 1f004096 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
>>>
>>>
>>
>

Re: [casper] netbooting ROACH2

[Gary, Dale E.]

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 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,
>>
>> 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:
>> > 1f004096 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
>>
>>
>

Re: [casper] netbooting ROACH2

[Gary, Dale E.]

> 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,
>
> 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:
> > 1f004096 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
>
>

Re: [casper] netbooting ROACH2

[David MacMahon]

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:
> 1f004096 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

Re: [casper] netbooting ROACH2

[Gary, Dale E.]

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 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:
1f004096 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...

Regards,
Dale


On Thu, Jun 6, 2013 at 3:50 PM, David MacMahon wrote:

> 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/etch ip=dhcp
>
> Having the rootpath end with "etch" suggests that you are using a root
> file system based on Debian "Etch", which used for ROACH1.  The ROACH2
> filesystem is now based on Debian "Squeeze".
>
> Hope this helps,
> Dave
>
>

Re: [casper] netbooting ROACH2

[David MacMahon]

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/etch ip=dhcp

Having the rootpath end with "etch" suggests that you are using a root file 
system based on Debian "Etch", which used for ROACH1.  The ROACH2 filesystem is 
now based on Debian "Squeeze".

Hope this helps,
Dave

Re: [casper] netbooting ROACH2

[Gary, Dale E.]

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, 2013 at 1:51 PM, John Ford  wrote:

> > 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, but
> > please correct me if not.
> >
>
> I should have explained more fully.   We have a custom uImage that enables
> both of the IIC ports on the ROACH2 for use by users.  That's the
> uImage-current that we use, but the other one worked fine besides the IIC
> issue.
>
> > I have the u-boot.bin (with the same checksum), but am not using it.  I
> am
> > confused about what steps I need to take, and thought I could just follow
> > the same procedure for ROACH-1, but do I first have to update the u-boot
> > as
> > in these instructions?
> >
> > http://www.mail-archive.com/casper@lists.berkeley.edu/msg03351.html
>
> I think you do need the newest uboot, but I'm not positive.  But I think
> that one main thing is that you don't have the right kernel somehow being
> loaded.  I think that your server is serving the wrong one, since what was
> in the mail showed an older kernel being started up:
>
> > Linux version 2.6.25-svn3489 (dave@lapster) (gcc version 4.2.2) #6 Fri
> > Aug
> > > 12 09:36:28 SAST 2011
>
> Which is (nearly) the same as our roach1 kernel image:
>
> Yes, Master<1009> strings uImage-roach1 | more
> Linux-2.6.25-svn2338
> ...
>
> Whereas our roach2 kernel looks like this:
>
> Yes, Master<1007> strings uImage-r2borph3 | more
> Linux-3.7.0-rc2+
> ...
>
> >
> > I actually tried it, but our network seems to be down at the moment.
>  What
> > about romfs?  Is this only needed for soloboot?
>
> I think that's right.  The file system should be on the NFS server.
> Here's what our mounts look like:
>
> root@vegasr2-2:~# mount
> rootfs on / type rootfs (rw)
> 10.16.96.203:/export/home/tofu/cicadaroots/vegasr2/ on / type nfs
>
> (ro,noatime,vers=2,rsize=4096,wsize=4096,namlen=255,hard,nolock,proto=udp,timeo=11,retrans=3,sec=sys,mountaddr=10.16.96.203,mountvers=1,mountproto=udp,local_lock=all,addr=10.16.96.203)
> proc on /proc type proc (rw,relatime)
> sysfs on /sys type sysfs (rw,relatime)
> devpts on /dev/pts type devpts (rw,noexec,relatime,mode=620)
> tmpfs0 on /var/tmp type tmpfs (rw,relatime,size=32768k)
> tmpfs1 on /tmp type tmpfs (rw,relatime,size=16384k)
> root@vegasr2-2:~#
>
> John
>
> >
> > Thanks,
> > Dale
> >
> >
> > On Thu, Jun 6, 2013 at 4:44 AM, John Ford  wrote:
> >
> >> 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 old.
> >>
> >> Yes, Master<1017> md5sum uImage-current
> >> 300753db387044c3cb8f5f9d92c4fb37  uImage-current
> >>
> >> We also used the following:
> >> Yes, Master<1018> md5sum uImage-r2borph3
> >> ac6feb36b96c410a336fb3103fafb82c  uImage-r2borph3
> >>
> >> Our uboot is:
> >>
> >> Yes, Master<1022> md5sum u-boot.bin
> >> e396454ffa9d1e2dcbf87abf9eafccba  u-boot.bin
> >>
> >> Hope this helps!
> >>
> >> John
> >>
> >> > 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 am almost
> >> > there, but the ROACH hangs during the boot process, which suggests
> >> either
> >> > a
> >> > setup problem or the wrong Image or filesystem.  The uImage is
> >> > uImage-r2borph3, and the filesystem is
> >> > roach2-debian-fs-snapshot-24-10-2012.tar.gz.  According to the output
> >> > during the boot process (see below), I appear to have bootp and tftp
> >> set
> >> > up
> >> > correctly.  Can anyone spot the problem based on this information, or
> >> > suggest a way to get more information on what might have gone wrong?
> >> > Perhaps something to do with the USB device?
> >> >
> >> > Thanks,
> >> > Dale
> >> >
> >> > ===Output of boot process
> >> > Waiting for PHY auto negotiation to complete done
> >> > ENET Speed is 1000 Mbps - FULL duplex connection (EMAC0)
> >> > BOOTP broadcast 1
> >> > DHCP client bound to address 192.168.24.121
> >> > Using ppc_4xx_eth0 device
> >> > TFTP from server 192.10

Re: [casper] netbooting ROACH2

[G Jones]

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 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, but
>> please correct me if not.
>>
>
> I should have explained more fully.   We have a custom uImage that enables
> both of the IIC ports on the ROACH2 for use by users.  That's the
> uImage-current that we use, but the other one worked fine besides the IIC
> issue.
>
>> I have the u-boot.bin (with the same checksum), but am not using it.  I am
>> confused about what steps I need to take, and thought I could just follow
>> the same procedure for ROACH-1, but do I first have to update the u-boot
>> as
>> in these instructions?
>>
>> http://www.mail-archive.com/casper@lists.berkeley.edu/msg03351.html
>
> I think you do need the newest uboot, but I'm not positive.  But I think
> that one main thing is that you don't have the right kernel somehow being
> loaded.  I think that your server is serving the wrong one, since what was
> in the mail showed an older kernel being started up:
>
>> Linux version 2.6.25-svn3489 (dave@lapster) (gcc version 4.2.2) #6 Fri
>> Aug
>> > 12 09:36:28 SAST 2011
>
> Which is (nearly) the same as our roach1 kernel image:
>
> Yes, Master<1009> strings uImage-roach1 | more
> Linux-2.6.25-svn2338
> ...
>
> Whereas our roach2 kernel looks like this:
>
> Yes, Master<1007> strings uImage-r2borph3 | more
> Linux-3.7.0-rc2+
> ...
>
>>
>> I actually tried it, but our network seems to be down at the moment.  What
>> about romfs?  Is this only needed for soloboot?
>
> I think that's right.  The file system should be on the NFS server.
> Here's what our mounts look like:
>
> root@vegasr2-2:~# mount
> rootfs on / type rootfs (rw)
> 10.16.96.203:/export/home/tofu/cicadaroots/vegasr2/ on / type nfs
> (ro,noatime,vers=2,rsize=4096,wsize=4096,namlen=255,hard,nolock,proto=udp,timeo=11,retrans=3,sec=sys,mountaddr=10.16.96.203,mountvers=1,mountproto=udp,local_lock=all,addr=10.16.96.203)
> proc on /proc type proc (rw,relatime)
> sysfs on /sys type sysfs (rw,relatime)
> devpts on /dev/pts type devpts (rw,noexec,relatime,mode=620)
> tmpfs0 on /var/tmp type tmpfs (rw,relatime,size=32768k)
> tmpfs1 on /tmp type tmpfs (rw,relatime,size=16384k)
> root@vegasr2-2:~#
>
> John
>
>>
>> Thanks,
>> Dale
>>
>>
>> On Thu, Jun 6, 2013 at 4:44 AM, John Ford  wrote:
>>
>>> 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 old.
>>>
>>> Yes, Master<1017> md5sum uImage-current
>>> 300753db387044c3cb8f5f9d92c4fb37  uImage-current
>>>
>>> We also used the following:
>>> Yes, Master<1018> md5sum uImage-r2borph3
>>> ac6feb36b96c410a336fb3103fafb82c  uImage-r2borph3
>>>
>>> Our uboot is:
>>>
>>> Yes, Master<1022> md5sum u-boot.bin
>>> e396454ffa9d1e2dcbf87abf9eafccba  u-boot.bin
>>>
>>> Hope this helps!
>>>
>>> John
>>>
>>> > 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 am almost
>>> > there, but the ROACH hangs during the boot process, which suggests
>>> either
>>> > a
>>> > setup problem or the wrong Image or filesystem.  The uImage is
>>> > uImage-r2borph3, and the filesystem is
>>> > roach2-debian-fs-snapshot-24-10-2012.tar.gz.  According to the output
>>> > during the boot process (see below), I appear to have bootp and tftp
>>> set
>>> > up
>>> > correctly.  Can anyone spot the problem based on this information, or
>>> > suggest a way to get more information on what might have gone wrong?
>>> > Perhaps something to do with the USB device?
>>> >
>>> > Thanks,
>>> > Dale
>>> >
>>> > ===Output of boot process
>>> > Waiting for PHY auto negotiation to complete done
>>> > ENET Speed is 1000 Mbps - FULL duplex connection (EMAC0)
>>> > BOOTP broadcast 1
>>> > DHCP client bound to address 192.168.24.121
>>> > Using ppc_4xx_eth0 device
>>> > TFTP from server 192.100.16.206; our IP address is 192.168.24.121;
>>> sending
>>> > through gateway 192.168.24.1
>>> > Filename 'uImage'.
>>> > Load address: 0x400
>>> > Loading:
>>> #

Re: [casper] netbooting ROACH2

[John Ford]

> 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, but
> please correct me if not.
>

I should have explained more fully.   We have a custom uImage that enables
both of the IIC ports on the ROACH2 for use by users.  That's the
uImage-current that we use, but the other one worked fine besides the IIC
issue.

> I have the u-boot.bin (with the same checksum), but am not using it.  I am
> confused about what steps I need to take, and thought I could just follow
> the same procedure for ROACH-1, but do I first have to update the u-boot
> as
> in these instructions?
>
> http://www.mail-archive.com/casper@lists.berkeley.edu/msg03351.html

I think you do need the newest uboot, but I'm not positive.  But I think
that one main thing is that you don't have the right kernel somehow being
loaded.  I think that your server is serving the wrong one, since what was
in the mail showed an older kernel being started up:

> Linux version 2.6.25-svn3489 (dave@lapster) (gcc version 4.2.2) #6 Fri
> Aug
> > 12 09:36:28 SAST 2011

Which is (nearly) the same as our roach1 kernel image:

Yes, Master<1009> strings uImage-roach1 | more
Linux-2.6.25-svn2338
...

Whereas our roach2 kernel looks like this:

Yes, Master<1007> strings uImage-r2borph3 | more
Linux-3.7.0-rc2+
...

>
> I actually tried it, but our network seems to be down at the moment.  What
> about romfs?  Is this only needed for soloboot?

I think that's right.  The file system should be on the NFS server. 
Here's what our mounts look like:

root@vegasr2-2:~# mount
rootfs on / type rootfs (rw)
10.16.96.203:/export/home/tofu/cicadaroots/vegasr2/ on / type nfs
(ro,noatime,vers=2,rsize=4096,wsize=4096,namlen=255,hard,nolock,proto=udp,timeo=11,retrans=3,sec=sys,mountaddr=10.16.96.203,mountvers=1,mountproto=udp,local_lock=all,addr=10.16.96.203)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
devpts on /dev/pts type devpts (rw,noexec,relatime,mode=620)
tmpfs0 on /var/tmp type tmpfs (rw,relatime,size=32768k)
tmpfs1 on /tmp type tmpfs (rw,relatime,size=16384k)
root@vegasr2-2:~#

John

>
> Thanks,
> Dale
>
>
> On Thu, Jun 6, 2013 at 4:44 AM, John Ford  wrote:
>
>> 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 old.
>>
>> Yes, Master<1017> md5sum uImage-current
>> 300753db387044c3cb8f5f9d92c4fb37  uImage-current
>>
>> We also used the following:
>> Yes, Master<1018> md5sum uImage-r2borph3
>> ac6feb36b96c410a336fb3103fafb82c  uImage-r2borph3
>>
>> Our uboot is:
>>
>> Yes, Master<1022> md5sum u-boot.bin
>> e396454ffa9d1e2dcbf87abf9eafccba  u-boot.bin
>>
>> Hope this helps!
>>
>> John
>>
>> > 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 am almost
>> > there, but the ROACH hangs during the boot process, which suggests
>> either
>> > a
>> > setup problem or the wrong Image or filesystem.  The uImage is
>> > uImage-r2borph3, and the filesystem is
>> > roach2-debian-fs-snapshot-24-10-2012.tar.gz.  According to the output
>> > during the boot process (see below), I appear to have bootp and tftp
>> set
>> > up
>> > correctly.  Can anyone spot the problem based on this information, or
>> > suggest a way to get more information on what might have gone wrong?
>> > Perhaps something to do with the USB device?
>> >
>> > Thanks,
>> > Dale
>> >
>> > ===Output of boot process
>> > Waiting for PHY auto negotiation to complete done
>> > ENET Speed is 1000 Mbps - FULL duplex connection (EMAC0)
>> > BOOTP broadcast 1
>> > DHCP client bound to address 192.168.24.121
>> > Using ppc_4xx_eth0 device
>> > TFTP from server 192.100.16.206; our IP address is 192.168.24.121;
>> sending
>> > through gateway 192.168.24.1
>> > Filename 'uImage'.
>> > Load address: 0x400
>> > Loading:
>> #
>> >
>>  #
>> >
>>  #
>> >
>>  #
>> >  
>> > done
>> > Bytes transferred = 1390149 (153645 hex)
>> > ## Booting kernel from Legacy Image at 0400 ...
>> >Imag

Re: [casper] netbooting ROACH2

[Gary, Dale E.]

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, but
please correct me if not.

I have the u-boot.bin (with the same checksum), but am not using it.  I am
confused about what steps I need to take, and thought I could just follow
the same procedure for ROACH-1, but do I first have to update the u-boot as
in these instructions?

http://www.mail-archive.com/casper@lists.berkeley.edu/msg03351.html

I actually tried it, but our network seems to be down at the moment.  What
about romfs?  Is this only needed for soloboot?

Thanks,
Dale


On Thu, Jun 6, 2013 at 4:44 AM, John Ford  wrote:

> 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 old.
>
> Yes, Master<1017> md5sum uImage-current
> 300753db387044c3cb8f5f9d92c4fb37  uImage-current
>
> We also used the following:
> Yes, Master<1018> md5sum uImage-r2borph3
> ac6feb36b96c410a336fb3103fafb82c  uImage-r2borph3
>
> Our uboot is:
>
> Yes, Master<1022> md5sum u-boot.bin
> e396454ffa9d1e2dcbf87abf9eafccba  u-boot.bin
>
> Hope this helps!
>
> John
>
> > 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 am almost
> > there, but the ROACH hangs during the boot process, which suggests either
> > a
> > setup problem or the wrong Image or filesystem.  The uImage is
> > uImage-r2borph3, and the filesystem is
> > roach2-debian-fs-snapshot-24-10-2012.tar.gz.  According to the output
> > during the boot process (see below), I appear to have bootp and tftp set
> > up
> > correctly.  Can anyone spot the problem based on this information, or
> > suggest a way to get more information on what might have gone wrong?
> > Perhaps something to do with the USB device?
> >
> > Thanks,
> > Dale
> >
> > ===Output of boot process
> > Waiting for PHY auto negotiation to complete done
> > ENET Speed is 1000 Mbps - FULL duplex connection (EMAC0)
> > BOOTP broadcast 1
> > DHCP client bound to address 192.168.24.121
> > Using ppc_4xx_eth0 device
> > TFTP from server 192.100.16.206; our IP address is 192.168.24.121;
> sending
> > through gateway 192.168.24.1
> > Filename 'uImage'.
> > Load address: 0x400
> > Loading:
> #
> >
>  #
> >
>  #
> >
>  #
> >  
> > done
> > Bytes transferred = 1390149 (153645 hex)
> > ## Booting kernel from Legacy Image at 0400 ...
> >Image Name:   Linux-2.6.25-svn3489
> >Image Type:   PowerPC Linux Kernel Image (gzip compressed)
> >Data Size:1390085 Bytes = 1.3 MiB
> >Load Address: 
> >Entry Point:  
> >Verifying Checksum ... OK
> >Uncompressing Kernel Image ... OK
> > id mach(): done
> > MMU:enter
> > MMU:hw init
> > MMU:mapin
> > MMU:setio
> > MMU:exit
> > setup_arch: enter
> > setup_arch: bootmem
> > ocp: exit
> > arch: exit
> > Linux version 2.6.25-svn3489 (dave@lapster) (gcc version 4.2.2) #6 Fri
> Aug
> > 12 09:36:28 SAST 2011
> > AMCC PowerPC 440EPx Roach Platform
> > Zone PFN ranges:
> >   DMA 0 ->   131071
> >   Normal 131071 ->   131071
> > Movable zone start PFN for each node
> > early_node_map[1] active PFN ranges
> > 0:0 ->   131071
> > Built 1 zonelists in Zone order, mobility grouping on.  Total pages:
> > 130048
> > Kernel command line: console=ttyS0,115200 root=/dev/nfs
> > rootpath=192.100.16.206:/srv/roach2_boot/etch ip=dhcp
> > PID hash table entries: 2048 (order: 11, 8192 bytes)
> > console [ttyS0] enabled
> > Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
> > Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
> > Memory: 516608k available (2084k kernel code, 720k data, 132k init, 0k
> > highmem)
> > Mount-cache hash table entries: 512
> > BORPH version CVS-$Revision: 1.10 $ Initialized
> > net_namespace: 152 bytes
> > NET: Registered protocol family 16
> >
> > PCI: Probing PCI hardware
> > SCSI subsystem initialized
> > usbcore: registered new interface driver usbfs
> > usbcore: registered new interface driver hub
> > usbcore: registered new device d