Continued from: http://lab46.corning-cc.edu/user/jbrant/csit2320/video_wall_4_starcraft

Once Chromium is installed, running it can be a bit tricky across multiple computers, luckily we have created a number of scripts to get the system up and running.

You will need the following two scripts to launch Chromium and display it's awesomeness.. But save these for the moment, because there is more preliminary work to do!

NOTE All of the IP addresses and computer names are very dependent on your setup, if your system differs, you must go through the code and update any variances..

cr-start.sh

#!/bin/bash
#
 
        pkill python
        pkill crappfaker
 
        cd /root/cr-1.9/startup
        source ./cr-run
        cd /root/cr-1.9/mothership/configs
        #python dmx.conf /root/cr-1.9/bin/Linux/spheres &
        python dmx.conf /usr/lib/xscreensaver/$1 -fps -geometry 2749x1590+0+0 &
        sleep 8
 
for i in 1 2 3 4 5 6; do
 
        ssh 10.80.1.7$i "pkill crserver;source /root/cr-1.9/startup/cr-run;/root/cr-1.9/bin/Linux/crserver" &
done
        sleep 2
        source /root/cr-1.9/startup/cr-run
        cd /root/cr-1.9/bin/Linux
        ./crappfaker &

cr-run.sh

# chromium start script
 
export LD_LIBRARY_PATH=/root/cr-1.9/lib/Linux
export CRMOTHERSHIP=wall01.lair.lan
export DISPLAY=wall01:1

xup.sh

#!/bin/bash
#
# xup - bring X up on all video wall nodes
#
for i in 01 02 03 04 05 06; do
        ssh wall$i "startx" &
done

wallup.sh

#!/bin/bash
#
# wallup - bring Xdmx online
#
#Xdmx :1 +xinerama -ac -ignorebadfontpaths -configfile dmx.conf & (sleep 4; fluxbox -display localhost:1) &
/usr/bin/Xdmx :1 +xinerama -ac -ignorebadfontpaths -configfile /root/dmx.conf & (sleep 2; export DISPLAY=localhost:1; /usr/bin/xlogo -geometry 1x1-1-1) &

wakeup.sh

#!/bin/bash
#
# wakeup - wake up a sleeping video wall
#
for i in 01 02 03 04 05 06; do
        ssh wall$i "echo -n \"[wall$i] \"; export DISPLAY=\"localhost:0\"; xhost +; xset dpms force on" &
done

There's one more thing that must be done before we can start up chromium, configure the dmx. Navigate to the mothership config directory.

$ cd /cr-1.9/mothership/config/

Edit the dmx.conf file, and change the following to match your setup.

TILE_ROWS
TILE_COLS
HOSTS

Save the file and we can now continue.

Now that you have gone through all the work of getting everything set up and obtaining the scripts, you probably want to run the wall right?

To get things rolling, follow this procedure.
Log into wall01

$ ssh root@wall01.student.lan

Enter the password…
SCP your startup scripts, and place the two chromium scripts in /cr-1.9/startup

Now you want to start the X-server on the wall machines.

$ ./xup.sh

This will start up the xserver on pairs of monitors, but not one unified x-window.

To make the wall run as one monitor execute the wallup script.

$ ./wallup.sh

Verify that the mouse controlled off of wall01 can be moved across the entire field of view.

Once this has been verified, open up a large version of x-eyes - this is a good monitor offset tool and can identify any areas where your monitor offset may need to be adjusted in the dmx.conf file.

This LOOKS impressive, but we are not done yet, we have not unleashed the full power….

NOTE if the screens go into standby mode, you can wake the wall up using the wakeup.sh script.

$ ./wakeup

At this point, the hard work is done - all we have to do is go to the chromium startup folder and execute the scripts..

$ cd /cr-1.9/startup
$ ./cr-start.sh

This will now launch an accelerated graphical display called “spheres” - this can be changed to any in the chromium folder, feel free to experiment. To change the graphics, edit the cr-start.sh script and change the following line.

#python dmx.conf /root/cr-1.9/bin/Linux/spheres <-- Change this to anything in the /bin/Linux folder.

Enjoy!