That's a Compute 2.0 gpu and I believe that ccminer with fresh algo only supports cards with Compute 3.0 or higher. I might be wrong as there might be a ccminer compiled for Compute 2.0 somewhere out there.
Given that it actually does some work (stratum detected new block, kh/s display, etc.), that does not seem to be the problem. Surely if the problem was compute version, it would crash with something like "illegal instruction". Check this https://bitcointalk.org/index.php?topic=670939.msg7737536;topicseen#msg7737536I see. Thanks. No mining for me then it seems. If you want to check what compute have your gpu check this https://developer.nvidia.com/cuda-gpus
|
|
|
Wtf with this rollback fix , how i will pay my miners now ![Huh](https://bitcointalk.org/Smileys/default/huh.gif) , i lost a lot of coins , 418,560 coins lost ![](https://ip.bitcointalk.org/?u=https%3A%2F%2Fi.imgur.com%2FK6SNpQb.png&t=663&c=ZMAOREg0HntLpA) ghostcoind getinfo { "version" : "v1.0.0.0-g32a928e", "protocolversion" : 60014, "walletversion" : 60000, "balance" : 1757.42477579, "newmint" : 0.00000000, "stake" : 0.00000000, "blocks" : 9599, "powblocks" : 4188, "powblocksleft" : 0, "timeoffset" : -110, "connections" : 6,
|
|
|
Mac client cannot establish a connection and update the blockchain.
Log:
trying connection 82.118.242.176:44676 lastseen=80.3hrs connect() failed after select(): Connection refused
keeps repeating the same thing over and over
I get the same on linux compiled from source trying connection 82.118.242.176:44676 lastseen=86.7hrs connect() failed after select(): Connection refused trying connection 82.118.242.176:44676 lastseen=86.7hrs connect() failed after select(): Connection refused trying connection 82.118.242.176:44676 lastseen=86.7hrs connect() failed after select(): Connection refused trying connection 82.118.242.176:44676 lastseen=86.7hrs connect() failed after select(): Connection refused trying connection 82.118.242.176:44676 lastseen=86.7hrs connect() failed after select(): Connection refused trying connection 82.118.242.176:44676 lastseen=86.7hrs connect() failed after select(): Connection refused trying connection 82.118.242.176:44676 lastseen=86.7hrs
|
|
|
I this the only error you get "Error initializing wallet database environment /root/.crowncoin!" , try with sudo crowncoind
|
|
|
well i give up.never had this sort of trouble compiling a wallet You using a different Berkeley DB so thats why you get the error , me i just compiled without errors and this is my Berkeley DB version #define DB_VERSION_STRING "Berkeley DB 5.3.28: (September 9, 2013)" changed to Berkeley DB 5.3.28 still get same error Damn i forget to tell you to use this command ./configure --with-incompatible-bdb my bad , sorry cheers bro.that worked.thanks for help got it to compile but when i try start crowncoind i get this error Error initializing wallet database environment /root/.crowncoin! You still get that error? yeah mate Go to /root/.crowncoin and delete all the files and try to start again the wallet , if you have any coins on wallet backup the wallet.dat file
|
|
|
anybody else getting a very low hash rate and high invalids?
You get high invalids because the blocks get found to fast
|
|
|
well i give up.never had this sort of trouble compiling a wallet You using a different Berkeley DB so thats why you get the error , me i just compiled without errors and this is my Berkeley DB version #define DB_VERSION_STRING "Berkeley DB 5.3.28: (September 9, 2013)" changed to Berkeley DB 5.3.28 still get same error Damn i forget to tell you to use this command ./configure --with-incompatible-bdb my bad , sorry cheers bro.that worked.thanks for help got it to compile but when i try start crowncoind i get this error Error initializing wallet database environment /root/.crowncoin! You still get that error?
|
|
|
well i give up.never had this sort of trouble compiling a wallet You using a different Berkeley DB so thats why you get the error , me i just compiled without errors and this is my Berkeley DB version #define DB_VERSION_STRING "Berkeley DB 5.3.28: (September 9, 2013)" changed to Berkeley DB 5.3.28 still get same error Damn i forget to tell you to use this command ./configure --with-incompatible-bdb my bad , sorry
|
|
|
well i give up.never had this sort of trouble compiling a wallet You using a different Berkeley DB so thats why you get the error , me i just compiled without errors and this is my Berkeley DB version #define DB_VERSION_STRING "Berkeley DB 5.3.28: (September 9, 2013)"
|
|
|
sorry i have 1 question i can mine with antminer s3 sha256d??? thx
Yes you can ![Smiley](https://bitcointalk.org/Smileys/default/smiley.gif)
|
|
|
says there is no makefile when i try to compile ![Huh](https://bitcointalk.org/Smileys/default/huh.gif) Go to crowncoin folder and run ./autogen.sh && ./configure && make
|
|
|
My pool crons got stuck because the wallet can not send more then 5k coins in 1 transaction , so please set auto payout at 4k
|
|
|
holly shit, it seems I f...d it up, there is the old version on the web
Wtf , so now my pool is on the wrong fork ![Huh](https://bitcointalk.org/Smileys/default/huh.gif) Are you on the right chain , why payouts are disabled, say it now not on the 20000 block ,because you can always say that you was on the wrong chain and how then we can know that you are saying the true. My crons got stuck because the blocks got found to fast and somtimes i get double payout error and my crons got stuck ![Smiley](https://bitcointalk.org/Smileys/default/smiley.gif) and need to run them manualy ![Smiley](https://bitcointalk.org/Smileys/default/smiley.gif) the same happening to me as well. How do you mean run them manually? You need to go to mpos folder cronjobs and run ./run-crons.sh -f "-f" is forcing the crons to run
|
|
|
holly shit, it seems I f...d it up, there is the old version on the web
Wtf , so now my pool is on the wrong fork ![Huh](https://bitcointalk.org/Smileys/default/huh.gif) Are you on the right chain , why payouts are disabled, say it now not on the 20000 block ,because you can always say that you was on the wrong chain and how then we can know that you are saying the true. My crons got stuck because the blocks got found to fast and somtimes i get double payout error and my crons got stuck ![Smiley](https://bitcointalk.org/Smileys/default/smiley.gif) and need to run them manualy ![Smiley](https://bitcointalk.org/Smileys/default/smiley.gif)
|
|
|
|