Wow, 737 GH/s, highest I've seen here  |
|
|
|
Everyone working properly now? Everything looks good from this end, all shares processed and stats should be in sync. Servers appear stable and all is well... While it was down, I made some mods to the getwork server that eliminated some resource hogging and unstable code related to long polling - if anyone notices problems with LPs, let me know, but it should work much better and faster now. A long poll should hit as soon as a new block is broadcast on the network instead of a second or two later. Also, let me know how the drop outs after a block is solved work out now... I will keep an eye on it, but I can't always see it when a block solves, if I'm off killing people in BF3  Block processing time seems to be between 3 - 6 seconds, down from a maximum of 6 minutes previously. Seems to work fine. The fixes/optimizations sound good, let's hope they work |
|
|
|
|
Are the website and pools both down atm?
edit: nvm, works now, must have been you, Inaba, fixing the block thing.
edit2: Thanks for the fixes!!
edit3: I guess you still are working on stuff, can't connect to both site and pools.
|
|
|
|
Minimum 20% (VAT) of total value (including shipping cost) goes to her royal majesty if I am not wrong.
If it arrives by couriers, they may charge another fee on top of that for the handling.
BFL has now put international shipping cost at $88 (forgot what it was before but lower I think), that smells like courier to me.
Sounds as we could use a reseller within EU. |
|
|
|
Is merged mining still worthwhile?
@0.0038 $ per NMC, it seems fairly pointless.
Personally, every last bit counts. |
|
|
|
I must say that both Goat/Chaang AND Bitcoin Magazine/its representatives have been acting in an extremely childish manner. I thought Bitcoin Magazine would be something to look forward to. Maybe not.
Without taking side in the dispute, I would say that unless they post transcripts/pictures of this forum in the magazine, the quality of the magazine shouldn't be affected by what is discussed here. That's one thing I don't get. How do people extrapolate the content/value/quality of the magazine based on a disagreement going on in the forum? It makes no sense to me... A disagreement outside of the magazine is just that - outside of the magazine. I don't get that either. Oh well, so many things in life are... curious. edit: I think Im done editing this post. |
|
|
|
I must say that both Goat/Chaang AND Bitcoin Magazine/its representatives have been acting in an extremely childish manner. I thought Bitcoin Magazine would be something to look forward to. Maybe not.
Without taking side in the dispute, I would say that unless they post transcripts/pictures of this forum in the magazine, the quality of the magazine shouldn't be affected by what is discussed here. |
|
|
|
Ordered 3 copies.
Hope to see the first one in the mail very soon!
Don't hold your breath. I ordered some copies as well, but I'm not expecting them until the middle of march. |
|
|
|
Yeah, i'm not sure what happened there. The getwork server was just plain locked up, no crash or error... kind of bizaar. I swear, no problems for weeks or months and the minute I am out of contact for more than an hour or two, BAM. It's like it lies in wait for me...
Back in the days, when I had a Cyrix '686 cpu, I couldn't leave it's company if I was installing stuff. As long as I was in the room no errors would come up, if I had to go out of the room for just a few mins, I would always come back to an error/bsod. |
|
|
|
Happy to hear about the progress |
|
|
|
If I were just mining on an internet connection, no surfing, connected to a pool what can I expect my bandwidth usage to be for a month?
Will it change as I add on more mining power?
I cannot give you any specific numbers, but the bandwidth usage is negligible. I am downloading/uploading with full speed pretty often, and it does not affect the miners at all. |
|
|
|
Doing lots of work on the source again, so sorry for no real updates at the moment, but a lot of stuff will change sooner or later. Currently i try seperating parts of the game and put them into the (new) frontpage like user settings and the whole exchange, which i also try to debug at the same time, or more precise: rewrite. So there are currently no big news except that i try to work on my free time on this thing..
Thanks for keeping us informed. |
|
|
|
I have the beginnings of a solution in my head for the new block problem, so it's something I will be working on in the immediate future. It's going to require some changes to the way DGM is handled, so I need to do a lot of testing and checking before I put that type of fix into place.
If you need some help with testing, when it gets so far, let us know, I'm sure some of us would be happy to contribute. |
|
|
|
I've ordered some additional hardware that may help out with this, but it may not make a difference to this particular problem. I think it may stem from the way EMC handles DGM when a new block starts, there's a bucket load of DB activity setting up the new miners for the new block, and there may be some queries that are holding everyone else up. I will investigate that as well as how to best leverage the new hardware.
Crossing my fingers |
|
|
|
|
I'm still having issues with server communication. It seems that whenever we solve a block, I cannot communicate with the servers for a few minutes, tried all the servers, us1/2/3, tried various miners, kernels and internet connections. While it's not a problem for the most part, there is the problem when we solve a fast block, it can be very possible for me not to be able to submit any shares. My connection works fine for everything else, so I think it might be something to do with me connecting to the US servers from Europe, and when we solve a block, and new work has to be distributed, the fact that I'm in Europe, might be reason why I can't come through the "congested" route. At least that is my idea, been watching it happen every single time we solve a block now, this did not occur at my previous pool (MMC).
|
|
|
|
The current code in Git has been updated with a few fixes:
1. Hashrate display should be working correctly now. Please report back if it still doesn't work.
2. Updated opencl and phatk2 to use Diapolo's method of detecting if the device is a CPU.
3. Autodetect messages will no longer appear for devices which have a config manually defined.
The Windows binary has also been updated with these changes.
Could you update the main post to point to the new updated phoenix2? I cant find the updated compiled windows version. As far as I can tell from a little research, jedi95 deleted the old phoenix-2.0.0.zip, and reuploaded a new file with the same name approx. 3 hrs ago, the link in the first post should work, and I'm guessing it's the updated binary. |
|
|
|
|
Just tried to log in, for me, it all seems to work. All the rigs are there etc.
|
|
|
|
total btc: 99.575
est conv: 5.85
______
total: 582.51375
cost: 568.5 + 60 = 628 total
close enough for me. card has been sent.
Great news! |
|
|
|
|
Show Posts
