Fix #21 - Offline interface + Tool updates + Bugfix
Lots of stuff in this one.
First, fixes a small bug in the last update that causes error messages on LPs (does not effect mining).
All the BAMT tools are upgraded as well. Some of the changes are things I had fixed/added long ago and never made it into the mainline. Other improvements are all new. Lots of changes you probably won't notice but should help things work in more situations. Most don't need you to change anything, but a couple things do need your attention to take advantage of them:
There are 2 new per GPU config options:
# optional phoenix queuesize parameter: how many work units to keep queued at all times
# queue_size: 2
# optional phoenix avgsamples parameter: how many samples to use for hashrate average
# avg_samples: 10
These correspond to the matching Phoenix parameters. There is also a new optional item that can be specified on each pools file line to pass a backup pool URL to Phoenix.
This is the 4th paramter on an entry, after the primary, max shares, and pool timeout (max shares and pool timeout are optional but the place must be held).
So, to use a backup pool, make an entry like:http://u:firstname.lastname@example.org
or, if you don't want to set maxshares and pool timeout:http://u:email@example.com
You will find an example bamt.conf and pools file, both with all options described, in /opt/bamt/examples
Finally, I've added a new thing I call the BAMT Offline Config and Control Thing. I'll try to explain it.
There is a new directory, "BAMT", that will show up on the USB key when it in inserted into a Windows or Mac PC (or another linux box too, but with a linux box you could just mount the real drive anyway..)
Inside the BAMT directory are 3 more directories, their function described below.
Files inside the CONFIG directory are synced with files in the /etc/bamt
directory inside the BAMT system. Syncronization is done based on last write
timestamp, and is performed any time the /etc/init.d/mine script is executed.
The newer version of the file will replace the older whether from this
directory or from /etc/bamt. Please check that your system clocks are
reasonably accurate on all computers that touch either set of files, or
you may have unexpected results.
This allows you to access and modify the system's configuration from another
machine, or to create a ready to mine key with complete config before you ever
turn on the miner. For people who are terrified of linux, you can now do all
your configuration with whatever OS you are comfortable in.
Files inside the CONTROL directory are used to effect the operation of
the BAMT node. The primary reason to use these settings is in the
recovery of a node that is locking up at boot or in debugging strange
issues. In other words, if your rig is mining fine, nothing to see in
Inside CONTROL you will find several flag files and a directory
called ACTIVE. To activate a particular option, move the flag file into
the ACTIVE directory. To disable an active option, remove it from the
ACTIVE directory (it is suggested you keep the flag files right outside
of the ACTIVE directory in the CONTROL directory). If you delete or
lose the flag files, it is not a problem. Simply create a file with
the name of the option you wish to use. The contents are unimportant.
The names are not case sensitive.
Known options at the time this document was written:
noX - Do not start X (Mining will not start without X)
noReXconf - Do not regenerate /etc/X11/xorg.conf
noMine - Do not start the mining processes (but do start X)
noOC - Do not overclock any GPUs (but do start mining processes)
noOCGPUx - Do not overclock GPU x
noGPUx - Do not mine with GPU x
noStatus - Do not gather status in offline output dir
noSync - Do not sync offline and live configs
Contains various information that may be useful when troubleshooting problems.
Most of this is generated when the node boots up or when a serious error
is detected. Information contained includes the output out various
diagnostics, log files, etc.
If your machine is locking up after boot, you might not be able to login and
look at what's going on. The STATUS directory contains information that will
help you see what's happening.
OK... I think that's most of it.. enjoy.