On Mon, Dec 24, 2001 at 02:16:16PM -0500, Flemming Videbaek wrote: > > During the last days run some fb3 problems were reported. > I found today that the 'boot memory' was corrupted. > The boot-mem is now reloaded, and the processor re-booted, > albeit with an error - Is this significant ? I do not know > " > Attached TCP/IP interface to dc unit 0 > Error: PROXY with sequential addr disabled. > Shared mem IP Address must be specified. > Attaching network interface lo0... done. > Mounting NFS file systems from host opus for target fb3: > /home > ...done > " This looks okey. If fb3 booted and the daq code started, then it is definitely okey. The "proxy" and "shared mem IP address" whining is probably caused by leftover junk in the boot nvram- I suspect the script used to load the boot nvram does not clear the "shared memory ip address" field. -- Konstantin Olchanski Email: olchansk@triumf.ca Snail mail: 4004 Wesbrook Mall, TRIUMF, Vancouver, B.C., V6T 2A3, Canada
This archive was generated by hypermail 2b30 : Tue Dec 25 2001 - 19:30:33 EST