My rig has a hard time rebooting from the ssh command. Most of the time it sits there until you manually reboot it yourself. I'm getting some errors like "cant read os media" etc. Is this a motherboard specific problem?

never type reboot

always type coldreboot

and above all.. leave that thing alone and let it mine

ok, I'll remember that. Any specifics why 'reboot' doesn't work?

it just doesn't. no one knows why. part of bamt's mystery

If you want to support further development of BAMT (http://bamter.org/): 1PoRYaGS56ksQmK7XXLurW3B2zwCAE8PRc

I've put a pull request to ckolivas to fix 'quit'I guess it will be there once he accepts the pull (or if anyone for some unknown reason needs it urgently ... it's in my git or look at the pull request)It seems it hasn't worked for a while

I've put a pull request to ckolivas to fix 'quit'I guess it will be there once he accepts the pull (or if anyone for some unknown reason needs it urgently ... it's in my git or look at the pull request)It seems it hasn't worked for a while

Edit: and it's now in ckolivas' git.

And an explanation for anyone who uses BAMT and wants 'quit' to work:

The next version (or current git) will be API version 1.2

With the new version you must include "--api-listen --api-allow W:127.0.0.1" when you start cgminer if you want the local machine to be able to send cgminer the 'quit' command(The 'W:' means allow 127.0.0.1 to have write/priviledged access to cgminer)

The next verison will still allow all read access to cgminer as any current version does without changing the options you start cgminer with.

As mentioned above in my quote, the 'quit' command will also be fixed in the next release.

Also for lodcrappo:And what is an unavoidable bug in probably every piece of API usage software, that you can fix with 1.2:At the moment you probably look for "MHS 5s" to find the 5s average.That will actually fail if anyone starts cgminer with the --log option with some value other than 5.You can find the correct value for '5' with the 'config' command in the new 1.2 "Log Interval" - which of course will be '5' unless someone runs cgminer with the --log option.(The --log option has been in cgminer for a long time)So if "Log Interval" is "10" then you should look for "MHS 10s" not "MHS 5s"

...quit without the | did not work in the version I used in creating the BAMT controller for cgminer. I will retest this the next time we update....

"quit\n" didn't (and never will) work."quit" always has been accepted by the API to mean quit cgminer - but stopped working due to a problem with the api.c doquit() function - however, the command "quit" was being accepted and attempting to do what was requested.You should not be adding extra characters on the end - as your normal reporting interface shouldn't do that either (if it does)

I'm trying to overvolt a reference 5970 in BAMT, but cannot get it to work.I have tired every possible variation in bamt.conf I can think of, but nothing seems to work.Using atitweak I can get the card to undervolt, but overvolting just seems impossible...Is there some sort of built in lock that stops setting vcore higher than 1.05?

I'm trying to overvolt a reference 5970 in BAMT, but cannot get it to work.I have tired every possible variation in bamt.conf I can think of, but nothing seems to work.Using atitweak I can get the card to undervolt, but overvolting just seems impossible...Is there some sort of built in lock that stops setting vcore higher than 1.05?

I don't believe there is any linux tool (not just limitation of BAMT) which enables overvolting.

There is RadeonVolt but it doesn't work with 5900 series. If you want to overvolt in Linux you are looking at a custom BIOS flash.

I'm trying to overvolt a reference 5970 in BAMT, but cannot get it to work.I have tired every possible variation in bamt.conf I can think of, but nothing seems to work.Using atitweak I can get the card to undervolt, but overvolting just seems impossible...Is there some sort of built in lock that stops setting vcore higher than 1.05?

I don't believe there is any linux tool (not just limitation of BAMT) which enables overvolting.

There is RadeonVolt but it doesn't work with 5900 series. If you want to overvolt in Linux you are looking at a custom BIOS flash.

I wonder how (or if) windows tools which allow overvolting would work under wine.

I'm trying to overvolt a reference 5970 in BAMT, but cannot get it to work.I have tired every possible variation in bamt.conf I can think of, but nothing seems to work.Using atitweak I can get the card to undervolt, but overvolting just seems impossible...Is there some sort of built in lock that stops setting vcore higher than 1.05?

I don't believe there is any linux tool (not just limitation of BAMT) which enables overvolting.

There is RadeonVolt but it doesn't work with 5900 series. If you want to overvolt in Linux you are looking at a custom BIOS flash.

I'm trying to overvolt a reference 5970 in BAMT, but cannot get it to work.I have tired every possible variation in bamt.conf I can think of, but nothing seems to work.Using atitweak I can get the card to undervolt, but overvolting just seems impossible...Is there some sort of built in lock that stops setting vcore higher than 1.05?

I don't believe there is any linux tool (not just limitation of BAMT) which enables overvolting.

There is RadeonVolt but it doesn't work with 5900 series. If you want to overvolt in Linux you are looking at a custom BIOS flash.

Anyone getting BAMT to work on GA-990XA-UD3 bios version F8 version 1.1? I can't seem to boot from the USB, downloading linuxcoin but I would rather have BAMT working, there is a BIOS update that supports Support Quick Boost function which is version F10G but I need a workable USB drive to update the BIOS? can anyone confirm that this will fix my issue to get BAMT to boot?

Bitcoinica still has not given me 50% of my claim of 600 BTCINTERSANGO can go down with bitcoinica for abandoning customersAlberto Armandi is a SCAMMER