CLONWiki - User contributions [en]

Clasxt

2009-01-21T19:48:53Z

129.57.81.176:

'''Clonxt''' machines are diskless 'thin clients' from neoware, running newlinux.

To reboot in single user mode do following:

* Power on the EON and hold the left shift key down until you are shown a boot prompt
* The boot prompt should display 'Software'
* Enter ''Software -s ramdisk=12000'' and press enter
* As the OS boots, press alt-F2 (possibly more than once) until you are greeted with a bash prompt

Some useful information can be found in following paper:

Some reports indicate that 3.x builds do not work. The error that is reported is
FATAL ERROR
The device that contains the configuration file (config.xml) could not be found. m0n0wall cannot continue booting.
I do not yet know of a solution. This tutorial should be construed to apply only to the 2.x builds in the meantime. Please email me if you get 3.x working on an EON.

Here's how to install the latest build of the excellent m0n0wall firewall on a Neoware EON 4000 thin client. These machines make excellent firewalls for home users and small businesses because they are cheap, compact, sturdy, and powerful enough to run a several megabit connection. The hardware is available in a variety of configurations, with CPUs roughly equivalent to a 150-200Mhz Pentium. Before embarking on this little journey, you should be aware of a few caveats:

* Some Neoware boxes come with a 32-pin Disk-on-Chip module in a socket on the motherboard. m0n0wall does not ship with the required driver to run this module. Therefore, on these systems you will need a hard drive, compact flash to IDE adapter, or similar device to boot from. You may also be able to netboot your firewall (this is supported on the built-in network device), though I do not cover that in this tutorial.
* The motherboard accepts both PC133 DIMMs or SO-DIMMs. It will use both at the same time. However, when using a DIMM, be sure it is less than 1.1" (28mm) tall, or you will not be able to install a second network card.
* There are many different revisions of the NeoLinux operating system and not all include the necessary software to complete this tutorial.
* You may need to purchase several EON 4000s to get suitable software and hardware.
* These instructions were based on NeoLinux 2.4-100802, with kernel 2.2.20. Your particular configuration may vary slightly.

With those potential issues in mind, follow along!

There are three main steps to be completed to get m0n0wall running on your EON. First, you will need to get single-user access to the NeoLinux installation. Next, you need to enable networking and fetch and install m0n0wall. Third, you need to configure it to fit your requirements. I will address the first two of these, as adequate resources exist to help with the latter.

To begin, you will need:

* One or more Neoware EONs with disk-on-chip modules that plug into the IDE header
* Access to the internet from your EON (or to a web server on a LAN)
* A supported PCI network card. Common Intel or 3Com cards work fine.
* At least 64MB of suitable memory. Some EONs ship with SO-DIMMs, others with DIMMs. These should be short enough to accomodate a PCI network card.
* See the m0n0wall supported hardware page for more information.

Step ONE: Get single-user access to the NeoLinux distribution.

* Power on the EON and hold the left shift key down until you are shown a boot prompt
* The boot prompt may vary, but pressing tab should display either 'Software' or 'Eon_Software'.
* Enter, as appropriate, either
Software -s ramdisk=12000
or
Eon_Software -s ramdisk=12000
and press enter.
* As the OS boots, press alt-F2 (possibly more than once) until you are greeted with a bash prompt.

Step TWO: Fetch and install m0n0wall.

* Check that your installation has the necessary software:
bash# ls /usr/bin/wget
. If NeoLinux reports that it is not found, you will have to try a different EON. Keep this hardware however: a single working EON can program m0n0wall onto several disk-on-chip modules, even those without the proper software. More on this later.
* Plug the EON into a network which provides DHCP information and enable the ethernet connection:
bash# cp /etc/sysconfig/network-scripts/ifcfg-eth0.default /etc/sysconfig/network-scripts/ifcfg-eth0
bash# ifup eth0
* Create a ramdisk on which to place temporary files during the installation:
bash# mkfs.ext2 /dev/ram0
bash# mount /dev/ram0 /mnt/usbcdrom
bash# cd /mnt/usbcdrom
bash# /usr/bin/wget http://hostname/path/to/m0n0wall
bash# cp /bin/gunzip .
bash# cp /bin/dd .
* Now you're ready. You have created a ramdisk with the two utilities you will need to rewrite IDE disk-on-chip modules with m0n0wall. At this point, if you have modules containing copies of NeoLinux without wget, you should try using them first. That way if something goes wrong you can repeat these steps later. With the machine running, remove the IDE DOC that you booted from and replace it with the one you want to reprogram.
* Then,
gunzip -c m0n0wall-file-name.img | dd of=/dev/hda bs=16k
Ignore the warning about trailing garbage.

