That doesn't sound good. Has anyone else tested this version out yet?

Thanks for the reply and I am glad to hear development continues. I will point El to your reply later today. Thanks again. When a new release is published, I will be more than happy to pay my part of the bounty.

Hi Shadders, could you please comment on this post regard x-roll-ntime -> https://bitcointalk.org/index.php?topic=18567.msg560731#msg560731

lodcrappo - thanks for all of your assistance, BAMT is a great piece of software.

Since phoenix sound like it is going to stay an integral part of bamt, I have started chiming in over on the Phoenix thread regarding what needs to be corrected in phoenix.

thread here - > https://bitcointalk.org/index.php?topic=6458.0

It would seem that slush has identified the problems with phoenix and we are looking for others to help.

There is currently a 30 BTC bounty to get the errors slush has found corrected along with rollNTime and other small fixes. If anyone watching the BAMT thread would like to throw in on the bounty or can do the work necessary, please help out.

Thanks.

Any luck slush?

Server2 has 1/3 the load of the main server. You would do good to mine on server2. All of the stats from server2 still show up on this page -> https://arsbitcoin.com/poolstats.php

Well said.

On github ( https://github.com/jedi95/Phoenix-Miner/network ), it looks like aldiyen has added rollNTime support to his git repo.

I'll add another 10 BTC to the bounty to see these issues fixed.

Well i'm sure there are a lot of people using Phoenix to mine, is there anyone who can fork the project and create a new release fixing these issues if Jedi95 is not around? Again, I am willing to pay to see the phoenix miner properly cleaned up with the necessary changes made. Maybe we should all start a bounty? Maybe that would get development on the project going again.

Hotdog does have a point. I can ssh into my miners from my iPhone and fix almost any issue as long as I have cell service. If you have an iPhone, you might want to also checkout the app iBitcoin, it's pretty impressive and shiny.

Are these the open issues over at github.com or are there other outstanding issue not yet posted?

EDIT:

The reason I am interested is that El over at btcguild.com has implemented QoS into his pool server and it doesn't play nice with phoenix. Here is the  conversation:

[16:37] <gigavps> @Eleuthria still getting miner idle warnings, since you suggested it was somehow on my end i reset all network equipment
[16:37] <gigavps> [05/10/2011 20:34:26] Phoenix v1.6.2 starting... [05/10/2011 20:34:26] Setting auto kill signal for 180 seconds. [05/10/2011 20:34:26] Connected to server [05/10/2011 20:34:26] Currently on block: 148211 [05/10/2011 20:34:30] Result: 050dafcb accepted [05/10/2011 20:34:33] Result: c74016fc accepted [05/10/2011 20:34:34] Result: 099d91dd accepted [05/10/2011 20:34:45] Result: 6c6bc416 accepted [05/10/2011 20:34:46] Result: 2e039bbe accepted [05/10/2011 20:34:50] Result: 0a9de4ce accepted [05/10/2011 20:35:08
[16:37] <gigavps> [05/10/2011 20:35:51] Warning: work queue empty, miner is idle
[16:41] <@Eleuthria> I'd suggest a better miner if you're running that fast on a single client
[16:41] <gigavps> all gpus are 310-317 Mh/s
[16:42] <gigavps> i'm using phoenix
[16:42] <gigavps> are you suggesting that phoenix is not a good miner?
[16:42] <@Eleuthria> Yes.
[16:42] <@Eleuthria> Phoenix is terrible and inefficient, it tosses out a getwork after finding a single share instead of exhausting the space
[16:44] <@Eleuthria> cgminer is better in every way
[16:44] <gigavps> i am all for learning and improving, but why do i not have these problems on other pools like arsbitcoin.com, yourbtc.net, mainframe.nl?
[16:44] <@Eleuthria> But if you insist on using phoenix, add -q 2 or -q 3
[16:45] <@Eleuthria> Because we put you in the back of the line after just feeding you work.
[16:45] <@Eleuthria> So you acn't just spam us with getwork requests.
[16:45] <@Eleuthria> Which is whats happening in your log
[16:45] <@Eleuthria> You finished 3 shares in under 3 seconds
[16:45] <Dyaheon> you're the guy with the 20GH/s operation?
[16:46] <@Eleuthria> On phoenix, that means you're issuing a new getwork multiple times per second
[16:46] <@Eleuthria> Even though a single getwork can contain multiple shares
[16:46] <@Eleuthria> poclbm fixed that, cgminer never had that problem, and my understanding is diablo never had that issue either.

Is there someone watching this thread that can fix this issue?

I would be willing to offer a bounty to have phoenix patched and a new release of the miner created.

Try mining on server2.arsbitcoin.com if you are not aleady doing so.

What about the new features in cgminer to set a range for gpu clock, fan and temp? Is this of no value or will it be built into bamt somehow?

How can I add -q 2 command line param for when bamt starts up phoenix?

EDIT:

Here is a conversation I had with El at btcguild about phoenix...

[16:37] <gigavps> @Eleuthria still getting miner idle warnings, since you suggested it was somehow on my end i reset all network equipment
[16:37] <gigavps> [05/10/2011 20:34:26] Phoenix v1.6.2 starting... [05/10/2011 20:34:26] Setting auto kill signal for 180 seconds. [05/10/2011 20:34:26] Connected to server [05/10/2011 20:34:26] Currently on block: 148211 [05/10/2011 20:34:30] Result: 050dafcb accepted [05/10/2011 20:34:33] Result: c74016fc accepted [05/10/2011 20:34:34] Result: 099d91dd accepted [05/10/2011 20:34:45] Result: 6c6bc416 accepted [05/10/2011 20:34:46] Result: 2e039bbe accepted [05/10/2011 20:34:50] Result: 0a9de4ce accepted [05/10/2011 20:35:08
[16:37] <gigavps> [05/10/2011 20:35:51] Warning: work queue empty, miner is idle
[16:41] <@Eleuthria> I'd suggest a better miner if you're running that fast on a single client
[16:41] <gigavps> all gpus are 310-317 Mh/s
[16:42] <gigavps> i using phoenix on bamt
[16:42] <gigavps> are you suggesting that phoenix is not a good miner?
[16:42] <@Eleuthria> Yes.
[16:42] <@Eleuthria> Phoenix is terrible and inefficient, it tosses out a getwork after finding a single share instead of exhausting the space
[16:44] <@Eleuthria> cgminer is better in every way
[16:44] <gigavps> i am all for learning and improving, but why do i not have these problems on other pools like arsbitcoin.com, yourbtc.net, mainframe.nl?
[16:44] <@Eleuthria> But if you insist on using phoenix, add -q 2 or -q 3
[16:45] <@Eleuthria> Because we put you in the back of the line after just feeding you work.
[16:45] <@Eleuthria> So you acn't just spam us with getwork requests.
[16:45] <@Eleuthria> Which is whats happening in your log
[16:45] <@Eleuthria> You finished 3 shares in under 3 seconds
[16:45] <Dyaheon> you're the guy with the 20GH/s operation?
[16:46] <@Eleuthria> On phoenix, that means you're issuing a new getwork multiple times per second
[16:46] <@Eleuthria> Even though a single getwork can contain multiple shares
[16:46] <@Eleuthria> poclbm fixed that, cgminer never had that problem, and my understanding is diablo never had that issue either.
[16:47] <gigavps> do you mind if I post this conversation on the bamt forum topic?
[16:47] <@Eleuthria> bamt?
[16:48] <gigavps> https://bitcointalk.org/index.php?topic=28967.0
[16:48] <@Eleuthria> euh...one of those
[16:49] <gigavps> not sure what you mean
[16:50] <@Eleuthria> Never been a fan of these linuxcoin distros
[16:50] <gigavps> how do you decide when I go to the back of the queue? by worker? by ip address?
[16:50] <gigavps> i run 5 gpus per worker
[16:50] <@Eleuthria> Are you able to add command-line arguments to phoenix in that thing
[16:51] <@Eleuthria> -q 3 would fix it

I might be a 0Mh/s right now but i'm at the top of the donors board! -> https://arsbitcoin.com/statsDonate.php

Catch me if you can....

With the interest thus far, there does not seem to be a big market for something like this.

I have been tossing around the idea, hence the post. I want to do things a bit differently as in provide the tech / hardware / redundancy for a fixed monthly fee and let the pool operator market their pool as they please.

I got you to 85. 

1AgY6zRuqTF6jSgK1WD7pRVodnSXsfMDA7

Where do you mine?