I see people keep asking for a BAMT able to run with 7970 cards so I am thinking to share mine.
It may work for you or it may not...give it a try. It worked for me two months already so is not gonna blow your PC.

It is a BAMT updated to SDK 2.6 and 8.921 AMD driver using cgminer 2.5.0.
SDK 2.6 was recommended by ckolivas for 7970 and the 8.921 driver was (I tried all recent drivers) the only one that did not gave me hardware errors with cgminer.
Other (more recent) SDK/driver combinations could work also but this one worked perfectly for me.

All you need to do is edit bamt.conf at the cgminer_opts line and enable cgminer in each GPU section for how many cards you have.
If you want to use a separate cgminer config be my guest, I personally enter all the options I need in that cgminer_opts line.

I give no guarantees that it will work for you, it does for me with three 7970 cards.

root password = root
user password = live

Download:
https://ca.isohunt.com/torrent_details/402809617/BAMT+for+7970?tab=summary

Hope this damn torrent will work, eventually add these trackers to your bit-torrent client:

http://announce.opensharing.org:2710/announce
http://exodus.desync.com:6969/announce

It work for my, Thanks a lot

A bit later, gigavps found that 2.3f would sometimes just exit with no clear indication of why.  He was desperate for a fix, and I believe contacted you guys, posted on the cgminer forum, etc.  When no solution was forthcoming, he asked me if I could hack mother to detect that it had exited and start it back up.  So I did.

Anyway I instrumented the newer cgminer restart problem in bamt and it is indeed in theopt/bamt/mother monitoring file. The perl parsing of ps axu output fails to detect cgminer is there and it then callsetc/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 inopt/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

This error is currently the bane of my existence. 

Why does this happen, on a fresh BAMT, immediately after setting the root password?  Once that error happens, if you reboot, there's a chance it might work on next boot, but sometimes reformatting the USB helps.

I've had to format BAMT so many times now that the USB sticks are dying, and it's mostly because of this stupid Xauthority error.

Any tips?  I've asked in the past but no real solutions to this.

This error is currently the bane of my existence. 

Why does this happen, on a fresh BAMT, immediately after setting the root password?  Once that error happens, if you reboot, there's a chance it might work on next boot, but sometimes reformatting the USB helps.

I've had to format BAMT so many times now that the USB sticks are dying, and it's mostly because of this stupid Xauthority error.

Any tips?  I've asked in the past but no real solutions to this.

Found this:
https://bt.irlbtc.com/view/65915.msg885677#msg885677

I believe I had this one time, I think I did this to fix it. (Or it's maybe a bad USB flash drive?)

Fresh image to USB flash drive.
Booted with a monitor attached.
Logged in as root via the gui.
Minimal mods to the bamt.conf to get the cards enabled and on a pool. (tweak/oc/tune later)
Ran cgminer via the gui, hit F for fixer, applied all.
As root via the gui, changed PW.
Then SSH'd to it from PuTTY.

I just remember getting an error like that before, and I think logging in on the rig first before hitting it via SSH made that go away. Or I'm way off base, and I'm thinking of something completely different. Either way, hope it helps.