That's it! At this point you can remove the DOC and replace it with another one and repeat the reprogramming step, as many times as needed.

When you next boot the machine, it should load m0n0wall exactly as it would on any other x86-compatible system. Jump right in with the m0n0wall quick-start guide for PC platforms. Chapter 3: Initial Configuration is probably where you will want to start. Good luck!

Version 0.3 | Content date: 05 July 2008 | Page last generated: 2009-01-18 13:11 CST

Scratch

2009-01-21T19:48:06Z

129.57.81.176:

5126
303-6644

CLAS12 DC (Mac 14-nov-2007): 2 stereo, +-6 degrees, good resolution (1% dp/p, 1 mrad angle), six 6-layer superlayers, 112 wires per layer; reconstruction improvements: use double hits, use segment angle in road dictionary, early l-r ambig. resolution (now it resolved locally and then corrected after track reconstructed ?), find tracks with no TOF hit and cut off accidental tracks (using residials ?), derive off-diagonal terms in error matrix

SVT readout:

SVX4 - old chip
132ns clock, 40pipeline cells ->5.2us trigger latency; can select readout window like pipeline TDCs (position defined +-132us, window size 132ns fixed)
initial part stored upto 4 events, they are rotating internally
32 bits per hit, 128 channels per chip, ... -> 3.2us per chip to get data from the chip to the buffer of 512 full events
L2 pipeline 16us
L1 latency from Amrit is 3us, Amrit will try to make it 4us
Use the same clock as entire CLAS12 trigger system (256MHz)

FSSR 125ns instead of 132ns (built for BTev, never used)
self-triggering, do not need L1ACCEPT, L2 pipe 16us can be implemented

SVX4 goes to review !!!

Generic DAQ drawing will be sent to Amrit in April

Clasxt

2009-01-21T19:47:58Z

129.57.81.176:

'''Clonxt''' machines are diskless 'thin clients' from neoware, running newlinux.

To reboot in single user mode do following:

* Power on the EON and hold the left shift key down until you are shown a boot prompt
* The boot prompt should display 'Software'
* Enter ''Software -s ramdisk=12000'' and press enter
* As the OS boots, press alt-F2 (possibly more than once) until you are greeted with a bash prompt

Some information can be found in following paper:

Some reports indicate that 3.x builds do not work. The error that is reported is
FATAL ERROR
The device that contains the configuration file (config.xml) could not be found. m0n0wall cannot continue booting.
I do not yet know of a solution. This tutorial should be construed to apply only to the 2.x builds in the meantime. Please email me if you get 3.x working on an EON.

Here's how to install the latest build of the excellent m0n0wall firewall on a Neoware EON 4000 thin client. These machines make excellent firewalls for home users and small businesses because they are cheap, compact, sturdy, and powerful enough to run a several megabit connection. The hardware is available in a variety of configurations, with CPUs roughly equivalent to a 150-200Mhz Pentium. Before embarking on this little journey, you should be aware of a few caveats:

* Some Neoware boxes come with a 32-pin Disk-on-Chip module in a socket on the motherboard. m0n0wall does not ship with the required driver to run this module. Therefore, on these systems you will need a hard drive, compact flash to IDE adapter, or similar device to boot from. You may also be able to netboot your firewall (this is supported on the built-in network device), though I do not cover that in this tutorial.
* The motherboard accepts both PC133 DIMMs or SO-DIMMs. It will use both at the same time. However, when using a DIMM, be sure it is less than 1.1" (28mm) tall, or you will not be able to install a second network card.
* There are many different revisions of the NeoLinux operating system and not all include the necessary software to complete this tutorial.
* You may need to purchase several EON 4000s to get suitable software and hardware.
* These instructions were based on NeoLinux 2.4-100802, with kernel 2.2.20. Your particular configuration may vary slightly.

With those potential issues in mind, follow along!

