This pool only as about 2-3Th/s compered to other Bitcoin sites, but the pool also mine other sha256 coins which hopefully help out. It wouldn't be so bad if we found a block ever 3-4 days, but it just hasn't happened yet  The good thing is, is that you got more of a share of the block when we do find it, 'cos there is only about a hundred or so people mining sha-256! Well I wish you guys good luck, at this difficulty rate and the age of my miner I need to be pulling in daily BTC amounts esp with the next difficulty coming up. I'll see you when the alt coins become more profitable to mine. |
|
|
|
The pool as not found a block yet, so you/we haven't been paid yet.
So effectively we are almost solo mining with a pool this small? |
|
|
|
BTC minimum auto threshold set to 0.01 coins. BTC withdrawals under 0.01 will be subject to a fee of 0.001 BTC.
Shouldn't my BTC total be slowly incrementing upwards as I mine? I've got 9489408 valid round shares and 0 invalid but I've got 0.00000000 BTC earned after nearly 20 hours of mining. On other pools I would have slowly been creeping towards 1 BTC and my total BTC would be increasing incrementally as I mined. Thanks |
|
|
|
I spoke to soon. My fathers Saturn, which has been running great since we got it displays this on the cgminer output screen sometimes.
013-11-02 09:28:09] KnC: core 0-34 was disabled due to 10 HW errors in a row
[2013-11-02 09:28:14] KnC: core 4-166 was disabled due to 10 HW errors in a row
Is there a particular cause of this and is it something that can be fixed? I have ran enabledallcores and using .98 firmware. Just sub-standard hardware?
Try going back to 0.96 |
|
|
|
Added a few Gh to the BTC pool  |
|
|
|
I found a block in my pool First BTC Block for me! Also my jupiter is much happier on 0.96 sitting at 555Gh/s on the box and 551Gh/s at the pool. With a 10 round average climbing from 531Gh/s |
|
|
|
|
Found my Jupiter hashing at 140Ghs just now (cgminer and pool), so back to 0.96 for me.
|
|
|
|
Those are good points I guess there is no way to give access to just the web interface and block ssh access.
If not I guess the renter would have to prepay enough to justify the risk.
As I said, the root password is not the same as the admin password, you can change the root password to be different to the admin (web login) password. So change the root password and they can't ssh into the box, they can just use the web admin. To change the root password from ssh just type passwdTry it, change the root password, then logout of ssh and login again with the new root password. You will notice that the web account still uses the old password. If you want to change the web account password its: passwd admin |
|
|
|
I have a hypothetical question. If a 3rd party wants to rent a few days of hashtime on my Jupiter and I give him remote access including my password, if he changes the password without telling me is there any way to regain access without the new password or is the Jupiter permanently hi-jacked?
Change the root password then you can always get in and change the admin password |
|
|
|
|
Hmm slush's seems to be suffering from a DDOS
|
|
|
|
So I was one of the lucky ones that got my Jupiter which came with 0.95 and flashed it to 0.96 and got it hashing at 555 Gh/s on the miner and 555 Gh/s on the pool (Slush) 0.97 dropped my performance down to 525 Gh/s on the miner and sub 510 average on the pool. I left it a few days to get up to speed but it never did. 0.98 showed no better, if anything out was worse with cgminer disabling and enabling cores all the time. So in desperation I flashed back to 0.96 and everything is back to normal speed. Weird. Oh and my miner still shows 1.1.2000 after reboots and never change to the correct date. Otherwise everything is good |
|
|
|
Anyone noticed their miner has the date 1 Jan 2000?
clear browser cache & make sure your pc time is correct.. had that one... hehe No mine has that date on the miner, if I ssh in. then you are not using 0.97, right? That was the case for earlier firmwares.... Nope, been on 0.97 since it was released |
|
|
|
Anyone noticed their miner has the date 1 Jan 2000?
clear browser cache & make sure your pc time is correct.. had that one... hehe No mine has that date on the miner, if I ssh in. |
|
|
|
|
Anyone noticed their miner has the date 1 Jan 2000?
|
|
|
|
Cklovas nor any rep ever never instructed anyone to erase the .factory files.
Don't know why someone would do such a thing.
I D ten T error most likely |
|
|
|
Anyone here had that problem? Ckolivas, is there a way to use your code without changing the kncminer boot files? Using bfgminer or cgminer alternatives don't involve directly touching those files, its just people deleting them by accident thats causing the problem. I'd hazard to guess that its the network.conf.factory thats causing the problem, if deleted the miner won't be able to get a dhcp address probably because it turns on dhcp. |
|
|
|
regarding the latest news I'm really wondering how many customers have put themselves out of mining the last days ? (...)
The missing files are causing critical issues, and the miner is no longer able to complete its boot sequence.
The files concerned, are;
Cgminer.conf.factory
Network.conf.factory
(...)
Further more I'm not pleased to read that a missing default config file, stored on a persistent partition where users might modify or even delete it, causes a complete boot failure of $k hw used for btc-mining. Seriously ?! Without having deeper knowledge of the exact technical reasons which lead KnC's devs to this decision: How about a simple 'check if file exists if not skip it or copy some default-config from system-image' ? Or as alternative put those files in a place a user can not damage (all dirs except '/config').. You risk it by SSH'ing to the device, basically don't do it unless you are 100% sure you won't mess up. I don't blame KnC for taking this stance. After all on the devices web interface it warns "KnCMiner products are carefully engineered and are not designed to be user serviceable in hardware or software other than when specifically directed by a member of the KncMiner team." |
|
|
|
somebody doesn't like me helping competition - i post and pool stops responding, distributed denial of service attack?
Slush? Yes, my Jupiter just switched to my backup pool |
|
|
|
Crap, everyone is reporting their chips running in the 45 degree range. I have one at 48, two at 55 and one at 64. I'm hashing at a pretty stable rate of around 540-550. Should I be concerned about the temps?
No, mines the same. People are chasing ghosts around here. |
|
|
|
|
Show Posts
