Topic: BAMT version 0.5 - Easy USB based mining Linux with farm wide management tools - page 25. (Read 324185 times)

I was responding to the numerous requests from people as to why bamt keeps restarting the newer versions. We know you only support older versions but that doesn't mean that everyone out there will want to stick to them. I instrumented it because cgminer kept getting blamed, and I had no care about the AMD aspect; I was just explaining why it was hard to test it on hardware I had available to try it on (all of which have nvidia GPUs).

BAMT is only for AMD gpu mining.  It is not designed to work without one.

If you use the cgminer included in BAMT, you'll not have this problem.  Newer versions of cgminer are not supported at this time.  If we release an update, we will adjust mother to work with the updated version.

usb key has died.  might work if you reflash, might not, or might work for a day or two and die again.

underclocking will crash cards too.  you may also have a situation where your over/underclocking of card A is making card B unstable.  messing with clocks is a loser's game in many cases.  you will just have to experiment until you find what works.

yup, you're right    i was looking into it and find it to be restarted and the counter set to zero. I just cant tell why, because the card ist underclocked, not overclocked.
Is there a logfile where i can get further informations on why it crashed?

This happens maybe for 3-rd time, other bamt rigs are in working condition. I know only one solution - clean format and fresh install but this would happened in monday because I am far away. Next step will be strong UPS for main rigs ... or MS Windows.

I would create a fresh USB stick and copy over your config files, just to rule out some issues with your current USB stick. I have had wacky things happen sometimes and building it fresh from the image has resolved them.

So problems continues after new unexpected power down : xauth:  error in locking authority file /root/.Xauthority
message : read-only file system
Starting mining processes...: minestart_mining: starting mining processes
..muninrm: cannot remove `/etc/munin/plugins/gpuhash_all': Read-only file system
rm: cannot remove `/etc/munin/plugins/gputemp_all': Read-only file system
rm: cannot remove `/var/lib/munin/plugin-state': Read-only file system
ln: creating symbolic link `/var/lib/munin/plugin-state/run': File exists
..GPU 0..fan 0..OC 0..GPU 1..fan 1..OC 1..GPU 2..fan 2..OC 2.

I cant reboot machine, or start mining  

Well after a few hours of messing around with this, I had to shoehorn shit all over the place to make it mine on a machine that did NOT have an AMD card which BAMT seems not to work with...

Anyway I instrumented the newer cgminer restart problem in bamt and it is indeed in the /opt/bamt/mother monitoring file. The perl parsing of ps axu output fails to detect cgminer is there and it then calls /etc/init.d/mine restart . So it is in fact bamt that is restarting cgminer, and if I edit the mother script to parse the output of ps axu differently, it does NOT continually restart cgminer. Alas I don't really know perl, but it does seem to need fixing.

If you copy this file on top of mother in /opt/bamt it shouldn't restart on you (note this is not the correct fix and will probably not restart cgminer should it actually really crash):
http://ck.kolivas.org/apps/cgminer/temp/mother

Based on what you cut and pasted, that's not what appears to be the case.

thanks for reply, but i dont think this is the case. It looks like one card is behind all other cards right from the beginning - not reseting at some point. It just sums up slower.
If this really is the case i miss some good mhashs on that, amirite?

As per the README, a single instance of cgminer can mine only one LP chain

You need to run 2 cgminers to mine two chains at the same time

Meanwhile ... I've seen comments about BAMT and cgminer 2.6.4 - but it also seems that no one with BAMT know how, wants to sort it out
i.e. I have completely NFI what even is wrong
If it is just a BAMT problem, then fine, but if it is a cgminer problem, then someone who uses BAMT and understands it needs to come visit FreeNode IRC #cgminer

My latest 'linux' change to the API means that when you exit cgminer (properly) and start it again immediately, it will open the API port successfully immediately as long as nothing is still holding the old one open
If it's still held open by a connecting app, then it's the same as before.
i.e. before it would take up to 90s to open the API port, but now if the port is only in TIME_WAIT and closed, it doesn't delay the new one opening (SO_REUSEADDR)