There are three main steps to be completed to get m0n0wall running on your EON. First, you will need to get single-user access to the NeoLinux installation. Next, you need to enable networking and fetch and install m0n0wall. Third, you need to configure it to fit your requirements. I will address the first two of these, as adequate resources exist to help with the latter.

To begin, you will need:

* One or more Neoware EONs with disk-on-chip modules that plug into the IDE header
* Access to the internet from your EON (or to a web server on a LAN)
* A supported PCI network card. Common Intel or 3Com cards work fine.
* At least 64MB of suitable memory. Some EONs ship with SO-DIMMs, others with DIMMs. These should be short enough to accomodate a PCI network card.
* See the m0n0wall supported hardware page for more information.

Step ONE: Get single-user access to the NeoLinux distribution.

* Power on the EON and hold the left shift key down until you are shown a boot prompt
* The boot prompt may vary, but pressing tab should display either 'Software' or 'Eon_Software'.
* Enter, as appropriate, either
Software -s ramdisk=12000
or
Eon_Software -s ramdisk=12000
and press enter.
* As the OS boots, press alt-F2 (possibly more than once) until you are greeted with a bash prompt.

Step TWO: Fetch and install m0n0wall.

* Check that your installation has the necessary software:
bash# ls /usr/bin/wget
. If NeoLinux reports that it is not found, you will have to try a different EON. Keep this hardware however: a single working EON can program m0n0wall onto several disk-on-chip modules, even those without the proper software. More on this later.
* Plug the EON into a network which provides DHCP information and enable the ethernet connection:
bash# cp /etc/sysconfig/network-scripts/ifcfg-eth0.default /etc/sysconfig/network-scripts/ifcfg-eth0
bash# ifup eth0
* Create a ramdisk on which to place temporary files during the installation:
bash# mkfs.ext2 /dev/ram0
bash# mount /dev/ram0 /mnt/usbcdrom
bash# cd /mnt/usbcdrom
bash# /usr/bin/wget http://hostname/path/to/m0n0wall
bash# cp /bin/gunzip .
bash# cp /bin/dd .
* Now you're ready. You have created a ramdisk with the two utilities you will need to rewrite IDE disk-on-chip modules with m0n0wall. At this point, if you have modules containing copies of NeoLinux without wget, you should try using them first. That way if something goes wrong you can repeat these steps later. With the machine running, remove the IDE DOC that you booted from and replace it with the one you want to reprogram.
* Then,
gunzip -c m0n0wall-file-name.img | dd of=/dev/hda bs=16k
Ignore the warning about trailing garbage.

That's it! At this point you can remove the DOC and replace it with another one and repeat the reprogramming step, as many times as needed.

When you next boot the machine, it should load m0n0wall exactly as it would on any other x86-compatible system. Jump right in with the m0n0wall quick-start guide for PC platforms. Chapter 3: Initial Configuration is probably where you will want to start. Good luck!

Version 0.3 | Content date: 05 July 2008 | Page last generated: 2009-01-18 13:11 CST

Clasxt

2009-01-21T19:44:55Z

129.57.81.176:

CLON Index

2009-01-21T19:41:26Z

129.57.81.176:

[[Apache]]

[[automounts]]

[[Bootp]]

[[CAEN A464]] caenet board (installed in sy527 mainframes)

[[CAEN SY1527 Mainframe]]

[[CAEN SY527 Mainframe]] and modules

[[CAEN V1190]] TDC board (128 ch 100 ps)

[[CAEN V1290]] TDC board (32 ch 25 ps)

[[CAEN V288]]

[[CAEN V775]] TDC Board

[[Capfast]]

[[Cisco Switches]]

[[Clasweb]]

[[Clon00]]

[[Clon01]]

[[Clon02]]

[[Clon03]]

[[Clon04]]

[[Clon05]]

[[Clon06]]

[[Clon10]]

[[Clon20]]

[[Clondaq1]]

[[Clondaq2]]

[[Clondb1]]

[[Clonfs]] Main RAID System

[[Clonfs1]]

[[Clonfs2]]

[[Clonmon]]

[[Clonmon1]]

[[Clonpc1]]

[[Clonpc2]]

[[Clonweb]]

[[Clonwiki]]

[[Clonxt]]

[[clonhp]]

[[clonhp2]]

[[Compcontrol CC121]]

