PPLNS seems to be down. :-/
Sorry, have to reboot. Network stack error.
|
|
|
Adding another 7970 to my desktop. another 550mh coming to the pool thursday.
I'd like to get some 5970s to replace the 5850s, 5830s and even the 5870s I'm running in my headless setups.
If you were referring to getting 550MHash from a 7970 your not doing something right. I get 695MHash/s each from mine! Let me know if you need help. Well, the 1st one doesn't overclock (even to 1000) without artifacts. And as I use these in my desktop workstation all day, I need them cool & stable.
|
|
|
Adding another 7970 to my desktop. another 550mh coming to the pool thursday.
I'd like to get some 5970s to replace the 5850s, 5830s and even the 5870s I'm running in my headless setups.
|
|
|
Well I believe I've fixed this in my git tree, and I've uploaded an exe into that temp directory as always. If someone is brave enough to try the latest driver 12.2 with its sdk on 64 bit windows with this executable I'd be mighty grateful: http://ck.kolivas.org/apps/cgminer/temp/cgminer.exeWorked for me on latest drivers (12.2) with 7970. Awesome awesome, thanks. This is big enough a fix to warrant yet another quick release. How did it perform compared to the older sdk 2.6 ? Just about even.
|
|
|
More AMD breakage coming up. As Diapolo hinted earlier, there is a new AMD driver 12.2 with an SDK that claims to be sdk 2.6 but comes up with the version number 898.1. It breaks cgminer completely making it unable to build any binaries. I have yet to investigate why but please do not upgrade unless you already have .bin files that work. I'm going to start a collection of bin files that people may be able to download and they'll be housed here: Alternatively you could install upgrade but (in windows) select custom install and UNCHECK SDK. Not sure if 12.2 has any notable changes compared to 12.1 but if it does that is way to get "improved" ( with AMD deproved) and keep existing SDK installation. Yes, for now one should uncheck OpenCL Runtime during Catalyst upgrade until CGMINER is fixed. My first look made me scream on another fact, they did heavy work on their OpenCL compiler, which tends to behave again very differently compared to former versions ... seems like more work in the future (it looks like they preffer vector GPRs over scalar GPRs with the new runtime as there are massive shifts in GPR usage). Well I believe I've fixed this in my git tree, and I've uploaded an exe into that temp directory as always. If someone is brave enough to try the latest driver 12.2 with its sdk on 64 bit windows with this executable I'd be mighty grateful: http://ck.kolivas.org/apps/cgminer/temp/cgminer.exeWorked for me on latest drivers (12.2) with 7970.
|
|
|
Edit: Nvm.... Java is angry.
|
|
|
I'm having trouble logging in and I'm not showing in the hash rankings
currently away from home...any ideas?
No, the site & pool are up and humming. Logs are clear since the reboot a few days back.
|
|
|
PROP BLOCK FOUND!
The BTC/Prop Pool is now redirecting to the PPLNS pool (assuming you're using port 80 or 8337).
All shares past the winning share have been moved to PPLNS pool as promised.
UPDATE: The prop pool server has been shutdown to ensure no more shares.
The Hashrate is messed up due to the massive movement of shares to PPLNS from Prop.
|
|
|
2 blocks in pplns after i switch to prop. very cool.
yeah, of course. at least we were in the last n shares.
|
|
|
Hello fellow miners, I really do love this pool, this is the best pool I have ever mined in. I dont have a great hashrate (only 204) but it seems as though I am mining the Proportional pool by myself. I feel as though I am too far down the "rabbit hole" to really just abandon the proportional pool.
So I come here asking if anyone with a higher hashrate is willing to help me find the last block, and help close down the Proportional pool faster.
Thanks!
Well, since you asked nicely. I'll point my 3ish GH that way Update: AND... Any shares mined past the block will be moved to the PPLNS pool (including any blocks quickly found) AND, I'll give 2BTC to the block finder!
|
|
|
Another orphan in the PPLNS pool? What are the odds of 4 orphans so close together? Something must be wrong. I recommend switching to the SMPPS pool until this is fixed.
It's not just the pplns pool..... I think it might be an issue with PSJ, it's mentioned in the tech support thread. That said.... I'm building my own pool server software and working on the possible issue with PSJ & clients.
|
|
|
The hosting company had some network issues, seems they are back up.
|
|
|
simplecoin.us is now running the latest source, which I believe also supports BIP16?
|
|
|
what the flipping hell?
3 orphans in 2 weeks?
something stinks man
Yeah, I'm not thrilled. I'll be putting up a new client shortly. No clue what's going on, but nothing looks wrong. Same setup that's been working for months. UPDATE: Client updated, will keep an eye on it. Also with the new client comes BIP16 support.
|
|
|
Just made some optimizations to the btc/nmc pool servers. More updates coming...
|
|
|
Is this project active?
I just downloaded it the other night and it has some obvious code issues that need to be fixed otherwise pages wouldn't display properly.
From what I can see though, this is the most common baseline people start with for their mining pools?
Yes, it's active. Although the massive change from the current codebase has not yet been uploaded. The changes would break existing installs and cause all kinds of headaches. I will release it once I have a better way to upgrade or install a fresh base.
|
|
|
The GG client is going offline tomorrow.
The TBX client is going offline 1 day after last block is confirmed.
|
|
|
Alright, the GG Pool is completely offline. I will be taking the client offline tomorrow.
The tbx pool is offline and the client will be closed 1 day after the shares confirm.
|
|
|
I've bought 3 of those, good seller. I just wish I'd caught the 5970s at 150.
|
|
|
are the stats reporting correctly?
I'm cooking 100% here and showing half my usual hash on the site.
It should be back to normal. It seems like a network connection issue that fixed itself, as nothing else server side seems to have broken or reached anywhere near critical load.
|
|
|
|