Some possible problems, that would stop this new feature being faster than before (and thus only the same as before), would be:
killing cgminer, rather than quitting it via the API, may hold the port until it times out
running a php script that doesn't exit (php often holds the ports until timeout)
any other app that does the same ...

Also note, that there is no way to actually get around the timeout if the port is held, that's just how sockets work (properly) on linux.
(on windows ... wow that's a different issue, any code can go grab another non privileged socket that wasn't opened with SO_EXCLUSIVEADDRUSE and use it as it pleases, and the original app may not know but will get it back when the offending app closes it)

the mining software crashed and BAMT's mother kicked it in the ass and got it restarted for you.
phoenix crashing is usually the result of too much overclocking.

Check here for more tips: (Using BAMT section)
http://bamter.org/redmine/projects/bamt/wiki/FAQ

Just find the IP of your rig, and SSH to it. If on windows, a great free SSH tool is Putty. (Google that)

i have 3x6950 and 1x5350 all unclocked
since i dont have a computer at home right now i simply jumped in head-first.
i only had two hours to busy myself with the thing but found it surprisingly easy.

if ssh etc are already part of the package, it might be cool to add it in to the menu and suppy a commented conf file so even a noob like me can work it^^

What hashing hardware do you have? GPU model or FPGA ?

i believe ssh/telnet is already a feature in BAMT, did you read all the readme and visit the website for it?

tried BAMT yesterday, works like a charm.
on win7, the new catalyst shitdrivers slowed my system down to 700mhash, getting back to 1250mhasch now.
great system, almost completely noob-proof, took me 30mins to figure it out and 20mins to configure.

pet peeve / feature request:


I'd like to be able to ssh/telnet into my rig since its miles away.
if there isnt already (and i just havent found it), would it be possible to include some sort of preconfigured static IP service (like http://www.dtdns.com/) and a semi-preconfigured ssh-tunnel-thingy that i can use to log in from work?


as a linux-noob, i hertily approve of and recommend this product.

Here's a link to the thread:

http://www.bitcointrading.com/forum/index.php?topic=416.msg1835#msg1835

Feel free to share that link with whomever.  

To save time, see the script in the post to update cgminer with 1 execution of the script.  I'm not sure if with my instructions if BAMT will start mining automatically or if the "export GPU_MAX_ALLOC_PERCENT=100" has to be added to the internal BAMT scripts or something.  If anyone has any suggestions I will add them.  Someone sent me a wonderful PM which provided this info to me, I still have to go over it and add that info into the guide.

I'm not sure, definitely worth experimenting.  I know cgminer can't do both at the same time.  Maybe one card can be configured to cgminer doing LTC and another is configured to phoenix doing BTC, I see that as being a possibility.

You just need to compile the current cgminer version (2.6.X) with the --enable-scrypt flag.  Just follow the few post that have cgminer upgrade instructions and add that.

Hello. I have problem after power off/on. Bamt.conf i ok and 3 GPU's are ok but no mining.
http://anonymouse.org/cgi-bin/anon-www.cgi/http://anonymouse.org/cgi-bin/anon-www.cgi/http://anonymouse.org/cgi-bin/anon-www.cgi/http://anonymouse.org/cgi-bin/anon-www.cgi/http://anonymouse.org/cgi-bin/anon-www.cgi/http://anonymouse.org/cgi-bin/anon-www.cgi/http://img846.imageshack.us/img846/6608/bamt1.jpg
mother says all is ok, bamt fixer cant start - just popup window and closes quickly
P.S. cant start X server due internal error ... problem solved: starting X manual
Other problems after power off after 7-10 days uptime one of my rigs cant boot with error - some like "kernel panic not syncing: no init found try passing init option tolerance address space collision on of device [0x] ..." on 8gb usb flash.
Tnx :-)