[[CycladesTS1000]]

[[DATEL DVME-628]]

[[DNS server]]

[[Electronics Documentation]]

[[EtherLite32]]

[[EPICS Base Installation]]

[[EPICS: Software IOC]]

[[EPICS: vxWorks IOC]]

[[EPICS: Software IOC for CAEN HV]]

[[EPICS: generation of DBs and GUIs for HV]]

[[EPICS: CVS usage examples]]

[[EPICS: Gamma Profiler]]

[[Event Monitor]]

[[Fiber Channel Switches]]

[[FieldPoint]]

[[Foundry BigIron 15000 Switch]]

[[Foundry Switches]]

[[JAVA installation]]

[[JLAB Discriminators]]

[[Joerger VSC16]]

[[HYTEC VSD2992]]

[[Labeling Machines]]

[[Linux Installation Procedure]]

[[Linux Customization on CLON Cluster]]

[[Lnf cluster]]

[[Mac OS X Installation Procedure]]

[[MRTG]]

[[mSQL]]

[[MySQL Installation]]

[[MySQL Usage]]

[[Nagios]]

[[Nagios Plugins]]

[[NFS]]

[[NIS server]]

[[Nrpe]]

[[Ntp]]

[[OMS VME44]] by Oregon Micro Systems

[[OMS VS4]] by Oregon Micro Systems

[[OpenSSL]]

[[PERL]]

[[Procmail]]

[[raidold]]

[[Routing]]

[[Rrdtool]]

[[SBS VIPC616]]

[[Serial Connections from Computer Ports]]

[[Slow Controls Time History]]

[[SmartSockets]]

[[SNMP]]

[[Software Documentation]]

[[Solaris Installation Procedure]]

[[Solaris Customization on CLON Cluster]]

[[SSH]]

[[Struck SIS3801]]

[[Sudo]]

[[SUN Microsystems]]

[[SYSTRAN VMESC5]]

[[Tcl/Tk]]

[[Tftp]]

[[JLAB FLEXIO]]

[[Troubleshooting printing]]

[[UNIX Automount on CLON Cluster]]

[[UPS (Uninterruptible Power Supplies)]]

[[UPS CHB1]]

[[UPS CHB2]]

[[UPS Troubleshooting]]

[[VI editor]]

[[VMIC VMIVME-3122]]

[[VMIC VMIVME-2120]]

[[VMIC VMIVME-1129]]

[[VMIC VMIVME-2232]]

[[VMIC VMIVME-6015]]

[[VMIC VMIVME-6016]]

[[VNC]]

[[WIENER]]

[[Wiki]]

[[Wiring]]

[[X server]]

[[Xycom DIO XVME-240]]

[[Xycom XVME-564]]

[[Xycom XVME-560]]

[[ZFS]]

CLON meeting January 21, 2009

2009-01-21T16:22:39Z

129.57.81.176:

Clas On-line Meeting, Wednesday, January 21 at 10am in Room A110
------------------------------------------------------------------

1. Current run status

- HV mainframes, boards

- discriminators

2. Next run preparations

CLON meeting January 21, 2009

2009-01-21T16:22:30Z

129.57.81.176:

January 21, 2009 online meeting minutes

2009-01-21T16:16:43Z

129.57.81.176:

present: Sergey Boyarinov, Sergey Pozdnyakov, Nerses Gevorgyan

'''1. Current run status'''

'''HV system'''

* in CLAS everything works for now

* there are good spare boards: 1461N - 9 boards, 1461P - 2 boards

* SY527 with old CAENET controller: repair ??? waiting for instructions from CAEN

* there is no good spare Lecroy mainframes; 2 in repair since November 2008, 1 from July 2008, waiting for status; 3 in Counting House, repair needed, RMA under way;
there is one Lecroy mainframe (temporary rack in EC), can be replaced with sy1527 (from Yuri ?) so we'll have 1 spare mainframe and 8 1461N boards, will do it after the run (tomorrow); need to register ''hvec2'' IP name

* two SY1527LC mainframes with 'full crate' problem (when crate is full, first board shuts off and sometimes disapeares) have to be repaired in CAEN, will send them one by one starting from ECHV2 where TCP/IP is broken as well

* waiting for answer from CAEN about other SY1527/SY1527LC, if they have the same problem

