sure.  can probably copy 2.7 from any "0.5" bamt image into a 0.4 disk for that matter.  but i am not sure thats a good idea with the stability issues.

when cgminer works but bamt can't talk to it, usually means the API handling part of cgminer has died.  often I see that happen as a precursor to cgminer totally locking up (or even taking down the entire rig, which always sucks).  but maybe it also can happen and then cgminer goes on like a zombie without communication to the outside world.  maybe possibilities.

It is the same. changeme

EDIT -> Not same in 0.5b
See notes at http://bamter.org/download.html

Sorry I was unclear. Just too eager to get it up and running

Yes, I had touble. 'changeme' did not work. I downloaded bamt_v0.5b.img and copied from BAMT/CONF/FROM to BAMT/CONF/TO.

I have now booted the stick on a box with a screen attached. There I could set the password in the root terminal. New password worked.

Im pretty sure I didn't mess up when trying with 'changeme'. I tried like 10 times.

I get these same issues on 0.4 where when a gpu is dead in cgminer, i coldreboot only to come back 10 minutes later and xOrg is taking up 99% cpu. I've just worked around it up to this point because lodcrapppo has enough to do I'm sure.

To be clear, this only happens on 4 out of 18 rigs.

Err oops I wasn't aware of that.

On .4 I had to install libncurses-dev and libcurl4-openssl-dev and define CFLAGS instead of just using the normal CFLAGS="-O2 -Wall -march=native" ./configure, but I suck at Linux so there may be an easier way.  This has worked for me on 6 installs though.

I had a board that would do this also.  It was totally untraceable.  Would run stable for days some times, others it would reboot 4 or 5 times a day.  Changed hardware, changed software, beat my head on various walls, nothing helped.  I stripped everything from the mobo with the intent of smashing the hell out of it one day, Office Space style.  Noticed a "smudge" of some sort on the back of the board, some unidentifiable substance clinging there like a someone with a cold sneezed before the board got packaged.  I wiped it off with some alcohol swabs and reinstalled everything.  Disco.  Whatever the hell it was, was causing something to randomly short out and reboot the board.  I never inspected the board before I built the system, just pulled it from the box, and installed everything.  Now, I very carefully check every component before I do an install.


Back on topic;

I have the same issues as D&T is having with the 0.5 release, don't know if it is BAMT related or a cgminer thing, so until I have the time, and energy to track it down, going to stick with the 0.4. 

It is very unlikely but possible.  ATX power switch is "soft" meaning shorting it will cause MB to send power off signal to the OS rather than kill power directly.  On some motherboards (but not the 890FXA-GD70 grr) you can change this to be instant off (no holding for 5 seconds to hard poweroff).  IF you did that and the problem switched to hard power down it likely is a short.  

If you have any switch connected to the power switch header you could also try removing it and see if the problem goes away.  If it does then power switch itself likely has an intermittent short.  Personally I don't use any power switches.  Just set BIOS to power on after power loss and use the power supply and then use the AC power switch on PSU.

The only time I have ever seen a machine reboot for no reason in my cluster is because one of the two PSUs was overloaded or the fan on the PSU had stopped working.