* multi-pin HV connectors must be improved, need to ask manufacturer if glue can be used or some other solution can be recommended; Sergey P. will contact company; connectors must be improved, '''otherwise it will be a big problem for the CLAS and CLAS12'''

* will be good to modify medm gui generating process to have geographic addressing information in gui (alarm gui and probably main gui)

* 1520 boards (used in IC): 4 in CLAS, 2 channels are bad in 2 boards, one spare channel; 2 boards in test setup: one board is good, one has channel 8 dead (must goto repair if we have more then 1 month downtime, probably in March); may buy one more when have a money

'''Discriminators'''

* 3 v895B boards in counting house: one just from repair and working, one has unstable width and will be send to CAEN, one has 2 channels with min threshold 600mV and 45mV (must be from 5mV to 50mV); about 7 boards in CLAS has similar threshold problem, Sergey P. will ask CAEN if we can fix them onsite

* will not buy new boards, will ask Chris to build boards onsite

'''2. Next run'''

* Target labview setup: meet with Chris

* DCHV EPICS debugging

* ask Chris if he can replace some FASTBUS power supplies

* will try to migrate classc5 and probably classc12 to EPICS 3.14

January 21, 2009 online meeting minutes

2009-01-21T16:10:25Z

129.57.81.176:

January 21, 2009 online meeting minutes

2009-01-21T15:45:31Z

129.57.81.176:

present: Sergey Boyarinov, Sergey Pozdnyakov, Nerses Gevorgyan

'''1. Current run status'''

'''HV system'''

* in CLAS everything works for now

* there are good spare boards: 1461N - 9 boards, 1461P - 2 boards

* there is no good spare Lecroy mainframes; 2 in repair since November 2008, 1 from July 2008, waiting for status; 3 in Counting House, repair needed, RMA under way;
there is one Lecroy mainframe (temporary rack in EC), can be replaced with sy1527 (from Yuri ?) so we'll have 1 spare mainframe and 8 1461N boards, will do it after the run (tomorrow)

* two SY1527LC mainframes with 'full crate' problem (when crate is full, first board shuts off and sometimes disapeares) have to be repaired in CAEN, will send them one by one starting from ECHV2 where TCP/IP is broken as well

* waiting for answer from CAEN about other SY1527/SY1527LC, if they have the same problem

* multi-pin HV connectors must be improved, need to ask manufacturer if glue can be used or some other solution can be recommended; Sergey P. will contact company; connectors must be improved, '''otherwise it will be a big problem for the CLAS and CLAS12'''

* will be good to modify medm gui generating process to have geographic addressing information in gui (alarm gui and probably main gui)

January 21, 2009 online meeting minutes

2009-01-21T15:22:28Z

129.57.81.176:

present: Sergey Boyarinov, Sergey Pozdnyakov, Nerses Gevorgyan

'''1. Current run status'''

'''HV system'''

* in CLAS everything works for now

* there are good spare boards: 1461N - 9 boards, 1461P - 2 boards

* there is no good spare Lecroy mainframes; 2 in repair since November 2008, 1 from July 2008, waiting for status; 3 in Counting House, repair needed, RMA under way;
there is one Lecroy mainframe (temporary rack in EC), can be replaced with sy1527 (from Yuri ?) so we'll have 1 spare mainframe and 8 1461N boards, will do it after the run

* two SY1527LC mainframes with 'full crate' problem (when crate is full, first board shuts off and sometimes disapeares) have to be repaired in CAEN, will send them one by one starting from ECHV2 where TCP/IP is broken as well

* multi-pin HV connectors must be improved, need to ask manufacturer if glue can be used or some other solution can be recommended; Sergey P. will contact company; connectors must be improved, '''otherwise it will be a big problem for the CLAS and CLAS12'''

* will be good to modify medm gui generating process to have geographic addressing information in gui

January 21, 2009 online meeting minutes

2009-01-21T15:15:38Z

129.57.81.176:

present: Sergey Boyarinov, Sergey Pozdnyakov, Nerses Gevorgyan

'''1. Current run status'''

'''HV system'''

* in CLAS everything works for now

* there are good spare boards: 1461N - 9 boards, 1461P - 2 boards

* there is no good spare Lecroy mainframes; 2 in repair since November 2008, 1 from July 2008, waiting for status; 3 in Counting House, repair needed, RMA under way;
there is one Lecroy mainframe (temporary rack in EC), can be replaced with sy1527 (from Yuri ?) so we'll have 1 spare mainframe and 8 1461N boards, will do it after the run

* two SY1527LC mainframes with problems have to be repaired in CAEN, will send them one by one starting from ECHV2 where TCP/IP broken as well

*

* will be good to modify medm gui generating process to have geographic addressing information in gui

CLON Group Meetings

2009-01-21T15:02:34Z

129.57.81.176:

[[CLON meeting December 13, 2006]] >>>>> [[December 13, 2006 online meeting minutes]]

==== 2007

[[CLON meeting September 5, 2007]] >>>>> [[September 5, 2007 online meeting minutes]]

[[CLON meeting September 12, 2007]] >>>>> [[September 12, 2007 online meeting minutes]]

[[CLON meeting September 19, 2007]] >>>>> [[September 19, 2007 online meeting minutes]]

[[CLON meeting September 26, 2007]] >>>>> [[September 26, 2007 online meeting minutes]]

[[CLON meeting October 3, 2007]] >>>>> [[October 3, 2007 online meeting minutes]]

[[CLON meeting October 10, 2007]] >>>>> [[October 10, 2007 online meeting minutes]]

[[CLON meeting October 17, 2007]] >>>>> [[October 17, 2007 online meeting minutes]]

[[CLON meeting October 24, 2007]] >>>>> [[October 24, 2007 online meeting minutes]]

[[CLON meeting October 31, 2007]] >>>>> [[October 31, 2007 online meeting minutes]]

[[CLON meeting November 7, 2007]] >>>>> [[November 7, 2007 online meeting minutes]]

[[CLON meeting November 14, 2007]] >>>>> [[November 14, 2007 online meeting minutes]]

[[CLON meeting November 28, 2007]] >>>>> [[November 28, 2007 online meeting minutes]]

[[CLON meeting December 12, 2007]] >>>>> [[December 12, 2007 online meeting minutes]]

==== 2008

[[CLON meeting January 16, 2008]] >>>>> [[January 16, 2008 online meeting minutes]]

[[CLON meeting January 23, 2008]] >>>>> [[January 23, 2008 online meeting minutes]]

[[CLON meeting January 30, 2008]] >>>>> [[January 30, 2008 online meeting minutes]]

[[CLON meeting February 13, 2008]] >>>>> [[February 13, 2008 online meeting minutes]]

[[CLON meeting March 5, 2008]] >>>>> [[March 5, 2008 online meeting minutes]]

[[CLON meeting March 12, 2008]] >>>>> [[March 12, 2008 online meeting minutes]]

[[CLON meeting March 26, 2008]] >>>>> [[March 26, 2008 online meeting minutes]]

[[CLON meeting April 16, 2008]] >>>>> [[April 16, 2008 online meeting minutes]]

[[CLON meeting April 23, 2008]] >>>>> [[April 23, 2008 online meeting minutes]]

[[CLON meeting May 21, 2008]] >>>>> [[May 21, 2008 online meeting minutes]]

[[CLON meeting June 4, 2008]] >>>>> [[June 4, 2008 online meeting minutes]]

[[CLON meeting June 18, 2008]] >>>>> [[June 18, 2008 online meeting minutes]]

[[CLON meeting July 2, 2008]] >>>>> [[July 2, 2008 online meeting minutes]]

[[CLON meeting July 16, 2008]] >>>>> [[July 16, 2008 online meeting minutes]]

[[CLON meeting September 10, 2008]] >>>>> [[September 10, 2008 online meeting minutes]]

[[CLON meeting September 17, 2008]] >>>>> [[September 17, 2008 online meeting minutes]]

[[CLON meeting September 24, 2008]] >>>>> [[September 24, 2008 online meeting minutes]]

[[CLON meeting October 1, 2008]] >>>>> [[October 1, 2008 online meeting minutes]]

[[CLON meeting October 15, 2008]] >>>>> [[October 15, 2008 online meeting minutes]]

[[CLON meeting November 12, 2008]] >>>>> [[November 12, 2008 online meeting minutes]]

[[CLON meeting January 21, 2008]] >>>>> [[January 21, 2009 online meeting minutes]]